GitHub user DRDAVIDBANNER added a comment to the discussion: Disaster recovery in cloudstack
Hi Kunal, I’m Pete, CTO at Sendense. This is a use case we handle with Sendense: agentless VM replication and disaster recovery between CloudStack sites. Building on the suggestion above, I’d set this up as two separately operable sites, with site B having its own CloudStack management, compute, storage and networking. Sendense then keeps recovery copies of your workloads ready at the second site and provides the replication, testing and failover workflow. **The source and destination storage can also be different.** You can keep your existing NFS storage at site A and use a different storage type at site B—for example, NFS at one site and block storage at the other. Each site can use the storage that suits its requirements and budget. Sendense handles protection and recovery across those environments, with no NFS workaround needed. The different host IDs and storage locations you mentioned are handled through the destination configuration. Each site uses its own CloudStack resources, and the replica is prepared for the destination’s compute, storage and networks. You don’t need to reproduce the source host IDs or manually reconcile copied disk files. For your setup, the workflow would look like this: 1. **Configure replication to site B.** Select the VMs you want to protect, their destination placement and the replication schedule. 2. **Bring new VMs into the same workflow.** As you add workloads at site A, add them to protection through Sendense, which manages their replication to the recovery site. 3. **Test recovery while production stays running.** Use an isolated test failover to boot the recovered VMs and check that the websites and their dependencies work. 4. **Activate the recovery workloads when needed.** Bring the services up at site B, then use your Cloudflare routing to direct traffic to the recovered environment. For your websites, I’d include the database VMs and gateway/reverse proxy in the recovery plan, then test the complete path from Cloudflare through to the application. That gives you a practical way to verify the service will work from the second site. There’s more on the workflow here: [[Sendense disaster recovery](https://sendense.com/solutions/dr-at-scale)](https://sendense.com/solutions/dr-at-scale). Happy to walk through your two-site layout and show how this would work with your existing NFS setup and the storage you’re considering for site B. GitHub link: https://github.com/apache/cloudstack/discussions/13146#discussioncomment-19267780 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
