Discussions specific to the VMware vSphere hypervisor
Post Reply
ferrus
Veeam ProPartner
Posts: 246
Liked: 31 times
Joined: Dec 03, 2015 3:41 pm
Location: UK
Contact:

Windows 2019 incompatible with VMware quiescence?

Post by ferrus » Sep 11, 2019 2:35 pm

Has anyone come across this issue? https://kb.vmware.com/s/article/60395

We're preparing a Win 2019 gold image, and have run into problems performing basic VMware operation (cloning).

That led us to the article above, that seems to suggest that VMware quiescing, is now incompatible with Windows 2019.
The options are to disable it, or migrate to using legacy MBR disks.

This won't affect us too much, in our current environment - but if we need to introduce a Windows 2019 VM with a non-VSS aware DB (MySQL, Postgres etc) - what are the options? Just pre and post job scripts, rather than pre-freeze/post-thaw?

Gostev
SVP, Product Management
Posts: 24638
Liked: 3467 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Windows 2019 incompatible with VMware quiescence?

Post by Gostev » Sep 11, 2019 3:10 pm

With Veeam, you can use pre-freeze and post-thaw scripts that do not rely on VMware Tools quiescence

ferrus
Veeam ProPartner
Posts: 246
Liked: 31 times
Joined: Dec 03, 2015 3:41 pm
Location: UK
Contact:

Re: Windows 2019 incompatible with VMware quiescence?

Post by ferrus » Sep 11, 2019 3:21 pm

Ah - I thought the pre-freeze and post-thaw scripts relied on successful VMware quiescence, for some reason.

So the loss of VMware quiescence for Windows 2019 - do we just lose general in-guest housekeeping then? Flushing disk caches, etc?

Gostev
SVP, Product Management
Posts: 24638
Liked: 3467 times
Joined: Jan 01, 2006 1:01 am
Location: Baar, Switzerland
Contact:

Re: Windows 2019 incompatible with VMware quiescence?

Post by Gostev » Sep 11, 2019 3:37 pm

Well, you're not incorrect with that impression as VMware Tools quiescence provides similar pre-freeze and post-thaw scripts functionality. Just harder to use, as you have to deploy and update those scripts on every VM on your own somehow.

However, Veeam does not rely on VMware quiescence for anything at all.

And no, you don't lose anything at all: it's just a question of your script (for example, normally you should call flush as the last line of your custom pre-freeze script).

Post Reply

Who is online

Users browsing this forum: ACW, foggy and 16 guests