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.
Execute the swstresback command to back up a backup management list.
Backup Data Size of Backup Management List
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/logicalNodeName/data |
Point
When you execute the swstresback 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 the swstresback command executes backup in the state holding the data saved before.
Execute the swstresrst command to restore a backup management list.
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 "8.1.1.3.1 Backing up Database" 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 the swsrpsetvol or swsrpdelvol 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 "8.1.1.3.2 Restoring Database" of the Management Server.
On the Managed Server, execute the swsrprecoverres 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.
This section describes the maintenance of a database used by a Management Server.
"8.7.2.1 Backup of Common Control and AdvancedCopy Manager Repository" to backup the ETERNUS SF Manager database.
Point
Use this save method only when the configuration information is changed due to the addition of a Managed Server, or fetching of new device information. It is recommended to save a database regularly (for example, once a day).
To safeguard against an input-output error in an external file while saved data is being acquired, it is recommended to keep at least two generations of saved data.
Backup Data Size of Database
Calculate the size using the following formula:
60 + (number of devices to be managed x 0.001) megabytes |
"8.7.2.2 Restore of Common Control and AdvancedCopy Manager Repository" to restore the ETERNUS SF Manager database.
Execute the command on the Management Serve.
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/logicalNodeName/swnode.ini
Save it in the /backup directory.
# cp /etc/opt/swstorage/swnode.ini /backup |
Backup Data Size of Registry
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/logicalNodeName/swnode.ini
Restore the following file saved in the /backup directory:
# cp /backup/swnode.ini /etc/opt/swstorage |
