Upgrade the On-Premise appliance in place

An upgrade replaces the system disk and keeps the data disk. Your integrator partner runs it; the appliance checks itself and rolls the database back if a migration fails.

Step 1/5

Preparation

Your integrator partner triggers the preparation: a database dump and a manifest of the running version.

Step 2/5

System disk swap

The VM is shut down. The system disk is replaced by the new version. The data disk stays attached, untouched.

Step 3/5

Boot checks

At boot, the appliance checks that the data disk is mounted and that at least 500 MB are free, then applies the database migrations. If a migration fails, the appliance restores the pre-upgrade dump by itself.

Step 4/5

Health check

After 60 seconds of stabilisation, the appliance checks that every service answers.

Step 5/5

Closure

Success: the manifest is archived for audit and your integrator partner is notified. Failure: the logs go to the integrator partner, who reinstalls the previous version on the same data disk.

Before the upgrade

Take a snapshot of the data disk from your hypervisor (backup). It is your fallback if the host fails during the operation. Collection pauses while the VM is off and resumes at restart, from the files still present on the PBX.

Last updated :

Suggest an edit