If you’ve recently upgraded to Veeam Backup & Replication 12.1 and have begun seeing your Linux jobs fail with the “Failed to check fingerprint” error, there is no need to worry! This issue is easily resolved with a few clicks. The cause of the error comes from the change to the format used by Veeam to store the Linux SSH fingerprints. If the config database is stored in an SQL 2019 or 2022 instance, the conversion process fails to process blank current_fingerprint values and sets them to NULL, causing the error in Veeam.
To resolve the issue, you must manually validate each fingerprint for each machine:
- From your Veeam Backup and Replication console, navigate to the General Options menu, and open the Security tab.
- Change the Linux hosts authentication settings from ‘Add all discovered hosts to the list automatically‘ to ‘Add unknown hosts to the list manually (more secure)‘:
- Validate SSH Fingerprints and Trust entries in the Untrusted node in the Inventory section. (This may require the job to run once after making the previous change)
- Once validated, run the jobs to verify the issues has been resolved. (You may set the Linux host authentication back to ‘Add all discovered hosts to the list automatically’ if the job is running successful)
If these changes have not resolved the Failed to check fingerprint error, or have any other backup questions, please reach out to Support@Managecast.com.