# backup size

**URL:** <https://forums.percona.com/t/backup-size/2303>\
**Category:** Percona XtraBackup\
**Created:** [October 16, 2012, 3:07pm UTC](https://forums.percona.com/t/backup-size/2303 "2012-10-16T15:07:28Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mugenbb6](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@mugenbb6](https://forums.percona.com/u/mugenbb6)\
**Post date:** [October 16, 2012, 3:07pm UTC](https://forums.percona.com/t/backup-size/2303/1 "2012-10-16T15:07:28Z")

</div>

When I run “innobackupex --slave-info --safe-slave-backup --user=user --password=password /backupdir/”, the backup is ~140gb which is about the size of my dataset. When I prep the backup with “innobackupex --apply-log /backupdir/timestamp”, the backup grows to 250gb.

I thought this was due to new data being written to the slave, so I even tried to stop the slave replication to make sure no new data is submitted before running innobackupex, and the size still grows.

Here’s my version:  
innobackupex -version  
InnoDB Backup Utility v1.5.1-xtrabackup;

My mysql version is 5.5.27

As a test, I’ve restored the backup to a test server, and my dataset is now 250gb. Running mysqlcheck optimize brings it back down to 140gb.

---

<div class="post-metadata">

**Author:** ![mugenbb6](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@mugenbb6](https://forums.percona.com/u/mugenbb6)\
**Post date:** [October 18, 2012, 4:04pm UTC](https://forums.percona.com/t/backup-size/2303/2 "2012-10-18T16:04:21Z")

</div>

Not sure if it helps, but I’m running percona-xtrabackup-2.0.0.

---

<div class="post-metadata">

**Author:** ![mugenbb6](https://avatars.discourse-cdn.com/v4/letter/m/46a35a/32.png) [@mugenbb6](https://forums.percona.com/u/mugenbb6)\
**Post date:** [October 19, 2012, 10:36am UTC](https://forums.percona.com/t/backup-size/2303/3 "2012-10-19T10:36:43Z")

</div>

I’ve installed the latest xtrabackup 2.0.3, and it’s the same result. Any help will be appreciated.