# Continuing support for innobackupex

**URL:** <https://forums.percona.com/t/continuing-support-for-innobackupex/2899>\
**Category:** Percona XtraBackup\
**Created:** [August 22, 2013, 6:40pm UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899 "2013-08-22T18:40:45Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![systems8900](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@systems8900](https://forums.percona.com/u/systems8900)\
**Post date:** [August 22, 2013, 6:40pm UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899/1 "2013-08-22T18:40:45Z")

</div>

I read the following on the main documentation site for innobackupex:

"

Does this mean support is planning on being dropped for this script? Is there a timeline for deprecation?

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [August 23, 2013, 2:13am UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899/2 "2013-08-23T02:13:25Z")

</div>

There are no plans on dropping support for the innobackupex wrapper script. I expect it will be just deprecated once something better will be introduced and simply there will be no need for using it.

---

<div class="post-metadata">

**Author:** ![systems8900](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@systems8900](https://forums.percona.com/u/systems8900)\
**Post date:** [August 23, 2013, 5:18pm UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899/3 "2013-08-23T17:18:24Z")

</div>

thank you so much for your response!

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [August 24, 2013, 3:20am UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899/4 "2013-08-24T03:20:42Z")

</div>

Actually, there is a plan to merge all functionality into XtraBackup binary itself, see this blueprint: [URL][https://blueprints.launchpad.net/percona-xtrabackup/+spec/rewrite-innobackupex-in-c[/URL]](https://blueprints.launchpad.net/percona-xtrabackup/+spec/rewrite-innobackupex-in-c%5B/URL%5D)

---

<div class="post-metadata">

**Author:** ![systems8900](https://avatars.discourse-cdn.com/v4/letter/s/51bf81/32.png) [@systems8900](https://forums.percona.com/u/systems8900)\
**Post date:** [August 26, 2013, 3:49pm UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899/5 "2013-08-26T15:49:27Z")

</div>

Is there any reason why we should be concerned about relying on this utility? The main comment of concern was that there are “code quality” issues with it. Does that mean it has bugs that could cause it to not function as it’s supposed to or result in anything else of concern such as data not being backed up or something?

Essentially, is there ANY reason I shouldn’t be using innobackupex in a production environment where backups are imperative?

---

<div class="post-metadata">

**Author:** ![przemek](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/przemek/32/3_2.png) [@przemek](https://forums.percona.com/u/przemek)\
**Post date:** [August 29, 2013, 12:23pm UTC](https://forums.percona.com/t/continuing-support-for-innobackupex/2899/6 "2013-08-29T12:23:53Z")

</div>

In the code quality comment it’s more about manageability of the code, so for example implementing changes is hard for developers. Innobackupex is used in many many production environments with great success. Also it’s only wrapper script for XtraBackup binary, which is the one responsible for main InnoDB backup part.  
So I wouldn’t be concerned about that. Of course no software is bug free and always the best practice is to verify your backups regularly.
