Veeam Backup & Replication 12 End of Support: What Changes After February 2027
Veeam Backup & Replication 12 stops receiving support and security fixes after February 2027. What End of Fix and End of Support mean, and how to plan the move to version 13.
Version 12 gets its last support and security fixes in February 2027
Veeam lists February 2027 as the last month Veeam Backup & Replication 12 receives support and security fixes. Version 12 passed its End of Fix date of November 2025, so Veeam creates no new updates, patches, or hotfixes for it. It is still supported and still receives security updates until then. Version 13, released November 2025, is supported through November 2028. Because a backup server is the system you depend on after an attack, it should not run on a version that no longer gets security fixes.
Veeam Backup & Replication lifecycle dates
Dates as Veeam lists them on its product lifecycle page, checked November 2026. Veeam notes that each month shown is the last month the service is offered.
| Version | Released | End of Fix | End of Support and Security Fix |
|---|---|---|---|
| 13 | November 2025 | November 2028 | November 2028 |
| 12 | February 2023 | November 2025 | February 2027 |
| 11 | February 2021 | February 2023 | February 2024 |
What End of Fix and End of Support mean
- End of Fix: Veeam creates no further updates, patches, or hotfixes for the version. It is still supported, and security updates are still provided until End of Support.
- End of Support and Security Fix: Veeam no longer supports the version, and it receives no security updates.
- To get support after that, Veeam requires an active maintenance contract and an upgrade to a version that has not reached End of Support.
If the upgrade cannot happen before the cutoff
Some environments cannot move on schedule, usually because a protected application or hypervisor is not yet supported by the newer version. In that case, treat the backup server as an exposed system and reduce what an attacker could do with it while the upgrade is planned.
- Keep the backup server off the production domain where possible, and limit who can sign in to it.
- Require multifactor authentication for the backup console and for the accounts that can delete backups.
- Keep at least one copy offsite or immutable, so a compromised backup server cannot erase every copy.
- Set a firm upgrade date with the application or hypervisor owner, and track it like any other deadline.
Plan the upgrade to version 13
- Confirm your maintenance or subscription is active, because Veeam ties support to an active contract on a supported version.
- Check Veeam's version 13 system requirements against your backup server, proxies, repositories, and the hypervisor and application versions you protect.
- Confirm that every add-on, plug-in, and integration you use has a version 13 release.
- Back up the Veeam configuration and confirm it can be restored before you start.
- Schedule the upgrade outside backup windows, then run a test restore from each repository afterwards.
- If the backup server runs on Windows Server 2016, plan that operating system change at the same time.
See the Windows Server 2016 end of life guide and the Backup and disaster recovery.
Upgrade Veeam without a gap in your backups
Send us your Veeam version, the systems you protect, and where your repositories live. We will help you check compatibility, plan the upgrade window, and prove restores afterwards. A planning call is planning support, not a quote, an audit, or a commitment on licensing, availability, or delivery dates.
Sources
Primary sources checked when this guide was written. Dates and product status can change, so confirm on the source before you rely on them.
Related services
Related resources
Turn the checklist into a plan
The 2-minute IT quiz turns this checklist into ranked priorities for your situation, before any contact details.
