# Log file ./ib\_logfile1 is of different size than other log files

**URL:** <https://forums.percona.com/t/log-file-ib-logfile1-is-of-different-size-than-other-log-files/6939>\
**Category:** Percona XtraBackup\
**Created:** [April 1, 2019, 11:46pm UTC](https://forums.percona.com/t/log-file-ib-logfile1-is-of-different-size-than-other-log-files/6939 "2019-04-01T23:46:21Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![remcp](https://avatars.discourse-cdn.com/v4/letter/r/3e96dc/32.png) [@remcp](https://forums.percona.com/u/remcp)\
**Post date:** [April 1, 2019, 11:46pm UTC](https://forums.percona.com/t/log-file-ib-logfile1-is-of-different-size-than-other-log-files/6939/1 "2019-04-01T23:46:21Z")

</div>

Hi everyone,

We lost one schema in our database a few days ago. We have backups generated and stored daily using the following:

```auto

$ innobackupex --defaults-extra-file=/root/.my.cnf --no-timestamp --stream=tar ./ | gzip - > backupfile.tar.gz

```

The above is generated on the following system:

> [@](#):
>
> CentOS Linux release 7.3.1611 (Core)  
> innobackupex version 2.4.8 Linux (x86\_64) (revision id: 97330f7)  
> mysqld Ver 5.7.18-15 for Linux on x86\_64 (Percona Server (GPL), Release 15, Revision bff2cd9)

We have our backup file and we’re trying to recover it on a different system first, because we don’t want to stop the production database server right away and we don’t want to mess up our existing data if the recovery goes wrong. So I’m trying the following:

```auto

$ tar -zxvf backupfile.tar.gz
$ innobackupex --defaults-file=./backup-my.cnf --apply-log .

```

On the following system:

> [@](#):
>
> Ubuntu Server 16.04.6 LTS (Xenial Xerus)  
> innobackupex version 2.4.13 Linux (x86\_64) (revision id: 3e7ca7c)  
> mysqld Ver 5.7.25-0ubuntu0.16.04.2 for Linux on x86\_64 ((Ubuntu))

Sadly, I’m always getting this error:

```auto

Log file ./ib_logfile1 is of different size 50331648 bytes than other log files 8388608 bytes!

```

Is there anything I can do to resolve this problem?
