This section explains how to back up the admin server.
For the admin server, the following two types of backup operations can be performed.
Backup after environment creation
For details, refer to "9.2.1 Backing Up All Management Information".
Periodical Backup and the Backup of Configuration Definition Information
There are backup methods such as periodical backup operations in short intervals (such as backup performed once every hour) and backup performed repeatedly whenever the configuration definition information is updated.
For details, refer to "9.2.2 Backing Up Configuration Definition Information".
Before starting periodical backup, it is necessary to decide the following items:
Frequency of Backing Up All Management Information
Decide how often you want to back up all of the management information.
Example
After setting up a system
03:00 A.M. on the 1st day of every month
Frequency of Periodical Backup
Specify how often you want to back up the system configuration file.
Example
Once every hour
Backup Destination
Decide the disk on which the backup data will be stored.
It is recommended to specify a different disk from the one that Resource Orchestrator is installed on.
For details on the free disk space necessary for backups, refer to the notes in "9.2.1 Backing Up All Management Information".
Backup Destination
The backup destination for configuration definition information can be defined beforehand. Define the following:
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data
[Linux Manager]
/etc/opt/FJSVrcvmr/customize_data
manager_backup.rcxprop
Set the following parameter in the tuning parameter file:
backup_dir=Backup_destination_folder |
If this tuning parameter file is omitted, the backup data will be saved in the following folder:
[Windows Manager]
Installation_folder\SVROR\Manager\var\backup
[Linux Manager]
/var/opt/FJSVrcvmr/backup
For details, refer to "9.2.2 Backing Up Configuration Definition Information".
Note
Backup files of the admin server should be stored on external storage media to prevent the backup data from being corrupted due to server failure.
From the second and successive backups, there are no problems even if backed up folders and configuration definition information from the last time are deleted. Delete earlier backups when disk space constraints make it necessary to do so.
While the following operations are being performed, do not execute backup:
Creation, modification, and deletion of resources
Server switchover and failback
Backup and restoration of system images
Collection and deployment of cloning images
When a periodical backup operation is performed without stopping the manager, if a conflict between the backup operation and the operations mentioned above occurs, the backup operation will be postponed until the operation is completed.
In a clustered manager configuration, because files are stored on the shared disk, the files and folders to be copied in this procedure are those stored on the shared disk.
For details on the folder names used on the shared disk, refer to "Appendix C Manager Cluster Operation Settings and Deletion" in the "Setup Guide VE".
