1) Exit all running application programs. If higher security is required, you should make a backup of the system disk in advance. For details on the backup procedure, see "6.3.1 Backing Up."
2) Disconnect disks other than the disk that will be the restore destination from the group to have only one disk connected to the group.
The command line shown below is an example of one used to disconnect disk Root2 from group Group1 to use disk Root1 as the restore destination when Root1 and Root2 are connected to Group1 and mirrored.
# sdxdisk -D -c System -g Group1 -d Root2 |
Confirm that only one disk is connected to group Group1 (Group1 is indicated in the GROUP field of only one disk).
# sdxinfo -D -c System |
Information
If disk Root1 has an INVALID slice, disconnect the Root1.
If a keep disk is disconnected (if the disconnected disk's TYPE field vale is keep in the sdxinfo -D command output), change the type attribute to undef to keep its connectibility to a group (or remove the disk from the class once and register it again as an undef disk). For the disk type attribute setting method, see "Changing the Disk Attributes" of "5.4.1 Class Configuration" or "D.7 sdxattr - Set objects attributes."
Example) Changing the type attribute of Root1 to undef after keep disk Root1 is disconnected from Group1
# sdxattr -D -c System -d Root1 -a type=undef |
See
When using GDS Management View, see "5.4.2 Group Configuration" of "5.4 Changes."
3) Acquire the target-port parameter of the physical disk to be restored.
If the disk to be restored is the disk of Expansion File Unit that is connected to 6 Gbps SAS card or internal disk of SPARC M12/M10, SPARC T4-4/T4-2/T4-1/T3-4/T3-2/T3-1, check the target-port parameter of the physical disk and make note of them.
For other disks, this procedure is not necessary.
# prtconf -v /dev/rdsk/c5t5000039488225F20d0s2 disk, instance #2 Driver properties: ... Hardware properties: ... Paths from multipath bus adapters: ... name='target-port' type=string items=1 value='5000039488225f22' ... |
4) Shutdown the system.
# shutdown -g0 -i0 -y |
5) Since file systems such as root (/), /usr, and /var cannot be unmounted during system operation, boot the system from a CD-ROM device (or network).
For the procedure, see the Solaris manual.
Note
To restore Solaris 10, to which the kernel patch 137111-08 or earlier has been applied, the version of an OS booted from a CD-ROM device (also network or emergency startup disk for restoration) must correspond to the version of the OS, to which the kernel patch 137111-08 or earlier has been applied, you are restoring.
To restore Solaris 10, to which the kernel patch 137137-09 or later has been applied, the version of an OS booted from a CD-ROM device (also network or emergency startup disk for restoration) must correspond to the version of the OS, to which the kernel patch 137137-09 or later has been applied, you are restoring.
To restore Solaris 11, the version of an OS booted from a CD-ROM device (also network or emergency startup disk for restoration) must correspond to the version of the OS you are restoring.
In a system where mirroring is conducted by GDS, booting from a CD-ROM device and performing an illegal operation may disrupt the mirroring environment. Be sure to follow the procedure described here and to avoid operations not provided in this procedure.
When mounting the file system on a physical slice at the time of recovery, mounting as read-only is recommended to write-lock.
6) Check the device names of physical slices that will be the restore destinations for the root (/), /usr, and /var file systems.
# eeprom nvramrc | grep sdx-root-slice
devalias sdx-root-slice-1 /devices/pci@1f,4000/scsi@3/sd@0,0:a,raw# eeprom nvramrc | grep sdx-usr-slice
devalias sdx-usr-slice-1 /devices/pci@1f,4000/scsi@3/sd@0,0:g,raw# eeprom nvramrc | grep sdx-var-slice
devalias sdx-var-slice-1 /devices/pci@1f,4000/scsi@3/sd@0,0:b,raw |
In this example, the physical slice device names are:
/ : /devices/pci@1f,4000/scsi@3/sd@0,0:a,raw
/usr : /devices/pci@1f,4000/scsi@3/sd@0,0:g,raw
/var : /devices/pci@1f,4000/scsi@3/sd@0,0:b,raw
Information
If /usr and /var file systems do not exist, the physical slice names are not displayed as shown below.
# eeprom nvramrc | grep sdx-usr-slice # eeprom nvramrc | grep sdx-var-slice |
For MPLB disks, check the physical slice names of paths after the first one as follows. In an environment booted from the network, if paths after the first one are defined, it is also possible to create backups from the physical slices of the paths.
# eeprom nvramrc | grep sdx-root-slice (First path)
devalias sdx-root-slice-1 /devices/pci@1f,4000/fibre-channel@4/sd@10,0:a,raw
...# eeprom nvramrc | grep sdx-root-alt-slice (Second path)
devalias sdx-root-alt-slice-1b /devices/pci@1f,4000/fibre-channel@5/sd@10,0:a,raw
... |
7) Identify the name of the physical slice to be restored.
The procedure on obtaining the name of the physical slice to be restored differs between the disk of Expansion File Unit that is connected to 6 Gbps SAS card or internal disk of SPARC M12/M10, SPARC T4-4/T4-2/T4-1/T3-4/T3-2/T3-1 and other cases.
[Disk of Expansion File Unit that is connected to 6 Gbps SAS card or internal disk of SPARC M12/M10, SPARC T4-4/T4-2/T4-1/T3-4/T3-2/T3-1]
Identify the name of the physical disk whose device name includes the target-port acquired in step 3).
# format </dev/null | grep -i t5000039488225f22d |
For the argument of the grep command, specify "t" + <target-port> + "d."
In this example, the physical disk name to be restored is c0t5000039488225F22d0.
Check the physical slice name from the physical disk name.
# ls -l /dev/rdsk/c0t5000039488225F22d0* | grep ":a,raw" |
For the argument of the grep command, specify the part after ":" of the device name confirmed in step 6).
In this example, the main physical slice name of the root (/) is c0t5000039488225F22d0s0.
[Other than the above]
Check the physical slice name from the device name of physical slice confirmed in step 6).
# ls -l /dev/rdsk | grep /devices/pci@1f,4000/scsi@3/sd@0,0:a,raw # ls -l /dev/rdsk | grep /devices/pci@1f,4000/scsi@3/sd@0,0:g,raw # ls -l /dev/rdsk | grep /devices/pci@1f,4000/scsi@3/sd@0,0:b,raw |
For the grep command arguments, specify the device names confirmed in step 6).
In this example, the physical slice names of root (/), /usr, and /var are c0t0d0s0, c0t0d0s6, and c0t0d0s1 respectively.
8) Restore the backup data on a tape medium back to the root (/), /usr, and /var file systems.
The following example shows the procedure for restoring data backed up with the ufsdump(1M) command.
# newfs /dev/rdsk/c0t0d0s0 |
Note
Data should not be restored from backup data created before the system disk was mirrored.
See
For details on the ufsrestore(1M) command, see the Solaris manual. After understanding the usage and the meaning of options, specify options properly.
9) Install the boot block to the root partition of system disk.
# installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk /dev/rdsk/c0t0d0s0 |
10) When using the shared class or local class, and the GDS configuration parameter SDX_DB_FAIL_NUM=0 was not set in "6.3.1 Backing Up", set the GDS configuration parameter.
Add the setting of SDX_DB_FAIL_NUM=0 to the end of /etc/opt/FJSVsdx/sdx.cf configuration file.
(Example) When the mount device of root file system is c0t0d0s0
# mount -F ufs /dev/dsk/c0t0d0s0 /mnt # vi /mnt/etc/opt/FJSVsdx/sdx.cf ... SDX_DB_FAIL_NUM=0 <- Added # umount /mnt |
11) Reboot the system.
# reboot |
Note
If the system is booted from an emergency startup disk for restoration, reboot the system using the shutdown(1M) command.
12) Check if there are no errors in the configuration and state of the shared and local classes.
# sdxinfo |
13) When using the shared class or local class, undo the GDS configuration parameter.
Comment out the line of SDX_DB_FAIL_NUM=0 in the /etc/opt/FJSVsdx/sdx.cf configuration file.
# vi /etc/opt/FJSVsdx/sdx.cf ... # SDX_DB_FAIL_NUM=0 |
14) Reconnect the disks that were disconnected in step 2).
# sdxdisk -C -c System -g Group1 -d Root2 |
Confirm that disk Root2 is connected to group Group1 (Group1 is indicated in the GROUP field of the Root2 line).
# sdxinfo -D -c System |
Synchronization copying will automatically take place, and when it is completed, the mirroring status is restored.
See
When using GDS Management View, see "5.4.2 Group Configuration" of "5.4 Changes."
Information
If a keep disk is disconnected from the group in step 2) and if the type attribute is not changed to undef, step 14) will result in an error and the error message "keep disk cannot be connected to existing group" will be output. In this event, change the disk's type attribute to undef first and retry step 14).
For the disk type attribute setting method, see "Information" in step 2).
