IBM V7.2 manual Snapshot database scenario

Snapshot database scenario

This scenario starts with SAP R/3 system TS1 running on the Primary server and clients using the Primary database. The Backup server has TS1 and DB2 stopped and DB2 file systems for data and logs unmounted.

1.From the Primary Server issue the suspend command on the Primary database: db2 “connect to ts1”

db2 “set write suspend for database”

2.Execute the FlashCopy task ts1db for flashing the data and log file systems from the Primary server as root user:

/usr/opt/ibm2105cli/rsExecuteTask.sh –v –s ESSCSS ts1db

The –v option indicates verbose mode, the –sparameter specifies the hostname of the Copy Services Server. Wait for rsExecuteTask to return.

3.Issue the resume command from the same connection in step 1: db2 “set write resume for database”

4.From the Backup server, mount the file systems:

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 mount /db2/TS1/log_dir

5.Start the DB2 instance db2ts1 on the Backup server: db2start

6.The following command performs crash recovery on the database and takes it

out of a suspended state :

db2inidb ts1 as snapshot

The database on the Backup server is now in a transactionally consistent state at the time the suspend command was issued against the Primary database.

7. Start the SAP system TS1 by logging on as user ts1adm on the Backup server and issuing the following command:

startsap

8.To reconfigure the transport system for the new host, log on to the SAP system and execute transaction STMS.

If a new snapshot image is desired, stop the SAP system TS1 on the Backup server and unmount the /db2/TS1/… file systems. Then, withdraw the existing FlashCopy pairs by executing the task ts1dbwd (if they had been flashed using the no copy option). Then re-establish the FlashCopy pairs and execute the above steps again.

Snapshot Database Scenario 26