thanks for your input. Yes, indeed the total size in the Action section says: 06.09.2014 22:00:19 :: VM size: 1,5 TB (1,1 TB used)
The repository only has one 1TB. And its a kind a work around (it is a external usb drive, mounted as VHD on the backup server, as we do not have access to the NAS from the client at the moment).
>"It might be because you have less free space in a repository than the total size of VMs of the job."
Does that mean, that whenever i will create a "new" fullbackup, i have to be sure, that there is enough space free on the repository drive, otherwise it will fill up the (Hyper-V) local drives as long there is space (as happen on my server) ? I understand, that if on the repository is not enough space free, then the job fails, but it should not fill up other drives...
In the logs are following errors (for all 4 Servers the same..)
08.09.2014 22:04:30 :: Processing 'SRV1' Error: Client error: There is not enough space on the disk.
Failed to write data to the file [D:\Backups\Fullsave_all_VM\Fullsave_all_VM2014-09-08T220045.vib].
Failed to perform data backup.
An existing connection was forcibly closed by the remote host
08.09.2014 22:04:32 :: All VMs have been queued for processing -> (that is a green event)
08.09.2014 22:04:58 :: Backup location "D:\Backups" is getting low on free disk space (64,0 KB left of 931,5 GB).
and then my hyper-v machines getting paused...
Btw: i ran the job yesterday, without the "deduplication" flag. It worked ok, no problems. Under D:\System Volume Information are still created some files, but smaller in size, and does not fill up the drives.