Thank you for sharing the details and sorry to hear about the challenges. The behavior is not expected, and will require review of the logs, so please open a Support Case as is noted when creating a topic and let Veeam Support review the behavior.
Be sure to include logs for Support to review (select the 3rd radio button, and select the Veeam Server itself to export logs from)
Please share the case number here once created. Thanks!
David Domask | Product Management: Principal Analyst
Two of my vm's had a size definition of disks which were not evenly divisible by 1024, so it had no unitprefix (G, B, K, T) since it was in bytes. Veeam did not like this.
I resized the disk to the nearest KB, and then it worked.
Thanks for sharing the outcome of the case mb1977, I do recall seeing something similar as well (should be fixed in an upcoming release), but it can be hard to spot with just the error. Glad you were able to get it resolved with Veeam Support.
David Domask | Product Management: Principal Analyst