mariabackup fails with massive DDLs

Hello,

an application use massive DDLs on master like

create temp table tmp_…
rename temp table to new_table
rename new_table to z_table...

etc.

This cause confusion with tablespaceid

InnoDB: At LSN: xxxxxxxx : unable to open file tablenae.ibd for tablespace yyyy
[Note] InnoDB: Ignoring data file ... with tablespace yyyy

Error log after restore:
:Expected tablespace flags 0x21 but found 0x0 in the file ...

This can be solved with
innodb_max_dirty_pages_pct=0

So it assume it is related to checkpoint (atomic DDL ?) and forcing a checkpoint
helds.

So backport of MDEV-3000 could help.