GitHub user Flpvoigt added a comment to the discussion: Disaster recovery in cloudstack
I would not put the two sites in the same CloudStack zone and expect CloudStack HA to replicate or migrate running VMs across the WAN. CloudStack HA is primarily for host/VM failure within a zone; it is not a complete-site DR mechanism. For this topology, I would use: 1. Separate sites as separate zones (or separate regions if they have independent Management Server clusters), rather than adding site-B hosts to site-A's zone. 2. Replicate the VM data outside the hypervisor layer: use the storage platform's replication or a supported CloudStack Backup & Recovery provider. In CloudStack 4.22+, a cross-zone backup repository can be used to create a new instance in another zone; the repository must be reachable from the destination zone. 3. Replicate/copy the CloudStack database and secondary storage as part of the DR plan. Templates and snapshots alone are not enough if you need the whole environment and its metadata. 4. Replicate the application data as well (database replication, object storage, etc.). Cloudflare Load Balancing can direct traffic to site B, but it does not replicate VM state or application data. A practical runbook is: take scheduled backups/snapshots in site A, copy them to a repository available in site B, keep equivalent networks/offerings/templates in site B, and restore/create the instances there during a site-A outage. Test the restore and DNS/Cloudflare failover regularly. I would avoid live migration across sites unless the hypervisor/storage vendor explicitly supports it with the required latency and shared storage guarantees. References: - https://docs.cloudstack.apache.org/en/latest/adminguide/backup_and_recovery.html - https://docs.cloudstack.apache.org/en/latest/conceptsandterminology/choosing_deployment_architecture.html GitHub link: https://github.com/apache/cloudstack/discussions/13146#discussioncomment-18704874 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
