hi, there will not be a lot of paying backup tools if just copying files is OK. You can't because active transactions change some files checkpoint, then you copied files are not at the same checkpoint state, and you can't use the copy for a restore.
The only way is to lock all the tables if you want to copy files. But this is not good if you have a mssive transactionnal DB (a lot of redo log will be generated during backup with locked tables). This can be a solution because hot backup of an oracle database uses this macanisme of macking a tablespace in backup mode. Mathias Selon "Ashley M. Kirchner" <[EMAIL PROTECTED]>: > > With all this discussion going on about the best way to backup MySQL > data, I have a question: Is there anything wrong with simply copying > the db files when you're backing up, as opposed to doing a full shutdown > of the server (regardless of whether it's a master or slave) and then > doing a dump of the data? (Note the difference, one will copy files, > the other dumps the data for backup.) > > -- > W | I haven't lost my mind; it's backed up on tape somewhere. > +-------------------------------------------------------------------- > Ashley M. Kirchner <mailto:[EMAIL PROTECTED]> . 303.442.6410 x130 > IT Director / SysAdmin / Websmith . 800.441.3873 x130 > Photo Craft Laboratories, Inc. . 3550 Arapahoe Ave. #6 > http://www.pcraft.com ..... . . . Boulder, CO 80303, U.S.A. > > > > > -- > MySQL General Mailing List > For list archives: http://lists.mysql.com/mysql > To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED] > > -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
