PDA

View Full Version : cannot open index file



mavis.chu
January 12th, 2011, 08:03 PM
Hi All,
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, "BackupSet1:parse-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?
Thanks

Mavis

paddy
January 13th, 2011, 01: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

Paddy

jz20k
January 30th, 2012, 10:47 AM
Hi paddy,

It's interesting that you say that because according to 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 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?

paddy
January 30th, 2012, 02: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.

tony-caffe
April 11th, 2013, 10:04 AM
source-directory value should be a directory where incremental backups are stored.

It has the format <destination-directory>/<backup set name>/<date stamp>

Paddy

That is exactly correct. I changed to backup directory and boom it worked! Thanks.

greitas
June 11th, 2013, 12:00 PM
Same problem, but this method not worked for me...

bluffy
July 17th, 2013, 11:06 PM
its not working friend..