A.5 Backing Up and Restoring Object Configuration (sdxconfig)

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.
By using the sdxconfig command, you can use disks registered with the class and volumes in the class from other systems.
However, backup and restoration for volume data and setup for disk labels may be required depending on a GDS version.
[Conditions for GDS versions]
- GDS version before system migration
  - 4.3A00 or earlier
- GDS version after system migration
  - The patch for PG97489 is applied in 4.3A20 or earlier
  - The patch for PG97489 is applied in 4.3A30 (RHEL5)
  - 4.3A30 (RHEL6)
  - 4.3A40 or later
When the above conditions are met, perform the following procedure. Usually, step 1, 5, and 7 are unnecessary. However, you have to perform these steps only when the above conditions are met.
1. Back up volume data in a class on a system before migration.
2. Back up a class object configuration by using the sdxconfig Backup command on the system before migration.
3. Remove the class object configuration by using the sdxconfig Remove command on the system before migration.
4. Connect disk which was removed from the class in step 3 to the system after migration.
5. Set up a MSDOS type disk label for the removed disk by using the parted(8) command on the system after migration.
  (For 4.3A30 or later, you can skip this step and specify the -e mklabel option in step 6.)
6. Restore the class object configuration by using the sdxconfig Restore command on the system after migration.
7. Restore volume data in the class on the system after migration.