9.6 Upgrade Veeam Cloud Connect from 9.0 to 9.5

This document has described a new Veeam Cloud Connect environment, where every component is deployed from scratch. Chances are however, as the software matures and is updated with newer versions, that service providers need to upgrade an existing environment with the latest version.

This chapter describes the steps required in order to upgrade Veeam Cloud Connect from v9.0 to v9.5, which has been proved so far to be the major step forward in the software. Other upgrades can be executed without specific recommendations. Nonetheless, the general concepts and the steps described here can be used as a reference also for other upgrades of Veeam Cloud Connect.

This document assumes that the Veeam Backup & Replication installation where Cloud Connect is running is updated to the latest v9.0 version, that is Update 2 (Build 9.0.0.1715). Update 2 can be obtained at the following link: https://www.veeam.com/kb2147.

As a best practice, already explained multiple times in this book, service providers should upgrade their Cloud Connect environments to the latest available version as soon as they are available, as it is advised that the receiving side of Cloud Connect (at the service provider) is at least running the same version of the one sending data (at the tenant). Veeam Backup & Replication installer has a specific warning system during an upgrade to notify end users that a service provider registered in the local installation is running a older version of Veeam Cloud Connect:

Tenant receives a warning if service provider is using a older version of Veeam Cloud Connect

This is however a warning, and tenants can proceed in their upgrade process. The final result is that tenants are running a version that is newer than the one used by service providers. Also, if tenants follow the warning and delay the upgrade, they are not able to use any new feature available in v9.5 (or any following version) until their service provider updates his own installation.

NOTE: the upgrade process requires some downtime of the Veeam Cloud Connect service. During the upgrade process no data will be lost, but services will be temporarily stopped to proceed with the upgrade. This means that tenants will not be able to consume the service, and any scheduled job running during the upgrade process would fail. Please plan accordingly and warn your tenants about the upcoming maintenance.

1. Upgrade Veeam Enterprise Manager

  1. Download Veeam Backup & Replication v9.5 ISO file;
  2. If you followed the design described in this book and have deployed the Enterprise Manager in a dedicated machine, mount the ISO file into that machine, start the Setup application and proceed first to upgrade this component:

Start the upgrade from enterprise Manager

The wizard recognizes that Enterprise Manager is installed and not updated to v9.5, so it automatically disabled the upgrade options for both Veeam Backup & Replication and Veeam Backup & Replication Console. Select the Upgrade link in the upper right;

  1. Accept the terms in the License Agreement and hit Next;
  2. The wizard identifies the already installed components and propose to upgrade them automatically:

review previously installed Veeam Enterprise Manager components

Hit Next;

  1. An existing license for v9.0 is going to be compatible with v9.5, so if you have a proper license in your environment, there is no need to load an additional license. Hit Next;
  2. There are some additional components required by the new Enterprise Manager v9.5, and they are listed as missing in the System Configuration Check:

system configuration check

Hit first of all Install to enable the missing features. Once the operation is completed, all the required component should be listed as available and you will be able to hit Next;

  1. Passwords of service accounts need to be verified:

Submit the password for the service account

Insert the password that was created for the EM service account, and hit Next;

  1. Accept to use the existing SQL server instance, with all the defined parameters. Hit Next. The upgrade wizard will warn you that the existing database will be used and upgraded if needed. Hit Yes;
  2. All the required information have been collected. Hit Install to start the upgrade process;

The installation completes and the new version of the Enterprise Manager is already running. You can verify its status by opening it using the shortcut saved on the desktop, and you can also test the new Veeam Cloud Connect Portal. The Enterprise Manager 9.5 in fact can control a Veeam Backup & Replication 9.0 server, thus allowing for multi-step upgrade processes.

2. Upgrade Veeam Backup & Replication Service

Once the Enterprise Manager has been upgraded, the following step is to upgrade the main Veeam Backup & Replication server.

  1. Mount the downloaded ISO file on the VBR server and start the Setup;
  2. Select the main Upgrade area on the left and click over it to start the upgrade process;
  3. Accept the terms in the License Agreement and hit Next;
  4. Setup will detect the previous version of Veeam Backup & Replication:

Detected previously installed Veeam Backup & Replication components

Click Next to proceed;

  1. Again, an existing license for v9.0 is going to be compatible with v9.5, so if you have a proper license in your environment, there is no need to load an additional license. Hit Next;
  2. There are some additional components required by the new Veeam Backup & Replication v9.5, and they are listed as missing in the System Configuration Check:

system configuration check

Hit first of all Install to enable the missing features. Once the operation is completed, all the required component should be listed as available and you will be able to hit Next;

  1. Passwords of service accounts need to be verified:

Submit the password for the service account

Insert the password that was created for the VBR service account, and hit Next;

  1. Accept to use the existing SQL server instance, with all the defined parameters. Hit Next. The upgrade wizard will warn you that the existing database will be used and upgraded if needed. Hit Yes;
  2. All the required information have been collected. Hit Install to start the upgrade process;

The installation completes and the new version of the Veeam Backup & Replication Server is already running. As part of the upgrade process, also the local Standalone Console is updated to v9.5.

3. Upgrade Veeam components

Once the upgrade is completed, you can open the console and connect to the VBR Server. First of all, this will show the new version:

New Veeam Backup & Replication v9.5 splash screen

Upon connection, the Console will list the existing additional components that needs to be updated:

Components upgrade

This is a mandatory step in the upgrade process that Veeam Cloud Connect administrators have to complete before the environment can be considered as fully upgraded. It’s only needed to hit Next and the software will take care of upgrading all the different components, also the Network extension appliances already deployed to tenants.

Components upgrade is completed

NOTE: proxy3 and proxy4 are not running at the time of the upgrade as they have been removed from the environment.

The upgrade is completed, and tenants can consume Veeam Cloud Connect v9.5 using their local installation with version 8.0, 9.0 and 9.5.

4. Tenant upgrade

Veeam Cloud Connect v9.5 is backwards compatible with Veeam Backup & Replication v8.0 (backups only) and v9.0 (backups and replications). End users can keep using their versions of the software, or decide at some point to upgrade to a newer version.

When customers decide to upgrade to version 9.5, during the first run of the Standalone Console, together with the option to upgrade the different server components, also backup jobs and backup copy jobs using Veeam Cloud Connect as a target are proposed as upgradable:

Components upgrade at the tenant side

The Legacy Backup information is related to existing Backup and backup Copy job that are consuming Veeam Cloud Connect. Because of different underlying changes in the database schema in v9.5, some information have to be upgraded in the jobs and some additional configuration data has to be transmitted to the service provider. If this operation is not completed, the job would start to fail with a specific error:

Unable to access target repository Error: Legacy cloud backup [Backup job name] detected. Please upgrade this backup first, then try again.

The error would eventually be also part of the Job Report:

Legacy backup job is failing if not upgraded

The Job report would be sent by default every 30 minutes to the email recipient, thus heavily reducing the chances that a Legacy job is left in a non upgraded state.

In order to make the job working again, the tenant could upgrade the job during the overall upgrade of the different components, or if the upgrade has been postponed, go afterwards under Backup & Replication - Backups - Cloud, select the Legacy Job and hit the Upgrade option from the contextual menu:

Upgrade a Legacy job

Legacy jobs can easily be identified by the warning sign over their icon. The upgrade takes just a few seconds, and after it’s completed the warning icon disappears and the job itself keeps running again without any error.