AWS - Creating a Backup

This page explains the procedure to do a backup of the installation of the the Solution Manager and the Denodo Platform components, when using the Automated Cloud Mode (AWS) of Solution Manager.

  • Backup of the Solution Manager. You have two options to do this:

    1. Create an AMI: from the AWS console create an AMI for the EC2 instance that runs Solution Manager. See Create an AMI from an Amazon EC2 Instance documentation on how to do it. This AMI will be the backup. You can do this periodically.

      Important

      To do a backup, the Solution Manager needs to be shut down temporarily to create the AMI. So, you should search for a time window that does not impact users.

      When creating the AMI, clear the check box No reboot. This is necessary because in order for the backup to be successful, all the services of the Solution Manager have to be stopped.

    2. Instead of creating an AMI, you can copy the following files and store them on a separate computer to keep them as a backup in case of failure of this instance:

      • Export the configuration of Solution Manager and store the resulting file.

      • Copy the file <SOLUTION_MANAGER_HOME>/conf/denodo.lic (this is the license file)

      • Copy the certificate file or the KeyStore file (e.g.: {<SOLUTION_MANAGER_HOME>/denodo_server_key_store.jks). Only necessary if TLS is enabled.

      • Copy the TrustStore file: usually {<SOLUTION_MANAGER_HOME>/jre/lib/security/cacerts.

      • When storing the configuration of Solution Manager on an external database:

        • Copy the file <SOLUTION_MANAGER_HOME>/conf/license-manager/LMConfigurationParameters.properties.

        • Copy the jar files of the <SOLUTION_MANAGER_HOME>/lib/solution-manager-extensions/ (these are jar files required to connect to this database).

        • Check with the administrator of this database that there are up-to-date copies of this database.

  • Backup of the components of the Denodo Platform:

    • The Solution Manager creates an AMI after performing the main operations on the clusters, such as when deploying promotions, after installing an update, after recreations, etc. These AMIs can be used as backup.