Top
ServerView Resource Orchestrator Cloud Edition V3.1.2 DR Option Instruction
FUJITSU Software
Chapter 2 Design > 2.6 Configuration of the Primary and Backup Sites
PreviousNext

2.6 Configuration of the Primary and Backup Sites

Define the configurations of the primary and backup sites.

Configurations to Perform Site Switchover Transparently for ROR Console Users

In order to perform site switchover transparently for ROR console users, when connecting to the admin server from the ROR console, perform either one of the following operations for the IP address and the host name (FQDN) of the admin server used for connecting the ROR console with the admin server.

These operations can only be performed when switching over the sites.

When switching over the tenants, connect to the network by specifying the FQDN of the admin server.


Items to be Matched between the Primary and Backup Sites

Match the following items between the primary and backup sites.

Switchover Method

Item

Description

Common

Levels and versions of FUJITSU Software ServerView Resource Orchestrator Cloud Edition managers

If patches are applied to the manager on either of the sites, ensure the patch is applied on the other manager.

Installation folders of FUJITSU Software ServerView Resource Orchestrator Cloud Edition managers

OS of the admin server

Use the same version.

Managed server configuration

Assign identical names to the servers and chassis to be registered in the server trees on both sites.
Use identical models and configurations for servers and chassis with the same names between sites.

The server names on the server trees can be changed according to the site.
Refer to "3.6 Creating Files Used for Switchover".

For virtual L-Server switchover (VM guests), the number of servers of the VM hosts can be reduced by using VM pool definition files.
For details on VM pool definition files, refer to "3.6 Creating Files Used for Switchover".

The number of blade chassis, and the LAN switch blades on them, on the server tree in the switchover destination site can be reduced.

For details, refer to "2.5 Degrading Blade Chassis".

Network devices connected with managed servers

Assign identical names to the network devices (L2 switches, firewalls, and Ethernet Fabric switches) to be registered in the network trees on both sites.
Use identical models and configurations for the network devices with the same names between sites.

For details on the network devices of the automatic configuration target (L2 switches, firewalls, Ethernet Fabric switches), configure the same settings of the network configuration information, and perform the same pre-configuration of the network devices.

For details on how to configure network configuration information, refer to "9.4.8 When Managing Network Devices as Resources" in the "Design Guide CE".

For details on the pre-configuration of network devices, refer to "9.2.3 Settings for Managed Network Devices" in the "Design Guide CE".

Configurations of network devices (blade configurations: CB, rack mount configurations: L2 switches)

Models, links, firmware, and account settings must be the same.
For details on the L2 switches of automatic configuration targets, refer to "Network devices connected with managed servers" in "Items".

LAN switch blade configuration

Assign identical names to the LAN switch blade to be registered in the server trees on both sites. (*)
Use identical models and configurations for the LAN switch blades with the same names between sites.

Of all of the LAN switch blades to be registered in the server tree on the switchover source site, when there are LAN switch blades to be degraded, it is not necessary to register LAN switch blades with the same names in the server tree on the switchover destination site.

For details, refer to "2.5 Degrading Blade Chassis".

Network settings (CB uplink/downlink ports, or VLAN settings for external switch VLANs)

The settings must be the same when performing manual network settings (L2, L3) in advance.

If it is not possible to match the settings of the sites in advance for reasons such as validation of the backup site, match them during the switchover procedure.

SAN switch settings (zoning)

Configure physical servers to access corresponding LUNs (in a replication relationship) of both sites.

  • When the switchover method is either physical L-Server switchover (physical OS) or physical/virtual L-Server switchover (VM host/VM guest), without ETERNUS storage

    Configure SAN switches of the backup site using the WWPNs of HBA ports on the primary site and that of storage ports on the backup site.

  • When the switchover method is either physical L-Server switchover (physical OS) or physical/virtual L-Server switchover (VM host/VM guest), using ETERNUS

    SAN switches are automatically configured during switchover, and no settings are required.

The admin LAN IP address of the admin server

For virtual L-Server switchover, when there are no network resources of the admin LAN, the IP addresses do not need to be the same.

The physical server name specified for a physical L-Server for NS Appliance

Rights changes due to customization of roles

If roles are customized on the primary site, ensure the same changes are made on the backup site.

For details on how to customize roles, refer to "5.1.3 Customizing Roles" in the "Design Guide CE".

The configuration of Active Directory when using the Single Sign-On function of ServerView Operations Manager

When operating Active Directory in a redundant configuration, use an Active Directory in a redundant configuration on both sites.

Physical/virtual L-Server switchover (VM host/VM guest)

The name of VM management software on FUJITSU Software ServerView Resource Orchestrator Cloud Edition

Specify the same names when installing VM management software for each site (excluding switchover target physical L-Servers).

When mapping definitions are created, different names can be used for each site.

For details on mapping definitions, refer to "3.6 Creating Files Used for Switchover".

Virtual L-Server switchover (VM guest)

Port groups (names, VLAN settings)

The settings must be the same when performing manual network settings in advance. For details on how to manually configure the network settings, refer to "C.2.5 Manual Network Configuration" in the "Setup Guide CE".

The name of VM management software on FUJITSU Software ServerView Resource Orchestrator Cloud Edition

When mapping definitions are created, different names can be used for each site.

For details on mapping definitions, refer to "3.6 Creating Files Used for Switchover".

Configurations of VM management software (cluster L-Server deployment policy)

Configure the same L-Server deployment policy settings (such as VMware HA is available) with the switchover source cluster for the cluster to which the VM host described in the VM pool definition file belongs.

For details on VM pool definition files, refer to "3.6 Creating Files Used for Switchover".

For details on the L-Server deployment policy settings, refer to "E.1.2 Preparations for Servers" in the "Design Guide CE".

Note

Do not configure the same vCenter instance IDs of VMware vCenter Server for each site.

* Note: If no network resources that configure external connection ports exist, it is not necessary to match the names of LAN switch blades on the server tree between sites.


Items to be Different between the Primary and Backup Sites

For the following items, configure different values between the primary and backup sites.

Item

Switchover Method

Item

Description

Items to be Different between Sites

Common

The computer name of the admin server

For the computer name of the admin server, configure different names for the primary and backup sites.

When re-installing the admin server due to a disaster, the computer names that have been used for the primary site or backup site before cannot be used.

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

IP addresses of storage units are required for replication.

The following resources to be registered with the primary site

  • Tenant names

  • Resource folder names

  • Pool names (global pools only)

  • L-Server template names

  • Virtual storage names

  • Network device names

  • Network resource names

  • Names of address set resources

  • User group names

  • User names

For the Active-Active operation or tenant switchover, do not create resources with the same names in different sites.
However, for resources that are created by DR switchover (import of configuration information) there is no problem with the same names being used between sites.

After switchover, which sites resources belong to should be defined, and it is recommended to add the site name to the beginning of the resource names.

Resource names duplicated between sites can be checked using the DR configuration check tool. For details, refer to "Checking Using the DR Configuration Check Tool" in "4.1 Normal Operation".

For network device names, ensure that the same names are not used for the network devices that are the target of switchover on the switchover source site and the network devices on the switchover destination site that will not be switched over.

For details on resources automatically created when installing the manager, refer to the following points:

  • For the following resources, their resource names can remain the same between sites and there is no need to change them:

    • The "supervisor" user group

    • Dual-role administrators whose access scope is "all"

  • For the following resources, delete the resource from one of the sites or change the resource names so that the resource names are not duplicated between the sites.

    • The "monitor" user group

    • L-Server templates (sample_large, sample_medium, sample_physical, sample_small)

    • Global pools (VMHostPool, ServerPool, StoragePool, NetworkPool, AddressPool, ImagePool)

The following resources to be registered with the primary site

  • Global L-Server name

For tenant switchover, do not create resources with the same names between sites.
However, for resources that are created by DR switchover (import of configuration information) there is no problem with the same names being used between sites.

Registered information on network resources

For the Active-Active operation or tenant switchover, do not register a network resource with the same IP address or VLAN ID as that of a network resource registered on one site, on the other site. If the network resource with the duplicated settings on the switchover destination site will be deleted when cleaning up during the switchover, there is no problem with registering a network resource with duplicated settings.

Registered information on address set resources

For the Active-Active operation or tenant switchover, do not register the MAC addresses and WWNs that are already registered with one site on another.

Settings of host names for virtual servers

For the Active-Active operation, when using "prefix with serial number" style of "3" to set host names of virtual servers, specify different character strings for the prefixes of each site.

For details on how to configure host names of virtual servers, refer to "18.4 Setting the Host Names for Virtual Servers" in the "Setup Guide CE".

Settings for Software ID Prefixes

For the Active-Active operation, change the prefix settings of the software IDs to use different prefixes between sites.

For details on how to set prefixes for software IDs, refer to Appendix A Settings for Software ID Prefixes".

Physical L-Server Switchover (Physical OS) or Physical/Virtual L-Server Switchover (VM Host/VM Guest)

The IP addresses of servers registered in the server tree

For the IP addresses configured in the servers registered in the server tree, the different IP addresses according to each site.

Also, for the IP addresses to be specified when creating physical L-Servers, do not use IP addresses that have been set for servers during the server registration to the server tree.


Virtual Storage Resource Names and Disk Resource Names

Information

Addition of Numbers to Virtual Storage Resource Names

For the virtual storage resource names of FUJITSU Software ServerView Resource Orchestrator Cloud Edition, the datastore name, the Cluster Shared Volume name, or the RAID group name is used. If the names overlap, the overlap will be avoided by the addition of numbers to the end of resource names. Therefore, in order to prevent to the addition of numbers to the end of the virtual storage names, configure the datastore name, Cluster Shared Volume name, and the RAID group name not to overlap with the virtual storage resource names between sites.


Configuration Files for Matching Details between the Primary and Backup Sites

When changing the following files in the primary site, also change the files in the backup site.
* indicates arbitrary files in the folders.
The above changes are not necessary when no file exists in both the primary and backup sites.

[Windows Manager]

Folder

File Name

Installation_folder\SVROR\Manager\etc\

trapop.bat

Installation_folder\SVROR\Manager\etc\customize_data\

auto_replace.rcxprop

cli_notlist_oc.rcxprop

create_image_previous_folder_name_scvmm.rcxprop

disable_num_of_address_check.rcxprop

folder.rcxprop

gui_always_home.rcxprop

gui_config.rcxprop

gui_enable_reverse_proxy.rcxprop

image_admin_hyperv.rcxprop

image_admin_hyperv_User_Group_Name.rcxprop

iscsi.rcxprop

iscsi_User_Group_Name.rcxprop

kb978336_scvmm.rcxprop

l_server.rcxprop

ldap_attr.rcxprop

library_share_deny.conf

library_share_User_Group_Name_deny.conf

manager_backup.rcxprop

manager_memory.rcxprop

multiple_ds.rcxprop

mwgui_config.rcxprop

network_device_model.xml

network_map.rcxprop

network_viewer.rcxprop

os_setting.rcxprop

os_setting_User_Group_Name.rcxprop

physical_l_server_nicmodify_blade.rcxprop

physical_l_server_nicmodify_rack.rcxprop

pool.rcxprop

product_report.rcxprop

rcxmgrctl_except_rba.rcxprop

scvmm_mac_pool.rcxprop

scvmm_mac_pool_Tenant_Name.rcxprop

server_control.rcxprop

show_vds_vc.rcxprop

spare_server_config.rcxprop

storage.rcxprop

tenant_config.xml

tenant_move.rcxprop

unm_mon.rcxprop

unm_provisioning.rcxprop

use_image_data_disk

vdipool_group_entitlement.rcxprop

viom.rcxprop

vm.rcxprop

vm_console.rcxprop

vmguest_uuid_output.rcxprop

vnetwork_excluded_vmware.rcxprop

vnetwork_hyperv.rcxprop

vnetwork_oraclevm.rcxprop

vnetwork_rhelkvm.rcxprop

vnetwork_rhelxen.rcxprop

vnetwork_vmware.rcxprop

Installation_folder\SVROR\Manager\etc\customize_data\alive_monitoring\

Physical.rcxprop

vm_Hyper-V.rcxprop

vm_VMware.rcxprop

Installation_folder\SVROR\Manager\etc\customize_data\home_tab\

home_infra_mes.txt

home_tenant_mes.txt

Installation_folder\SVROR\Manager\etc\customize_data\l_server\net\

*

Installation_folder\SVROR\Manager\etc\customize_data\net\

net_info.Network_Resource_Name.conf

net_info.L-Server_Name.conf

Installation_folder\SVROR\Manager\etc\customize_data\nicdefctl\host\

*

Installation_folder\SVROR\Manager\etc\customize_data\nicdefctl\model\

*

Installation_folder\SVROR\Manager\etc\customize_data\setup_wizard\

enable_advanced_mode.rcxprop

lplatform_console_setup_parameter_on

Installation_folder\SVROR\Manager\etc\customize_data\sysprep_guirunonce\

*

Installation_folder\SVROR\Manager\etc\customize_data\vm_prop

vm_*.rcxprop

Installation_folder\SVROR\Manager\etc\event_handler\

*

Installation_folder\SVROR\Manager\etc\l_platform\

enable_cloning

Installation_folder\SVROR\Manager\etc\l_server\

disable_check_num_of_cpu

enable_cpu_per_socket

Installation_folder\SVROR\Manager\etc\scripts\

*

Installation_folder\SVROR\Manager\etc\scripts\Exec_Script\

*

Installation_folder\SVROR\Manager\etc\scripts\network_resource\

Unm_network_setting.xml

Installation_folder\SVROR\Manager\etc\scripts\network_resource\Ruleset_Name\

*

Installation_folder\SVROR\Manager\etc\scripts\Vendor_Name\Unit_Name or Model_Name\common\

*

Installation_folder\SVROR\Manager\etc\scripts\Vendor_Name\Unit_Name or Model_Name\operations\Ruleset_Name\

*

Installation_folder\SVROR\Manager\etc\scripts\Vendor_Name\Unit_Name or Model_Name\rulesets\Ruleset_Name\

*

Installation_folder\SVROR\Manager\etc\user_scripts\

*

Installation_folder\SVROR\Manager\etc\vm\

delete_image_all_files_scvmm

delete_old_image

online_cloning

require_image_location

single_storage_vc

snapshot_skip_reconfig

thin_provisioning

vds_vc

Installation_folder\SVROR\Manager\rails\config\rcx\

vm_guest_params.rb

Installation_folder\SVROR\Manager\sys\irmctool

*

Installation_folder\SVROR\Manager\sys\usm\etc\

clariion.conf

emcpath.conf

falconstor.conf

fspath.conf

symmetrix.conf

usm.conf

Installation_folder\SVROR\Manager\var\lserver_repair\ruleset_backup\

*

Installation_folder\SVROR\ScwPro\tftp\rcbootimg\

awwn*.cfg


[Linux Manager]

Directory

File Name

/etc/opt/FJSVrcvmr/

trapop.sh

/etc/opt/FJSVrcvmr/customize_data/

auto_replace.rcxprop

cli_notlist_oc.rcxprop

create_image_previous_folder_name_scvmm.rcxprop

disable_num_of_address_check.rcxprop

folder.rcxprop

gui_always_home.rcxprop

gui_config.rcxprop

gui_enable_reverse_proxy.rcxprop

image_admin_hyperv.rcxprop

image_admin_hyperv_User_Group_Name.rcxprop

iscsi.rcxprop

iscsi_User_Group_Name.rcxprop

kb978336_scvmm.rcxprop

l_server.rcxprop

ldap_attr.rcxprop

library_share_deny.conf

library_share_User_Group_Name_deny.conf

manager_backup.rcxprop

manager_memory.rcxprop

multiple_ds.rcxprop

mwgui_config.rcxprop

network_device_model.xml

network_map.rcxprop

network_viewer.rcxprop

os_setting.rcxprop

os_setting_User_Group_Name.rcxprop

physical_l_server_nicmodify_blade.rcxprop

physical_l_server_nicmodify_rack.rcxprop

pool.rcxprop

product_report.rcxprop

rcxmgrctl_except_rba.rcxprop

scvmm_mac_pool.rcxprop

scvmm_mac_pool_Tenant_Name.rcxprop

server_control.rcxprop

show_vds_vc.rcxprop

spare_server_config.rcxprop

storage.rcxprop

tenant_config.xml

tenant_move.rcxprop

unm_mon.rcxprop

unm_provisioning.rcxprop

use_image_data_disk

vdipool_group_entitlement.rcxprop

viom.rcxprop

vm.rcxprop

vm_console.rcxprop

vnetwork_excluded_vmware.rcxprop

vnetwork_hyperv.rcxprop

vnetwork_oraclevm.rcxprop

vnetwork_rhelkvm.rcxprop

vnetwork_rhelxen.rcxprop

vnetwork_vmware.rcxprop

/etc/opt/FJSVrcvmr/customize_data/alive_monitoring/

Physical.rcxprop

vm_Hyper-V.rcxprop

vm_VMware.rcxprop

/etc/opt/FJSVrcvmr/customize_data/home_tab/

home_infra_mes.txt

home_tenant_mes.txt

/etc/opt/FJSVrcvmr/customize_data/l_server/net/

*

/etc/opt/FJSVrcvmr/customize_data/net/

net_info.Network_Resource_Name.conf

net_info.L-Server_Name.conf

/etc/opt/FJSVrcvmr/customize_data/nicdefctl/host/

*

/etc/opt/FJSVrcvmr/customize_data/nicdefctl/model/

*

/etc/opt/FJSVrcvmr/customize_data/setup_wizard/

enable_advanced_mode.rcxprop

lplatform_console_setup_parameter_on

/etc/opt/FJSVrcvmr/customize_data/sysprep_guirunonce/

*

/etc/opt/FJSVrcvmr/customize_data/vm_prop/

vm_*.rcxprop

/etc/opt/FJSVrcvmr/event_handler/

*

/etc/opt/FJSVrcvmr/l_platform/

enable_cloning

/etc/opt/FJSVrcvmr/l_server/

disable_check_num_of_cpu

enable_control

enable_cpu_per_socket

/etc/opt/FJSVrcvmr/scripts/

*

/etc/opt/FJSVrcvmr/scripts/Exec_Script/

*

/etc/opt/FJSVrcvmr/scripts/network_resource/

Unm_network_setting.xml

/etc/opt/FJSVrcvmr/scripts/network_resource/Ruleset_Name/

*

/etc/opt/FJSVrcvmr/scripts/Vendor_Name/Unit_Name or Model_Name/common/

*

/etc/opt/FJSVrcvmr/scripts/Vendor_Name/Unit_Name or Model_Name/operations/Ruleset_Name/

*

/etc/opt/FJSVrcvmr/scripts/Vendor_Name/Unit_Name or Model_Name/rulesets/Ruleset_Name/

*

/etc/opt/FJSVrcvmr/user_scripts/

*

/etc/opt/FJSVrcvmr/vm/

delete_image_all_files_scvmm

delete_old_image

online_cloning

require_image_location

single_storage_vc

snapshot_skip_reconfig

thin_provisioning

vds_vc

/opt/FJSVrcvmr/rails/config/rcx/

vm_guest_params.rb

/opt/FJSVrcvmr/sys/irmctool

*

/opt/FJSVrcvmr/sys/usm/etc/

clariion.conf

emcpath.conf

falconstor.conf

fspath.conf

symmetrix.conf

usm.conf

/var/opt/FJSVrcvmr/lserver_repair/ruleset_backup/

*

/var/opt/FJSVscw-tftpsv/tftproot/rcbootimg/

awwn*.cfg


When the contents of definition files shown below differ between sites at the switchover in the Active-Active operation, matching them is not easy.
When editing definition files on the switchover source site, merge the edited contents manually in the switchover destination site, before switchover. For details on how to edit definition files, see the references listed below.

Overview

File Name

Reference

Definition file for alive monitoring

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data\alive_monitoring

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data/alive_monitoring

  • File Name

    vm_VMware.rcxprop
    vm_Hyper-V.rcxprop

Refer to "C.1.6 Definition File for Alive Monitoring" in the "Setup Guide CE".

Editing information in the Home window of the ROR console

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data\home_tab

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data/home_tab

  • File Name

    home_infra_mes.txt
    home_tenant_mes.txt

Refer to "8.4 Editing Information in the Home Window" in the "Operation Guide CE".

When using driver-specific parameters such as GLS or Bonding for scripts for configuring networks

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data\net

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data/net

  • File Name

    net_info.network resource name.conf
    net_info.l_server name.conf

Refer to "B.8 Network Redundancy and VLAN Settings of L-Servers" in the "Setup Guide CE".

[Hyper-V]
Configuration file for access limitation in the image storage location

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data

  • File Name

    library_share_deny.conf
    library_share_User_Group_Name_deny.conf

Refer to "C.3.8 Collecting and Deleting Cloning Images" in the "Setup Guide CE".

[Hyper-V]
For specification of the VM guest administrator account when L-Servers are created by specifying an image

  • Stored folder

    [Windows Manager]

    Installation_folder\SVROR\Manager\etc\customize_data

  • File Name

    image_admin_hyperv.rcxprop
    image_admin_hyperv.User_Group_Name.rcxprop

Refer to "C.3.9 [OS] Tab Configuration" in the "Setup Guide CE".

When creating virtual L-Servers using VMware ESXi on other companies' servers

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data

  • File Name

    server_control.rcxprop

Refer to "C.1.5 Configuration when Creating a Virtual L-Server Using VMware ESXi on Other Vendor's Servers" in the "Setup Guide CE".

  • vm.rcxprop

    When modifying behaviors of server virtualization software

  • vm_console.rcxprop

    When configuring using console connections from public LANs

  • Stored folder

    [Windows Manager]

    Installation_folder\SVROR\Manager\etc\customize_data

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data

  • File Name

    vm.rcxprop
    vm_console.rcxprop

Refer to "C.2.1 Creating Definition Files" in the "Setup Guide CE".

When creating L-Servers connected with NICs using System Center 2012 Virtual Machine Manager

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data

  • File Name

    scvmm_mac_pool.rcxprop
    scvmm_mac_pool_Tenant_Name.rxxprop

Refer to "C.3.5 Manual Network Configuration" in the "Setup Guide CE".

When using distributed virtual switches

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\vm

    [Linux Manager]
    /etc/opt/FJSVrcvmr/vm

  • File Name

    vds_vc

Refer to "E.1.4 Network Preparations" in the "Design Guide CE".

iSCSI network definition file

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data\

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data/

  • File Name

    iscsi_User_Group_Name.rcxprop
    iscsi.rcxprop

Refer to "B.1.10 Definition File for iSCSI Network" in the "Setup Guide CE".

Configuration for ordering display of resources on trees

  • Stored folder

    [Windows Manager]
    Installation_folder\SVROR\Manager\etc\customize_data\

    [Linux Manager]
    /etc/opt/FJSVrcvmr/customize_data/

  • File Name

    gui_config.rcxprop

Refer to "2.3.1.3 Sorting the Resource List in the Tree" in the "Release Notes".

If the following configuration files exist in the Active-Active operation, contact Fujitsu technical staff.

[Windows Manager]

[Linux Manager]

Customized Settings on the Primary Site

For the Active-Standby operation, the following customizations on the primary site, which are performed according to "Chapter 18 Post-Installation Procedures" in the "Setup Guide CE", 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.

Back up the following files if they have been modified.

[Windows Manager]

[Linux Manager]

For the Active-Active operation, configurations of the following should be different between sites.

For configurations other than the above, use identical configurations between sites as with the Active-Standby operation.

PreviousNext
Copyright 2012-2015 FUJITSU LIMITED