Interesting. Seems 2019 is not very usable server to use. I understand in this case VSS is activated by vmware tools, but interesting how about some other backup software, example Veeam installs some temporary agent that activates VSS. Or at all some non-vmware backup system, like BackupExec or Acronis.
Yep, even IBM tivoli has the problem.
After contact with VMware support, they helped us.
Conflict between VMware´s and Windows snapshot providers. Disabled VMware´s and set Microsoft´s to automatic.
After that it worked.
Thanks for good support from VMware.
Can you please provide a detailed description on how you disable the VMware snapshot provider and enable Microsofts?
i have disabled the service "VMware Snapshot Provider" and left "Volume Shadow Copy" untouched (it is set to manual per default). not sure if this is the way to go, but my test run is now ok.
I tried out the advice (disable VMware snapshot provider service) and now snapshot can be taken without an error message. However, does this not completely disable app quiescing which could leave a backup or replica of a VM in a inconsistent state? How dependable is this workaround if a failover or restore is needed for a Windows Server 2019-based domain controller or SQL server?
I have read the various discussions about the problems encountered with Windows Server 2019 and VmWare 6.7.U2 and the 10.3.10 utilities.
I have the same problems with a newly installed infrastructure! Impossible to make a "VSS" capture of the server while a simple Snapshot is working.
With a Windows Server 2016 and Windows 10 client, this solution working perfectly.
I have noticed these problems with Acronis which also uses this function of VmWare and Microsoft.
Now is the solution proposed in this article supported by VmWare, Microsoft and Acronis to ensure that backups are consistent?
If I understand correctly, I just need to disable the "VMware snapshot provider service", correct ?
Has anyone tested a restoration with this solution?
Is VmWare currently developing a patch for this problem?
Thank you in advance and good luck for the rest.
I confirmed that Veritas NetBackup and Backup Exec provides their own VSS provider named Veritas VSS Provider.
Veritas VSS provider works well for Windows2019 Guest OS to make snapshot with quiescing.
Veritas (NetBackup and Backup Exec) may only provides the consistent VADP backup for Windows2019 Guest OS now.
1 person found this helpful
Virtual Disk service is started and startup type is Automatic.
* VMware snapshot provider service is stopped and disabled.
* that VMware Tools services are running.
*Ensure that Volume Shadow Copy service start up type is Automatic
Thank you for your information.
DANAND84: So with this solution, the backups are consistent and can therefore be used?
I finally received confirmation that Acronis does not work with Microsoft W2K19 and VmWare. Strangely enough, this information was given to me just by phone.
To conclude, the problem is not with us, go your way.
Great technical support. I am aware that the problem is not with them but I think it is justified to wait for support from Acronis from VmWare.
Thank you for your comments.
The problem is with GPT partition table and hidden partition recovery. When removing this partition snapshot with quiescing work correctly. With MBR partition table work correctly:)
Workaround from me create new VM on vSphere 6.5 and move the new machine to vSphere 6.7 and snapshot with quiescing working correctly.
Support waiting for KB from Microsoft because they told - the problem is in MS Windows 2019 server not to vSphere 6.7:)
We have exactly the same issue as well. Luckily we only deployed 1 2019 server so far so we'll just be holding off until they fix this... if they fix this.
The problem is with GPT partition table and hidden partition recovery. When removing this partition snapshot with quiescing work correctly
i can confirm this.
set up a new 2019 server vm, snapshotting with quiescing fails.
removed the recovery partition with diskpart, now snapshotting with quiescing works flawlessly.
who is responsible to fix this?