Xtrabackup 2.0.1 incremental backup don't drop table

Asked by Shay Fox


When I am doing full backup + incremental backup and restore it on another host I get orphan tables like table1 in the below log.
When I take the full backup, table1 was exist, but after a while when I took the incremental backup table1 was deleted (was dropped between the full and incremental operations). when I resorted the full + incremental on another host table1 wasn't drop properly, I expect it will be dropped after I restored the incremental and will be identical to the source DB.

note: no crash happened during the full and incremental backups.

is it a bug?

120729 23:55:42 InnoDB: Warning: trying to init to the tablespace memory cache
InnoDB: a tablespace 23837543 of name './DBname/table1.ibd',
InnoDB: but a tablespace 23831965 of the same name
InnoDB: already exists in the tablespace memory cache!
InnoDB: We assume that InnoDB did a crash recovery, and you had
InnoDB: an .ibd file for which the table did not exist in the
InnoDB: InnoDB internal data dictionary in the ibdata files.
InnoDB: We assume that you later removed the .ibd and .frm files,
InnoDB: and are now trying to recreate the table. We now remove the
InnoDB: conflicting tablespace object from the memory cache and try
InnoDB: the init again.


Question information

Revision history for this message
Alexey Kopytov (akopytov) said :

Yes, it's bug #856400.

Revision history for this message
Shay Fox (shay-fox) said :


Do you know when the fix will be available?
Is it the same in ver 2.0.0?


On Mon, Aug 6, 2012 at 12:51 PM, Alexey Kopytov <
<email address hidden>> wrote:

> Your question #204527 on Percona XtraBackup changed:
> https://answers.launchpad.net/percona-xtrabackup/+question/204527
> Linked to bug: #856400
> https://bugs.launchpad.net/bugs/856400
> "Remove dropped tables from a full backup when merging an incremental
> one"
> --
> You received this question notification because you asked the question.

This e-mail, as well as any attached document, may contain material which
is confidential and privileged and may include trademark, copyright and
other intellectual property rights that are proprietary to Kenshoo Ltd,
 its subsidiaries or affiliates ("Kenshoo"). This e-mail and its
attachments may be read, copied and used only by the addressee for the
purpose(s) for which it was disclosed herein. If you have received it in
error, please destroy the message and any attachment, and contact us
immediately. If you are not the intended recipient, be aware that any
review, reliance, disclosure, copying, distribution or use of the contents
of this message without Kenshoo's express permission is strictly prohibited.

Revision history for this message
Alexey Kopytov (akopytov) said :

No, this bug is not currently scheduled for any release, so I don't have any estimates.

Can you help with this problem?

Provide an answer of your own, or ask Shay Fox for more information if necessary.

To post a message you must log in.