VBR out of place upgrade from V11 to V12

[storageguy]

Hi,

We are planning to upgrade our VBR server from V11a to V12. Currently our VBR V11 server is in our Primary site and we are planning to put our new VBR V12 server in the Secondary site. The current VBR V11a server is on Windows 2016.

Our plans are:
1. Install a new Windows 2022 Server in our Secondary site.
2. Backup the configuration of our current VBR V11a server.
3. Install the new VBR V12 server to the new Windows 2022 in the Secondary site.
4. Restore the configuration of the VBR V11a server to the new VBR V12 server in the Secondary site.

Does the above scenarios are the proper way to do an out-of-place upgrade of the VBR from V11a to V12?

Thanks

[tyler.jurgens]

Only question I have is if you can import an 11a config into a 12 server. To be super safe, you could install the same 11a build on your 2022 server and import the config there, then do an in place v11 -> v12 upgrade.

[karsten123]

Just be aware: you cannot restore a 11 config to a 12 postgresql.

[ATDCO]

I would hold off with V12 until its next release or patch.
Just my opinion.

[Gostev]

Literally just shipped one

[ibarizz]

Just be aware: you cannot restore a 11 config to a 12 postgresql.

Is this true? Is there any official statement regarding this?

[karsten123]

it is documented in the helpcenter section for restore configuration backup under limitations, i think.

[Gostev]

Correct, it's all documented in the configuration restore section of the User Guide > Before You Begin

The correct way to do this is to upgrade to V12 in-place first and create a new configuration backup in V12. This new backup created from the V12 install on Microsoft SQL will be restorable to a V12 install on PostgreSQL.

[f.neumann]

Hi Gostev,

The correct way to do this is to upgrade to V12 in-place first and create a new configuration backup in V12. This new backup created from the V12 install on Microsoft SQL will be restorable to a V12 install on PostgreSQL.

Results in Error Message, containing the exact same version number:


So not completely supported right now?

[Gostev]

It's fully supported. The error message says you don't have P20230718 installed on the target backup server (where you're trying to restore the configuration backup to), and rather only on the source one (where the configuration backup was taken).

Wenn doch if not, please open a support case for further investigation.