Do not use editors such as vim(1) and sed(1) to edit configuration tables created with the sdxconfig Backup command or those saved in configuration files. To edit configuration tables, use the sdxconfig Convert command.
When the object of the class is removed using the sdxconfig Remove -e keepid command then it is restored using the sdxconfig Restore -e chkps command, restore the same configuration as the removed configuration.
When the object configuration of the shared class registered as a Gds resource in the cluster application is restored using sdxconfig Restore command, execute the following command on any one node within the class scope.
# /opt/SMAW/SMAWRrms/bin/hvgdsetup -a class_name ... Do you want to continue with these processes ? [yes/no] y
This command is set up in order to start up or stop the volume of shared class along with the change in the state of the cluster application.
For Backup (sdxconfig Backup) and Restore (sdxconfig Restore) of the object configurations, the settings for I/O Response Time Assurance Function are not backed up or restored. If you are using the I/O Response Time Assurance Function, see "7.15 I/O Response Time Assurance [IOmonitor]" for the resolution.
If you use the I/O Response Time Assurance Function and use the sdxconfig Remove command to delete a class that has been enabled to system panic mode, disable system panic mode before you execute the sdxconfig Remove command again. For details on how to change the system panic mode, see "8.3.2 Changing the System Panic Mode."
By using the sdxconfig command, you can use disks registered with the class and volumes in the class from other systems.
However, when using disks that were registered in the class on a system using GDS 4.3A00 or earlier with a system that uses this version of GDS, backup and restoration for volume data and setup for disk labels may be required.
Below are the procedures. Usually, step 1, 5, and 7 are unnecessary. However, you have to perform these steps only when the above conditions are met.
Back up volume data in a class on a system before migration.
Back up a class object configuration by using the sdxconfig Backup command on the system before migration.
Remove the class object configuration by using the sdxconfig Remove command on the system before migration.
Connect disk which was removed from the class in step 3 to the system after migration.
Set up a MSDOS type disk label for the removed disk by using the parted(8) command on the system after migration.
You can also skip this step and specify the -e mklabel option in step 6.
Restore the class object configuration by using the sdxconfig Restore command on the system after migration.
Restore volume data in the class on the system after migration.
When using multipath, register the native device to each node's Excluded Device List. For the Exclude Device List, see "6.1 Creating Excluded Device List"
