Backup and restore strategies

0 users found this article helpful


All scenarios assume a restore to exactly the same application and database version.

Mind that a typical Awingu environment consists of one or more appliances (virtual machines).

It's also important to check if Awingu relies on an external database.

When restoring an Awingu appliance which is on version 5.3.2; the database scheme should also be 5.3.2.


All scenarios: prior to restoring

  1. Consider taking a backup of the remaining infrastructure (if applicable).
  2. Shutdown every Awingu appliance if still running.
    After a successful restore and confirming Awingu is up and running again, delete them after this restore procedure.


Scenario 1: using backups or snapshots of virtual machines



  1. If applicable: Restore the backup of the external database.
  2. Restore the backup(s) of the virtual machine(s) and boot them.


Scenario 2: using an environment backup


Mind that an environment backup does not include all data: metrics and shares (shared files) are not recovered when using this backup strategy.


Creating the environment backup

Important: if applicable, mind to also back up the external database.
The environment backup itself does not include the external database. 
If Awingu uses an internal database, it will be included.

There are some different ways to create environment backups. It can be triggered manually (System Settings > Global > Troubleshoot and select the appropriate action) or through the API.

It's also possible however to schedule an automatic daily backup. Navigate to System Settings > Global > Connectivity: Environment Backups to adust the settings. Here SFTP credentials can be specified.

It's also possible to configure whether the vault should be backed up as well. Mind that this may lead to a very short service interruption for single sign-on (SSO) each time the daily backup is created. It's also possible to leave this disabled, in which case SSO will fall back to pre-authentication after restoring the backup.

Be sure to regularly download these backups using an SFTP connection to the Awingu appliance.


Restoring the environment backup

  1. Prior to restoring:
  2. Restore the database (if necessary).
  3. Deploy a new Awingu appliance. Note: the Awingu version must be equal to the one which generated the environment backup.
  4. Start the installation wizard by surfing to https://<awingu_appliance_ip>:8080/ 
  5. After accepting the EULA, import the backup file.
  6. Continue to follow the steps in the wizard. Information such as IP addresses, hostnames and credentials of the Awingu appliance (and if applicable, external database) will be prefilled. It is possible to change these.
  7. If this was a multi-node before: it is necessary to manually scale again, so deploy additional Awingu appliances and add them through System Settings > Global > Service Management.

Depending on whether there was a backup of the vault, it may also be necessary to reconfigure Single Sign-On (SSO). 



Was this article helpful?

Tell us how we can improve it.