Veeam Backup and Replication Community Edition aborts backup job

[sput]

Hello everyone,
I'm running Hyper-V 3 virtual servers (Server 2019) on a MS Server 2019.
These guest servers have been assigned space on the Hyper-V in logical volumes for storing the virtual hard disks.
When creating the VMs, I chose the fixed size option for the virtual hard disk.
I chose the size of the virtual hard disk so that the respective volume is almost completely used.
From the point of view of the hyperbvisor, the corresponding hard disks are of course almost full.
From the point of view of the respective VM, however, there is plenty of space.
And that's exactly what Veeam Backup and Replication complains about when I want to run a backup job and aborts the job.
Do I still have options to still run the job successfully?
Under General Options/Notification there is the item "Skip VM Processing when free disk space is below .... %”. Will there be any problems if I deselect this option?
Does the job then run, or does Veeam need enough space on the respective volume to be able to run the job?
I would be extremely grateful for any hints and suggestions for my problem.
Greetings Sput

[Gostev]

What error does Veeam abort the job with?

[sput]

Hello,

the reported error is

Processing RD01 Error: Skipping VM processing due to insufficient free disk space on drive G:\

Greetings Sput

[Regnor]

If you adjust the percentage value or completely disable the skip option in the general options, your backup job will run.

The danger in that case is, that during the backup where your VMs are running on snapshots, your production storage could fill up. This depends on your change rate during the backup, so keep an eye on the free space. 5% of 100GB is nothing, 5% of 10TB is plenty of space.

[Gostev]

You're probably thinking VMware, but he has Hyper-V. I think this error relates to the inability to create an in-guest Microsoft VSS snapshot (due to lack of free disk space) and is thus unaffected by the General Options setting you mention. I think it can only by ensuring every volume of the guest OS has sufficient free disk space.

[sput]

Hello,

I have converted the affected virtual disks from fixed size to dynamic disks. That solves my problem for now. However, I will expand the storage and create correspondingly large volumes to convert the dynamic disks back into fixed-size disks.
Greetings Sput