4.2.12 Switchover Using the Batch Command [Switchover Destination Site]

Perform switchover using a batch command.

For Site Switchover
Execute the batch command on the switchover destination site to switch the site.
>Installation_folder\SVROR\Manager\bin\rcxrecovery <RETURN>

For Tenant Switchover

Execute the batch command on the switchover destination site to switch over tenants.

Note

When performing the switchover of the last tenant which will remain on the switchover source site, specify the -global option in addition to the -tenant option.

When switching over a tenant (tenant1) (The other tenants will remain on the switchover source site after the switchover operation)
>Installation_folder\SVROR\Manager\bin\rcxrecovery -tenant tenant1 <RETURN>
When switching over tenants (tenant, tenant2) (No tenants will remain on the switchover source site after the switchover operation)
>Installation_folder\SVROR\Manager\bin\rcxrecovery -tenant tenant2,tenant3 -global -nocleanup <RETURN>

For details on the rcxrecovery command, refer to "A.2 rcxrecovery".

The rcxrecovery command displays messages which represent the status of the switchover process. In addition, the following operations require manual operations or decisions by an administrator. Respond to inquiries from the system to continue execution of the command.

For virtual L-Server switchover (VM guest), the following messages are displayed.

It is necessary to manually delete the network settings on which cleanup is performed in the network settings "corresponding to network resources" configured on the switchover destination site beforehand. It is necessary to manually create the network (virtual switches, port groups) which has been configured on the switchover source site beforehand.
After the operation is complete, enter "y", and continue the command.

For network resources that have been cleaned up, clear their network configurations manually using VM management software or the network devices. Also, if you have manually configured the network on the primary site, configure the network for the backup site again.

Press [y] when the reconfiguration is complete. : y

When the -nocleanup option is not specified and the backup site is to be cleaned up, an inquiry will be displayed to ask if you really want it to be cleaned up. Press "y" to approve the cleanup and continue the rcxrecovery command. If cleanup of the backup site cannot be performed, press "n" to quit the command.
When VM management software is not configured on the physical L-Server, manual restoration of VM management software is necessary. The rcxrecovery command will show a prompt while waiting for the restoration of VM management software. In that case, continue the command after restoration of VM management software is completed.
If VMware ESXi is installed on the server that is the target of switchover, the VM host must be registered in SVOM. After registration is complete, continue the command execution. The command will be postponed until registration is complete.

Information

The rcxrecovery command performs the following:

Mapping of storage
Storage resource mapping is performed, based on the files defining the relations between the storage on the primary and backup sites.
Division of import resources
Imported resources are divided using the following units:
- Resources in the global pool and resources belonging to individual tenants
- Physical L-Server resources and virtual L-Server resources
Deletion of the backup site environment
Deletes the following environments used for backup site operations.
- L-Platform Templates
- L-Platform Configuration Information
- Resource Information
- Accounting Information
- Metering Logs
- Usage Charge
Import the information
Imports the following information:
- L-Platform Templates
- L-Platform Configuration Information
- Resource Information
- Accounting Information
- Metering Logs
- Usage Charge Files

Note

Configured physical servers and linked L-Servers for which only configuration definition has been created are not covered by disaster recovery switchover.
Execute the rcxadm config command as follows to back up the information which is used to relate the configuration definition to L-Server again later.

[Windows Manager]

>Installation_folder\SVROR\Manager\bin\rcxadm config filter -convert -indir indir -outdir outdir <RETURN>

The following information will be output to outdir, using the file name convert.txt.
After completing the restoration procedure, perform creation of a link with an L-Server and setting the scope again as shown below:

[command]
rcxadm lserver convert -with BX900_1 -name physical_lserver_1
rcxadm lserver convert -with BX900_3 -name physical_lserver_2 -to /tenant_1
rcxadm lserver convert -with BX900_6 -name physical_lserver_3 -label test_label3 -comment test_comment3 -to /folder_1
[user]
user_1, physical_lserver_1
user_1, /tenant_1/physical_lserver_2
user_2, /folder_1/physical_lserver_2
[usergroup]
usergroup_1, physical_lserver_1
usergroup_2, /folder_1/physical_lserver_3

Storage using the ETERNUS dynamic LUN mirroring is switched to the LUN that was prepared on the backup site when the switchover operation is performed after a disaster. Operation may be different if the storage is not released even after deleting an L-Platform.
Perform operation so that the import of the resource configuration information and user definition file (XML file) using the rcxrecovery command is not executed at the same time as modification of the resource configuration information or user definition file (XML file) due to L-Server creation, or export operations using the rcxmgrexport command.
The RC console may not display the correct power status of L-Servers immediately after a disaster recovery switchover. Wait for about three minutes after the switchover to see the correct power status of L-Servers.
As the performance information (the information displayed in the dashboard and in operational status displays) depends on the configuration of the primary site, this is not carried over to the backup site when switched over. The information on the backup site is displayed.
Importing may fail when switchover is performed to the backup site, due to a VM guest switchover failure. In this case, perform the import again using the following procedure, but excluding the managed servers for which import failed. Disaster recovery switchover fails when configuration import fails. In this case, execute the failover command again after taking the corrective action for the cause of the import failure. When you execute the command again, the -nocleanup option needs to be specified if the previous command was executed without the -nocleanup option and configuration cleanup was performed and the "cleanup of resources" process ended in "completed".
The following shows an example of where the VM guest could not be restored during L-Server import.
1. An error occurs during import
  >Installation_folder\SVROR\Manager\bin\rcxrecovery <RETURN> FJSVrcx:ERROR:62569:/tenant1/l-platform1/l-server1:lserver:import was interrupted. Message=:67154: VM Guest not found
2. The status of the relevant resources is displayed to help determine the cause of the error.
  >Installation_folder\SVROR\Manager\bin\rcxadm config show -type lserver -name /tenant1/l-platform1/l-server1 -dir dir1 -format xml<RETURN>
  For -dir, specify the folder that was most recently exported in the folder below.
  rcxrecovery -dir option, or the import folder specified in fa_dr.rcxprop\ManagerExport\RORexport_date
3. Delete the resource where the problem occurred from the export file.
  >Installation_folder\SVROR\Manager\bin\rcxadm config filter -exclude lserver -name /tenant1/l-platform1/l-server1 -indir dir1 -outdir dir2 <RETURN>
4. Use the export file output in 3) to overwrite the file in the folder specified for -dir in 2).
5. Import again.
  >Installation_folder\SVROR\Manager\bin\rcxrecovery -nocleanup<RETURN>