It is recommended that an emergency startup disk for restoration where the system for restoration is installed be excluded from GDS management.
The emergency startup disk for restoration cannot be managed as a local or shared class object.
It is possible to register the emergency startup disk for restoration with the root class and configure mirroring, but the following points should be taken into consideration.
Even in a mirroring environment configured with GDS, the system cannot be booted from the mirror disk of the emergency startup disk for restoration.
Because the system is booted for restoration work only from the mirror source disk, only data on the mirror source disk may be updated during the work and the data equivalence between the mirror source disk and the mirror disk is no longer guaranteed. Therefore, after the restoration work, unconfigure the mirroring before booting from the restored system disk. This operation procedure is different from that for "5.1.9 Unmirroring the System Disk." For details, contact field engineers.
Information
GDS Snapshot can be used to create replicas (snapshots) of system volumes to create an alternative boot environment in which the system is booted from the replication volume.
This alternative boot environment can serve as the system for restoration, instead of an emergency startup disk.
It is easier to create an alternative boot environment than to create an emergency startup disk, and additionally, it is possible to make the alternative boot environment redundant by configuring mirroring.
For details, see "1.5.6 Creating an Alternative Boot Environment."
