This section explains notes on operation until failback of the switched configuration is performed after switchover.
When Performing Tenant Switchover while the Switchover Source Site is Operating
For global resources shared with the tenants for which switchover is not performed and the resources of L-Server templates, the same resources may exist in both the switchover source and destination sites. When modifying the settings of the corresponding resources, perform the same modifications for the resources of the two sites.
For example, when editing L-Server template A in the switchover destination site, edit L-Server template A in the switchover source site using the GUI or the CLI in the same way.
When the Accounts Manager Invoices Usage Charges
The procedure is as follows.
Invoicing Usage Charges
The accounts manager receives two types of files, the usage charge files for the primary site for the month of the recovery sent from the infrastructure administrator and the usage charge files sent from the backup site. Use these files to calculate the usage charge for the tenants on the month of recovery and issue the invoice. The calculation procedure using the files mentioned above is as follows.
Extract usage charge detail files
Extract usage charge files from both the primary site and backup site, and obtain usage charge detail files for each L-Platform. The name format of the usage charge detail files is as follows.
For further information refer to "15.4.6.2 Usage charge Detail File" in the "Operation Guide CE".
yyyyMM_L-PlatformID.csv
Prevent duplicate charging for products charged monthly
For each L-Server in the usage charge detail file, if the UsageFrequency column for the image, CPU, and memory is set to "1 month", compare the values of the ItemAmount columns in the usage charge detail files from the primary site and the backup site and delete the row with the lower value. For the rows for the disks, delete only the rows with the same size and pool name from the primary site usage charge file. If there are multiple pairs of rows with the same size and pool name, delete only one for each pair. If there are no products being charged monthly, then this operation can be omitted.
Merge usage charge detail files
For each L-Platform, copy the rows after line 2 of the csv data of the backup site and add them to the end of the usage charge detail file from the primary site.
Calculate the usage charges of L-Platforms
Calculate the usage charges of L-Platforms. Total the values of the ItemAmount column of the usage charge detail file.
Calculate the usage charges of tenants
Perform steps b to d for every L-Platform and total the usage charges of L-Platforms to calculate the tenant usage charge.
When Tenant Switchover was Performed
The following limitations apply to L-Platform templates:
Image information referencing a cloning image in a global pool may be unavailable.
Segment information referencing a network resource in a global pool may be unavailable.
Deployment fails if you subscribe to using an L-Platform template containing unavailable image or segment information.
This unavailable template information becomes available when the resources of all the global pools are switched over.
When Switchover Was Performed Using the Active-Active Operation
After switchover, do not mix resources that have been switched from the switchover source site with resources that were already on the switchover destination site. If mixed, resources cannot be found and failback will fail.
Patterns where resources are mixed are as follows:
When linking global pools that were already on the switchover destination site to the tenants switched over using DR
When linking global pools switched over using DR to the tenants that were already on the switchover destination site
When moving resources that were already on the switchover destination site to the global pools switched over using DR
When moving resources switched over using DR to the global pools that were already on the switchover destination site
When creating an L-Platform/L-Server using both the resources switched over using DR and those that were already on the switchover destination site
In order to identify on which site the corresponding resources were created, it is recommended to add their site names to the beginning of the resource names.
For details, refer to "Items to be Different between Sites" of "Items to be Different between the Primary and Backup Sites" in "2.6 Configuration of the Primary and Backup Sites".
When Additional Recovery Is Planned
When additional recovery is planned on the switchover source site after the switchover operation, do not perform the following operations.
Unmounting or deletion from VM hosts and physical servers on disks used by the following resources which are to be restored, on the switchover source site
L-Servers
L-Platforms
Tenants
Image Resources
Reuse of disks used by the following resources which are to be restored, in the switchover source site
L-Servers
L-Platforms
Tenants
Image Resources
Editing and deletion of L-Platform templates used for deployment of L-Platforms outside the switchover, on the switchover destination site
When Switchover Was Performed Using the Blade Chassis Degradation Configuration
When switchover was performed using the blade chassis degradation configuration, perform the following operations after the switchover, as necessary.
Network resources using LAN switch blades to be degraded as external connection ports are created in the switchover destination site without port specification. Configure the external connection ports of network resources as necessary.
For details, refer to "5.4.4 Configuring VLANs on LAN Switch Blades" in the "User's Guide for Infrastructure Administrators (Resource Management) CE".
When virtual L-Server switchover (VM guest) is performed, confirm that the virtual network created on the VM management software is automatically configured. If the virtual network is not configured automatically, refer to the information on virtual networks shown in the VM profiles of the target VM and create a virtual network with the same name as the switchover source site on the VM host.
