DSE migration toolkit
The DataStax Enterprise (DSE) migration toolkit includes the DataStax migration tools that you can use to migrate your data across DSE and another Apache Cassandra®-based database, such as Astra DB or HCD.
This documentation doesn’t describe all possible migration paths; it focuses on migrations using DataStax migration tools like ZDM Proxy.
|
Whenever possible, DataStax recommends using the Zero Downtime Migration (ZDM) tools when you need to maintain live traffic for your applications while transferring data. This is most relevant for full-scale platform migrations where you move your data and switch your applications to connect to your new databases. The ZDM tools orchestrate and synchronize read/write requests while you use a data migration tool to copy data from one cluster to the other. Then, you can take as much time as you need to validate the data and simulate production workloads on your new cluster before updating your application code to use the new databases. For information about clusters that support the ZDM tools, including supported DSE versions, see Cluster compatibility for Zero Downtime Migration. |
Migrate your data
The tools and process for data migration to or from DSE depends on your DSE version and the other database’s platform or version.
-
Migrate data to DSE
-
Migrate data from DSE
The following information provides guidance on migrations to DSE, with a focus on data transfer tools:
Generally, DataStax recommends migrating to the latest version of DSE, unless you have a specific functional requirement or a compatibility issue that requires migrating to an earlier version.
When migrating from DSE to another Cassandra-based database, follow the migration guidance for your target database to determine cluster compatibility, migration options, and recommendations. For example, for Astra DB, see Astra migration toolkit, and for HCD, see HCD migration toolkit.
For information about source and target clusters that are supported by the ZDM tools, see Cluster compatibility for Zero Downtime Migration.
If your target database isn’t directly compatible with a migration from DSE, you might need to take interim steps to prepare your data for migration, such as upgrading your DSE version, modifying the data in your existing database to be compatible with the target database, or running an extract, transform, load (ETL) pipeline.
Migrate your code
In the case of a platform migration where you want to shift your applications to use your new databases, migrate your data first, and then update your client applications to connect exclusively to the new databases.
If you are already using a compatible Cassandra driver, you can modify the driver connection string to connect to the new databases. For some migrations, changing the connection string might be the only change you need to make to your code. However, you might want to update your code to take advantage of features and improvements available in your new database platform or a newer driver version.
For database-specific connection information, see the documentation for your target database and version.
Get support for your migration
If you have questions about your DSE migration, contact your DataStax account representative or DataStax Support.
