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 details about a sample shell programs that will do this, see Appendix B. Sample Shell Program.

Whether you can switch sites in the event of a disaster is determined based on the status of paired logical volume groups and the protection mode. Refer to the table below to see whether you can switch sites in the event of a disaster.

If you cannot switch sites due to a disaster, HiRDB cannot be restarted at the disaster recovery site, and you will need to use the backup data to recover the database. You will also need to re-create all system files.

Table 5-6 Whether you can switch sites in the event of a disaster

Processing method	Protection mode	Status of paired logical volume groups	Whether you can switch sites in the event of a disaster
All synchronous method	data	There is a paired logical volume group whose status is COPY.	N#2
		There are no paired logical volume groups whose status is COPY.	Y
	never	There is a paired logical volume group whose status is COPY.	N#2
		There is a paired logical volume group whose status is PSUE or PSUS.	Y#1
		There are no paired logical volume groups whose status is COPY, PSUE, or PSUS.
All asynchronous method	--	There is a paired logical volume group whose status is COPY.	N
		There are no paired logical volume groups whose status is COPY.	Y
Hybrid method	data	There is a paired logical volume group whose status is COPY.	N#2
		There are no paired logical volume groups whose status is COPY.	Y
	never	There is a paired logical volume group whose status is COPY.	N#2
		There is a paired logical volume group whose status is PSUE or PSUS among the paired logical volume groups in which system files are created.	Y#1
		There are no paired logical volume groups whose status is COPY and there are no paired logical volume groups whose status is PSUE or PSUS among the paired logical volume groups on which system files are created.

Legend:

Y: You can switch sites in the event of a disaster.

N: You cannot switch sites in the event of a disaster.

--: Not applicable

#1

It may not be possible to start HiRDB after switching sites. For details, see 5.1.5 Results of switching sites in the event of a disaster.

#2

You can switch sites and run at a reduced capacity by skipping the paired logical volume group that satisfies this condition by specifying it in the pd_start_skip_unit operand.

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, SVOL-Takeover, or SVOL-SSUS-Takeover was successful for all paired logical volume groups (the return value of the horctakeover command is 1, 2, or 5), you can switch sites in the event of a disaster.

Change the value specified for the remote site's pd_rise_disaster_mode operand to alone. If the pd_rise_disaster_mode operand was omitted, you must specify it.

Use the pdstart command to start the HiRDB system at the remote site. When the KFPS05210-I message is output and HiRDB start processing finishes, switching sites because of a disaster is complete.

If HiRDB cannot be started, refer to the error message that was output during HiRDB start processing, eliminate the cause of the error, and then restart HiRDB.