“Business Recovery Service (BRS) provides disaster recovery (DR) for Elastic Cloud Servers (ECSs), Elastic Volume Service (EVS) disks, and Dedicated Distributed Storage Service (DSS). BRS uses technologies, such as host-level replication, data redundancy, and cache acceleration, to ensure data reliability and service continuity.”
“BRS supports asynchronous replication with second-level RPO and an RTO under 30 minutes.”
Huawei source: Training PDF pp. 245–246
Technical Deep Dive
The statement misidentifies the recovery objective. Huawei's V3.5 material says Business Recovery Service (BRS) supports asynchronous replication with a recovery point objective (RPO) on the order of seconds and a recovery time objective (RTO) below 30 minutes. The stem incorrectly substitutes 'RTO of only seconds', so the answer is FALSE, option B.
RPO measures how far behind the latest committed production data the recovered copy may be after a failure. A second-level RPO means the amount of potential lost change data can be limited to a short time, depending on replication health and the failure scenario. RTO measures how long it takes to restore service following an incident. Bringing up recovery ECS instances, attaching replicated storage, completing network changes and starting application processes all take time; these operations are represented by the RTO rather than the RPO.
Huawei BRS can protect ECS and related storage resources by replicating data and configuration to a recovery site. It supports failover and disaster recovery drills. Crash consistency means the restored image resembles data after a sudden power loss; it is not necessarily the same as an application-consistent checkpoint. Databases may still need log replay or recovery procedures, and distributed applications may require coordination among services. Architects must test both RPO and RTO, validate routing and access at the DR site, and monitor replication lag. The false wording about seconds-long RTO is the decisive error.
Submit