Jobs targeting an S3-Compatible repository fail with either of the following errors:
Error: S3 error: Content-MD5 HTTP header is required for Put Object requests with Object Lock parameters Code: InvalidRequest Agent failed to process method
S3 error: Checksum Type mismatch occurred, expected checksum Type: null, actual checksum Type: sha256
Starting in Veeam Backup & Replication 13.0.1, the software now utilizes the SHA256 algorithm for hash calculation when signing API requests to S3 storage systems.
SHA256 is supported by AWS (as stated in their documentation), but not all S3-compatible storage systems implement SHA256, instead relying on the obsolete MD5.
For on-premises storage devices, review the settings to determine if the option to use compliant SHA-256 hashing is available. If this option is not available, we encourage you to contact your storage vendor for assistance in determining if newer firmware is available that includes SHA-256 hashing or if it will be available in an upcoming firmware release.
If SHA-256 hashing cannot be enabled on the S3-compatible storage or is not available, Veeam Backup & Replication can be configured to re-enable the legacy MD5 hashing method.
Notes:
Create the following registry value:
Key Location: HKLM\SOFTWARE\Veeam\Veeam Backup and Replication\
Value Name: S3UseMd5ContentHash
Value Type: DWORD (32-Bit) Value
Value Data: 1
Modify the following configuration file and set the indicated value:
Configuration file: /etc/veeam/veeam_backup_and_replication.conf
Section: [root]
Setting: S3UseMd5ContentHash=1
For more information on applying custom settings on the Veeam Storage Appliance, please review:
KB4779: Applying Custom Settings to Veeam Software Appliance
If this KB article did not resolve your issue or you need further assistance with Veeam software, please create a Veeam Support Case.
To submit feedback regarding this article, please click this link: Send Article Feedback
To report a typo on this page, highlight the typo with your mouse and press CTRL + Enter.
This form is only for KB Feedback/Suggestions, if you need help with the software open a support case