White Papers

13 PS Series Asynchronous Replication Best Practices and Sizing Guide | BP1012
3.3 Between replication events (repeating)
Once first replication has occurred, the system continues to keep track of volume data changes that occur so
that subsequent replication processes can copy those changes to the replica set. This tracking process does
not consume additional space.
Configure
replication partnership
Configure
volume replication
BEGIN
Replication transfer processing
First replication?
YES
NO
Replica reserve in
secondary group receives
copy of entire volume
Replica set in secondary group
receives copy of all primary volume
data changes that occurred between
beginning of last replication to
beginning of this replication
Is fast failback
recovery enabled
on primary volume?
YES
END
Replication transfer processing
YES
Replication
setup
Replication
processing
Between
replication
events
All changes to the primary volume are
tracked for the next replication cycle,
including changes that occurred during the
previous replication cycle.
Create a new hidden snapshot
of primary volume
 Designate primary and secondary group relationship
 Set delegated space size in secondary group
 Select replication partner (secondary) group
 Set local reserve %
 Set replica reserve % (using delegated space on secondary group)
 Set fast failback recovery (optional)
 Set allow temporary use of free pool space (default is enabled)
Retain hidden snapshot for
failback recovery
Is fast failback
recovery enabled
on primary volume?
Space consumed by current
hidden snapshot is released and
returned to local reserve. Pointers
to the updates captured by the
hidden snapshot are retained for
next replication cycle.
Delete old failback snapshot.
Retain current hidden snapshot
for use in failback recovery
NO
Replication process