Backup Job Misleading Completion Percent

[mkaec]

I have a backup job with 1 VM in it with 1 disk that is sized at 4.9 TB. However, only 3.65 TB is used on that disk.

When the backup job runs an active full, after 2.5 TB has been backed up, the job status is 50% complete and the job line item shows "Hard disk 1 (4.9 TB) 2.5 TB read at xxx MB/s". Once the 3.65 TB is backed up, the percentage magically increases to 99% and the job finishes. It does show the total VM used space earlier in the job details, but not the per-disk used space. (That's moot for this example. But it is applicable to other VMs.)

I'd prefer if these stats referenced the actual used space instead of disk provision size.

[Andreas Neufert]

Hello Marc,

thanks for the feedback. The actual %tage shows the disk status. To know in advance what free space is on the disk, we would have to read the data first which is not good. So this %tage view was used to not delay the processing.

[mkaec]

As I mentioned, it does show the entire VM used space earlier in the job log. It knows that without reading the data. And, on Hyper-V, there are PowerShell commands that will show the file size of each disk. I'm sure there is an API equivalent. That wouldn't be a guarantee of used space, but it would be closer than using the defined size.

http://www.itprotoday.com/virtualizatio ... per-v-host

Thanks for considering this feature request.

[foggy]

Size of all files on disk could be far from the VM actually used space, since there could be a lot of dirty blocks (which also need to be read, since they contain data, but are not used). Anyway, thanks for the request.

[Andreas Neufert]

... and usually there is Change Block Tracking based backups which as well have nothing to do with the VM or OS informations.

[mkaec]

Here is an example.

This is a job with 1 VM in it. Veeam knows that, while the VM size is 127 GB, the actual used space is 27.4 GB. 6.6 GB has been processed. Veeam calculated this as 5% complete. But 6.6 GB / 27.4 GB = 24% complete.