The source appliance replicates snapshots atomically to the target, meaning the contents of the replica always exactly matches the source's share at the time the snapshot was taken. Because the snapshots for all shares sent in a particular group are taken at the same time, the entire package contents after the completion of a successful replication update exactly matches the group's content when the snapshot was created on the source.
However, each share's snapshots are replicated separately, so it is possible for some shares within a package to have been updated with a snapshot that is more recent than those of other shares in the same package. This is true during a replication update and after a failed replication update.
To summarize:
Each share is always point-in-time consistent on the target.
When no replication update is in progress and the previous replication update succeeded, each package's shares are also point-in-time consistent with each other.
When a replication update is in progress or the previous update failed, package shares may be inconsistent with each other, but each one will still be self-consistent. If package consistency is important for an application, one must clone the replication package, which always clones the most recent successfully received snapshot of each share.
Related Topics