[V13] System Requirements for our 2025 release

[Gostev]

You won't be able to upgrade to V13 if you have unsupported ESXi versions registered in the Inventory. The upgrade wizard will detect them and refuse to continue, thus forcing you to remain on V12 while you are still using ESXi 6.x

If you do a new V13 install, you won't be able to add unsupported ESXi versions to the Inventory.

[ds_nl]

Will existing Veeam Agents (e.g. CentOS) managed through backup server just stop working after the upgrade to v13 or will there be a backwards compatibility?

That would be good to know, so it can be planned accordingly.

[Gostev]

Usually unsupported Linux versions are blocked. Maybe older agents will continue working until you update them but it's hard to predict this far out.

[ewing.ng]

Why Linux agent not support RHEL 7 ?

RHEL: dropping support for RHEL 7, RHEL 8.0 through 8.3; minimum supported version is 8.4.

I know RHEL 7 end of support in June 2024. But some application still need to execute in RHEL 7 environment.
And we already have Red hat extended support which can provide support til June 2028.

If Veeam 13 and it's Linux agent not support RHEL 7, we can't upgrade it and maintain Veeam 12 version

[Gostev]

Correct, you will need to stay on V12 in environments with RHEL7 for the time being then. That's totally fine with us and this is the very reason why we extended V12 support by one extra year from usual 3 years, allowing V13 to drops from its System Requirements lots of "old baggage" used by relatively few customers and allowing our QA to focus their attention on what's actually important - the platform versions used by vast majority of our customers.

[ewing.ng]

If we keep existing Veeam Linux agent version for RHEL 7 OS, just upgrade Veeam B&R version from 12 to 13.
We don't upgrade Linux agent version.

Pls share with us still support to backup RHEL 7 OS for physical server after Veeam version upgrade.

[Gostev]

It's unlikely to be a supported configuration with V13 due to significant platform architecture changes that old agent versions are not aware of or prepared for. Your best bet is to therefore stay with V12 until you eventually get rid of RHEL7.

[MartinDT]

Is there a reason you are dropping AlmaLinux support for Proxies / repositories?
We have a number of sites using it for the Proxy / Immutable repository copy.

[Gostev]

We made the decision to focus on Rocky of all RHEL alternatives. Notably, with V13 we plan to provide "Just Enough OS" ISO based on a special version Rocky that will be centrally managed and updated by Veeam, so it might be a better choice for running all your remote backup infrastructure components than self-managing their OS like you're doing it today.

[vmtech123]

Thanks for the info.
I keep most products pretty up to date, without pushing forward TOO hard so no issues from me. I'm a fan on dropping at least SOME support to keep applications lightweight, and costs to QA down to either enable new features or avoid crazy price increases.

If someone is using Server2012 and vSphere 6, priorities should not be updating Veeam first lol

[RubinCompServ]

@vmtech123

And then there's the guy who had a post a year ago, who was looking for assistance migrating his VMs from ESXi 4.1 to ESXi 8...

[pesos]

+1 on wanting the plug-ins (Google Cloud, AWS, Kasten, Nutanix, etc.) to be an optional checkbox during upgrade/installation. We're not currently running into space constraints on our VBR server's C drive, but it would be nice to skip installing/upgrading plug-ins for services that we don't use. Could probably also cut down the install/upgrade time if it can skip those components.

omg yes +1000

[tegroup]

Sounds great! I'm looking forward to deploying a Veeam OVH ASAP!