Cloud ConnectorsSetup

In the source system, please run the following command:

 sudo bash -c "$(curl -L https://download.skyformation.net/v2/download/installer/edge/migration_export.sh)" $@ 2>&1 | tee "migration-export-at-`date --iso-8601=ns`.log"

When prompted, enter a path where your configurations will be saved. Please make sure it is a non-existing directory.

When the process is finished, you should see the message: ==> Done export! The backup dir is in:<Your backup directory>.

Copy the directory created in step 1, from the source system to the target system (using scp or rsync for example)

In the target system, please run the following command:

sudo bash -c "$(curl -L https://download.skyformation.net/v2/download/installer/edge/migration_import.sh)" $@ 2>&1 | tee "migration-import-at-`date --iso-8601=ns`.log"

When prompted, enter the path to the directory that was copied in step 2.

When the process is finished, you should see the messages: Services are running successfully and then ==> Done import!

On the source system, go to the Cloud Connectors UI , navigate to Settings > Accounts and stop all the active accounts one by one. Then, wait at least 5 minutes to let each account stop gracefully. Note of the accounts that were active.

Remove any old utilities image from the system. On the source system terminal, run the following command:

sudo docker image rm -f skyformation/troubleshoot-utils 

If the image is not present you will get the following error :

Error: No such image: skyformation/troubleshoot-utils

This is okay. You can ignore this error.

Export source settings:

On the source host, run the following based on your migration path:

(Version 2.5.x only) Install Exabeam Cloud Connectors platform on the target host with the same Exabeam Cloud Connectors platform version as the source. To confirm the source version, in the Exabeam Cloud Connectors platform UI go to Settings > General. To install the Exabeam Cloud Connectors platform with a specific software version, see Install Exabeam Cloud Connectors. To install version 2.4 on your target host, please contact support to get the command to install old version.

Stop the SK4 service on both the source and the target:

sudo systemctl stop sk4compose

Override the encryption key in the target with the one from the source:

1. Find the location of the docker-compose.yml file on the source and target systems and if an override file exists (source only)

   1. On the terminal of each system, type:

      cat /etc/systemd/system/sk4compose.service | grep ExecStart 

   2. In the output line, the compose file path shows after the -f. If more than one file appears as a parameter -f, the first one is the compose file and the second one is the override file.

      An example result:

      ExecStart=/usr/local/bin/docker-compose -f /opt/sk4/docker-compose.yml up
      
      The docker-compose.yml file full path is /opt/sk4/docker-compose.yml

      Note

      The location of the docker-compose.yml file may be different between the source and the target. This is okay. You should not change the location of the file on any system.

2. Find the SKYFORMATION_ENC_KEY string from the source and target machines. Run the following:

   grep SKYFORMATION_ENC_KEY <compose file full path> | uniq | cut -f2- -d=

3. Replace the SKYFORMATION_ENC_KEY env variable in the target machine (using the key from the source machine). On the target machine run the following:

   sudo sed -i 's/<CURRENT_KEY_IN_TRG>/<OLD_KEY_FROM_SOURCE>/g' <target system compose file full path>

   Repeat the command from to get the SKYFORMATION_ENC_KEY on the target to make sure it was successfully replaced.

4. If an override file exists on the source machine, copy it to the directory where the compose resides on the target system and edit the file /etc/systemd/system/sk4compose.service to add the additional -f flag with the override file, similar to what was in the source system.

Copy the contents of the three docker volumes (sk4_conf, sk4_pg_data, sk4_pg_conf) from the source system to the target system:

1. First, find out the location of these docker volumes on the source and target systems – it is not necessarily in the same path! modify only the content, do not change the path/location of the volume on the target system.

   To find the path, type (source and target systems):

   sudo docker volume inspect sk4_conf

   The path is listed under the Mountpoint entry. The three volumes are all located under the same root path.

2. For each of the three volumes, copy the *contents* of the directory from the source system into their corresponding locations on the target system (using scp or rsync for example).

3. Check file permissions on YML and SH files in the sk4_conf directory on the target:

   • For the SH file, the execute flag should be enabled. If not, run chmod +x *.sh to configure file permissions.

   • For the YML files, read+write access is required for the user account that runs the Exabeam Cloud Connectors platform.

On the target system, start the configuration service based on your installation version.

Import configurations into the target, based on your installation:

1. Copy the sk4etcdkbackup-<date> or sk4zookbackup-<date> folder generated in Step 3 from the source system to the local home folder ($PWD) on the target.

2. Run the command for the your migration path:

   • If the target is on Exabeam Cloud Connectors platform 2.5.x, import the etcd contents using the sk4etcdkbackup-<date> folder:

     sudo docker run --rm --network=sk4_isolated_nw -v "$PWD/sk4etcdbackup-<date that was created during the import>":/local skyformation/troubleshoot-utils:latest etcd-import /local 

     Run the following command to ensure data has been imported successfully. You should see entries (more than one) for the imported data, specifically there should be an entry for each account that was imported:

      sudo docker container exec -it sk4etcd etcdctl get "" --prefix=true --keys-only

   • If the target is on Exabeam Cloud Connectors platform 2.4.x, import the zookeeper contents using the sk4etcdkbackup- folder:

     sudo docker run --rm --network=sk4_isolated_nw -v "$PWD/sk4zookbackup-<date> ":/local skyformation/troubleshoot-utils:latest zookeeper-import /local

Start the Exabeam Cloud Connectors platform on the target:

sudo systemctl start sk4compose

On the Exabeam Cloud Connectors UI on the target, start all the accounts that were active on the source.

After verifying data is flowing on the target, stop and disable Exabeam Cloud Connectors on the source:

sudo systemctl stop sk4compose
sudo systemctl disable sk4compose