# Backup fails if done just after restore

**URL:** <https://forums.percona.com/t/backup-fails-if-done-just-after-restore/4932>\
**Category:** Percona XtraBackup\
**Created:** [June 16, 2016, 4:13am UTC](https://forums.percona.com/t/backup-fails-if-done-just-after-restore/4932 "2016-06-16T04:13:34Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![weeblr](https://avatars.discourse-cdn.com/v4/letter/w/67e7ee/32.png) [@weeblr](https://forums.percona.com/u/weeblr)\
**Post date:** [June 16, 2016, 4:13am UTC](https://forums.percona.com/t/backup-fails-if-done-just-after-restore/4932/1 "2016-06-16T04:13:34Z")

</div>

Hi All,

Been using innobackupex for a few years now. While setting up some new infrastructure, I noticed the following:

- innobackupex version 2.3.4 Linux (x86\_64) (revision id: e80c779)
- backup and restore works fine (I have some script automating most of the usage)
- when restoring, innobackupex does not restore the ib\_logfile0 file, which is expected

however, if one does another backup, shortly after the restore operation, and there was no write on the database in the mean time (at least I think that’s the reason), then the next backup fails with:

2016-06-16 08:20:01 7f32156b4740 InnoDB: Operating system error number 2 in a file operation.  
InnoDB: The error means the system cannot find the path specified.  
InnoDB: File ./ib\_logfile0: ‘open’ returned OS error 71. Cannot continue operation

Restore is done with:  
innobackupex –defaults-file=/etc/mysql/my.cnf --copy-back db\_tmp Am I missing something somewhere?

I suspect on a real production server, this won’t be an issue, as there will always be some writes in between a restore and next backup but still a bit strange.

Thanks for any input.