Supported disaster recovery path for Veeam Backup Enterprise Manager

[Steve_Sons]

Case ID: 08042403

Hello,
we are looking for clarification on the supported disaster recovery path for Veeam Backup Enterprise Manager deployed as a Linux-based Veeam Software Appliance.

Our scenario is the following:
• Enterprise Manager is running as a Linux-based Veeam Software Appliance
• the original server/appliance may fail and need to be redeployed
• we want to understand whether the previous Enterprise Manager configuration can be restored onto a newly deployed Linux Enterprise Manager appliance in a supported way

What we found in the documentation so far:
• The official documentation states that configuration backup and restore is not supported for Veeam Backup Enterprise Manager.
• At the same time, the documentation also describes EMCO-based backup/restore of the Enterprise Manager configuration database for specific migration scenarios, for example Windows to Linux, using the Enterprise Manager DB Migration utility and restoreemdatabase.
• In the Veeam Host Management Console on the appliance, it is also possible to create a support logs bundle and optionally include the configuration database file.

Our questions are:
• Is there any supported disaster recovery procedure for restoring the configuration of a previous Linux-based Enterprise Manager appliance onto a newly deployed Linux Enterprise Manager appliance?
• If yes, is EMCO the supported mechanism for that scenario?
• Can a Linux-based Enterprise Manager appliance create an EMCO backup of its own configuration database, or is EMCO only intended for the documented migration scenarios?
• If EMCO is not the supported DR path for Linux-to-Linux recovery, is there any other supported recovery method?
• Or is redeploying Enterprise Manager and manually reconfiguring it the only supported approach?

We are specifically asking about a DR/redeployment scenario for an existing Linux-based Enterprise Manager appliance, not a Windows-to-Linux migration.
If there is a supported procedure, could you please point us to the relevant documentation or clarify the intended product behavior?

Thank you.