Problem backup after upgrade vcenter to version 6.7 Update 3o (6.7.0.50000)

[baronej]

Hello Everyone,
last sunday we upgraded our vcenter 6.7 to the last version (vCenter Appliance 6.7 Update 3o (6.7.0.50000) Release Date: 2021-09-21 VAMI:18485166.
We also upgraded our version of Veeam to the last 10.0.1.4854 (P20210609).

When we try to backup our vCenter at the end there is a problem in removing snapshot of the VM (VM snapshot stucks at 0%)

Here is the report:

Code: Select all

vcsa_clean 	Warning 	14:06:50 	14:28:43 	319,6 GB 	319,6 GB 	68,4 GB 	0:21:52 	Removing VM snapshot... (0% done)
Removing VM snapshot Details: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond XXX.XXX.XXX.XXX:443

The return job return a warning

The vCenter restart without snapshot and the vmotion option are greyed out.

To solve the problem of greyed out we follow with success the KB of VMware:
https://kb.vmware.com/s/article/1029926

Please help. We cannot backup our vCenter!

Do you know if passing to the new release veeam 11 we resolve the problem? Thanks

[baronej]

The problem is present ONLY for our vCenter.
The other vm's are backed up successfully.

[veremin]

What's your support ticket Id for this issue (it's requested when you create a New Topic)? Thanks!

[baronej]

Yesterday we opened a ticket.

The answer:
This problem is encountered very often as the vCenter has to manage the creation and deletion of the snapshot of itself.
I kindly ask you to do the following test:

- Add the ESXI host where the VCSA resides in Veeam as a stand alone
- Edit the vCenter backup job, disable VMware Tools Quiescence and Application-Aware Processing and Guest File System Indexing and add the VM vCenter from the stand alone host.
In this way, the ESXI Host will manage the creation / commit of the snapshot.
- Run the job

We did it and it works!

The only thing i don't like is that since we got a used ESXi in our cluster (where the vcsa lives), when i add it as standalone server veeam tells me: the server already exists.
So we added the server with its IP address. It doesn't matter because now we can backup our vCenter.
In the job we excluded all backup proxies (it didn't work) and used the veeam's own Veeam Backup Proxy.

Thanks to support.