# Failing @ Percona

**URL:** <https://forums.percona.com/t/failing-percona/4206>\
**Category:** Percona XtraBackup\
**Created:** [May 6, 2015, 3:31pm UTC](https://forums.percona.com/t/failing-percona/4206 "2015-05-06T15:31:41Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![jrivera](https://sea1.discourse-cdn.com/flex019/user_avatar/forums.percona.com/jrivera/32/13_2.png) [@jrivera](https://forums.percona.com/u/jrivera)\
**Post date:** [May 6, 2015, 11:19pm UTC](https://forums.percona.com/t/failing-percona/4206/2 "2015-05-06T23:19:06Z")

</div>

Let me try to answer but others may have a better suggestion, so here goes:

1] You can run “–apply-log --export” during the prepare phase so as to create those .exp and .cfg files needed when importing the individual tables. You can read further here - [url][Percona XtraBackup](http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/restoring_individual_tables_ibk.html%5B/url%5D). This is going to be a tedious task in case you plan on importing a lot of tables.

2] There is no exclude option but i think you may be able to use either --databases or --tables-file options, of course you should not include the database you want NOT to be backed up in the process. For further reading - [url][Percona XtraBackup](http://www.percona.com/doc/percona-xtrabackup/2.2/innobackupex/innobackupex_option_reference.html%5B/url%5D)

3] There is no specific rule on whether you run --apply-log after the backup was created or before you want the backup restored. BUT, to make sure that your backup is valid, you can run --apply-log to check it. To understand what --apply-log does, please refer to [url][Percona XtraBackup](http://www.percona.com/doc/percona-xtrabackup/2.2/xtrabackup_bin/preparing_the_backup.html%5B/url%5D), since --apply-log implies running xtrabackup --prepare twice.

---

_[View the full topic](https://forums.percona.com/t/failing-percona/4206)._
