Veeam—S3 error: Content-MD5 HTTP header is required

When Veeam 13 introduced support for SHA256 hashes for request signatures, it changed how requests to S3-compatible storage were made.

This error indicates that Veeam is not sending the MD5 hashes that current versions of Zadara Object Storage expect.

Resolution

To resolve this issue, Veeam provides guidance on configuring your Veeam clients to use MD5 hashes: https://helpcenter.veeam.com/docs/vbr/userguide/s3_compatible_limitations.html?ver=13

To use MD5 instead of SHA256:

On Linux-based backup server, set the S3UseMd5ContentHash value in the /etc/VeeamAgentConfig configuration file.
On Microsoft Windows-based backup server, set the HKEY_LOCAL_MACHINE\SOFTWARE\Veeam\Veeam Backup and Replication\S3UseMd5ContentHash {DWORD} registry value. This setting enables the use of MD5 for all S3 compatible object storage systems.