Figure 1-6 Remote replication without using a consistency group
Secondary storage
system
Remote replication
session 01
Remote replication
session 02
Remote replication
session 03
Primary storage
system
Remote replication
session 01
Remote replication
session 02
Remote replication
session 03
Remote replication
session 01
Remote replication
session 02
Remote replication
session 03
Primary
LUN01
Primary
LUN02
Primary
LUN03
Primary
LUN01
Primary
LUN02
Primary
LUN03
Primary
LUN01
Primary
LUN02
Primary
LUN03
Secondary
LUN01
Secondary
LUN02
Secondary
LUN03
Secondary
LUN01
Secondary
LUN02
Secondary
LUN03
1. No consistency group is created.
2. A task failure causes data
inconsistency.
3. Data becomes invalid.
· Data, log, and change tracking
information of a database are
respectively stored on primary
LUN01, primary LUN02, and
primary LUN03.
· No consistency group is
created on the primary storage
system.
· During synchronization,
remote replication session 02
fails due to a fault.
· Remote replication sessions
01 and 03 succeed. As a
result, data in the primary
storage system becomes
inconsistent with that in the
secondary storage system.
· After the remote replication
session failure, the secondary
storage system recovers data
in the primary storage system,
but data in the primary
storage system is still
unusable because the three
primary LUNs store data at
different points in time.
Before data
replication
Data replication
Data recovery
Phases in a process of data becoming invalid
Secondary
LUN02
Secondary
LUN01
Secondary
LUN03
Remote Replication Using a Consistency Group
If associated LUNs are added to a consistency group, data unavailability is prevented as
shown in Figure 1-7.
OceanStor V3 Series
Remote Replication Feature Guide for Block
1 Feature Description
Issue 06 (2018-01-30) Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
18
To Next Page
Loading...
