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

33
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:14:59 AM
Gathering Existing Writer Metadata.
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:15:01 AM
Gathering Backed Up Writer Metadata.
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:15:01 AM
Checking writer configuration.
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:15:01 AM
Performing Pre-Restore phase.
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:15:03 AM
Starting pre-exec script 'C:\Program Files\OmniBack\bin\SQL_man_restore.bat'...
Executing vss manual restore
=======================================================================
Please start restore of SQL server files now!
Delete file C:\deleteWhenFinished.txt
on machine TPC193
as soon as restore finishes!
=======================================================================
==============================================
C:\deleteWhenFinished.txt deleted, continuing.
==============================================
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:21:17 AM
Performing Post-Restore phase.
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:21:17 AM
Script executed successfully.
[Normal] From: [e-mail] "MSVSSW" Time: 4/19/2011 1:21:19 AM
Saving writer configuration.
[Normal] From: [e-mail] "" Time: 4/19/2011 1:24:31 AM
OB2BAR application on "tpc193.tic.dp" disconnected.
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.
-manual_restore SQL_man_restore.bat
specifies that data will be restored by a third party tool. Instead of restoring data directly,
Data Protector executes the specified script which restores the data.
An example of the SQL_man_restore.bat script used in the above session can be found in
Appendix A: Script used for manual MS SQL database restore section.
Follow the steps described in the previous section to restore all required transaction logs and to
recover the database to the desired point-in-time.
Microsoft Exchange 2010 backup
Microsoft discontinued the support for online backup APIs with this version of Exchange. The only
possible way to backup Exchange 2010 is using Virtual Shadow Copy Service. It is possible to
perform backup of Exchange 2010 by using Data Protector’s MS Volume Shadow Copy Integration
as it was explained in the previous sections. Due to the complexity of the Exchange 2010 setup,
introduction of Database Availability Groups (DAG) and diversity of installation cases, a new