The BCManager architecture shows eReplication Server components associated with the production and DR environments, while the one-click fault-recovery workflow explicitly performs recovery by setting storage resources at the DR site to writable, mapping LUNs, configuring storage, and recovering services.
The statement is therefore TRUE. In a dual-eReplication-server remote DR deployment, management operations can normally be initiated through either management endpoint because the servers coordinate DR configuration and protection information. Fault recovery is different because the production environment is assumed to be unavailable or impaired. Recovery must consequently be executed from the DR-side management environment that remains accessible and can coordinate activation of DR resources.
The fault-recovery workflow reflects this requirement: secondary resource consistency is checked, DR storage is made writable, LUNs are mapped, the storage configuration is completed, and services are recovered at the DR site.
Huawei also recommends placing DR management capabilities where they remain available when production infrastructure fails, reinforcing the design objective of independent DR-side recovery control.
Study Guide Topics: Data Protection Solution → OceanStor BCManager eReplication → Remote DR Deployment → One-Click Fault Recovery → Recovery Plan Execution.
