Thanks. I also used "disaster recovery" with the "offline backup" option before. I also just noticed: Every time I open the backup settings, the email address field is empty. Btw: It is really confusing that it still says "disaster recovery" while the documentation uses other names....

@tmk do you not monitor elsewhere ? (zabbix/centreon/...)

@mguimond Not sure how old your XO is but this is the current Commit. Master, commit 5349f. Suggest try updating and try again. Maybe someone from Vates will have more information.

@Mathieu +1 We have the same problem. Changing a bit in the mac-address of the replicated/DRed VM seems to get the plugin to accept to sync again. But obviously not a good solution.

@Chico008 I think it's not a bug, it's a feature.

Ping @Team-Documentation-Knowledge-Management

@probain No worries, im still learning/improving my ansible/terraform skills aswell

Small warning: XenTools are still a clusterfuck. On (allmost) all machines without our main environment it keeps the ip-configuration within the Realtek emulated NIC and never transfers it to the Xen device. It's fucked for long now - but doesn't matter if all VMs are getting their IPs via DHCP. Currently struggling with: Windows Server 2016 + XenTools/Management 9.4.2. At least it didn't break the whole VM by destroying the disk device drivers this round. tl;dr: Snapshot your VMs and have a documentation at hand, when upgrading the tools/drivers.

Hi @jshiells, After some tests, I don't think it can be caused by the load balancer. If the load balancer tries to migrate a VM that is being backed up, the migration instantly fails and nothing happens. Reversely, if a backup job starts when a VM is being migrated by the load balancer, the backup will fail for that VM with error "cannot backup a VM currently being migrated".