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).
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.
This section describes the maintenance of a database used by a Management Server.
Execute stgdbdmp (Database save command) to save a database space.
Execute this command on the Management Server.
After saving a database, refer to "7.7 Maintaining a database of ETERNUS SF Manager" and save a database of ETERNUS SF Manager as well.
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.
Database backup data size
Calculate the size using the following formula:
60 + (number of devices to be managed x 0.001) megabytes |
Refer to the following file, and beginning from the last line, search for any message with "rdb: ERROR: qdgXXXXX-" in its contents (also check the messages displayed at the same time). Then, obtain the value of "qdgXXXXX" to determine the recovery mode.
/var/opt/FJSVswstf/log/RDBSWSTF.log
/var/opt/FJSVswstf/<logical-node-name>/log/RDBSWSTF.logNote
If multiple errors occur simultaneously, recovery using recovery modes 1 to 5 may not be possible.
To restore a database to its state when it was last saved, re-create the database and execute "7.1.1.3.1 Saving a database" in recovery mode 0.
Data updated or inserted after the last time the database was saved cannot be recovered.
The swstsrsemtch (Resource match command) with -x option will need to be executed on all Managed Servers on which the backup is performed, after which swsrprecoverres (Resource adjustment command) with -r option will need to be executed on the Managed Servers on which the replication is performed.
Execute the database recovery command for database recovery if an I/O error occurs in a database space.
Execute this command on the Management Server.
For details on this command, refer to "8.3.19 stgdbrcv (Database recovery command)".
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 |