Skip to main content
Question

veeam 13 backup server appliance disaster recovery

  • April 18, 2026
  • 3 comments
  • 39 views

Hello Community,

 

We have two DC’s and running Veeam 13 for Backup and Replication of VMware Virtual Infrastructure. In previous versions we have backup server VM running in the secondary DC and replicated to the primary DC. In case of loss of secondary DC, we can recover the VM on the Primary DC by simply powering it ON and then recovering any other VMs. However with Veeam 13 we have observed that the Veeam policy doe snot allow the Veeam Server to be replicated. 

What should be the recovery steps for the Veeam backup server (we have deployed the Veeam software appliance)?

My thoughts:

  1. Deploy a new Veeam backup server appliance with same network IP as the previous server.
  2. Import the config backup
  3. Rescan all the backup components.

Is this the right approach or should we deploy the server appliance with a different IP and import the previous backup config?

 

BR,

Sudhir

 

3 comments

Tommy O'Shea
Forum|alt.badge.img+5
  • Veeam Legend
  • April 18, 2026

Does your network subnet span across your multiple sites? If it doesn't you'll need to configure your spare Veeam secret with a different IP. The configuration backup restore can handle going onto a server with a different IP address as long as all the backup infrastructure is resolvable and reachable from the new server. 

If it is on the same subnet, you might be able to consider setting up high availability with a node in each site. 


  • Author
  • Comes here often
  • April 18, 2026

Thanks Tommy for your reply. The network subnets are stretched across both DC’s, unfortunately we have Veeam Advantage and not premium license for HA. The only concern with having a backup server with new IP was about opening firewall ports for all the communication with the new Backup server IP.


Tommy O'Shea
Forum|alt.badge.img+5
  • Veeam Legend
  • April 19, 2026

Rather than messing around with setting the same IP and potentially having duplicate IPs on your network while trying to keep the spare up to date, I'd rather just ensure that all firewall rules are created reference both Veeam IP server addresses. Perhaps in your firewall you can create a host group that contains both.