Resolution

For instructions on upgrading your Awingu environment, and details about the changes in the Awingu version, please take a look at our release notes.

This article contains important factors to keep in mind/to expect when planning to upgrade Awingu to the latest version.

• Awingu upgrades are incremental.
  You may need to upgrade through multiple Awingu versions to be able to upgrade to the latest release, depending on your current version of Awingu. These are defined in our release notes; there's also an overview
  at the end of this article.
   
• Take a snapshot of the appliance(s) (and if applicable: external database) before EACH upgrade. 
  Before carrying out an Awingu version upgrade, it is always highly recommended to shutdown the appliance(s) and take a snapshot/backup of the appliance(s). If applicable: do the same for the external database. If there are major issues during/after the upgrade, contact the support team first for an analysis, so the cause can hopefully be determined, and perhaps the failed upgrade can even be resolved. In a worst case, the support team will recommended to restore these snapshots, in order to restore accessibility to the Awingu appliance as quickly as possible.
• Rebooting before starting the upgrade is a good idea.
  
   
• Download or Download & Upgrade. 
  When you are on the General Info page of the System Settings, there's an option to Download or Download & Upgrade (depending on which version).
  Download will download the update packages, ready to install later (the button will change when the packages are downloaded.
  Download & Upgrade will download the upgrade packages. When complete, the installation begins immediately.
   
• Service interruption. 
  When upgrading an environment, there will always be service disruption, a period where users cannot access/use the environment. This is also the case for a multi-node environment, so it's recommend to upgrade outside business hours.
  
   
• Service interruption period. 
  During an environment upgrade, the estimated length can be calculated as about 15 minutes per appliance in the cluster.
  For example, if there are 3 nodes in the cluster, this will take approximately 45 minutes to upgrade.
  However, in some situations the upgrade can take up to 40 minutes per appliance, depending on the disk and network speed.
  
   
• Do not refresh the System Settings page. 
  While the upgrade is in progress, do not refresh the System Settings page. When using the built-in admin account to do the upgrade, the account will be automatically logged out after 15 minutes. This is no problem, just log in and open the System Settings again.
  
   
• NEVER reboot the appliance(s) manually during an upgrade unless told so. 
  It is important to never reboot appliances while they are in an upgrading state because "it feels like the upgrade is taking too long" (check the service interruption points above for estimation and maximum expected service interruption). If the appliance seems to be stuck in an upgrading state, either:
  • Contact the support team. This is the preferred option, as the support team may still be able to see the cause of the failing upgrade.
    Worst case, they will advise restoring the snapshot(s).
  • If this takes too long: shut down the appliance(s) and restore to the snapshot(s) (and if applicable: the external database) from before the upgrade. Then contact our support team. In this case, it will not be possible to determine what the cause of a failed upgrade was.

Upgrade paths

This is a summary of the upgrade paths:

Related info: No upgrades available / latest version not available .