Validating SSH Fingerprints

In this article

    Veeam Backup & Replication treats fingerprints of Linux VMs and Linux hosts differently:

    Validating SSH Fingerprints of Linux VMs

    When you enable the Add unknown hosts to the list manually (more secure) option in Veeam Backup & Replication settings, Linux-based machines whose fingerprints are not stored in the Veeam Backup & Replication database or the known_hosts file become unable to communicate to the Veeam backup server. During discovery, Veeam Backup & Replication puts such machines to the Untrusted node. To start managing an untrusted computer, you need to validate its fingerprint manually in the Veeam Backup & Replication console.

    To validate the SSH fingerprint:

    1. Open the Inventory view.
    2. In the inventory pane, expand the Virtual Infrastructure node and click Untrusted.
    3. In the working area, Veeam Backup & Replication will display a list of machines whose fingerprints need to be validated. Check fingerprints of the machines in the list and validate them in one of the following ways:

    Click to zoom in

      • To validate a fingerprint of a specific computer in the list, select the necessary computer in the working area and click Trust on the ribbon. Alternatively, you can right-click the computer and select Trust.

    Click to zoom in

    Validating SSH Fingerprints of Linux Hosts

    If the SSH public key fingerprint of a Linux host is changed, Veeam Backup & Replication places this host in the Unavailable folder. To be able to use this server, do the following:

    1. In the Backup Infrastructure view, expand the Managed Servers node and select Unavailable.
    2. Right-click the Linux server and select Properties.
    3. In the SSH Connection step of the Edit Linux Server wizard, click Apply.
    4. In the pop-up dialogue window, click Yes to confirm that you trust this server.
    5. Click Finish to close the wizard.

    Validating SSH Fingerprints 

    I want to report a typo

    There is a misspelling right here:

     

    I want to let the Veeam Documentation Team know about that.