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


To have a better experience, please upgrade your IE browser.


FusionCloud 6.3.0 Solution Description 05

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).
Implementation Principles

Implementation Principles

Logical Architecture

This section describes CSDR components and their positions in the system architecture layer by layer.

Figure 22-5 shows the logical architecture of CSDR.

Figure 22-5 Logical architecture of CSDR
Table 22-2 Component details





CSDR console

CSDR management console.



CSDR service system, which receives requests from the CSDR management console.

Management domain

ManageOne operation plane

Provide operation management for CSDR, such as quota, metering and so on.

ManageOne OM Plane

Provide operation and maintenance management for CSDR, such as alarm, log and so on.


Provides identity and access management for CSDR.

Service Flow

  • Figure 22-6 shows the workflow of CSDR.
    Figure 22-6 Service flow of CSDR
    1. A VDC operator applies for an ECS DR service instance on the ManageOne operation plane.
    2. After receiving the task of creating DR protection, eReplication invokes Nova API to query the number and capacity of volumes mounted to ECSs at the production end and obtains the corresponding storage device information.
    3. eReplication invokes Cinder API to create a secondary volume on the corresponding DR storage device.
    4. eReplication invokes DRExtend to create remote replication pairs between the primary and secondary volumes. Add all remote replication pairs in the service instance to the remote replication consistency group.
    5. eReplication invokes DR Nova API to unmount the system volumes of ECSs in the DR center.
  • Figure 22-7 shows the workflow of fault recovery of CSDR.
    Figure 22-7 Service flow of fault recovery

    1. BCManager eReplication invokes DRExtend API to perform a switchover of the consistency group.
    2. BCManager eReplication invokes Nova API to configure DR ECSs to release the placeholder tag of the DR ECSs.
    3. BCManager eReplication invokes Cinder API to mount volumes to the DR ECSs.
    4. BCManager eReplication invokes Nova API to start DR ECSs.
    5. Create the protected group again on eReplication.
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 162304

Downloads: 264

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