This section explains how to restore the admin server.
Note
In a clustered manager configuration, restore backed up contents to the cluster-shared disk.
For details on the folder names used on the shared disk, refer to "B.3 Configuration" in the "ServerView Resource Coordinator VE Installation Guide".
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 for the image files storage folder confirmed during backup.
For details on restoring certificates, refer to "2.1 Manager Installation" and "3.1 Manager Uninstallation" of the "ServerView Resource Coordinator VE Installation Guide".
Restoration 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 given 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 the "Deployment services" have not been installed.
Stop the manager.
For details on how to stop the manager, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
Restore the backup folder that was copied in "2. Backing up system and cloning images" of "B.2 Backing Up System Images" to the folder specified during installation.
Example
Default value after installation
[Windows]
Installation_folder\ScwPro\depot
[Linux]
/var/opt/FJSVscw-deploysv/depot
Restart the manager.
For details on how to restart the manager, refer to "5.1 Manager" of the "ServerView Resource Coordinator VE Setup Guide".
Import the system configuration file
Import the system configuration file that was exported in "3. Export the system configuration file" of "B.2 Backing Up System Images".
For details, refer to "7.2 Importing the System Configuration File" of the "ServerView Resource Coordinator VE Setup Guide".
Restore image settings
Restore the following image settings if they were 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 the "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 import 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.
Restoration 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 failback has been performed after server switchover, restore can be performed.
Managed servers 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 the time of backup.
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 agent's "Deployment service" following the procedure described in "5.2 Agent" of the "ServerView Resource Coordinator VE Setup Guide"
LAN switches and physical link data (used by the Network Map) cannot be backed up.
Register LAN switches and network links following the instructions given in "12.2 Preparations".
The VIOM coordination user name and password cannot be backed up. Register VIOM settings before a restore operation.
For details on the registration method, refer to "6.1.1 Registering VIOM Coordination" in the "ServerView Resource Coordinator VE Setup Guide".
