This chapter explains how to configure a Disaster Recovery environment.
Configure a Disaster Recovery environment using the following flow.
Pre-setup preparations
Perform pre-setup preparations for the primary and backup sites.
For details, refer to the "Design Guide CE".
Replication of Storage Units
Copy the primary site information to the backup site using the storage unit replication function.
For storage replication, use the functions explained in "17.1.3 High Availability for Storage Chassis" in the "Operation Guide CE".
Disaster Recovery can be operated on LUNs created beforehand or on dynamic LUN mirroring storage of ETERNUS. For details on prerequisites for storage replication, refer to "7.2 Storage Chassis High Availability Design" in the "Design Guide CE".
For primary sites, it is not necessary for the disk resources for the backup site to have been detected. Therefore, it is not necessary to connect storage units for the backup site to the server for the primary site.
Configure the image file storage folder on the storage that is the target of the replication. Copy the image files stored in the image file storage folder in the same way.
When Creating Physical L-Servers
Refer to "Appendix D Preparations for Creating a Physical L-Server" in the "Design Guide CE".
When Using Server Virtualization Products to Create L-Servers
Refer to "Appendix E Preparations for Creating a Virtual L-Server" in the "Design Guide CE". Installation of VM management software on the backup site is not necessary when it is installed on physical L-Servers on the primary site.
When Using VMware Virtual L-Servers
Enter the following commands for the VM host and disable detection of the copied LUNs.
>esxcfg-advcfg -s 0 /LVM/DisallowSnapshotLUN <RETURN> |
Note
LUNs which were created by ETERNUS dynamic LUN mirroring are handled as LUNs created beforehand after a disaster recovery failover from the primary site to the backup site. Replication settings must be performed manually before future failover operations because automatic replication setting is not available for LUNs created beforehand. For details about LUNs created by dynamic LUN mirroring and LUNs created beforehand, refer to "D.3 Storage Preparations" in the "Design Guide CE".
Configure the Disaster Recovery function
Perform the following configuration to collect information for disaster recovery failover and simplify failover operations.
Create folders to contain failover information
Create the following folders and files which are used to contain failover information.
The folder which contains failover information The folder which contains failover information\Image - Folder to contain physical server image files The folder which contains failover information\ManagerExport - Output directory of the rcxmgrexport command The folder which contains failover information\MAP - Folder to contain the mapping file of physical server names The folder which contains failover information\OtherBackupFiles - Folder to contain definition files and user scripts The folder which contains failover information\vmmgr_file.txt - File to define VM management software |
Information
For the contents of vmmgr_file.txt, Refer to "6. Create the file used in disaster recovery".
Example
D:\ D:\Export\Image D:\Export\ManagerExport D:\Export\MAP D:\Export\OtherBackupFiles D:\Export\vmmgr_file.txt |
Create the following folders under the failover information folder.
The failover information folder and the folders under it need to be replicated to the backup site because they are used in recovery operations.
The following folders must be created. Any folder name can be used.
Image
This folder is used to transfer physical image files. Any folder name can be used.
ManagerExport
This folder is mandatory. The folder name must not be changed.
MAP
This folder is used to map physical server names. The folder name must not be changed.
OtherBackupFiles
This folder is used to contain files other than the above. Any folder name can be used.
Install and configure the manager
Install Resource Orchestrator manager on the primary and backup sites.
When the environment is configured so that disaster recovery is transparent to ROR console users, SVOM and VIOM need to be installed on the admin server of backup site under either of the following conditions. Once installation is complete, the conditions do not apply.
The admin server of primary site must be stopped
The network connecting to the primary site must be disconnected
Specify the failover information folder which was created in step 2. in the following definition file. The same settings must be made on the backup site as well as on the primary site in preparation for disaster recovery failover.
[Windows Manager]
Installation_folder\SVROR\Manager\etc\customize_data\fa_dr.rcxprop
After installing the manager, set up SSL if necessary.
For details, refer to "Chapter 2 Installation" and "Chapter 3 SSL Communication Environment Settings for the ROR Console" in the "Setup Guide CE".
Note
The site certificate that was issued by the CA should be used for the Disaster Recovery environment.
When test certificates are used, certificates on the backup site also need to be imported to the browser during installation or after switchover.
For details, refer to "Chapter 6 Importing a Certificate to a Browser" in the "Setup Guide CE".
When using Disaster Recovery, a license for the "DR option" is necessary.
After installing Resource Orchestrator, register the license for the "DR option" on the primary and backup sites.
For details on how to register the license, refer to "Chapter 5 License Setup and Confirmation" in the "Setup Guide CE".
The image file storage folder must be the Image folder created in step a. of "2. Set up for disaster recovery".
The following certificate files installed on both the primary and backup sites must be the same files. When installing a manager on the backup site, copy the files from the primary site. Perform this operation after stopping the manager.
When configuring a single backup site to inherit multiple primary sites, copy the following files of the manager on the primary site that is first created to the managers on the other primary sites.
Installation_folder\SVROR\Manager\etc\opt\FJSVssmgr\current\certificate
Installation_folder\SVROR\Manager\etc\opt\FJSVrcxdm\certificate
Installation_folder\SVROR\Manager\sys\apache\conf\ssl.crt
Installation_folder\SVROR\Manager\sys\apache\conf\ssl.key
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
Configure managed servers
Configure the settings of managed servers and network devices for the primary and backup sites.
Refer to "Chapter 2 Design" beforehand.
For details, refer to the following sections in the "Setup Guide CE".
"Chapter 7 Registering Infrastructure Administrators"
"Chapter 8 Creating Definition Files"
"Chapter 9 Registering Resources with Resource Orchestrator"
"Chapter 11 Installing Software and Registering Agents on VM Hosts"
"Chapter 12 Registering Resources to the Global Pool"
"Chapter 13 Creating L-Server Templates"
"Chapter 14 Creating an L-Server for an Infrastructure Administrator"
"Chapter 15 Collecting and Registering Cloning Images"
"Chapter 16 Creating L-Platform Templates"
For Disaster Recovery environments, configure as follows.
Register servers on the server tree in advance on the backup site as well as on the primary site. As for pools, L-Platforms, users and user groups registered on the orchestration tree on backup site, these do not need to be the same as those of primary site. Register them depending on the operations that will be performed on the backup site.
For network devices registered on the network device tree, prepare identical devices and register them in advance on the backup site.
When NS Appliance is used as a network device, also create an NS Appliance on the backup site and register it as a network device beforehand.
For NS Appliance operation procedures refer to the "NS Option Instruction".
When using the auto-configuration function for network devices
Copy the files and folders below to the backup site.
Installation_folder\SVROR\Manager\etc\customize_data\network_device_model.xml
Installation_folder\SVROR\Manager\etc\scripts\
Regarding the following configurations, use information that satisfies the necessities of both the primary and backup site.
Under Installation_folder\SVROR\Manager\etc\storage\emc
Installation_folder\SVROR\Manager\etc\customize_data\storage_portset.rcxprop
Under Installation_folder\Manager\etc\customize_data\fc_connection_pattern
Configure the server NIC definition
When using a NIC other than one in the default configurations of network auto-configuration and using a blade server, create a server NIC definition, and reflect it on the manager.
Create the same server NIC definition for the backup site same as for the primary site in advance, and reflect it on the manager.
Execute the rcxadm nicdefctl commit command, and reflect the created server NIC definition on the manager.
For details on server NIC definitions, refer to "14.11 Server NIC Definitions" in the "Reference Guide (Command/XML) CE".
For details on the rcxadm nicdefctl commit command, refer to "5.15 rcxadm nicdefctl" in the "Reference Guide (Command/XML) CE".
Create the files used for disaster recovery
Create the VM management software definition file
Create the following file under the failover information folder. This file is used to register VM management software to Resource Orchestrator on the backup site.
vmmgr_file.txt
The format of the VM management software definition file is shown below. Note that the first line of the example below is to explain the content of the file, so do not include this line in the actual file.
For details on the VM management software definition file, refer to "A.2 rcxrecovery".
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 |
Create the physical server mapping definition file
If you want to change the names of servers used for physical L-Servers on the primary and backup sites, create a physical server mapping definition file.
This file must be located in the MAP folder under the failover information folder and be a csv file which includes the following content.
#PhysicalServer Server1-1,Server2-1 Server1-2,Server2-2 : : |
Server1-1 and Server1-2 are the server names on the primary site.
Server2-1 and Server2-2 are the corresponding server names on backup site.
For details on the physical server mapping definitions, refer to "A.2 rcxrecovery".
Set up for automatic failover information collection
The portion of failover information, excluding setting information for firewalls and server load balancers, which is modified through operations by tenant users or tenant administrators can be collected automatically. There are the following two methods for operations to automatically collect the information:
Operation collecting the information periodically
To start operations for switchover at regular intervals, perform the following operation:
[Windows Manager]
>Installation_folder\SVROR\Manager\bin\rcxmgrexport -interval minutes <RETURN> |
For details on the rcxmgrexport command, refer to "A.1 rcxmgrexport".
Operation collecting the configuration definition information after changes are made
Execute the following command to collect the information automatically when operations by tenant users or tenant administrators which change the failover information are performed.
[Windows Manager]
>Installation_folder\SVROR\Manager\bin\rcxmgrexport -event on <RETURN> |
For details on the rcxmgrexport command, refer to "A.1 rcxmgrexport".
Note
When collecting the switchover information using Disaster Recovery, the information for the entire system is collected. When collecting the information in environments with a high frequency of update, or with short time intervals configured, normal operations may be affected. Review the operation method, considering the impact on business.
There is information which is not collected by the automatic collection performed by "7. Set up for automatic failover information collection", but is necessary for disaster recovery failover. Perform the operation described in "4.1 Normal Operation" to manually collect this failover information.
