From owner-freebsd-questions@FreeBSD.ORG Thu Jan 22 17:38:13 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id DB5F0C46 for ; Thu, 22 Jan 2015 17:38:13 +0000 (UTC) Received: from mail-ie0-x231.google.com (mail-ie0-x231.google.com [IPv6:2607:f8b0:4001:c03::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 9E7759A7 for ; Thu, 22 Jan 2015 17:38:13 +0000 (UTC) Received: by mail-ie0-f177.google.com with SMTP id vy18so2662581iec.8 for ; Thu, 22 Jan 2015 09:38:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=KT7VqN+4LZC3jw+uslUQfYopv+whRjpn7gwVHWsD03A=; b=UAx7yGhlDvzUJyQtqROk9DBMViN+jWdQ/IgFEf8c0bbO8kHufTb6gGDeB9LGBXVEx3 2lclWqlGJMLMZ6A3UsvfOHwJAA+lM24QzhzYMJnUsLcYOTBe2Eq5WhOgaJZv5fPc/NyN qsng7Bh2Mmq5CKFfPs/gvS/ICmn4oJlqJu99zhGDHNbRvH+rizC8yUvflBxSgMCwkt2X NqYUWOE75UrmSNcS7VBSlVhsp9bCBrChh5FCDrQZ4dFGy9+TYNv/wpC9PeRVbHpIPGAh u/bQnsbXav7JdikP92j+d57X6/UX5o9AeEXvhwwkBawNfcWTIsJvrmhtL+nEq9F2AgEs /oKA== MIME-Version: 1.0 X-Received: by 10.42.130.7 with SMTP id t7mr4407905ics.25.1421948292928; Thu, 22 Jan 2015 09:38:12 -0800 (PST) Sender: christopher.maness@gmail.com Received: by 10.36.122.212 with HTTP; Thu, 22 Jan 2015 09:38:12 -0800 (PST) In-Reply-To: <54C120E6.5090301@corp.ssimicro.com> References: <20150120010551.c17d9f50.freebsd@edvax.de> <54C120E6.5090301@corp.ssimicro.com> Date: Thu, 22 Jan 2015 09:38:12 -0800 X-Google-Sender-Auth: RsUvxnS2kbNCDFURBumPU5SGXT0 Message-ID: Subject: Re: Dump/Restore for system migration From: Chris Maness To: markham breitbach Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: "freebsd-questions@freebsd.org" 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 17:38:13 -0000 On Thu, Jan 22, 2015 at 8:10 AM, markham breitbach < markhamb@corp.ssimicro.com> wrote: > > 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 > > > That actually sounds pretty good. The target system has been running for a few days source system powered off. I am not sure if a rsync right now would do more harm than good. However, I do understand that rsync will ignore files that have already changed. I use rsync -vaur flags on most of my backups. Thanks, Chris