You can upgrade the operating system of an existing VMware backup proxy in place, from Ubuntu 22.04 LTS to Ubuntu 24.04.5 LTS, without deploying a new proxy. The upgrade uses the Ubuntu do-release-upgrade tool and runs from the proxy's command line.
This article covers the operating system release upgrade only. To update the backup proxy, see How to upgrade VMware backup proxy.
⚠ Important
Create a recovery point for the VMware backup proxy before you start. If the upgrade fails, restoring the proxy to that recovery point is the supported recovery method.
Before you begin
Make sure that you have:
A maintenance window. The proxy is unavailable for backup and restore while the upgrade runs. Backup and restore jobs that are queued can be picked up by another proxy in the same pool. Jobs that stay queued or running on this proxy remain in that state until the proxy is back online or job sanitization cleans them up.
Access to the VMware console for the proxy virtual machine.
Root or sudo privileges on the proxy. The upgrade requires them.
Access to the VMware vSphere Client, to create the snapshot and, if needed, revert to it.
Sufficient free disk space in the root (/) and /boot partitions of the proxy. Neither Ubuntu nor Druva publishes an official minimum. do-release-upgrade calculates the space it needs before it starts, and stops with a "Not enough free disk space" message that tells you how much to free on which mount. To avoid this, check the following thresholds before you start:
Partition | Minimum | Recommended |
/ (root) | 4 GB | 5 GB |
/boot | 300 MB | 500 MB |
To check the available space, run:
df -h / /boot /var /tmp
df -i / /bootNetwork access from the proxy to the Ubuntu servers. The upgrade downloads packages from the internet, so the proxy needs outbound access to Ubuntu's servers (for example, ubuntu.com).
Prompt=lts set in /etc/update-manager/release-upgrades. You set this in the procedure below. Do not set Prompt=never before or during the upgrade; it is used only after the upgrade is verified (see Step 7).
Considerations
do-release-upgrade cannot target a specific point release. The point release is set by the package versions in the Ubuntu 24.04 (noble-updates) suite at the time you run the upgrade, so the proxy ends up on the latest 24.04.x release. At the time of this release, that is 24.04.5. If Ubuntu publishes a later 24.04 point release before you upgrade, you get that release instead, which is supported. The proxy stays on the Ubuntu 24.04 (noble) series either way.
This procedure upgrades proxies that run Ubuntu 22.04 only.
Procedure
Step 1: Take a snapshot of the proxy
In the VMware vSphere Client, locate the backup proxy virtual machine.
Create a snapshot of the virtual machine. Whether to include the virtual machine's memory in the snapshot is your choice.
Step 2: Check free disk space
Log in to the proxy through the VMware console.
Run the following commands and confirm that the root (/) and /boot partitions meet the thresholds listed in Before you begin:
df -h / /boot /var /tmp
df -i / /boot
Step 3: Configure the release upgrade prompt
Open /etc/update-manager/release-upgrades for editing.
Set the following value:
Prompt=ltsSave the file.
Step 4: Check that the upgrade is offered
Run the following command:
do-release-upgrade -c
The command reports whether Ubuntu 24.04 is available as an upgrade.If the upgrade is not offered, see Upgrade is not offered under Troubleshooting. Do not continue.
Step 5: Run the upgrade
📝 Note
Run the upgrade from the VMware console. If you run it over SSH, an initial warning asks to start an additional SSH daemon on port 1022. Enter y and press Enter to accept. Running the upgrade from the VMware console is recommended.
From the VMware console, run the following command:
sudo do-release-upgradeRespond to the prompts as follows:
Prompt | What to enter |
Do you want to start the upgrade? Continue [yN] Details [d] | Enter y. The package download and installation start. |
Configuration file conflicts. Prompts appear for locally modified files, for example /etc/sysctl.conf, /etc/audit/auditd.conf, /etc/nfs.conf and /etc/ssh/sshd_config. | Keep the currently installed (local) version. For command-line prompts, enter N (the default). For dialog screens, select keep the local version currently installed. This keeps your proxy configuration and customizations from being overwritten. |
Remove obsolete packages? Continue [yN] Details [d] | Enter y to remove deprecated packages. |
Restart required. To finish the upgrade, a restart is required. If you select 'y' the system will be restarted. Continue [yN] | Enter y to restart the proxy. |
Wait for the upgrade to complete. The virtual machine restarts automatically.
Step 6: Verify the upgrade
After the proxy restarts, confirm that:
The proxy is running Ubuntu 24.04. Run the following command:
. /etc/os-release; echo "$PRETTY_NAME | $VERSION_ID | $VERSION_CODENAME"
The output is similar to Ubuntu 24.04.5 LTS | 24.04 | noble (or a later 24.04.x release).
You can also run cat /etc/os-release.The Druva-EnterpriseWorkloads service is running.
The proxy shows as connected in the Management Console. Go to Protect > VMware, select the vCenter or ESXi host, and click Backup Proxies.
Step 7: Stop further release upgrade prompts
After you verify the upgrade, set the following value in /etc/update-manager/release-upgrades so that Ubuntu doesn't offer a further release upgrade (for example, 24.04 to 26.04):
Prompt=never
Regular apt update and apt upgrade and security updates continue to work. This step is recommended to keep the proxy on Ubuntu 24.04.
