[MySQL生產環境資料恢復]innobackupex: fatal error: OR no 'datadir'
1 執行恢復命令
[xxx@xxx-c001db1 tmp]$ time /usr/bin/innobackupex --rsync --user="user" --password="#xxx$" /mysqldata/shared/backup
[--rsync ] 可以記錄master點,以便進行復制設定。
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 2009-2012. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
131023 04:26:26 innobackupex: Starting mysql with options: --password=xxxxxxxx --user='user' --unbuffered --
131023 04:26:26 innobackupex: Connected to database with mysql child process (pid=24497)
131023 04:26:32 innobackupex: Connection to database server closed
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql Ver 14.14 Distrib 5.5.25a, for Linux (x86_64) using readline 5.1
innobackupex: Using mysql server version Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.
xtrabackup: Error: Please set parameter 'datadir'
innobackupex: fatal error: no 'mysqld' group in MySQL options
innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options
real 0m6.379s
user 0m0.219s
sys 0m0.124s
mysql 26087 26086 0 04:32 pts/3 00:00:00 -bash
2 去check 配置檔案有無datadir配置引數。
[xxx@xxx-c001db1 sharding_setup_1]$ cat /xxx/xxx/xxx/5.5.25a/my.cnf |grep datadir
datadir=/mysqldata/data
看起來my.cnf裡面已經配置了。
3 自定義備份制定my.cnf,試下看。
[xxx@xxx-c001db1 backup]$ time /usr/bin/innobackupex --rsync --user="user" --password="#xxx$" --defaults-file=/opt/xxx/xxx/5.5.25a/my.cnf /mysqldata/backup
InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 2009-2012. All Rights Reserved.
This software is published under
the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.
131023 06:33:41 innobackupex: Starting mysql with options: --defaults-file='/opt/xxx/xxx/5.5.25a/my.cnf' --password=xxxxxxxx --user='user' --unbuffered --
131023 06:33:41 innobackupex: Connected to database with mysql child process (pid=22321)
131023 06:33:47 innobackupex: Connection to database server closed
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
innobackupex: Using mysql Ver 14.14 Distrib 5.5.25a, for Linux (x86_64) using readline 5.1
innobackupex: Using mysql server version Copyright (c) 2000, 2011, Oracle and/or its affiliates. All rights reserved.
innobackupex: Created backup directory /mysqldata/shared/backup/2013-10-23_06-33-47
131023 06:33:47 innobackupex: Starting mysql with options: --defaults-file='/opt/xxx/xxx/5.5.25a/my.cnf' --password=xxxxxxxx --user='user' --unbuffered --
131023 06:33:47 innobackupex: Connected to database with mysql child process (pid=22358)
131023 06:33:49 innobackupex: Connection to database server closed
131023 06:33:49 innobackupex: Starting ibbackup with command: xtrabackup_55 --defaults-file="/opt/xxx/xxx/5.5.25a/my.cnf" --backup --suspend-at-end --target-dir=/mysqldata/shared/backup/2013-10-23_06-33-47
innobackupex: Waiting for ibbackup (pid=22419) to suspend
innobackupex: Suspend file '/mysqldata/shared/backup/2013-10-23_06-33-47/xtrabackup_suspended'
xtrabackup_55 version 2.0.0 for Percona Server 5.5.16 Linux (x86_64) (revision id: 417)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /mysqldata/data
xtrabackup: Target instance is assumed as followings.
xtrabackup: innodb_data_home_dir = /mysqldata/data
xtrabackup: innodb_data_file_path = ibdata01:1G:autoextend
xtrabackup: innodb_log_group_home_dir = /mysqldata/iblogs
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 1073741824
131023 6:33:49 InnoDB: Using Linux native AIO
xtrabackup: using O_DIRECT
131023 6:33:49 InnoDB: Warning: allocated tablespace 68, old maximum was 9
>> log scanned up to (450994458760)
[01] Copying /mysqldata/data/ibdata01 to /mysqldata/shared/backup/2013-10-23_06-33-47/ibdata01
>> log scanned up to (450994626288)
>> log scanned up to (450994768050)
[01] ...done
[01] Copying ./billing/enum_invoice_tax_status.ibd to /mysqldata/shared/backup/2013-10-23_06-33-47/./xxx/xxxxtb.ibd
[01] ...done
.......
4 OK,成功了,在innobackupex的命令列上面指定--defaults-file=/opt/xxx/xxx/5.5.25a/my.cnf既可解決此問題。
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/26230597/viewspace-1080262/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- 生產環境資料庫恢復一例資料庫
- 使用innobackupex恢復mysql資料庫MySql資料庫
- 生產環境故障處理演練-mysql資料庫主從恢復MySql資料庫
- 使用RMAN將生產庫資料恢復到另外環境追溯先前的資料資料恢復
- MySQL資料庫生產環境安全規範MySql資料庫
- Xtrabackup恢復時報錯'Error: datadir must be specified'Error
- mysql innobackupex增量備份恢復MySql
- 【MySql】innobackupex增量備份和恢復MySql
- MySQL innobackupex全量備份恢復MySql
- 【MySql】innobackupex 增量備份和恢復MySql
- 生產環境搭建高可用Harbor(包括恢復演練實操)
- Elasticsearch系列---生產資料備份恢復方案Elasticsearch
- mysql之 Innobackupex(全備+增量)備份恢復MySql
- 【RMAN】RAC資料恢復至單機環境資料恢復
- 【資料庫資料恢復】LINUX環境下ORACLE資料庫誤刪除的資料恢復資料庫資料恢復LinuxOracle
- 生產環境搭建MySQL複製的教程MySql
- mysql資料恢復MySql資料恢復
- 記一次 Vagrant 環境下更換 MySQL 資料目錄 datadir 的坑MySql
- 【伺服器虛擬化資料恢復】Xen Server環境下資料庫資料恢復案例伺服器資料恢復Server資料庫
- 成功恢復無備份RAC環境資料庫資料庫
- 生產環境資料遷移問題彙總
- 寶塔資料庫恢復 mysql資料庫丟失恢復 mysql資料庫刪除庫恢復 寶塔mysql資料庫恢復資料庫MySql
- 使用innobackupex線上增量備份和再增量備份及恢復mysql資料庫MySql資料庫
- 生產環境中MySQL複製的搭建KPMySql
- 【伺服器資料恢復】AIX系統環境下LV被破壞如何恢復資料?伺服器資料恢復AI
- redmine生產環境搭建
- Django生產環境搭建Django
- RAC環境利用備份恢復RAC資料庫(五)資料庫
- RAC環境利用備份恢復RAC資料庫(四)資料庫
- RAC環境利用備份恢復RAC資料庫(三)資料庫
- RAC環境利用備份恢復RAC資料庫(二)資料庫
- RAC環境利用備份恢復RAC資料庫(一)資料庫
- innobackupex備份恢復實戰
- 【伺服器資料恢復】AIX環境下誤刪除邏輯卷的資料恢復方案伺服器資料恢復AI
- innobackupex: Error: noError
- 一次生產環境的docker MySQL故障DockerMySql
- 生產環境使用 pt-table-checksum 檢查MySQL資料一致性MySql
- 【伺服器資料恢復】Linux環境下RAID6磁碟陣列資料恢復案例伺服器資料恢復LinuxAI陣列