From owner-freebsd-questions@FreeBSD.ORG Thu Jan 22 16:10:14 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 97DD3A4D for ; Thu, 22 Jan 2015 16:10:14 +0000 (UTC) Received: from mail.ssimicro.com (mail.ssimicro.com [64.247.129.10]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.ssimicro.com", Issuer "RapidSSL SHA256 CA - G3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 4CD69A71 for ; Thu, 22 Jan 2015 16:10:13 +0000 (UTC) Received: from markham.ssimicro.com (markham.ssimicro.com [64.247.130.99]) (authenticated bits=0) by mail.ssimicro.com (8.14.7/8.14.7) with ESMTP id t0MGAB2G009430 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT) for ; Thu, 22 Jan 2015 09:10:12 -0700 (MST) Message-ID: <54C120E6.5090301@corp.ssimicro.com> Date: Thu, 22 Jan 2015 09:10:14 -0700 From: markham breitbach User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-questions@freebsd.org Subject: Re: Dump/Restore for system migration References: <20150120010551.c17d9f50.freebsd@edvax.de> In-Reply-To: <20150120010551.c17d9f50.freebsd@edvax.de> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Jan 2015 16:10:14 -0000 On 2015-01-19 5:05 PM, Polytropon wrote: >> Is there a better way to do this? > Usually not, because dump + restore is _the_ way to do it. > Except of course you're using ZFS. :-) I have often done system migrations using rsync over ssh something like rsync -aHv / root@targethost:/ The great thing about rsync is that is will only transfer what it needs to, so the first run will take a while to get pretty much everything over. I then run a second time with a --delete switch to catch anything that changed while the first run was going (A full sync of my mail store can take well over 24 hours!). The second run will go much faster, depending on the size of the initial run. Finally, I will mount RO, so I know nothing is changing and run a final sync, which usually only takes a couple of minutes, then light up the new system. If you already have a system dump/restore you could also just use rsync as the final step to catch the stragglers. -Markham