Re: use xtrabackup restore mysql5.5 fail

[Chicken Urine]

The file exist? Do you have read access to the backup directory?

El lunes, 13 de agosto de 2012 19:21:26 UTC-3, 郑森林 escribió:

xtrabackup: Error: cannot open ./xtrabackup_checkpoints
xtrabackup: error: xtrabackup_read_metadata()
xtrabackup: This target seems not to have correct metadata...
 InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Warning: cannot open ./xtrabackup_logfile. will try to find.
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
xtrabackup: Fatal error: cannot find ./xtrabackup_logfile.

....

....

120814  4:30:20  InnoDB: Initializing buffer pool, size = 100.0M

120814  4:30:20  InnoDB: Completed initialization of buffer pool

120814  4:30:21  InnoDB: highest supported file format is Barracuda.

InnoDB: The log sequence number in ibdata files does not match

InnoDB: the log sequence number in the ib_logfiles!

120814  4:30:21  InnoDB: Database was not shut down normally!

InnoDB: Starting crash recovery.

InnoDB: Reading tablespace information from the .ibd files...

120814  4:31:52  InnoDB: ERROR: We were only able to scan the log up to

InnoDB: 16072742871552, but a checkpoint was at 16072742871894.

InnoDB: It is possible that the database is now corrupt!

InnoDB: Last MySQL binlog file position 0 1045380241, file name ./mysql-bin.008046

120814  4:31:53 Percona XtraDB (http://www.percona.com) 1.0.17-12.5 started; log sequence number 16072742871894

120814  4:31:54  InnoDB: Assertion failure in thread 140474221307648 in file xtrabackup.c line 1371

InnoDB: Failing assertion: cset == 0

InnoDB: We intentionally generate a memory trap.

InnoDB: Submit a detailed bug report to http://bugs.mysql.com.

InnoDB: If you get repeated assertion failures or crashes, even

InnoDB: immediately after the mysqld startup, there may be

InnoDB: corruption in the InnoDB tablespace. Please refer to

InnoDB: http://dev.mysql.com/doc/refman/5.1/en/forcing-innodb-recovery.html

InnoDB: about forcing recovery.

xtrabackup version 1.6.6 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: undefined)

xtrabackup: xtrabackup_logfile detected: size=97712783360, start_lsn=(16072742871894)

[郑森林]

xtrabackup_logfile this file will delete after run this commnd
"xtrabackup --prepare --target-dir=/usr/local/mysql/data/"
have read access to the backup directory.

> > InnoDB: Submit a detailed bug report tohttp://bugs.mysql.com.

[Chicken Urine]

Can you please add some more information about the process you're following?

[Justin Swanhart]

Hi,

You must have write access to prepare a database backup.  When you prepare the backup, the xtrabackup_logfile and xtrabackup_checkpoints files are used to roll the database forward and make it consistent for restoration.  This requires writing the changes from those files into the InnoDB tablespaces, which requires write access.

--Justin

--
You received this message because you are subscribed to the Google Groups "Percona Discussion" group.

To post to this group, send email to percona-d...@googlegroups.com.
To unsubscribe from this group, send email to percona-discuss...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/percona-discussion?hl=en.