This section provides information on the maintenance of a backup management list. A backup management list is maintained on the server that performs the backup.
A backup management list is backed up.
For details of this, refer to swstresback (Resource backup command).
Backup management list backup data size
Check the size of the file that the subdirectory of the following directory contains.
/etc/opt/FJSVswsts/data |
In the cluster environment, check the size of the file that the subdirectory of the following directory contains.
/etc/opt/FJSVswsts/<logical node name>/data |
Point
When you execute swstresback (Resource backup command) by using the same directory used before to save data, the file system in which these directories exist should be at least three times greater than the size returned in query above.
This is because swstresback (Resource backup command) executes backup in the state holding the data saved before.
A backup management list is restored.
For details of this, refer to swstresrst (Resource restore command).
When the transaction volume or backup volume is a volume group, the volume configuration information file "/etc/lvmconf/<volume_group_name>.conf" is required to restore the volume configuration information in the processing after backup and restoration.
In order to prepare for a system crash, ensure that you maintain the above mentioned file on another storage medium at the time of creating the volume group.
Point
Usually, a volume configuration information file "/etc/lvmconf/<volume_group_name>.conf" is automatically created at the time of vgcreate (1M) execution. If vgcfgbackup (1M) is used, a backup of the volume configuration information can be created by assigning arbitrary file names. For details of this, refer to the online manual or the man command.
This section describes the maintenance of a replication management list.
To back up a replication management list, back up the repository of the Management Server. For information about backing up a repository, refer to "Saving a database" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server.
Point
Operational information for replication management is saved in a repository.
It is recommended that a replication management list be backed up when operation information for replication management is changed with swsrpsetvol (Replication volume information setting command), or with swsrpdelvol (Replication volume information deletion command).
Perform the following steps to restore a replication management list:
Restore the repository to the Management Server. For information about restoring a repository, refer to "Recovering a database" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server.
If the Management Server is Windows
Select "RDB dictionary and DSI recovery (LOAD Mode)" as the recovery method.
If the Management Server is Solaris or Linux
Specify 0 for stgdbrcv -m option (recovery mode) as the recovery method.
On the Managed Server, execute swsrprecoverres (Resource adjustment command) with the -r option.
Point
When above 2 steps are performed, operational information for replication management of a repository is copied to a Managed Server, where it is then available for use.
When this information for replication management in the repository does not need to be changed, and only the operation information for replication management on the Managed Server is incorrect (for some reason), perform only step 2.
When the source volume or replica volume is a volume group, the volume configuration information file "/etc/lvmconf/<volume_group_name>.conf" is needed to restore the volume configuration information in the post-processing script.
In order to prepare for a system crash, ensure that you maintain the abovementioned file on another storage medium at the time of creating the volume group.
Point
Usually, a volume configuration information file "/etc/lvmconf/<volume_group_name>.conf" is automatically created at the time of vgcreate (1M) execution. If vgcfgbackup (1M) is used, a backup of volume configuration information can be created with arbitrary file names. For details of this, refer to the online manual or the man command.
For information about maintaining a database used by a Management Server, refer to "Maintaining a database" in the ETERNUS SF AdvancedCopy Manager Operation Guide relevant to the OS of the Management Server:
This section describes the maintenance of a registry. Perform this procedure on a Management Server or a Managed Server.
In a command prompt window, back up the following files using the copy command, etc.
/etc/opt/swstorage/swnode.ini
/etc/opt/swstorage/<Logical-node-name>/swnode.ini
Save it in the /backup directory.
# cp /etc/opt/swstorage/swnode.ini /backup |
Registry backup data size
Check the size of the file to be backed up.
In a command prompt window, use the copy command or another method to restore the following files.
/etc/opt/swstorage/swnode.ini
/etc/opt/swstorage/<Logical-node-name>/swnode.ini
Restore the following file saved in the /backup directory:
# cp /backup/swnode.ini /etc/opt/swstorage |
