Migrating Sisense in Linux Environments
If you are running Sisense on Linux, you can migrate your Sisense assets from one environment to another, for example, from development to production, or from a single-node to a multi-node cluster. Below are the steps you need to perform to successfully migrate Sisense assets between Linux deployments.
Migrating between Similar Environments
You can easily migrate Sisense between similar environments. The basic flow is to back-up your assets from your current environment, install Sisense in the new environment, and then restore your assets from the backup to the new environment. During the backup process, Sisense creates a .tar file that you later restore in the new environment.
To migrate from one environment to another:
- Enable the Sisense command line application - SI.
- Backing up and Restoring Sisense using the command:
si system backup [-include-farm no]
If you want to back up your .ecdata files, set -include-farm to yes. Keep in mind that .ecdata files contain your raw data and can be very large in size.
A backup archive is created in the following directory:
If your models are very large, you can export and import the model schema only (without hte data) and build them in the new environment as described in Exporting and Importing Models.
- Install Sisense on the new environment as described in Initializing Sisense on Linux.
- Restore the Sisense assets to the new environment with the following command:
si system restore -name sisense_assets_collector_some_date [-include-farm yes/no]
Restore the following files manually:
- Static datasource files, such as .xls and .csv files
- SSL certificates and private keys
Reschedule any scheduled ElastiCube builds:
kubectl -n sisense get cronjobs.batch -o json > jobs.json
kubectl -n sisense apply -f jobs.json
Migration from Sisense Windows Deployment
Sisense provides premium support for migrating Sisense from a Windows environment to Linux. For more information about this service, contact your Customer Success Manager.