Migrate DataStax Installer installations

Support for the DataStax Installer ended with DSE 6.0.

If you installed an earlier version of DSE using the DataStax Installer, you must convert your installation to a tarball or package installation of the same version before upgrading to DSE 6.x.

Follow these instructions to convert a DataStax Installer installation to a DSE tarball or package installation. You might need to modify some steps or commands for your specific environment and version.

For assistance, contact IBM Support.

Migration process for cluster stability

You must perform this migration on every node in every cluster that uses the DataStax Installer. To avoid downtime, migrate one node at a time in the following order:

For multi-cluster deployments, migrate one cluster at a time.
For multi-datacenter clusters, migrate one datacenter at a time.
If using racks, migrate one rack at a time within a datacenter.
Within a datacenter (or rack), migrate one node at a time.

For each node, prepare to convert the installation, and then complete the appropriate installation-specific conversion steps. On production clusters that cannot tolerate downtime, ensure that each migrated node is healthy (Up/Normal status) and able to service queries for existing data before proceeding to the next node. Otherwise, start DSE after migrating all nodes in a cluster to verify that the installation runs as expected.

Because this process maintains the same DSE version, you don’t need to prioritize seed nodes or certain workload types like you would during an upgrade.
Repeat until you have migrated all nodes in all racks, datacenters, and clusters.

Prepare to convert your installation

Run dse -v to get your current DSE version, including the patch release number.

It is critical that you migrate to the same version as your existing installation, including the patch release.

For example, if your current version is DSE 5.1.11, you must migrate to a package or tarball installation of DSE 5.1.11 exactly. Changing versions can result in data loss, incompatible configuration files, and other issues.

Back up your entire DSE installation, including data (SSTable snapshots), logs, and configuration files, and then store these backup files in a separate directory from your DSE installation.

For instructions, see Back up and restore a DSE package installation or Back up and restore a DSE tarball installation.
After creating a backup, uninstall DSE 5.1 without removing your existing data and configuration files.

The migration will fail if you remove your existing data and configuration files.

Use the DataStax Installer to uninstall DSE 5.1. When prompted by the uninstaller, select the option to keep your data and configuration files in place.

Determine the type of installation that the DataStax Installer created, and then follow the appropriate conversion path:

Installation type Indicators Conversion path

Installation type	Indicators	Conversion path
Services installation	Typically created when you run the DataStax Installer with `root` permissions. With a services installation, you start DSE using the `service dse start` command.	Convert to the package installation type for your environment. When installed from a package (Yum or APT), DSE runs as a service. Convert to a Yum-managed package on RHEL-based systems Convert to an APT-managed package on Debian-based systems
No-services installation	Typically created when you run the DataStax Installer with custom directories or without `root` permissions. With a no-services installation, you start DSE with the `dse` command.	Convert to a tarball installation. When installed from a tarball, DSE runs as a stand-alone process.

Services installation

Typically created when you run the DataStax Installer with root permissions. With a services installation, you start DSE using the service dse start command.

Convert to the package installation type for your environment. When installed from a package (Yum or APT), DSE runs as a service.

Convert to a Yum-managed package on RHEL-based systems
Convert to an APT-managed package on Debian-based systems

No-services installation

Typically created when you run the DataStax Installer with custom directories or without root permissions. With a no-services installation, you start DSE with the dse command.

Convert to a tarball installation. When installed from a tarball, DSE runs as a stand-alone process.

Convert to a Yum-managed package on RHEL-based systems

Move your existing DataStax Installer backup directory to another location:
```
cd /usr/share/dse \
sudo mv backups backups.old
```
Install DSE with Yum at the same patch version that you verified previously.

For example, to install DSE 5.1.11:
```
sudo yum install dse-full=5.1.11-1 \
dse=5.1.11-1 dse-libsolr=5.1.11-1 dse-libtomcat=5.1.11-1 \
dse-liblog4j=5.1.11-1 dse-libcassandra=5.1.11-1 dse-libspark=5.1.11-1 \
dse-libgraph=5.1.11-1 dse-libhadoop2-client-native=5.1.11-1 \
dse-libhadoop2-client=5.1.11-1
```
Because you kept the existing configuration files in place when you uninstalled DSE with the DataStax installer, the Yum installation respects those files and they are used by the package-installed version of DSE.
Repeat this process until you have migrated all nodes in the recommended order.

Convert to an APT-managed package on Debian-based systems

Move your existing DataStax Installer backup directory to another location:
```
cd /usr/share/dse \
sudo mv backups backups.old
```

Configure and install DSE at the same patch version that you verified previously, modifying the apt-get install command to preserve your existing configuration files.

The migration will fail if you don’t include the Dpkg::options flags with apt-get install. These options keep the existing configuration files in place, and prevent them from being overwritten by the new packages.

Use the instructions in Install DataStax Enterprise (DSE) 5.1 on Debian-based systems with APT with the following modifications:

Add the following Dpkg::options to the apt-get install commands:

-o Dpkg::Options::="--force-confdef"
-o Dpkg::Options::="--force-confold"

List all packages with the same version as your previous installation. For example, to install DSE 5.1.11:

sudo apt-get -o Dpkg::Options::="--force-confdef" -o Dpkg::Options::="--force-confold" install \
dse-full=5.1.11-1 \
dse=5.1.11-1 dse-libsolr=5.1.11-1 dse-libtomcat=5.1.11-1 \
dse-liblog4j=5.1.11-1 dse-libcassandra=5.1.11-1 dse-libspark=5.1.11-1 \
dse-libgraph=5.1.11-1 dse-libhadoop2-client-native=5.1.11-1 \
dse-libhadoop2-client=5.1.11-1

Repeat this process until you have migrated all nodes in the recommended order.

Convert to a binary tarball

If you have any DSE Analytics nodes, re-create the Spark RDD directory, adjusting the base direction as appropriate:
```
mkdir ~/dse/spark/rdd
```
Get the DSE tarball for the same patch release as your previous installation, and then extract the tarball to a different directory.

For instructions on downloading and preparing the tarball before extraction, see Install DataStax Enterprise (DSE) 5.1 with a binary tarball.

You must extract the new tarball to a different directory to avoid conflicts with the previous installation’s preserved data and files.

For example, to extract a DSE 5.1.11 tarball to /dse5111tar:
```
sudo tar -xzvf dse-5.1.11-bin.tar.gz -C /dse5111tar
```
Compare your backup configuration files to the new installation’s configuration files, and then transfer your previous values to the new installation’s configuration files.
Make sure all paths, such as data directories and log files, are set correctly in the new installation’s configuration files.

Remember that the new installation is in a different directory than your previous installation. The paths must point to the locations that contain your previous installation’s SSTables and other files in order to access that data and continue normal operations when you start DSE.
Repeat this process until you have migrated all nodes in the recommended order.