Announcement

Announcement Module
Collapse
No announcement yet.

XtraBackup fail to create backup

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

  • XtraBackup fail to create backup

    hi,
    im trying to create backup using Xtrabackup tool but it failed to start the backup.
    my DB size is about 6.5T.

    innobackupex: Using mysql server version 5.5.30-30.2-log

    130930 07:44:00 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/mnt/dwh_mysql/2013-09-30_07-44-00 --tmpdir=/tmp
    innobackupex: Waiting for ibbackup (pid=21137) to suspend
    innobackupex: Suspend file '/mnt/dwh_mysql/2013-09-30_07-44-00/xtrabackup_suspended_2'

    xtrabackup_55 version 2.1.3 for Percona Server 5.5.16 Linux (x86_64) (revision id: 608)
    xtrabackup: uses posix_fadvise().
    xtrabackup: cd to /var/lib/mysql
    xtrabackup: Target instance is assumed as followings.
    xtrabackup: innodb_data_home_dir = /var/lib/mysql
    xtrabackup: innodb_data_file_path = ibdata1:10M:autoextend
    xtrabackup: innodb_log_group_home_dir = /var/lib/mysql
    xtrabackup: innodb_log_files_in_group = 2
    xtrabackup: innodb_log_file_size = 268435456
    xtrabackup: using O_DIRECT
    130930 7:44:01 InnoDB: Warning: allocated tablespace 48650, old maximum was 9
    File size limit exceeded (core dumped)
    innobackupex: Error: ibbackup child process has died at /usr/bin/innobackupex line 389.

    does anyone know how to solve this?

    thanks,

    Ronnysh

  • #2
    Hi Ronnysh,

    As per the error, you are exceeded OS file size limits. Can you check what is currently limit set at OS level with "ulimit -a" ? you can paste output here.
    if it's not enough then you can update it by changing limits in vi /etc/security/limits.conf

    Comment


    • #3
      hi niljoshi,
      it looks like the server has no OS file limits.

      core file size (blocks, -c) 0
      data seg size (kbytes, -d) unlimited
      scheduling priority (-e) 0
      file size (blocks, -f) unlimited
      pending signals (-i) 514945
      max locked memory (kbytes, -l) 64
      max memory size (kbytes, -m) unlimited
      open files (-n) 1024
      pipe size (512 bytes, -p) 8
      POSIX message queues (bytes, -q) 819200
      real-time priority (-r) 0
      stack size (kbytes, -s) 8192
      cpu time (seconds, -t) unlimited
      max user processes (-u) 514945
      virtual memory (kbytes, -v) unlimited
      file locks (-x) unlimited

      Comment


      • #4
        Hi Ronny,

        Looks like you could be hitting individual files size on filesystem/OS level. Can you please provide some more information like what OS and filesystem you are using? Is Innodb_file_per_table is ON? It could be also helpful if you can provide the output of "ls- alh" of your data dir. Thanks.

        Comment

        Working...
        X