Recovering the Sisense Environment after a General Failure

If you experience problems in your Sisense Linux deployment, for example, your data becomes corrupted or you experience storage failures, you can recover Sisense and your data if you have created a backup file.
The procedure below describes how to remove your current instance of Sisense and restore a previous version with the config.yaml file you created when Sisense was installed.
This process describes how to recover your Sisense environment, however, the following are not restored and must be restored manually under /opt/sisense/storage:

  • branding
  • configuration
  • connectors
  • emails
  • licensing
  • plugins
  • reports
  • system_backups
  • translations
  • data
  • SSL Certificate: Back up your certificates and the private key used to install Sisense.

To recover an instance of Sisense:

  1. Remove the corrupted Sisense and user data.

    1. Connect to your primary instance of Sisense with the SSH protocol using the user that you used to install Sisense.

    2. Make sure you are in the home directory where Sisense was installed. If you are not, open the directory where Sisense was installed.

    3. Open the config.yaml file and edit it with the command:
      vi config.yaml
    4. Set the following values to true to remove the cluster and your Sisense user data:
      uninstall_cluster
      remove_user_data
    5. Run the updated script with the following command:
      bash ./sisense.sh config.yaml
    6. Reboot your Kubernetes Servers with the following command:
      ssh <instance_ip_address> sudo reboot

  2. Reinstall Sisense.

    1. Open and edit the config.yaml file.
    2. Change the following values to false:
      uninstall_cluster
      remove_user_data

  3. Restore your Sisense data with the following commands:

    1. Load completion and login Sisense swagger in order to run SI commands.
    2. Validate that the completion script is in your current working directory. Type the command ls and search for the file.
    3. Enter the following command:
      source add_completion-ns-sisense.sh
  4. Restore your Sisense backup tarball with the following Sisense Linux command: For: sisense_assets_collector_yyyy_mm_dd_hh_mm.tar.gz, located in the /opt/sisense/storage/system_backups directory:
    si system restore -name sisense_assets_collector_yyyy_mm_dd_hh_mm
    Note:
    • This will look in the /opt/sisense/storage/system_backups directory by default.
    • You must omit the file extension (tar.gz).

  5. Restore the following files manually:

    • Static datasource files, such as .xls and .csv files
    • Connector manifest files
    • SSL certificates and private keys
  6. Reschedule any scheduled ElastiCube builds.

Your Sisense deployment is now restored.