# ibdata\* files in wrong location for recovery?

**URL:** <https://forums.percona.com/t/ibdata-files-in-wrong-location-for-recovery/2199>\
**Category:** Percona XtraBackup\
**Created:** [January 23, 2012, 4:35pm UTC](https://forums.percona.com/t/ibdata-files-in-wrong-location-for-recovery/2199 "2012-01-23T16:35:33Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dchicks](https://avatars.discourse-cdn.com/v4/letter/d/ed8c4c/32.png) [@dchicks](https://forums.percona.com/u/dchicks)\
**Post date:** [January 23, 2012, 4:35pm UTC](https://forums.percona.com/t/ibdata-files-in-wrong-location-for-recovery/2199/1 "2012-01-23T16:35:33Z")

</div>

I’m using XtraBackup 1.6.3. (I do realize there is a new version just out.) I’m also using the streaming option to create a gzipped archive of my backup via InnoBackupEx. When I recover the archive, I have an interesting issue. The ibdata\* files get extracted directly into my /var/lib/mysql directory. However, on my server, they are located in /var/lib/mysql/innodb. Interestingly, to run the --apply-log step, I have to leave the files in /var/lib/mysql, then move them to /var/lib/mysql/innodb prior to starting my MySQL instance.

Would this be considered a bug of some sort? It certainly makes recovering from a backup less than straightforward. It took me a while to figure it out. Before that, I would recover and find that my database was unreadable.

Thoughts?

Thanks,  
Dave

---

<div class="post-metadata">

**Author:** ![xaprb](https://avatars.discourse-cdn.com/v4/letter/x/49beb7/32.png) [@xaprb](https://forums.percona.com/u/xaprb)\
**Post date:** [January 25, 2012, 8:01am UTC](https://forums.percona.com/t/ibdata-files-in-wrong-location-for-recovery/2199/2 "2012-01-25T08:01:16Z")

</div>

I would think this is worth reporting as a bug.