# [EMAIL PROTECTED] / 2003-06-27 14:44:55 +0200:
> I have a question regarding mysqlhotcopy's use.
> I'd like to use the --flushlog option in order to have a nice backup &
> synchronized log for my replication slave in case of recover need
> (without stopping the master).
> But the lock used by mysqlhotcopy made me split the backups into
> something like:
>
> mysqlhotcopy db_name_1 db_name_2
> mysqlhotcopy db_name_3 db_name_4 db_name 5
> mysqlhotcopy db_name_6
>
> (that way because the backup of db_name_1 and db_name_2 is fast and I
> don't want these table to be locked a long time (a few sec. max), and
> the backup of db_name_6 is long (~2-3mn) but it supports the lock).
why don't you just cron mysqladmin flush-logs ? the binlog is a
complete backup AFAICT.
> So if I flush the logs each time, not only I'll may have little pieces
> of logs, but I can't see how to use these to recover a slave.
I don't use replication yet, sorry.
> I was thinking to filter these little log files in order to rewrite a
> correct one but is it possible to do the inverse of the mysqlbinlog command?
Why would you want to do anything like that?
--
If you cc me or remove the list(s) completely I'll most likely ignore
your message. see http://www.eyrie.org./~eagle/faqs/questions.html
--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
