How to migrate an existing deployment to another server

Goal

In this guide we'll migrate an existing deployment of Cloud Connectors (formally SkyFormation) from one server to another.

An example usecase to such migration can be to move off of a deployment on a shared host that runs other applications, and we would like to allocate dedicated resources for each.

Steps

1. As we'll be installing the latest version on the new instance, to keep data versions aligned, first upgrade the source instance to the latest version - upgrade guide.
2. Next we need to figure out is whether the source deployment is in an Exabeam-appliance layout, or standalone layout -
   1. Find whether a docker-compose.yml is located under /opt/sk4 (Standalone layout) or /opt/exabeam/data/sk4 (Exabeam appliance layout).
3. Run this procedure to export the settings from instance 1, copy the output to instance 2 - link
4. Install the latest CC version on the new machine (link)
   1. if it has a mounted at /opt/exabeam/data then install with a -d=exabeam flag ; otherwise omit that flag
5. Stop sk4 on the new instance:

   1. sudo systemctl stop sk4compose

6. Replace the docker-compose.yml on the new instance w/ the one from source instance
   • If the source instance was not deployed with Exabeam appliance layout and the new one is - or vise-versa - DO NOT copy this file over - instead, copy the SKYFORMATION_ENC_KEY from the source docker-compose.yml and replace in the destination one in all its occurances
7. Replace the /opt/exabeam/data/sk4/conf (or /var/lib/docker/volumes/sk4_conf/_data for Standalone deployment layout) on the new instance with the one copied from instance 1
8. Start only the zookeeper service on the new instance:

   /usr/local/bin/docker-compose -f /opt/exabeam/data/sk4/docker-compose.yml up -d zookeeper

9. Run the import command from the guide in step #1
10. Start the sk4compose service on the new instance:

    1. sudo systemctl start sk4compose

11. After validating all is good on the the new instance, stop and disable sk4compose from source instance:

    1. sudo systemctl stop sk4compose

    2. sudo systemctl disable sk4compose

Troubleshooting

• If there are additional docker-compose-*.yml files on the source, additional manual steps will likely be needed in order to complete the migration
• If the export process halts and in unable to complete, first stop the sk4compose service and only start the sk4zookeeper service, and re-run it

  • sudo systemctl stop sk4compose

  • /usr/local/bin/docker-compose up -f /opt/exabeam/data/sk4/docker-compose.yml zookeeper -d