Hi,
I’m trying to backup an individual partition following the procedure explained in the Percona web (“Backing up and restoring individual partitions”).
Source table is in “alienvault_siem” database defined as:
CREATE TABLE acid_event (
id bigint(20) unsigned NOT NULL AUTO_INCREMENT,
int_date int(10) unsigned NOT NULL,
event_id binary(16) NOT NULL,
device_id int(10) unsigned NOT NULL,
[…]
PRIMARY KEY (id,int_date),
KEY event_id (event_id)
) ENGINE=InnoDB AUTO_INCREMENT=10896148 DEFAULT CHARSET=utf8
/*!50100 PARTITION BY RANGE (int_date)
(PARTITION P20130212 VALUES LESS THAN (20130213) ENGINE = InnoDB,
PARTITION P20130213 VALUES LESS THAN (20130214) ENGINE = InnoDB,
PARTITION P20130214 VALUES LESS THAN (20130215) ENGINE = InnoDB,
PARTITION P20130215 VALUES LESS THAN (20130216) ENGINE = InnoDB,
PARTITION P20130216 VALUES LESS THAN (20130217) ENGINE = InnoDB,
PARTITION P20130217 VALUES LESS THAN (20130218) ENGINE = InnoDB,
PARTITION P20130218 VALUES LESS THAN (20130219) ENGINE = InnoDB,
PARTITION P20130219 VALUES LESS THAN (20130220) ENGINE = InnoDB,
PARTITION P20130220 VALUES LESS THAN (20130221) ENGINE = InnoDB,
PARTITION P99999999 VALUES LESS THAN MAXVALUE ENGINE = InnoDB) */
When I execute innobackupex, it skips the desired partition.
Command line:
innobackupex --user=bkpuser --password=pass --include=‘^alienvault_siem[.]acid_event#P#P20130219’ /root/testbackup/
Log line:
[…]
[01] Skipping ./alienvault_siem/acid_event#P#P20130219.ibd.
[…]
However, if I execute innobackupex with --include=‘^alienvault_siem[.]acid_event’ it takes all the partitions in acid_event successfully.
What’s wrong backing up an individual partition?
Is anyone in the same situation? Can anyone help me?
Thanks in advance!
