HP Data Protector 6.2 software integration with HP 3PAR Storage System

29
[Normal] From: [e-mail] "MSVSSW" Time: 4/18/2011 9:22:21 PM
Saving writer configuration.
[Normal] From: [e-mail] "" Time: 4/18/2011 9:25:32 PM
OB2BAR application on "tpc193.tic.dp" disconnected.
[Normal] From: [e-mail] "FL194_Writer0" Time: 4/18/2011 9:22:49 PM
Unloading medium to slot C:\FL1\10394b8254dac5491551665009a.fd from device
FL194_Writer0
[Normal] From: [e-mail] "FL194_Writer0" Time: 4/18/2011 9:22:49 PM
COMPLETED Media Agent "FL194_Writer0"
C:\Users\administrator.TIC>
Where:
-vss
specifies the type of restore session. It this case, it is a Virtual Shadow Copy session.
-barhost tpc193.tic.dp
specifies the server name where data will be restored.
-tree "/SqlServerWriter(SQL Server 2008 R2:SQLWriter)/TPC193/DB1_3PAR"
specifies the name of the object to be restored.
-no_recovery
specifies that Data Protector should leave the restored database in restoring mode.
Figure 26: MS SQL Database is left in the restoring mode after restore
The next step is to restore the database transaction logs that have been taken since the full VSS based
backup. Restore of transaction logs can be done using the Data Protector Restore GUI (see
Figure 27).
Transaction log backups must be restored one by one in the order they have been taken, starting with
the one that was taken after the full VSS backup. Make sure that you select the option Restore only this
backup. In addition, you must specify the following option in the Options tab (see
Figure 28):
Leave database nonoperational, but be able to restore additional transaction logs.
With these options selected, the database will remain in the restoring mode and it will be possible to
restore the next transaction backup. When restoring the last transaction backup, select the option
Leave database operational. No additional transaction logs can be restored. This will result in
bringing the database in the online mode after restore of the transaction logs is done.