Any special considerations before upgrading from 11.0.1.1261 to 12?

[cosmik]

Got VBR 11a (P20230227) running under a server 2019 VM. Infrastructure is ESXi with the exception of the Backup repo which is a Debian 12 box, using fast link XFS over an iSCSI block device. Any special issues I should take care beforehand?

I'm reading https://community.veeam.com/vug-south-a ... -12-1-6361 and from the looks of it admin credentials are needed. Would I run any into issues if a different admin account is used for the upgrade, compared to the one used for the original installation (which is now disabled)?

EDIT: I could not locate the VBR 11 P20240304 patch as a standalone file, to patch to the latest v11 branch (always do so, before upgrading to a major next version. Any idea where it can be download from as a simple patch (instead of an ISO)?

[Mildur]

Hello Michael

Start with the checklist we have in our help center.
It contains all information regarding pre-checks and the upgrade itself.

You can do a direct upgrade from your "v11a (P20230227)" to "v12.3". Our pre-requisite checker in the install wizard will tell you if you have unsupported configurations for the target version:
https://www.veeam.com/kb4696

Best,
Fabian

[cosmik]

That's perfect Fabian, thanks mate

[Seve CH]

Hi Michael

Please note that v12 uses different backup chains format. Careful planning is needed if you use vSphere tags for job mapping or you will end up with incompatible jobs or new backup chains (more storage needed). If you don't use vSphere tags, just ignore this comment. But if you do...

The new backup copy jobs are incompatible with vSphere tags ("From Infrastructure" option is no longer available).
If you use vSphere tags to map VMs to backup copy jobs, you won't be able to update the backup copy chains to the v.12 format and the job will remain as legacy backup copy job (it works without problems). You won't be able to update to v.13 in the future until you migrate, but that's it so far.

BUT: The legacy backup copy job is only compatible with the old backup job format. It cannot be mixed (old->legacy, new->new, but new->legacy is not working). If you convert the backup jobs to v.12 or create new backup jobs, they won't be compatible with the legacy backup copy jobs anymore and you will need to reengineer/migrate them to v.12 backup copy jobs.

Best regards
Seve

[cosmik]

Hi Steve,

no, I'm not using any vSphere tags for job mapping.

I've just completed the upgrade, went smooth so far including the upgrade of the Veeam components running on my physical backup repo. I guess tonight it'll show whether it went ok or sideways

Now, with regard to your notes, the sole backup job seems to be in order. How can I tell whether it's in the "new"/V12 format? If it is in the old, how can I migrate it to the new one?

EDIT: found thgis https://helpcenter.veeam.com/docs/backu ... ml?ver=120 and in my console no "Upgrade backup chain format" option is offered, so I presume I'm in the clear