Announcement

Announcement Module
Collapse
No announcement yet.

innobackupex failing

Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • innobackupex failing

    Hi all,
    I'm hoping someone can help me out, I'm trying to evaluate xtrabackup on a test host of mine, where I've installed :
    percona-xtrabackup-2.0.6-521.rhel5.i386.rpm on a Red Hat Enterprise Linux Server release 5.3 (Tikanga)
    The version of the test DB I'm trying this on is: 5.0.87sp1-enterprise-gpl-log and my Innodb files are per table.

    After installing xtrabackup without error, I try:

    innobackupex --user=### --password=### --defaults-file=/etc/my.cnf /tmp/




    InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy


    and Percona Ireland Ltd 2009-2012. All Rights Reserved.





    This software is published under


    the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.





    130501 17:44:37 innobackupex: Starting mysql with options: --defaults-file='/etc/my.cnf' --password=xxxxxxxx --user='xxxx' --unbuffered --


    130501 17:44:37 innobackupex: Connected to database with mysql child process (pid=19998)


    130501 17:44:43 innobackupex: Connection to database server closed


    IMPORTANT: Please check that the backup run completes successfully.


    At the end of a successful backup run innobackupex


    prints "completed OK!".





    innobackupex: Using mysql Ver 14.12 Distrib 5.0.87sp1, for pc-linux-gnu (i686) using readline 5.1


    innobackupex: Using mysql server version Copyright (C) 2000-2008 MySQL AB





    Warning: xtrabackup_51: ignoring option '--log-stream' due to invalid value '/var/log/mysql/query.log'


    innobackupex: Created backup directory /tmp/2013-05-01_17-44-43


    130501 17:44:43 innobackupex: Starting mysql with options: --defaults-file='/etc/my.cnf' --password=xxxxxxxx --user='xxx' --unbuffered --


    130501 17:44:44 innobackupex: Connected to database with mysql child process (pid=20021)


    130501 17:44:46 innobackupex: Connection to database server closed





    130501 17:44:46 innobackupex: Starting ibbackup with command: xtrabackup_51 --defaults-file="/etc/my.cnf" --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/tmp/2013-05-01_17-44-43 --tmpdir=/tmp


    innobackupex: Waiting for ibbackup (pid=20027) to suspend


    innobackupex: Suspend file '/tmp/2013-05-01_17-44-43/xtrabackup_suspended'





    Warning: xtrabackup_51: ignoring option '--log-stream' due to invalid value '/var/log/mysql/query.log'


    xtrabackup_51 version 2.0.6 for MySQL server 5.1.59 pc-linux-gnu (i686) (revision id: 521)


    xtrabackup: uses posix_fadvise().


    xtrabackup: cd to /var/lib/mysql


    xtrabackup: Target instance is assumed as followings.


    xtrabackup: innodb_data_home_dir = /var/lib/innodb-tables


    xtrabackup: innodb_data_file_path = phoenixdb:500M:autoextend


    xtrabackup: innodb_log_group_home_dir = /var/lib/mysql/


    xtrabackup: innodb_log_files_in_group = 3


    xtrabackup: innodb_log_file_size = 15728640


    >> log scanned up to (96 3701437428)


    [01] Copying /var/lib/innodb-tables/phoenixdb to /tmp/2013-05-01_17-44-43/phoenixdb


    >> log scanned up to (96 3701437428)


    >> log scanned up to (96 3701437428)


    >> log scanned up to (96 3701437428)


    >> log scanned up to (96 3701437428)


    >> log scanned up to (96 3701437428)


    >> log scanned up to (96 3701437428)


    [01] ...done


    xtrabackup_51: Can't create/write to file '/tmp/2013-05-01_17-44-43/./phoenixdb/Report.ibd' (Errcode: 20)


    [01] xtrabackup: error: cannot open the destination stream for ./phoenixdb/Report.ibd


    [01] xtrabackup: Error: xtrabackup_copy_datafile() failed.


    [01] xtrabackup: Error: failed to copy datafile.


    innobackupex: Error: ibbackup child process has died at /usr/bin/innobackupex line 381.

    Any advice? Is there a set of reserved labels for table names that might cause the backup to fail (in that the table it's failing on looks to be called Report)? I'm also curious about the Warning mentioned about the query.log file and if there's a complete set of Errcodes around.

    I'd very much appreciate anyone taking a look, and any advice you all may have.
    Rob.

  • #2
    If I run: perror 20
    I get: OS error code 20: Not a directory (if that helps/is related)


    Comment


    • #3
      I'm guessing that what's happening is that since the shared tablespace file (normally ibdata1?) file has the same name as a folder the script tries to copy from in the mysql data directory that the process is failing:

      For example, in my test /etc/my.cnf I have :
      innodb_data_file_path = phoenixdb:500M:autoextend
      but my data directory path contains: /var/lib/mysql/phoenixdb - (where Report.ibd exists)

      Does anyone here have any help/advice? If I'm correct, innobackupex is unusable for me, as I can't change db my.cnf - am I totally wrong?
      Last edited by robulus; 05-02-2013, 09:56 AM.

      Comment


      • #4
        Is there a way to specify via the innobackupex command parameters an alternative backup path for the tablespace file that would have been the ibdata1 file? (which I *think* is causing the problem in my case)

        Comment

        Working...
        X