Announcement

Announcement Module
Collapse
No announcement yet.

Full backup instead of partial

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

  • Full backup instead of partial

    Hi,

    We are trying to make partial backups that allows more control in case of restore.
    I'm using partial backup option and it seems like the option is ignored.

    See the command:

    innobackupex --databases="mail" --no-timestamp /backup_dir/2012-09-12/

    MySQL server configuration including the option innodb_file_per_table and the server is running with this option from the beginning.

    The output of innobackupex indicates that all the other db's are copied too.
    Finally we get the backup directory full of other db's backups.

    Some server info:

    Debian 6.0.5
    2.6.32-5-amd64
    mysqld Ver 5.1.63-0+squeeze1-log for debian-linux-gnu on x86_64 ((Debian))
    v1.5.1-xtrabackup

    Maybe we are missing something here.
    Please advise.

    Best Regards,
    Ilya Bar-Haim

  • #2
    Hi,

    Can you please try with below command and let me know it works or not?
    innobackupex --include="mail\." --no-timestamp /backup_dir/2012-09-12/

    You can get more information here for partial backup.

    http://www.percona.com/doc/percona-xtrabackup/innobackupex/p artial_backups_innobackupex.html

    Regards,
    Nil

    Comment


    • #3
      Hi Nil,

      Thanks for reply.
      It actually worked but it I've noticed that other DB's folders were created in backup directory without tables files in them. I'm curios why the option "--databases" doesn't work as expected.

      Another issue during preparation for restore - then I'm trying to perform the command:
      "innobackupex --apply-log --export /backup/db_backup/full_backup/2012-09-19/"

      it fails with the following error:

      120919 09:59:31 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/backup/db_backup/full_backup/2012-09-19/backup-my.cnf " --defaults-group="mysqld" --prepare --target-dir=/backup/db_backup/full_backup/2012-09-19 --export

      xtrabackup version 2.0.2 for Percona Server 5.1.59 unknown-linux-gnu (x86_64) (revision id: undefined)
      xtrabackup: error: --export option can only be used with --innodb-file-per-table=ON.
      innobackupex: Error:
      innobackupex: ibbackup failed at /usr/bin/innobackupex line 374

      I'm sure that the server is running with "innodb-file-per-table" option.
      Any ideas? Have you seen this behavior before?

      Best,
      Ilya

      Comment


      • #4
        Hi,

        I've noticed that backup-my.cnf file created during the backup doesn't include the option "innodb-file-per-table".
        After adding the option manually command ran successfully.
        I'd like to avoid editing this file for every backup.

        Best,
        Ilya

        Comment

        Working...
        X