Comprehensive data protection for all workloads
- Posts: 21
- Liked: never
- Joined: Jun 08, 2010 1:37 pm
- Full Name: Vyacheslav Frolov
VeeamAgent.exe use 100% of all CPUs while waiting for removing "VEEAM BACKUP TEMPORARY SNAPSHOT".
It's well noticeable when a snapshot takes a long time for removing (after replicating a big VM with high disk activity).
I use VB&R v.230 + vSphere 5 patch on WinXP SP3. Network mode. VMware tools quiescence and VSS are disabled.
Is it known ussue?
- SVP, Product Management
- Posts: 28222
- Liked: 5007 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
I believe, these 2 issues are unrelated. Get an updated agent version from our support, this should address high CPU usage issue after original vSphere 5 patch. As for snapshot commit, basically it is normal for large snapshots to take long time to commit (as lots of blocks need to be copied over and committed into VMDK). Thanks!
Users browsing this forum: Baidu [Spider], jhoughes and 41 guests