Use the pdstop command to normally terminate the HiRDB system at the main site.

Note

If normal termination fails, do not attempt to switch sites to test disaster preparedness. Refer to the error message that was output when you tried to terminate HiRDB and eliminate the cause of the error. Then try to normally terminate HiRDB again.

Use either of the following methods to check the status of all paired logical volume groups:

• Executing the pairvolchk command
• Executing a shell program that internally executes the pairvolchk command

For an example of a shell program that does this, see Appendix B. Sample Shell Program.

Note

If there is a paired logical volume group whose pair status is not PAIR, take the necessary steps to change the pair status to PAIR. If even one paired logical volume group has a pair status that is not PAIR, do not attempt to switch sites to test disaster preparedness.

Use the horctakeover command to take control over all paired logical volume groups. If the takeover fails, refer to RAID Manager's error log to eliminate the cause of the takeover failure. Then, re-execute the takeover.

If Swap-Takeover was successful for all paired logical volume groups (the return value of the horctakeover command is 1), execute the pairvolchk command on each paired logical volume group to check its pair status. If Swap-Takeover was successful for all paired logical volume groups and the pair status of all paired logical volume groups is PAIR, you can proceed to switch sites to test disaster preparedness.

Change the value specified for the remote site's pd_rise_disaster_mode operand to normal.

Reference note

Because the default value of the pd_rise_disaster_mode operand is normal, you do not need to do anything if the pd_rise_disaster_mode operand was omitted.

Use the pdstart command to start the HiRDB system at the remote site. If the KFPS05210-I message is output and the HiRDB start processing finishes, switching sites to test disaster preparedness is complete.

If HiRDB does not start, refer to the error message that is output during the HiRDB start processing, eliminate the cause of the error, and then restart HiRDB.