innobackup.pl - bug report
"Maciej Dobrzanski" <[email protected]>
| Newsgroups | gmane.comp.db.mysql.bugs |
|---|---|
| Message-ID | <009f01c3a387$cc0f40d0$0c0a010a@pikachu> |
Hi, This is how I have my InnoDB data files configured: innodb_data_home_dir=/var/lib/mysql/innodb/ innodb_data_file_path=ibdata/ibdata_base:12G When innobackup.pl creates backup-my.cnf file, it sets the value of `innodb_data_home_dir' to a new location, `innodb_data_file_path' remains untouched, but `ibdata' directory is never created in the backup directory. This causes an error in ibbackup: 031105 10:51:58 ibbackup: Copying /var/lib/mysql/innodb/ibdata/ibdata_base to /mnt/backup/2003-11-05_10-49-44/ibdata/ibdata_base ... 031105 10:51:58 InnoDB: Operating system error number 2 in a file operation. InnoDB: See http://www.innodb.com/ibman.html for installation help. InnoDB: The error means the system cannot find the path specified. InnoDB: In installation you must create directories yourself, InnoDB InnoDB: does not create them. InnoDB: File name /mnt/backup/2003-11-05_10-49-44/ibdata/ibdata_base InnoDB: System call create. InnoDB: Cannot continue operation. The solution is to manually create `ibdata' directory inside the new `innodb_data_home_dir' while ibbackup copies logfiles, but this is something innobackup.pl should do before running ibbackup. Regards, Maciek -- mysql, database, sql, query -- MySQL Bugs Mailing List For list archives: http://lists.mysql.com/bugs To unsubscribe: http://lists.mysql.com/[email protected]