B&R V10: Backup errors after upgrade

[Tecbil]

Before, everything went smoothly for months.
But after upgrade from B&R 9.5u4 to B&R V10 I am not able to perform backups for every single of my 6 VMs anymore:
The BackupJob report gives for every VM and every virtual disk the same error:

Code: Select all

Preparing backup proxy VMware Backup Proxy for disk Hard disk 1 [hotadd]
Error: Agent: Failed to process method {HotAdd.AttachDisks}: Failed to open VDDK disk [[esxi03-LocalStorage-01-970evoplus_m2nvme_2tb-01] <myVM>/<myVM>.vmdk] ( is read-only mode - [true] ) Logon attempt with parameters [VC/ESX: [vcenter.<myDomain>.com];Port: 443;Login: [administrator@vsphere.local];VMX Spec: [moref=vm-1053];Snapshot mor: [snapshot-1913];Transports: [hotadd];Read Only: [true]] failed because of the following errors: 

But then it does not show what those "following errors" are.

What I've already tried:

• Removed and re-added vCenter to the B&R repository

• Deleted and re-created the whole BackupJob

• Checked whether Microsoft Visual C++ Redistributable is installed --> it is three times: 2008, 2010 and 2015-2019

• Rebooted the whole B&R server

• Checked in vCenter the following setting: <myESXihost> --> Configure --> System --> Advanced system settings --> Config.Defaults.security.host.ruissl = true

Any help would be appreciated.

[Gostev]

Hello!

Please include the support case ID, as requested when you click New Topic.

In general, this looks like some basic issue with logon to vCenter Server failing, so hopefully it should be easy for support to troubleshoot.

Thanks!

[Tecbil]

Hi Gostev

I am on Community Edition with my homelab so I don't think I can open a ticket, can I?

[Tecbil]

OK, maybe I should read the forum rules first. Sorry about that.
Here is the support case ID:
04012529

[dtang]

Good morning,
I looked at your case and saw that you have just a PDF report attached. We would require logs (according to https://www.veeam.com/kb1832), to be able to investigate further.
The error is very generic, I assume it's just a VDDK Error 13, but we need to double check.

[Tecbil]

Solved. I did all the recommended solutions from https://www.veeam.com/kb1832 which did not solve the problem directly.
In the end I just did a full shutdown of the B&R server (which is the proxy at the same time in my case), powered on again and...voilà! The problem was gone.
Not sure what it was in the end.

[Gostev]

Thanks for updating us! This is why reboot is always the first troubleshooting step for anything in IT