We are running asynchronous Protection Domains and also employee Veeam backups of VMs. If we failover to the secondary site and then failback to the primary site, Veeam no longer recognizes the VMs in previously created backup jobs. We have to delete all the old backup jobs and set them up again. This is with ESXi hosts. Is that normal?
Already have an account? Login
Login to the community
Login with your account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
I didn’t face this issue before, however, you should open a case with Veeam support. Also, you can leverage Veeam Replication instead, no additional license required. Veeam Replication with ESXi will give you the same Failover, Failback, and more.
During the failover process, failed over vm is unregistered from the main site cluster and VM is registered in the DR Site.
Same process if repeated during the failback process.
Veeam Backup jobs are based on the VM names. I don’t think its a issue you might face issue for incremental backups.
did you try to run the full backup ? please share backup failure error for more details