Restore the GDS configuration information in the copy destination cluster system.
Change the physical disk name in GDS configuration files.
If the physical disk names registered in the GDS class are different in the copy source and destination systems, use the "sdxconfig Convert" command to change the physical disk names in the configuration file to the physical disk names in the copy destination system. This setting is performed on the node where the configuration file was backed up.
Example: Changing the physical disk described in the "/var/tmp/Class1.conf" configuration file from "c1t4d0" to "c1t4d2"
# sdxconfig Convert -e replace -c Class1 -p c1t4d0=c1t4d2 -i /var/tmp/Class1.conf -o /var/tmp/Class1.conf -e update
Change of physical disk names in the Excluded List of GDS
In environments using the Excluded List, if the physical disk names entered in the Excluded List are different in the copy source and destination systems, change the physical disk names to those entered in the Excluded List for the copy destination system. Perform this task on all nodes.
For details on the Excluded List, see "PRIMECLUSTER Global Disk Services Configuration and Administration Guide".
Restoring the object configuration information of local and shared classes
Execute the following command on the node where the configuration file was backed up.
If private slice data were copied
# sdxconfig Restore -c Class1 -i /var/tmp/Class1.conf -e chkps
If private slice data were not copied
# sdxconfig Restore -c Class1 -i /var/tmp/Class1.conf
Note
After restoring with the "sdxconfig Restore" command, shared classes become local classes.
If the following message is displayed, take corrective measures with reference to the "PRIMECLUSTER Global Disk Services Configuration and Administration Guide":
ERROR: device: disk label is not matched with class class
Restart OS on all nodes.
Change of the class attribute
If the Class is a shared class, change the restored class from local class to shared class.
Perform the following operation on the nodes on which you restored the class object configuration in Step 3.
Stop the GDS volume.
# sdxvolume -F -c Class1
Change class attribute to shared class.
# sdxattr -C -c Class1 -a type=shared,scope=fuji4:fuji5
Preliminary setup for Gds resources used in RMS
Perform the following operation on any node.
# /opt/SMAW/SMAWRrms/bin/hvgdsetup -a Class1
Associate Master with Proxy.
If PRIMECLUSTER GDS Snapshot is used, associate Master with Proxy.
See
For how to associate them, see "PRIMECLUSTER Global Disk Services Configuration and Administration Guide."
Start the GDS volume.
If the GDS volume stopped in Step 5. includes any GDS shared class volumes which are not registered to RMS (e.g. classes used by GFS), start the volume on all the nodes in the class scope by executing the sdxvolume -N command, since it will not start automatically at the time of starting the RMS.
Example: Starting classes used by GFS (gfs and gfs01)
Execute the following commands on all the nodes in the class scope.
# sdxvolume -N -c gfs
# sdxvolume -N -c gfs01