All parts excluding the failed portion must be in the same configuration as that used before the removal.
To add the system board that is removed with DR. The GDS disk and the PCI card must be on the same mounted slot locations as those used before the removal.
Similarly, not the GDS disk, but the PCI card must be replaced with PCI Hot Plug. For corrective action against disk failures, see the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide"
The mirrored volumes must be synchronized.
Hot swap with DR/PCI Hot Plug is not allowed in the following conditions:
If there's a volume that is not synchronized in the mirror disk group. The disk that is connected to a system board or PCI card belongs to this mirror disk group, and
If there's an ACTIVE slice on the disk in the 1) volume.
You can presume the following causes if the volumes are not synchronized. Check the slice state before initiating hot swap using the "sdxinfo(1)" command.
If you detach the source disk during synchronization copy.
If there's only one ACTIVE slice during TEMP slice detachment.
When you will sequentially remove the system board (or PCI card) to which each mirrored disk is connected using DR (or PCI Hot Plug).
The disks must be mirrored between the system boards (or PCI cards).
If the mirrored disks are connected to the same system board, you are not allowed to remove the system board using DR.
If the mirrored disks are connected to the same PCI card, you are not allowed to operate hot swap of the PCI card using PCI Hot Plug.
The disk should be non-GDS, and the I/O path to the disk must not be redundant.
If the disk is controlled in a redundant I/O configuration with the Multipath Disk Control, it is necessary to follow the DR/PCI Hot Plug procedure for the Multipath Disk Control. Also, if you are using non-Fujitsu redundant I/O software (for example, EMC PowerPath), check how DR/PCI Hot Plug is supported for each software product, then follow the procedure.
The class attribute (scope) must be set to access the shared class disk on all the nodes.
You can check the class attribute (scope) on the Class Configuration screen of the GDS Management View.
