Emergency

Proper way to backup and restore?

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Proper way to backup and restore?

    Hi,

    I'm struggling with xtrabackup for a while. There are some Innodb corrupt warnings while or after restore on different server. It's going pretty unstable. There is no corruption on production database of course. Example after-restore error:

    140721 10:29:39 InnoDB: Error: page 2504 log sequence number 97651749064
    InnoDB: is in the future! Current system log sequence number 54429130252.
    InnoDB: Your database may be corrupt or you may have copied the InnoDB
    InnoDB: tablespace but not the InnoDB log files. See
    InnoDB: http://dev.mysql.com/doc/refman/5.5/...-recovery.html
    InnoDB: for more information.
    Here are the versions and options I use to backup and restore, I'd be grateful if someone check and recommend something:

    Prod server (backup via):
    percona-xtradb-cluster-server-5.5 version 5.5.34-25.9-607.precise
    percona-xtrabackup
    version 2.1.6-702-1.precise

    Restored on:
    percona-server-server-5.5 version 5.5.37-rel35.0-657.wheezy
    percona-xtrabackup-21
    version 2.1.9-746-1.wheezy

    Backup command (innobackupex):
    --galera-info --rsync
    --galera-info --rsync --incremental


    Restore command (innobackupex):
    --apply-log --use-memory=2G --ibbackup=xtrabackup_51

    Thanks.

  • #2
    I have had this before with very busy servers using mysqlhotcopy. Never had it with inno/xtra backup.
    Is your server under heavy load when backing up?
    Also - what is the size of the log file?

    Comment


    • #3
      We are following the most basic configuration from howtos -- http://www.percona.com/doc/percona-x...bkx_local.html

      We are also having the same issue using the following:

      Backup: percona-xtrabackup-2.2.6-5042.el6.x86_64

      innobackupex --user=$MYSQL_USER --password=$MYSQL_PASS backupdir

      Restore: percona-xtrabackup-2.2.6-5042.el5

      step 1: completely clearing our my mysql data dir
      step 2: innobackupex --copy-back backupdir
      step 3: restore mysql data dir permissions

      Errors:
      2014-11-07 18:34:10 2ad2ffacd940 InnoDB: Error: page 15560 log sequence number 2659725285
      InnoDB: is in the future! Current system log sequence number 1758689814.
      InnoDB: Your database may be corrupt or you may have copied the InnoDB
      InnoDB: tablespace but not the InnoDB log files. See
      InnoDB: http://dev.mysql.com/doc/refman/5.6/...-recovery.html
      InnoDB: for more information.

      Comment


      • #4
        Same issue.. anyone get this sorted?

        Comment


        • #5
          Can you please share full error log along with my.cnf configuration file to check further. From quick look, It seems those LSN errors will eventually fix once current log sequence number catches up with future log sequence number High amount of fake DML queries can speed up this operation to fix. On safe side, you can check database consistency via mysqlcheck --all-databases or mysqldump to verify that all database tables are in good shape.

          Comment

          Working...
          X