[生产环境数据恢复]innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options

1 运行恢复命令 

[[email protected] 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配置參数。

[[email protected] sharding_setup_1]$ cat /xxx/xxx/xxx/5.5.25a/my.cnf |grep datadir

datadir=/mysqldata/data

看起来my.cnf里面已经配置了。

3  自己定义备份制定my.cnf,试下看。

[[email protected] 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

[生产环境数据恢复]innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options

时间: 2024-10-11 14:49:26

[生产环境数据恢复]innobackupex: fatal error: OR no 'datadir' option in group 'mysqld' in MySQL options的相关文章

故障案例:主从同步报错Fatal error: The slave I/O thread stops because master and slave have equal MySQL server

场景一:因为数据量非常,大概有1.4T,需要在原先master1-slave1的情况下再创建一个库slave2,并且挂在slave1下,即master1-slave1-slave2的结构.为了方便,当时停掉从库salve1,show master status记录状态,开启log_slave_updates,并且关闭salve1,然后将这个从库的data文件夹直接copy到新的从库,结果在创建slave2和slave1的主从关系时报错 Fatal error: The slave I/O thr

Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs; these UUIDs must be different for replication to work

配置MySQL主从复制,遇到报错 Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs;  these UUIDs must be different for replication to work 是因为主从服务器里auto.cnf中的server-uuid是相同的(服务器是复制过去的). 把从服务器中的auto.cnf重命名或者删除,然后重新启动MySQL,

配置MySQL主从复制报错Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work

配置MySQL主从复制报错 Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server ids; these ids must be different for replication to work (or the --replicate-same-server-id option must be used on slave but this do

Composer环境混乱引起--Fatal error: Call to undefined method Fxp

Fatal error: Call to undefined method Fxp\Composer\AssetPlugin\Package\Version\V ersionParser::parseLinks() in C:\Documents and Settings\Administrator\Applicatio n Data\Composer\vendor\fxp\composer-asset-plugin\Repository\VcsPackageFilter.php on line

解决Fatal error in launcher: Unable to create process using '"'

问题 分析原因 网上看了很多方案都说直接运行 python3 -m pip install --upgrade pip 来升级pip版本就好了,这个在大多数情况下都是有用的.因为重装以后会根据更改后的python的执行文件来创建关联. 但是如果你的pip已经是最新版本的话就行不通了,因为已经是最新的版本根本就不让你升级.那么就用下面的命令来强制重装 pip 解决 python27 -m pip install --upgrade --force-reinstall pip 并配置环境变量 解决F

MySQL 主主报错: Fatal error: The slave I/O thread stops because master and slave have

Mysql 主主启动错误处理 error 信息: Slave_IO_State: Master_Host: 192.168.6.87 Master_User: replication Master_Port: 3306 Connect_Retry: 60 Master_Log_File: mysql-bin.000003 Read_Master_Log_Pos: 106 Relay_Log_File: mysqld-relay-bin.000002 Relay_Log_Pos: 4 Relay_

生产环境可用mysql5.7.23安装全过程

生产环境安装5.7.23全过程 先执行initialization.sh优化脚本 详情见 Linux 在安装mysql前,需要先查看一下是否清空了系统自带了mysql我们这里需要删除系统自带了mysql lib 我们先把mysql放置在/opt下先上传与线上版本一致的 [[email protected] opt]# cat /etc/redhat-release CentOS release 6.5 (Final) [[email protected] opt]# ll total 62932

奉上SCCM生产环境部署Error Logs

奉上SCCM生产环境部署Error Logs SCCM生产环境部署报错日志,供大家查看,如有此类问题,可共同探讨,附件为日志查看器及相关日志.

Zen Cart 138 在PHP5.3环境下出现的Fatal error: Cannot redeclare date_diff()

Zen Cart 138 在PHP5.3环境下出现的Fatal error: Cannot redeclare date_diff() in includes/functions/functions_general.php错误的解决方法 原因是在这个文件中已存在函数:date_diff()了,此时,我们需要做到与旧版本的PHP兼容,将Zen Cart中的date_diff()函数进行修改,解决方法如下: if(function_exists('date_diff') && phpversi