SQL thinks the DB is still being restored...

[jymm]

We have a new version of Veritas Backup Exec and are trying to restore a few databases to another SQL 2k server on the network (my test box). Even though the backup job says that it is done (and all I have seen for the last couple of hours) Everything else (enterprise mgr, dbcc checkdb...) thinks the databases are still 'loading' (or being restored).

The mdf & ldf files look to be the correct size, so I know it pushed down all of the data (all 3 gig)

ideas? I have always told the network person that we should not backup unless we planned to restore... now I am wondering ... what was I thinking?

 

[clapag22]

Sounds like it was restored with the "NORECOVERY OPTION" set, which leaves the DB non-operational so you can restore additional transaction logs.

This is from BOL:

RESTORE DATABASE MyNwind
FROM MyNwind_1, MyNwind_2
WITH NORECOVERY
RESTORE LOG MyNwind
FROM MyNwindLog1
WITH NORECOVERY
RESTORE LOG MyNwind
FROM MyNwindLog2
WITH RECOVERY

 

[jymm]

Was not restored through SQL --- restored through Backup-Exec...

 

[SQLSister]

Not familiar with the backup program you used so I can't help there. But you were absolutely right to try to restore. Think how much more upsetting this would be if you were doing this in a crisis when they needed production back on line now. At least now you have the time and space to figure out what went wrong and write a procedure to follow when the real thing does occur. It's for times like these that we can be grateful we tried something first on a a test box!

But clapag22 may be on to something, your backup program may have a simliar option and you just need to find it.

 

[SQLBill]

Backup Exec has an option on the SQL tab called RECOVER DATABASE. This MUST be checked for the LAST file being restored.

BTW-there is a forum for Veritas: Backup Exec


-SQLBill

 

[jymm]

newest version does not have that option --- I will re-post in veritas forum since over night things did not solve themselves

 

[jymm]

interestingly enough the person in charge of the backup software checked the box to have Backup Exec start a FULL DBCC after the restore... that seemed to make things work.

ah - 'enhancements' to vendor software without documentation... what a joy

thanks all