Configure the settings of managed servers and network devices for the primary and backup sites.
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.
Common Configurations
For details on the items to match or to be different, between the primary and backup sites, refer to "Chapter 2 Design".
Register servers on the server tree in advance on the backup site as well as on the primary site. It is also necessary to configure the BIOS settings on the registered server in advance. For details, refer to "8.2.7 Configuring BIOS Settings of Managed Servers" in the "Design Guide CE".
As for pools, L-Platforms, users and user groups registered on the orchestration tree on the backup site, these do not need to be the same as those of the primary site. Register them depending on the operations that will be performed on the backup site before switchover.
For network devices registered on the network 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
Install the backup site before moving on to the phase to register it in the resource pool. When using the backup site for tasks with lower priority, proceed with the backup site installation before performing switchover.
Configurations when an L-Server Linked with a Configured Virtual Machine (VMware) is the Switchover Target
When L-Servers linked with configured virtual machines (VMware) are switchover targets, it is necessary to modify the configurations regarding the UUIDs of VM guests before performing switchover. Modify configurations following the descriptions in the VMware section in "Configuration Requirements for VM Guest Switchovers" in "D.2 Configuration Requirements" in the "Design Guide VE".
Configuration When Performing Virtual L-Server Switchover (VM Guest)
The advisory notes regarding performing virtual L-Server switchover (VM guest) are given below.
Install VM hosts on the primary site and the backup site respectively.
Do not configure VM hosts on physical L-Servers.
Before performing switchover, perform the following preparations for the backup site in order to be able to mount the replicated LUNs on the correct VM hosts. It is necessary to mount the replicated LUNs on the VM host connected with the images stored in each VM host registered in the VM pool used by L-Servers in the LUNs, or in VM hosts connected with the images stored in the LUNs.
Note
Define the information of the VM hosts connected with the LUNs storing images in advance, since the information must be entered during the switchover procedure. Refer to "4.2 Switchover Operations between Sites Using the Disaster Recovery Function".
When using FC or iSCSI connection disks
Configure the zoning and mapping settings so that the replicated LUNs can be referred to from the VM hosts.
When using NAS connection disks
Operate the network links or the storage software so that the replicated LUNs can be mounted on the VM hosts.
Prepare the NFS connection information files which describe the information (NFS server addresses and NFS paths) for mounting each replicated LUN (datastore) in the following format. Use this file during the switchover procedure. Refer to "4.2 Switchover Operations between Sites Using the Disaster Recovery Function".
Datastore name, IP address or FQDN, NFS path |
Example
storage_X,192.168.3.230,/nfs/data |
When using distributed virtual switches, the connections between the virtual machines and the port group of the distributed virtual switches in the switchover destination site cannot be restored. After switchover, configure the settings again.
When editing the destination VM files of the virtual machines through direct operation of VM management software, edit all VM files to deploy on the datastore in which the system disks or data disks of the virtual machines are located.
When editing the destination VM file through direct operation of VM management software, edit the VM file for a template (cloning image) to deploy in the datastore.
Only a datastore used by the switchover target L-Servers or cloning images can be mounted in the VM host, during the switchover procedure. When mounting a replicated datastore other than the above, manually mount it after switchover.
Once disks are deleted from a virtual machine in the switchover source site, any snapshot of the virtual machine taken before deletion of disks cannot be used on the switchover destination site. Therefore you should delete snapshots and take a new one after deleting disks from a virtual machine.
If snapshots taken before deletion of disks are not deleted, there will be following effects on the switchover destination site:
Unavailable snapshots consume the disk resources.
If the usage charge calculation function is enabled in the accounting settings, the usage charge for unavailable snapshots are calculated in the same way as other available snapshots.
