Introduction to storage-based replication and host-based replication of OceanStor ReplicationDirector

3

To protect the mission-critical data of disaster recovery virtual machines, OceanStor ReplicationDirector provides two disaster recovery modes:
1. Storage-based replication: The remote replication feature of the underlying SAN storage replicates and protects data of disaster recovery virtual machines. Both Synchronous remote replication and asynchronous remote replication are supported.
2. Host-based replication: FusionCompute enables the real-time asynchronous replication feature to replicate and protect disaster recovery virtual machine data. The feature is supported by Hypervisor of virtual storage and FusionStorage.

Other related questions:
Introduction to the OceanStor ReplicationDirector host and host group
In OceanStor ReplicationDirector, a host refers to an application server deployed at the production site or disaster recovery site. A host protected at the production site is called a production host, and a host used for testing or disaster recovery at the disaster recovery site is called a disaster recovery host. A host group is a collection of one or more hosts of the same type.

Introduction to the asynchronous remote replication period
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.

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 cannot the initial synchronization of the LUN-based remote replication synchronize the file storage pool information?
The creation sequence of an N8500 LUN-based remote replication is to create a remote replication relationship, start initial synchronization, and then create a file storage pool. Therefore, a file storage pool is created after the synchronization process. After initial synchronization, the secondary LUN does not have the file storage pool information, and an alarm, File storage pools for replication fail to be obtained, will be generated for a disaster recovery test. Therefore, if you want to perform a disaster recovery test, start an incremental synchronization to synchronize the file storage pool information of the primary LUN to the secondary LUN.

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