2.2 Switchover Levels

The following levels of switchover are supported:

Item	Description	Remarks
Switchover levels	Site switchover
Switchover levels	Tenant switchover	When the configuration is for performing physical/virtual L-Server switchover (for VM hosts or VM guests), tenant switchover cannot be performed.

Before performing tenant switchover, check the following advisory notes.

Note

Advisory notes for using network devices are given below.
- For each item for which switchover will be performed, prepare the network devices for both the primary site and the backup site.
- For the network devices prepared for switchover targets, use the same resource name when registering them in the network resource tree of the primary and backup sites.
- Do not use network devices prepared for switchover levels selecting from L-Platforms which belong to another switchover level.
When performing physical/virtual L-Server switchover (VM host/VM guest), prepare VM management software for each level performing switchover at the same time.
Perform design so as not to use the same virtual storage resources for tenants switched over separately.
Configure the control item (copy group) for storage replication for each tenant being switched over simultaneously. Refer to "Figure 2.5 Configuring Copy Groups".
Address set resources cannot be shared among tenants. Register the address set resources in the local pool for each tenant.
To migrate global pool images to the switchover destination site at the same time as tenant switchover, perform tenant switchover after migrating the images to the local pool of the tenants.
When creating the following resources, do not create resources with the same names in different sites.
- Tenant resource folder name
- Global Pool Name
- Global L-Server Name
- Virtual Storage Name
- VM management software (physical/virtual L-Server switchover (VM host/VM guest))
- Network device name
- Network resource name
- Name of the address set resource
When creating network resources, do not use the same VLAN IDs in different sites.

Before tenant switchover, lock the resources used by the target tenants to be switched over in the switchover source site. Locking resources prevents the overlapping use of the resource in multiple sites. Refer to "Figure 2.6 Locking Resources". For details on how to lock and unlock resources, refer to "4.2 Switchover Operations between Sites Using the Disaster Recovery Function".

Resource	Operations Restricted by Locking
Network resources	Deployment using the relevant resources Migration to another pool Release of registered resources Deletion of resources Creation of an L-Server for which only the configuration definition has been created, that uses the relevant resources Registration of physical servers of relevant subnets in the server tree
Address Set Resources	Deployment using the relevant resources Migration to another pool Release of registered resources Deletion of resources Creation of an L-Server, consisting of an L-Server definition for which only the configuration definition has been created, that uses the relevant resources
Disk resources	Deployment using the relevant resources Migration to another pool Unregistration from pools
Virtual storage resources	Deployment using the relevant resources Migration to another pool Unregistration from pools Starting of an L-Server for which only the configuration definition has been created, that uses the relevant resources
Pool resources	Deletion of a storage pool where disk resources have been locked
L-Servers	Configuration changes using locked resources (addition of NICs and attachment of disks) Using virtual machines with locked resources as L-Servers

Create image information of the L-Platform template for each tenant. In addition, use cloning images in the local pools of the tenant.
When tenant switchover is performed, cloning images in global pools may not be included in the resources to be switched over.
The image information becomes unavailable if the cloning image it references has not been switched over.
After that, when the resources of the global pool that contains the cloning image are switched over, the image information becomes available again.
An L-Platform template needs to have separate segment information for each tenant. The segment information becomes unavailable if the network resource it references has not been switched over.
After that, when the resources of the global pool that contains the network resource are switched over, the segment information becomes available again.
Create an L-Platform template for each tenant. For the image information and the segment information comprising an L-Platform template, use the information of the tenant or the information you decided to use for the tenant.
An L-Platform template using the image information or the segment information that has become unavailable because the resource has not been switched over cannot be used for deployment.
After the image and segment information become available again by a switchover of global pool resources, the L-Platform template can be used for deployment.

Figure 2.5 Configuring Copy Groups

Figure 2.6 Locking Resources