Hi guys, I've been reading Maatkit documentation, High Performance MySQL 2nd Edition, and googling to try to learn what my options are in terms of backing up and recovery of MySQL.
For our database layer, we will be launching with several physical machines, each of which will have MySQL 5.1, RAID-10 (hardware), NO LVM, and will have about 1000 database shards, with all tables using the INNODB engine. In the documentation for mk-parallel-dump (http://www.maatkit.org/doc/<http://www.google.com/url?sa=D&q=http://www.maatkit.org/doc/&usg=AFQjCNEW7nDyG7G4-qE1px0Kd7pAm8ZWcQ> mk-parallel-dump.html), it says: "...mk-parallel-dump is not a backup program! It is only designed for fast data exports, for purposes such as quickly loading data into test systems. Do not use mk-parallel-dump for backups..." But in the book, it seems to point that mk-parallel-dump can be used as a backup solution. So my questions are: 1. Can mk-parallel-dump be used to backup the innodb databases? 2. Is it recommended to use innodb_file_per_table option? 3. What do you recommend for specific documentation, methodologies, techniques for raw and logical backups? Thanks, Konstantin
_______________________________________________ New York PHP Community MySQL SIG http://lists.nyphp.org/mailman/listinfo/mysql NYPHPCon 2006 Presentations Online http://www.nyphpcon.com Show Your Participation in New York PHP http://www.nyphp.org/show_participation.php
