This section explains the relationship between the version of Qumulo Core that a cluster runs and data replication between it and other clusters. It also gives recommendations for upgrading Qumulo Core in relation to data replication tasks.
The replication process creates a consistent point-in-time copy of data in a directory on a source cluster when Qumulo Core transfers the data to a directory on a target cluster. Because two clusters are required for the replication process, there are specific requirements for version of Qumulo Core that the two clusters must run.
Replication for Qumulo Core 6.0.0.x (and Higher)
For Qumulo Core 6.0.0.x (and higher), clusters that run different versions can replicate with all quarterly and non-quarterly versions, up to eight quarters in the future.
The following example shows a replication compatibility matrix for quarterly and non-quarterly version of Qumulo Core.
| 6.0.0.x (q) | 6.0.1 | 6.1.0 (q) | … | 8.0.0 (q) | 8.0.1 | … | 10.0.0 (q) | 10.0.1 | |
|---|---|---|---|---|---|---|---|---|---|
| 6.0.0.x (q) | ✅ | ✅ | ✅ | ✅ | |||||
| 6.0.1 | ✅ | ✅ | ✅ | ✅ | |||||
| 6.1.0 (q) | ✅ | ✅ | ✅ | ✅ | ✅ | ||||
| … | |||||||||
| 8.0.0 (q) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ | |||
| 8.0.1 | ✅ | ✅ | ✅ | ✅ | |||||
| … | |||||||||
| 10.0.0 (q) | ✅ | ✅ | ✅ | ✅ | |||||
| 10.0.1 | ✅ | ✅ |
The following example shows replication options for a cluster running the quarterly (future) 8.0.0 version.
6.0.0.x (q) ➤ 6.1.0 (q) ➤ … ➤ 7.2.0.2 (q) ➤ 7.3.0 (q) ➤ 8.0.0 (q) ➤ 8.1.0 (q) ➤ 8.2.0 (q) ➤ … ➤ 9.3.0 (q) ➤ 10.0.0 (q)
The following example shows replication options for a cluster running the non-quarterly (future) 8.0.1 version.
6.1.0 (q) ➤ 6.1.0 (q) ➤ … ➤ 7.2.0.2 (q) ➤ 7.3.0 (q) ➤ 8.0.1 ➤ 8.1.0 (q) ➤ 8.2.0 (q) ➤ … ➤ 9.3.0 (q) ➤ 10.0.0 (q)
This schema doesn’t impact replication compatibility for versions lower than 6.0.0 that are still only compatible with a maximum of two quarterly versions.
Replication for Qumulo Core 5.0.1 to 6.0.0
From Qumulo Core 5.0.1 to 5.3.4, clusters that run different versions can replicate between the current version and up to two previous or future quarterly versions.
The following example shows replication options for a cluster running the quarterly 5.1.0 version.
4.3.0 (q) ➤ 5.0.0 (q) ➤ 5.1.0 (q) ➤ 5.2.0 (q) ➤ 5.3.0 (q)
The following example shows replication options for a cluster running the non-quarterly 5.1.1 version
5.0.0 (q) ➤ 5.1.0 (q) ➤ 5.1.1 ➤ 5.2.0 (q) ➤ 5.3.0 (q)
- From version 5.0.1, Qumulo Core blocks replication between unsupported versions. For example, version 5.0.1 can't replicate with versions before 4.3.0 or after 5.2.0.
- In this scenario, version 5.2.0 is a hard limit. Versions 5.2.1 (and higher) can't replicate with versions 5.0.1 (or lower).
Replication for Qumulo Core 2.11.0 to 5.0.0
From Qumulo Core 2.11.0 to 5.0.0, clusters that run different versions can replicate between at least two consecutive quarterly versions. For example:
| 4.1.5 | 4.2.0 (q) | 4.2.1 | |
|---|---|---|---|
| 4.1.5 | ✅ | ✅ | |
| 4.2.0 (q) | ✅ | ✅ | ✅ |
| 4.2.1 | ✅ | ✅ |
Upgrade Recommendations
Because the target directory of an existing replication relationship is read-only to all client access, use the following recommendations to upgrade a cluster whose file system root directory is the target of a replication relationship.
Regardless of version, upgrading Qumulo Core while a replication job is running interrupts the job in progress. When both clusters return to states in which replication is possible, the replication job resumes.
If the Source Cluster is Available
To avoid having to resynchronize your clusters after you reconnect the replication relationship, we recommend the following steps.
-
Copy the upgrade image to a directory on the source cluster. (It isn’t possible to 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 steps interrupt the replication process.
On clusters that run Qumulo Core 2.12.5 (and lower), this process requires additional time to resynchronize the clusters by running a full-tree scan after you reconnect the replication relationship.
-
To temporarily make the target relationship writable for the duration of the upgrade, use the Make Target Writable action in the Qumulo Core Web UI.
-
Wait for the upgrade to complete.
-
Use the Reconnect Relationship action in the Qumulo Core Web UI.