Comment 3 for bug 1551272
Revision history for this message
| Sergei Glushchenko (sergei.glushchenko) wrote | #3 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
Well, the problem actually is that MySQL is seeing t1.ibd in two locations. The original one, which is /tmp/foo/t1.ibd and the one in the backup directory, which you are using as new datadir. I think you are using MySQL 5.7 and old path is stored not only in .isl file, bit in the data dictionary as well.
To resolve this conflict I beleive you will need to remove .ibd from one of the locations. Again, I don't think it will be correct if xtrabackup on prepare would "fix" the path in the data dictionary because there are cases when one need to place t1.ibd to the same path either on old server or the new one. This could probably be added as optional step.