innobackupex treats files as folders during incremental
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Triaged
|
Low
|
Unassigned | ||
2.0 |
Won't Fix
|
Low
|
Unassigned | ||
2.1 |
Triaged
|
Low
|
Unassigned | ||
2.2 |
Triaged
|
Low
|
Unassigned | ||
2.3 |
Triaged
|
Low
|
Unassigned |
Bug Description
innobackupex treats regular files located in backup root directory as folders and tries to look up full backup's metadata there:
[root@dev10 ~]# ls -lah /root/backup/
total 1.5M
drwxr-xr-x 4 root root 4.0K Feb 13 14:56 .
drwxr-x--- 10 root root 4.0K Feb 13 14:38 ..
drwxr-xr-x 4 root root 4.0K Feb 13 14:50 2011-02-13_14-49-57
-rw-r--r-- 1 root root 1.5M Feb 13 14:52 full.tar.gz
[root@dev10 ~]#
[root@dev10 ~]# innobackupex --incremental /root/backup
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.
110213 14:56:42 innobackupex: Starting mysql with options: --unbuffered --
110213 14:56:42 innobackupex: Connected to database with mysql child process (pid=11600)
110213 14:56:49 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.14 Distrib 5.1.54, for unknown-linux-gnu (x86_64) using readline 5.1
innobackupex: Using mysql server version Copyright (c) 2000, 2010, Oracle and/or its affiliates. All rights reserved.
innobackupex: Created backup directory /root/backup/
110213 14:56:49 innobackupex: Starting mysql with options: --unbuffered --
110213 14:56:49 innobackupex: Connected to database with mysql child process (pid=11624)
110213 14:56:53 innobackupex: Connection to database server closed
110213 14:56:53 innobackupex: Starting ibbackup with command: xtrabackup --backup --suspend-at-end --target-
innobackupex: Waiting for ibbackup (pid=11635) to suspend
innobackupex: Suspend file '/root/
xtrabackup: Error: cannot open /root/backup/
xtrabackup: error: failed to read metadata from /root/backup/
innobackupex: Error: ibbackup child process has died at /usr/bin/
[root@dev10 ~]#
So it turns out that when innobackupex just takes the latest object from the backup root directory and does not check either it is a file or folder.
I suggest that innobackupex should pick the folder as a base for incremental backup basing on facts when the object inside backup root is a directory and it is named with a timestamps (like the names of the folders innobackupex creates)
Changed in percona-xtrabackup: | |
status: | New → Confirmed |
importance: | Undecided → Low |
importance: | Low → Medium |
assignee: | nobody → Vadim Tkachenko (vadim-tk) |
Changed in percona-xtrabackup: | |
status: | Confirmed → Triaged |
assignee: | Vadim Tkachenko (vadim-tk) → nobody |
You should explicitly specify --incremental- basedir= along with --incremental option.