Top
ServerView Resource Orchestrator Cloud Edition V3.4.0 DR Option Instruction
FUJITSU Software

3.6 Creating Files Used for Switchover

Create the following files on the switchover source site.

When performing failback, it is also necessary to create the following files on the switchover destination site.

  1. Create the mapping definitions of physical servers [Physical L-Server switchover (physical OS), Physical/Virtual L-Server switchover (VM host/VM guest)]

    When names of physical servers registered on the server tree of Resource Orchestrator are different between the switchover source site and the switchover destination site, creating mapping definitions enables defining of the relationships of corresponding servers 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 (",").

      #PhysicalServer 
      Server1-1,Server2-1 
      Server1-2,Server2-2

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

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

    For details on the physical server mapping definitions, refer to "B.2 rcxrecovery".

    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"
  2. Create the mapping definitions of VM management software [Physical/virtual L-Server switchover (VM host/VM guest), virtual L-Server switchover (VM guest)]

    When names of VM management software registered on the VM management tree of Resource Orchestrator are different between the switchover source site and the switchover destination site, creating the mapping definitions enables defining of the relationship of corresponding VM management software 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 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 (",").

      #VMManagementSoftware 
      VMM1-1,VMM2-1 VMM1-2,VMM2-2

    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.

    For details on the mapping definitions of VM management software, refer to "B.2 rcxrecovery".

    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"
  3. Create a definition file of VM management software [Physical/virtual L-Server switchover (VM host/VM guest)]

    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.
    • The format of this definition file is shown below.

      For details on the VM management software definition file, refer to "B.2 rcxrecovery".

      #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

    After performing failback, when restoring the switchover destination site to the state that it was in before switchover, create this definition file on the switchover destination site, in addition to the definition file for failback. In addition, include the information of the switchover destination site in the definition file.

    The definition file created for VM management software is used when performing "4.2.1 Stopping Services and Releasing Resources [Switchover Destination Site]".

    Note

    When using virtual L-Server switchover (VM guest), do not create this file.

  4. Create a VM pool definition file [Virtual L-Server switchover (VM guest)]

    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.
    • The format of this definition file is shown below.

      For details on the VM pool definition files, refer to "B.2 rcxrecovery".

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

    After performing failback, when restoring the switchover destination site to the state that it was in before switchover, create this definition file on the switchover destination site, in addition to the definition file for failback. In addition, include the information of the switchover destination site in the definition file.

    The definition file created is used when performing "4.2.1 Stopping Services and Releasing Resources [Switchover Destination Site]".

    Note

    When performing physical/virtual L-Server switchover (VM host/VM guest), do not create this file.

    Information

    By configuring the number of VM pools specified in the VM pool in the file above as one smaller than that of the switchover source site, the number of VM hosts can be reduced on the switchover destination site.