Geo-redundant DR solution networking and replication

Dear Lucas,

Huawei's geo-redundancy with two active-active sites and a DR site solution provides the following solutions:

1. Remote Ethernet in the different city, asynchronous data replication.

2. FC networking in the same city, synchronous data replication.

Hope this can help you. Thank you.

the combinations of networking and replication technologies are recommended is

HyperMetro (SAN) and Asynchronous Replication (SAN) DR Principles

The
HyperMetro technology provided by storage devices is used for same-city
DR. Remote replication functions provided by storage devices are used
to replicate application data from a production data center to a DR
center for remote DR.

For details about storage
HyperMetro (SAN) and Asynchronous Replication (SAN) of the DR Star
networking, see About DR Star in the storage device online help.

• Storage
  devices are deployed for a production data center and a same-city DR
  center to implement HyperMetro DR. For details about the HyperMetro DC
  Solution, 
  

• Asynchronous
  remote replication is used between a same-city DR center and a remote
  DR center. The principles for asynchronous remote replication are as
  follows:

1. After
   an asynchronous remote replication relationship is set up between a
   primary LUN at a production site and a secondary LUN at a DR site, an
   initial synchronization is implemented.

2. If
   the primary LUN receives a write request from a production host during
   the initial synchronization, data is written only to the primary LUN.

3. After the initial synchronization is complete, Slave LUN Data Status is Synchronized or Consistent. (If the host sends no write request during the initial synchronization, Slave LUN Data Status is Synchronized; otherwise, Slave LUN Data Status is Consistent.).

   
   

I/O processing procedure in asynchronous replication

1. The primary LUN receives a write request from a production host.

2. After data is written to the primary LUN, a write completion response is immediately returned to the host.

3. Incremental
   data is automatically synchronized from the primary LUN to the
   secondary LUN based on the user-defined synchronization period. (If the
   synchronization type is Manual,
   users need to trigger the synchronization manually.) Before the
   synchronization, the storage system creates snapshots for the primary
   LUN and secondary LUN.

• The
  snapshot generated for the primary LUN ensures data consistency between
  the primary LUN and the secondary LUN during data synchronization.

• The
  snapshot for the secondary LUN provides backup for the data on the
  secondary LUN before synchronization. This ensures that data on the
  secondary LUN is usable even when an exception occurs during
  synchronization.

4. During the synchronization, data is read from the snapshot of the primary LUN and copied to the secondary LUN.

5. After
the synchronization is complete, the snapshots of the primary and
secondary LUNs are canceled, and the next synchronization period starts.