2006/4/13, Duzenbury, Rich <[EMAIL PROTECTED]>: > Hi all, > > I have two servers that have production data on them, and then one > server where I would like to keep an active copy of the data. > > Currently, there is a job that runs in the middle of the night that > basically does a > mysqldump --host=production_server --all-databases | mysql > --host=backup_server > > It takes a long time to copy over all the data, when in reality, it's > not changing that much. The great thing about this approach is that > yesterdays tables are very nearby and easily accessible in the case > where someone fat-fingers some data. > > The trick to this is that I want the backup server to be one day behind > the production server, not real time mirrored, so maybe replication > isn't the right thing, I am not sure. I am using the innodb storage > engine for most things, though there are a few myIsam tables. >
Setup the replication, then do a cron job with a start/stop slave ? http://dev.mysql.com/doc/refman/4.1/en/stop-slave.html The things is that if you modify data on the slave, they won't go back to the original state... the backup assure you a clean copy. -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
