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


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


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).
Local Protection Solution

Local Protection Solution

This section describes the characteristics, DR technologies, and principles of the local protection solution.

Solution Introduction

This solution uses the snapshot technology to ensure local availability of host services. In addition, it can protect snapshots of protected objects for rolling back data, preventing data loss and data corruption caused by viruses.


As the information technology develops, data security and availability are becoming the major concerns of enterprises. This solution provides protection and DR for key data in mainstream application systems.

Solution Description

This solution employs the snapshot and clone technologies on the production service systems to implement local protection and data rollback.

The following lists the supported DR technologies:
  • Clone (SAN)
  • Snapshot (SAN)
  • Snapshot (NAS)
  • Snapshot (VIS)
Deployment Modes

One eReplication Server is deployed on a server in the production center to provide DR management for production resources. The network between the eReplication Server and production center must be properly connected.

Clone (SAN) DR

Based on the storage clone technology, data copies can be synchronized with source data in real time, providing continuous data protection to achieve zero data loss.

Figure 1-34 shows the network of clone (SAN) DR.

Figure 1-34  Clone (SAN) DR
Snapshot DR

If data suffers non-physical damage such as a virus attack or mistaken data deletion or replacement, a snapshot created before the damage can be used to recover lost data, ensuring data security and retrievability of the source data. Snapshot (SAN), snapshot (VIS), and snapshot (NAS) are different in implementation principles, but same in network.

Figure 1-35 shows the network of snapshot (SAN) DR.

Figure 1-35  Snapshot (SAN) DR
DR Management
eReplication provides the following functions:
  • Automatically identify the storage LUN and remote replication relationship by detecting applications on hosts and the storage system of applications.
  • Protect service hosts and VMs based on preset DR policies.
  • Modify snapshot quantity or time tables of the policy by snapshot configuration.
  • Perform the recovery plan to roll back snapshots by one click.

Clone DR Principles

Clone is a type of snapshot. A clone provides a complete copy of the source data at a time point. Using clone can implement LUN-level data recovery without interrupting services.

Figure 1-36 shows the network of clone (SAN) DR.
Figure 1-36  Implementation principles
Cloning contains three phases:
  1. Synchronization: Data is copied from the primary LUN to a secondary LUN. Then, dual-write is implemented between the primary and secondary LUNs.
  2. Splitting: After a synchronization is complete, you can split the pair at a certain time point. Then, the secondary LUN becomes an available copy of the primary LUN and stores all data on the primary LUN at the time when the pair was split.

    After a pair is split, the secondary LUN is accessible to hosts, allowing hosts to access data identical to that on the primary LUN without affecting the performance of the primary LUN. After a pair is split, you can perform a synchronization or reverse synchronization again between the primary LUN and the secondary LUN.

  3. Reverse synchronization: If you want to restore data on the primary LUN, you can perform a reverse synchronization to copy data from the secondary LUN to the primary LUN. After the reverse synchronization is complete, the pair is automatically split.
During a synchronization or reverse synchronization, hosts can still access the primary LUN, ensuring service continuity.

Snapshot DR Principles

This solution uses the snapshot technology to ensure local availability of host services. It employs snapshot to protect data locally and implement data rollback, preventing data loss and data corruption caused by viruses.

Figure 1-37 shows the network of snapshot (SAN) DR.
Figure 1-37  Implementation Principles
You can roll back a source LUN using a snapshot or recreate a snapshot as required.
  • If a source LUN encounters non-physical damage, you can perform rollback to quickly recover data on the source LUN to the data at the time point when the virtual snapshot was activated.
  • If data on a source LUN is changed, you can reactivate the snapshot of the source LUN to quickly synchronize data changes made to the source LUN.
Updated: 2019-05-21

Document ID: EDOC1100075861

Views: 14770

Downloads: 70

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