Error after vSphere update

VMware specific discussions

backup error

Veeam Logoby Rohail2004 » Wed Feb 02, 2011 2:24 pm

[merged into existing discussion]

i am keep getting the following error while trying to run the back up..

Freezing guest operating system
CreateSnapshot failed, vmRef "432", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>
Rohail2004
Enthusiast
 
Posts: 41
Liked: never
Joined: Wed Oct 06, 2010 6:54 pm

File is larger than the maximum size supported by datastore

Veeam Logoby milfner » Wed Feb 16, 2011 8:38 am

[merged into existing discussion]

Before explaining my problem, I will give you a breif overview. I have an SBS 2008 VM on a datastore that has a block size of something small (i think it was 1MB), this was created inadvertently. I now realize that the total size of the OS hard disk will not exceed something like 250GB due to this 1MB cache size limitation on the datastore (called "Second Mirror). I have a feeling that the following error I am getting on Veeam Backup & Replication is due to this???

I tried backing up this VM and I receive the following error.....

0 of 0 files processed

Total VM size: 256.00 GB
Processed size: 0.00 KB
Processing rate: 0 KB/s
Backup mode: HOTADD/NBD without changed block tracking
Start time: 16/02/2011 7:15:31 PM
End time: 16/02/2011 7:15:55 PM
Duration: 0:00:24


Freezing guest operating system
CreateSnapshot failed, vmRef "208", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>
milfner
Influencer
 
Posts: 20
Liked: 1 time
Joined: Wed Feb 16, 2011 7:51 am

backup Job failing

Veeam Logoby pwynne2009 » Mon Feb 21, 2011 9:45 am

[merged into existing discussion]

Hi,

My backup job for a file server is failing for me. below is the mesage I get for the failure. Has anyone seen this before?

"CreateSnapshot failed, vmRef "vm-164", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>"
pwynne2009
Lurker
 
Posts: 2
Liked: never
Joined: Tue Feb 08, 2011 3:14 pm
Full Name: Paul Wynne

Veeam backup snapshot size issue

Veeam Logoby dilpz213 » Wed Mar 02, 2011 9:58 am

[merged into existing discussion]

Hi All,

We have been using Veeam Backup and Replication 5.0.0.179 to backup smaller VMs from our ESXi 4 environments to other Windows servers in our LAN. This weekend we did a P2V of a Windows 2003 fileserver to one of our new ESXi installations. The ESXi host has raided internal disks (no shared storage) divided into 2 VMFS datastores. Datastore 1 has a default block size and is 924GB in size. Datastore 2 has a 4mb block size and and is also 924GB in size as it hosts a large 800GB VMDK for this fileserver.

The fileserver consists of 2 VMDKs. The first one is 220GB in size and is the system volume/app store hosted on datastore 1. Datastore 1 has around 556GB free. The second, as mentioned above is 800GB in size and is on Datastore 2 which has 124GB free on it.

When attempting to do a Veeam backup job to a windows share on another server in network mode, the job fails with the following error:

Freezing guest operating system
CreateSnapshot failed, vmRef "vm-422", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>

Is this error because there isnt enough space to make the snapshot or because the snapshot veeam is trying to make is too big for the block size of the datastore? If it is the latter, is there any way of getting round the problem without having to trash the datastore and reformat? Or am I going to struggle anyway as I only have 124GB free left on datastore 2? I have already tried doing the backup job excluding the 220GB VMDK and doing the 800GB VMDK on its own. I still get the same error. Any advice would be much appreciated.

Thanks
dilpz213
Novice
 
Posts: 3
Liked: never
Joined: Wed Mar 02, 2011 9:13 am
Full Name: Dilpz

Re: Error after vSphere update

Veeam Logoby Vitaliy S. » Wed Mar 02, 2011 10:10 am

Dilpz, you need either move VM configuration files to a datastore with larger block size or reformat the existing datastore (storing VMX file) with larger block size.
Vitaliy S.
Veeam Software
 
Posts: 19575
Liked: 1106 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Error after vSphere update

Veeam Logoby dilpz213 » Wed Mar 02, 2011 11:39 am

Hi Vitaliy,

Thanks for your input. Ok, we will try to reformat the datastore. As this VM is spread over datastore 1 and 2, will both datastores required formatting to the 8mb block size or just the one with the larger VMDK?
dilpz213
Novice
 
Posts: 3
Liked: never
Joined: Wed Mar 02, 2011 9:13 am
Full Name: Dilpz

Re: Error after vSphere update

Veeam Logoby Alexey D. » Wed Mar 02, 2011 11:47 am

Just make sure that VM's configuration files are either on the datastore with "larger VMDK" or on the datastore with 8 MBs block size.
Alexey D.
 

Re: Error after vSphere update

Veeam Logoby dilpz213 » Wed Mar 02, 2011 12:56 pm

Hi Alexey, I had a hunch it might be something like that. I moved the config files - and it seems to have worked! Thanks. I guess it makes sense as ESX will try to make the snapshot in the same place as where the config files are and in my case, the snapshot had the potential to exceed 1tb and therefore it failed as where the config files were previously, the block size was only 2mb. Am I right?
dilpz213
Novice
 
Posts: 3
Liked: never
Joined: Wed Mar 02, 2011 9:13 am
Full Name: Dilpz

Re: Error after vSphere update

Veeam Logoby Alexey D. » Wed Mar 02, 2011 1:00 pm

You're 100% correct!
Alexey D.
 

Fileserver Backup fails

Veeam Logoby ritterbruder » Fri Apr 08, 2011 2:15 pm

[merged into existing discussion]

First time poster, 10 days into trial. I know there have been a few threads about this but my question stems more of how can I specifically fix this in my scenario. I am new to virtualization and created a file server vm and threw some files on it. It is thin provisioned and has about 29gb of space used so far (it is all one large vmdk file, not cut into small chunks). When I attempt my first backup this is the error I receive.

Total VM size: 1.00 TB
Processed size: 0.00 KB
Processing rate: 0 KB/s
Backup mode: HOTADD/NBD without changed block tracking
Start time: 4/8/2011 1:36:18 AM
End time: 4/8/2011 1:37:09 AM
Duration: 0:00:51


Freezing guest operating system
CreateSnapshot failed, vmRef "vm-88", timeout "1800000", snName "VEEAM BACKUP TEMPORARY SNAPSHOT", snDescription "Please do not delete this snapshot. It is being used by Veeam Backup.", memory "False", quiesce "False"
File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>


My target is a 2tb iscsi target mounted onto a server 2008r2 as a partition. From what I've read I think it has something to do with block size. I would like to know how to deal with this the best way possible without totally redoing my vm. Thanks everyone.
ritterbruder
Novice
 
Posts: 8
Liked: never
Joined: Fri Apr 08, 2011 1:54 pm
Full Name: clark keller

File <unspecified filename> is larger than the maximum size

Veeam Logoby ivan_cecoel » Tue Apr 12, 2011 7:48 am

[merged into existing discussion]

Hi everyone, I have a problem when I try to do a backup from a VM, the error is

File <unspecified filename> is larger than the maximum size supported by datastore '<unspecified datastore>

I found the solution in this forum, format the partition with another block size, but in my case that's a problem.

I have the VM with the OS disk in a Fiber Disks, and I have the other disks into SATA disks (6 disks 600Gb every disk) , I only want to backup the OS disk, the other disks I'll do a tape backup. I select only de OS disk in the veeam backup but the error stills...
I can't format the datastore, there are more servers and this server it's in production and I can't stop them.
There are any possibilities to backup only the OS disk?
I saw another possibilitie are copy de config file of the VM to another datastore with a block size bigger, it's possible? Could be some problem?

Thank you so much.
ivan_cecoel
Novice
 
Posts: 8
Liked: never
Joined: Mon Jun 28, 2010 9:05 am
Full Name: Ivan Hidalgo

Re: Error after vSphere update

Veeam Logoby Vitaliy S. » Tue Apr 12, 2011 8:12 am

If re-formatting the datastore is not an option for you, then moving VM configuration files to the datastore with a larger block size should make a trick.
ivan_cecoel wrote:I select only de OS disk in the veeam backup but the error stills...

That's expected. Reading back through my responses above, you should notice that when snapshot is created it affects all disks attached to the VM and the only way to exclude the disk from snapshotting is to make it independent, thus meaning you won't be able to backup it either.
Vitaliy S.
Veeam Software
 
Posts: 19575
Liked: 1106 times
Joined: Mon Mar 30, 2009 9:13 am
Full Name: Vitaliy Safarov

Re: Error after vSphere update

Veeam Logoby Daveyd » Mon Apr 18, 2011 2:41 pm

I have a VM that is configured like this:

C: (O/S) - 30GB vmdk on 400GB Datastore formatted with 1MB block size with 40GB free
D: (Data) - 1.48GB vmdk on 1.5TB Datastore formatted with 8MB block size with 20GB free

I am obviously receiving the same Veeam error when trying to do a backup. It looks as if I need to move the .vmx file from the OS datastore to the Data datastore. My question is, in doing so, how much free space do I need for the snapshot? As you can see I do not have tons of free space on either datastore.
Daveyd
Expert
 
Posts: 272
Liked: 10 times
Joined: Thu May 20, 2010 4:17 pm
Full Name: Dave DeLollis

Re: Error after vSphere update

Veeam Logoby Gostev » Mon Apr 18, 2011 2:59 pm

Depends on how active the VM in question is. You need enough space to accommodate incoming disk changes while backup is running (which can be anywhere between few minutes to few hours depending on amount of incremental changes).

Our product starts throwing warnings at 10GB free space. 20GB or 40GB is better, and should be enough in most cases (unless VM in question is highly active Exchange or SQL server).

Thanks.
Gostev
Veeam Software
 
Posts: 21396
Liked: 2350 times
Joined: Sun Jan 01, 2006 1:01 am
Location: Baar, Switzerland

Re: Error after vSphere update

Veeam Logoby Daveyd » Mon Apr 18, 2011 4:20 pm

Thanks for the info. Is the recommended procedure to move the vmx file to power down the VM, unregister it from vCenter, copy the vmx file to the 8MB block datastore the re-register it in vCenter?
Daveyd
Expert
 
Posts: 272
Liked: 10 times
Joined: Thu May 20, 2010 4:17 pm
Full Name: Dave DeLollis

PreviousNext

Return to VMware vSphere



Who is online

Users browsing this forum: Bing [Bot] and 16 guests