I'm getting a the following warning on 2 of my my Veeam Backup and Replication Jobs:
[Warning] VM all stuck VM snapshot consolidation attempts have failed.
Most likely reason is a virtual disk being locked by some external process. Please troubleshoot the locking issue, and initiate snapshot consolidation manually in vSphere Client.
When I try to manually consolidate the snapshots, I get error: Failed - Unable to access file since it is locked.
Also, when I look at the 2 VM's in vSphere Client, I'm also getting error, "This virtual machine needs to have it's disks consolidated. You should consolidate disks to improve performance and optimize disk utilization.
I've just checked to see if there were any Snapshots on the 2 VM's and there were no Snapshots. It just says you are here.
Any help in this situation would be most appreciated.
Please have a read of my EE Article to manually check if the VM has a snapshot attached
HOW TO: VMware Snapshots :- Be Patient
and then we can discuss how to deal with it correctly, and that is not to delete it from the datastore browser, or use the consolidation option!
So check now, oh and do not rely on the Snapshot function, to check!
So, you've not been checking, so lesson learnt, let's move on.
Okay, so what we need to try is the following...
Can you check your Veeam Backup and Replication server, and check it does not have any of these VM parent disks attached to it ?
Hopefully, I'm looking in the right area.
Is Veeam installed on a virtual server ?
Edit the Veeam Backup and Replication VM Settings, look at the virtual disks attached to the Veeam VM server.
We have 2 ESXi Servers (ESXi1 and ESXi2)'
The Veeam Backup & Replication Server (on EXSI1) is used for Backup only and is attached to a USB External Storage Device (for Backups only ) and the 2 VM's data are stored on the Datastore1.on the ESXi1 server.
Also, the Veeam Backup & Replication Server (on ESXi2) is used for Replication only and is attacked to the Datasstore1 on the ESXi2 server and the 2 VM's replication also attached to Datastore1 on the ESXi2 server..
You need to check in the disk settings of the Veeam VM include any VM disks of other VMs it has not unmouted, before we can proceed
Right Click the Veeam VMs, and select Edit Settings, and Look a virtual disks
and check they do not have the 134/135 parent disks attached.
the procedure you did for the VMs which are being backed up
for the Veeam VMs to check the disks.
I was able to Consolidate the vm's.
but maybe didn't work ?
Can you check the Veeam virtual server, and just check in the VM Settings, it does not have any of the parent disks connected ?
it should only have Veeam server disks connected to it.
and then I'm going to need a screenshot to listing of the VM folder of all the files for VM-135