innobackup.pl - bug report

innobackup.pl - bug report

am 05.11.2003 11:30:12 von Maciej Dobrzanski

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/bugs?unsub=gcdmb-bugs@m.gmane.org

Re: innobackup.pl - bug report

am 05.11.2003 16:26:51 von Heikki Tuuri

Maciej,

thank you for the bug report. I have forwarded it to the maintainer of the
innobackup code. It already creates automatically the database directories,
but creating the ibdata directory has been forgotten.

Hmm... or even better is to change ibbackup itself so that it creates the
directory.

Best regards,

Heikki
Innobase Oy
http://www.innodb.com
InnoDB - transactions, row level locking, and foreign keys for MySQL
InnoDB Hot Backup - hot backup tool for InnoDB which also backs up MyISAM
tables


..........................
List: MySQL BugsĀ« Previous Message
From: Maciej Dobrzanski Date:November 5 2003 11:30am
Subject: innobackup.pl - bug report



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 Bugs Mailing List
For list archives: http://lists.mysql.com/bugs
To unsubscribe: http://lists.mysql.com/bugs?unsub=gcdmb-bugs@m.gmane.org