Migrate from Linux install
StackState Self-hosted v5.1.x
Last updated
StackState v5.1
StackState Self-hosted v5.1.x
Last updated
This document describes how to migrate data from the Linux install of StackState to the Kubernetes or OpenShift install.
To migrate from the Linux install to the Kubernetes or OpenShift install of StackState, the following high level steps need to be performed:
on Kubernetes.
from the Linux install to the Kubernetes or OpenShift install.
from the Linux install to the Kubernetes or OpenShift install.
Incoming data from agents (Kafka) and node synchronisation data (Zookeeper) won't be copied.
After the migration:
Run both instances of StackState side by side for a number of days to ensure that the new instance runs correctly.
Stop the Linux install for StackState.
Remove the Linux install for StackState.
Before you start the migration procedure, make sure you have the following information and tools available:
Access to:
The Linux machines running your old StackState installation.
The cluster running your new StackState installation.
The values.yaml file used to install your StackState installation on Kubernetes/OpenShift.
Tools:
To export the StackGraph data, execute the regular StackState Linux backup procedures as described below.
Ensure that the StackGraph node is up and running.
Login to the StackState node as user root.
Stop the StackState service:
Create a directory to store the exported data:
Export the StackGraph data by creating a backup:
Copy the file /opt/stackstate/migration/sts-export.graph to a safe location.
Start the StackState service:
Enable the MinIO component by adding the following YAML fragment to the values.yaml file that is used to install StackState
Include the credentials to access the MinIO instance:
Replace MINIO_ACCESS_KEY with 5 to 20 alphanumerical characters.
Replace MINIO_SECRET_KEY with 8 to 40 alphanumerical characters.
Run the appropriate helm upgrade command for your installation to enable MinIO.
Start a port-forward to the MinIO service in your StackState instance:
In a new terminal window, configure the MinIO client to connect to that MinIO service:
Verify that access has been configured correctly:
The output should be empty, as we haven't created any buckets yet.
If the output isn't empty, the automatic backup functionality has been enabled. Disable the automatic backup functionality and configure MinIO as described above (i.e. not as a gateway to AWS S3 or Azure Blob Storage and without any local storage).
Create the bucket that is used to store StackGraph buckets:
The output should look like this:
The output should look like this:
Verify that the backup file was uploaded to the correct location:
The output should look like this:
Most importantly, the backup file uploaded in the previous step should be listed here.
Restore the backup:
The output should look like this:
Remove the YAML snippet added in step 1 and run the appropriate helm upgrade command for your installation to disable MinIO.
Notes:
To access the Elasticsearch instance that runs as part of the Kubernetes or OpenShift installation for StackState, execute the following command:
and access it on http://localhost:9200.
To modify the elasticsearch.yml configuration file, use the Helm chart value stackstate.elasticsearch.esConfig.
For example:
The restore scripts that are part of the .
To import the StackGraph data into the Kubernetes/OpenShift installation, the same component that is used for the backup/restore functionality will be used.
Note that the should not be enabled until after the migration procedure has completed.
Upload the backup file created in the previous step when from the Linux install:
To migrate Elasticsearch data from the Linux install to the Kubernetes or OpenShift install, use the functionality .