EFI Boot Entry Case Sensitivity Issue Causing Back_欧博ABG-会员注册-官网网址

We are encountering an issue with Veeam Backup & Replication regarding EFI boot entries on some of our servers.
These servers have a traditional UEFI firmware and use a FAT32-formatted EFI System Partition (ESP).
Due to the nature of the VFAT filesystem (which is case-insensitive but case-preserving), all EFI paths written by the firmware during boot are automatically uppercased (e.g., \EFI\REDHAT\SHIMX64.EFI).

However, Veeam B&R appears to perform a case-sensitive check when validating the path of the EFI boot entry. This leads to false warnings, such as:

Code:

Cannot find EFI boot manager entry for EFI System Partition GUID [xxxxx-...].

We confirmed this by manually recreating the EFI entries using lowercase paths (e.g., \EFI\redhat\shimx64.efi), which made the warning disappear.
But upon reboot, the firmware restores its own uppercased version, and the warning reappears.

Summary:

The EFI partition is VFAT → not case-sensitive.

Firmware auto-creates or modifies UEFI entries in uppercase.

Veeam treats the path check as case-sensitive → leads to unnecessary warnings.

This affects backup validation or reliability status.

Request:
Could you confirm whether Veeam’s EFI entry validation logic is indeed case-sensitive?
If so, would it be possible to make this check case-insensitive, as per UEFI and VFAT behavior?

Thank you for your assistance.
BR,
Seb

Support case ID: 07738392

(责任编辑：)

搜索

热门标签:

EFI Boot Entry Case Sensitivity Issue Causing Back