Date: Thu, 26 Mar 2009 12:23:44 -0500 From: "Jack L. Stone" <jacks@sage-american.com> To: Karl Denninger <karl@denninger.net>, Jake Scott <jake@poptart.org> Cc: freebsd-stable@freebsd.org, fs@freebsd.org Subject: Re: support quality (Re: dump | restore fails: unknown tape headertype 1853384566) Message-ID: <3.0.1.32.20090326122344.00ee69f0@sage-american.com> In-Reply-To: <49CBA34B.9070708@denninger.net> References: <alpine.BSF.2.00.0903261432350.31074@cyhz.syveoyr.bet> <3.0.1.32.20090326065337.00f081e0@sage-american.com> <3.0.1.32.20090325072137.00ee6b48@sage-american.com> <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> <alpine.BSF.2.00.0903261432350.31074@cyhz.syveoyr.bet>
next in thread | previous in thread | raw e-mail | index | archive | help
At 10:46 AM 3.26.2009 -0500, Karl Denninger wrote: >Jake Scott wrote: >> >>> That said there are plenty of other reasos to use proper dump tools >>> (data portability, confirming the ability to actually read all rows >>> from a table, using a more often exercised code path and perhaps less >>> likely to have edge case bugs, etc). >> This thread has drifted off the main issue of using the FS dump/restore problem. Although, the DBs may be included as a part of this dump, it should NOT be relied upon as a backup/restore of DBs. We use MySQL's dump/backup tools strictly for the DBs. The dumps of the DBs (using MySQL's own dump tool) here are run by cron jobs every hour or few hours at most. That keeps our DB backups very recent and near current as possible is a restore is needed. Jack (^_^) Happy trails, Jack L. Stone System Admin Sage-american
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.1.32.20090326122344.00ee69f0>