- Posts: 56
- Liked: never
- Joined: May 12, 2014 2:05 pm
I cannot see anything in VBR but i can see that the backup user account is accessing the vCenter exaclty at the time when this is happening.
Also the snapshot creation fails and then it runs again 4hrs later, so i have VMs that has like 170 failed snapshots and all of the VMDK-files are around 20MB.
And i can see on the VM that the hard disk vmdk file name changes every time this happens.
So vmdk filename ends with "000218.vmdk"
One example is:
"Consolidate virtual machine disk files, The virtual disk is either corrupted or not a supported format."
"Consolidate virtual machine disk files, An error occurred while consolidating disks: 38 (Function not implemented)."
Veeam backup says this on one of the jobs: "has stuck VM snapshot, will attempt to consolidate periodically "
When looking at the datastore on this VMs i can se all the small vmdk-files.
Also, This 2 VMs is on 2 completley different systems.
Different backup servers, different versions, different version of ESXi and so on.
Different storage etc.
Anyone else that has seen this behavior in Veeam backup?
it looks like there is some built in task scheduler that i cannot see
- Veeam Software
- Posts: 4307
- Liked: 355 times
- Joined: May 19, 2015 1:46 pm
Please double-check if any other software aside Veeam could access the hosts, and contact our support team directly so they can take a closer look at your setup. Once you do please post your case ID in this thread.
Users browsing this forum: No registered users and 27 guests