-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 02, 2009 12:23 pm
- Full Name: LE COQ MANUEL
- Location: Bretagne
- Contact:
Problem backup
I have a problem with one VM.
This VM is Windows 2003 in my domain.
I have this message when i save this vm.
In VMWARE:
Creating a quiesced snapshot failed because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
In Veeam:
VCB error: Error: Other error encountered: Snapshot creation failed: Could not quiesce file system. An error occurred, cleaning up...
I have apply this KB Vmware:
http://kb.vmware.com/selfservice/micros ... Id=1009073
I don't change my problem.
Snapshot manually works perfectly
Best Regards
This VM is Windows 2003 in my domain.
I have this message when i save this vm.
In VMWARE:
Creating a quiesced snapshot failed because the create snapshot operation exceeded the time limit for holding off I/O in the frozen virtual machine.
In Veeam:
VCB error: Error: Other error encountered: Snapshot creation failed: Could not quiesce file system. An error occurred, cleaning up...
I have apply this KB Vmware:
http://kb.vmware.com/selfservice/micros ... Id=1009073
I don't change my problem.
Snapshot manually works perfectly
Best Regards
-
- VP, Product Management
- Posts: 27371
- Liked: 2799 times
- Joined: Mar 30, 2009 9:13 am
- Full Name: Vitaliy Safarov
- Contact:
Re: Problem backup
Hello Manuel,
Basically, there is a difference between creating snapshot using VIC (manually) and the way Veeam creates it (we are using Managed Object Browser for that). The difference is that quiesce option is only available with MOB (and with vSphere client), you may email us to support@veeam.com to get the instructions of creating snapshot using MOB, to see how it works for you.
However, we do recommend to use Veeam VSS integration for Windows VMs for keeping your backups in consistent state instead of VMware quiesce.
Here is the topic discussing all the methods: Transactionally Consistent Backups
Thank you.
Basically, there is a difference between creating snapshot using VIC (manually) and the way Veeam creates it (we are using Managed Object Browser for that). The difference is that quiesce option is only available with MOB (and with vSphere client), you may email us to support@veeam.com to get the instructions of creating snapshot using MOB, to see how it works for you.
However, we do recommend to use Veeam VSS integration for Windows VMs for keeping your backups in consistent state instead of VMware quiesce.
Here is the topic discussing all the methods: Transactionally Consistent Backups
Thank you.
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 02, 2009 12:23 pm
- Full Name: LE COQ MANUEL
- Location: Bretagne
- Contact:
Re: Problem backup
Thank you it works perfectly. What is the repercussions of disabling this option
Best regards
Best regards
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Problem backup
With this option disabled, you will get crash-consitent backups (read "useless" in many cases), unless you are using Veeam VSS or custom pre-freeze/post-thaw scripts instead.
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 02, 2009 12:23 pm
- Full Name: LE COQ MANUEL
- Location: Bretagne
- Contact:
Re: Problem backup
Which may be why this error only on this vm?
Best regards
Best regards
-
- Chief Product Officer
- Posts: 31804
- Liked: 7298 times
- Joined: Jan 01, 2006 1:01 am
- Location: Baar, Switzerland
- Contact:
Re: Problem backup
No, this error is because VMware quiescence does not work well sometimes on certain VMs - not so reliable... this was one of the reasons why we have implemented and are maintaining our own quiescence mechanism for customers to use (Veeam VSS integration).
-
- Enthusiast
- Posts: 36
- Liked: 1 time
- Joined: Sep 02, 2009 12:23 pm
- Full Name: LE COQ MANUEL
- Location: Bretagne
- Contact:
Re: Problem backup
Thanks!
Who is online
Users browsing this forum: Bing [Bot] and 152 guests