Date: Tue, 23 Jan 2018 14:00:22 +0100 From: Michael Gmelin <freebsd@grem.de> To: tech-lists <tech-lists@zyxst.net> Cc: freebsd-virtualization@freebsd.org Subject: Re: syncing bhyve instances Message-ID: <8BCCEBAF-EDA9-421B-815A-FB4E1BA5B57B@grem.de> In-Reply-To: <d32d894b-7015-7eff-c5d2-795d76e8c5f6@zyxst.net> References: <d51c09bc-fbe3-4d79-2228-c8b9742db768@zyxst.net> <5A66137D.5090608@redbarn.org> <d32d894b-7015-7eff-c5d2-795d76e8c5f6@zyxst.net>
next in thread | previous in thread | raw e-mail | index | archive | help
> On 22. Jan 2018, at 20:47, tech-lists <tech-lists@zyxst.net> wrote: >=20 >> On 22/01/2018 16:38, Paul Vixie wrote: >> for live sync you'll have to run software inside the guest that knows >> how to properly freeze state. for example if there's a live database of >> any kind you'll want it to be in its quiet state before you sync from >> it. in those situations, i do use rsync. >=20 > Yeah, thought it might be this. Sorry I wasn't more clear initially > about the use case. >=20 > Basically, the production server is in a datacentre and the reserve > server is on a very fast vdsl service. The reason for the reserve server > is, if the production server fails then I swap DNS to point at the > reserved server and the guests on it without interruption of service. > All guests are running databases (mysql) though they aren't especially > busy. So I guess the best bet would be mysql replication for the > databases and rsync for everything except mysql? >=20 > thanks everyone who took the time to answer For the database, mysql replication is the way to go (otherwise you would ne= ed to stop/lock the server every time you do a snapshot and you'll get near-= realtime replication which will always be more current than your snapshots).= For the system I'd suggest to create automation for the setup, so you can a= pply changes to both systems without a need to sync/clone/copy from one to t= he other. For anything else left (data files on disk, non-system, non-packag= e, non-config) use regular rsync (or zfs send if your setup permits - I'd st= ick with rsync). Yours, Michael p.s. Make sure to include monitoring (especially replication latency and dat= a integrity) >=20 > --=20 > J. > _______________________________________________ > freebsd-virtualization@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-virtualization > To unsubscribe, send any mail to "freebsd-virtualization-unsubscribe@freeb= sd.org"
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8BCCEBAF-EDA9-421B-815A-FB4E1BA5B57B>