Filter
Top Products
files).
During restore, because the target VM host will be automatically set to VM maintenance mode, the VM host should be in a state that
allows VM maintenance mode to be set.
If the target VM host is in a high-availability configuration, all VM guests stored on shared disks should be migrated to another VM
host beforehand.
After restoring the VM host, migrate the VM guests back to their original VM host.
Refer to the server virtualization software manual and "D.3 Functional Differences between Products" in the "Design Guide VE" for
information on how to restore and migrate VM guests, or about the VM maintenance mode.
- Deleting a managed server will delete its backed up system images at the same time.
- It is not possible to backup, restore, or delete a system image from a managed server for which a system image (including different
versions) is already being backed up, restored, or deleted.
- When restoring a system image on a server whose name was changed after the deployment of a cloning image, check that the
"
server_name
" displayed on the server resource tree and the System Image List match the new server name before restoring the system
image.
- For managed servers on which the Watchdog function is enabled, backup or restore operations on that server may be aborted by an
automatic restart or shutdown. The Watchdog is a function which automatically restarts or shuts down non-responsive servers when
their operating system does not respond for a given period.
Therefore, it is highly recommended to disable the Watchdog function before a backup or restore operation.
For details on the Watchdog function, refer to the server manual.
- If the disk size of the source (backed up) server differs from that of the destination (restored) server, restore is possible only in cases
where the disk size of the destination server is larger than that of the source server.
In that case, unused disk space will remain on the destination server. To use this unused disk space, a partition should first be created
from it.
Restoring a system image to a server on which the disk size is smaller than that of the source (backed up) server is not possible. This
also applies to server switchover and failback operations that are based on backup and restore, as well as cloning operations.
Therefore, it is also necessary to ensure that spare servers of cloning destination servers have a large enough disk.
- When backing up or restoring system images, or collecting and deploying cloning images, up to four processes can be executed
simultaneously. If four processes are already being executed, any additional image operations will enter a standby state.
Moreover, server switchover which is executed using the backup and restore method or any restore process performed during failback
will also enter a standby state. When Auto-Recovery or manual switchover using the backup and restore method is used, please limit
the number of image operations (backup or restore of system images, or collection and deployment of cloning images) performed at
the same time to 3.
- When using backup and restore for PRIMEQUEST servers, check that the boot option settings and BIOS settings of the target servers
match. When the settings are different, execute the function after changing the settings so they match. For details on how to change
boot options, refer to "9.1.10 Changing Boot Options".
When using PRIMEQUEST1000x2, disable the x2APIC mode of the UEFI.
16.2 Backup
This section explains how to collect a system image backup.
System images can only be backed up from managed servers that are not in "stop" status.
System images can also be backed up using commands.
Refer to "Chapter 4 Image Operations" in the "Reference Guide (Command) VE" for details.
Preparations
Execute the command below before performing backup if the managed server has the following configuration.
- In a SAN data environment using a built-in disk boot, and a physical WWN or VIOM
[Windows Manager]
- 116 -