B.2 rcxrecovery

rcxrecovery -help 
rcxrecovery [-dir directory] [-map mapping_dir] [-mirror storage_file] [-vmmgr vmmgr_file] 
               [-vm_pool pool_file] [-nocleanup] [-allon| -alloff] [-salvage] [-config_file_switchover {on -type {Active-Active| Active-Standby}| off}] 
rcxrecovery [-dir directory] [-map mapping_dir] [-mirror storage_file] [-vmmgr vmmgr_file] 
               [-vm_pool pool_file] [-nocleanup] [-allon| -alloff] -global [-tenant tenant1[,tenant2,,,]] [-salvage] 
               [-config_file_switchover {on -type {Active-Active| Active-Standby}| off}] 
rcxrecovery [-dir directory] [-map mapping_dir] [-mirror storage_file] [-vmmgr vmmgr_file] 
               [-vm_pool pool_file] [-allon| -alloff] -tenant tenant1[,tenant2,,,] [-salvage] 
               [-config_file_switchover {on -type {Active-Active| Active-Standby}| off}]

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

Example

[Windows Manager]

>Installation_folder\SVROR\Manager\bin\rcxrecovery -dir E:\Export\ManagerExport <RETURN>

[Linux Manager]

# /opt/FJSVrcvmr/bin/rcxrecovery -dir /DRImport/Export/ManagerExport <RETURN>

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

[Linux Manager]

/etc/opt/FJSVrcvmr/customize_data/fa_dr.rcxprop

When specifying this option, also specify the following options, if necessary.

• -map
• -mirror
• -vmmgr
• -vm_pool

-map mapping_dir

Specify the folder in which the mapping files that define the relationships of the server names between the switchover source site and the switchover destination site are stored.

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 names of physical servers on the server tree or VM management software registered on the VM management tree of Resource Orchestrator are different between the switchover source site and the switchover destination site, creation of mapping definitions enables defining of the relationship between sites.

This file must be located in the MAP folder under the switchover information storage folder and be a csv file that includes the following content.

• Any file name can be used.
• Comments cannot be set in this definition file.
• Blank lines in this definition file are regarded as meaningless and skipped.
• Enter the physical server mapping definitions in a single file.
• When defining physical server mapping, enter "#PhysicalServer" in a single line in this definition file. Enter the mapping definitions for physical servers after this line.
• Each physical server mapping definition should be stated in a single line, separating two corresponding physical server names using a comma (",").
• Enter mapping definitions for VM management software in a single file.
• When defining VM management software mapping, enter "#VMManagementSoftware" in a single line in this definition file. Enter the mapping definitions for VM management software after this line.
• Each VM management software mapping definition should be stated in a single line, separating two corresponding VM management software names using a comma (",").

Example

#PhysicalServer 
Server1-1,Server2-1 
Server1-2,Server2-2 
#VMManagementSoftware 
VMM1-1,VMM2-1 
VMM1-2,VMM2-2 

Server1-1 and Server1-2 are the server names on the switchover source site.

Server2-1 and Server2-2 are the server names on the switchover destination site.

VMM1-1 and VMM1-2 are the VM management software names on the switchover source site.

VMM2-1 and VMM2-2 are the VM management software names on the switchover destination site.

Information

Mapping definitions of physical servers and VM management software can be described in the MAP folder using either one of the following file configurations.

• Enter descriptions in a single file
• Enter descriptions in (two) different files

When including both the definition of physical server mapping and the definition of VM management software in the same file, do not give the descriptions as follows:

• Describing the physical server mapping definitions after the line including "#VMManagementSoftware", and before the line including "#PhysicalServer"
• Describing the VM management software mapping definitions after the line including "#PhysicalServer", and before the line including "#VMManagementSoftware"

-vm_pool vm_pool

Specify the definition file that defines the VM pool to which the VM host belongs.

When this option is specified, the switchover operation is performed assuming that the VM host has been pre-configured.

Create the file defining VM hosts on which the switchover target virtual L-Server is operating under the switchover information storage folder as follows.

• Specify the file name as vm_pool.csv.
• Lines beginning with sharp signs ("#") are comments in this definition file.
• Blank lines in this definition file are regarded as meaningless and skipped.

Example

#vmpool_name,vmhost_name,vmhost_type 
/VMHostPool,192.168.2.1,VMware 
/VMHostPool,192.168.2.2,OVM-SPARC 
/tenant1/TenantVMHostPool,vmhost1.example.org,VMware 
/tenant1/TenantVMHostPool,vmhost2.example.org,OVM-SPARC 
/tenant2/TenantVMHostPool,192.168.10.15
    

• Specify the VM pool name of the switchover source site for vmpool_name.
• Specify the VM host name (displayed on the server tree of the ROR console in the switchover destination site) of the switchover destination site to be registered in the vmpool_name in the switchover destination site for vmhost_name.

• Specify the VM host type for vmhost_type.

  "VMware" and "OVM-SPARC" can be specified for vmhost_type. If this option is omitted, "VMware" is set.

• When registering multiple VM hosts in a VM pool, enter multiple lines.

If omitted, the vm_pool.csv file 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\custmize_data\fa_dr.rcxprop

[Linux Manager]

/etc/opt/FJSVrcvmr/customize_data/fa_dr.rcxprop

-mirror storage_file

Specify the intermediate files for output mapping using the -recovery option and -mode prepare option of the rcxstorage command on the switchover source 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 switchover destination 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.

Create the information in the switchover information storage folder in order to register VM management software of Resource Orchestrator on the switchover destination site.

• Specify the file name as vmmgr_file.txt.
• Lines beginning with sharp signs ("#") are comments in this definition file.
• Blank lines in this definition file are regarded as meaningless and skipped.

Example

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

Each item to specify is explained below. Use the information registered on the switchover source 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 switchover destination site during switchover when a disaster occurs.

This option is valid during switchover including global environments.

When this option is omitted, the environment of the switchover destination site 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, switchover destination 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.

-alloff

Specify this option to power off all L-Servers after switchover.

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 resources in the global pool.

When this option and the -tenant option are omitted, all resources on the switchover source site will be switched over. When this option is specified, configuration definition information on the switchover destination 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 switchover destination site will not be cleared.

-salvage

Use this option to recover the resources that were degraded by the limitation of switchover scope after failback.

When this option is specified, it is assumed that the -nocleanup option and the -config_file_switchover off option are also specified.

For how to use this option, refer to "4.6 Additional Recovery Operation after Failback".

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 switchover destination 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 switchover destination site that has already been performed.

When the automatic collection of switchover information is enabled, executing rcxrecovery disables the setting.

After the switchover is completed, enable the setting referring to "3.7 Configuring Automatic Collection of Switchover Information".

-config_file_switchover

Use this option to forcibly enable or disable automatic takeover of configuration files.

• When "on" is specified

  Automatic takeover of configuration files is enabled regardless of the value of "#Config File Switchover" in the DR definition file (fa_dr.rcxprop).

  • -type {Active-Active| - It is necessary to specify it with the Active-Standby} option.
  • - When -type Active-Active is specified, the operation is the same as when "DR_operation_method=1" is defined for "#DR Operation Method" in the DR definition file (fa_dr.rcxprop).
  • - When -type Active-Standby is specified, the operation is the same as when "DR_operation_method=2" is defined for "#DR Operation Method" in the DR definition file (fa_dr.rcxprop).

• When "off" is specified

  Automatic takeover of configuration files is disabled regardless of the value of "#Config File Switchover" in the DR definition file (fa_dr.rcxprop).

Permissions

Refer to "5.1.2 Roles and Available Operations" in the "Design Guide CE".

Location

Admin server

0

The command executed successfully.

1

An error has occurred.

>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 
 - Customized role 
 - 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 
 [xx:xx:xx] (1/8)check of input data : completed 
 [xx:xx:xx] (2/8)cleanup of resources : completed 
 [xx:xx:xx] (3/8)copy and configure the definition files : completed 
 [xx:xx:xx] (4/8)import physical resources : completed 
 ------------------------------------------------------------ 
 When this is in the process of physical/virtual L-Server 
 switchover (VM host/VM guest) and the VM management 
 software (vCenter Server/SCVMM) is not installed on 
 physical L-Servers which are in switchover scope, the 
 configuration of VM management software in switchover 
 source site needs to be restored to the VM management 
 software in switchover destination site here. 
 After the restoration of the VM management software 
 configuration is complete, press Y to continue. 
 ------------------------------------------------------------ 
 Press [y] when restoration is complete. : y 
 [xx:xx:xx] (5/8)register/refresh VM management software : completed 
 [xx:xx:xx] (6/8)import virtual resources : completed 
 [xx:xx:xx] (7/8)import middleware information : completed 
 [xx:xx:xx] (8/8)start/stop L-Platform, L-Servers : completed 
 [xx:xx:xx] rcxrecovery finished