We have a log table as part of one of our databases which is ~5GB and gets rolled up every hour (lots of transactions). I’ve found when doing an incremental restore of our databases it spends a lot of time processing this one table, which at the end of the day isn’t critical to getting our site back online. If there were an emergency and we needed to restore quickly then this table would slow us down.
Is there anyway to exclude this one table when backing up or restoring?
Hi noodlesnz;
As far as I know, there is no option to exclude tables, only to include tables. So you would have to explicitly include all the tables except for the one you want to exclude. Another option is to setup a slave server where that table does not exist and use replication filters to filter out replication events for that table (though replication filters can be a beast to maintain and rarely do what you expect). Then you could backup the new slave where that table does not exist.
[url]The innobackupex Option Reference
-Scott