# innobackup --database restore Mariadb 10.1.16 not support Drop tablespace

**URL:** <https://forums.percona.com/t/innobackup-database-restore-mariadb-10-1-16-not-support-drop-tablespace/5065>\
**Category:** Percona XtraBackup\
**Created:** [September 2, 2016, 12:48am UTC](https://forums.percona.com/t/innobackup-database-restore-mariadb-10-1-16-not-support-drop-tablespace/5065 "2016-09-02T00:48:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![ritchieliu029](https://avatars.discourse-cdn.com/v4/letter/r/f04885/32.png) [@ritchieliu029](https://forums.percona.com/u/ritchieliu029)\
**Post date:** [September 2, 2016, 12:48am UTC](https://forums.percona.com/t/innobackup-database-restore-mariadb-10-1-16-not-support-drop-tablespace/5065/1 "2016-09-02T00:48:56Z")

</div>

Hi all,

I try to backup --database only on 150GB data for master (single mariadb 10.1.16) and slave replication (one node of the galara cluster). sqldump is not a option which takes too long. I successfull did the backup with following:  
innobackupex --user=root --password=password --databases=“XXX” /opt/mysql/innobackupbackup/xxxbackup --slave-info --no-timestamp --parallel=4  
innobackupex --apply-log --export /opt/mysql/innobackupbackup/xxxbackup

But when i restore it. Mariadb 10.1.16 not support the below:  
ALTER TABLE mydatabase.mytable DISCARD TABLESPACE;  
ALTER TABLE mydatabase.mytable IMPORT TABLESPACE;

How can we restore it with knowing the binlog position of master to be able to startup slave?  
innodb\_file\_per\_table option is enabled in both servers.  
Thanks.  
Ritchie