Error: Failed to parse "-quiescedsnap"

[psykie]

Hi,

Just after updating our ESXi 4.1 hosts we are getting an error backing up VMs which are not using application-aware image processing. The error we are getting is this

Code: Select all

Error: Failed to parse "-quiescedsnap"

We have opened a ticket (ID#5214680) in which we were notified that a fix is on its way. The problem is a new line in the VMX config is not being parsed properly....

Code: Select all

guest.commands.sharedSecretLogin.hostd-quiescedsnap = " "

In the meantime we cannot backup around 200 of our VMs! I was wondering if there is a indicative release date/time for this fix. In the meantime I have started installing VMware data recovery to fill in the gap.

Any info is appreciated

thanks

[E.Kok]

Sorry, can't help you but Just to let Veeam know I have the same problem.

After updating our ESX 4.1 hosts and updating VMware-tools on the guests several replication-jobs stopped working with:

Code: Select all

10-9-2012 10:06:52 :: Error: Failed to parse "-quiescedsnap"

I tried completely removing one of these replica's and also deleted and recrerated the Veeam-job, all to na avail.

[foggy]

Stuart, no strict release date but, according to our QC, the fix should be available in a couple of days.

[psykie]

Thanks for the update foggy.
I can understand not rushing out the fix. What I cannot understand is not warning clients (at least through the forum) not to patch their hosts yet until the issue is solved.
The latest esxi 4.1 patches were released over 11 days ago and still no warning.

[foggy]

The fix for current version (6.1) is already available through technical support.

P.S. Perfect example of why you should always thoroughly test every update before you deploy it in production.

[Gostev]

Folks, I have just found out about this new issue - otherwise, I would have definitely included it into the weekly forum digest. I will update Known Issues sticky accordingly later today.

FYI, the update that brakes stuff is ESX(i) 4.1 build 800380. By the way, this is the first time in my memory when VMware update or patch brakes our product's functionality - usually, VMware does great job maintaining compatibility to ensure 3rd party vendors are not affected, and never add new features in those updates. What is causing the issue here is that they did add some new feature, and that cause new VMX entry to appear that is unknown to our product.

[salex]

Tell me where to get a patch to fix this problem? or tell me when will the update veeam.

[Vitaliy S.]

Hello Alex, please take a look at this topic for more details:
[KNOWN ISSUES] 6.1 : Known Issues, Patches and Hotfixes

[salex]

Thank you very much!

[JoshF]

Hi team,

Does this only affect v6.1, or does this also affect previous versions? Have applied 4.1 U3 into a Test environment and backing up machines in this environment with Veeam 6.0.0.181 and these seem to be working as expected - does this affect certain modes, or if this is an issue, it just simply doesnt work regardless of what config is set?

[foggy]

Yes, this issue affects all versions of Veeam B&R and is reproduced on the VMs that have the above mentioned entry in their configuration file. Since there are no hotfixes available for previous B&R versions, it is recommended to upgrade to v6.1 and apply the patch to avoid possible problems. Thanks.

[JoshF]

Thanks for the confirmation Foggy. Much appreciated

[Loris]

Code: Select all

guest.commands.sharedSecretLogin.hostd-quiescedsnap = " "

I commented the line above out of the vmx file and tried the backup again and it worked.

Will this cause issues later on down the track?

[Gostev]

Only with VMware, if at all.

[farge]

Hi,

Do you know if vCenter 4.1 U3 is also involved in the problem or just the ESX(i) version?

Thanks,
E.

[Gostev]

I believe, this is specific to ESX(i).

[E.Kok]

Any news yet?
I'm now a week without replication and waiting for a fix.
Come on Veeam! This is really taking too long.

[foggy]

Ed, the fix for this issue is available through technical support since September, 10.

[E.Kok]

Unbelievable that clients won't get notified about these fixes and that it can only be obtained by making a support-call.
Must be me, but I'm a little frustrated now. Sorry, about that.

[foggy]

I believe that if you had a case open with support, you would be notified immediately. Actually, you can download this patch here.

[E.Kok]

Thank you.

[Gostev]

Unbelievable that clients won't get notified about these fixes and that it can only be obtained by making a support-call.
Must be me, but I'm a little frustrated now. Sorry, about that.

Actually, information about this fix was included in the weekly forum digest. Every forum member is subscribed to the digest by default. So we do notify - and it is only your choice not to read the digests, or opt out of receiving them.

Here is the blog post about that specific digest issue. The guy actually says exactly the opposite from what you are saying:

I have to say, Veeam’s communications and openness continues to impress me. A lot of vendors would keep this information close, or tell folks that it must be something they’re doing that’s wrong, and pass the buck. While some could read the above as Veeam having issues, I see it as them being a part of the community and sharing issues as soon as they’re aware of them. This is part of the reason I really like dealing with them as a vendor!

[uharmsen]

Hallo,
is a Fix also available for B&R Version 4.1.2?

[foggy]

No. Hotfix support for this version has ended almost 2 years ago.

[paulj]

Hotfix for v6.0?

[paulj]

Code: Select all

guest.commands.sharedSecretLogin.hostd-quiescedsnap = " "

I commented the line above out of the vmx file and tried the backup again and it worked.

Will this cause issues later on down the track?

By that do you mean you just put a # in front of the line?

[paulj]

Code: Select all

guest.commands.sharedSecretLogin.hostd-quiescedsnap = " "

I commented the line above out of the vmx file and tried the backup again and it worked.

Will this cause issues later on down the track?

I found I also needed to turn off "quiesce" option and turn on "VSS" option for my sql install.

[Vitaliy S.]

Hotfix for v6.0?

You need to be running 6.1 to apply the hotfix or upgrade straight to 6.5 to resolve it.

[paulj]

Every time I have upgraded veeam (twice now) it has required me to re-create every backup job, thereby introducing 2x weeks of pain as I have start backing up every server from scratch again, so "upgrading" isn't so simple for me.

[Vitaliy S.]

Hi Paul, job recreation is not required during the upgrade, did you get in touch with our support on this?