We are facing similar problem when renaming InnoDB tables in cycle:
-- versions ---------------------
mysql --version
mysql Ver 14.14 Distrib 5.5.23, for Linux (x86_64) using readline 5.1
xtrabackup_55 -v
xtrabackup_55 version 2.0.3 for Percona Server 5.5.16 Linux (x86_64) (revision id: 470)
-- The problem occurs when applying log ------------
InnoDB: Starting crash recovery.
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 2788 of name './db2/ShopOfferAvgPositionCategoryTemp.ibd'
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 2788 of name './db2/ShopOfferAvgPositionCategory.ibd' already exists in the tablespace
InnoDB: memory cache!
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/innobackupex line 378
The problem occurs always when this RENAME TABLE is done while the backup is being taken:
RENAME TABLE `ShopOfferAvgPositionCategory` TO `ShopOfferAvgPositionCategorySwitch` , `ShopOfferAvgPositionCategoryTemp` TO `ShopOfferAvgPositionCategory` , `ShopOfferAvgPositionCategorySwitch` TO `ShopOfferAvgPositionCategoryTemp`
We are facing similar problem when renaming InnoDB tables in cycle: ------- -------
-- versions -------
mysql --version
mysql Ver 14.14 Distrib 5.5.23, for Linux (x86_64) using readline 5.1
xtrabackup_55 -v
xtrabackup_55 version 2.0.3 for Percona Server 5.5.16 Linux (x86_64) (revision id: 470)
-- The problem occurs when applying log ------------
innobackupex --apply-log --use-memory=48GB /data/db_restore
InnoDB: Starting crash recovery. ShopOfferAvgPos itionCategoryTe mp.ibd' ShopOfferAvgPos itionCategory. ibd' already exists in the tablespace innobackupex line 378
InnoDB: Reading tablespace information from the .ibd files...
InnoDB: Error: trying to add tablespace 2788 of name './db2/
InnoDB: to the tablespace memory cache, but tablespace
InnoDB: 2788 of name './db2/
InnoDB: memory cache!
innobackupex: Error:
innobackupex: ibbackup failed at /usr/bin/
-- ------- ------- ------- ------- ------- ------- ------- -
The problem occurs always when this RENAME TABLE is done while the backup is being taken:
RENAME TABLE `ShopOfferAvgPo sitionCategory` TO `ShopOfferAvgPo sitionCategoryS witch`
, `ShopOfferAvgPo sitionCategoryT emp` TO `ShopOfferAvgPo sitionCategory`
, `ShopOfferAvgPo sitionCategoryS witch` TO `ShopOfferAvgPo sitionCategoryT emp`