← ← Back to all products
Proxmox Backup Server
Active
OtherLatest Version: 4.2Latest Release: Apr 29, 2026
Support summary
Proxmox Backup Server 3 reaches EOL in 68 days. Start upgrade planning and compatibility testing now.
What do EOL and support statuses mean?Next EOL
Aug 31, 2026
Proxmox Backup Server 3 · 68 days left
Supported cycles
2
0 lts
Versions
4
Latest Version
4.2
Active Support
2
EOL
2
Lifecycle Timeline
Today ↓
4
4
3
3
2
2
1
1
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 4 | Aug 6, 2025 | Yes | No | 4.2 | No | Active |
| 3 | Jun 28, 2023 | Yes | Aug 31, 2026 | 3.4 | No | Active |
| 2 | Jul 13, 2021 | No | Jul 31, 2024 | 2.4 | No | EOL |
| 1 | Nov 11, 2020 | No | Sep 30, 2022 | 1.1 | No | EOL |
Data sources
Sources
Frequently Asked Questions
Which versions of Proxmox Backup Server have reached end of life?
The following Proxmox Backup Server versions have reached end of life and no longer receive security updates: 2, 1. It is recommended to upgrade to a supported version.
Is it safe to continue using Proxmox Backup Server 2?
Proxmox Backup Server 2 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Proxmox Backup Server?
The latest version of Proxmox Backup Server is 4.2, released in the 4 release cycle.
How many versions of Proxmox Backup Server are currently supported?
Proxmox Backup Server currently has 2 actively supported version(s): 4, 3.
When does Proxmox Backup Server 4 reach end of life?
Proxmox Backup Server 4 does not have a specific end-of-life date announced yet.
What should I do when Proxmox Backup Server reaches end of life?
When a Proxmox Backup Server version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.