Hotswap server backups
-
I think this would be a luxury/business/pro feature.
Can we consider a way to have 2 x Cloudrons:
One would be the live and active server.
The second would be the destination for backups but directly cloning to a second instance as a hot-swap.
The use case would be faster recover from a total server failure or some kind of provider issue.
It could be a second VPS with the same provider (I appreciate server snapshots are also an option there), or with another provider.
I appreciate this is not a high-availability setup, and there would be data-loss in the event of needing - but that's no different to a backup restore.
Switching to the hot-swap would just involve updating the DNS A record for the hot-swap, and then logging into it to trigger it to update all other DNS managed by the Cloudron.
It can come with all the usual warnings on data-loss from swapping, and not recommending swapping back after etc.
-
@jdaviescoates within the same provider, sure. I found an article on something similar for a wordpress managed platform, will see if I can remember what it was...
-
-
The hard part is not the DNS failover but how to keep the data in sync between two servers. This is easy if the data is "static". Indeed, for static stuff, you can just probably put into some CDN and you are good. For dynamic stuff, you have to somehow sync the files/database etc. To design this is very application specific. Does anyone of a product that does this? Would be good to know how they approached it/solved it.
(AWS does this with multi-AZ deployments but these are for apps you developed. And also these are quite expensive solutions.).
-
@girish Hey. Yeah, the point is it wouldn't be any more in sync than the backups. Rsync would make it a bit friendlier for a more frequent update interval.
Completely respect this isn't true high-availability (Unless you use MariaDB Cluster or PerconaDB Xtra-DB )
Unison could work for more up-to-date file replication:
-
This is easier with Yugabyte DB.
