Endpoint backup FIPS Error

[Y-ASK]

Case 01088983

Backing up a Windows 2012 R2 server to a Veeam Backup & Replication (8.0.0.2030) server using the Endpoint software latest version and this what we get:

Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

What's odd is that both of these servers have been FIPS complaint as required by our organization for some time now and the backups have been working fine for a couple of months now. Last Friday is the first time we received the error/failure. I'm sure it's probably a matter of telling the Veeam system to use some sort of FIPS complaint encryption scheme...

Backing up to a local (D) drive works just fine but as soon as we sent up a backup to point to the Veeam Backup & Replication server and start a backup the error occurs.

[Dima P.]

Hello Thomas,

the error occurs.

To clarify, you got this error in VEB backup session window, right? Can you share a screenshot please? Thanks

[Y-ASK]

Yes, Here's a cut and paste of the entire message:

Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.
Job has been stopped with failures. Name: [Backup Job PM], JobId: [d061ef1c-ff4e-4522-a837-b5084054ce66] Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

Details:
Preparing for backup
Error: This implementation is not part of the Windows Platform FIPS validated cryptographic algorithms.

I've heard back from support and they have pretty much said wait for Backup and Replication Ver. 9 for FIPS support. We are going with a local drive backup until then.

[Dima P.]

Hi Thomas,

I’ll make sure we got your case tested by QA department. Thanks for heads up!

[MartinNZ]

Check for Registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\FipsAlgorithmPolicy\Enabled If it is set to Dword 1 (ie enabled) this is most likely your problem. Set to Dword 0 (ie disabled) and it should work. If yours is a federal government environment where FIPS compliance is required you will need to open a support case with Veeam

[Dima P.]

Thanks for sharing - that’s a good workaround! To all future readers, if you see this error in the upcoming v9 - please report to this thread. Thanks.