IN THIS ARTICLE
Outlines the version requirements and upgrade recommendations for clusters utilizing replication in Qumulo Core
REQUIREMENTS
- Source and target cluster running Qumulo Core 2.7.3 or above
DETAILS
Replication creates a copy of the data in a directory on your cluster and transfers it to a directory on a second target cluster to generate a point-in-time consistent 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 dependent on what version of Qumulo Core you are running on either cluster.
Qumulo Core Version Requirements with 2.11.0 or above
Starting with Qumulo Core 2.11.0, clusters using different software versions can still use replication, up to and including the previous and subsequent quarterly release. For example, a quarterly release like 2.12.0 can replicate with any version of software from 2.11.0 (the previous quarterly) to 2.13.0 (the subsequent quarterly). A non-quarterly release like 2.11.4 can replicate with any version from 2.11.0 to 2.12.0.
Use the table below to identify replication compatibility between releases. Cells marked with an 'x' are compatible; cells that are blank are not.
| 3.1.0 | 3.1.1 | 3.1.2 | 3.1.3 | 3.1.4 | 3.1.5 | 3.1.6 | 3.2.0 | 3.2.1 | 3.2.2 | 3.2.3 | 3.2.4 | 3.2.5 | 3.3.0 | 3.3.1 | 3.3.2 | |
| 3.0.0 | x | |||||||||||||||
| 3.0.1 | x | |||||||||||||||
| 3.0.2 | x | |||||||||||||||
| 3.0.3 | x | |||||||||||||||
| 3.0.4 | x | |||||||||||||||
| 3.0.5 | x | |||||||||||||||
| 3.1.0 | x | x | x | x | x | x | x | x | ||||||||
| 3.1.1 | x | x | x | x | x | x | x | x | ||||||||
| 3.1.2 | x | x | x | x | x | x | x | x | ||||||||
| 3.1.3 | x | x | x | x | x | x | x | x | ||||||||
| 3.1.4 | x | x | x | x | x | x | x | x | ||||||||
| 3.1.5 | x | x | x | x | x | x | x | x | ||||||||
| 3.1.6 | x | x | x | x | x | x | x | x | ||||||||
| 3.2.0 | x | x | x | x | x | x | x | x | x | x | x | x | x | x | ||
| 3.2.1 | x | x | x | x | x | x | x | |||||||||
| 3.2.2 | x | x | x | x | x | x | x | |||||||||
| 3.2.3 | x | x | x | x | x | x | x | |||||||||
| 3.2.4 | x | x | x | x | x | x | x | |||||||||
| 3.2.5 | x | x | x | x | x | x | x | |||||||||
| 3.3.0 | x | x | x | x | x | x | x | x | x | |||||||
| 3.3.1 | x | x | x | |||||||||||||
| 3.3.2 | x | x | x |
Qumulo Core Version Requirements with 2.10.x and below
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 above. Replication will fail if either cluster is on a different version.
Upgrade Recommendations
No matter what version either cluster is currently running, upgrading Qumulo Core while a replication job is running will interrupt the job in progress. Once both clusters return to a state where replication is supported, the job will resume.
There are specific recommendations regarding upgrades if you create a replication relationship with a target directory path specifying the file system root (supported in 2.12.0 or above). Since the target directory of an established replication relationship is read-only to all client protocol access, upgrading a cluster whose file system root directory is the target of a replication relationship requires the following:
- If the source cluster is available: Copy the upgrade image to a directory on the source cluster (copying it to the read-only target cluster is not allowed) and wait for the upgrade image to be replicated to the target cluster before proceeding with the documented Web UI or CLI upgrade process
- If the source cluster is unavailable or this is not possible for some reason: Temporarily make the target relationship writable for the duration of the upgrade using the “Make Target Writable” action in the Web UI, and then re-establish the relationship using the “Reconnect Relationship” action after the upgrade completes. Note that this will interrupt replication for the duration of the process. On clusters running Qumulo Core 2.12.5 or below, it will also require additional time to resynchronize the clusters using a full-tree scan after the relationship is reconnected.
IMPORTANT! The first option is recommended whenever possible to avoid having to resync the clusters after a relationship is reconnected.
RESOLUTION
You should now be able to successfully understand the version requirements and upgrade recommendations with replication in Qumulo Core
ADDITIONAL RESOURCES
Replication: Continuous Replication with 2.11.2 and above
Replication: Continuous Replication with 2.11.1 and below
Like what you see? Share this article with your network!
Comments
0 comments
Please sign in to leave a comment.