Huawei CBS V500R005C30: Active-Active Disaster Recovery Solution

7/17/2019 Huawei CBS a-A GDR Solution
Huawei CBS V500R005C30
Active-Active Disaster Recovery Solution
HUAWEI TECHNOLOGIES CO., LTD.

http://slidepdf.com/reader/full/huawei-cbs-a-a-gdr-solution 1/33
Contents
 A-A DR Architecture
 Deployment
 Data Replication
 Solution and RTO for different scenarios in case disaster strikes

 Data loss
 Impact on Performance and Dimensioning
Active-Active DR Architecture – High Level
Site A (Main Site) BMP BMP Site B
BMPD BMPD
B B
USRDB USRDB
GMDB GMDB GMDB GMDB

CDRDB CDRDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter CBPAdapte
CBPAdapter
r
1 2r
GMDB GMDB
SEE SEE SEE SEE

DCC
FEP/ FEP/
USAU FEP FEP USAU
USAU2
USAU1 GFEP GFEP
EMPP
SMPP+
CAP/MAP/INAP If SMSC/
Core Network GGSN/ then SM
MSC/STP SMSC MMSC directly.
PGW
HUAWEI TECHNOLOGIES CO., LTD. Huawei proprietary. No spread without permission. Page 4
Active-Active DR Architecture – Low Level
See next page for Architecture in Low Level
Notes:
1. CRM/ESB is assumed to send requests to BMP Cluster 1 in site A via BMPGateway1.
2. BMP Custer 1 is Active while BMP Cluster 2 is Standby.

3. CBP & CBPAdapter are in Active-Active model, each site with 100% capacity, 50% production traffic.
4. OCG(SEE) is in all active mode.
Scenarios:
1. Operation & Management
a. BMP of Site A writes the updates to physical database (BMPDB, SYSDB, USRDB etc) and when the tran
the updates will be synchronized/written in Site B due to the mechanism of physical database.
b. At the same time, the updates will be synchronized to both GMDB of Site A & Site B from the physica
2. Calling & Data Usage & Other Service

a. When the CBP updates the GMDB and these updates don’t need to be written to physical database, t
synchronized from GMDB of site A to GMDB of site B or vice versa, depending on which site receive and p
b. When the CBP updates the GMDB and these updates need to be written to physical database. No ma
processes the traffic, the updates will first synchronized to physical database of site A and then written to
Acronyms
BMP: Business Management Point
In the Huawei OCS solution, the BMP implements service operation management, and provide system ma
management, Offer Management, resource management, customer management & customer service Ma
CRM/CC system which provides the GUI for subscribers and telecom operators can invoke these functions
CBP: Convergent Billing Point

In the Huawei OCS solution, the CBP implements rating, charging and accounting functions and supports o
For online charging, after receiving the charging & authentication request from the OCG, the CBP perform
reservation for the conversation duration, and indicates the conversation duration to the OCG. After recei
deduction request from the OCG, the CBP deducts the expense in real time.
GMDB: General Memory Database

A Huawei-developed relational database system designed based on physical memory and database indust
is applied to the applications that require high-performance database access and real-time processing.
OCG: Online Control and Charging Gateway

OCG provides online call and charging control and routing service.
SEE: Service Execution Environment

FEP/GFEP: General Front End Processor
USAU: Universal Signaling Access Unit
7/17/2019 BMPGatew Huawei CBS a-A GDR Solution
BMPGatew BMPGatew
ay
ay
Site A (Main Site) ay Site
BMP1 BMP3
w, r
w, r BMPD BMPD
B B
USRDB USRDB
Invoicin
Invoicin Invoi
gg GMDB GMDB g
CDRDB GMDB GMDB CDRDB
BillMgm CBP1 BillM
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
t t
BillDB BillDB
Report Repo
CBPAdapte
CBPAdapter
r r
1 2r r
Mediatio GMDB GMDB Media
n n
I200
I2000 SEE SEE SEE SEE
DCC
FEP/ FEP/
USAU FEP FEP USAU
USAU2
USAU1 GFEP GFEP
EMPP
SMPP+
CAP/MAP/INAP
If SMSC/
Core Network then SM
MSC/STP GGSN SMSC MMSC directly.
DR Deployment Scheme -1/2

NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma Remark
nual
CBPAdapter A-A Two-node cluster (100% capa city, Two-node cluster (100% capa city, Both GMDB in site 1/2 is div
(incl. GMDB) 50% production traffic) 50% production traffic) each scheme adopts o
CBP (incl. A-A Two-node cluster (100% capa city, Two-node cluster (100% capa city, Both GMDB in site 1/2 is div

GMDB) 50% production traffic) 50% production traffic) each scheme adopts o
USAU A-A Two-node cluster (100% capacity, Two-node cluster (100% capa city, Both No date replication
50% production traffic) 50% production traffic)
FEP/GFEP A-A Two-node cluster (100% capacity, Two-node cluster (100% capa city, Both No data replication
50% production traffic) 50% production traffic) 1，Depends on wheth
polling mode.
SEE (i.e. OCG) A-A N+1 cluster (load balancing, N+1 cluster (load balancing, Both In case N=1, Site 1/2 will
100% capacity, 50% production 100% capacity, 50% production In case N>=2, Site 1/2 wi
enough because N provid
traffic) traffic)
traffic is handled)
BMPGateway A-S Two-node cluster (100% capacity, Single-node system (100% Both No date replication
(SLB) 100% production traffic) capacity, 0% production traffic)
BMP A-S N+1 cluster (100% capacity, N+1 cluster (100% capacity, 0% Both Including UPC/GL/AR/
100% production traffic) production traffic)
BMPDB(SYSD A-S Two-node cluster (100% capacity, Single-node system (100% Both Oracle Active Data Gu
B) 100% production read traffic, capacity, 0% production read
100% production write traffic) traffic, 0% production write traffic)
DR Deployment Scheme- 2/2 (End)
NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma Remark

nual
USRDB A-S Two-node cluster (100% capacity, Single-node system (100% Both
100% production read traffic, capacity, 0% production traffic)
100% production write traffic)
CDRDB, BillDB A-S Two-node cluster traffic)

100% production (100% capacity, Single-node (100%
production traffic) capacity, 0% Both .
SDU Currently SDU is deployed along with USRDB in the same board, the mode and deployment is same as USRDB;
In future, SDU will be replaced by memory DB (OMDB), the mode and deployment is same as SEE.
Invoicing A-S Two-node cluster (100% capacity, Single-node (100% capacity, 0% Both
100% production traffic) production traffic)
Bill A-S Single-node (100% capacity, Single-node (100% capacity, 0% Both
Management 100% production traffic) production traffic)
Report A-S Single-node (100% capacity, Single-node (100% capacity, 0% Both By default, DR is not s
100% production traffic) production traffic) In case of DR, only rep
source file will not be r
Mediation A-S Single-node (100% capacity, 50% Single-node (100% capacity, Both No date/file replication
production traffic) 50% production traffic)
I2000 A- Two-node cluster or single- Single-node (100% capacity, 0% Both If I2000 is deployed in
S(Optio node(100% capacity, 100% production traffic) then DR is not suppor
nal) production traffic) If I2000 is deployed in
DR can be supported,
single-node in DR site
Oracle GoldenGate Data Replication
Site A (Main Site) Site B

OG
Ora
Source Target
Oracle DB Oracle DB
Online
1. The Oracle Golde
redo logs source DB extrac
and archive log a
3, Apply local trail file.
Archived 1, Extract 2. OGG sends the t
redo log source DB to targ
files
2.1 Send 2.2 Receive 3. The OGG of the t
Trail files Network Trail files file content and
the target DB to
Date Replication for BMPDB and USRDB
Site A (Main Site) BMP BMP Site

1 3
read
Cach Cach
e e
write
BMPD BMPD
Write, read B B
(Read-write (Read-only
status) status)
USRDB USRDB
write write write

(Read-write write (Read-o
Cache
status) Cacher Cache Cache status)
GMDB r GMDB r
r
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
r r
SEE SEE SEE SEE
Cache Cache Cache Cache
 For BMPDB/USRDB , Huawei use Oracle DB, the Replication solution will use Oracle Golden Gate. License fee needs to b
 BMPGateway + BMP+BMPDB are deployed in one DR switch group.
Date Replication for USRDB – Low Level : Asynch
Replication
Site A Site B
Active Active
Application Application
1. Update
1. Update
2. Send change
USRDB USRDB
replication engine
3. Update (remote change)

3. Update (remote chang
 To respect the high performance requirement on real time rating and charging, Huawei provides asynchronous replication
 The related application includes BMPAPP, CBPAPP.
Date Replication for GMDB – High Level
GMDB GMDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
CBPAdapte
CBPAdapter
r r
1
GMDB 2
GMDB
For Memory DB, it is made by Huawei, it support high performance service processing. Consider to the
performance, the data replication also adopt Asynchronous Replication solution.
Date Replication for GMDB – Low Level : Asynchr
Replication
Site A Site B
Active Active
Application Application
1. Update
2. Send change
GMDB GMDB
Scheme Scheme
1a replication engine
Scheme 1b
Scheme
2b 2a
3. Update (remote change)
3. Update (remote chang
 To respect the high performance requirement on real time rating and charging, Huawei provides asynchronous replication
 The related application includes CBPAPP, CBPAdapter
Routing
 There is routing table in CBPAdapter(GMDB), so it can know which CBP to route.

 All the routing table in each site are same and keep the FULL routing data. So when one CB
CBPAdapter can route the request to the other CBP.
 CBPAdapter first checks the routing table of discrete number, if the MSISDN is not found in
based routing will be applied.
GMDB GMDB GMDB GMDB
CBP1 CBP2 CBP3 CBP4

CBP1 CBP2 CBP3 CBP4
135* 138* 135* 138*
CBPAdapte
CBPAdapter
r
1 2r
GMDB GMDB
Virtual GT of OCG(SEE)
 SEE cluster in both sites share the same Virtual GT (GT3). SEE cluster in site A has a real GT(GT1), SEE clu
a real GT(GT2) 。
 STP is assumed to support polling.
 USAU1 in Site A talks to SEE cluster in Site A only, while USAU2 in Site B talks to SEE cluster in Site B onl
MSC STP USAU1 SEE SEE USAU2
IDP(DGT=GT3)
IDP(DGT=GT3)
IDP(DGT=GT3)
RRBE(OGT=GT1)
RRBE(OGT=GT1)
RRBE(OGT=GT1)
ERB(DGT=GT1)
ERB(DGT=GT1) ERB(DGT=GT1)
IDP(DGT=GT3)
IDP(DGT=GT3)
IDP(DGT=GT
RRBE(OGT=G
RRBE(OGT=GT2)
RRBE(OGT=GT2)
Scenario1: When CBP (APP2) is down
BMP BMP
Site A (Main Site) 1 3 Site B
w, r w r
w, r BMPD BMPD r
B B
USRDB USRDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
r 1. D
1 2r
GMDB GMDB b
C
2. W
SEE SEE SEE SEE t
s
t
i
i
Scenario1: CBP GDR switchover flow
GDR switchover duration: 3s
RTO/Downtime：
3s System
switch
Single node Dual cluster
failure switch Service
failure takeover
Time
Dual cluster Disaster System switch schedule
switch detection（ About less than 3s）
In case of Manual The GDR software:

Switch: Depending 1. Check the CBP data replication link, if it is not
on decision stopped, stop it.
mechanism; 2. Set the CBP2 status to faulty in system
In case of
Automatic Switch:
definition table in BMPDB(SYSDB), update the
Configurable, status of CBP2 into the cache of other normal
about 10minutes CBPs and CBPAdapter. Then CBPAdapter
automatically change routing.
Scenario2: When CBP Adapter1 is down
Site A (Main Site) Site B
GMDB GMDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
CBPAdapte
CBPAdapter
r
1 2r
GMDB GMDB
SEE SEE SEE SEE

DCC
FEP/ FEP/
FEP FEP
GFEP GFEP
EMPP
SMPP+
Core Network
MSC/STP GGSN SMSC MMSC
Scenario 2: CBP Adapter Rerouting Flow
GDR switchover duration: 10s

RTO/Downtime：
10s System
switch
Single Dual cluster
node
failure switch
failure Service
takeover
Time
Dual cluster Disaster Rerouting (About schedule
switch detection less than 10s）
In case of Manual The GDR software:

Switch: Depending
on decision 1. Check the CBPAdapter data replication link, if it is
not stopped, stop it.
mechanism; 2. Set the CBPAdapter1 status to faulty in system
In case of Automatic definition table in BMPDB(SYSDB), update the
Switch: status of CBPAdapter1 into the cache of every CBP
Configurable, about and SEE. Then SEE automatically change routing.
10minutes SEE automatically set the CBPAdapter1 status to
faulty and will not send requests to CBPAdapter1.
Scenario 3.1.1: When OCG(SEE) is down (i.e. number of faulty SEE
to switch
1 3
CBPAdapte
CBPAdapte CBPAdapte
CBPAdapte
rr rr
GMDB GMDB
SEE SEE SEE SEE SEE SEE SEE SEE SEE SEE
USAU1
USAU1 USAU2
USAU2
50% traffic 50% traffic
MSC/STP
Scenario 3.1.2: When OCG(SEE) is down (i.e. number of faulty SEE
Cluster+USAU1 will switch jointly
1 3
CBPAdapte
CBPAdapte CBPAdapte
CBPAdapte
rr rr
GMDB GMDB
SEE SEE SEE SEE SEE SEE SEE SEE SEE SEE
USAU1
USAU1 USAU2
USAU2
50% traffic 50% traffic
MSC/STP
 USAU+OCG(SEE) are deployed in one DR switch group.
Scenario 3.1.2: OCG(SEE)+USAU GDR switchove
flow
GDR switchover duration: <13s
System
switch System recover
Single Signaling/IP
node links takeover
failure
Time
Disaster detection System Signaling schedule
switch takeover
(About less (About
In case of Manual than 3s) less than
10s)
Switch: Depending
on decision
mechanism; 1. Notify BMP that Depend on STP’s ability, STP
In case of Automatic SEE is down. needs to send charging
Switch: requests to USAU in site B,
Configurable, about that is STP-USAU-SEE-
10minutes CBPAdapter.
Scenario 4.1: When BMP1 in BMP Cluster 1 is down (i.e. number o

Scenario 4.1: When BMP1 in BMP Cluster 1 is down (i.e. number o
BMP<=1), no need to switch
Suppose there are multiple BMPs(e.g. BMP1-3) in BMP Cluster 1 in main site, and only BMP1 is down, then BMP2 and
BMP3 can takeover the services, and GDR switch is not required. The mechanism is similar to that of SEE.
BMPGatew
BMPGatew BMPGatew
ay
ay
BMP BMP
1 w, r 3w, r w,r
w, r BMPD BMPD
B B
USRDB USRDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
r r
1 2r r
GMDB GMDB
SEE SEE SEE SEE
Scenario 4.2: When BMP Cluster 1is down, BMP Cluster
1+BMPDB1+BMPGateway will switch jointly
Because BMPDB(SYSDB) forms a complete data, and BMP at each site talks to BMPDB(SYSDB) on that site only, so BMP
Cluster 1 and BMPDB(SYSDB) need switch jointly. BMPGateway is also included in the DR switch group.
BMPGatew
BMPGatew BMPGatew
ay
ay
BMP BMP
w, r 1 w, r 3 w, r w,r
w, r BMPD BMPD
B B
USRDB USRDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
r r
1 2r r
GMDB GMDB
SEE SEE SEE SEE
 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

Scenario 4.3: When BMPDB1 is down, BMP Cluster 1+BMPDB1+B
switch jointly
Because BMPDB(SYSDB) forms a complete data, and BMP at each site talks to BMPDB(SYSDB) on that site only, so BMP
Cluster 1 and BMPDB(SYSDB) need switch jointly. BMPGateway is also included in the DR switch group.
BMPGatew
BMPGatew BMPGatew
ay
ay
BMP BMP
w, r 1 w, r 3 w, r w,r
w, r BMPD BMPD
B B
USRDB USRDB
GMDB GMDB
CBP1
CBP1 CBP2
CBP2 CBP3
CBP3 CBP4
CBP4
BillDB BillDB
CBPAdapte
CBPAdapter
r r
1 2r r
GMDB GMDB
SEE SEE SEE SEE

Scenario 4.4: When BMPGateway is down, BMP Cluster 1+BMPDB

will switch jointly
CRM/ESB is assumed to send all requests to BMP Cluster 1 in site A via BMPGateway1. When BMPGateway is down,
CRM/ESB needs to change BMPGateway IP address to BMPGateway of site B.
CRM/ES
B
100% traffic
100% traffic
BMPGatew
BMPGatew BMPGatew
Site A (Main Site) ay
ay ay Site B
BMP Cluster 1 BMP Cluster 2

BMP BMP
1 3
w, r w,r
BMPD BMPD
B B

Scenario 4: BMP Cluster 1+BMPDB1+BMPGateway GDR switchov
GDR switchover duration: 3m-8m
Service
takeover System recover
Single Dual cluster
node Peripheral
switch element
failure failure
switch
Time
Dual cluster Disaster System Peripheral schedule
switch detection switch element switch
(About less (About less than
than 3m) 5m)
In case of Manual 1. Start the application in CRM/ESB needs to change BMPGatew
Switch: Depending the DRBMPAPP. address to BMPGateway of site B. (
on decision 2. Oracle take over(1-3m).
configuration, depending on CRM/E
mechanism; 3. The GDR software:
 Notify CBPs of site A to
capability)
In case of
Automatic Switch: change BMP Cluster IP
Configurable, address to BMP Cluster
about 10minutes of site B.(auto)
 Notify OCGs of site A to
change BMP Cluster IP

address to BMP Cluster
of site B.(auto)
Summary Table of Switchover Duration of Different

Scenarios
Scenario Switchover Duration Remark
Scenario1: When CBP (APP2) is down 3s

Scenario2: When CBP Adapter1 down 10s
Scenario 3.1.1: When OCG(SEE) down(<=X) 0s no need to switch
Scenario 3.1.2 : When OCG(SEE) down(>X) 13s
Scenario 4: 3m-8m CRM/ESB needs to c
BMPCluster+BMPDB+BMPGateway GDR BMPGateway IP ad
switchover flow BMPGateway of sit
duration depends o
capability, we assum
finished in 5m
7/17/2019
Data Loss - Oracle Physical DB Huawei CBS a-A GDR Solution
Redo Log Data loss: = Data latency

The data is replicated to the disk and (WAN:0.4 ) * Broadband width (e.g.
redundancy node near real time. The Data latency: < 1-2s, generally less t
latency depends on network
efficiency.
During switchover, the redo log will b
No Data Loss.
BMP Production Node BMP Redundancy Node
Active
Active (Read-
write )
Physic Redo
al DB Log
Disk Disk
7/17/2019
Data Loss - GMDB (i.e. CBP memory database Huawei CBS a-A GDR Solution
Data Loss = from GMDB to Buffer (<

Every 1s or 1M bytes data, buffer Redundancy Node.
sends data to standby host / disk / Buffer to Redundancy Node = Data
redundancy node. The copy speed
depends on network efficiency.
efficiency (WAN:0.4 ) * Broadband w
Data latency: < 1-2s, generally less t
CBP/CBPAdapter Production Node CBP/CBPAdapter Redundancy
Active Standby Standby
Buffer
GMDB (Log)
Disk Disk
7/17/2019
Performance Impact Huawei CBS a-A GDR Solution
 CBPAdapter: The AA system performance impact is estimated around 15% compared with
solution.
 CBP: The AA system performance impact is estimated around 15% compared with without
 OCG(SEE): The AA system performance impact is estimated around 15% compared with wit
 BMP: The AS system performance impact is estimated around 10% compared with without
7/17/2019
Requirement on Dimensioning Huawei CBS a-A GDR Solution
For A-A DR solution,

1. License for Oracle GoldenGate is needed for physical DB, including BMPDB(SYSDB), USRD
BillDB.
This data replication software allows physical DB in DR site to be opened read-write whil
•
synchronization occurs. But currently, the physical DB in DR site keeps read only.
It allows one way data replication and two-way data replication.
•
It provides scheme based data replication, that is, one DB can be divided to two scheme
•
scheme, one way or two way data replication is adopted.

Huawei CBS 5.5 adopts scheme based one way data replication. But currently, one DB ju
•
scheme.
2. The bandwidth needs recalculation.
Thank you
www.huawei.com
Copyright©2015 Huawei Technologies Co., Ltd. All Rights Reserved.

The information in this document may contain predictive statements including, without limitation, stateme
future financial and operating results, future product portfolio, new technology, etc. There are a number of
cause actual results and developments to differ materially from those expressed or implied in the pred
Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an a
may change the information at any time without notice.

Huawei CBS V500R005C30: Active-Active Disaster Recovery Solution

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei CBS V500R005C30: Active-Active Disaster Recovery Solution

Uploaded by

Copyright:

Available Formats

7/17/2019 Huawei CBS a-A GDR Solution

Huawei CBS V500R005C30

Active-Active Disaster Recovery Solution

HUAWEI TECHNOLOGIES CO., LTD.

Site A (Main Site) BMP BMP Site B

GMDB GMDB GMDB GMDB

SEE SEE SEE SEE

See next page for Architecture in Low Level

2. BMP Custer 1 is Active while BMP Cluster 2 is Standby.

2. Calling & Data Usage & Other Service

CBP: Convergent Billing Point

GMDB: General Memory Database

OCG: Online Control and Charging Gateway

SEE: Service Execution Environment

DR Deployment Scheme -1/2

NE Type Mode Site 1 (Main Site) Site 2 Auto/Ma Remark

CDRDB, BillDB A-S Two-node cluster traffic)

Site A (Main Site) Site B

Site A (Main Site) BMP BMP Site

write write write

3. Update (remote change)

 There is routing table in CBPAdapter(GMDB), so it can know which CBP to route.

GMDB GMDB GMDB GMDB

CBP1 CBP2 CBP3 CBP4

MSC STP USAU1 SEE SEE USAU2

GDR switchover duration: 3s

In case of Manual The GDR software:

Site A (Main Site) Site B

SEE SEE SEE SEE

GDR switchover duration: 10s

In case of Manual The GDR software:

50% traffic 50% traffic

50% traffic 50% traffic

 USAU+OCG(SEE) are deployed in one DR switch group.

Scenario 4.1: When BMP1 in BMP Cluster 1 is down (i.e. number o

SEE SEE SEE SEE

SEE SEE SEE SEE

 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

SEE SEE SEE SEE

 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

Scenario 4.4: When BMPGateway is down, BMP Cluster 1+BMPDB

BMP Cluster 1 BMP Cluster 2

 BMP Cluster 1+BMPDB1+BMPGateway are deployed in one DR switch group.

GDR switchover duration: 3m-8m

change BMP Cluster IP

Summary Table of Switchover Duration of Different

Scenario Switchover Duration Remark

Scenario1: When CBP (APP2) is down 3s

Data Loss - Oracle Physical DB Huawei CBS a-A GDR Solution

Redo Log Data loss: = Data latency

BMP Production Node BMP Redundancy Node

Data Loss = from GMDB to Buffer (<

CBP/CBPAdapter Production Node CBP/CBPAdapter Redundancy

Active Standby Standby

For A-A DR solution,

scheme, one way or two way data replication is adopted.

Copyright©2015 Huawei Technologies Co., Ltd. All Rights Reserved.

You might also like