If I backup two Linux appliances (VMware ova) in different backup jobs which have the same SSH fingerprint name but different values so the backup jobs take it in turn to fail after I have trusted the untrusted SSH fingerprint. They alternate between being trusted.
Is there a way for Veeam to trust both or do I need to look at changing the name on one of the two appliances?
Best answer by JMeixner
Hello
why do the two appliances have the same SSH fingerprint?
And two systems with the same name will cause problems not only in Veeam, I think.
+17Hello
why do the two appliances have the same SSH fingerprint?
And two systems with the same name will cause problems not only in Veeam, I think.
+21Typically, you do not have the same SSH fingerprint for Linux machines as asked by Joe. I would look at making them both different from each other, so the backups work as expected.
+14What is running inside those appliances and do you need guest processing configured for those? Linux doesn’t have a VSS equivalent, so if you’re not running a database inside those appliances, need file indexing or any kind of pre/post-script, you might think about disabling guest processing.
Thanks for your replies.
They don’t have the same fingerprint value, just the same name. They are FreePBX appliances so the question around the need to have indexing is probably valid so I’ll look at disabling it for that VM.
The backup job fails when trying to connect to the VM so indexing isn’t the issue, it’s the initial connection over SSH.
The two VMs are on separate networks so if there is no solution in Veeam to allow both fingerprints, I’ll look at changing the fingerprint on one or both.
+7In general, I setup backups for Linux appliances to Backup Only and disable Application Aware Processing. There are a couple of exceptions I guess as noted, but I’ve never needed AAP inside of a linux VM so far.
+17Would it be a problem to set a different name to one of the appliances?
A duplicate name is a problem in most systems. As you see the SSH key is saved in combination with the machibe name and this is the reason why you have to trust the key each time the other machine is processed.
+20Hi
Just following up on your post here. Did you end up getting your Linux appliance backup issue with SSH footprint sorted? Can you share which avenue you took to resolve it? Also, if one of the comments assisted you, we ask you please mark one as ‘Best Answer’ so others who come across your post with a similar issue can benefit.
Thank you.
Thanks
I had to change the name of the appliance which made the SSH fingerprint different and solved the problem.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
