No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

OceanStor BCManager 6.5.0 eReplication User Guide 02

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Performing Planned Migration

Performing Planned Migration

This section describes how to perform planned migration at the DR site if data or applications at the production site need to be recovered to the DR site due to power failure, upgrade, or maintenance. During planned migration, the latest service data changes will be synchronized to the DR site. Ensure that the management and storage networks between the sites are normal.

Prerequisites

  • You have logged in to the eReplication as a user with DR management permission.
  • The production site and DR site communicate with each other correctly. The management system and the DR environment at the DR site are working correctly.
  • At least one recovery plan has been created in the system.
  • Storage devices, hosts, or VMs at the site where a protected group resides have been refreshed, if storage devices, hosts, or VMs at the production site or DR site change. For details, see Refreshing Resource Information.
The following table describes requirements for each protected object type.

Protected Object

Requirement

Oracle/IBM DB2/Microsoft SQL Server/Microsoft Exchange Server/SAP HANA

  • The database configuration of the DR host must be the same as that of the production host, including instance name, database name, and storage path.
  • Applications running at the production site have been manually shut down and disks are offline. LUNs of the applications that need to be recovered have been unmapped from production storage arrays; you can also modify the execution steps in a recovery plan to enable the Stop production service step.

FusionSphere VM

  • If the VM IP address for VM recovery is not configured, the IP address of the VM after planned migration is the same as that at the production end. If you want to configure a different IP address, configure one on the Protected Object tab page.
  • If disks are added to or deleted from the protected VM, refresh the VM information and manually execute the protected group where the VM resides.

VMware VM

  • The names of protected VMs cannot contain pound signs (#). Otherwise, you may fail to modify the VMs configuration file while performing planned migration.
  • If the VM IP address for VM recovery is not configured, the IP address of the VM after planned migration is the same as that at the production end. If you want to configure a different IP address, configure one on the Protected Object tab page.

Context

If the VM where the production site resides is configured with an IP address but without any network adapter, after the planned migration, the IP address of the VM where the DR site resides is:
  • Windows
    • Dynamically obtained when VM specifications already configured.
    • Consistent with that of the VM where the production site resides when VM specifications not configured.
  • Linux

    Dynamically obtained.

If you do not perform at least one successful DR test before planned migration, the failure probability of the planned migration will increase, and planned migration failure will stop the running of DR services. Therefore, before performing planned migration, you are advised to perform at least one successful DR test.

If the recovery plan is based on the snapshot or clone protection policy template, planned migration cannot be performed.

The time spent on planned migration is related to the data volume. Larger data volume indicates longer time.

In DR DC solutions (geo-redundant mode), services can be migrated from the production center to the same-city or remote DR center.

Procedure

  1. On the menu bar, select Utilization > Data Recovery.
  2. Select the remote recovery plan for which you want to perform planned migration and click More > Planned Migration on the Operation list.
  3. Perform planned migration based on the protected object type.

    NOTE:
    If Huawei multipathing software has been installed on the Linux DR host, ensure the configured I/O suspension time is not 0 and all virtual devices generated by the software have corresponding physical devices. For details, see the OceanStor UltraPath for Linux V100R008C00 User Guide.
    • If the protected object type is LUN, Local File System, Oracle, IBM DB2, Microsoft SQL Server, FusionSphere VM, or Microsoft Exchange Server,SAP HANA, perform the following:
      1. When the protected objects are databases, manually close applications running at the production site, ensure disks are in the offline state, and unmap LUNs relevant to the applications from production storage arrays. Alternatively, you can customize the planned migration procedure to enable the Stop production service step.
      2. Select a DR site.
        NOTE:
        • If T series V2 or a later version is deployed at the DR site, the DR host whose services you want to recover can belong to only one host group that belongs to only one mapping view. The secondary LUN of the remote replication pair that corresponds to the storage LUN used by the protected applications can belong to only one LUN group, and the LUN group must belong to the same mapping view as the host group. If T series V200R001C00 is deployed, after creating mapping view, you cannot select the Enable Inband Command to modify the properties of the mapping view.
        • If the storage is T series V2R2 or a later version or 18000 series, the storage support automatic host adding and storage mapping. If the connection between the storage device and the host initiator is normal, the hosts, host groups, LUN mappings, and mapping views will be created in the storage device automatically.
        • In the asynchronous replication scenario of the HANA database, you need to log in to the database to create a snapshot for restoring the database before stopping the service system and database applications. For details, see Creating a HANA Snapshot File.
      3. Select a DR host or host group and click Planned Migration.
      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.
    • If the protected object type is VMware VM, perform the following:
      1. Select the cluster you want to recover.

        VMs will be recovered to the cluster. You need to set DR Site, DR vCenter, and DR Cluster.

        NOTE:

        Upon your first test network selection, you need to set the cluster information.

      2. Select a network.

        The default recovery network is the network relevant to the resource mapping. If you want to change it, plan or select another network based on site requirements.

        NOTE:

        If Production Resource and DR Resource are not mapped, select Production Resource and DR Resource and click Add to the mapping view for mapping.

      3. Select non-critical VMs.

        In the Non-Critical VM list, select non-critical VMs you want to stop to release computing resources.

      4. Click Planned Migration.
      5. 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.
      6. Click OK.
    • If the protected object type is FusionSphere VM, perform the following steps:
      1. Select the cluster you want to recover.

        VMs will be recovered to the cluster. Select DR Site.

      2. Select an available powered-on host.

        The host will provide resources for VMs.

      3. Select non-critical VMs.

        In the Available VMs list, select non-critical VMs you want to stop to release computing resources.

      4. Click Planned Migration.
      5. 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.
      6. Click OK.
      NOTE:

      During the planned migration in host-based replication DR mode, if the migration task remains in the Stop the VM step for a long time, a possible cause is that the internal program of the operating system cannot be closed. You can log in to FusionCompute and then log in to the VM using Virtual Network Computing (VNC) as an administrator, identify the failure cause, and safely stop the VM. If the failure persists, forcibly stop the VM on FusionCompute. (Forcible VM stop may result in a planned migration failure.) After forcibly stopping the VM, go to the Recovery page, select the protected group of the VM, click Start on the Protected Object page, and select Consistency verification to synchronize data. After data synchronization, execute the planned migration again.

    • If the protected object type is NAS File System, perform the following:
      1. 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.
      2. Click OK.

Result

After the planned migration is being started, you can view the execution process and result. If the planned migration fails, you can resolve the problem and try again.

Follow-up Procedure

If the DR technology in use is remote replication, the system automatically creates snapshots at the DR end to protect the data during the planned migration. After the planned migration is complete, if the created snapshots cannot be automatically deleted, manually delete them to release storage space.

NOTE:

A snapshot name is a string of 31 characters in the following format: DRdata_LUNID_YYYYMMDDHHMMSS_BAK. YYYYMMDDHHMMSS means the point in time when data starts to be backed up; LUNID indicates the snapshot ID, whose value is an integer between 1 and 65,535. This naming format enables you to quickly find the desired snapshots at the DR end.

After executing planned migration, services are running at the DR site. If you want to switch the services back to the original production site, perform the following::
  1. Perform reprotection

    Before switching back services, performing reprotection can protect running data at the DR site and automatically recover the service data generated at the DR site to the original protection site based on the specified policy.

  2. Test the recovery plan.

    After reprotection, the service data at the DR site is recovered to the production site. Before service failback, you need to perform a DR test to ensure data usability.

  3. Clear test data.

    This operation will automatically clear the test data generated during the DR test to ensure the successful rate of service failback.

  4. Perform planned migration.

    This operation will automatically migrate services back to the original production site.

  5. Perform reprotection again.

    To ensure that services can be recovered at the DR site during failback, reprotection needs to be performed again.

For recovery plans whose protected object type is FusionSphere VM (non-OpenStack architecture), after the planned migration is successfully executed, you can export the configuration file, and view information about the FusionSphere VMs before and after the planned migration, such as resource mappings. The configuration file can be exported by performing the following:
  1. Select the recovery plan used to perform the planned migration and click the Protected Object tab in the lower area.
  2. Click Export to save the exported configuration file locally.
Translation
Download
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 10780

Downloads: 55

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next