Print Email PDF

Replication: Continuous Replication with 2.11.1 and below


Outlines how to utilize Continuous Replication with Qumulo Core 2.11.1 and below

  • Replication Page Overview
  • Create a Replication Relationship
  • Authorize a Replication Relationship
  • Replicating
  • Edit or Delete a Replication Relationship
  • Additional Considerations


  • Admin privileges required
  • Source and target cluster running the same version of Qumulo Core 2.7.3 to 2.11.1 on any model of Qumulo hardware, including HPE

We highly recommend upgrading to the latest version of Qumulo Core to fully utilize Continuous Replication with the additional improvements in functionality and performance we've implemented since the original release. 


Continuous Replication takes a snapshot of the data in a directory on your cluster and transfers it to a directory on a second target cluster. While a replication job is running, Qumulo Core takes the latest changes and replicates them without the worry of scheduling them into an existing job. And with the help of snapshots, a point-in-time consistent copy of the source directory is generated on the target cluster.

In Qumulo Core 2.9.2 and above, incremental replication jobs will no longer resend the entire file contents when only part of a file has changed. The replication engine will scan modified files for any changed regions and only send those changes over to the target so that job runtime is proportional to the amount of data changes made. With this change, the throughput statistics in the Replication Job Details UI only include data actually transferred. Unmodified data that does not need to be transferred is reported as “Unchanged”. 

NOTE: The initial replication job after installing 2.9.2 will still send the entire file and the first job may fall back to resending the entire file if the relationship hasn’t completed a job since being upgraded to 2.8.8 or later.

Replication Page Overview

In the Web UI, hover over the Cluster menu on the Source Cluster and select Replication under the Configurations section in the dropdown.


A list of Replication relationships will display with the following details:


Status (#): represents the current status of each relationship including Replicating, Blackout Window, Awaiting Authorization, etc. and displays the number of relationships

Source: specifies the file path of the source directory

Target: specifies the file path of the target directory

Role: indicates whether the cluster is serving in the role of a source or target directory for that particular relationship

Last Attempt: states whether the last replication attempt completed or failed

Recovery Point: displays a timestamp from the last successful Replication on the source cluster and represents the time Qumulo Core took a snapshot of the source directory and started moving data across to the target

Continuous Replication: displays whether the relationship is enabled or disabled

Create a Relationship for Replication

  1. Click the Create Relationship button on the replication page of the Source cluster .


  2. Fill in the following fields:
    • Source Directory Path: path of the existing directory you wish to replicate
    • Target Directory Path: path of existing empty directory on the target cluster where you wish to replicate data
    • Target Address: one of the IP (preferably floating IP) addresses from a node on the target cluster
    • Port Number: select the default port option 3712 or create a custom port configuration

    NOTE: Custom port configuration may be necessary to meet enterprise network firewall rules. To override, select the Custom radio button and enter the port number. For questions on custom port configuration, reach out to Qumulo Care for additional information.


  3. Verify that Continuous Replication Enabled is On

  4. Click Add Blackout Window.
  5. Select the day(s) or times to suspend replication between the source and target directories.


    • To add up to 10 additional blackout windows, click the +Add Blackout Window button
    • For additional details, check out the Replication: Blackout Windows article
  6. Click Save Relationship.  

The relationship will now be available on the replication page where you can see the status and manage the replication job. A replication job will not start until the relationship has been authorized on the Target cluster. Continue on to the next section for steps on how to Authorize a Replication Relationship.

Authorize a Replication Relationship

  1. Log on to the Target cluster.
  2. Click See Details on the authorization request notification banner.


  3. Click Accept on the replication page to authorize the relationship. 

IMPORTANT! Replication will not start if you are currently in a blackout window or if Continuous Replication for that relationship is disabled.


While a replication job is running, a progress bar will display on the replication page under the status column. Note that the percentage reflects both the number of files to be moved as well as the amount of data to be transferred and is not based solely on the amount of data being replicated.


Click on the Details option to review the Throughput, Run Time, and Data statistics of the current job in progress. Files that have not changed since the previous replication job will be reflected in the Unchanged column and will not be transferred. 


NOTE: Qumulo Core versions 2.7.9 and below will display "Replicating" in the status column until the replication job completes. The Details page and Progress bar are not available in these previous releases.

Edit or Delete a Replication Relationship

  • To Edit an existing Replication relationship, click the pencil icon next to the job on the Source cluster

Note that you cannot edit the source and target directory paths. To make these changes, you must create a new relationship.


  • Delete a relationship by clicking the trashcan icon on either the Source or Target cluster and confirm by selecting Yes, Delete when prompted


Additional Considerations

  • Upgrading Qumulo Core while a replication job is running will cause the job in progress to fail. Once both clusters return to a state where replication is possible (same version), Continuous Replication can resume. Please wait until after the replication job completes to perform any upgrades.
  • Utilizing Continuous Replication will increase load on the cluster and may cause latency delays depending on the applications in use while a job is running. 
  • At the beginning of a replication job, a snapshot is created for the directory. The old snapshot is programmatically deleted when it is no longer needed. There will be one reference snapshot used for replication on the cluster at all times. Admins can view the snapshot(s) used for replication along with other policy-based snapshots.
  • A snapshot is taken of the directory on the target cluster at the conclusion of each successful job. The previous snapshot is then deleted so the directory always contains only the most recent snapshot. 
  • Target directory permissions will be updated from read/write to read-only when a replication relationship is created. If the relationship is deleted, the permissions will revert to read/write automatically.
  • A replication relationship that includes the root directory of the target cluster is not permitted. Including the root directory makes the entire target cluster read-only and may prohibit administrative functions such as upgrades.
  • Continuous Replication does not support replicating local user or group information and will fail if it encounters a file associated with local users or groups.
  • Qumulo Core supports up to 100 replication relationships.


You should now be able to successfully configure and manage Continuous Replication in Qumulo Core 2.11.1 and below


Replication: Continuous Replication with 2.11.2 and above

Replication: Failover and Failback with 2.11.4 and below

Replication: Failover and Failback with 2.12.0 and above

Replication: Version Requirements and Upgrade Recommendations

Replication: Blackout Windows

QQ CLI: Replication


Like what you see? Share this article with your network!

Was this article helpful?
0 out of 0 found this helpful



Please sign in to leave a comment.

Have more questions?
Open a Case
Share it, if you like it.