IN THIS ARTICLE
This article outlines the version requirements and upgrade recommendations for clusters that run Qumulo Core.
Replication creates a copy of the data in a directory on your cluster and transfers it to a directory on a second target cluster. This process generates a consistent point-in-time copy of the source directory on the target cluster.
Because two clusters are required for this feature, there are specific version requirements and upgrade considerations depending on what version of Qumulo Core you run on either cluster.
Replication for Qumulo Core 5.0.1 (and Higher)
Important: From version 5.0.1, Qumulo Core blocks replication between unsupported versions. For example, version 5.0.1 can't replicate with releases before 4.3.0 or after 5.2.0.
Qumulo Core 5.0.0 (and higher) supports replication between the current cluster version and up to two previous or future quarterly releases.
- This example shows quarterly releases with your current cluster version at 5.1.0.
4.3.0 (q) ← 5.0.0 (q) ← 5.1.0 (q) → 5.2.0 (q) → 5.3.0 (q)
- This example shows non-quarterly releases with your current cluster version at 5.1.1.
5.0.0 (q) ← 5.1.0 (q) ← 5.1.1 → 5.2.0 (q) → 5.3.0 (q)
Replication for Qumulo Core 2.11.0 to 5.0.0
From Qumulo Core 2.11.0 to 5.0.0, clusters that use different software versions can use replication between at least 2 consecutive quarterly releases.
The following table illustrates replication between Qumulo Core versions 4.1.0 to 5.0.0. Cells marked with an x are compatible.
Replication for Qumulo Core 2.10.x (and Lower)
To use replication with earlier versions of Qumulo Core, the source and target cluster must be running the same version of Qumulo Core 2.7.3 (or higher).
Important: If the clusters run different versions of Qumulo Core, replication fails.
If you create a replication relationship with a target directory path that specifies the file system root directory (Qumulo Core 2.12.0 and higher supports this), you must follow specific recommendations for upgrading your cluster.
Note: Regardless of version, upgrading Qumulo Core while a replication job runs interrupts the job in progress. When both clusters return to a state in which replication is possible, the job resumes.
Because the target directory of an existing replication relationship is read-only to all client access, upgrading a cluster whose file system root directory is the target of a replication relationship has the following requirements.
If the Source Cluster is Available
To avoid having to resynchronize your clusters after the relationship is reconnected, we recommend the following steps.
- Copy the upgrade image to a directory on the source cluster (you can't copy it to the read-only target cluster).
- Wait for the upgrade image to replicate to the target cluster.
- Continue with the normal upgrade process.
If the Source Cluster is Unavailable or Another Issue Exists
The following process interrupts the replication process. On clusters that run Qumulo Core 2.12.5 (and lower), it also requires additional time to resynchronize the clusters by running a full-tree scan after you reconnect the relationship.
- To temporarily make the target relationship writable for the duration of the upgrade, use the Make Target Writable action in the Web UI.
- Wait for the upgrade to complete.
- Re-establish the relationship by using the Reconnect Relationship action. Note that this will interrupt replication for the duration of the process.
Like what you see? Share this article with your network!