xtrabackup partial backup one database issue

25 views
Skip to first unread message

prasanth kumar

unread,
May 12, 2018, 6:52:45 AM5/12/18
to Percona Discussion

HI

i have tried many times  take out particular database from mariadb 10.0.23 with xtrabackup 2.4 partial backup.


1.  xtrabackup --backup --user=root --password=Oracle@123  --databases=12345 --target-dir=/home/xxxx  --socket=/var/lib/mysql/mysql.sock

2. prepare:xtrabackup --prepare --user=root --password=Oracle@123   --target-dir=/home/xxxx  --socket=/var/lib/mysql/mysql.sock

while preparing i seeing this error for all dbs
InnoDB: Operating system error number 2 in a file operation.
InnoDB: The error means the system cannot find the path specified.
InnoDB: Could not find a valid tablespace file for `vjngrnew_db/radacct`. Please refer to http://dev.mysql.com/doc/refman/5.7/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
InnoDB: Failed to find tablespace for table `rn_db`.`radacct` in the cache. Attempting to load the tablespace with space id 434333

3. i have skipped this ,  i have tried to import  newbox/datadir along with mysql_installdb for system tables.

there also i am seeing the same error.
InnoDB: The error means the system cannot find the path specified.
180512 15:42:20 [ERROR] InnoDB: Could not find a valid tablespace file for 'whitefield_db/radacct'. See http://dev.mysql.com/doc/refman/5.6/en/innodb-troubleshooting-datadict.html for how to resolve the issue.
InnoDB: Error: tablespace id is 1 in the data dictionary
InnoDB: but in file ./mysql/innodb_table_stats.ibd it is 564842!
2018-05-12 15:42:20 7f34813ff700  InnoDB: Assertion failure in thread 139863483479808 in file fil0fil.cc line 635
InnoDB: We intentionally generate a memory trap.
InnoDB: Submit a detailed bug report to http://bugs.mysql.com.
InnoDB: If you get repeated assertion failures or crashes, even
InnoDB: immediately after the mysqld startup, there may be
InnoDB: corruption in the InnoDB tablespace. Please refer to
InnoDB: http://dev.mysql.com/doc/refman/5.6/en/forcing-innodb-recovery.html
InnoDB: about forcing recovery.
180512 15:42:20 [ERROR] mysqld got signal 6 ;
This could be because you hit a bug. It is also possible that this binary
or one of the libraries it was linked against is corrupt, improperly built,
or misconfigured. This error can also be caused by malfunctioning hardware.

please help me to solve as well post doc for partial backup


Regards
Prasanth



Reply all
Reply to author
Forward
0 new messages