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

31
Figure 28: Select option to leave database in the restore mode in order to be able to restore additional transaction logs
An example of the restore-session output of transaction logs can be found in the Appendix B:
Microsoft SQL Server Transaction Log Restore section.
Microsoft SQL restore from virtual copy
In situations that virtual copies/snapshots are still available, it is possible to restore the database data
by promoting virtual copies to its parents. The advantage of using this type of restore is significant
when the amount of data to be restored is relatively large. Similar to the previous section, you must
use Data Protector CLI commands to perform this kind of restore. To repeat the restore process from
the previous section using 3PAR Storage System promotion capability, you must start the omnir CLI
command with the option –manula_restore <name_of_script>. With this option specified,
the restore process will stop at the point where data has to be restored to the production disks. Instead
of restoring data from media, the specified script will be started. The restore process will wait for the
script to finish before continuing with the restore session. The script can be written in the way that
restores the data. It is also possible that the script is just waiting for the user to manually restore the
data.
After starting the restore with this command and when the restore process is waiting for data to be
restored, it is required to perform the following steps to restore data from virtual copies:
• Take the database offline