Top
ServerView Resource Orchestrator Cloud Edition V3.1.0 DR Option Instruction
ServerView

A.2 rcxrecovery

Name

[Windows Manager]
Installation_folder\SVROR\Manager\bin\rcxrecovery - Disaster Recovery switchover


Format

rcxrecovery -help
rcxrecovery [-dir directory] [-map mapping_dir] [-mirror storage_file] [-vmmgr vmmgr_file] [-nocleanup] [-allon]
rcxrecovery [-dir directory] [-map mapping_dir] [-mirror storage_file] [-vmmgr vmmgr_file] [-nocleanup]
            [-allon] -global [-tenant tenant1[,tenant2,,,]]
rcxrecovery [-dir directory] [-map mapping_dir] [-mirror storage_file] [-vmmgr vmmgr_file]
            [-allon] -tenant tenant1[,tenant2,,,]

Description

rcxrecovery is the command to perform switch over using DR (Disaster Recovery).


Subcommands

None.

Options

-help

Specify this option to display the specifications for this command.

-dir directory

Specify the folder to store the information for the target of switchover due to Disaster Recovery. If omitted, the ManagerExport folder under the folder (hereinafter, import definition folder) specified for import=directory will be specified in the following folder.

[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\fa_dr.rcxprop

-map mapping_dir

Specify the folder in which to store the mapping files defining the relationships of the server names between the primary and backup sites.

If the -dir option and this option are omitted, the MAP folder under the import definition folder will be used. If there is no import definition folder, mapping of server names will not be performed.

When using different server names between the primary and backup sites, create a file under the MAP folder with the following content before executing the rcxrecovery command. Physical server names will be replaced when importing the primary configuration on the backup site.

#PhysicalServer
Physical server name on primary site-1, Physical server name on backup site-1
Physical server name on primary site-2, Physical server name on backup site-2
:         :
-mirror storage_file

Specify the intermediate files for output mapping using the -recovery option and -mode prepare option of the rcxstorage command on the primary site.

If the -dir option and this option are omitted, the storage_file under the import definition folders will be assigned. When there is no storage_file under the import definition folder, mapping of storage will not be performed.

-vmmgr vmmgr_file

Specify the VM management software definition file to register VM management software on the backup site.

If the -dir option and this option are omitted, the vmmgr_file.txt under the import definition folder will be assigned. When there is no vmmgr_file.txt under the import definition folder, VM management software cannot be registered.

The definition file formats for VM management software are as follow. The description in the first line is the explanation of detailed definitions, and the description is not included in vmmgr_file.txt.

name     soft name  ip              user name  password  physical-lserver
vcenter, vmware-vc, 192.168.1.24,   admin,     admin,    yes
scvmm,   ms-scvmm,  192.168.100.77, root,      root,     no

Each item to specify is explained below. Use the information registered on the primary site.

name:

The name of VM management software to register in Resource Orchestrator.

soft name:

Specify the type of VM management software. The only specifiable values are vmware-vc (vCenter) and ms-scvmm (SCVMM).

ip:

Specify the IP address of VM management software.

user name:

Specify the user ID used when logging in to VM management software.

password:

Specify the password used when logging in to VM management software.

physical-lserver:

Specify "yes", when creating VM management software on a physical L-Server.
Specify "no", when not creating VM management software on a physical L-Server.
When "no" is specified, as messages to recover VM management software are output during command execution and the process is stopped, perform recovery while operations are stopped.

-nocleanup

Specify this option when not clearing the configuration definition information of a backup site during switchover when a disaster occurs.
This option is valid during switchover including global environments.
When this option is omitted, the backup site environments will be cleared. When clearing environments, whether the environments must be deleted or not is confirmed during the command execution. When "y" is entered for an inquiry, backup site environments are cleared and the switchover operation continues. When "n" is entered, the switchover operation is aborted.

-allon

After switchover, specify this option when powering on all L-Servers.
When this option is omitted, L-Servers will be powered on based on their startup status when the switchover information was obtained.

-global

Specify this option when switching over global resources.
When this option and the -tenant option are omitted, all resources on the primary site will be switched over. When this option is specified, configuration definition information on the backup site will be cleared.

-tenant tenant1

Specify the tenant for switchover.
When this operand is omitted by specifying the global option, the resources included in the tenant cannot be switched over.
When this option is specified and -global option is omitted, configuration definition information on the backup site will not be cleared.

Note

  • When there are many imported L-Platforms or L-Servers, the information for L-Platforms or L-Servers may not be displayed in the [Usage Condition] tab. After a while, confirm the information in the [Usage Condition] tab again.

  • When an error occurs while using this command, an error cause message is displayed. Take corrective action based on the displayed message, then execute the command again. If the previous command was executed with the option that clears the configuration definition information of the backup site and "cleanup of resources" ended with "completed", then specify the -nocleanup option when you execute the command again. This option will skip unnecessary configuration cleanup of the backup site that has already been performed.

Examples

>rcxrecovery <RETURN>
------------------------------------------------------------
The following administrative information that exists on the
manager will be deleted.
 - L-Platform templates
 - L-Platform configuration information
 - Resource information
   - L-Servers
   - L-Server templates
   - Tenants
   - Resource folders
   - Image resources
   - Users
   - User groups
   - Network resources
   - Address resources
   - Resource pools
     * Resources registered in pools will be unregistered.
   - Accounting information
   - Metering logs
Please specify the "-nocleanup"option when you do not want
to delete the administrative information.
Caution: In the following case, reply "n" to this prompt to
quit the command and rerun the command with "-nocleanup"
option.
- rcxrecovery had been executed to failover the whole site
   or global resources, and
- "-nocleanup" had not been specified, and
- rcxrecovery had exited with some error after the 2nd
  process "cleanup of resources" had completed, and
- rcxrecovery has rerun after the error had been recovered.
------------------------------------------------------------
Press [y] to continue rcxrecovery, or [n] to cancel
rcxrecovery. : y
(1/10)check of input data                     : completed
(2/10)cleanup of resources                    : completed
(3/10)copy of definition files                : completed
(4/10)import physical resources (global)      : completed
(5/10)import physical resources (tenant)      : completed
------------------------------------------------------------
When migrating the VM management software (vCenter/SCVMM) on
a primary site using DR, if replication is not used, and VM
management software is prepared on the backup site, after DR
there are cases where VM hosts may not be recognized by the
VM management software on the backup site. Please perform
recovery manually so that the VM management software on the
backup site recognizes the VM hosts. After the recovery is
complete, press Y to continue.

However, when VM management software has been installed on a
physical L-Server of Resource Orchestrator, as the same VM
management software as the primary site will be started on
the backup site, this procedure is unnecessary. In such cases,
press Y.
------------------------------------------------------------
Press [y] when recovery is complete. : y

(6/10) register/refresh VM management software : completed
(7/10)import virtual resources (global)        : completed
(8/10)import virtual resources (tenant)        : completed
(9/10)import middleware information            : completed
(10/10)start l-platform                        : completed
rcxrecovery finished