HP StorageWorks P9000 Replication Manager Software 7.1 CLI User Guide (TB584-96026, May 2011)

Figure 74 Tape restoring multiple databases (multiple volume configuration)
In the operations shown in the above figure, the data restored from tape is stored on secondary volume
2, but when data on secondary volume 1 is restored to primary volume 1, Application Agent treats
this as a completed restoration. As such, EX_DRM_SQL_RESTORE cannot be used to restore DB2 on
secondary volume 2 to primary volume 2. To restore the contents of secondary volume 2 to primary
volume 2, perform the procedure again from tape restoration.
Database status when restoring and recovering
When Application Agent is used to restore data from a secondary volume to a primary volume, the
status of the database becomes either loading or standby.
• Loading status (Reading)
The database can neither be viewed nor updated.
• Standby status (Read-only)
The database can be viewed, but not updated.
Transaction logs can be applied to databases in the loading status and standby status. For details
about operation using transaction logs, see “Operation using SQL Server transaction logs” on page 309.
Backup cannot be performed for databases in the loading status and standby status. To be backed
up, a database in the loading status or standby status needs to be changed to a status that allows
viewing and updating. To allow viewing and updating of a database in the loading status or standby
status, use the drmsqlrecovertool command or drmsqlrecover command to recover the
database. These commands can also be used to toggle the status of a database between loading
and standby.
The following figure shows database statuses during restoration and recovery.
CLI User Guide 279