Replication Pair

Overview

A Replication Pair is similar in concept to a Subclient which are used by other Agents; it maps a designated set of data on a source computer to a location on a destination computer, for the purpose of monitoring changes on the source and replicating the changes to the destination computer. A single Replication Pair can be configured to replicate all the data on a source computer, or multiple Replication Pairs can be created, allowing more granular control of data.

When creating a Replication Pair, and selecting the source and destination paths for replication, consider the following:

An absolute location on the destination computer, e.g., a directory such as H:\replication\, used as a destination path for one Replication Pair, may not be used by any other Replication Pair, even one in a different Replication Set; however, other Replication Pairs can use subdirectories of that one as their destination path, e.g., H:\replication\pair2\.
When source data contains stubs from a data migration, the stubs themselves will be replicated, and not the actual data which has been migrated.
For a Replication Pair with the Automatically detect mount points option selected, for each mount point in the specified directory or volume, an additional, separate Replication Pair will be automatically created and its source path marked with an asterisk ("*") at the beginning to indicate it is a mount point.
Replication pairs with the Engage All VSS Writers option selected in the Manage Pairs dialog box, engages all available VSS writers during backup, ensuring the consistency of backup data.
The source path cannot be a mapped network drive.
For Windows, a UNC path can be used as a destination. For data replication to succeed, the destination computer must have permissions to the location pointed to by the UNC path. Note that the UNC path can be to a NetApp file server; for more information.
When selecting a destination folder for a Replication Pair, ensure that the selected path does not contain any data as the existing data will be pruned during Orphan File processing.

For step-by-step instructions, see Add or Edit a Replication Pair.

Replication Pair Conflicts

Certain Replication Pair combinations are not possible, or are only possible using different Replication Sets. The following table highlights the most common such cases.

Type of Combination or Conflict	Windows		UNIX		Examples Note that (A), (B), (C) in the examples represent different computers
Type of Combination or Conflict	Same Replication Set	Different Replication Sets	Same Replication Set	Different Replication Sets
Exact same destination path	No	No	No	No	Windows: (A) D:\test => (B) E:\test (A) F:\test => (B) E:\test UNIX: (A) /test/pair => (B) /mount/pair (A) /home/path => (B) mount/pair
Child/parent destination paths	No	No	No	No	Windows: (A) D:\test => (B) E:\test (C) F:\test => (B) E:\test\test1 - - - - - - (A) D:\test => (B) E:\test (C) F:\ => (B) E:\ UNIX: (A) /test/pair => (B) /mnt/parent (A) /test/mnt => (B) /mnt/parent/abc
Source path same as destination (volumes are on different computers)	N/A	Yes	N/A	Yes	Windows: (A) D:\test => (B) D:\test (C) D:\test => (B) E:\test UNIX: (A) /test/pair => (B) /test/pair (A) /test/lot => (B) /test/lot
Same destination path on multiple computers	N/A	Yes	N/A	Yes	Windows: (A) D:\test => (B) D:\test (A) D:\test => (C) D:\test UNIX: (A) /test/pair => (B) /test/pair (A) /test/pair => (C) /test/pair
Same destination volume, different folders	Yes	Yes "Allow Recovery Points" option must be disabled	Yes	Yes	Windows: (A) D:\test => (B) D:\test (C) E:\data => (B) D:\test1 UNIX: (A) /secured => (B) /dest/secure (C) /plain => (B) /dest/plain
Source volume can also be destination volume; destination volume can also be source volume	No	No	Yes	Yes	Windows: (A) D:\test => (B) E:\test (C) F:\test => (A) D:\test - - - - - - (A) D:\test => (B) D:\test (C) D:\data => (A) D:\data - - - - - - (A) D:\test => (B) D:\test (B) D:\test => (C) E:\data - - - - - - (A) D:\test => (B) D:\test (B) D:\data => (C) E:\data UNIX: (A) /test => (B) /dest (B) /send => (A) /test - - - - - - (A) /one => (B) /two (B) /two => (C) /four
Same source path in multiple pairs	No	Yes	Yes	Yes	Windows: (A) D:\test => (B) D:\test (A) D:\test => (C) E:\test UNIX: (A) /source => (B) /dest (A) /source => (B) /dest2 (A) /source => (C) /dest
Source parent folder already used (Nested mount point is not supported.)	No	Yes with warning that the new pair will change to the parent path	Yes	Yes	Windows existing: (A) D:\ => (B) D:\ Windows new: (A) D:\data => (B) E:\data UNIX existing: (A) /test/source => (B) /test UNIX new: (A) /test/source/one=> => (B) /test2
Source child folder already used	No	No	Yes	Yes	Windows existing: (A) D:\data => (B) E:\data Windows new: (A) D:\ => (B) D:\ UNIX existing: (A) /test/source => (B) /folder1 UNIX new: (A) /test => (B) /new