Cluster compatibility for Zero Downtime Migration
True zero downtime migration is only possible if your database meets the minimum requirements described in Compatibility requirements for ZDM Proxy, including compatibility of the origin (source) and target (destination) clusters.
Compatible origin and target clusters for migrations with zero downtime
You can use ZDM Proxy to support migrations between Astra, DataStax Enterprise (DSE), Hyper-Converged Database (HCD), open-source Apache Cassandra®, and and other Cassandra-based databases. Supported migration paths include cross-platform migrations and same-platform upgrades.
DataStax tests ZDM Proxy compatibility with Astra, DSE, HCD, and open-source Cassandra. Support for other Cassandra-based databases is possible if the origin and target clusters share a common protocol version. However, DataStax doesn’t test all data store providers, and DataStax doesn’t guarantee full support for any specific data store aside from the platforms and versions listed here.
- Compatible origin clusters
-
Migrate from one of the following:
-
Astra DB Serverless or Astra Managed Clusters (Astra DB Classic).
-
Hyper-Converged Database (HCD).
-
DataStax Enterprise (DSE) version 4.7.1 and later.
-
Apache Cassandra® version 2.1.6 and later.
ZDM Proxy requires that the origin and target clusters share a common protocol version. Therefore, Cassandra 2.0 migrations are only possible when migrating to 2.1 or 2.2 because Cassandra 2.0 supports only
v2. -
Other Cassandra-based databases that are based on a compatible Cassandra version, such as ScyllaDB and Yugabyte.
-
- Compatible target clusters
-
Migrate to one of the following:
-
Astra DB Serverless or Astra Managed Clusters (Astra DB Classic).
For more Astra DB migration paths, see Astra migration toolkit.
-
HCD.
-
DSE, if the cluster is running the same or later version as the origin cluster.
-
Cassandra, if the cluster is running the same or later version as the origin cluster.
-
|
You can use ZDM for major version upgrades to your current database platform, such as upgrades from DSE 5.0 to DSE 6.9. Using ZDM reduces the risk of data loss or corruption due to breaking changes between versions, provides a seamless rollback option, and streamlines the upgrade process, eliminating the need for interim upgrades and progressive manual reconfiguration. |
Incompatible clusters and migrations with some downtime
If you don’t want to use ZDM Proxy or your databases don’t meet the zero-downtime requirements, you can still complete the migration, but some downtime might be necessary to finish the migration.
If your origin cluster is incompatible with ZDM Proxy, ZDM Utility, and ZDM Proxy Automation, you might be able to use standalone data migration tools such as DSBulk Migrator or a custom data migration script. Make sure you transform or prepare the data to comply with the target cluster’s schema.
For more complex migrations, such as RDBMS-to-NoSQL migrations, it is likely that your migration will require downtime for additional processing, such as extract, transform, and load (ETL) operations. For example, see the data modeling and compatibility considerations for migrating to DSE.
DataStax recommends that you contact your DataStax account representative or DataStax Support for guidance on incompatible or partially compatible migrations.
