Claudio, > ehm....the problems is exactly that. On production server you cannot stop or > lock the server so I need > the replication slave mainly for backups (actually MySQL replication is > simply great for this)
Just don't rely on the slave to BE the backup. You can use it to make it easier to take backups, but don't fall into the "slave==backup" trap. An accidental DROP TABLE can show you why slave!=backup. > NOTE: > I have tried Innodb Hotbackup Tool today but it was locking the production > server! Right, it does that :) So it sounds like you have a mixture of InnoDB and MyISAM tables, which is what I was trying to ask you in my previous message. In this case you have to do some dirty tricks. It depends on your situation. For example, you can get the InnoDB data out with --single-transaction; you can get the MyISAM data with flush-and-rsync, then repair and replace missing rows, etc. There is no "good" solution. But with a little work, and some knowledge of your workload, you can get most of the data out without too much trouble, leave the troublesome ones for last, roll up your sleeves for those, and then fix the differences with mk-table-checksum and/or other approaches. Have fun. -- Baron Schwartz, Director of Consulting, Percona Inc. Our Blog: http://www.mysqlperformanceblog.com/ Our Services: http://www.percona.com/services.html -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/mysql?unsub=arch...@jab.org
