VMware Cloud Community
NEET123
Contributor
Contributor
Jump to solution

unable to quiesce an application

hi,

i have my backup exec 2010 r3 running for one year without problem.  i have my production running in Vsphere 5.0 (vcenter U1 and esx 5.0 U1) still running ok.  but when i started my test esx1 5.0 and another esx2 5.0 U2 both build 914586 and i deploy Vcenter 5.0 U2.  My backup exec r3 stop running properly with error...  "An attempt to take a snapshot of a virtual machine failed because it was unable  to quiesce an application."

I have lots of testing... if i put the vm shutoff, backup will work but of course this is not acceptable...  and even if i put vm to vcenter 5.0 U1 and esx 5.0 U1, it will now fail too but rest of the prod vm are still fine.

below is just the solution from backup exec,

http://www.symantec.com/business/support/index?page=content&id=TECH136400&actp=search&viewlocale=en_...

but i'm using backup exec 2010 r3 now, it's higher than the recommended solution which is upgrade to backup exec 2010 r2.

anybody encounter this kind of problem?

thanks for any comment you may add and more power,

neetu

0 Kudos
1 Solution

Accepted Solutions
jrmunday
Commander
Commander
Jump to solution

Maybe a long shot, but here is a interesting link where this issue was resolved by correcting the host time settings;

http://payze.wordpress.com/2012/10/23/99/

Also, have you tried re-installing VM Tools on this affected guest?

vExpert 2014 - 2022 | VCP6-DCV | http://www.jonmunday.net | @JonMunday77

View solution in original post

0 Kudos
3 Replies
jrmunday
Commander
Commander
Jump to solution

Maybe a long shot, but here is a interesting link where this issue was resolved by correcting the host time settings;

http://payze.wordpress.com/2012/10/23/99/

Also, have you tried re-installing VM Tools on this affected guest?

vExpert 2014 - 2022 | VCP6-DCV | http://www.jonmunday.net | @JonMunday77
0 Kudos
NEET123
Contributor
Contributor
Jump to solution

i never thought of that... probably lots of things on my mind, just reinstalling the vmtools will do...  hayz... i will test again vsphere 5.1 but maybe end of the year...  thanks again!

0 Kudos
Lenora_BE
Enthusiast
Enthusiast
Jump to solution

Neet123, did reinstalling the vmware tools fix the problem?

0 Kudos