After Upgrade

After you upgrade Veeam Backup & Replication to version 12.3, perform the following steps:

1. If you use remote backup consoles, upgrade them to version 12.3. If you use remote backup consoles of version 11a, you can upgrade them to version 12.3 automatically when connecting to backup server version 12.3.
2. Download and install the latest available update from the Veeam Updates page.
3. Open the Veeam Backup & Replication console. If necessary, the automated upgrade wizard will automatically appear, prompting you to upgrade the product components running on remote servers. Follow the wizard to complete the upgrade process.
4. If some remote servers are unavailable at the time of upgrade, you can run the upgrade wizard at any time later from the main product menu, or by closing and re-opening the Veeam Backup & Replication console. Note that the out-of-date product components cannot be used by jobs until they are updated to the backup server version.
5. Azure compute accounts based on Microsoft Entra ID (formerly Azure Active Directory) user credentials (created with the Use existing account option selected) are obsolete. Replace these accounts with new ones to restore workloads to Microsoft Azure and use Azure archive storage or the Microsoft Azure Plug-In for Veeam Backup & Replication appliance.
6. If you use the Virtual Labs functionality, open settings of each Virtual Lab, and click through the wizard to redeploy each virtual lab with the new proxy appliance version.
7. If you are using Linux servers for your backup infrastructure components, the process of upgrade to version 12.3 will automatically deploy the new persistent data mover only to Linux servers with the VMware Backup Proxy role. To deploy it on other Linux servers, click through the Linux server properties, or use Set-VBRLinux PowerShell cmdlet to mass-deploy. Until you do this, those Linux servers will continue using the legacy run-time data mover to avoid issues with backup repository not meeting the persistent data mover requirements.
8. Enable any scheduled jobs that you have disabled before the upgrade.

Note that immediately after the upgrade, the backup server performance may decrease. This happens due to the maintenance job that optimizes the configuration database. The process may take up to an hour depending on the database size.