# xtrabackup is still failing evern after upgrading Percona XtraBackup to 2.1.6 **URL:** \ **Category:** Percona XtraBackup\ **Created:** [December 2, 2013, 12:41pm UTC](https://forums.percona.com/t/xtrabackup-is-still-failing-evern-after-upgrading-percona-xtrabackup-to-2-1-6/3130 "2013-12-02T12:41:34Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![krishna](https://avatars.discourse-cdn.com/v4/letter/k/71c47a/32.png) [@krishna](https://forums.percona.com/u/krishna)\ **Post date:** [December 2, 2013, 12:41pm UTC](https://forums.percona.com/t/xtrabackup-is-still-failing-evern-after-upgrading-percona-xtrabackup-to-2-1-6/3130/1 "2013-12-02T12:41:34Z")
Hi Team, Percona xtrabackup is upgraded to the latest version “percona-xtrabackup.x86\_64 - 2.1.6-702.rhel5”, but still observing the same error mentioned below. xtrabackup: error: log block numbers mismatch: xtrabackup: error: expected log block no. 2671901, but got no. 1068025125 from the log file. xtrabackup: Error: xtrabackup\_copy\_logfile() failed. innobackupex: Error: ibbackup child process has died at /usr/bin/innobackupex line 389. DBD::mysql::db selectrow\_array failed: MySQL server has gone away at /usr/bin/innobackupex line 1325. Here are the DB related parameters in my.cnf innodb\_file\_per\_table=1 innodb\_max\_purge\_lag=100000 innodb\_buffer\_pool\_size=120GB innodb\_log\_buffer\_size=80M innodb\_log\_file\_size=2GB innodb\_open\_files=1000 innodb\_flush\_log\_at\_trx\_commit=2 innodb\_flush\_method=O\_DIRECT innodb\_thread\_concurrency=0 innodb\_flush\_neighbor\_pages=0 innodb\_io\_capacity=10000 max\_allowed\_packet=48M query\_cache\_type = 0 query\_cache\_size = 10M max\_connections=40000 Backup command is a pearl script, might not be able to share that due security reasons. Could you please suggest if there needs any parameter value changes if so how much? Kindly suggest a permanent solution please! Best Regards, Krishna