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

Figure 25: Select Microsoft SQL Writer components to be restored.

Restore to any point-in-time from media

To be able to restore MS SQL database to any point-in-time, the following is required:

• All transaction log backups must be available from the time when the full VSS based backup was

taken until the desired time at which the database should be recovered.

• Database must be left in the recovery mode after restore of full VSS backup is performed (this is

only possible by using the Data Protector CLI command omnir).

Recovery of Microsoft SQL database to any point-in-time is a two-step process:

• Restore full VSS based backup and leave the database in recovery mode.

• Apply all transaction log backups up to the time of recovery.

Note

Make sure that the backup of all remaining transaction logs has been performed before starting the

restore process.

To leave the database in the recovery mode after restore of full VSS base backup, use the Data

Protector omnir CLI. (This cannot be done from the Data Protector GUI). To find out which full

backups are available, use the following CLI command:

C:\>"\Program Files\OmniBack\bin\omnidbvss.exe" -list session

Session Key IR Disk-Only Barlist Name

===============================================================================

[0] 2011/04/18-26:tpc193 FALSE FALSE tpc193_SQL_DB1_3PAR

[1] 2011/04/18-35:tpc193 FALSE FALSE tpc193_SQL_DB1_3PAR

C:\>

To find the component names of the objects that were backed up in the backup session that is to be

restored, execute following command:

C:\>"\Program Files\OmniBack\bin\omnidbvss.exe" -get session 2011/04/18-35:tpc193

===============================================================================

Session ID: 2011/04/18-35

Barlist Name: tpc193_SQL_DB1_3PAR

Bar Hostname: tpc193.tic.dp

Backup Type: FULL

Instant Restore: FALSE