After v11 upgrade all backup and replica jobs fail

[Eddo]

Hello all,

I already opened support ticket 04683729 for some help.
Maybe someone has an idea that I can try to fix this problem asap .

After upgrading to v11 yesterday all backup and replica jobs fail.
Our customer has 2 office locations with 2 ESXi servers (version 6.7.0, 17167734) and a physical vCenter Server at each location.
Our own office is running a Veeam Enterprise Manager installation and offsite repository for the offsite copy jobs.
Both locations are having the same problem and same error.
The only error I could find was a certificate error when verifying access to the ESXi servers. Exactly described in:
https://helpcenter.veeam.com/docs/backu ... ml?ver=110

The backup or replica job starts, a snapshot is taken and after that the job fails when trying to read the disks in the vm.

This is the error in Veeam:

6-3-2021 11:46:09 :: Error: Failed to open VDDK disk [[ESX01HED RAID10 SSD] WatchGuard Dimension_1/WatchGuard Dimension_1.vmdk] ( is read-only mode - [true] )
Logon attempt with parameters [VC/ESX: [VCHED];Port: 443;Login: [administrator];VMX Spec: [moref=vm-10513];Snapshot mor: [snapshot-12962];Transports: [nbd];Read Only: [true]] failed because of the following errors:
Failed to open disk for read.
Failed to upload disk. Skipped arguments: [vddkConnSpec>];
Agent failed to process method {DataTransfer.SyncDisk}.

Thank you,
Edwin van der Veen
The Netherlands

[Gostev]

Hi Edwin,

I'm afraid this one would be an environment-specific issue which may not even be related to v11.

I've got a summary of top issues since launch from support management just a couple of hours ago, and nothing there matches the above description. While all major regressions pop on our radar almost immediately due to many similar support cases opened, especially those that cause "all backup and replica jobs fail"

Our support engineers will help you to troubleshoot the issue. Issues when "nothing works" are typically the easiest ones to solve anyway!

Thanks!

[Eddo]

Hello Gostev,

Thanks for having a look in the known issues summary.
We will wait for support to contact us.

Edwin

[Eddo]

Hello all,

The problem is solved. I had to disable IPv6 on the machine running Veeam.
I unchecked the IPv6 option in the NIC settingds but that wasn't enough.

A support engineer added the setting below in a remote session at the machine.
This setting disables all IPv6 communication on the NICs.

Code: Select all

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip6\Parameters]
"Dhcpv6DUID"=hex:00,01,00,01,25,c9,f6,15,e8,d8,d1,52,07,16
"DisabledComponents"=dword:000000ff

Thanks for the support!
Edwin