No. Although innobackupex is derived from the same GPL and open-source wrapper script that InnoDB Hot Backup uses, it does not execute ibbackup, and the xtrabackup binary does not execute or link to ibbackup. You can use Percona XtraBackup without any license; it is completely separate from InnoDB Hot Backup.
That’s the way the source for the tool was distributed from Oracle. Nowadays, it is a symbolic link to innobackupex for backward compatibility with Percona XtraBackup.
Because innobackupex is a patched version of Oracle ’s innobackup script (now renamed to mysqlbackup), it is quite similar in some ways, and familiarity with innobackup might be helpful.
Aside from the options for specific features of innobackupex, the main differences are:
See The innobackupex Option Reference for more details.
xtrabackup is a C program written to take advantage of the InnoDB or XtraDB features in order to make it as fast, less resource-consuming and unobtrusive (locking the database server) as possible. That is only possible with those engines. In the case of MyISAM a “read lock” is needed.
innobackupex is a script written in Perl which wraps xtrabackup and other backup tools (such as tar4ibd) and provides you with the functionality of each tool taking care of the details.
However, for some specific tasks, you must use xtrabackup directly. See the Percona XtraBackup User Manual for details on each one.
Zmanda Recovery Manager is a commercial tool that uses Percona XtraBackup for Non-Blocking Backups:
“ZRM provides support for non-blocking backups of MySQL using |Percona XtraBackup|. ZRM with |Percona XtraBackup| provides resource utilization management by providing throttling based on the number of IO operations per second. |Percona XtraBackup| based backups also allow for table level recovery even though the backup was done at the database level (needs the recovery database server to be |Percona Server| with XtraDB).”
In most of the cases this is due to not having install the required libraries (and version) by xtrabackup. Installing the GCC suite with the supporting libraries and recompiling xtrabackup will solve the issue. See Compiling and Installing from Source Code for instructions on the procedure.
In case the ibdata and ib_log files are located in different directories outside of the datadir, you will have to put them in their proper place after the logs have been applied.
This usually happens when database being backed up contains large amount of files and Percona XtraBackup can’t open all of them to create a successful backup. In order to avoid this error the operating system should be configured appropriately so that Percona XtraBackup can open all its files. On Linux, this can be done with the ulimit command for specific backup session or by editing the /etc/security/limits.conf to change it globally (NOTE: the maximum possible value that can be set up is 1048576 which is a hard-coded constant in the Linux kernel).
For general inquiries, please send us your question and someone will contact you.