innobackupex ignores --databases without --stream
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Fix Released
|
High
|
Sergei Glushchenko | |
| 1.6 |
Won't Fix
|
Undecided
|
Unassigned | |
| 2.0 |
Won't Fix
|
Undecided
|
Unassigned | |
| 2.1 |
Won't Fix
|
Undecided
|
Unassigned | |
| 2.2 |
Fix Released
|
High
|
Sergei Glushchenko |
Bug Description
If --stream is not given, innobackupex-1.5.1 from xtrabackup-
Related branches
- Laurynas Biveinis (community): Needs Fixing on 2013-03-22
-
Diff: 1012 lines (+706/-130)8 files modifieddoc/source/innobackupex/partial_backups_innobackupex.rst (+1/-4)
doc/source/xtrabackup_bin/partial_backups.rst (+6/-1)
doc/source/xtrabackup_bin/xbk_option_reference.rst (+8/-0)
innobackupex (+7/-0)
src/xtrabackup.c (+356/-125)
test/t/ib_databases.sh (+50/-0)
test/t/ib_databases_file.sh (+57/-0)
test/t/xb_databases_options.sh (+221/-0)
- Alexey Kopytov (community): Disapprove on 2014-08-25
-
Diff: 1052 lines (+686/-143)9 files modifieddoc/source/innobackupex/partial_backups_innobackupex.rst (+1/-5)
doc/source/xtrabackup_bin/partial_backups.rst (+6/-1)
doc/source/xtrabackup_bin/xbk_option_reference.rst (+8/-0)
innobackupex.pl (+8/-0)
src/innodb_int.h (+2/-2)
src/xtrabackup.cc (+338/-135)
test/t/ib_databases.sh (+48/-0)
test/t/ib_databases_file.sh (+57/-0)
test/t/xb_databases_options.sh (+218/-0)
- Alexey Kopytov (community): Approve on 2014-08-27
-
Diff: 1051 lines (+674/-143)9 files modifiedstorage/innobase/xtrabackup/doc/source/innobackupex/partial_backups_innobackupex.rst (+1/-5)
storage/innobase/xtrabackup/doc/source/xtrabackup_bin/partial_backups.rst (+6/-1)
storage/innobase/xtrabackup/doc/source/xtrabackup_bin/xbk_option_reference.rst (+8/-0)
storage/innobase/xtrabackup/innobackupex.pl (+8/-0)
storage/innobase/xtrabackup/src/xtrabackup.cc (+329/-135)
storage/innobase/xtrabackup/test/inc/common.sh (+2/-2)
storage/innobase/xtrabackup/test/t/ib_databases.sh (+46/-0)
storage/innobase/xtrabackup/test/t/ib_databases_file.sh (+56/-0)
storage/innobase/xtrabackup/test/t/xb_databases_options.sh (+218/-0)
Changed in percona-xtrabackup: | |
importance: | Undecided → Medium |
assignee: | nobody → Aleksandr Kuzminsky (akuzminsky) |
Changed in percona-xtrabackup: | |
milestone: | none → 1.3.1 |
Will Bryant (willbryant) wrote : | #1 |
Changed in percona-xtrabackup: | |
milestone: | 1.3.1 → 1.6 |
assignee: | Aleksandr Kuzminsky (akuzminsky) → Valentine Gostev (core-longbow) |
Changed in percona-xtrabackup: | |
milestone: | 1.6 → 1.7 |
Valentine Gostev (longbow) wrote : | #2 |
Linked branch contains test
Changed in percona-xtrabackup: | |
status: | New → Triaged |
status: | Triaged → Confirmed |
assignee: | Valentine Gostev (core-longbow) → Vadim Tkachenko (vadim-tk) |
Changed in percona-xtrabackup: | |
status: | Confirmed → Triaged |
assignee: | Vadim Tkachenko (vadim-tk) → nobody |
Changed in percona-xtrabackup: | |
milestone: | 1.7.0beta1 → 1.7.0 |
tags: | added: doc |
tags: | removed: doc |
tags: | added: innobackupex |
Stewart Smith (stewart) wrote : | #3 |
Marking as Won't fix for the old stable 1.6 release. If you need a fix for this bug in 1.6, please say so here or contact us (Percona) to arrange something.
Using XtraBackup 2.0.0 I encountered the same symptoms with --databases. I worked around this with --include as suggested in comment #1.
summary: |
- innobackupex ignores --databases without --stream + innobackupex ignores --databases |
summary: |
- innobackupex ignores --databases + innobackupex ignores --databases without --stream |
Alexey Kopytov (akopytov) wrote : | #5 |
In fact in XtraBackup 2.0 the --databases option has no effect for InnoDB files for both local and streaming backups, i.e. all InnoDB files are always backed up. Currently, only .frm and non-InnoDB tables are limited by that option.
I suggest to introduce --databases and --databases-file xtrabackup. --databases option of innobackupex would be mapped to one of them.
Alexey Kopytov (akopytov) wrote : | #7 |
Bug #1274766 marked as a duplicate of this one.
Matthew B (utdrmac) wrote : | #8 |
Just wanted to +1 this. I have a client with multiple databases but only wants 1 backed up. If I use --databases=
Additionally, different behavior is experienced during the file phase of backups (during the .frm, MYI, MYD part). If I specify --databases=
140819 02:12:02 innobackupex: Continuing after ibbackup has suspended
140819 02:12:02 innobackupex: Executing FLUSH TABLES WITH READ LOCK...
>> log scanned up to (1286337694402)
140819 02:12:03 innobackupex: All tables locked and flushed to disk
140819 02:12:03 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/mnt/san/
innobackupex: Backing up files '/mnt/san/
>> log scanned up to (1286337694402)
140819 02:12:04 innobackupex: Finished backing up non-InnoDB tables and files
140819 02:12:04 innobackupex: Executing FLUSH ENGINE LOGS...
140819 02:12:04 innobackupex: Waiting for log copying to finish
xtrabackup: The latest check point (for incremental): '1286337692872'
xtrabackup: Stopping log copying thread.
.>> log scanned up to (1286337694402)
xtrabackup: Creating suspend file '/mnt/san/
xtrabackup: Transaction log of lsn (1286331699845) to (1286337694402) was copied.
140819 02:12:05 innobackupex: All tables unlocked
==== But if I do this, --include=
140819 09:29:05 innobackupex: Executing FLUSH TABLES WITH READ LOCK...
>> log scanned up to (1286949139524)
140819 09:29:05 innobackupex: All tables locked and flushed to disk
140819 09:29:05 innobackupex: Starting to backup non-InnoDB tables and files
innobackupex: in subdirectories of '/mnt/san/
innobackupex: Backing up files '/mnt/san/
innobackupex: Backing up files '/mnt/san/
innobackupex: Backing up files '/mnt/san/
innobackupex: Backing up files '/mnt/san/
percona.
percona.db.opt is skipped because it does not match '^alex_
innobackupex: Backing up files '/mnt/san/
innobackupex: Backing up files '/mnt/san/
innobackupex: Backing up files '/mnt/san/
Shahriyar Rzayev (rzayev-sehriyar) wrote : | #9 |
Percona now uses JIRA for bug reports so this bug report is migrated to: https:/
Try using the --include option. --databases seems to affect for which databases the files other than .ibd are backed up, so I am using:
--databases="mysql myapp_production" --include= "myapp_ production\ ..*"
I'm not sure if this is the intended behavior.