Free space on datastore.

[hoogvliet]

The message comes from Veeam.
VM's with this error all have a physical RDM, but I thought that phisical RDM will automatically be skipped by Veeam.
Also tried to replicate the server but also get this error.
There must be a way to backups only the VM systemdisk without the pRDM, right?

[dellock6]

Yes, by excluding specific disks in the job properties...

Luca.

[Vitaliy S.]

VM's with this error all have a physical RDM, but I thought that phisical RDM will automatically be skipped by Veeam.

Yes, it is skipped, but the snapshot is still taken for the entire VM.

[jspeicher]

this is the only way i believe you can work around this, i'm open to be corrected, because we currently have some extremely large vm's we're needing to just do a backup of the 0:0/system drive, but we don't have a datastore that's large enough for the snapshots.

http://kb.vmware.com/selfservice/micros ... Id=1002929

I believe the above will allow a change in the snapshot location.

[Vitaliy S.]

Yes, changing the workingDir parameter should help.

[coryvmbkp]

Hi,
I just started trying out the free version of veeam, for vmware. I've run the veeamzip on a couple vm's and so far it seems to work.
On this other vm though, I'm running into the error: "Production datastore 'backup' is getting low on free space (305.0 MB left), and may run out of free disk space completely due to open snapshots. Error: Insufficient free disk space on production datastore 'backup'."

Basically, on my vmware host there are 3 internal hard drives. All my other vm's use 2 of them, but the vm I'm trying to back up is as follows:
VM -> primary hard disk on one of the two disks that other vm's (with successful backups) are on.
VM -> extra disk - for extra mount point in linux, and an extra disk - for nfs shares and samba shares ---> these are both stored on a datastore of their own that is fully used (thick provisioned disks) so it has the above 305MB free).

But, the Settings for the two extra disks, in vmware, have the checkbox "Independent" checked. This says "Independent disks are not affected by snapshots". So I'm not sure why the veeam backup is failing without free space, as these two extra disks shouldn't be affected by snapshots, and the vm and it's primary hard disk is on a datastore with plenty of free space (>800GB).

Thanks

[Vitaliy S.]

Hi Cory,

Try to use the workaround with workingDir parameter, meanwhile I will try to find out if there is any registry key to change the threshold that prevents you from backing up this VM.

Thanks!

[kte]

it seems that this parameters doesn't work if uou have alot of storage vmotions

k

[dannyvdz]

I am trying to backup a Ubuntu Server which is running on ESXI 5.1
The server has 5 drives assigned as separate virtual drives. I excluded all but the OS-drive which is 50 GB (otherwise I'd backup 2,75 TB).
However when I start the backup I have insufficient space on my datastore. I checked my datastore and I have a total of 250 GB free space.
How can I fix this? I tried removing and adding the job again and checked my my settings several times..

[Vitaliy S.]

Hello Danny,

Even if you exclude disk from the backup job, the snapshot is still taken against all VM disks. The only way to exclude disks from snapshotting is to make them independent.

Thank you!

[dannyvdz]

Ok, thanks for the info but how is this done best?

Nevermind.. I think I found out how.. now just let me see if backups work!

[dannyvdz]

Unfortunately this doesn't change Veeam's behaviour, There still insufficient free disk space

[Vitaliy S.]

You can try to use the reg key below (should be applied to the main Veeam B&R registry hive) which will change the threshold for this error message, but doing this is highly NOT recommended, because this may cause you issues in future.

BlockSnapshotThreshold - the default value is 2 (GB), try to set it to 0

[klre]

Hi,
I've got the below mentioned error message when I try to do a full backup of a server with 2 disks.
System Disk: Disk:0:0 (on datastore 1)
Data Disk: Disk:0:1 (on datastore 2)

Error message:
Processing 'Server' Error: Insufficient free disk space on production datastore 'datastore 2'.

I know this message appears if there is not enough space for the snapshot.
But my problem is, I don't want to take a snapshot of disk:0:1. I also set this disk as independent, to make sure, vsphere won't take a snapshot of it. With the snapshot-manager everything works fine, but with veeam it doesn't.
Is there a known issue with this or any workaround?

thank you in advance.

[Vitaliy S.]

Reto, as a workaround you can either try to reg key above, or use a VMware WorkingDir VM parameter to resolve this issue. Thanks!

[Vishez]

Hello
Yes i read another same theme but nothing help. I have Veeam Free and try to zip virtual machine on different datastores and each time
21.08.2014 14:21:28 :: Job started at 21.08.2014 14:21:27
21.08.2014 14:21:28 :: Building VM list
21.08.2014 14:21:52 :: VM size: 1,2 TB (1,0 TB used)
21.08.2014 14:21:52 :: Changed block tracking is enabled
21.08.2014 14:22:28 :: Preparing next VM for processing
21.08.2014 14:22:28 :: Processing 'win.2k8' Error: Insufficient free disk space on production datastore 'share_is'.
21.08.2014 14:22:30 :: All VMs have been queued for processing
21.08.2014 14:22:47 :: Backup file \\xxx.xxx.xxx.xxx\Volume_1\Backup_win.2k8_2014-08-21T142127.vbk
21.08.2014 14:22:48 :: Job finished with error at 21.08.2014 14:22:48

On others same. On all datastores I have enough space to copy 1.2 TB.
And in all datastores created backup file about 16mb and then stopped.

[foggy]

Aleksandr, please review the tread above and if nothing helps, contact technical support directly.

[Vishez]

Well, seems nothing help or i do something wrong.
Go in Veeam в Files and see this - there is 2 hard dive that see veeam - logical. It's my server disks c and E that on virtual machine. So disk C that named datastore1 - Total size 274Gb Free Space 138Gb. And disk Е that named share_is - Total size 931Gb Free Space 305Mb. Can it be that i cant do backup cos Free space 305Mb on share_is? And what i can do to fix it?

[foggy]

Can you make a snapshot of the same VM using vSphere client manually?

[Vishez]

Can you make a snapshot of the same VM using vSphere client manually?

Yep. I can. U need some logs from it snapshot?

[foggy]

Me not, but our support engineers could be interested in some additional information. So please contact them directly with this for further investigation.

[Gostev]

Can it be that i cant do backup cos Free space 305Mb on share_is? And what i can do to fix it?

Yes, you need at least 2GB. Vitaly explained this at the end of the previous topic page.

[Luca82]

You can try to use the reg key below (should be applied to the main Veeam B&R registry hive) which will change the threshold for this error message, but doing this is highly NOT recommended, because this may cause you issues in future.

BlockSnapshotThreshold - the default value is 2 (GB), try to set it to 0

Hi Vitality, I've the same issue but in hyper-v environment. I don't find the BlockSnapshotThreshold registry on Veeam Server (V8)...could you help me how to workaround this issue?

[Vitaliy S.]

This registry key should be created manually, by default it is not present in the registry hive. Also consider migrating your VMs to the volume with more space, as 2 GBs of free space is way too low for a production datastore.

[PatrickW]

Just raised this as a case under 1824707 but I'm sure it doesn't need hte full attention of a support rep, I swear I've missed something obvious.

Error I'm getting is :
Production datastore is getting low on free space (980.0 MB left), and may run out of free disk space completely due to open snapshots.

Now initially I can understand that this was valid, I'd provisioned a 500GB datastore and then configured it as a 500GB disk in the guest. However I've since expanded the datastore to 550GB, but left the disk at 500GB. Surely 10% free space on the datastore is enough :

So I reckon I must be missing something basic but I can't spot what. Any thoughts please?

[PTide]

Hi,

So the problem is that even after expanding the disk VBR keeps throwing that error during backup? Pleas review the thread and if nothing helps kindly keep working with support team.

Thanks

[GabesVirtualWorld]

VEEAM 9.5 gives me this error for some VMs:
Getting VM info from vSphere
Production datastore <datastorename> is getting low on free space (84.6 GB left), and may run out of free disk space completely due to open snapshots.
Error: Skipping VM processing due to insufficient free disk space on datastore.

I thought there was a 2GB limit, but the error mentions 84GB left. How should I interpretate this?

[veremin]

I thought there was a 2GB limit, but the error mentions 84GB left. How should I interpretate this?

Most likely 84 GB is 5% of datastore capacity. Check Menu -> General Options -> Notifications -> "Skip VMs when free disk space is below X %". Thanks.

[GabesVirtualWorld]

Thanks!

[westinbuilding]

Hi, I have been receiving "Production datastore XXXX is getting low on free space and may run out of free disk space completely due to open snapshots."

I've check snapshot manager and confirmed there are not snapshots nor orphaned snapshots. I think the only option that I have left is to increase the datastore.

The question is how much should I increase? The message doesn't exactly how much more it needs...

Any suggestions?

Thanks...