首页 / MYSQL / 使用xtrabackup实现MySQL主从复制_MySQL

使用xtrabackup实现MySQL主从复制_MySQL

内容导读

互联网集市收集整理的这篇技术教程文章主要介绍了使用xtrabackup实现MySQL主从复制_MySQL，小编现在分享给大家，供广大互联网技能从业者学习和参考。文章包含18026字，纯文字阅读大概需要26分钟。

内容图文

环境描述

主从环境
项目	Master	Slave
OS版本	SuSE 11sp1 x86_64	SuSE 11sp1 x86_64
MySQL版本	官方版本5.5.37	官方版本5.5.37
hostname	NDMC74	NDMC75
IP	192.168.223.132	192.168.223.133
PORT	3306	3306
server-id	1323306	1333306
参数文件	/etc/my.cnf	/etc/my.cnf
DATADIR	/data/mysql/mysql3306/data	/data/mysql/mysql3306/data

主从库相关配置确认

（1）server-id配置

Master节点：

NDMC74:~ # mysql -S /tmp/mysql.sock -e "show global variables like 'server_id';"

+---------------+---------+

| Variable_name | Value |

+---------------+---------+

| server_id | 1323306 |

+---------------+---------+

Slaver节点：

NDMC75:~ # mysql -S /tmp/mysql.sock -e "show global variables like 'server_id';"

+---------------+---------+

| Variable_name | Value |

+---------------+---------+

| server_id | 1333306 |

+---------------+---------+

（2）确认binlog是否开启

NDMC74:~ # mysql -S /tmp/mysql.sock -e "show global variables like 'log_bin';"

+---------------+-------+

| Variable_name | Value |

+---------------+-------+

| log_bin | ON |

+---------------+-------+

Master上使用xtrabackup做全库备份

NDMC74:~ # innobackupex --defaults-file=/etc/my.cnf /data/backup/innobackupex

This software is published under

the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:

http://www.percona.com/xb/p

140731 11:20:44 innobackupex: Connecting to MySQL server with DSN 'dbi:mysql:;mysql_read_default_file=/etc/my.cnf;mysql_read_default_group=xtrabackup' (using password: NO).

140731 11:20:44 innobackupex: Connected to MySQL server

140731 11:20:44 innobackupex: Executing a version check against the server...

140731 11:20:44 innobackupex: Done.

IMPORTANT: Please check that the backup run completes successfully.

At the end of a successful backup run innobackupex

prints "completed OK!".

innobackupex: Using mysql server version 5.5.37-log

innobackupex: Created backup directory /data/backup/innobackupex/2014-07-31_11-20-44

140731 11:20:44 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/etc/my.cnf" --defaults-group="mysqld" --backup --suspend-at-end --target-dir=/data/backup/innobackupex/2014-07-31_11-20-44 --tmpdir=/tmp --extra-lsndir='/tmp'

innobackupex: Waiting for ibbackup (pid=25767) to suspend

innobackupex: Suspend file '/data/backup/innobackupex/2014-07-31_11-20-44/xtrabackup_suspended_2'

xtrabackup version 2.2.3 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )

xtrabackup: uses posix_fadvise().

xtrabackup: cd to /data/mysql/mysql3306/data

xtrabackup: open files limit requested 8192, set to 8192

xtrabackup: using the following InnoDB configuration:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 3

xtrabackup: innodb_log_file_size = 268435456

>> log scanned up to (6118588398)

[01] Copying ./ibdata1 to /data/backup/innobackupex/2014-07-31_11-20-44/ibdata1

>> log scanned up to (6118588398)

[01] ...done

[01] Copying ./test/tt.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/test/tt.ibd

[01] ...done

[01] Copying ./tp50/warehouse.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/warehouse.ibd

[01] ...done

[01] Copying ./tp50/item.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/item.ibd

[01] ...done

>> log scanned up to (6118588398)

[01] Copying ./tp50/district.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/district.ibd

[01] ...done

[01] Copying ./tp50/customer.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/customer.ibd

>> log scanned up to (6118588398)

[01] ...done

[01] Copying ./tp50/history.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/history.ibd

>> log scanned up to (6118588398)

[01] ...done

[01] Copying ./tp50/new_orders.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/new_orders.ibd

[01] ...done

[01] Copying ./tp50/orders.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/orders.ibd

>> log scanned up to (6118588398)

[01] ...done

[01] Copying ./tp50/order_line.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/order_line.ibd

>> log scanned up to (6118588398)

[01] ...done

[01] Copying ./tp50/stock.ibd to /data/backup/innobackupex/2014-07-31_11-20-44/tp50/stock.ibd

>> log scanned up to (6118588398)

[01] ...done

>> log scanned up to (6118588398)

xtrabackup: Creating suspend file '/data/backup/innobackupex/2014-07-31_11-20-44/xtrabackup_suspended_2' with pid '25767'

140731 11:22:07 innobackupex: Continuing after ibbackup has suspended

140731 11:22:07 innobackupex: Executing FLUSH TABLES WITH READ LOCK...

140731 11:22:07 innobackupex: All tables locked and flushed to disk

140731 11:22:07 innobackupex: Starting to backup non-InnoDB tables and files

innobackupex: in subdirectories of '/data/mysql/mysql3306/data'

innobackupex: Backing up files '/data/mysql/mysql3306/data/mysql/*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (72 files)

>> log scanned up to (6118588398)

innobackupex: Backing up file '/data/mysql/mysql3306/data/test/tt.frm'

innobackupex: Backing up file '/data/mysql/mysql3306/data/test/v1.frm'

innobackupex: Backing up file '/data/mysql/mysql3306/data/test/v2.frm'

innobackupex: Backing up file '/data/mysql/mysql3306/data/test/v3.frm'

innobackupex: Backing up files '/data/mysql/mysql3306/data/performance_schema/*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (18 files)

innobackupex: Backing up files '/data/mysql/mysql3306/data/tp50/*.{frm,isl,MYD,MYI,MAD,MAI,MRG,TRG,TRN,ARM,ARZ,CSM,CSV,opt,par}' (10 files)

140731 11:22:08 innobackupex: Finished backing up non-InnoDB tables and files

140731 11:22:08 innobackupex: Executing FLUSH ENGINE LOGS...

140731 11:22:08 innobackupex: Waiting for log copying to finish

xtrabackup: The latest check point (for incremental): '6118588398'

xtrabackup: Stopping log copying thread.

.>> log scanned up to (6118588398)

xtrabackup: Creating suspend file '/data/backup/innobackupex/2014-07-31_11-20-44/xtrabackup_log_copied' with pid '25767'

xtrabackup: Transaction log of lsn (6118588398) to (6118588398) was copied.

140731 11:22:09 innobackupex: All tables unlocked

innobackupex: Backup created in directory '/data/backup/innobackupex/2014-07-31_11-20-44'

innobackupex: MySQL binlog position: filename 'mysql-bin.000009', position 376

140731 11:22:09 innobackupex: Connection to database server closed

140731 11:22:09 innobackupex: completed OK!

NDMC74:~ #

NDMC74:/data/backup/innobackupex/2014-07-31_11-20-44 # ls -l

总计 1048608

-rw-r--r-- 1 root root 357 07-31 11:20 backup-my.cnf

-rw-r----- 1 root root 1073741824 07-31 11:20 ibdata1

drwxr-xr-x 2 root root 4096 07-31 11:22 mysql

drwxr-xr-x 2 root root 4096 07-31 11:22 performance_schema

drwx------ 2 root root 71 07-31 11:22 test

drwx------ 2 root root 4096 07-31 11:22 tp50

-rw-r--r-- 1 root root 23 07-31 11:22 xtrabackup_binlog_info

-rw-r----- 1 root root 95 07-31 11:22 xtrabackup_checkpoints

-rw-r--r-- 1 root root 572 07-31 11:22 xtrabackup_info

-rw-r----- 1 root root 2560 07-31 11:22 xtrabackup_logfile

为了保证备份集中的数据一致，需要操作：

NDMC74:~ # innobackupex --apply-log /data/backup/innobackupex/2014-07-31_11-20-44

This software is published under

the GNU GENERAL PUBLIC LICENSE Version 2, June 1991.

Get the latest version of Percona XtraBackup, documentation, and help resources:

http://www.percona.com/xb/p

IMPORTANT: Please check that the apply-log run completes successfully.

At the end of a successful apply-log run innobackupex

prints "completed OK!".

140731 11:28:16 innobackupex: Starting ibbackup with command: xtrabackup --defaults-file="/data/backup/innobackupex/2014-07-31_11-20-44/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/data/backup/innobackupex/2014-07-31_11-20-44 --tmpdir=/tmp

xtrabackup version 2.2.3 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )

xtrabackup: cd to /data/backup/innobackupex/2014-07-31_11-20-44

xtrabackup: This target seems to be not prepared yet.

xtrabackup: xtrabackup_logfile detected: size=2097152, start_lsn=(6118588398)

xtrabackup: using the following InnoDB configuration for recovery:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 1

xtrabackup: innodb_log_file_size = 2097152

xtrabackup: using the following InnoDB configuration for recovery:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 1

xtrabackup: innodb_log_file_size = 2097152

xtrabackup: Starting InnoDB instance for recovery.

xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)

InnoDB: Using atomics to ref count buffer pool pages

InnoDB: The InnoDB memory heap is disabled

InnoDB: Mutexes and rw_locks use GCC atomic builtins

InnoDB: Compressed tables use zlib 1.2.3

InnoDB: Using CPU crc32 instructions

InnoDB: Initializing buffer pool, size = 100.0M

InnoDB: Completed initialization of buffer pool

InnoDB: Highest supported file format is Barracuda.

InnoDB: 128 rollback segment(s) are active.

InnoDB: Waiting for purge to start

InnoDB: 5.6.17 started; log sequence number 6118588398

[notice (again)]

If you use binary log and don't use any hack of group commit,

the binary log position seems to be:

InnoDB: Last MySQL binlog file position 0 324258362, file name ./mysql-bin.000008

xtrabackup: starting shutdown with innodb_fast_shutdown = 1

InnoDB: FTS optimize thread exiting.

InnoDB: Starting shutdown...

InnoDB: Shutdown completed; log sequence number 6118588408

140731 11:28:18 innobackupex: Restarting xtrabackup with command: xtrabackup --defaults-file="/data/backup/innobackupex/2014-07-31_11-20-44/backup-my.cnf" --defaults-group="mysqld" --prepare --target-dir=/data/backup/innobackupex/2014-07-31_11-20-44 --tmpdir=/tmp

for creating ib_logfile*

xtrabackup version 2.2.3 based on MySQL server 5.6.17 Linux (x86_64) (revision id: )

xtrabackup: cd to /data/backup/innobackupex/2014-07-31_11-20-44

xtrabackup: This target seems to be already prepared.

xtrabackup: notice: xtrabackup_logfile was already used to '--prepare'.

xtrabackup: using the following InnoDB configuration for recovery:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 3

xtrabackup: innodb_log_file_size = 268435456

xtrabackup: using the following InnoDB configuration for recovery:

xtrabackup: innodb_data_home_dir = ./

xtrabackup: innodb_data_file_path = ibdata1:1G:autoextend

xtrabackup: innodb_log_group_home_dir = ./

xtrabackup: innodb_log_files_in_group = 3

xtrabackup: innodb_log_file_size = 268435456

xtrabackup: Starting InnoDB instance for recovery.

xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)

InnoDB: Using atomics to ref count buffer pool pages

InnoDB: The InnoDB memory heap is disabled

InnoDB: Mutexes and rw_locks use GCC atomic builtins

InnoDB: Compressed tables use zlib 1.2.3

InnoDB: Using CPU crc32 instructions

InnoDB: Initializing buffer pool, size = 100.0M

InnoDB: Completed initialization of buffer pool

InnoDB: Setting log file ./ib_logfile101 size to 256 MB

InnoDB: Progress in MB: 100 200

InnoDB: Setting log file ./ib_logfile1 size to 256 MB

InnoDB: Progress in MB: 100 200

InnoDB: Setting log file ./ib_logfile2 size to 256 MB

InnoDB: Progress in MB: 100 200

InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0

InnoDB: New log files created, LSN=6118588408

InnoDB: Highest supported file format is Barracuda.

InnoDB: 128 rollback segment(s) are active.

InnoDB: Waiting for purge to start

InnoDB: 5.6.17 started; log sequence number 6118588428

[notice (again)]

If you use binary log and don't use any hack of group commit,

the binary log position seems to be:

InnoDB: Last MySQL binlog file position 0 324258362, file name ./mysql-bin.000008

xtrabackup: starting shutdown with innodb_fast_shutdown = 1

InnoDB: FTS optimize thread exiting.

InnoDB: Starting shutdown...

InnoDB: Shutdown completed; log sequence number 6118588438

140731 11:28:26 innobackupex: completed OK!

NDMC74:~ #

Master上创建同步账号并授权REPLICATION

mysql> CREATE USER 'repl'@'192.168.223.%' IDENTIFIED BY 'replpass';

Query OK, 0 rows affected (0.02 sec)

mysql> GRANT REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'repl'@'192.168.223.%';

Query OK, 0 rows affected (0.02 sec)

然后在Slave上测试，看看能否使用repl用户登录Master服务器：

NDMC75:~ # mysql -h192.168.223.132 -urepl -preplpass

mysql> show grants\G

*************************** 1. row ***************************

Grants for repl@192.168.223.%: GRANT REPLICATION SLAVE, REPLICATION CLIENT ON *.* TO 'repl'@'192.168.223.%' IDENTIFIED BY PASSWORD '*D98280F03D0F78162EBDBB9C883FC01395DEA2BF'

1 row in set (0.00 sec)

将Master的全备scp到Slave主机上

NDMC74:~ # cd /data/backup/innobackupex/

NDMC74:/data/backup/innobackupex # scp -r ./2014-07-31_11-20-44 192.168.223.133:/data/backup

将Slave上的MySQL停掉，然后将Master的备份文件放到Slave的datadir目录下：

NDMC75:~ # mv /data/backup/2014-07-31_11-20-44 /data/mysql/mysql3306/data

NDMC75:~ # cd /data/mysql/mysql3306

NDMC75:/data/mysql/mysql3306 # chown -R mysql:mysql data

注意：Slave的my.cnf文件和Master的一样，只是修改一下server-id即可。

启动Slave数据库

NDMC75:~ # /usr/local/mysql/bin/mysqld --defaults-file=/etc/my.cnf &

NDMC75:~ # ps -ef |grep mysqld

mysql 1293 1 1 11:50 pts/0 00:00:01 /usr/local/mysql/bin/mysqld --defaults-file=/etc/my.cnf

root 3124 19598 0 11:51 pts/0 00:00:00 grep mysqld

同时查看一下error.log文件，看看有没有错误信息。

在slave上执行change master设置主服务器复制信息

Master binlog信息从备份文件中可以获得：

NDMC74:~ # cd /data/backup/innobackupex/2014-07-31_11-20-44

NDMC74:~ # cat xtrabackup_binlog_info

mysql-bin.000009 376

mysql> change master to master_host='192.168.223.132', master_user='repl', master_password='replpass',master_port=3306,master_log_file='mysql-bin.000009',master_log_pos=376;

Query OK, 0 rows affected (0.05 sec)

在slave上启动复制

mysql> start slave;

Query OK, 0 rows affected (0.00 sec)

检查主从复制是否正常

mysql> show slave status\G

*************************** 1. row ***************************

Slave_IO_State: Waiting for master to send event

Master_Host: 192.168.223.132

Master_User: repl

Master_Port: 3306

Connect_Retry: 60

Master_Log_File: mysql-bin.000009

Read_Master_Log_Pos: 452

Relay_Log_File: mysql-relay-bin.000002

Relay_Log_Pos: 329

Relay_Master_Log_File: mysql-bin.000009

Slave_IO_Running: Yes

Slave_SQL_Running: Yes

Replicate_Do_DB:

Replicate_Ignore_DB:

Replicate_Do_Table:

Replicate_Ignore_Table:

Replicate_Wild_Do_Table:

Replicate_Wild_Ignore_Table:

Last_Errno: 0

Last_Error:

Skip_Counter: 0

Exec_Master_Log_Pos: 452

Relay_Log_Space: 485

Until_Condition: None

Until_Log_File:

Until_Log_Pos: 0

Master_SSL_Allowed: No

Master_SSL_CA_File:

Master_SSL_CA_Path:

Master_SSL_Cert:

Master_SSL_Cipher:

Master_SSL_Key:

Seconds_Behind_Master: 0

Master_SSL_Verify_Server_Cert: No

Last_IO_Errno: 0

Last_IO_Error:

Last_SQL_Errno: 0

Last_SQL_Error:

Replicate_Ignore_Server_Ids:

Master_Server_Id: 1323306

1 row in set (0.00 sec)

内容总结

以上是互联网集市为您收集整理的使用xtrabackup实现MySQL主从复制_MySQL全部内容，希望文章能够帮你解决使用xtrabackup实现MySQL主从复制_MySQL所遇到的程序开发问题。如果觉得互联网集市技术教程内容还不错，欢迎将互联网集市网站推荐给程序员好友。

内容备注

版权声明：本文内容由互联网用户自发贡献，该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务，不拥有所有权，不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容，请发送邮件至 gblab@vip.qq.com 举报，一经查实，本站将立刻删除。

内容手机端

扫描二维码推送至手机访问。

本文链接：https://qyyshop.com/info/579429.html

来源：【匿名】

【上一篇】Mysql----浅入浅出之视图、存储过程、触发器_MySQL 【下一篇】用IE远程创建Mysql数据库的简易程序

更多 ►

【使用xtrabackup实现MySQL主从复制_MySQL】教程文章相关的互联网学习教程文章

使用Xtrabackup进行MySQL备份：

使用Xtrabackup进行MySQL备份：一、安装1、简介Xtrabackup是由percona提供的mysql数据库备份工具，据官方介绍，这也是世界上惟一一款开源的能够对innodb和xtradb数据库进行热备的工具。特点：(1)备份过程快速、可靠；(2)备份过程不会打断正在执行的事务；(3)能够基于压缩等功能节约磁盘空间和流量；(4)自动实现备份检验；(5)还原速度快；2、安装其最新版的软件可从 http://www.percona.com/software/percona-xtrabackup/ 获得。本文...

MySQL 採用Xtrabackup对数据库进行全库备份【图】

1，xtrabackup简单介绍关于数据库备份以及备份工具。參考：http://blog.itpub.net/26230597/viewspace-1460065/，这里来介绍xtrabackup已经怎样使用xtrabackup进行对数据库的全备份已经恢复。 2，xtrabackup下载下载地址为：http://www.percona.com/downloads/XtraBackup/Chorm浏览器以下。在“DOWNLOADPERCONA XTRABACKUP”以下，选择版本号号以及os版本号。有的浏览器打不开，可能会出现“No files found with current filters.”...

Percona Xtrabackup备份mysql (完整备份与增量备份)

Percona Xtrabackup备份mysql (完整备份与增量备份)Xtrabackup简介Percona XtraBackup是开源免费的MySQL数据库热备份软件，它能对InnoDB和XtraDB存储引擎的数据库非阻塞地备份（对于MyISAM的备份同样需要加表锁）。XtraBackup支持所有的Percona Server、MySQL、MariaDB和Drizzle。XtraBackup优势：1、无需停止数据库进行InnoDB热备2、增量备份MySQL3、流压缩到传输到其它服务器4、能比较容易地创建主从同步5、备份MySQL时不会增大...

如何用Percona XtraBackup进行MySQL从库的单表备份和恢复【转】【代码】

前提应该确定采用的是单表一个表空间，否则不支持单表的备份与恢复。在配置文件里边的mysqld段加上innodb_file_per_table = 1 环境说明：主库:192.168.0.1 从库1:192.168.0.2 从库2:192.168.0.3 备份工具 : Percona xtrabackup version 2.4.8 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 97330f7) 在主库上创建chenfeng库:mysql> create database chenfeng; Query OK, 1 row affected (0.08 sec)mysql> use che...

MySQL--Percona-XtraDB-Cluster使用xtrabackup来添加节点【代码】【图】

虽然PXC支持在线增加群集节点，但是目前尚未解决wsrep_sst_method=xtrabackup 或wsrep_sst_method=mysqldump时报错的问题，因此尝试手动完成xtrabackup备份和恢复并添加到群集节点。场景：有三台干净的CentOS 6的服务器，IP配置为：192.168.166.169,192.168.166.170,192.168.166.171，准备搭建三节点的Percona XtraDB Cluster，目前192.168.166.169,192.168.166.170已加入到群集，准备将192.168.166.171加入到群集中。192.168.166....

Mysql中-Xtrabackup备份和恢复应用【代码】【图】

关于Xtrabackup(又或innobackupex)的介绍，详细参考官方文档Xtrabackup安装指南文件准备[root@wuxiang11 ~]# cd percona-xtrabackup/ [root@wuxiang11 percona-xtrabackup]# ls libev-4.15-1.el6.rf.x86_64.rpm percona-release-0.1-4.noarch.rpm percona-xtrabackup-24-2.4.4-1.el7.x86_64.rpm开始安装依赖文件[root@wuxiang11 percona-xtrabackup]# rpm -ivh libev-4.15-1.el6.rf.x86_64.rpm warning: libev-4.15-1.el6.rf.x8...

mysql备份与恢复 mysqldump+binlog xtrabackup【代码】

数据备份的方式：物理备份：拷贝存放库和表文件的目录 cp tar 逻辑备份：备份创建库和表插入记录时的sql语句数据备份策略：完整备份：备份数据库服务器上的所有库、所有表。差异备份：备份自完整备份后，生成的新数据。增量备份：备份自上一次备份后，生成的新数据。完整备份+差异备份完整备份+增量备份mysqldump 做完整备份 mysqldump -hser_ip -uusername -ppassword 数据名 > 目录/x.sql ...

使用Xtrabackup进行MySQL备份【代码】

一、安装1、简介Xtrabackup是由percona提供的mysql数据库备份工具，据官方介绍，这也是世界上惟一一款开源的能够对innodb和xtradb数据库进行热备的工具。特点：(1)备份过程快速、可靠； (2)备份过程不会打断正在执行的事务； (3)能够基于压缩等功能节约磁盘空间和流量； (4)自动实现备份检验； (5)还原速度快；2、安装其最新版的软件可从 http://www.percona.com/software/percona-xtrabackup/ 获得。本文基于CentOS7.2的系统，因此...

Mysql 备份恢复与xtrabackup备份【代码】【图】

??新年贺词??　　2017年即将过去，新年的钟声即将敲响。在这辞旧迎新的美好时刻，我向全国各族人民，向香港特别行政区同胞、澳门特别行政区同胞，向台湾同胞和海外侨胞，向工作在一线的运维工程师们，向为开源事业做出贡献的朋友们，向世界各国各地区的朋友们，致以新年的祝福！　　今天是2017的最后一天，在这样一个特殊的日子里，希望大家都能事事顺心，快乐常在，希望在2018年里都能有所成就，创造不一样的价值。　　让我们满怀...

使用binlog日志， XtraBackup备份工具，MySQL AB复制

[mysqld] .. .. log-bin-index=mysql-bin //启用二进制日志，并指定前缀 server_id=1 binlog_format=STATEMENT //在Mysql5.7中，binlog日志格式默认为ROW，但它不记录sql语句上下文相关信息。需要将binlog日志格式修改为STATEMENT .. .. [root@dbsvr1 ~]# systemctl restart mysqld.service2）确认binlog日志文件新启用binlog后，每次启动MySQl服务都会新生成一份日志文件： [root@dbsvr1 ~]# ls /va...

关于通过linux crontab+xtrabackup自动化备份mysql数据的说明【代码】【图】

解决方法1： ln -s /usr/local/mysql/bin/mysql/usr/bin/mysql解决办法2：在备份脚本中引入环境变量source /etc/profile本文出自 “凡夫俗子” 博客，请务必保留此出处http://caoyt.blog.51cto.com/9978141/1653876关于通过linux crontab+xtrabackup自动化备份mysql数据的说明标签：linux定时任务自动备份mysql本文系统来源：http://caoyt.blog.51cto.com/9978141/1653876

MySQL备份恢复工具xtrabackup

XtraBackup是Percona提供的一个开源的、免费的MySQL数据库备份工具，它能够对InnoDB和XtraDB数据库进行热备份，据官方介绍，XtraBackup具有以下特点： 1. 备份过程快速、可靠； 2. 备份过程不会打断正在执行的事务； 3. 能够基于压缩等功能节约磁盘空间和流量； 4. 自动实现备份检验； 5. 恢复速度快。2、安装XtraBackup最新版本可以从https://www.percona.com/software/percona-xtrabackup获得。# yum install htt...

xtrabackup 链接不上MySQL的问题

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oyand Percona LLC and/or its affiliates 2009-2013. All Rights Reserved. This software is published underthe GNU GENERAL PUBLIC LICENSE Version 2, June 1991. Get the latest version of Percona XtraBackup, documentation, and help resources:http://www.percona.com/xb/p 150712 22:29:59 innobackupex: Executing a version check agains...

mysql5.6利用xtrabackup全备及增量备份【图】

[root@local-db opt]# innobackupex --defaults-file=/etc/my.cnf --user=root --password=123456 /bak/mysql/该语句将拷贝数据文件（由my.cnf里的变量datadir指定）至备份目录下（/bak/mysql/），注意：如果不指定--defaults-file，默认值为/etc/my.cnf。备份成功后，将在备份目录下创建一个时间戳目录（本例创建的目录为/bak/mysql/2015-07-08_18-52-43），在该目录下存放备份文件。（2）恢复删除数据库test123，尝试恢复恢复之...

每天进步一点点——mysql——Percona XtraBackup（innobackupex）

XtraBackup后，其实会有几个工具： innobackupex：这个是其实是下面三个工具的一个perl脚本封装，可以备份MyISAM, InnoDB, XtraDB表。 xtrabackup：一个由C编译而来的二进制文件，只能备份InnoDB和XtraDB数据。 xbcrypt：用来加密或解密备份的数据。 xbstream：用来解压或压缩xbstream格式的压缩文件。建议使用perl封装的innobackupex来作数据库备份，因为比较容易使用。所以下面只介绍innobackupex的使用。其它的使用参考：h...

MYSQL - 技术教程分类

MySQL 教程 MySQL 安装 MySQL 管理 MySQL PHP 语法 MySQL 连接 MySQL 创建数据库 MySQL 删除数据库 MySQL 选择数据库 MySQL 数据类型 MySQL 创建数据表 MySQL 删除数据表 MySQL 插入数据 MySQL 查询数据 MySQL WHERE 子句 MySQL UPDATE 更新 MySQL DELETE 语句 MySQL LIKE 子句 MySQL UNION MySQL 排序 MySQL 分组 MySQL 连接的使用 MySQL NULL 值处理 MySQL 事务 MySQL ALTER命令 MySQL 索引 MySQL 临时表 MySQL 复制表 MySQL 元数据 MySQL 序列使用 MySQL 处理重复数据 MySQL 及 SQL 注入 MySQL 导出数据 MySQL 导入数据 MySQL 函数 MySQL 运算符 mysql 全部

MYSQL - 最热教程

sql分组取最大记录方法 mysql如何设置默认值 mysql创建数据表时指定默认值教程 MySQL 5.7 的初始化操作（root初始密码...Oracle中合并数据集(多行变一行)mysql 相同内容的字段合并为一条的方法解决mysql设置时区时的错误Unknown or ...解决ubuntu下mysql的'Access denied fo...ubuntu系统中MysqlERROR1045(28000)报错...mysql数据库设置不区分大小写

首页 / MYSQL / 使用xtrabackup实现MySQL主从复制_MySQL

使用xtrabackup实现MySQL主从复制_MySQL

内容导读

内容图文

内容总结

内容备注

内容手机端

【使用xtrabackup实现MySQL主从复制_MySQL】教程文章相关的互联网学习教程文章

使用Xtrabackup进行MySQL备份：

MySQL 採用Xtrabackup对数据库进行全库备份【图】

Percona Xtrabackup备份mysql (完整备份与增量备份)

如何用Percona XtraBackup进行MySQL从库的单表备份和恢复【转】【代码】

MySQL--Percona-XtraDB-Cluster使用xtrabackup来添加节点【代码】【图】

Mysql中-Xtrabackup备份和恢复应用【代码】【图】

mysql备份与恢复 mysqldump+binlog xtrabackup【代码】

使用Xtrabackup进行MySQL备份【代码】

Mysql 备份恢复与xtrabackup备份【代码】【图】

使用binlog日志， XtraBackup备份工具，MySQL AB复制

关于通过linux crontab+xtrabackup自动化备份mysql数据的说明【代码】【图】

MySQL备份恢复工具xtrabackup

xtrabackup 链接不上MySQL的问题

mysql5.6利用xtrabackup全备及增量备份【图】

每天进步一点点——mysql——Percona XtraBackup（innobackupex）

MYSQL - 相关标签

TR - 相关标签

MYSQL - 技术教程分类

MYSQL - 最新教程

MYSQL - 最热教程