Note
Disk in DISABLE status
When taking this procedure to restore the system disk, check before taking this procedure or check in the procedure 8-2) that no DISABLE disks exist.
If a disk in DISABLE status exists, follow "(1) Disk is in DISABLE status." in "F.1.2 Disk Status Abnormality" to restore the disk in DISABLE status first, and then take the following procedure.
However, when the condition to forcibly remove a class that is described in "(1) Disk is in DISABLE status." in "F.1.2 Disk Status Abnormality" is satisfied, the disk cannot be restored by the following procedure. In this case, follow "(4) System cannot be booted (Failure in all boot disk devices)."in "F.1.5 System Disk Abnormality"to restore the disk.
8) Switching to the alternative boot environment
If the system cannot be booted due to a failed system disk or damaged data, switch the environment to the alternative boot environment created in the proxy volume to allow the system to continue operating.
8-1) Boot the system through the alternative boot environment.
Execute the boot command in the OpenBoot environment. For the boot command, you can specify one of the boot devices in the alternative boot environment output in the message as shown in step 5-3).
# shutdown -y -g0 -i0 ok boot /pci@1f,4000/scsi@3/disk@2,0:a |
Information
The boot command may fail as below if the number of the boot device names in the alternative boot environment output in step 5-3) exceeds the number of boot devices in the alternative boot environment.
ok boot /pci@1f,4000/scsi@3/disk@2,0:a
Rebooting with command: boot /pci@1f,4000/scsi@3/disk@2,0:a
Boot device: /pci@1f,4000/scsi@3/disk@2,0:a File and args:
Evaluating: boot /pci@1f,4000/scsi@3/disk@2,0:aCan't open boot device ok |
If this happens, you should specify another boot device name in the alternative boot environment output in step 5-3) and try the boot command again.
8-2) Confirm that it was booted normally.
Using the mount(1M) command or the sdxinfo command, make sure that it was booted normally in the alternative boot environment and that GDS objects do not contain errors. Additionally, according to need, you should confirm that file system contents in the alternative boot environment are correct and that applications can normally run.
8-3) Break up the former boot environment according to need.
To break up the former boot environment, break the master and proxy relationships, remove the master volumes, and remove groups and disks from the master groups as follows. You may not perform this procedure when restoring system disks in step 9).
# sdxproxy Break -c System -p Proxy1 # sdxproxy Break -c System -p Proxy2 # sdxvolume -F -c System -v root,usr,home,swap,var,opt # sdxvolume -R -c System -v root # sdxvolume -R -c System -v usr # sdxvolume -R -c System -v home # sdxvolume -R -c System -v swap # sdxvolume -R -c System -v var # sdxvolume -R -c System -v opt # sdxgroup -R -c System -g Group1 |
See
When using GDS Management View, see "5.5.5 Breaking a Proxy," "5.5.1 Removing Volume," "5.5.2 Removing a Group," and "5.4.1 Class Configuration."
9) Restoring system disks
After rebooting the system in the alternative boot environment, restore backup disk data back to the original system disks.
9-1) Cancel the master and proxy relationship.
# sdxproxy Break -c System -p Proxy1 # sdxproxy Break -c System -p Proxy2 |
See
When using GDS Management View, see "5.5.5 Breaking a Proxy."
Information
ETERNUS Disk Storage System SAN Boot Environment
When using the OPC function, do not break the master and proxy relationship. However, the original system disks are not in a mirroring configuration and need replacement, break the relationship.
9-2) Remove the master volumes.
# sdxvolume -F -c System -v root,usr,home,swap,var,opt # sdxvolume -R -c System -v root # sdxvolume -R -c System -v usr # sdxvolume -R -c System -v home # sdxvolume -R -c System -v swap # sdxvolume -R -c System -v var # sdxvolume -R -c System -v opt |
See
When using GDS Management View, see "5.5.1 Removing Volume."
Information
ETERNUS Disk Storage System SAN Boot Environment
When using the OPC function, only stop master volumes (with sdxvolume -F) and do not remove the master volumes (with sdxvolume -R). However, the original system disks are not in a mirroring configuration and need replacement, remove the master volumes.
9-3) If an original system disk crashed, swap the failed disk.
The following is an example of swapping disk Root1 (physical disk c0t0d0).
See
When using GDS Management View, see "5.3.4 Disk Swap."
9-3-1) Exclude the disk to be swapped from the GDS management to make it exchangeable.
# sdxswap -O -c System -d Root1 |
9-3-2) Swap physical disk c0t0d0.
9-3-3) Include the swapped disk into the GDS management.
# sdxswap -I -c System -d Root1 |
9-4) Join a group of the backup disks as the master and a group of the original system disks as the proxy.
# sdxproxy Join -c System -m Proxy1 -p Group1 -a Proot=root:on,Pusr=usr:on,Phome=home:on # sdxproxy Join -c System -m Proxy2 -p Group2 -a Pswap=swap:on,Pvar=var:on,Popt=opt:on |
See
When using GDS Management View, see "5.2.4.1 Join."
Information
ETERNUS Disk Storage System SAN Boot Environment
When the relationship between the master and the proxy was not canceled, by using the following command, it is possible to restore data from the proxy groups (backup disk groups) to the master groups (original system disk groups) with the OPC function. When using GDS Management View, see "Restore" in "5.3.3 Restore." In the Restore Master dialog box, select "No" to "Rejoin" and "Yes" to "Instant Restore."
# sdxproxy Restore -c System -p Proxy1,Proxy2 -e instant |
9-5) Confirm that synchronization copying is complete.
# sdxinfo -S -c System
OBJ CLASS GROUP DISK VOLUME STATUS
------ ------- ------- ------- ------- --------
slice System Group1 Root1 root STOP
slice System Group1 Root2 root STOP
slice System Group1 Root1 usr STOP
slice System Group1 Root2 usr STOP
slice System Group1 Root1 home COPY
slice System Group1 Root2 home COPY
slice System Group2 Var1 swap STOP
slice System Group2 Var2 swap STOP
slice System Group2 Var1 var COPY
slice System Group2 Var2 var COPY
slice System Group2 Var1 opt COPY
slice System Group2 Var2 opt COPY
slice System Proxy1 Proot1 Proot ACTIVE
slice System Proxy1 Proot2 Proot ACTIVE
slice System Proxy1 Proot1 Pusr ACTIVE
slice System Proxy1 Proot2 Pusr ACTIVE
slice System Proxy1 Proot1 Phome ACTIVE
slice System Proxy1 Proot2 Phome ACTIVE
slice System Proxy2 Pvar1 Pswap ACTIVE
slice System Proxy2 Pvar2 Pswap ACTIVE
slice System Proxy2 Pvar1 Pvar ACTIVE
slice System Proxy2 Pvar2 Pvar ACTIVE
slice System Proxy2 Pvar1 Popt ACTIVE
slice System Proxy2 Pvar2 Popt ACTIVE |
If synchronization copying is in process, COPY is displayed in the STATUS field for slices of the copy destination proxy group. If the STATUS of every slice in the proxy group is STOP, the synchronization copying is completed.
Information
On the GDS Management View main screen, slices composing copy destination volumes are indicated as below.
If synchronization copying is in process, the status is "copy" and the icon color is blue.
After synchronization copying is completed, the status is "stop" and the icon color is black.
Note
ETERNUS Disk Storage System SAN Boot Environment
In a situation where the multiplicity of master volumes is two or more, if restore is performed with the OPC function, the master volume slices other than the OPC copy destinations will be invalid. To restore the mirror status of the master volumes, execute the resynchronization copying of the master volumes. If the boot environment is switched to the original boot environment in step 9-6), the master volumes are rebooted and the resynchronization copying is automatically executed.
Information
ETERNUS Disk Storage System SAN Boot Environment
When the OPC function is available, it is possible to perform the subsequent procedures without waiting until synchronization copying is completed.
9-6) Through similar steps as 4) and 5) in "6.4.6 Backing Up" and 8) in this sub-section, part the proxy groups, create an alternative boot environment, and switch to the alternative boot environment.
Information
Canceling system disk mirroring in an alternative boot environment
To cancel system disk mirroring after switching to the alternative boot environment in step 8), perform the following procedure. The following describes the procedure concerning the configuration as below.
10) Breaking up the former boot environment
Break up the former boot environment according to need. Break the master and proxy relationships, remove the master volumes, and remove groups and disks from the master groups as follows.
# sdxproxy Break -c System -p Proxy1 # sdxproxy Break -c System -p Proxy2 # sdxvolume -F -c System -v root,usr,home,swap,var,opt # sdxvolume -R -c System -v root # sdxvolume -R -c System -v usr # sdxvolume -R -c System -v home # sdxvolume -R -c System -v swap # sdxvolume -R -c System -v var # sdxvolume -R -c System -v opt # sdxgroup -R -c System -g Group1 # sdxgroup -R -c System -g Group2 # sdxdisk -R -c System -d Root1 # sdxdisk -R -c System -d Root2 # sdxdisk -R -c System -d Var1 # sdxdisk -R -c System -d Var2 |
See
When using GDS Management View, see "5.5.5 Breaking a Proxy," "5.5.1 Removing Volume," "5.5.2 Removing a Group," and "5.4.1 Class Configuration."
11) Unmirroring system disks in an alternative boot environment
See
When using GDS Management View, see "5.5.4 Unmirroring the System Disk."
11-1) Exit all active application programs.
To ensure safe mirroring cancellation, exit all running application programs. If higher security is required, you should make backups of system disks.
11-2) Remove those disks not used as system disks after canceling the mirroring.
# sdxdisk -D -c System -g Proxy1 -d Proot2 # sdxdisk -D -c System -g Proxy2 -d Pvar2 |
11-3) Confirm that cancellation of the mirroring is complete.
# sdxroot -R -c System -d Proot1,Pvar1 |
11-4) Reboot the system.
# shutdown -y -g0 -i6 |
11-5) Verify that the mirroring was cancelled normally.
Using the mount(1M) command or the sdxinfo command, verify that the system disk mirroring was cancelled properly.
11-6) Cancel the system disk management.
# sdxvolume -F -c System -v Proot,Pusr,Phome,Pswap,Pvar,Popt # sdxvolume -R -c System -v Proot # sdxvolume -R -c System -v Pusr # sdxvolume -R -c System -v Phome # sdxvolume -R -c System -v Pswap # sdxvolume -R -c System -v Pvar # sdxvolume -R -c System -v Popt # sdxgroup -R -c System -g Proxy1 # sdxgroup -R -c System -g Proxy2 # sdxdisk -R -c System -d Proot1 # sdxdisk -R -c System -d Proot2 # sdxdisk -R -c System -d Pvar1 # sdxdisk -R -c System -d Pvar2 |
