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

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

  1. MySql配置主从模式 Last_IO_Error: 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.

    今天在学习MyCat环境搭建的时候,在配置MySql的主从模式,发现slave在配置完毕后,配置的内容全部正确的情况下,报错了? Last_IO_Error: Fatal error: The sla ...

  2. "Last_IO_Error: Fatal error: The slave I/O thread stops because master and slave have equal MySQL server UUIDs

    最近在部署MySQL主从复制架构的时候,碰到了"Last_IO_Error: Fatal error: The slave I/O thread stops because master a ...

  3. 配置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 ha ...

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

    Fatal error: Call to undefined method Fxp\Composer\AssetPlugin\Package\Version\V ersionParser::parse ...

  5. innobackupex: fatal error: no ‘innodb_buffer_pool_filename’解决方法

    http://www.ttlsa.com/mysql/innobackupex-1-5-1-fatal-error-no-innodb_buffer_pool_filename/

  6. 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...

    在搭建Mysql主从架构过程中,由于从服务器是克隆的主服务器系统,导致主从mysql uuid相同, Slave_IO无法启动,报错如下: The slave I/O thread stops bec ...

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

    https://blog.csdn.net/cug_jiang126com/article/details/46846031

  8. asp.net core 2.2 生产环境直接更新View页面并立即生效

    有的时候我们会直接在生产环境上更新页面文件,比如更改了JS代码,CSS代码或页面的文案,布局等.这种没有改到后台代码的情况一般就是直接发布页面文件了,在asp.net core 2.2以前的版本(没有 ...

  9. caffe编译环境的错误:..build_release/src/caffe/proto/caffe.pb.h:23:35: fatal error: google/protobuf/arena.h: 没有那个文件

    在搭建caffe的环境时出现错误: .build_release/src/caffe/proto/caffe.pb.h:23:35: fatal error: google/protobuf/aren ...

随机推荐

  1. Replace - with an en dash character (–, –) ?

    这个安卓开发过程中eclipse的提示,新浪网友给出这个解决方法:http://blog.sina.com.cn/s/blog_5ea8670101015dgk.html  太笨了. 看看stacko ...

  2. [ACM] hdu 4418 Time travel (高斯消元求期望)

    Time travel Problem Description Agent K is one of the greatest agents in a secret organization calle ...

  3. 约瑟夫问题--list模拟循环链表

    约瑟夫问题 Time Limit: 1000ms   Memory limit: 65536K  有疑问?点这里^_^ 题目描写叙述 n个人想玩残酷的死亡游戏,游戏规则例如以下: n个人进行编号,分别 ...

  4. HdU 4046 Panda 段树

    链接:http://acm.hdu.edu.cn/showproblem.php?pid=4046 意甲冠军:到了bw组成的长度为n的字符串(n<=50000).有m次操作(m<=1000 ...

  5. 新版SDK自己主动加入PlaceholderFragment的思考

    自从Android SDK更新到22.6.3,发现新建Activity的时候,会自己主动生成一个Fragment.这个Fragment是activity的静态内部类.同一时候生成了一个xml叫frag ...

  6. prepareCall()运行存储过程

    CallableStatement 对象为全部的 DBMS 提供了一种以标准形式调用已储存过程的方法.已储存过程储存在数据库中.对已储存过程的调用是 CallableStatement对象所含的内容. ...

  7. PHP实现栈(Stack)数据结构

    栈(Stack),是一种特殊的后进先出线性表,其只能在一端进行插入(插入一般称为压栈.进栈或入栈)和删除(删除一般称为弹栈.退栈或出栈)操作,允许进行插入和删除操作的一端称为栈顶,另一端则称为栈底.栈 ...

  8. Linux查看进程线程个数

    1.根据进程号进行查询: # pstree -p 进程号 # top -Hp 进程号 2.根据进程名字进行查询: # pstree -p `ps -e | grep server | awk '{pr ...

  9. HDU2647-Reward(拓扑排序)

    Reward Time Limit: 2000/1000 MS (Java/Others)    Memory Limit: 32768/32768 K (Java/Others) Total Sub ...

  10. iOS Dev (59) 高度自适应的UITextView

    iOS Dev (59) 高度自适应的UITextView 作者:阿锐 地址:http://blog.csdn.net/prevention - 例如以下 _inputTextView 为一个 UIT ...