innodb_doublewrite not copied back to proper location
Bug #1184888 reported by
Rocco
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Percona XtraBackup moved to https://jira.percona.com/projects/PXB |
Invalid
|
Medium
|
Unassigned | ||
2.0 |
Won't Fix
|
Medium
|
Unassigned | ||
2.1 |
Won't Fix
|
Medium
|
Unassigned | ||
2.2 |
Invalid
|
Medium
|
Unassigned | ||
2.3 |
Invalid
|
Medium
|
Unassigned |
Bug Description
innobackupex: back to original data directory '/data/mysql'
innobackupex: Copying '/backup/
/etc/mysql/my.cnf:
innodb_
Ubuntu deb installed.
ii percona-xtrabackup 2.1.3-608.precise
Not sure if it's a problem or not (That the doublewrite file will be missing). InnoDB log files are copied to correct destination.
innobackupex: back to original InnoDB log directory '/log/mysql-bin'
tags: | added: pxc |
no longer affects: | percona-xtradb-cluster |
tags: | added: i49767 |
To post a comment you must log in.
It copies the files based on backup-my.cnf I believe, what is the path set in that for innodb_ doublewrite_ file?
Probably copy-back/move-back should use my.cnf of system than the
backup-my.cnf.