From owner-freebsd-stable@FreeBSD.ORG Thu Mar 26 15:35:32 2009 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8D738106564A for ; Thu, 26 Mar 2009 15:35:32 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from hedwig.simons-rock.edu (hedwig.simons-rock.edu [208.81.88.14]) by mx1.freebsd.org (Postfix) with ESMTP id 54CFD8FC16 for ; Thu, 26 Mar 2009 15:35:32 +0000 (UTC) (envelope-from peter@simons-rock.edu) Received: from cesium.hyperfine.info (c2.8d.5646.static.theplanet.com [70.86.141.194]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by hedwig.simons-rock.edu (Postfix) with ESMTP id B74002BB36B; Thu, 26 Mar 2009 11:35:30 -0400 (EDT) Date: Thu, 26 Mar 2009 11:35:29 -0400 From: "Peter C. Lai" To: Jake Scott Message-ID: <20090326153528.GH13398@cesium.hyperfine.info> References: <49C9E635.5010106@kkip.pl> <49C83673.3000604@aldan.algebra.com> <200903251820.54749.doconnor@gsoft.com.au> <200903251925.36108.doconnor@gsoft.com.au> <3.0.1.32.20090325072137.00ee6b48@sage-american.com> <3.0.1.32.20090326065337.00f081e0@sage-american.com> <3.0.1.32.20090326070807.00f081e0@sage-american.com> <200903261331.n2QDVd4b038485@lava.sentex.ca> <20090326140131.GA45201@hyperion.scode.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.17 (2007-11-01) Cc: "Jack L. Stone" , Peter Schuller , fs@freebsd.org, freebsd-stable@freebsd.org Subject: Re: support quality (Re: dump | restore fails: unknown tape headertype 1853384566) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Mar 2009 15:35:33 -0000 On 2009-03-26 02:45:45PM +0000, Jake Scott wrote: > Absolutely. You really must use a tool that interacts with the database to > perform the backup. Most commercial DBs have hooks that allow the backup > routines to call out to custom snapshot facilities. One would usually > request a backup through the database, which would then freeze IO to its > data files and maybe log files, deal with flushing caches etc and then call > your snapshot routine. I'm not aware that MySQL and Postgres do though so > the best you can do is a dump. With MySQL at least, you can (ab)use the replication facilities so that you can set up a "slave" and do the fs-level dump while the slave is in a "frozen" state - the last time I played with MySQL, you could basically desync your slave for a period of time (basically until transaction logs are purged on the master), during which the slave will be consistent; do the fs-level backup then kick the master to sync with the slave again. -- =========================================================== Peter C. Lai | Bard College at Simon's Rock Systems Administrator | 84 Alford Rd. Information Technology Svcs. | Gt. Barrington, MA 01230 USA peter AT simons-rock.edu | (413) 528-7428 ===========================================================