Introduction to the asynchronous remote replication period

0

The asynchronous remote replication period is manually set during the creation of an asynchronous remote replication task. The period control policies include Manual, Timed wait when synchronization begins, and Timed wait when synchronization ends. For a file system, the period control policy can be set to Specify the time policy in addition to the preceding ones.

Other related questions:
What Is the Difference Between Synchronous Remote Replication and Asynchronous Remote Replication
Both synchronous remote replication and asynchronous remote replication can be used in disaster recovery solutions implemented by storage systems to back up data remotely. However, they are implemented in different ways and applicable to different service scenarios. Implementation modes are describes as follows: ? Synchronous remote replication: When a host writes data to the primary LUN, a write request is also sent to the secondary LUN. After both LUNs return a response indicating a successful I/O write, the primary storage system sends the host a response indicating a successful I/O write, implementing real-time data synchronization between the primary LUN and the secondary LUN. ? Asynchronous remote replication: When writing data to the primary LUN, the primary storage system records the changed data. After the primary LUN returns a response indicating a successful write, the primary storage system sends the host a response indicating a successful write. Then, data synchronization is triggered by a user manually or by the system based on user-defined trigger conditions to ensure data consistency between the primary LUN and the secondary LUN. Service scenarios are described as follows: ? Synchronous remote replication requires high bandwidth and low data latency. Therefore, synchronous remote replication is typically used in disaster recovery scenarios where the primary and secondary storage systems are adjacent to each other, such as the intra-city data backup and disaster recovery scenario. ? Asynchronous remote replication is not demanding on bandwidth and data latency. Therefore, asynchronous remote replication is applicable to disaster recovery scenarios where the primary and secondary storage systems are far away from each other or the network bandwidth is limited.

What is the relationship between NAS remote replication and SAN asynchronous remote replication?
The N8500 NAS remote replication is implemented based on SAN asynchronous remote replication. Each N8500 NAS remote replication pair corresponds to a consistency group of SAN asynchronous remote replication. If any resource in the consistency group of SAN asynchronous remote replication is faulty, the N8500 NAS remote replication become invalid as well. Then the storage unit will generate an alarm. You can rectify the fault according to the suggested actions in the alarm.

Introduction to the Dorado remote replication feature
Remote replication is the core technology used for remote data synchronization and disaster recovery. The remote replication feature has two modes: Synchronous remote replication: In this mode, data is synchronized in real time to achieve full protection for data consistency and to minimize data loss in the event of a disaster. Asynchronous remote replication: Data is synchronized periodically to minimize the adverse impact on service performance caused by the long latency of long-distance data transfer.

Why Does Asynchronous Remote Replication Site Recovery Need Multiple Synchronization Operations?
Multiple synchronization operations help minimize the write delay between the primary LUN and the secondary LUN. In addition, multiple synchronization operations are performed at short intervals. In this case, if you stop services and initiate data synchronization again, incremental data can be quickly synchronized before new write I/Os arrive. This prevents data loss and minimizes the downtime.

Specifications of S5600T remote replication
Specifications of S5600T V100R005 remote replication are as follows: -Maximum number of asynchronous remote replication groups: 256 (each primary LUN has a maximum of one secondary LUN.) -Maximum number of synchronous remote replication groups: 512 (each primary LUN has a maximum of two secondary LUNs and the secondary LUNs belong to different arrays) -Maximum number of remote replication consistency groups: 16 -Maximum number of pairs in a remote replication consistency group: 8 -Maximum capacity of synchronous remote replication: 476 TB -Default maximum capacity of asynchronous remote replication: 29 TB -Maximum number of connected remote disk arrays: 32 The specifications vary with the product version. For the latest specifications, see Software Specifications.

If you have more questions, you can seek help from following ways:
To iKnow To Live Chat
Scroll to top