From owner-freebsd-questions@FreeBSD.ORG Fri Jun 22 16:09:06 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id F0B0C106567B for ; Fri, 22 Jun 2012 16:09:05 +0000 (UTC) (envelope-from perrin@apotheon.com) Received: from oproxy6-pub.bluehost.com (oproxy6.bluehost.com [IPv6:2605:dc00:100:2::a6]) by mx1.freebsd.org (Postfix) with SMTP id B6C558FC12 for ; Fri, 22 Jun 2012 16:09:05 +0000 (UTC) Received: (qmail 2388 invoked by uid 0); 22 Jun 2012 16:09:04 -0000 Received: from unknown (HELO box543.bluehost.com) (74.220.219.143) by cpoproxy3.bluehost.com with SMTP; 22 Jun 2012 16:09:04 -0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=apotheon.com; s=default; h=Content-Type:MIME-Version:Message-ID:Subject:To:From:Date; bh=oSbvLAR1xs50KPQBmobXiHpsA4uAVS39Dyse/RPUTuA=; b=ZYzApJYF3iSkJzwt50qyUQCXWwIg1JfxMQ8y0ZDq04jVAVkKsQCOvFUz7zM8j8ynmkai55VIK7X0KfqswC9nxyR+qzkw5YLoo7naZiEDCwvPXotsA6L6XGR4r1ux6N+m; Received: from [24.8.180.234] (port=60793 helo=localhost) by box543.bluehost.com with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.76) (envelope-from ) id 1Si6Pw-00017o-8g for freebsd-questions@freebsd.org; Fri, 22 Jun 2012 10:09:04 -0600 Date: Fri, 22 Jun 2012 10:09:03 -0600 From: Chad Perrin To: FreeBSD Questions Message-ID: <20120622160903.GE24912@hemlock.hydra> Mail-Followup-To: FreeBSD Questions MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) X-Identified-User: {2737:box543.bluehost.com:apotheon:apotheon.com} {sentby:smtp auth 24.8.180.234 authed with perrin@apotheon.com} Subject: backup tools X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 22 Jun 2012 16:09:06 -0000 I'm setting up a "new" backup server using FreeBSD. It will be used for backing up laptops, which will not be connected to the network by any kind of schedule, so backups will be initiated manually rather than by cron or other scheduled procedures. I'm trying to decide on what tools to use for managing backups. In the past I have used rsync, which has worked reasonably well, but fails one of my desired criteria for the new backup procedures, and is less than ideal for others. My criteria for procedures are: 1. They should minimize the need for additional software beyond the base system as much as reasonably possible. This means not only that I do not want to have to specify the installation of a bunch of stuff, but also that I do not want a bunch of dependencies pulled in with something I choose to install (if anything). Ideally, I should be able to do this with just the base system, though that seems unlikely at this point. 2. They should require only copyfree licensed or public domain tools -- no copyleft licensed tools, no proprietary licensed tools, no noncommercial or nonderivative licensed tools, and no "permissively" licensed tools where the license comes with annoying restrictions such as the Apache License requirements for specific bookkeeping procedures. I might bend on the requirement for non-copyfree "permissive" licenses if I have to, but I'd rather not; bending on any of the others would probably involve just giving up and going back to rsync. 3. They should provide for incremental backups. 4. They should provide for the ability to quickly and easily test backup integrity without restoring the backups anywhere, which most likely means some kind of checksum comparisons akin to what rsync provides. 5. They should allow for transferring data from the system to be backed up to the backup server via SSH. 6. They should use tools as simple as possible, preferably command line tools. 7. There should be documentation somewhere out there for how to set something like this up, someone willing to help me figure out how to get it set up, or an obvious path to setting it up so that I do not spend a week just figuring it all out, if at all possible. 8. They should preferably not require creating a local archive on the laptop before copying to the backup server if it can reasonably be avoided, so that a big chunk of empty HDD space will not need to be maintained for backups to work. Any help figuring out what tools would work for these purposes would be appreciated. I might be able to make exceptions for some parts of this if there are suitable alternative approaches. Thanks in advance for any help I can get in figuring this out. -- Chad Perrin [ original content licensed OWL: http://owl.apotheon.org ]