Split-mirror restore scenario
This scenario starts with the SAP R/3 system TS1 running on the Primary server. The Backup server has TS1 stopped and DB2 file system for data and logs unmounted.
1.Edit the userexit program and place it in the appropriate directory on the Primary server so DB2 knows where archived logs are located. The user exit program will archive the logs.
2.Issue the suspend command on the Primary database:
db2 “connect to ts1”
db2 “set write suspend for database”
3.Execute the FlashCopy task ts1dbdata from the Primary server as root user:
/usr/opt/ibm2105cli/rsExecuteTask.sh
ts1dbdatafc
Wait for rsExecuteTask to return.
4.Issue the resume command from the same connection in Step 2:
db2 “set write resume for database”
5.If the Primary database gets corrupted due to a database application error or some other error that prevents the database from being restarted, another FlashCopy task that copies the former target volumes to the former source volumes can then be executed. At this point, DB2 should no longer be running on the Primary server.
6.Unmount the /db2/TS1/… data file systems on the Primary 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
7.Execute the FlashCopy task ts1dbrev from the Primary server as root user:
/usr/opt/ibm2105cli/rsExecuteTask.sh
ts1dbdatarevfc
Wait for rsExecuteTask to return.
8.Mount the /db2/TS1/… data file systems on the Primary server:
mount /db2/TS1/db2ts1/NODE0000 mount /db2/TS1/sapdata1 mount /db2/TS1/sapdata2 mount /db2/TS1/sapdata3 mount /db2/TS1/sapdata4 mount /db2/TS1/sapdata5
| 34 |
