Upgrading from Community to Enterprise

Aerospike Enterprise Edition includes additional features and provides access to tested and certified builds, hot patches and 24x7 Enterprise Support. To see all other benefits of using the Enterprise Edition, see Features and editions.

Use the following steps to upgrade a cluster of community-version nodes to the enterprise version. For the purposes of upgrading, you can add an enterprise node to a cluster of community nodes.

Perform the following steps on each node, one node at a time.

Check migrations

Verify that the cluster is not migrating data before you stop one of the nodes. Run the following command to check migration status:

# Migrations are complete when all `migrate_progress_recv` and
# `migrate_progress_send` values return 0.
asadm -e "show stat like migrate_tx_partitions_active migrate_tx_partitions_remaining migrate_rx_partitions_active migrate_rx_partitions_remaining migrate_record_receives -flip "

Stop the Aerospike service

Run the following command to display the current status of the Aerospike Service:
Terminal window
```
sudo service aerospike status
```
Run the following command to stop the Aerospike service on the node:
Terminal window
```
sudo service aerospike stop
```

Back up the configuration File

Create a backup of the current configuration file:

sudo cp /etc/aerospike/aerospike.conf /etc/aerospike/aerospike.conf.bac

Uninstall the Community Aerospike server package

RedHat/CentOS
Debian/Ubuntu

sudo rpm -e aerospike-community-server

# If you have tools package installed separately
sudo rpm -e aerospike-community-tools

sudo dpkg -r aerospike-community-server
sudo dpkg --purge aerospike-server-community

# If you have tools package installed separately
sudo dpkg -r aerospike-community-tools
sudo dpkg --purge aerospike-community-tools

Install Aerospike Enterprise packages

For details about downloading and installing Aerospike Enterprise packages, see Install Aerospike.

Restore the configuration backup

Restore the backed up configuration file to /etc/aerospike/aerospike.conf:

sudo cp /etc/aerospike/aerospike.conf.bac /etc/aerospike/aerospike.conf

Start the Aerospike server

The following steps ensure that you have installed the Aerospike Enterprise server and that migrations have finished so that you can proceed to the next node.

Start the Aerospike service with the following command:
Terminal window
```
sudo service aerospike start
```
If you see warnings in the Aerospike log about deprecated parameters, confirm their usage in Aerospike 3 in the Configuration Reference.
Wait for Aerospike’s service port (port 3000) to open before continuing. When the service port opens, the following command will return “OK”:
Terminal window
```
asinfo -v STATUS
```
If your server contains any in-memory namespaces without persistence, you must wait for migrations to complete before continuing to the next node to prevent data loss.

Run the following command to verify migrations are complete:
Terminal window
```
# Migrations are complete when all `migrate_progress_recv` and
# `migrate_progress_send` values return 0.
asadm -e "show statistics like migrate_progress"
```
If all namespaces are persisted, you may continue to upgrade the next node and not lose any data.

If writes are still active on the cluster, and you choose to not wait for migrations to complete between node upgrades, some record updates may be overwritten during migration conflict resolution. Contact Aerospike Support for further details if necessary.

Verify the installation

After completing all the steps above on each node, follow the steps in Verify an installation to confirm that Aerospike was installed successfully and is running.