ServerView Resource Orchestrator Cloud Edition V3.1.0 DR Option Instruction

2.1 Prerequisites

This section explains the prerequisites for configuring a Disaster Recovery environment.

Item	Reference
Configurations	Refer to "Supported Configurations".
	Refer to "Configuration of the Primary Site and Backup Sites".
Environments	Refer to "Items that must be Identical on the Primary and Backup Sites".
Settings	Refer to "Items that must be Different on the Primary and Backup Sites".
	Refer to "Customized Settings on the Primary Site".
Licenses	Refer to "Necessary Licenses".
Space Estimation	Refer to "Estimation of Replication Disk Capacity".

Supported Configurations

The following configuration is supported:

Admin servers	An admin server on which Windows manager is installed
Managed servers	Blade servers
Managed L-Server/L-Platform	Physical L-Servers Virtual L-Servers using VMware or Hyper-V Use the following configuration when you use a virtual L-Server. VM host: Install on a Physical L-Server VM data: Deploy data on the SAN storage disks with Fibre Channel connections VM management software: Install on either a Physical L-Server or the admin server Recovery of VM management software needs to be performed using backup and restore of VM management software when it is configured on the admin server.
Managed switch blade settings	A CB (Connection Blade) which is in switch mode or end host mode IBP mode cannot be used.

Note

• L-Platforms including server load balancers (SLB) cannot be used.

• L-Servers on the primary site for which only the configuration definition has been created are not covered by disaster recovery failover.

Configuration of the Primary Site and Backup Sites

Choose either of the following configurations to make Disaster recovery failover from the primary site to the backup site transparent to ROR console users.

• Assign the same IP address to the admin servers of the primary and backup sites to make the FQDN of the admin servers the same.

  In this case, do not connect the admin servers on the primary site and the backup site to the same network.

• Assign different IP addresses to the admin servers of the primary and backup site but make the FQDN of the admin servers the same.

  In this case, when failover is performed, DNS server settings need to be changed so that the FQDN is resolved to the IP address of the admin server on the backup site. Upon switchover this IP address will be switched with the IP address of the admin server on the backup site.

  
  

Items that must be Identical on the Primary and Backup Sites

The following must be the same between the primary and backup sites.

• The version and level of the manager

• The installation folder of the manager

• Managed server configuration

  Some services may not continue after disaster recovery failover if the number of managed servers in the backup site is smaller than that of the primary site. To avoid that situation, it is recommended that the primary site and backup site have the same server configuration so the server and network trees display the same contents.

• Resource names registered in server and network trees (except chassis names)

  Different server names can be used by preparing a mapping file in advance.

• Network device configurations (network device models, connections, firmware, account settings)

  The configuration must be the same when performing auto-configuration of network devices.

• External networks (VLAN, CB uplink port settings) and SAN switch settings (zoning).

  The setting must be the same when performing manual network settings in advance.

• The tuning parameters in the following file

  • Settings under installation_folder\SVROR\Manager\etc\customize_data except the below files

    • storage_portset.rcxprop

    • storage_vmhost.rcxprop

  • Installation_folder\SVROR\Manager\rails\config\rcx\vm_guest_params.rb

    For details on configuring tuning parameters, refer to "Message number 69122" in "Messages".

• The user name of the dual-role administrator created during Resource Orchestrator installation

  
  

Items that must be Different on the Primary and Backup Sites

The following must be different between the primary and backup sites.

• The computer name of the admin server

  The computer name must be changed after each disaster recovery failover/failback. Computer names which were used in the past cannot be used again.

• The IP addresses of servers registered in the server tree

  Assign a different IP address when creating a physical L-Server with IP address auto-configuration.

• The IP addresses of storage units which are registered to the admin server

  IP addresses of storage units are required for replication.

• The user names of dual-role administrators and infrastructure administrators

  User names of dual-role administrators (except the one created during ROR installation) and infrastructure administrators.

• Virtual storage resources and disk resources

  Assign a different name excluding the composition in which all the resources that exist in the mirror and the replication relation are made the same name when the storage device is NetApp storage, and the disk resource name and the virtual storage name are used as the alias name and the RAID group name of ESC.

  
  

Customized Settings on the Primary Site

The following customizations, which are performed according to "Chapter 19 To Customize Environment" in the "Setup Guide CE", of the primary site need to be reflected on the backup site before switchover. Configure the backup site while setting up the environment, or reflect the settings as a part of switchover.

• "19.1 Settings for Sending Email"

• "19.2.3 Setting Application process settings"

• "19.2.4 Setting Application process to be used"

• "19.3 Customizing the Dashboard"

• "19.4 Setting the Host Names for Virtual Servers"

• "19.5 Setting the Method for Setting Resource Names"

• "19.6 Settings for the Overcommit Function"

• "19.7 Editing the Environment Setup File for the L-Platform API"

• "19.9 System Disk Settings for Physical L-Servers"

• "19.12 Edit the License Agreement"

• "19.13 Editing the User Agreement when Registering a User"

Back up the following files if they have been modified.

• Installation_folder\RCXCFMG\config\command_config.xml

• Installation_folder\RCXCFMG\config\mail_config.xml

• Installation_folder\RCXCFMG\config\vsys_config.xml

• Installation_folder\RCXCTMG\Charging\conf\accounting.properties

• Installation_folder\RCXCTMG\MyPortal\config\application_process.properties

• Installation_folder\RCXCTMG\MyPortal\config\custom_config.xml

• Installation_folder\RCXCTMG\MyPortal\config\managerview_config.xml

• Installation_folder\RCXCTMG\MyPortal\config\license\create\default

• Installation_folder\RCXCTMG\MyPortal\config\license\reconfigure\default

• Installation_folder\RCXCTMG\MyPortal\config\license\return\default

• Installation_folder\RCXCTMG\SecurityManagement\conf\portal.properties

• Installation_folder\IAPS\F3FMihs\servers\FJapache\htdocs\sopdocs\pub\html\ja\cRegApply_agreement.forUse_ja.html

  
  

Necessary Licenses

DR licenses are required for each physical server for which disaster recovery failover is performed.

Estimation of Replication Disk Capacity

The following resources of admin servers need to be covered by storage replication. Take the disk space consumed by these resources into account when you estimate the disk space for replication. For details, refer to "Chapter 3 Installation" and "Chapter 4 Operation".

• The image file storage folders of physical servers

• The output of the rcxmgrexport command

• The output of the rcxstorage command

• User scripts and definition files