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

Remote Replication Feature Guide for File 04

OceanStor 5300 V3, 5500 V3, 5600 V3, 5800 V3, and 6800 V3 Storage System V300R002

"This document describes the file system remote replication feature, in terms of the implementation principle,application scenario, and explains how to configure and manage this feature."
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).
Service Switchover

Service Switchover

When the primary site of a remote replication session encounters a disaster, the secondary site can quickly take over services from the primary site to ensure service continuity.

The remote replication feature not only implements remote data backup but also recovers services as soon as possible in the case of a disaster to keep service continuity. You must consider the following two indicators when designing a DR solution.

  • RPO

    Recovery Point Objective (RPO) refers to the maximum acceptable time period prior to a failure or disaster during which changes to data may be lost as a consequence of recovery. Data changes preceding the failure or disaster by at least this time period are preserved by recovery. The RPO indicates the tolerable amount of lost data. In asynchronous remote replication scenarios RPO is equal to the time that you set. Set RPO of file system remote replication to Interval.

  • RTO

    Recovery Time Objective (RTO) refers to the maximum acceptable time period required to bring one or more applications and associated data back from an outage to a correct operational state. It takes the recovery time point as the objective and ensures that the secondary host can take over services as quickly as possible. The RTO indicates the tolerable service interruption time. The RTO of file system remote replication depends on host services and fault scenarios.

The remote replication parameter should be chosen based on users' requirements for the RPO and RTO.

Working Principle

Services can run on the secondary storage system only when the following conditions are met:
  • Historical service data exists in the secondary storage system.
  • The service on the production host has also been configured on the secondary host.
  • The secondary storage system allows a host to access the file system shared to the host.
When the primary site fails due to a disaster, the remote replication links between the primary file system and the secondary file system are down. In this case, administrator needs to set the access permission of secondary file system manually to accessible, and a service switchover can be performed. Figure 1-3 shows how a service switchover is implemented when a disaster occurs.
Figure 1-3  Service switchover when a disaster occurs

NOTE:
After a primary/secondary switchover is implemented, the primary and secondary sites will record changed data respectively to avoid the full synchronization next time when the secondary site turns back to the primary one.
Translation
Download
Updated: 2019-01-02

Document ID: EDOC1000069276

Views: 10161

Downloads: 194

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