From owner-freebsd-virtualization@freebsd.org Mon Jan 22 19:47:21 2018 Return-Path: Delivered-To: freebsd-virtualization@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 2CAC7ED2215 for ; Mon, 22 Jan 2018 19:47:21 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id EFBFF6B350 for ; Mon, 22 Jan 2018 19:47:20 +0000 (UTC) (envelope-from tech-lists@zyxst.net) Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id B87D620FC0 for ; Mon, 22 Jan 2018 14:47:18 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute4.internal (MEProxy); Mon, 22 Jan 2018 14:47:18 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=zyxst.net; h= content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=SuUgQclq7JMvE+pv+Ug7hWpsj3LSc iMIgfVUXAK1QiE=; b=Jjg8veXGexanepk6G6dh6NOJLKTdLU6bQLWNrY+7sfQ4A dkBWja5gDYZtF8w3K+Oec0oFlh1kmUrGtfLKhrd9ZFgcMSPom23v3EvPA26QwNH5 9F9uCnL0QJh1vS4ksPTUxZ1Ywh1SlDeypGqdGVstyGDc/+xU+ltVqdZv4S1pEAZS q1ptXgGXKljPF5cKOFjxuYjjfZ7syFkB2nTsogEpcrCC78awyEZbldKfYaz6uS/0 wUASeUi0CWD4nxjvfr8gZIevhf3OL556VQUmhjGgxsKhgH+HV2ZnFWI+6TRJW7rK SN3VCYEw+9UXCoAqu7NYi8hkKXOROcWhQ4XRoBnRA== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=SuUgQc lq7JMvE+pv+Ug7hWpsj3LSciMIgfVUXAK1QiE=; b=fQ8Nml+mm9DaRwGvCYqZ0h oEqMPYe9p7tB7Sm9YKZ4Cgfp6itlI5O4WCxsoTnb/GmIDHByGume6NZKtHyLthh6 X1sEuvPdBaHyn2uzVC1aXImiUJF4hIwbmxhtZYFCIROXpw146tQ36OswDVzP+Jrx jIz9hymVzGgXoWn47qev81mugqxMErj8x2pvhQASIB9KxWfZ++N12uE4AS4rOhEx 4RxHHl8Kmv32I+QysCl4GlKuV2Rit5hhZw1viqO8uuK3TcZMru3DK/RzBLTWGkIu ndTTSr3Y3JkCe8ArRJ7YrHBzgb3YdF6GiyDlY4HT3HWVa+CwfxWloTHmAFxARhGg == X-ME-Sender: Received: from desktop.parsley.growveg.org (parsley.growveg.org [82.70.91.97]) by mail.messagingengine.com (Postfix) with ESMTPA id 39C49240F8 for ; Mon, 22 Jan 2018 14:47:18 -0500 (EST) Subject: Re: syncing bhyve instances To: freebsd-virtualization@freebsd.org References: <5A66137D.5090608@redbarn.org> From: tech-lists Message-ID: Date: Mon, 22 Jan 2018 19:47:16 +0000 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <5A66137D.5090608@redbarn.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-GB Content-Transfer-Encoding: 8bit X-BeenThere: freebsd-virtualization@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: "Discussion of various virtualization techniques FreeBSD supports." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 22 Jan 2018 19:47:21 -0000 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. Yeah, thought it might be this. Sorry I wasn't more clear initially about the use case. 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? thanks everyone who took the time to answer -- J.