VSSControl: Failed to freeze guest.

[cag]

I tried to add application aware replication of a VM from Source to DR I get the following error.
2/28/2012 10:03:59 PM :: Unable to release guest. Error: VSSControl: Failed to freeze guest, wait timeout
This is due to the VM is my Vcenter Server.

Now if I add the ESXi host as the source instead of the vcenter server to select the VM will this break my replication job and need to start from scratch or will it just continue as before.

[Gostev]

You will need to start from scratch, but you can map the new job to an existing replica VM to avoid full sync.

[JustinCredible]

I am having this same problem with my Veeam DB being on a VM I'm trying to back up. I've increased the timeout to 30 min and that didn't help. I resolved it before by moving the database locally but I would like to avoid that and keep it on our DB server. Is there any way to accomplish this?

[Gostev]

If you are using version 6.0, do you have the latest patch #3 installed?

[daniel.Soares]

Hello
I have the same issue
using veeam B&R 6.0.0.181 64bit
I think my last patch installed is patch 2
where can I download the latest patches?

thanks

[Vitaliy S.]

You can download it from our customer support portal: http://www.veeam.com/KB1442

[daniel.Soares]

the KB says Patch 3 Release Notes for Veeam Backup & Replication 6.0.0.153
I have Veeam B&R 6.0.0.181 is that an issue?
I use 64bit version

[Cokovic]

Version 6.0.0.181 is Patch 3
So you've got the newest version of this release.

[Gostev]

Or better yet, just upgrade to 6.1

[Dotcommie]

We're currently using version 6.1, and have recently started getting the same issue. I've added the ESXi server to the VMs and added our vCenter server to the backup from that rather than from the big list.

I'm still troubleshooting ours because we have had a number of shut downs due to power that may have started this problem. Currently, only the vCenter server is causing any failures.

[foggy]

Rick, weren't you considering an upgrade to the latest version of Veeam B&R? Among huge new capabilities it provides, it also handles the process of vCenter backup more efficiently, allowing to back it up with VSS enabled without issues.

[madgonc]

I had same prolem and solved with logs delete. when logs are above 12GB, backups starts having problems with this error.
I think that is something related with high workload on disk/CPU/Mem, but I know too that is solved with logs.
This problem start yesterday when I create a new database and move about 20 mailboxes to this new exchange database. logs grown alot and jobs stucked.

! now is working!

[foggy]

Thanks for chiming in with your resolution, however the thread is discussing the issue occurring while backing up/replicating vCenter server VM with application-aware image processing enabled, which is addressed in all the recent versions of Veeam B&R with the help of vCenter database exclusions. In your case, the issue is most likely caused by some other reasons. There's a dedicated topic regarding VSS issues with Exchange VMs, probably worth reviewing.