Upgrade unsupported DSE versions
Upgrades involving unsupported versions of DSE often require intermediate upgrades and significant reconfiguration efforts that add complexity and risk. In some cases, an in-place upgrade might be unreasonable or impossible.
Cross-cluster upgrades (recommended)
As an alternative to an in-place upgrade, you can deploy a new cluster with your desired DSE version, and then use the Zero Downtime Migration (ZDM) tools to orchestrate live traffic to both clusters while you copy your data to the new cluster. After you validate the data on the new cluster, you can safely decommission your current cluster.
With the ZDM tools, there is no need for intermediate upgrades, progressive reconfiguration, or management of mixed-version nodes. If you need to rollback, you can seamlessly discard the new cluster and continue using your existing cluster.
Minimum compatibility for ZDM starts at DSE 4.7.1 due to Cassandra native protocol support in ZDM Proxy.
In-place upgrade guides for unsupported versions
In-place upgrade guides are available on a limited basis for unsupported DSE versions.
All upgrades to unsupported versions, including intermediate upgrades, require access to the relevant software packages or tarball files. If your required version isn’t available for download, contact IBM Support.
| DSE version | Patch release | Upgrade to this version | Upgrade to a supported version |
|---|---|---|---|
DSE 6.7 |
Not available |
Not available |
|
DSE 6.0 |
|
||
DSE 5.0 |
|||
DSE 4.8 |
|
||
DSE 4.7 |
Not available |
|
|
DSE 4.0, 4.5, or 4.6 |
Not available |
Upgrade to DSE 4.7 or 4.8, then follow subsequent upgrade paths |
|
Earlier versions |
Not available |
Upgrade to DSE 4.0, 4.5 or 4.6, then follow subsequent upgrade paths |
