Discussions specific to the VMware vSphere hypervisor
Post Reply
Posts: 20
Liked: never
Joined: Dec 03, 2018 9:09 am
Full Name: lazman

Quiesce fail on Windows Server 2019

Post by lazman » Mar 26, 2019 5:23 pm

i have esxi 6.7u1 and veeam B&R 9.5 u4

I'm doing tests with standard Windows Server 2019.
If I try to take a snapshot of the 2019 VM, select: Quiesce guest file system (needs VMware Tools installed).
It gives me an error and does not take the snapshot. I have installed the VMware tools 10.3.10.

I asked VMware for assistance and one of their technicians removed the VMware tools part called "Volume Shadow Copy support". Showing me what time the VM quiesce is now.

My question is:
If veeam needs the VMware tools to temporarily install its "agent" when backing up, and then remove it once the backup is finished, how can I tell if the backup is consistent? I don't want my servers backing up by turning off the power.

Thank you

SVP, Product Management
Posts: 24785
Liked: 3513 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Quiesce fail on Windows Server 2019

Post by Gostev » Mar 27, 2019 12:49 am

Hello! Partly because of the numerous issues with VMware Tools quiescence (especially in early days), Veeam offers a proprietary engine to ensure backup consistency, which is called "application-aware processing". If you enable application-aware processing in the job settings, and make sure you have the option "Require successfull processing" selected, you can be sure your backup is consistent (as otherwise, VM processing will simply fail). Thanks!

Posts: 1
Liked: 1 time
Joined: Apr 11, 2019 4:00 pm
Full Name: Sebastien BLANCHET

Re: Quiesce fail on Windows Server 2019

Post by blanchet » Aug 13, 2019 9:47 am 1 person likes this post

There is a workaround to use VMware Tools quiescing with Windows Server 2019.

The problem comes from the GPT partition table and the hidden partition recovery. When removing this partition, snapshot with quiescing works correctly.

  • Backup the vm with VeeamZip (in case you do a mistake)
  • Delete the hidden recovery partition with diskpart (this recovery partition is useless because you already have Veeam to recover the vm)

    Code: Select all

    select disk 0
    select partition 1
    delete partition override
  • Reboot the vm to check that everything is ok

    Code: Select all

    shutdown /r /t 0
  • Create a Veeam backup job with VMware quiescing enabled
  • Run the backup job, and check that everything works as expected

This procedure has been validated on the following virtual infrastructure
  • VMware ESXi, 6.7.0, 13006603
  • Veeam Backup & Replication 9.5u4
  • Windows Server 2019 v1809

Post Reply

Who is online

Users browsing this forum: nsimao and 13 guests