Data Domain: Configuring Collection Replication in DDOS 5.0 and Later Versions

Summary: Configuring Collection Replication in DDOS 5.0 and later.

This article applies to This article does not apply to This article is not tied to any specific product. Not all product versions are identified in this article.
Check out other resources

Symptoms

This article describes the initial setup for a collection replication pair. In a collection replication pair, the destination system is an exact copy of the source, including all user account and password information.

Cause

Collection replication performs whole-system mirroring in a one-to-one topology, continuously transferring changes in the underlying collection, including all the logical directories and files of the Data Domain file system.

Collection replication does not have the flexibility of the other types, but it can provide higher throughput and support more objects with less overhead, which may work better for high-scale enterprise cases.

Collection replication replicates the entire /data/col1 area from a source Data Domain system to a destination Data Domain system.

Resolution

Below are the steps to Configure Collection Replication in DDOS 5.0:

On the DESTINATION system:

  1. Run the filesys destroy command to completely empty any existing file system constructs.
  2. Run the filesys create command on the destination system to create a fresh file system.
  3. Run the hostname command on both the source system and the destination system to identify each hostname. For Example: sysadmin@abc
# hostname Hostname: abc.tech.local
  1. The replication command is case-sensitive. Copy the name exactly as displayed. Errors in case, fully qualified domain names, and host names prevents replication from working.
  2. Run the replication add command on the Data Domain system with the form:
replication add source col:// <source> destination <destination>
Where <source> and <destination> indicate the type of replication, the directory path to follow, and the host names.
For example, the command to add a Collection Replication context is: sysadmin@abc 
# replication add source col://abc.tech.local destination col://abc.tech.local
  1. Run the filesys enable command to enable the file system.

On the SOURCE system:

  1. Run the filesys disable command.
  2. Run the same replication add command that was run on the destination on the source Data Domain system:
replication add source col:// <source> destination <destination>
For Example: sysadmin@abc 
# replication add source col://abc.tech.local destination col://abc.tech.local
  1. Run the filesys enable command to start the file system.
  2. Run the replication initialize command, on the source system only, to start replication.
replication initialize <destination>
For Example: sysadmin@abc 
# replication initialize rctx://0
  1. Verify the configuration by typing the following:
# replication show config

Note: In a collection pair, once replication has been established, the destination path can be substituted with rctx://0

For Example: 
replication show stats rctx://0

Note: If your issue persists after performing the steps in this article, contact your contracted support provider, upload a Support Bundle (see article Data Domain: How to collect and upload a support bundle (SUB) from a Data Domain Restorer (DDR) Log in to Dell Support is required to view article), and Create a service request.

Additional Information

Related articles:
(Log in to Dell Support is required to view these articles)


Ensure that both Source and Destination Data Domains can resolve the partner Data Domain hostnames and their own hostnames (use the # net lookup command) through DNS or through Hostname local resolution (by adding them manually). 

Each data domain should have two host entries, an entry for its own hostname and one for the replication partner. 

Check the hosts mapping with the command: 

# net hosts show 
# net hosts add <target IP> <target FQDN> <target hostname>

Example 

# net hosts add 192.168.3.3 bkup20.yourcompany.com bkup20

Ensure that both Source and Destination Data Domains can reach the remote peer Data Domain through TCP port 3009 as this is the port used to get the remote peer CA certificates. You check in SE mode

# se telnet <IP> 3009

Affected Products

Data Domain

Products

Data Domain
Article Properties
Article Number: 000060089
Article Type: Solution
Last Modified: 30 Oct 2024
Version:  4
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.