The reason is an unintentional change in the innodb_version format in 5.1.60, see the server bug #917246.
We have to implement a workaround in XtraBackup though, by updating the regexps used to detect XtraDB 5.1.
The reason is an unintentional change in the innodb_version format in 5.1.60, see the server bug #917246.
We have to implement a workaround in XtraBackup though, by updating the regexps used to detect XtraDB 5.1.