By backing up the resources of Resource Orchestrator listed below, it is possible to restore the admin server even if files needed to boot the OS are deleted, or files of the manager are deleted from the installation folder making it impossible to boot this software, or other mistakes made by system administrators result in damage to the system.
It is recommended that you create a backup once a system using Resource Orchestrator has been configured, and after the registration, modification, or deletion of resources.
The resource files managed by Resource Orchestrator are:
Configuration definition information of Resource Orchestrator (database of the Resource Orchestrator manager)
System images and cloning images (files in the image file storage folder)
Back up Resource Orchestrator resources on the admin server using the following procedure:
Install the configuration definition information backup and restore tool
Back up certificates and session encryption keys
Back up system images and cloning images (*1)
Back up configuration definition information
Back up the OS property definition file
Check image management information (*1)
*1: Necessary when using the RCVE backup and restore, or cloning functions for physical servers.
Restore backed up resources to the admin server using the following procedure:
Reinstall the manager and the backup and restore tools of the configuration definition information, and restore the certificates and session encryption keys
Restore system images and cloning images (*1)
Restore configuration definition information
Restore the OS property definition file
Configure image management information (*1)
*1: Necessary when using the RCVE backup and restore, or cloning functions for physical servers.
Note
Target Resources for the Backup and Restore Tool
The configuration definition information managed by Resource Orchestrator (database of the manager) is the target of backup and restore.
System images, cloning images (files in the image file storage folder), VM management software, and VM guests consisting of VM hosts and L-Servers or virtual disks are not the target of backup and restore tools. Perform backup and restore another way.
Functional Range of the Backup and Restore Tool
The backup and restore tool does not support online backup, which is the backup of managers without stopping them.
After restoration, the status is the same as immediately after the backup operation.
Execution Timing for the Backup and Restore Tool
When performing backup and restoration, take care regarding the following points:
Do not perform back up or restoration of the admin server while server switchover or failback is taking place, or while a system image is being backed up or restored.
After backup, only when the following hardware configuration and configuration changes have not been performed, is it possible to perform restoration. When performing hardware configuration or configuration changes, perform backup again.
Replacement of a chassis, LAN switch, managed server, or power monitoring device hardware
Replacement of the NIC of a managed server
LAN connections between managed servers and LAN switches
Server switchover or takeover (*1)
Creation and deletion of L-Servers with the server type "Physical"
Attachment and detachment of L-Server disks with the server type "Physical"
*1: If failback has been performed after server switchover, restore can be performed.
Information
Recovery can also be performed by first backing up the entire admin server disk, and then restoring it.
In clustered manager configurations, the disk shared between cluster nodes should also be backed up and restored.
After backing up the entire disk of the admin server, when Resource Orchestrator resources have been backed up, and restoration of the entire disk of the admin server is complete, perform the steps 2.-5. in "I.4 Restoring an Admin Server" and restore system images, cloning images, and configuration definition information.
