The following two switchover operations are supported:
Item | Description | Remarks |
|---|---|---|
Switchover Operations | Active-Standby operation | |
Active-Active operation | When the configuration is for performing physical/virtual L-Server switchover (for VM hosts or VM guests), the Active-Active operation cannot be performed. |
Differences between the operations are as follows:
Active-Standby operation
An operation that cleans up the configuration of the switchover destination site in order to take over that of the switchover source before a switchover.
Select this operation when all resources in the switchover destination site are used for a switchover, such as in a disaster.
The configuration of the switchover destination site is cleaned up before a switchover.
Collecting the configuration information of the switchover destination site in advance enables the information to be restored after failback is performed.
Figure 2.5 Active-Standby Operation
Active-Active operation
An operation that maintains the configuration of the switchover destination site while taking over that of the switchover source during a switchover.
Select this operation when some resources in the switchover destination site are used for a switchover while services are continued.
Physical servers and network devices required for importing the target configuration of the switchover source site must be prepared on the switchover destination site in advance.
When using the physical servers and network devices for other purposes until just before a switchover, those to be stopped for the switchover, and tenants, L-Platforms, and L-Servers which operate using those physical servers and network devices must be defined in advance.
It is necessary to delete the tenants, L-Platforms and L-Servers which were operating when switchover was performed. For details of the corrective actions, refer to "4.2.1 Stopping Services and Releasing Resources [Switchover Destination Site]".
It is possible to restore deleted tenants, L-Platforms and L-Servers after performing failback. For details, refer to "When Restoring the Switchover Destination Site after Failback" in "4.5 Operation after Failback".
Estimate the number of resources to be used on the switchover destination site used for switchover based on the following conditions.
It is recommended to prepare the same number of the following resources on the switchover destination site as on the switchover source site.
The VM hosts and physical servers in the VM pool and server pool used by the tenant that is the switchover target
The reason this is recommended is because when all of the following conditions are met, there is a possibility that recovery of virtual L-Servers or physical L-Servers on the switchover destination site may fail due to a lack of resources.
- When the same number of VM hosts and physical servers as the switchover source site are not prepared on the switchover destination site
- When limiting of switchover scope is not performed
Prepare the same number of the following resources on the switchover destination site as are on the switchover source site.
Network devices used by the tenant that is the switchover target
When performing switchover or failback in increments, prepare the network devices necessary for each switchover.
Depending on the planned use of the resources prepared on the switchover destination site, take the following action as necessary.
When the prepared resources will not be used until switchover
No action is necessary.
When the prepared resources will be used for another purpose until switchover
Identify the L-Platforms or L-Servers that use these resources from the CLI or the GUI in advance.
After that, stop the identified L-Platforms or L-Servers during the switchover procedure.
The physical servers and network devices used for the switchover cannot be used for the original services of the switchover destination site until failback of the switched configuration is completed.
Perform failover/failback by tenant. Neither failover nor failback are possible by site. For details on the switchover levels, refer to "2.3 Switchover Levels".
There are some notes on the setting of resource names, etc. For details, refer to "Items to be Different between the Primary and Backup Sites" in "2.6 Configuration of the Primary and Backup Sites".
Editing of definition files may be required. For details, refer to "Configuration Files for Matching Details between the Primary and Backup Sites" in "2.6 Configuration of the Primary and Backup Sites".
There are specified settings for L-Platform templates. For details, refer to "Creation of Information on L-Platform Templates for Active-Active Operation" in "3.3 Manager Installation and Configuration".
There are some notes on operations after switchover. For details, refer to "When Switchover Was Performed Using the Active-Active Operation" in "4.3 Operation after Switchover".
Different prefixes must be set for software IDs of primary and backup sites in advance.
When switchover is performed between sites with the same prefix set, the IDs of software information with the same software ID in the sites may be changed during import.
For prefix settings for software IDs, refer to Appendix A Settings for Software ID Prefixes".
Figure 2.6 Active-Active Operation
