Limitations and Considerations

In this article

    Mind the following limitations and considerations for configuration restore:

    • You can restore the configuration only to an appliance that is present in the Veeam Backup & Replication infrastructure.
    • You cannot restore the configuration to an unavailable appliance or to an appliance whose major version is outdated.
    • You must stop all policies that are currently running on the appliance to which you restore.
    • You cannot restore the configuration to a new appliance if the original appliance is present in the Veeam Backup & Replication infrastructure.
    • Sessions of policies that were running during backup are not restored.
    • Veeam Backup & Replication allows you to restore the configuration to a new appliance if the original appliance is not present in the Veeam Backup & Replication infrastructure. However, we recommend that you stop the original appliance if it is present in the Microsoft Azure infrastructure. This is required because two different appliances must not be connected to the same backup repositories.
    • The version of the appliance to which you restore the configuration must be the same or higher than the version of the backed-up appliance.
    • The appliance to which you restore the configuration preserves its TLS certificate.
    • [If you restore configuration to another appliance] During restore, parameters of the target appliance are overwritten. If you want to save the parameters, you must do it before you start configuration restore.
    • [If you restore configuration to another appliance] During restore, Veeam Backup & Replication removes the appliance and its Blob storage backup repositories from the Veeam Backup & Replication infrastructure. If the restore fails, you need to re-add the appliance and its repositories to the Veeam Backup & Replication infrastructure.