Use the following steps to perform an in-place restore from a secondary copy using the DB2 command line:
1. Update the database configuration parameter VENDOROPT that needs to be restored with the option to use the required copy precedence, client name and Data Protection Suite instance.
Example:
2. At the DB2 command prompt, type the following command to restore from a secondary copy:
Example:
Where testdb1 is name of the database.
Where CvClientName= windb2test1 is the name of the client machine as it appears in the CommCell GUI Where CvDb2RestoreCopyPrec=2 is the copy precedence number as it appears in the Storage policy properties Where CvInstanceName=Instance001 is the Data Protection Suite Instance Name
db2 update db cfg for target using VENDOROPT
"'CvSrcClientName=client1,CvSrcDB2InstanceName=db2inst3, CvClientName=client2,CvInstanceName=Instance001'"
db2 restore db source load <source software install path>/Base/libDb2Sbt.so taken at <backup_image_timestamp> ON </database-storage-path-location> into target REDIRECT
db2 "restore db source load <source software install
path>/Base/libDb2Sbt.so taken at <backup_image_timestamp> into target WITHOUT PROMPTING"
db2 restore db source continue
db2 update db cfg for target using LOGARCHOPT1 "'CvSrcDbName=source,CvSrcClientName=client1, CvSrcDB2InstanceName=db2inst3,CvClientName=client2, CvInstanceName=Instance001'"
db2 update db cfg for target using VENDOROPT
"'CvSrcClientName=client1,CvSrcDB2InstanceName=db2inst3, CvClientName=client2,CvInstanceName=Instance001'"
db2 rollforward db target to end of logs and stop
db2 update db cfg for database_name using VENDOROPT
"'CvClientName=clientname,CvDb2RestoreCopyPrec=x,CvInstanceName=Instance00x'"
db2 update db cfg for testdb1 using VENDOROPT
"'CvClientName=windb2test1,CvDb2RestoreCopyPrec=2,CvInstanceName=Instance001'"
db2 restore db database_name load "'<software install path>\Base\DB2Sbt.dll'" taken at <backup_image_timestamp>
db2 restore db testdb1 load "'/opt/Data Protection Suite/Base/libDb2Sbt.so’" taken at 20120417152658
Where 20120417152658 = timestamp of the backup image that is being restored Cross Machine/Cross Database Restore
Use the following steps to perform a cross machine\cross database restore from secondary copy using the DB2 command line:
1. Update the database required for cross machine\cross database restore from secondary copy with the option to use the required copy precedence, client name and Data Protection Suite instance.
Example:
2. At the DB2 command prompt, type the following command to cross machine\cross database restore from secondary copy with copy precedence as 2:
Example for cross machine\cross database restore from secondary copy with copy precedence as 2:
3. Run the following command to continue the restore operation:
4. Re-update the target db2 database using LOGARCHOPT1 configuration parameter.
5. Run the following command to roll forward the DB2 database:
Example:
Where:
source = source db name testdb2 = target db name
CvClientName= windb2test1 is the name of the client computer as it appears in CommCell console. CvDb2RestoreCopyPrec=2 is the copy precedence number as it appears in the storage policy properties CvInstanceName=Instance001 is the Data Protection Suite Instance name
20120417152658= timestamp of the backup image that is being restored.
You can recover the database by re-applying the log files containing transactions that are not part of any database backup image. The roll-forward capability is applied after a database or table space image is restored.
Before re-applying the logs (roll-forward) on the restored database, you must enable the logarchmeth1database configuration parameter to perform the log archiving. Whenever the log files are restored with the roll-forward capability, DB2 searches for the following target restore paths:
z DB2's own directory path for log file restores
z The retrieve Path that was specified during the installation of the DB2 iDataAgent z The archive Path that was specified during the installation of the DB2 iDataAgent z The path identified (if any) in the Overflow Directory field within the Roll-Forward.
If it is unable to find any of these paths, the appropriate error is reported in a file within the DB2 Audit Error Path that was specified during installation of the DB2 iDataAgent. db2 update db cfg for database_name using VENDOROPT
"'CvClientName=clientname,CvDb2RestoreCopyPrec=x,CvInstanceName=Instance00x'"
db2 update db cfg for testdb2 using VENDOROPT
"'CvClientName=windb2test1,CvDb2RestoreCopyPrec=2,CvInstanceName=Instance001'"
db2 restore db sample load <source software install
path>/Base/libDb2Sbt.so taken at <backup_image_timestamp> into target redirect
db2 restore db sample load "'/opt/simpana/Base/libDb2Sbt.so’" taken at 20120417152658 into testdb2 redirect
db2 restore db source CONTINUE
db2 update db cfg for testdb2 using LOGARCHOPT1
"'CvSrcDbName=source,CvClientName=windb2test1,CvInstanceName=Instance001,CvDb2RestoreCopyPrec=2'"
db2 rollforward db target to end of logs and complete.
db2 rollforward db testdb2 to end of logs and complete
After recovering the database, you will not be able to reapply the logs.
Reapplying the Logs to the End of Logs
At the DB2 command prompt, type the following command to reapply the logs: