We also had this problem, case number 07123320, and could not find the cause. All backups of a particular Windows VM were performed correctly according to veeam, but when doing a file-level restore, drive letters were not shown for some disks. Sometimes disk C:, other times the DB disk was missing. Also, the VM could not be booted from surebackup.
We found that one of our two Windows backup proxies (both in SAN mode) kept causing the problem. A health check of the backups did not help to identify the problem. The proxy with the problem was investigated for all possible error sources (HW, Bios, SAN, Config, etc) without success and was identical to the other proxy. This problematic proxy backed up about 400 VMs daily - without ever generating such an error.
I automated the checking of all VM backups (Windows VMs only) by using a script with Publish-VBRBackupContent and comparing the number of mounted volumes with the information from vCenter.
Solution:
First we changed the agent for this VM to have working backups again and later we switched to Linux proxies (planned for other reasons) and the problem completely disappeared.
We found that one of our two Windows backup proxies (both in SAN mode) kept causing the problem. A health check of the backups did not help to identify the problem. The proxy with the problem was investigated for all possible error sources (HW, Bios, SAN, Config, etc) without success and was identical to the other proxy. This problematic proxy backed up about 400 VMs daily - without ever generating such an error.
I automated the checking of all VM backups (Windows VMs only) by using a script with Publish-VBRBackupContent and comparing the number of mounted volumes with the information from vCenter.
Solution:
First we changed the agent for this VM to have working backups again and later we switched to Linux proxies (planned for other reasons) and the problem completely disappeared.
Statistics: Posted by Spex — Sep 20, 2024 10:28 am