From owner-freebsd-questions@FreeBSD.ORG Fri Oct 16 15:47:55 2009 Return-Path: Delivered-To: questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id E3CE6106566B for ; Fri, 16 Oct 2009 15:47:55 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) by mx1.freebsd.org (Postfix) with ESMTP id A01ED8FC12 for ; Fri, 16 Oct 2009 15:47:55 +0000 (UTC) Received: from r55.edvax.de (port-92-195-71-245.dynamic.qsc.de [92.195.71.245]) by mx02.qsc.de (Postfix) with ESMTP id 8ABB61E33D; Fri, 16 Oct 2009 17:47:53 +0200 (CEST) Received: from r55.edvax.de (localhost [127.0.0.1]) by r55.edvax.de (8.14.2/8.14.2) with SMTP id n9GFlqw9001475; Fri, 16 Oct 2009 17:47:52 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Fri, 16 Oct 2009 17:47:52 +0200 From: Polytropon To: Warren Block Message-Id: <20091016174752.14724f2a.freebsd@edvax.de> In-Reply-To: References: <560f92640910142042tc46f1e3lb81ac1e4528a44ab@mail.gmail.com> <20091015143947.GB54613@gizmo.acns.msu.edu> <560f92640910151742h33393131j9974c23db37602b8@mail.gmail.com> Organization: EDVAX X-Mailer: Sylpheed 2.4.7 (GTK+ 2.12.1; i386-portbld-freebsd7.0) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Jerry McAllister , questions@freebsd.org, Nerius Landys Subject: Re: Best procedure for full backup of live system X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Polytropon List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 16 Oct 2009 15:47:56 -0000 On Thu, 15 Oct 2009 21:47:57 -0600 (MDT), Warren Block wrote: > Just a general note: backup to a hard drive isn't bad, but it's not the > same as removable media. One failure can kill all of your backups... That's why it's often a good choice two have at least two hard disks (maybe external ones) for backup, so if one fails (which seems to be a problem of "modern" disks rather than older ones), there's still an intact backup on the other one (or on one of the others). > Backup in general is making copies of information > you won't need as long as you have a backup of it.a A wise summary. :-) > dump(8) doesn't do all sectors, just ones used by the filesystem. > > Also, dump doesn't cross filesystems. In a typical FreeBSD install, /, > /var, and /usr are separate filesystems. A dump of / won't get them all > at once. The dump utility is good when you want to work partition-wise. If you have a setting where everything goes into a big /, dumping it will get all data - from that partition. Slices and MBR are out of dump's scope. > > My server should boot fine with the FreeBSD CDROM (fixit), because it > > uses a subset of the GENERIC kernel device drivers. > > If you can, try that before an actual emergency. Furthermore, it's good to check backups regularly. A defective backup is NO backup. If data doesn't restore as intended (e. g. to a testing system), then...? A situation that many of you surely have come across, as I have: Operator: The hard disk crashed, we need to restore from backups. Customer: Of course I have backups! Here! Customer hands over three tapes. Operator starts restore with tape #1. Operator: First tape is through. Good. Next one. Computer displays rroor reading /dev/nsa0: Tape is defect, cannot read. Operator: Do you have other set of tapes? This #2 is defective. Customer: Yes! Tape #3! Operator: I need a working tape #2. Customer: BUT I *HAVE* BACKUPS!!! Testing the backups may take some time, I agree, but it's mostly worth it - it's worth as much as your data is to you. -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...