This section explains how to restore the Admin Server.
Note
In a clustered Manager configuration, restore backed up contents to the cluster-shared disk. Refer to "B.3 Configuration" in the "ServerView Resource Coordinator VE Installation Guide" for details on where files and folders should be restored to.
Reinstall the Manager and restore authentication resources
If the Manager does not run correctly because of damaged files, uninstall and re-install the Manager before restoring agent certificates and the session encryption key.
When re-installing the Manager, use the path confirmed during backup for the image files folder.
Refer to "2.1 Manager Installation" and "3.1 Manager Uninstallation" of the "ServerView Resource Coordinator VE Installation Guide" for details on restoring certificates.
Restore of the session encryption key is only required if passwords were saved using the -save option of the rcxlogin command. This step is not required if no password was saved, or if passwords are to be saved again after re-installation. For details on the rcxlogin command, refer to "2.1 rcxlogin" of the "ServerView Resource Coordinator VE Command Reference".
To restore the session encryption key, restore the following file from the backup folder to the following destination.
[Windows]
Installation folder \Manager\Rails\config\rcx_secret.key
[Linux]
/opt/FJSVrcvmr/rails/config/rcx_secret.key
Because saved passwords are stored in the home directory of the OS user account for which the password was saved, authentication may fail if the home directory contents were damaged. In that case, either restore the home directory contents or save the password again using the rcxlogin command.
Restore the system and cloning images
Use the following procedure to restore system and cloning images.
This step is not required if deployment services have not been installed.
Stop the Manager.
Refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide" for details on how to stop the Manager.
Restore the backup folder that was copied in "2. Backing up system and cloning images" of "B.2 Backup" to the folder that was specified at installation time.
Example
Default value after installation:
[Windows]
Installation_folder\ScwPro\depot
[Linux]
/var/opt/FJSVscw-deploysv/depot
Restart the Manager.
Refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide" for details on how to restart the Manager.
Import the system configuration file
Import the system configuration file that was exported in "3. Export the system configuration file" of "B.2 Backup".
Refer to "7.2 Importing the System Configuration File" of the "ServerView Resource Coordinator VE Setup Guide" for details.
Restore image settings
Restore the following image settings if those had been modified at the time of backup.
Maximum number of system image versions
Maximum number of cloning image versions
For details on the maximum number of system image versions, refer to "6.3.1.3 Changing the Maximum Number of System Image Versions" in the "ServerView Resource Coordinator VE Setup Guide".
For details on the maximum number of cloning image versions, refer to "6.3.1.4 Changing the Maximum Number of Cloning Image Versions" in the "ServerView Resource Coordinator VE Setup Guide".
This step is not required if deployment services have not been installed.
Note
When the system configuration file is exported, in all sections, "operation" will become a hyphen ("-"). Therefore, do not import the system configuration file until after correcting "operation" to "new". For details on the system configuration file, refer to "Appendix D Format of CSV System Configuration Files" of the "ServerView Resource Coordinator VE Setup Guide".
If you are importing the system configuration file when the OS of the managed server is not started, registration of the Agent will fail. Therefore, start the OS before performing import.
If you are setting a VM host as a spare server, leave "operation" as a hyphen ("-") in the "SpareServer" section of the corresponding physical server. After import is completed, set the spare server of the corresponding physical server from the RC console.
Do not perform restore during server switchover, failback, while a system image is being backed up or restored, or while a cloning image is being collected or deployed.
Restore only certificates, system images, cloning images and system configuration files that were backed up at the same time.
Restore can only be executed if none of the settings or hardware configuration changes described below have been made since backing up the Admin Server:
Replacement of a chassis, LAN switch blade, managed server or power monitoring device hardware
Replacement of a managed server NIC
LAN connections between managed servers and LAN switch blades
server switchover or takeover (*1)
*1: If in switchback status after server switchover, restore can be performed.
A managed server using HBA address rename must be restarted after being restored.
Maintenance mode settings cannot be recovered after restore. Set the maintenance mode in accordance with the information recorded at backup time.
If the managed server's Agent was registered, perform either one of the following after restoring the Admin Server to enable subsequent system image backup or cloning image collection operations.
Restart the managed server.
Restart the service described in "Deployment service" in "5.2 Agent" of the "ServerView Resource Coordinator VE Setup Guide".
LAN switches and physical link data (used by the Network Map) are not subject to backup.
LAN switches and physical link data should be manually restored following the instructions given in "12.2 Preparations".
