Migrating to Veeam Backup Appliance is needlessly complex

[unsichtbarre]

Howdy all,
Case # 08178159
We have read the writing on the wall for VMware and security and are very excited about migrating to the Veeam Backup Appliance, however the process is needlessly complicated/painful and will deny many users the opportunity to improve their backup infrastructure.

Mostly I am referring to the fact that https://www.veeam.com/kb4800 does not mention that after you have met all of the prerequisites, you still have to upgrade the PostgreSQL database on the Windows side prior to performing the migration!

This migration is not exactly simple in the first place and can be disruptive as you need to open a case with Veeam, then wait for the authorization key, then disable all Veeam services. This after having read the KB, only to discover you need to perform a database upgrade on Windows (migration) - which is only documented in a few places and not very well explained. Now re-enable all services and go through database migration/upgrade.

It seems to me that the process of upgrading to latest Veeam 13 (as the KB states) should also update the DB to a version supported for migration!

Thanks,
-JB

[Mildur]

Hi John

still have to upgrade the PostgreSQL database

That is new to me. Let me double check.
Are you using a on-host PostgreSQL server deployed by Windows VBR or self managed Remote PostgreSQL.

This migration is not exactly simple in the first place and can be disruptive as you need to open a case with Veeam, then wait for the authorization key, then disable all Veeam services.

Yes, for now, a case is required. We need to make sure that all configurations on the backup server are supported by VSA. We still have storage plug-ins and platform integrations that are not supported with VSA today. It would also be disruptive if less experienced customers started the migration without consulting any documentation or our support team first. That's the reason we have decided for the option through support for now.

In the future, we will open the migration process without requiring a support case. But first, we have to make sure that there are no blockers anymore, so customers can migrate just as they are used to with Windows-to-Windows migrations. This will take time and cannot be done overnight.

should also update the DB to a version supported for migration!

This is a long-standing request, and you will find topics about it in this forum. We have plans to manage PostgreSQL updates on Windows based backup server, but no ETA.

Best,
Fabian

[unsichtbarre]

Thanks @Mildur

Upgrading the Postgres database is a pretty significant omission in https://www.veeam.com/kb4800

Case # 08178159
"As per the logs of XXX.XXX-01.XXX.XXX.com server, it is running PostgreSQL 15.10 and the Veeam Software Appliance uses version 17 as per the requisites in the User Guide: https://helpcenter.veeam.com/docs/vbr/u ... 0you%20are
You need to upgrade the PostgreSQL version from 15 to 17 in XXX.XXX-01.XXX.XXX.com server before migrate the Database."

THX,
-JB

[Mildur]

Hi John,

I’m still working on confirming whether updating to PostgreSQL v17 on the source backup server is a requirement.

While I agree that VSA requires PostgreSQL v17, I do not see how that affects the database version on the source Windows server. VSA already comes with PostgreSQL v17, and it should not matter what kind of source database engine or version the Windows backup server has used. Can be MSSQL or PostgreSQL.

But as mentioned, I will clarify this in my lab and if necessary with our R&D team. I will provide you with an update when I have it.

Best,
Fabian

[Mildur]

Hi John,

I ran the test in my lab:

1.) New Windows VBR deployment v12.3.2 with PostgreSQL 15.17-1 from the v12.3.2 ISO.
2.) Windows VBR: upgraded to v13.0.2; PostgreSQL remained on v15.17-1.
3.) Deployed a VSA v13.0.2.
4.) Migrated the configuration from Windows to Linux VBR using KB4800.

As you can see in my screenshot, the migration was successful with my source Windows backup server using PostgreSQL v15.17.

Since the case is already closed and the logs were deleted, I cannot really comment on why our Support Team answered that you must upgrade PostgreSQL on the Windows backup server to v17.

I would like to repeat my question from my earlier comment. Did you use on-host PostgreSQL server deployed by Windows VBR or self managed remote PostgreSQL. Same for VSA, did you plan to use self managed remote PostgreSQL for the Software Appliance?



Best,
Fabian