Restore configuration backup from v12 to v13

[I_am_I]

Hi,

We have a customer who has VBR V12 running on a Windows 2016 server. We will replace this server by a new Windows 2025 server and migrate VBR to this new server. Is it possible to install V13 on the new server and use the configuration backup from the V12 server or should both VBR versions be the same on the old and new server?

[Mildur]

Hi I_am_I,

It depends.

For the same database engine (MSSQL to MSSQL or PostgreSQL to PostgreSQL), the VBR build of the target backup server can be the same or higher.
However, if you want to switch the configuration database engine (e.g. MSSQL to PostgreSQL), both backup servers must be on the exact same version.

Best,
Fabian

[tyler.jurgens]

Fabian is correct, of course!

I'd suggest from a change management perspective that you don't try to do both at the same time. While no one expects issues to arise if you follow the outline Fabian provided, I always recommend to make one change at a time. Eg: Do a backup of the V12 configuration on the Windows 2016 server and restore the configuration to a new V12 install on the Windows 2025 server. You can also switch to PostgreSQL at that time if you aren't on PostgreSQL already. Then you can validate your V12 install is working as expected, with the server properly scoped for V13 recommended specs. You have an easy rollback at that point as well if the unexpected happens. Once you're at a good, stable state, you would then upgrade your Veeam V12 to V13.

You get a solid baseline after each change to validate if the change was successful. Items like AV or GPOs may behave differently on each OS, which can cause a kerfuffle. It is always tempting to change everything at once and be done with it, but if you do you're left with a question of "Wait, what was it that broke this thing?" if something goes wrong. I'm a big fan of the making the smallest amount of changes you can do at one time. It will save you many headaches in the future.