Diego Roccia wrote:
> 4/5 times a week, coders call my db administrator saying "ops, I
> dropped/ruined/ate the table X, now I need it as it was yesterday".
> So I need to give DB Admin a tool to quickly restore a single table
> (read "files") as it was x days ago (with 1<x<=4). The version mismatch
> problem is not applicable with this retention.
One thing you should really be aware of, then, is that the practice of
splitting each table out into a set of files is only applicable with MyISAM
tables. Any InnoDB tables will all be stored in the InnoDB table space, which
may be multiple files, but will not be split on any simple boundaries like
tables.
If your goal is to easily restore single tables, check out the --tab option to
mysqldump. It will produce two files for each table, one containing the table
structure and one containing the data. If you combine this with another
structure only mysqldump to capture views, procedures, and other such non
table specific metadata, it should give you what you're looking for.
--
Frank Sweetser fs at wpi.edu | For every problem, there is a solution that
WPI Senior Network Engineer | is simple, elegant, and wrong. - HL Mencken
GPG fingerprint = 6174 1257 129E 0D21 D8D4 E8A3 8E39 29E3 E2E8 8CEC
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
