GET 24/7 LIVE HELP NOW

Announcement

Announcement Module
Collapse
No announcement yet.

Problem backing up from Percona Server 5.5.8-beta20.0-46

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

  • Problem backing up from Percona Server 5.5.8-beta20.0-46

    I'm unable to backup my database with XtraBackup 1.5. The previous versions of XtraBackup complain about the Server version, so I've gone to 1.5. The invocation is this:

    root@rs02:/logs/backup# innobackupex-1.5.1 --user=root --password=xxxxxxxxx /logs/backup


    which returns this:

    Version string '' contains invalid data; ignoring: '' at /usr/bin/innobackupex-1.5.1 line 1719.

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

    This software is published under
    the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

    110224 16:46:34 innobackupex-1.5.1: Starting mysql with options: --password=xxxxxxxxx --user=root --unbuffered --
    110224 16:46:34 innobackupex-1.5.1: Connected to database with mysql child process (pid=48795)
    110224 16:46:41 innobackupex-1.5.1: Connection to database server closed
    IMPORTANT: Please check that the backup run completes successfully.
    At the end of a successful backup run innobackupex-1.5.1
    prints "completed OK!".

    innobackupex-1.5.1: Using mysql Ver 14.14 Distrib 5.5.8, for Linux (x86_64) using readline 5.1
    innobackupex-1.5.1: Using mysql server version Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.

    innobackupex-1.5.1: Created backup directory /logs/backup/2011-02-24_16-46-41
    110224 16:46:41 innobackupex-1.5.1: Starting mysql with options: --password=xxxxxxxx --user=root --unbuffered --
    110224 16:46:41 innobackupex-1.5.1: Connected to database with mysql child process (pid=48825)
    110224 16:46:45 innobackupex-1.5.1: Connection to database server closed

    110224 16:46:45 innobackupex-1.5.1: Starting ibbackup with command: xtrabackup_55 --backup --suspend-at-end --target-dir=/logs/backup/2011-02-24_16-46-41
    innobackupex-1.5.1: Waiting for ibbackup (pid=48837) to suspend
    innobackupex-1.5.1: Suspend file '/logs/backup/2011-02-24_16-46-41/xtrabackup_suspended'

    xtrabackup_55 Ver 1.5 Rev 203 for 5.5.7-rc unknown-linux-gnu (x86_64)
    xtrabackup: uses posix_fadvise().
    xtrabackup: cd to /data
    xtrabackup: Target instance is assumed as followings.
    xtrabackup: innodb_data_home_dir = /data
    xtrabackup: innodb_data_file_path = data01.ibd:16M:autoextend
    xtrabackup: innodb_log_group_home_dir = /data
    xtrabackup: innodb_log_files_in_group = 3
    xtrabackup: innodb_log_file_size = 4294967296
    xtrabackup: use O_DIRECT
    110224 16:46:45 InnoDB: Warning: allocated tablespace 191, old maximum was 0
    InnoDB: No valid checkpoint found.
    InnoDB: If this error appears when you are creating an InnoDB database,
    InnoDB: the problem may be that during an earlier attempt you managed
    InnoDB: to create the InnoDB data files, but log file creation failed.
    InnoDB: If that is the case, please refer to
    InnoDB: http://dev.mysql.com/doc/refman/5.1/en/error-creating-innodb .html
    innobackupex-1.5.1: Error: ibbackup child process has died at /usr/bin/innobackupex-1.5.1 line 542.


    I've searched for any bad files as per the above recommended doc page, and looked for errors of numerous sorts. The backup directory is chmod 777. Any help would be much appreciated.

  • #2
    Can you verify that the InnoDB log files are where xtrabackup is trying to find them? You might edit innobackupex and add a 'strace' to the beginning of the xtrabackup command so you can see what file it's trying to open.

    Comment

    Working...
    X