7. The following command places the Backup database into a rollforward pending state and take it out of a suspended state:
db2inidb ts1 as standby
8. Perform a DB2 backup on the Backup server using the supported backup system:
db2 “backup database ts1 to /backupfs”
9.Stop the DB2 instance on the Backup server: db2stop
10.Unmount the /db2/TS1/… file systems on the Backup server: umount /db2/TS1/db2ts1/NODE0000 umount /db2/TS1/sapdata1 umount /db2/TS1/sapdata2 umount /db2/TS1/sapdata3 umount /db2/TS1/sapdata4 umount /db2/TS1/sapdata5 umount /db2/TS1/sapdata6 umount /db2/TS1/sapdata7 umount /db2/TS1/log_dir
11.Withdraw the FlashCopy pairs for the database and log files:
/usr/opt/ibm2105cli/rsExecuteTask.sh
and wait for the FlashCopy task to finish.
Restore the DB2 backup image taken on the Backup serverto any DB2 server, including the Primary server, using the DB2 restore command.
1.Stop the SAP system on the Primary server by logging on as user ts1adm and issuing the following command, which also stops the DB2 instance:
stopsap
2.Restore the DB2 backup to the desired machine:
db2 “restore database ts1 from /backupfs”
3.Make sure that logs from the Primary server are available to the machine where the database restore was performed, thus allowing a rollforward through the logs.
4.After the restore is successful, roll forward through the DB2 logs. The rollforward command allows the option to roll forward to end of logs or to roll forward to a point in time. Ensure all logs that are required from the Primary server are available to the new system:
db2 “rollforward database ts1 to end of logs and stop” or
db2 “rollforward database ts1 to
32 |
