Introduction

Veeam Backup and Replication v13.0.1 supports a direct in-place upgrade from v12.3.1 build 12.3.1.1139 or later on Windows. The installer runs a hard configuration check before the upgrade proceeds and will stop on several specific conditions. This post summarizes the full upgrade process -- blockers, deprecated features, platform changes, component order, wizard walkthrough, and known post-upgrade issues -- based on the official Veeam documentation and confirmed community experience. Full article with expanded tables and PowerShell references at anystackarchitect.com.

Supported Upgrade Path

Direct in-place upgrade to v13.0.1 requires v12.3.1 build 12.3.1.1139 or later. See KB4763 for the official version requirement. If below that build, update to v12.3.1 first (KB4696), then upgrade to v13.

Hard Upgrade Blockers -- Must Resolve Before Running Installer

These are red items in the Configuration Check (Step 6 of the wizard). The installer will not proceed past them. Source: official Veeam upgrade checklist.

Deprecated Features (Functional on Existing Jobs, Not Available for New Jobs, Removed in v13)

• Reversed incremental backup mode -- use forward incremental with synthetic or active full

• Restore-point-based job retention -- switch all jobs to day-based retention

• Non per-machine backup chains (single-storage format) -- per-machine only for new jobs and repos

• AD-based authentication for Cloud Connect tenants -- existing tenants unaffected; new tenants must use local users or MFA

• VBK/VBM double-click restore from Windows Explorer -- initiate restores from the console

• Sequential tape processing option -- parallel is default; automatic fallback to sequential on single drive

• Managed Hardened Repository v2 -- upgrade via Veeam Infrastructure Appliance for continued security updates

• Recovery Media to CD/DVD -- use ISO or USB

• Agent job retention by restore point count -- switch to day-based

• Agent configuration import/export to/from XML

Platform and OS Changes

• VMware vSphere: minimum 7.0 -- vSphere 6.x dropped entirely

• VMware vCloud Director: minimum 10.4 -- versions through 10.3 dropped

• Hyper-V: minimum Windows Server 2016 -- 2012 and 2012 R2 dropped

• Guest OS (application-aware processing): 64-bit only -- 32-bit dropped. Crash-consistent host-level backup still works for 32-bit guests.

• Microsoft SQL Server (config DB): minimum SQL Server 2016 -- 2012 and 2014 dropped

• Linux: RHEL 7 dropped, RHEL 8.4+ minimum; Fedora dropped entirely; Rocky/Alma 9.4+ minimum; Debian 10 dropped

• Nutanix AHV: minimum 6.8

Non-blocking warning: managed servers on unsupported OS versions do not block the upgrade but cause immediate job failures afterward. Resolve before upgrading.

Database and PowerShell

PostgreSQL and SQL Server

PostgreSQL 17.6 is bundled and is the default for new v13 installs. SQL Server 2016 through 2025 remains supported. If upgrading from v12 with an existing SQL Server config DB, the installer upgrades it in place -- no PostgreSQL migration required. If v12 used the bundled PostgreSQL 15 instance, v13 installs PostgreSQL 17.6 alongside it; PostgreSQL 15 is left installed and unused, and can be removed after confirming v13 is healthy.

PowerShell 7 Required

The Veeam PowerShell module in v13 requires PowerShell 7. Windows PowerShell 5.x will not load the module. Update all scripts, scheduled tasks, and monitoring integrations to use pwsh.exe before upgrading.

Pre-Upgrade Checklist (Key Items)

• Confirm source version is v12.3.1 build 12.3.1.1139 or later

• Run Veeam Configuration Backup and store .bco off the server

• Snapshot the backup server VM -- rollback option

• Stop all jobs, restore sessions, and SureBackup sessions

• Disable scheduled jobs for the upgrade window

• Resolve all seven hard blockers above

• Check managed servers/proxies for unsupported OS versions

• Verify vSphere 7.0+, Hyper-V 2016+, SQL Server 2016+ if applicable

• Install PowerShell 7 if using Veeam PowerShell automation

• Verify 55.5 GB free disk space minimum: ~50.5 GB (3x ISO size) in install path + 5 GB on system volume

• Check that port 443 is not already in use on the backup server

• Download ISO: VeeamBackup&Replication_13.0.1.180_20251101.iso (~16 GB). Check for patches newer than base build.

Component Upgrade Order

Veeam Backup for M365 -> Veeam ONE -> Enterprise Manager -> VBR Server -> Remote Components

Veeam ONE v13 supports monitoring v12 environments, so upgrade it ahead of your VBR maintenance window. Use the 13.0.1 ISO for Veeam ONE -- 13.0.0 had a known upgrade failure bug fixed in build 13.0.1.5860. Enterprise Manager must be upgraded before VBR.

Post-Upgrade Validation

• Console connects and Help > About shows 13.0.1.x

• Run at least one backup job end to end

• Re-trust managed servers flagged as untrusted in Backup Infrastructure

• Verify hypervisor connections and current inventory

• Perform a test restore to validate recovery capability

• Run the Security and Compliance Analyzer under Configuration

• Test PowerShell automation scripts under PowerShell 7

Known Issues and Fixes

VeeamBackupRESTSvc Startup Timeout

The most common post-upgrade issue. VeeamBackupRESTSvc times out on first start due to heavy initialization load. Fix: increase Windows ServicesPipeTimeout registry value to 300000ms (5 minutes) under HKLM\SYSTEM\CurrentControlSet\Control, then reboot.

Console Connection Error

If console fails to connect, wait 5-10 minutes and retry -- services may still be initializing. If persistent, confirm all Veeam services are Running and apply the ServicesPipeTimeout fix. A separate Access Denied registry error indicates a console version mismatch -- update the remote console to v13.0.1.

Port 443 Conflict

v13's REST service requires port 443. If another application owns port 443 on the backup server, VeeamBackupRESTSvc will not start. Check for conflicts before upgrading: Get-NetTCPConnection -LocalPort 443

File Copy Jobs Fail on Multi-NIC Servers

A confirmed v13.0.1 bug causes File Copy jobs to fail with a Connection forwarder not registered error on servers with multiple NICs, while Backup Copy jobs to the same target succeed. Fix: disconnect the unused secondary NIC, or set a preferred network under Configuration > Network Traffic Rules.

PowerShell Scripts Break Under Windows PowerShell 5.x

Veeam PowerShell module requires PowerShell 7. Update all script launchers from powershell.exe to pwsh.exe.

Full article with expanded tables, PowerShell references, and platform compatibility details:

https://anystackarchitect.com/veeam-v12-to-v13-upgrade