Ask the Community
Groups
An error occurred while saving the snapshot: msg.snapshot.error-QUIESCINGERROR - Connect IT Community | Kaseya
<main> <article class="userContent"> <h2 data-id="issue"><strong>ISSUE</strong></h2> <p>To resolve the following error on VMware 6.0 </p> <pre class="code codeBlock" spellcheck="false" tabindex="0"> An error occurred while saving the snapshot: msg.snapshot.error-QUIESCINGERROR</pre> <br>Generally, you will see the attempt to create a snapshot, but the operation fails when it reaches about 30% completion.<h2 data-id="resolution"><strong>RESOLUTION</strong></h2> <p></p> <p><b>RESOLUTION 1</b>: For VMware 5.5: VMware <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Fcmd%3DdisplayKC%26externalId%3D2069952">KB 2069952</a>: “<a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Fcmd%3DdisplayKC%26externalId%3D2069952">msg.snapshot.error-QUIESCING-ERROR” in vCenter Server (2069952)</a>"<br><br><b>RESOLUTION 2:</b> For VMware 6.0: Apply Patch from <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D2147328">KB 2147328</a>: "VMware ESXi 6.0, Patch Release ESXi600-201610001 (2147328)"<br>This is the latest VMware 6.0 Patch. It include previous fixes to correct known Change Block Tracking and Snapshot bugs.<br><br><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=https%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Flanguage%3Den_US%26cmd%3DdisplayKC%26externalId%3D2147328">https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2147328</a><br> </p> <p><strong>Release Date</strong>: Oct 17, 2016</p> <br><strong>Download Filename</strong>:<br>ESXi600-201610001.zip<br> <br><strong>Build</strong>:<br>4510822<br> <br><strong>Download Size</strong>:<br>366.5 MB<br><br><strong>md5sum</strong>:<br>834a5d543c5b059daa7bedeb34c64f4f<br> <br><strong>sha1checksum</strong>:<br>edb061c7af236b569920f21b47dc7e65297431e6<br><strong>Host Reboot Required</strong>: Yes<br><strong>Virtual Machine Migration or Shutdown Required</strong>: Yes<br><br><strong>Bulletins</strong><br> <p> </p> <table cellpadding="3" style="margin: auto; border-spacing: 0px;"><tbody><tr><td colspan="1" rowspan="1" style="width: 40%;"> <p style="text-align: center;">Bulletin ID</p> </td> <td colspan="1" rowspan="1"> <p style="text-align: center;">Category</p> </td> <td colspan="1" rowspan="1"> <p style="text-align: center;">Severity</p> </td> <td colspan="1" rowspan="1"> <p style="text-align: center;">Knowledge Base Article</p> </td> </tr><tr><td colspan="1" rowspan="1">ESXi600-201610410-BG</td> <td colspan="1" rowspan="1">Bugfix</td> <td colspan="1" rowspan="1">Important</td> <td colspan="1" rowspan="1"><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fkb%2F2147329">2147329</a></td> </tr></tbody></table><p> </p> <p style="text-align: center;"> </p> <p><strong>Image Profiles</strong></p> <table cellpadding="3" style="margin: auto; border-spacing: 0px;"><tbody><tr><td colspan="1" rowspan="1" style="width: 44%;">Image Profile Name</td> <td colspan="1" rowspan="1" style="width: 39%;">Knowledge Base Article</td> </tr><tr><td colspan="1" rowspan="1">ESXi-6.0.0-20161004001-standard</td> <td colspan="1" rowspan="1"><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fkb%2F2147330">2147330</a></td> </tr><tr><td colspan="1" rowspan="1">ESXi-6.0.0-20161004001-no-tools</td> <td colspan="1" rowspan="1"><a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fkb%2F2147331">2147331</a></td> </tr></tbody></table><p> </p> <p>For information on patch and update classification, see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fkb%2F2014447">KB 2014447</a>.</p> <br> <h2 data-id="cause"><strong>CAUSE</strong></h2> <p>Unitrends use VMware's supplied APIs to give us the ability to request data blocks for a Guest VM for our backup. VMware then performs what it deems necessary (Snapshot/HotAdd) to provide the requested data (usually, changed blocks only) to our Unitrends solution. VMware will then provide to us, instructions for what data to collect and we then provide to VMware the confirmation of what we collected. When VMware confirms the checksum, the job is marked as successful on the Unitrends recovery console Administrative Interface and in your email reports, and VMware completes its process of returning the Guest VM to its original configuration.<br><br> </p> <h2 data-id="notes"><strong>NOTES</strong></h2> <p>Questions relating to these patches should be directed to VMware Support (see <a rel="nofollow" href="/home/leaving?allowTrusted=1&target=http%3A%2F%2Fkb.vmware.com%2Fselfservice%2Fmicrosites%2Fsearch.do%3Fcmd%3DdisplayKC%26externalId%3D2006985">How to file a Support Request in My VMware</a>).</p> </article> </main>