[FEATURE REQUEST] - eeam Software Appliance can't replicate itself

[Pistok]

I tried made "backup" to a replica computer (as all other) the newly installed VeeamAppliance, and I received an error message:
2026. 05. 14. 3:30:10 Warning : The Veeam Software Appliance cannot be added to backup jobs to protect itself (appliancename)

Earlier checked the limitations page, and it doesn't mention it.
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13
It mention only this: You cannot use third-party software to back up or restore a Veeam Software Appliance.

The problem not only cannot added in backup jobs, also can't add into a replica job. So I have had to make a replica by hand (stop server, clone server, start server). That's really strange and strong from veeam.

Case #08093610

The replica job's error messages:

The Veeam Software Appliance cannot be added to backup jobs to protect itself (CAD-VeeamBackup)
Error: Failed to connect to VM. [Failed to connect to guest agent. Errors: 'Failed to connect via WebAPI. ']

Failed to prepare guest for hot backup. Error: Failed to connect to VM. [Failed to connect to guest agent. Errors: 'Failed to connect via WebAPI. ']
Error: Failed to connect to VM. [Failed to connect to guest agent. Errors: 'Failed to connect via WebAPI. ']
Processing finished with errors at 5/13/2026 4:08:49 AM

[PTide]

Hi,

This is by design.

If you want to ensure proper recovery and availability, then I'd suggest configuration backup and HA.

Thanks!

[Pistok]

That's a really stone aged thing.
This feature worked well in the previous (all) solution. Then "misteriously gone".
Now here something which sounds a lazy solution - to duplicate a complete computer resurce and configure a HA system to get back that function what worked well in the last 12-13 years,

[Pistok]

Also my problem: The appliance limitation page doesn't mention this - i think - huge limitation!

[pma]

Hi Lukács,

Thank you for your feedback. We have updated the limitations page to reflect this behavior: https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

The reason for this limitation is security. VSA is designed as a secure-by-default, zero-trust black-box solution. This means that even if a Veeam Administrator account is compromised, an attacker cannot gain access to all secrets stored in the VBR database.

Operations such as backup and restore of the VSA appliance would expose this attack surface and potentially enable such an attack vector. To maintain the intended security model, these operations are therefore not permitted for VBR users.

[Pistok]

Hello @pma

For my side: Thanks for nothing. I migrated to a new system, and delete the originals, because of obsolete. Now I have to tell my boss I finished this project earlier, but now I have to migrate back to windows, because partial limitations documentation? Also ask for budget for windows licenses, for re build that system, and migrate back from this sh!t?

You mentioned something which works as well on windows server, and give some BS about security? If these security problems available on Windows server... and noone has problem with it... then why don't have a solution here? On windows server (also the earlier the windows workstation was enough) the Veeam B&R can be repicate itself without any problem. Also/or why don't have a "checkbox mentioned I understand the risk, but I want to backup my server?"

I hate the corporate BS when they do something wrong, problematic - arriving an answer "Ok, we put into that documentation, because this is the easiest ach cheapest way to do nothing about customer's problem". I using veeam product over a decade, and this is the first time, when I found out when the veeam managing the users exactly same as other multi.

[pma]

Hello,

For many years, the recommended and supported approach for protecting the Veeam Backup & Replication server has been to use the built-in Configuration Backup functionality. This allows the Veeam configuration database to be restored to a new VBR server if the original server is lost.
More information is available here:
https://www.veeam.com/kb2645
https://helpcenter.veeam.com/docs/vbr/u ... tml?ver=13

If a lower RPO is required for the backup server itself, the High Availability feature may also be a suitable option.

Regarding self-replication of the VBR server: while it may work in some scenarios, it is not the recommended approach. The main concerns are that backup or replication jobs rely on snapshots, and snapshot creation/removal may temporarily freeze the VBR server VM. This can potentially lead to issues such as:

• disconnection from the configuration database;

• disconnection from remote Veeam Backup & Replication agents;

• disconnection from network storage, for example iSCSI-presented storage;

• possible impact on running backup and replication tasks;

• in some configurations, duplicate VM identifiers may also affect HotAdd transport mode when the Veeam server or proxy is replicated within the same vCenter.

For these reasons, Veeam recommends using Configuration Backup and Restore rather than protecting the VBR server with regular backup or replication jobs.

At the same time, our goal is to make sure that all relevant limitations are properly reflected and that our documentation continues to provide clear and accurate guidance.

I also have added your request to the feature request list to consider an option that would allow customers to explicitly acknowledge the risks and proceed with self-replication if they choose to do so.
It would be very helpful if you could share a few more details about why Configuration Backup does not fully meet your requirements in this case. Understanding your RPO/RTO expectations and any operational constraints will help us better evaluate the request and possible improvements.

Thank you again for your feedback and for helping us improve the product and documentation.