This subsection describes the procedures for restoring the object configuration within class Class1 according to the configuration file and configuration information saved in advance as shown in "6.9.1 Backing Up" in the event of loss of the Class1 object configuration caused by a problem of some kind.
1) Stopping and restriction of the automatic startup of RMS
When restoring the object configuration of the shared class registered in the cluster application, stop RMS and then restrict the automatic startup of RMS.
For details about stopping and restriction of the automatic startup of RMS, see "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide."
2) Checking the class scope
With a cluster system, check names of nodes sharing the class. For node names that belong to the class scope, check the SCOPE field of class information output by the sdxinfo command and saved as shown in step 1) of "6.9.1 Backing Up."
3) Placing the configuration file
On a node where the object configuration of the class is restored (with a cluster system, on a node that belongs to the class scope), place the configuration file created in step 2) of "6.9.1 Backing Up" In this example, the path to a destination file is "/var/tmp/Class1.conf".
4) Restoring the object configuration of the class
Execute the following command on the node where the configuration file was placed in step 3) to restore the object configuration of class Class1 according to descriptions in the configuration file "/var/tmp/Class1.conf". Class1 is restored as a local class of that node.
After restoring the object configuration, reboot the node.
# sdxconfig Restore -c Class1 -i /var/tmp/Class1.conf # shutdown -y -i6 -g0 |
Information
If the Physical Disk Configurations Are Different
If the physical disk configuration of the system for restoration is different from that of the backed up system, use the sdxconfig Convert command and change physical disk names in the configuration file.
(Example 1)
Change a physical disk described in the configuration file "/var/tmp/Class1.conf" from c3t4d5 to c2t3d4.
# sdxconfig Convert -e replace -c Class1 -p c3t4d5=c2t3d4 -i /var/tmp/Class1.conf -o \ |
(Example 2)
Change the physical disk of Disk1 described in the configuration file "/var/tmp/Class1.conf" to c2t3d4.
# sdxconfig Convert -e replace -c Class1 -d Disk1=c2t3d4 -i /var/tmp/Class1.conf -o \ |
5) Changing the class type and expanding the class scope
If the backed up class, Class1, is a shared class, change the type and scope attributes of Class1. In this example, the scope of the backed up class is node1:node2.
5-1) Stop the volume in the class.
# sdxvolume -F -c Class1 |
5-2) Change the class type and expand the class scope.
# sdxattr -C -c Class1 -a type=shared,scope=node1:node2 |
6) Settings for using shared classes in a cluster application
When the object configuration of the shared class Class1 registered as a Gds resource in the cluster application is restored, execute the following command on any one node within the class scope of Class1.
# /opt/SMAW/SMAWRrms/bin/hvgdsetup -a Class1 ... Do you want to continue with these processes ? [yes/no] yes |
7) Startup and canceling the restriction of the automatic startup of RMS
If the automatic startup setting of RMS is changed in step 1), restore the settings.
Also, if RMS is stopped in step 1), start RMS.
For the settings on how to startup and automatic startup of RMS, see "PRIMECLUSTER Reliant Monitor Services (RMS) with Wizard Tools Configuration and Administration Guide."
