From owner-freebsd-questions@freebsd.org Fri Aug 28 14:08:37 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 1E1DD9C4826 for ; Fri, 28 Aug 2015 14:08:37 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from fly.hiwaay.net (fly.hiwaay.net [216.180.54.1]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DFB021D0B for ; Fri, 28 Aug 2015 14:08:36 +0000 (UTC) (envelope-from wam@hiwaay.net) Received: from kabini1.local (dynamic-216-186-222-143.knology.net [216.186.222.143] (may be forged)) (authenticated bits=0) by fly.hiwaay.net (8.13.8/8.13.8/fly) with ESMTP id t7SE8XY7014605 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO) for ; Fri, 28 Aug 2015 09:08:34 -0500 Subject: *Caution: Threadjack !!!!* Backup strategies (was: Replacing Drive with SSD) References: <55E047DC.40800@qeng-ho.org> Cc: FreeBSD - From: "William A. Mahaffey III" Message-ID: <55E06B61.7040305@hiwaay.net> Date: Fri, 28 Aug 2015 09:14:03 -0453.75 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit 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: Fri, 28 Aug 2015 14:08:37 -0000 On 08/28/15 07:55, Damien Fleuriot wrote: >> On 28/08/2015 07:59, Doug Hardie wrote: >> >>> I am having to replace a drive with a SSD. Normally if I were >>> >>> replacing it with another drive, I would hook up the new drive >>> to the computer and just use dd to copy everything (system would >>> be quiescent). Can I do the same with a SSD or does it need to >>> be setup differently? This is a boot drive (i.e., the only drive >>> in the system). The system is currently working fine, but the >>> drive temp is starting to go up so I want to replace it before >>> anything bad happens. >> > Any reason you're not using dump/restore ? > Now that would skip empty blocks :) > That would allow you to expand your partitions, in the process. > > Warren Block has a very good guide over there : > http://www.wonkity.com/~wblock/docs/html/backup.html > _______________________________________________ > freebsd-questions@freebsd.org mailing list > https://lists.freebsd.org/mailman/listinfo/freebsd-questions > To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org" > Warren's (fabulously lucid) page brings up a question for me. For years I have used a 'pull' strategy for across-the-LAN backups, w/ my 'backup servers' using tar or rsync to access data for backup on NFS-mounted (or automounted) directories that I want backed up. This all happens automatically overnight under cron. I am usually *not* backing up system files, but rather user data, although I have recently started backing up system stuff as well. Warren's page consistently illustrates a 'push'-ed backup, & involves system files. I am *dead* serious about automated backups, no possibility of forgetting to do it that way, but I always thought that trying to backup 'live' system files was a bad idea (right/wrong ?). There doesn't seem to be a way to do a 'push' backup w/o messing with live system files. I guess I am asking about 'best practices' for backups, & the wisdom/validity of backing up 'live' system files. Sorry for rambling, but the question(s) popped up for me while reading Warren's web page. Any input appreciated. Have a nice day & weekend :-). -- William A. Mahaffey III ---------------------------------------------------------------------- "The M1 Garand is without doubt the finest implement of war ever devised by man." -- Gen. George S. Patton Jr.