Veeam Backup and Replication v13 is now in the wild, and for service providers running Cloud Connect this is not just another point upgrade. It is a major platform refresh that touches the core backup server, gateways, explorers, agents, and the tenant facing control plane. With v13 bringing stronger security defaults, modernized components, and several legacy features finally retired, VCSP partners should plan their upgrades early so tenant adoption is smooth from day one.
I recently upgraded my Cloud Connect environment from 12.3 to v13. In this post I will walk through the upgrade flow exactly as the wizard presents it, with short practical notes at each stage. The focus is simple. What to verify, why Veeam is asking for it, and how to avoid tenant impact while moving your Cloud Connect stack cleanly onto v13.
Preparing for the upgrade
Before starting the upgrade, there are a few best practice steps you should complete across your VBR and Cloud Connect infrastructure. These include:
- Verify system compatibility
Confirm supported operating systems and system requirements are met for all Cloud Connect components, including the Cloud Connect server, gateways, repositories, and database hosts.
https://helpcenter.veeam.com/docs/vbr/userguide/system_requirements.html#backup_server_windows
- Take the VM snapshots with application consistent
Create snapshots of all critical servers such as the Cloud Connect VBR server, cloud gateways, and database servers. This is strongly recommended in production as an extra rollback layer.
- Back up the Veeam configuration
Export the VBR configuration from the Cloud Connect server. This is your primary rollback safety net if anything unexpected happens.
- Back up the Veeam database
Take a full backup of the VBR configuration database.
• If using PostgreSQL, take a full pg dump.
• If using SQL Server, take a full SQL backup.
- Confirm tenant version readiness
Make sure all tenant VBR servers are on the minimum supported build compatible with Cloud Connect v13. Tenants on older builds will fail after the provider upgrade. You will also see the tenant list during the Configuration Check stage.
- Put Cloud Connect into maintenance mode
Once preparation is complete and your maintenance window begins, put Cloud Connect into maintenance mode so tenant activity is controlled and predictable. Maintenance mode lets any in flight backup or backup copy task complete cleanly, so data already being written to cloud repositories is not cut off mid stream. After that, new tenant jobs cannot start and any new attempts fail fast with a clear maintenance message
This gives you a safe upgrade window. You avoid partial restore points, prevent new sessions from landing on services that are about to restart, and tenants see an explicit notice that the platform is under scheduled maintenance instead of random connection errors.
To enable Maintenance Mode from the VBR console Right Click on the Cloud Connect top level tree item and click on Maintenance Mode
Read the message and click Yes
Once completed you should see the following status in the Cloud Connect menu tree
Starting the upgrade
The setup wizard prompted to update Microsoft .NET Hosting 8.0.21.
After .NET 8.0.21 installed successfully, proceeded with the upgrade.
Read and Accept License Agreement
Provide License File
VBR 13 simplifies licensing during upgrade. Instead of manually downloading and uploading a license file, you can sign in to your Veeam account from the wizard and install a license directly.
You can still browse and install a local license file if required. Just ensure the license matches the correct product version.
System configuration check
At the System Configuration Check step, the wizard verifies required software components. If anything is missing, the setup installs it automatically. After installation, a reboot may be required. Click Reboot, then restart the setup and continue.
Once the VM is rebooted and online, Start the VBR setup again, Accept the agreement -> License details -> Perform Configuration Check
Configuration Check
During Configuration Check, VBR scans your environment for anything that will not survive the move to v13. This helps prevent breakage after the upgrade.
Pay close attention to warnings about removed features.
Deprecated features
-
Restore point based retention
Earlier you could set retention as “keep 30 restore points” instead of “keep 30 days.” In v13, you cannot configure restore point based retention for new jobs. New jobs must use time based retention. -
Reversed incremental backup mode
This mode kept the most recent backup as a full, with older restore points as incrementals. In v13, you cannot create new jobs with reversed incremental mode. Existing jobs may continue to run, but plan to migrate to forward incremental with periodic fulls. -
Single storage backup format option
Earlier you could choose the older single chain format at repository level. In v13, this format is no longer available for new repositories or jobs. The supported default is per machine backup chains. -
Active Directory based authentication for new Cloud Connect tenants
Earlier tenants could authenticate using AD users and groups. In v13, AD based authentication cannot be enabled for new tenants. New tenants must use local Veeam accounts or other supported methods. Existing AD based tenants are not forced to change immediately, but no new AD based tenants can be created.
Discontinued features
These are fully removed.
-
Universal Application Item Recovery wizard (U AIR)
The generic multi app item recovery wizard is removed. Use application specific recovery options instead. -
Starting restore by double clicking VBK or VBM in Windows Explorer
This shortcut is removed. Restores must be initiated from the Veeam console. -
Burning Recovery Media to CD, DVD, or BD
The built in burn option is removed. You can still create ISO or USB recovery media and burn using another tool if needed.
Unsupported operating systems
The Configuration Check also flags managed servers running unsupported Windows versions. Upgrade or remove those servers first, then click Retry to confirm everything is compliant before proceeding.
Unsupported tenant versions
Unsupported tenant version is one of the most critical checks in a Cloud Connect upgrade because it directly affects tenant backup continuity. Tenants on old builds cannot communicate with the provider once you move to v13. After the upgrade, their backup copy jobs, backup to cloud repository jobs, and restore portal operations will fail until they upgrade. This impacts all Cloud Connect traffic, including agent backups, Cloud Connect backup, and Cloud Connect replication if used.
Export or copy the tenant list and contact each tenant to confirm their current build, then schedule their VBR and agent upgrades as soon as possible.
Cloud Connect v13 is backwards compatible with the following tenant versions:
• Veeam Backup and Replication 12.3.2.3617 and later 12.3.2 builds
• Veeam Agent for Windows 6.3.2 and later
• Veeam Agent for Linux 6.3.2 and later
• Veeam Agent for Mac 2.3.1 and later
Review the list of Veeam components and plug ins that will be upgraded, then confirm before clicking Upgrade.
Select Update remote components automatically if you want gateways, proxies, and repositories upgraded automatically after the core server upgrade. Otherwise, VBR will prompt you to update them at first launch.
Upgrade execution
You will see the upgrade progress through six stages:
-
Upgrading Veeam Backup and Replication Server
Updates core VBR services, binaries, and configuration. -
Upgrading Veeam Backup and Replication Console
Updates the admin console to match the server version. -
Upgrading Veeam Explorers
Updates application explorers like AD, Exchange, SQL, Oracle, and SharePoint. -
Upgrading Veeam Agents redistributables
Refreshes Windows and Linux agent packages available for push install. -
Upgrading plug ins for Veeam Backup and Replication
Updates platform and integration plug ins such as VMware, Hyper V, Nutanix, Entra ID, and others. -
Finalizing installation and starting services
Completes cleanup and restarts all Veeam services on v13.
Upgrade completed successfully.
Launch the V13 console
View the certificate and install them locally
I really love the new UI look!
Post upgrade checks
After the upgrade:
• Confirm all Veeam components, including gateways and repositories, are updated and online.
• Verify all Cloud Connect services are running.
• Disable Cloud Connect maintenance mode.
• Confirm gateways are online and listening on required ports.
• Spot check repository writes and metadata updates.
• Run a tenant backup through a gateway and confirm a new restore point is created.
• Perform a restore test from Cloud Connect backups.
Hope this walkthrough helps you plan your v13 Cloud Connect upgrade with confidence and minimal tenant impact.
