Creating a Level-2 Copy Automatically and Mounting It

Procedure

1. In the navigation tree, choose Utilization > Data Mounting.
2. Click Create.
3. Set Name and Description of the mounting plan.
4. Select Protection Plan.

   If no proper protection plan is found, click Advanced Selection. On the Select Protection Plan page, search for the protection plan based on Type, Protection Plan, Protection Site, or Protected Object.

5. Select the copy or cloud copy to be mounted.
6. Configure the mounting settings.
   • If the mounted copy is a local copy or a remote copy, select Site and Host or Host Group to which the copy is mounted. If the protected object is VMware, select Site, vCenter, and Cluster, and configure the network and VM information required for the copy reuse scenario.

     Network: By default, the network corresponding to the resource mapping is used. You are advised to separate the network used by the copy from the network used by the production VM to avoid IP address conflicts.

     

     If you only need to mount the RDM disk to an existing VM, the configuration does not affect the network configuration of the target VM.

     VM IP Address: If you need to register a new VM and specify the VM IP address, set this parameter. If the RDM disk only needs to be mounted to a target VM and does not need to be registered as a new VM, you do not need to set this parameter.

     VM Configuration: To restore some VMs in a copy or mount RDM disks of some VMs in a copy to the target VM, click Set on the right of VM Configuration.

     • Restore some VMs in the copy: Set Registered to Yes. RDM Disk Mounting Configuration does not need to be configured.
     • If RDM disks of some VMs are mounted to the target VM, click Not Configured in the RDM Disk Mounting Configuration column and select the RDM disks to be mounted and mount them to the target VM.

       If Shares and Limit-IOPs of the RDM disk of the production VM are not Normal or Unlimited by default, Shares and Limit-IOPs of the target VM will change to the default values after the disk is mounted. If you need to change the value, log in to the target VM and perform the following steps as required:

       1. Log in to vSphere vCenter.
       2. In the navigation tree on the left, right-click the target VM and choose Edit Settings > Virtual Hardware from the shortcut menu.
       3. In the Virtual Hardware area, click before the disk name.
       4. In the expanded disk information, change Shares and Limit-IOPs of the target VM.
       

       • Batch configuration of registration and power-on status is supported.
       • By default, RDM disks are mounted to the controller where the system disk of the target VM resides. Therefore, the total number of disks in the controller where the system disk of the target VM resides plus the number of RDM disks to be mounted to the target VM cannot exceed 14. For example, if the number of disks in the controller where the system disk of the target VM resides is 2, the number of RDM disks to be mounted to the target VM cannot exceed 12.
   • If the mounted copy is a cloud copy, select Site and Cloud Server to which the copy is mounted, and select Disk Type.
     

     If the selected copy is a cloud copy and the site is a cloud site, you can perform the next step only.

7. Select a mounting time point.
8. (Optional) Select Create level-2 copy mounting and select Level-2 Copy Type.

   When the selected copy is a level-1 copy and is not a cloud backup copy, a level-2 copy is created for the selected copy to prevent data from being read and written to the selected copy, thereby destroying the data at the selected copy time.

9. Optional: If you want scripts to be executed automatically on the host to adapt to special data usage scenarios, for example, invoke the script to execute data decription, or stop or start a process, log in to the host to download the script template and customize the script, click Advanced to set the names of the pre-script and post-script to be mounted.
   

   

   • A customized script is not provided by eReplication, so the script provider must ensure the script correctness. Before configuring the script, ensure that the script has been tested and verified.
   • After the copy is mounted, if the protected object type is VMware VM, the VM name registered on the test host is in the format of Protected VM name_4-digit random number_Replica_Mounting plan name.

10. Set mounting items. Table 1 describes related parameters.

    Table 1 Mounting parameters

    Parameter	Description	Remarks
    Unmount Mounted Copies Before Mounting	Before mounting copies for multiple times, unmount the mounted copies. Otherwise, the copies may fail to be mounted. If this parameter is selected, the system automatically unmounts all copies mounted to the current host.	This parameter can be configured for supported protected objects.
    Delete the copies automatically after the unmounting	If this parameter is selected, the system automatically deletes the unmounted copy.	This parameter can be configured for supported protected objects.
    Start the database after the mounting	If this option is selected, the database is automatically started after the copy is mounted to the target host or host group. If this option is not selected, you need to log in to the host and manually start the database after the copy is mounted to the target host or host group.	This parameter can be configured when the protected object is Oracle, DB2, or SQL Server.
    Start the VM after the mounting	If this option is selected, the VM will be automatically started after the copy is mounted to the target cluster. You are advised to separate the network used by the copy from that used by the production VM to avoid IP address conflict. If this option is not selected, you need to log in to vCenter and manually start the VM after the copy is mounted to the target cluster. To avoid IP address conflict, you may need to edit the network settings of the VM before starting the VM on vCenter.	This parameter can be configured when the protected object is VMware.