Manual for xtrabackup 2.4 still suggests to use innobackupex, while xtrabackup now has the same functionality

[Valerii Kravchuk]

Manual (https://www.percona.com/doc/percona-xtrabackup/2.4/xtrabackup_bin/incremental_backups.html) says:

"If you want a usable full backup, use innobackupex since xtrabackup itself won’t copy table definitions, triggers, or anything else that’s not .ibd."

That's not true in 2.4 (and 2.3 as far as I remember), as innobackupex is just a symlink to xtrabackup for backward compatibility now:

[openxs@centos percona-xtrabackup]$ ls -l `which xtrabackup`
-rwxr-xr-x. 1 root root 21771208 Feb 12 09:38 /usr/bin/xtrabackup
[openxs@centos percona-xtrabackup]$ ls -l `which innobackupex`
lrwxrwxrwx. 1 root root 10 Feb 24 21:35 /usr/bin/innobackupex -> xtrabackup
[openxs@centos percona-xtrabackup]$ xtrabackup --version
xtrabackup version 2.4.1 based on MySQL server 5.7.10 Linux (x86_64) (revision id: a2dc9d4)

[Hrvoje Matijakovic (hrvojem)]

https://github.com/percona/percona-xtrabackup/pull/253

[Shahriyar Rzayev (rzayev-sehriyar)]

Percona now uses JIRA for bug reports so this bug report is migrated to: https://jira.percona.com/browse/PXB-469