Self-defining Startup Parameters for a Protected Object

If upper-layer services have special requirements on the startup sequence of databases or VMs, or on the recovery network of VMs, you can modify startup parameters based on live network conditions before performing DR. Therefore, databases or VMs can start services after DR. This operation can be performed only in the DR management system at the DR site.

Prerequisites

Procedure

  1. On the menu bar, select Utilization > Data Restore.
  2. When the protected objects are Oracle, IBM DB2, , SAP HANAor Microsoft SQL Server databases, you can define the startup sequence of databases during DR.

    1. Select a recovery plan whose protected objects are databases and click the Protected Object tab below it.
    2. Click .

    3. If you choose to start databases during DR testing, planned migration, or fault recovery, you can set the database startup sequence.
      • When multiple databases in a protected group are mutually dependent or upper-layer services have requirements on database startup sequence, you can set the startup sequence of databases. The default startup sequence number is 10. The database with a smaller number starts earlier. A smaller sequence number indicates a higher startup priority. Databases with the same priority start randomly.
      • For databases whose Database Type is Container database (CDB), you can choose whether to start pluggable databases of container databases.
    4. In the Warning dialog box that is displayed, read the content of the dialog box carefully and select I have read and understood the consequences associated with performing this operation.
    5. Click OK.

  3. When the protected objects are VMware VMs or FusionCompute VMs, you can define the startup sequence and DR network of VMs.

    1. Select a recovery plan whose protected objects are VMs and click the Protected Object tab below it.
    2. Click Startup Settings.
      • VMware VMs or FusionCompute VMs (Non-OpenStack Architecture)

    3. Choose whether to start VMs during DR testing, fault recovery, or planned migration.
      • If you select Yes, you can set the VM startup sequence. The default startup sequence number is 10. The startup sequence number for a VM ranges from 1 to 512. A smaller sequence number indicates a higher startup priority. VMs with higher priorities start earlier. VMs with the same priority start randomly. Template VMs cannot be started during recovery. By default, they cannot be started or modified.
      • If you select No, the VMs cannot be started during DR testing, fault recovery, or planned migration.
    4. If you want to modify the configurations for VM DR network, select a VM to be modified and click Network Settings in the operation area of the VM. In the dialog box that is displayed, modify the configurations.
      • FusionCompute VMs (Non-OpenStack architecture)

        If you specify a recovery network when recovering a VM, the system automatically assigns this network to the VM. If you do not specify a recovery network, the VM keeps original network settings after being recovered.

        In the FusionCompute scenario:

        • Before configuring this parameter for a VM, ensure that the VM at the production site has been configured with specifications attributes, or the template for creating the VM has been configured with specifications attributes. Only a VM that meets the prior requirements supports IP address customization. For details, see sections Configuring Specifications Attribute Customization for a Linux VM and Configuring Specifications Attribute Customization for a Windows VM in the document based on the actual version of FusionCompute.
        • If the version of FusionCompute is FusionCompute V100R005C00, see FusionCompute V100R005C00 Virtual Machine Management Guide.
        • If the version of FusionCompute is FusionCompute V100R005C10, see FusionCompute V100R005C10 Virtual Machine Management Guide.
        • If the version of FusionCompute is FusionCompute V100R006C00, see FusionCompute Product Documentation (Server Virtualization,FusionCompute V100R006C00U1).
        • In the FusionCompute scenario, you can modify configurations of the VM network in a batch.
        • Click Export IP Configuration to export the configuration template.
          1. Modify the configurations of the VM network. If Enable IPv4 Address Settings is set to N, IPv4 address settings are disabled. For details about how to modify the configuration information, see Note in the configuration template.
          2. Click Import IP Configuration to import the configuration template.

        • Currently, only IPv4 and IPv6 address settings are supported.
        • When configuring a customized IP address for a DR test or planned migration, if you need to enable the function of modifying the MAC address of a network adapter, go to the installation directory of eReplication, open the Runtime/LegoRuntime/conf/lego.properties configuration file, and add information changemac_when_modify_ip=true to the end of the file. Save the modification and exit, and restart eReplication for the modification to take effect. If you want to disable the function of modifying the MAC address of a network adapter, you can delete information changemac_when_modify_ip=true from the configuration file, and then restart eReplication for the modification to take effect.
        • Before configuring the DR network for a Linux VM, go to /etc/init.d and check whether the passwd_conf and setpasswd.sh files exist. If yes, delete the files and then select the network adapter whose recovery network you want to configure and configure an IPv4 address or elastic IP address.
        • Before configuring the DR network for a Windows VM, go to the root directory of drive C and check whether the setpass.vbs and passwd.inf files exist. If yes, delete the files and then select the network adapter whose recovery network you want to configure and configure an IPv4 address or elastic IP address.

          When configure the DR network for a Windows VM, the administrator account of the Windows operating system cannot be disabled.

      • VMware VMs

        When recovering a VM, if you have specified a recovery network, the system automatically assigns this network to the VM. If you do not specify a recovery network, the VM keeps original network settings after being recovered.

        • Only Windows and Linux VMware VMs can be configured with the network recovery function. For details about supported versions of the two operating systems, see the Guest OS Customization Support Matrix, which can be obtained from the VMware official website.
        • Network configuration is not supported for VMs whose host names contain periods (.) in versions earlier than vCenter 7.0.
        • For VMs running Windows, first enter the administrator authentication information about the VM operating system, then select a network adapter whose recovery network you want to configure, and choose to manually specify or automatically obtain the IP address/DNS server addresses based on your requirements.

          If you select the automatic mode, the system automatically assigns an IP address or DNS server address to the DR network.

          If the recovery network is not configured, the DR network uses the configuration of the production network.

        • For VMs running Linux, first select a network adapter whose recovery network you want to configure, then choose to manually specify or automatically obtain the IP address/DNS server addresses based on your requirements, and finally configure the global DNS server address.

          If you select the automatic mode, the system automatically assigns an IP address or DNS server address to the DR network.

Parent topic: DR Recovery
Copyright © Huawei Technologies Co., Ltd.