January 12th, 2011, 07:03 PM
cannot open index file
when I run following command
mysql-zrm --action parse-binlogs --source-directory=/usr/local/mysql/data, it is expected to obtain bin-log messages, however, "BackupSet1arse-binlogs:ERROR: cannot open index file /usr/local/mysql/data/index No such file or directory" is show out.
Is there any one can help me?
January 13th, 2011, 12:55 PM
source-directory value should be a directory where incremental backups are stored.
It has the format <destination-directory>/<backup set name>/<date stamp>
/usr/local/mysql/data appears to be incorrect
January 30th, 2012, 09:47 AM
It's interesting that you say that because according to [url]http://wiki.zmanda.com/index.php/How_do_I_recover_data_when_there_is_a_failure_or_d ata_loss%3F#Restoration_based_on_timestamp_-_Point_in_time_recovery[/url] that is exactly what you are supposed to do to parse the current bin logs in /var/lib/mysql
Is there no current way to parse bin logs not part of a backup set? If not, what is the current solution to replay bin logs with mysql-zrm that are not part of a backup directory?
January 30th, 2012, 01:14 PM
mysql-zrm-parse-binlogs can only work on incremental backups. If you want to parse binary logs that are not part of backup directory, use mysql command - mysqlbinlog.
April 11th, 2013, 09:04 AM
That is exactly correct. I changed to backup directory and boom it worked! Thanks.
Originally Posted by paddy
June 11th, 2013, 11:00 AM
Same problem, but this method not worked for me...
July 17th, 2013, 10:06 PM