Problem
Database is left in unrecovered state after restore completed successfully
If you set the time for Stop at beyond the end of the RESTORE LOG operation, the
database remains in the unrecovered state as if the RESTORE LOG operation was
run with Leave the database non-operational.
Action
Recover the database to the latest point in time by using the SQL Query Analyzer:
RESTORE DATABASE database_name WITH RECOVERY
After the recovery, additional transaction logs cannot be applied.
Problem
Instant recovery of a Microsoft SQL Server database configured on a Microsoft Cluster
Server system fails with "The physical filename may be incorrect"
Instant recovery of a Microsoft SQL Server split-mirror backup in a Business Copy XP
configuration on a Microsoft Cluster Server system fails with the following error:
[Microsoft][ODBC SQL Server Driver][SQL Server]Device
activation error.
The physical file name '<Data/Log filename>' may be incorrect.
Action
Perform the following steps:
1. Using Microsoft SQL Server Enterprise Manager, detach the Microsoft SQL Server
database that you want to recover.
2. Using Cluster Administrator, take the Microsoft SQL Server Disk resource offline.
3. On the application system, configure the ZDB_TAKE_CLUSRES_ONLINE omnirc
variable.
For details, see “ZDB integrations omnirc variables” on page 425.
4. Start instant recovery.
5. When the message Please, take MS SQL cluster resources online
appears in the Data Protector GUI, bring the Microsoft SQL Server cluster
resources online using Cluster Administrator.
Data Protector Microsoft SQL Server ZDB integration282