Upgrade Lighthouse

Lighthouse can be upgraded using a .lh_upg image file. Note the following conditions:

• AWS requires .aws.lh_upg and Microsoft Azure requires .azure.lh_upg. All other platforms use the standard .lh_upg file.

• Incremental upgrades to Lighthouse using lh_upg files are only supported from 20.Q3.x and not earlier releases.

Note:  Upgrades do not overwrite existing configurations or user files, however it is recommended that you perform a Configuration Backup before you upgrade a Lighthouse.

After the upgrade is complete, the Lighthouse instance reboots. It is unavailable during the reboot process.

About the Upgrade Process

Lighthouse performs the following high-level steps to upgrade to the new version:

1. Validates the upgrade image, and takes a backup of the current root file system and snapshot of data volume.

2. Reboots into the new root file system (from the upgrade image).

3. Performs data migrations and system re-configurations.

4. Commits the changes on success, or reverts on failure.

5. For Multiple Instance only, after a successful Primary upgrade: After a 10 minute delay, secondary instances are automatically upgraded in sequence.

Lighthouse uses LVM snapshots to manage storage during upgrade and data migration. If a failure occurs, the snapshot is used to revert the system to its previous state.

In regard to software versions, Lighthouse must be upgraded in succession. For example, to upgrade to a version that is several releases newer than your current release, you must install all the major releases in between to install the newest one.