Top
ServerView Resource Orchestrator Cloud Edition V3.4.0 DR Option Instruction
FUJITSU Software

2.9 Advisory Notes for Disaster Recovery Environments

Manager OSs

Windows and Linux managers are supported.

Specify the same OS for the managers used for the switchover source site and the switchover destination site.

For details on Windows managers and Linux managers, refer to "Chapter 2 Overview" in the "Design Guide CE".

Managed Servers

Managed servers of physical OSs (Windows, Linux), VMware, Hyper-V, and OVM for SPARC are supported.

Managed servers for physical OSs (Solaris), Solaris Zones, OVM for x86, KVM, Xen, Citrix Xen, and are not supported.

L-Servers which Cannot Be Recovered

The following L-Servers cannot be recovered by Disaster Recovery.

  • L-Servers for which only the configuration definitions have been created
  • L-Servers linked with configured physical servers

Advisory Notes for Configurations Including OVM for SPARC

Note the following advisory notes:

  • Configuration is only supported when automatic saving of VM guest configuration information is enabled.

For details on automatic saving of VM guest configuration information, refer to "Definition File of Whether to Save the Configuration Information" in "8.8.1 Creating Definition Files" in the "Setup Guide CE".

  • Switchover of cloning images (system packages) is not possible.

After completion of switchover, create the cloning images on the switchover destination site, using the same name as the ones on the switchover source site, and then register them in the image pool migrated from the switchover source site.

  • Switchover of the installation server is not possible.

Set up the installation server in advance on both the switchover source and destination sites. If the installation server has been configured as an L-Server, limit the switchover scope so that the L-Server is out of switchover scope.

  • After switchover, configuration of the network settings may be necessary.

The MAC addresses of NICs before and after switchover may be different values. In that case, the recognition order of NICs in the guest OS may be affected.

Check if the same communications with the IP addresses from before switchover can also be performed after switchover. When communications cannot be performed, modify the settings of NICs on the guest OS and NICs on the VM management software.

  • After switchover, it is necessary to import the ZFS storage pool to the data disk.

When the data disk is connected to the switchover target, and ZFS is used on the guest OS, ZFS storage pools other than the root will be exported after switchover.

After starting the guest OS, if necessary, import the ZFS storage pool. When there are services affected by the state in which the ZFS storage pool is temporarily exported, restart the services.

For details on how to import the ZFS storage pool, refer to the manuals of Solaris OS.

Server Load Balancers (SLB)

L-Platform switchover including server load balancers (SLB) is not supported. When creating, editing, or copying an L-Platform template, do not place SLBs in the L-Platform template. Instruct the tenant administrator not to create or release L-Platform templates including SLBs by accident.

VM Guests with VMware Fault Tolerance Enabled

VM guest switchover with VMware Fault Tolerance enabled is not supported. Do not use VMware Fault Tolerance.

VDI Coordination

Switchover of virtual L-Servers that use the VDI coordination function is not supported. Do not use VDI coordination when creating virtual L-Servers.

Global IP Addresses

Switchover of global IP addresses is not supported. Do not register global IP addresses in address pools.

Regarding The Automatic Quarantining Function

Environments in which the automatic quarantining function is used are excluded from the targets of recovery using Disaster Recovery.