Comprehensive data protection for all workloads
Post Reply
NT29
Enthusiast
Posts: 25
Liked: never
Joined: Oct 02, 2011 6:27 pm
Contact:

Job not possible for a disk of 256G

Post by NT29 »

Hello
I Made a new VM 2003R2 with 2 disks
c:25G
E: 256 G (the max possible for this version of OS)

I cannot sav the vm, here the message ...
Freezing guest operating system
CreateSnapshot failed, vmRef "vm-3068", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "True"
Impossible d’effectuer une opération de snapshot.
I modify the VM
Create a new disk of 250G, deplace the data, it works

Can you just explain me the raison of the error ?
thanks
dellock6
VeeaMVP
Posts: 6163
Liked: 1971 times
Joined: Jul 26, 2009 3:39 pm
Full Name: Luca Dell'Oca
Location: Varese, Italy
Contact:

Re: Job not possible for a disk of 256G

Post by dellock6 »

My suspect is you are using a VMFS datastore in vSphere 4.1, right? IF so, the VMFS is formatted as default, right again?
In this situation, maximum file you can save on the datastore is 256Gb, but is it safe to not go to the limit. I suppose also 255 Gb will work.
Luca Dell'Oca
Principal EMEA Cloud Architect @ Veeam Software

@dellock6
https://www.virtualtothecore.com/
vExpert 2011 -> 2022
Veeam VMCE #1
Vitaliy S.
VP, Product Management
Posts: 27347
Liked: 2785 times
Joined: Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov
Contact:

Re: Job not possible for a disk of 256G

Post by Vitaliy S. »

Can you create a quiescenced snapshot via vSphere Client manually? Btw, is there any reason why you use VMware Tools quiescence instead of Veeam's application aware image processing?
tsightler
VP, Product Management
Posts: 6032
Liked: 2859 times
Joined: Jun 05, 2009 12:57 pm
Full Name: Tom Sightler
Contact:

Re: Job not possible for a disk of 256G

Post by tsightler »

You'll want to look at VMware KB 1012384, specifically the section on calculating snapshot overhead. You'll see that for a VMFS 3.x volume with 1MB block size there is a 2GB "snapshot overhead" which means that a VMDK must be 254GB to be able to take a snapshot.
NT29
Enthusiast
Posts: 25
Liked: never
Joined: Oct 02, 2011 6:27 pm
Contact:

Re: Job not possible for a disk of 256G

Post by NT29 »

thanks a lot for your explanations
Post Reply

Who is online

Users browsing this forum: Google [Bot], Semrush [Bot] and 55 guests