# xtrabackup: This target seems to be not prepared . my backup has completed

**URL:** <https://forums.percona.com/t/xtrabackup-this-target-seems-to-be-not-prepared-my-backup-has-completed/7342>\
**Category:** Other MySQL® Questions\
**Created:** [December 11, 2019, 7:14am UTC](https://forums.percona.com/t/xtrabackup-this-target-seems-to-be-not-prepared-my-backup-has-completed/7342 "2019-12-11T07:14:02Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![pythondev1](https://avatars.discourse-cdn.com/v4/letter/p/f17d59/32.png) [@pythondev1](https://forums.percona.com/u/pythondev1)\
**Post date:** [December 11, 2019, 7:14am UTC](https://forums.percona.com/t/xtrabackup-this-target-seems-to-be-not-prepared-my-backup-has-completed/7342/1 "2019-12-11T07:14:02Z")

</div>

I run backups early in the morning. However I’ve noticed the backups complete yet. I am unsure why the backup completes but then it shuts itself down.  
Here is my backup script  
dest=“current\_backup/”;  
xtrabackup --backup --target-dir=$dest --no-timestamp 2\> $log;  
xtrabackup --prepare --target-dir=$dest 2\>\> $log;

My log when the backup happens.

91211 02:14:00 [00] Copying ib\_buffer\_pool to /db\_backup/current\_backup/ib\_buffer\_pool  
191211 02:14:00 [00] …done  
191211 02:14:00 Backup created in directory ‘/db\_backup/current\_backup/’  
191211 02:14:00 [00] Writing /db\_backup/current\_backup/backup-my.cnf  
191211 02:14:00 [00] …done  
191211 02:14:00 [00] Writing /db\_backup/current\_backup/xtrabackup\_info  
191211 02:14:00 [00] …done  
xtrabackup: Transaction log of lsn (5385754852588) to (5385817296328) was copied.  
191211 02:14:01 completed OK!  
xtrabackup version 2.4.9 based on MySQL server 5.7.13 Linux (x86\_64) (revision id: a467167cdd4)  
xtrabackup: cd to /db\_backup/current\_backup/  
xtrabackup: This target seems to be not prepared yet.  
InnoDB: Number of pools: 1  
xtrabackup: xtrabackup\_logfile detected: size=70254592, start\_lsn=(5385754852588)  
xtrabackup: using the following InnoDB configuration for recovery:  
xtrabackup: innodb\_data\_home\_dir = .  
xtrabackup: innodb\_data\_file\_path = ibdata1:12M:autoextend  
xtrabackup: innodb\_log\_group\_home\_dir = .  
xtrabackup: innodb\_log\_files\_in\_group = 1  
xtrabackup: innodb\_log\_file\_size = 70254592  
xtrabackup: using the following InnoDB configuration for recovery:  
xtrabackup: innodb\_data\_home\_dir = .  
xtrabackup: innodb\_data\_file\_path = ibdata1:12M:autoextend  
xtrabackup: innodb\_log\_group\_home\_dir = .  
xtrabackup: innodb\_log\_file\_size = 70254592  
xtrabackup: Starting InnoDB instance for recovery.  
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)  
InnoDB: PUNCH HOLE support available  
…  
Doing recovery: scanned up to log sequence number 5385817296328  
InnoDB: Database was not shutdown normally!  
InnoDB: Starting crash recovery.  
InnoDB: Doing recovery: scanned up to log sequence number 5385817296328 (99%)  
page\_cleaner: 1000ms intended loop took 530588ms. The settings might not be optimal  
starting shutdown with innodb\_fast\_shutdown = 1  
Starting shutdown…  
Shutdown completed.

Here is my.cnf  
sql\_mode = STRICT\_TRANS\_TABLES,NO\_ZERO\_IN\_DATE,NO\_ZERO\_DATE,ERROR\_FOR\_DIVISION\_BY\_ZERO,NO\_AUTO\_CREATE\_USER,NO\_ENGINE\_SUBSTITUTION  
innodb\_buffer\_pool\_size = 25G  
innodb\_buffer\_pool\_instances = 8  
innodb\_lock\_wait\_timeout = 3600000  
wait\_timeout = 86400  
interactive\_timeout = 86400  
max\_heap\_table\_size = 96M  
sort\_buffer\_size = 16M  
join\_buffer\_size = 16M  
tmp\_table\_size = 96M  
max\_sort\_length = 8K  
max\_allowed\_packet = 16M  
group\_concat\_max\_len = 16M  
max\_connections = 200  
max\_connect\_errors = 10  
expire\_logs\_days = 2  
max\_binlog\_size = 128M

symbolic-links=0  
log-bin=binlog  
binlog-format=ROW  
log\_slave\_updates  
wsrep\_log\_conflicts  
expire\_logs\_days=7