GitHub user TheKunalSen edited a discussion: Disaster recovery in cloudstack
So I have built a cloudstack setup where I have a nfs server, 3 hosts and 1 management server in one zone (172.16.17.0/24) And I have created a system gateway vm which is connected to a cloudflare tunnel and serving all my websites (routing the traffic into the internal 10.x.x.0/16 vms) through reverse proxy. For in-zone ha if the host goes down the vms migrate to another host this is okay But if I want to build a desaster recovery system where if this site goes down totally i still want my websites to be alive! There are a couple methods I have thought Which are 1. I build a site b setup almost same as this one and copy all the vms and all to that setup and setup a cloudflare tunnel load balancer which will load balance the traffic between two sites (note that the site b would be a new zone in that same management server which will be in a different public ip network 192.168.1.0/24) But in this case the problem is suppose I have 100 vms and I copied all of them manually to site b-zone-b and it's working, but if I create another vm on site-a-zone-a and I want that vm to replicate to site-b-zone-b, how is this possible cause the nfs storage would be different, the host ids would be different, the only thing which will be connected are the management servers. 2. If I try to add a site-b host which is on a different network on this zone then connect both the network on site to site vpn then the hosts gets added but the system vms on that host doesn't work or the agent states stays blank, even if i create another pod on that site -b network inside that site-a-zone-a the hosts gets added but the vms doesn't work properly, if this thing happens then host from different sites can migrate the vms between themselves. What do you think what would be the best strategy for desaster recovery in cloudstack for me! GitHub link: https://github.com/apache/cloudstack/discussions/13146 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
