[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 639
  • Last Modified:

Backup Exec MS SQL Restore

I'm trying to restore an MS SQL backup by redirecting it to another database server using Backup Exec 12.5
when ever i start the restore, the byte count shows 8192 and stays there forever. I have 'inventory-ed' and 'cataloged' as required.
any ideas?
1 Solution
Backup Exec is not related to SQL Server/MS. Please post only related to SQL Server here.
Probably it will be answered by SYMANTEC I believe.
adjaddyAuthor Commented:
I don't see SYMANTEC as one of the zones to select
I have had this issue before when the servers were different versions of SQL with Backup Exec. I think your issue may be caused by a know bug, see http://www.symantec.com/business/support/index?page=content&id=TECH75125
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Ron MalmsteadInformation Services ManagerCommented:
Question ...

Are you attempting to re-direct to a DB that already exists ?..

Try redirecting to a DB name that doesn't exist on the server you are restoring to.
If I remember this correctly...it should create the db for you.
Ron MalmsteadInformation Services ManagerCommented:
Don't create a DB..

Do your DB selection to restore.
On SQL redirection, put in the server you are redirecting to, and "restore to database" with a NEW name of a db that doesn't exist.

On SQL settings, check Replace databases and filegroups
Consistency check - full check including indexes

...try that.
Anthony PerkinsCommented:
>>I don't see SYMANTEC as one of the zones to select <<
adjaddyAuthor Commented:
Sorry guys, none of your responses work
 i need to restore the DB to overwrite an existing one that supports an application we are testing so creating another one won't help me

SQLSergeant Mike
the DB i'm restoring is less than 300GB
Ron MalmsteadInformation Services ManagerCommented:
You could try renaming the current DB to ..."Name Old 04212011",...then restore to the "old name".
adjaddyAuthor Commented:
no other solution worked

Featured Post

What is SQL Server and how does it work?

The purpose of this paper is to provide you background on SQL Server. It’s your self-study guide for learning fundamentals. It includes both the history of SQL and its technical basics. Concepts and definitions will form the solid foundation of your future DBA expertise.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now