Standby database scenario
This scenario starts with the SAP R/3 system TS1 running on the Primary server. On the Backup server, TS1 is stopped and the DB2 filesystems for data and logs are unmounted. This scenario assumes that the FlashCopy pairs and tasks are already defined on the ESS Copy Services Server.
Because the standby scenario requires logs from the Primary database to be applied to the Backup database, configure the SAP DB2 userexit program to copy the log files to the Backup server. Ship the archive logs to the Backup server so that the Backup database can apply these logs. To do this:
1.
2.In the configuration file initTS1.db6 in the directory /usr/sap/TS1/SYS/global set the value of the variable DB2DB6_STANDBY_DIR to the
For more details on how to configure the SAP DB2 administration tools, see the SAP manual SAP Database Administration Guide: IBM DB2 Universal Database for UNIX and Windows that is also available at http://service.sap.com/installguides.
1.Issue the suspend command on the Primary database: db2 “connect to ts1”
db2 “set write suspend for database”
2.Flash the data pairs from the Primary server:
/usr/opt/ibm2105cli/rsExecuteTask.sh
Attention: For this scenario, do not copy or make available to the Backup server the /db2/TS1/log_dir file system on the Primary server at this point.
3.Wait for the FlashCopy task to finish.
4.Issue the resume command from the same connection used in step 1: db2 “set write resume for database”
5.Mount the data filesystem on the Backup 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 mount /db2/TS1/sapdata6 mount /db2/TS1/sapdata7
Standby Database Scenario | 28 |
