From owner-freebsd-questions@freebsd.org Wed Jul 1 18:12:58 2015 Return-Path: Delivered-To: freebsd-questions@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 83C1B992AD8 for ; Wed, 1 Jul 2015 18:12:58 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: from mail-qk0-f181.google.com (mail-qk0-f181.google.com [209.85.220.181]) (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 478021EEE for ; Wed, 1 Jul 2015 18:12:58 +0000 (UTC) (envelope-from paul@kraus-haus.org) Received: by qkeo142 with SMTP id o142so35446639qke.1 for ; Wed, 01 Jul 2015 11:12:50 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:content-transfer-encoding:message-id:references:to; bh=HtUCaVdDkWIwA9Kdr2r1T+PlhyO5ovj4cquwaLhEhic=; b=gwJRUGZlE4FawbFSXhaN2MLsUHVXLpOiK8BuvNI2ZJFtfiOnexK1PSVatMNogOa16V rWZMZHQN5VVtqTYYl5cq3LQk0cYaqnYEHz4v3xAVFiZQL8Sxfg2tzc2in3OxnotrfhCG BDx3lYBE2kgh6C6aIijZS1VugLi+J/7hfQrc1r3+Fcjm3esvBiwY3Td+pgnr2vKk3pdc UznAA1iLWDeucplFwDLQQV+wY5Sj1qq0qkrFmh0wmLtBHk87UMWs0mqRs4aegZP+i2pP yPLGtVuF5G6Qi0vhwG2RMftTSpHXMVrOt6Tikta3nnnxxZpn30nD7g16toJdjmn5Pvjh aBSQ== X-Gm-Message-State: ALoCoQlak5u0k1DQRUeNnLK0NtsqBEuzSVwcmLuCdNV7IaiNshoSJO6sLqyeCpy8FVnEEoK3idiJ X-Received: by 10.140.202.65 with SMTP id x62mr37444391qha.102.1435774370695; Wed, 01 Jul 2015 11:12:50 -0700 (PDT) Received: from mbp-1.thecreativeadvantage.com (mail.thecreativeadvantage.com. [96.236.20.34]) by mx.google.com with ESMTPSA id b31sm1402319qge.5.2015.07.01.11.12.47 (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 01 Jul 2015 11:12:48 -0700 (PDT) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.3 \(1878.6\)) Subject: Re: Clarification on simple, incremental ZFS backup From: Paul Kraus In-Reply-To: <86y4izajna.fsf@WorkBox.Home> Date: Wed, 1 Jul 2015 14:12:49 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <8EDC3394-3288-4D75-9A94-1589732DACEE@kraus-haus.org> References: <861tgsaruw.fsf@WorkBox.Home> <55940F2E.6060009@freebsd.org> <86y4izajna.fsf@WorkBox.Home> To: FreeBSD Questions X-Mailer: Apple Mail (2.1878.6) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Jul 2015 18:12:58 -0000 On Jul 1, 2015, at 13:10, Brandon J. Wandersee = wrote: > Sure, but then what happens in the worst-case scenario, where the = source pool > needs to be clobbered and replaced? That's what I understood the = purpose > of replication to be--a means of completely restoring a system that's > beyond recovery. If I were to create a snapshot and then send it to = the > backup drive, I couldn't later restore a complete filesystem from it, > could I? I'd need a complete replica to make that happen, correct? You need to start with a FULL stream, then you apply incremental streams = to it. On the replica you end up with all the snapshots from the source. = So the process I follow is: Take a snapshot Send full stream -> recv to a designated backup pool (all it contains = are copies of other datasets) Take another snapshot Send incremental stream of changes between two snapshots -> recv to same = dataset repeat ... I take hourly snapshots on all my datasets and replicate nightly. If you need a full recovery you zfs send a FULL stream in the reverse = direction (and you can choose which snapshot to send, and even send them = all once the first FULL is done using -I). -- Paul Kraus paul@kraus-haus.org