一.基本資訊
生產環境mysql版本：mariadb 10.0.20   備份xtrabackup版本：xtrabackup 2.2.9 或 2.4.4 
測試恢復環境mysql版本：mariadb 10.0.20 恢復xtrabackup版本：xtrabackup 2.2.11 或 2.4.4
二.問題描述
  用xtrabckup將生產環境的備份在異機上恢復後，能正常啟動mysql，但在查看錶結構時，提示表不存在。
三.問題分析
  可以重現報借，如下是具體步驟：
1.將備份集從生產環境中copy到測試機，並更改owner許可權
drwxr-xr-x 13 root root      4096 Nov 18 09:36 xtrabackup_20161117010002
chown -R apps:apps xtrabackup_20161117010002
2.解壓備份集
innobackupex --decompress /apps/backup/xtrabackup_20161117010002
......................
161118 09:42:55  innobackupex: completed OK!
上面顯示OK，表示成功解壓
3.應用日誌準備備份集
innobackupex --apply-log /apps/backup/xtrabackup_20161117010002
....................
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: FTS optimize thread exiting.
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 54808221346
161118 09:46:24  innobackupex: completed OK!
上面顯示OK，表示成功備份整合功應用日誌
4.將備份集還原到mysql對應資料目錄
innobackupex --defaults-file=/apps/dbdat/my3306.cnf  --copy-back /apps/backup/xtrabackup_20161117010002
................................................
innobackupex: Starting to copy InnoDB system tablespace
innobackupex: in '/apps/backup/xtrabackup_20161117010002'
innobackupex: back to original InnoDB data directory '/apps/dbdat/mariadb10_data3306'
innobackupex: Copying '/apps/backup/xtrabackup_20161117010002/ibdata1' to '/apps/dbdat/mariadb10_data3306/ibdata1'
innobackupex: Starting to copy InnoDB undo tablespaces
innobackupex: in '/apps/backup/xtrabackup_20161117010002'
innobackupex: back to '/apps/dbdat/mariadb10_data3306'
innobackupex: Starting to copy InnoDB log files
innobackupex: in '/apps/backup/xtrabackup_20161117010002'
innobackupex: back to original InnoDB log directory '/apps/dbdat/mariadb10_data3306'
innobackupex: Copying '/apps/backup/xtrabackup_20161117010002/ib_logfile2' to '/apps/dbdat/mariadb10_data3306/ib_logfile2'
innobackupex: Copying '/apps/backup/xtrabackup_20161117010002/ib_logfile0' to '/apps/dbdat/mariadb10_data3306/ib_logfile0'
innobackupex: Copying '/apps/backup/xtrabackup_20161117010002/ib_logfile1' to '/apps/dbdat/mariadb10_data3306/ib_logfile1'
innobackupex: Copying '/apps/backup/xtrabackup_20161117010002/ib_logfile3' to '/apps/dbdat/mariadb10_data3306/ib_logfile3'
innobackupex: Finished copying back files.
161118 09:51:30  innobackupex: completed OK!
上面顯示OK，表示成功copy備份集
5.啟動mysql
/apps/svr/mariadb10/bin/mysqld_safe --defaults-file=/apps/dbdat/my3306.cnf &
檢查是否有成功啟動：
a 檢查程序
[

[email protected] ~]$ ps -ef|grep mysql
apps     21281 21204  0 09:52 pts/0    00:00:00 /bin/sh /apps/svr/mariadb10/bin/mysqld_safe --defaults-file=/apps/dbdat/my3306.cnf
apps     21837 21281 11 09:52 pts/0    00:00:01 /apps/svr/mariadb10/bin/mysqld --defaults-file=/apps/dbdat/my3306.cnf --basedir=/apps/svr/mariadb10 --datadir=/apps/dbdat/mariadb10_data3306 --plugin-dir=/apps/svr/mariadb10/lib/plugin --log-error=/apps/logs/mysql/error3306.log --open-files-limit=8192 --pid-file=/apps/dbdat/mariadb10_data3306/mysql.pid --socket=/tmp/mysql3306.sock --port=3306
apps     21906 21204  0 09:53 pts/0    00:00:00 grep mysql
b.檢查埠
[

[email protected] ~]$ netstat -an|grep 3306
tcp        0      0 0.0.0.0:3306                0.0.0.0:*                   LISTEN     
unix  2      [ ACC ]     STREAM     LISTENING     15423289 /tmp/mysql3306.sock
c.檢查錯誤日誌
161118 09:52:48 mysqld_safe Starting mysqld daemon with databases from /apps/dbdat/mariadb10_data3306
161118  9:52:49 [Note] /apps/svr/mariadb10/bin/mysqld (mysqld 10.0.20-MariaDB-log) starting as process 21837 ...
2016-11-18 09:52:49 7f56e11d0760 InnoDB: Warning: Using innodb_additional_mem_pool_size is DEPRECATED. This option may be removed in future releases, together with the option innodb_use_sys_malloc and with the InnoDB's internal memory allocator.
161118  9:52:49 [Note] InnoDB: Using mutexes to ref count buffer pool pages
161118  9:52:49 [Note] InnoDB: The InnoDB memory heap is disabled
161118  9:52:49 [Note] InnoDB: Mutexes and rw_locks use GCC atomic builtins
161118  9:52:49 [Note] InnoDB: Memory barrier is not used
161118  9:52:49 [Note] InnoDB: Compressed tables use zlib 1.2.3
161118  9:52:49 [Note] InnoDB: Using Linux native AIO
161118  9:52:49 [Note] InnoDB: Using CPU crc32 instructions
161118  9:52:49 [Note] InnoDB: Initializing buffer pool, size = 21.0G
161118  9:52:50 [Note] InnoDB: Completed initialization of buffer pool
161118  9:52:50 [Note] InnoDB: Highest supported file format is Barracuda.
161118  9:52:51 [Note] InnoDB: 128 rollback segment(s) are active.
161118  9:52:51 [Note] InnoDB: Waiting for purge to start
161118  9:52:51 [Note] InnoDB:  Percona XtraDB (http://www.percona.com) 5.6.24-72.2 started; log sequence number 54808221346
161118  9:52:51 [Note] Plugin 'FEEDBACK' is disabled.
161118  9:52:51 [Note] Server socket created on IP: '0.0.0.0'.
161118  9:52:51 [Note] Event Scheduler: Loaded 0 events
161118  9:52:51 [Note] Event Scheduler: scheduler thread started with id 2
161118  9:52:51 [Note] /apps/svr/mariadb10/bin/mysqld: ready for connections.
Version: '10.0.20-MariaDB-log'  socket: '/tmp/mysql3306.sock'  port: 3306  MariaDB Server
6.登入mysql查詢表
/apps/svr/mariadb10/bin/mysql -uroot -p -S /tmp/mysql3306.sock
MariaDB [(none)]> use ie2
Database changed
MariaDB [ie2]> show tables;
MariaDB [ie2]> desc Dos
    -> ;
ERROR 1146 (42S02): Table 'ie2.Dos' doesn't exist
MariaDB [ie2]> desc `MetaData`;
ERROR 1146 (42S02): Table 'ie2.metadata' doesn't exist
---檢查磁碟上的資料檔案
[

[email protected] mariadb10_data3306]$ cd ie2
[[email protected] ie2]$ ls -ltr
total 12988
-rw-rw-r-- 1 apps apps   131072 Nov 18 09:51 Dos.ibd
-rw-rw-r-- 1 apps apps     9921 Nov 18 09:51 Dos.frm
-rw-rw-r-- 1 apps apps       61 Nov 18 09:51 db.opt
[[email protected] ie2]$ cat db.opt
default-character-set=utf8
default-collation=utf8_general_ci
將生產環境的備份的配置檔案與測試恢復環境用diff比較一下：
[[email protected] dbdat]$ diff mariadb10_3306.cnf my3306.cnf
2,3c2,3
< mysqld=/apps/svr/mariadb10/bin/mysqld_safe
< mysqladmin=/apps/svr/mariadb10/bin/mysqladmin
---
> mysqld=/apps/svr/mariadb101/bin/mysqld_safe
> mysqladmin=/apps/svr/mariadb101/bin/mysqladmin
5c5
< log=/apps/logs/mysql/multi.log
---
> log=/apps/logs/mysql/multi3306.log
33c33
< server-id=621133306 
---
> server-id=313306 
107c107
< lower_case_table_names=0 
---
> lower_case_table_names=1 
212c212
< read_only=0
---
> read_only 
218c218
< #slave_exec_mode= 
---
> #c_mode= 
221,231c221
< slave_parallel_threads=0 # for mariadb10 
< 
< #server-id = 14
< #log-bin = slave-bin.log
< 
< #replicate_wild_do_table = ie2.%
---
> #slave_parallel_threads=4 # for mariadb10 
234c224
< slave_compressed_protocol=0 #for RBR
---
> #slave_compressed_protocol #for RBR
255c245
< expire_logs_days=3 
---
> expire_logs_days=7
313c303
< innodb_buffer_pool_size=24G  #for mariadb 
---
> innodb_buffer_pool_size=21G  #for mariadb 
328d317
< innodb_io_capacity_max=2400
335d323
< innodb_lru_scan_depth=1024
340c328
< innodb_file_per_table 
---
> innodb_file_per_table=1 
384c372
< innodb_thread_concurrency=32       #at least equal cpu nums 
---
> innodb_thread_concurrency=8       #at least equal cpu nums 
408c396
< key_buffer_size=2048M 
---
> key_buffer_size=1024M 
437c425
< myisam_max_sort_file_size=10G 
---
> myisam_max_sort_file_size=5G 
472c460
< #federated
---
> federated
492d479
< max_allowed_packet = 2G # add by alading on 20151110
499,500c486,487
< key_buffer = 512M
< sort_buffer_size = 512M
---
> key_buffer = 256M
> sort_buffer_size = 256M
511a499
>
上面配置比較，在於下面引數不同：
< lower_case_table_names=0 
> lower_case_table_names=1 
大小寫問題，改成 0 去試一下。
四.問題解決
 將配置檔案修改lower_case_table_names=0 ，並重啟mysql例項。
然後登入mysql檢視,不再報錯。
lower_case_table_names=1時，會將表名轉換成小寫來查詢和儲存。如果希望在資料庫裡面建立表的時候保留大小寫字元狀態，則應該把這個引數置0： lower_case_table_names=0。