Available free space on Production drive not updated/recognized

[Paulo Balau]

Hi All

Backup fails because:

"Production drive C:\ClusterStorage\Volume3 is getting low on free space (123,2 GB left), and may run out of free disk space completely due to open snapshots."

Yep! So, I managed to move some data to another location freeing up some space and now I have 144GB free on the volume. This value is enough to have the backup running!

BUT... Veeam keeps recognizing the previous 123GB!

I did tried some things like moving the VM to another host, cluster rescan, created new job for the VM, … with no success.

How may I do to have Veeam recognizing the new available space?

Thank you all!
Balau

[DGrinev]

Hi Paulo,

I am not sure I did understand all the settings you have.
Have you tried to initiate the repository rescan within Veeam B&R UI?

Thanks!

[Paulo Balau]

I have an Hyper-V Cluster. One of the VMs has several disks on a volume stating overall 144 GB free space (before it had only 123GB free so cleaned some space)
But, Veeam only recognizes "old" 123GB free. So when performing the backup I always get the error.
144GB free is 5% free and 123GB is 4% free

Yes, I tried a rescan, created a new job from scrath, …

Thanks!

[DGrinev]

Paulo,

It's not recommended approach, but you can try to lower the setting in the General Options -> Notifications -> "Skip VM processing when free disk space is below 5%".
What I would do in this situation - contact the support team and ask for assistance.

Thank you!

[Paulo Balau]

Exactly what I did: placed 4% as a workaround. And I got the job done.

[Paulo Balau]

Ok root cause identified. Hyper-V had not refreshed the free space available and we were assuming we had more space than we actually have.

[DGrinev]

I am glad you've nailed it.
Thank you for sharing the root cause that might be helpful for further readers!