Upgrading to 6 from Version 5.0 or Earlier

To upgrade Veeam Backup for Google Cloud to version 6, a backup appliance must be running version 3.0 or later. To upgrade the appliance, check the prerequisites and follow the instructions provided in section Updating Appliances Using Console.

When you perform upgrade to version 6 from Veeam Backup for Google Cloud version 5.0 or earlier, the backup appliance operating system is upgraded from Ubuntu 20.04 LTS to Ubuntu 22.04 LTS, and the configuration database is upgraded to PostgreSQL 16. Consider that during upgrade the original root disk of the backup appliance will be replaced with a new one.

How Upgrade to Version 6 Works

When upgrading backup appliances to version 6 from Veeam Backup for Google Cloud version 5.0 or earlier, Veeam Backup & Replication performs the following steps:

1. Instructs Veeam Backup for Google Cloud to create a cloud-native snapshot of the original appliance. If the upgrade process fails, the appliance will be reverted to the created snapshot.

Consider that this snapshot will be automatically removed by Veeam Backup & Replication from Google Cloud after the upgrade operation completes successfully.

2. Stops all running backup and restore sessions on the original backup appliance.
3. Upgrades the appliance configuration database to PostgreSQL 16.
4. Saves the following configuration files and settings to the data disk: the appliance configuration file (/etc/veeam/gcpbackup/veeam-gcp-backup.conf), nginx configuration files (/etc/nginx/nginx.conf, /etc/nginx/proxy_params), users, MFA and time zone settings, and Linux environment (/etc/ssh/, /root/, /home/).
5. Deploys a temporary VM instance from the Ubuntu 22.04 LTS image.
6. Detaches the boot disk from the newly created VM instance.
7. Detaches the outdated boot disk and attaches the new boot disk to the original appliance.
8. Removes the outdated boot disk from Google Cloud.
9. Restores the configuration files and settings saved at step 4 to the new boot disk.
10. Removes the temporary VM instance.

Limitations and Prerequisites

Before you start the upgrade process, consider the following requirements and limitations:

• The service account whose access keys you plan to use when deploying a backup appliance or connecting to the appliance must be assigned permissions required to perform upgrade. For the list of required permissions, see Plug-in Permissions.
• Outbound internet access must be allowed from the backup appliance to the PostgreSQL Apt Repository (apt.postgresql.org, apt-archive.postgresql.org) through port 80 over the HTTP protocol.
• Outbound internet access must be allowed from the backup appliance to the PostgreSQL through port 443 over the HTTPS protocol to download the repository key https://www.postgresql.org/media/keys/ACCC4CF8.asc.
• Outbound internet access must be allowed from the backup appliance to the Veeam Update Repository through port 443 over the HTTPS protocol.
• Outbound internet access must be allowed from the backup appliance to the Ubuntu Security Repository (security.ubuntu.com) through port 80 over the HTTP protocol.
• During upgrade, the data disk of the backup appliance will temporarily contain files of 2 databases. That is why the size of the data disk must be twice the total amount of storage space used by the configuration database.
• During upgrade, Veeam Backup & Replication will create a new root disk with default settings. That is why if you have previously modified the root disk settings, for example, if you have increased the volume size or enabled volume encryption, these settings will not be transferred, and custom 3rd-party software installed on the backup appliance will not be migrated.
• During upgrade, Veeam Backup & Replication will overwrite custom settings of the /etc/fstab configuration file on the backup appliance with the default settings. That is why if you have previously attached an additional disk to the backup appliance, you must re-mount the disk by adding its label or UUID to the /etc/fstab file.
• After the upgrade process completes, the original root disk will be automatically deleted from Google Cloud.