# Innobackupex from 5.5 to 5.6

**URL:** <https://forums.percona.com/t/innobackupex-from-5-5-to-5-6/4483>\
**Category:** Percona XtraBackup\
**Created:** [October 28, 2015, 6:48pm UTC](https://forums.percona.com/t/innobackupex-from-5-5-to-5-6/4483 "2015-10-28T18:48:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![amit](https://avatars.discourse-cdn.com/v4/letter/a/ee7513/32.png) [@amit](https://forums.percona.com/u/amit)\
**Post date:** [October 28, 2015, 6:48pm UTC](https://forums.percona.com/t/innobackupex-from-5-5-to-5-6/4483/1 "2015-10-28T18:48:04Z")

</div>

Hi

Are there known issues when using Innobackupex on Percona MySQL 5.5 and restore it in Percona MySQL 5.6. We are seeing date change when data was moved using Innobackupex. Not sure if it is safe to use innobackupex with version change

Percona MySQL 5.5 | 84 | Medical | NULL | NULL | 0000-00-09 04:59:40 | 9902-04-16 24:00:00 | | 85 | Supplies | NULL | NULL | 0000-00-09 04:59:40 | 9902-04-16 24:00:00 | ±—±-------------------±-----------±-----------±--------------------±--------------------+ Percona MySQL 5.6 | 84 | Medical | NULL | NULL | 2013-01-09 21:30:22 | 2013-01-09 21:30:22 | | 85 | Supplies | NULL | NULL | 2013-01-09 21:30:22 | 2013-01-09 21:30:22 | ±—±-------------------±-----------±-----------±--------------------±--------------------+

---

<div class="post-metadata">

**Author:** ![SQLGuy](https://avatars.discourse-cdn.com/v4/letter/s/dbc845/32.png) [@SQLGuy](https://forums.percona.com/u/SQLGuy)\
**Post date:** [November 4, 2015, 3:17pm UTC](https://forums.percona.com/t/innobackupex-from-5-5-to-5-6/4483/2 "2015-11-04T15:17:41Z")

</div>

I would think that would be very risky, if it would work at all. Remember that the databases would be at an old version, and the data dictionary and system tables would be at another. The best and safest way to do that kind of upgrade is to use mysqldump.