Upgrade to Veeam M365 Backup fails

[DHuppertz]

Hello together,

an upgrade from Veeam Backup v7 to v8 fails, when installing on the same server as VBR 12.2 with PostgreSQL allready installed.
Case number is 07424525, but nothing happened since last reply from support on Tuesday.

Any idea?

Kr
Dieter

[Polina]

Hi Dieter,

Have you already checked this KB https://www.veeam.com/kb4638 ?

[michaelsgcmd]

Not sure if this is the same issue but others have found when IPv6 is disabled on the NIC that anything to with PostgreSQL is failing.

veeam-backup-for-microsoft-365-f47/unab ... 95396.html

[DHuppertz]

@Polina:
Yes, everything in KB4638 wasalreay be done. But this wasn't the solution

@michaelsgcmd:
Thank you, the solution in the post worked for me: enabling IPv6 solved the problem.

My question now: must it be enabled for ever or could it be disabled again after upgrade?

Kr
Dieter

[mjr.epicfail]

Makes me wonder if psql connection to localhost is configured to use ipv6 instead of ipv4 on windows.

[DHuppertz]

Here the answer from support:
Hello Dieter,
Thanks for the update.
IPv6 must be enabled ever because in version 8, IPv6 host validation is used for the connection to PostgreSQL. As soon as you have it disabled, it won't be able to reconnect.
Kind Regards,
Marcos Sousa
Veeam Support

[DHuppertz]

And one more explications about the issue from support:
When PostgreSQL is already installed/in use, we automatically assume that Veeam Backup & Replication uses the IPv4 connection, and to not damage anything we switch to IPv6.
Kind Regards,
Marcos Sousa
Veeam Support

[mjr.epicfail]

So its like I thought.

@Polina, can you elaborate a bit on why the IPv6 was chosen for validation while IPv4 is valid as well?
In most hardening you will disableIPv6 when not in use.

[karsten123]

for windows os, disable ipv6 is never a good idea. microsoft requires it for internal stuff.

[stevepogue]

We opened a case as well and discovered that we had to enable IPV6.
Did some research into PostGreSQL and discovered that you can make it communicate on IPV4.
Edit the postgresql.conf file in Program Files\PostGreSQL\15\data and change this line:
listen_addresses = '*'
to
listen_addresses = '0.0.0.0'

The PostGreSQL documentation states that this makes it communicate on IPV4 addresses.

After the above change. Restart service and then remove IPV6 from the adapter

[ITP-Stan]

for windows os, disable ipv6 is never a good idea. microsoft requires it for internal stuff.

For domain controllers and Exchange servers you are correct.
For other servers it's fine, unless some specific software configuration needs it.

Removing the binding from the adapter is not the correct way to disable.
You have to change it in the registry.
https://learn.microsoft.com/en-us/troub ... in-windows