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

2.3 Switchover Levels

The following levels of switchover are supported:

Item

Description

Remarks

Switchover levels

Site switchover

This cannot be performed in Active-Active operation.

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

  • When an NS Appliance is used as a network device, prepare a physical L-Server for NS Appliance for each unit for which switchover will be performed.

  • Specify the physical server name to create a physical L-Server for NS Appliance. Specify the same physical server name in each site.

  • 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.7 Configuring Copy Groups".

  • There are specified locations for storing switchover target resources. For details, refer to "Storage Location of Switchover Target Resources for Tenant Switchover" in "3.4 Configuring Managed Resources".

  • Address set resources cannot be shared among tenants. Register the address set resources in the local pool for each tenant.

  • 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".

  • 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.8 Locking Resources". For details on how to lock and unlock resources, refer to "4.2 Switchover 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

  • The following template information used for the switchover target tenants should be created as tenant-specific templates.

    • Software Information

    • Image Information

    • Segment Information

    • L-Platform Templates

    When created as global templates, they may also be used for tenants outside the switchover targets. In this case, the tenants cannot be deleted from the switchover source site after switchover, and information with the same IDs will be copied to the switchover destination site.

  • When creating tenant-specific image information, use tenant-specific software information and cloning images in the local pool of the tenant.

    Cloning images in global pools may not be included in switchover targets. If no suitable resource exists, the template information cannot be used.

  • When creating tenant-specific L-Platform templates, it is recommended to use tenant-specific information on images and segments.

    While the information on images and segments of global templates refers to resources in global pools, the resources may not be included in switchover targets. If no suitable resource exists, the template information cannot be used.

Figure 2.7 Configuring Copy Groups


Figure 2.8 Locking Resources