数据库备份概述
数据备份方式
- 物理备份
冷备:cp、tar、… - 逻辑备份
- mysqldump
- mysql
数据备份策略
- 完全备份
备份所有数据 - 增量备份
备份上一次备份后,所有新产生的数据 - 差异备份
备份完全备份后,所有新产生的数据
物理备份
物理备份及恢复
- 备份操作
- cp -rp /var/lib/mysql/数据库 备份目录/文件名
- tar -zcvf xxx.tar.gz /var/lib/mysql/数据库/*
- 恢复操作
- cp -rp 备份目录/文件名 /var/lib/mysql/
- tar -zxvf xxx.tar.gz -C /var/lib/mysql/数据库名/
注意事项
物理备份,一定要把整个数据库目录备份下来
逻辑备份
逻辑备份及恢复
- 备份操作
mysqldump -uroot -p密码 库名 > 路径/xxx.sql - 恢复操作
mysql -uroot -p密码 库名 < 路径/xxx.sql
库名标示方式
- –all-databases 或者 -A //所有库
- 数据库名 //单个库
- 数据库名 表名 //单张表
- -B 数据库1 数据库2 //多个库
注意方式
- 无论备份还是恢复,都要验证用户权限
mysqldump备份与恢复
一:使用mysqldump进行逻辑备份
(1)备份MySQL服务器上的所有库
将所有的库备份为mysql-all.sql文件:
[root@dbsvr1 ~]# mysqldump -u root -p --all-databases > /root/alldb.sql
Enter password: //验证口令
[root@dbsvr1 mysql]# file /root/alldb.sql //确认备份文件类型
/root/alldb.sql: UTF-8 Unicode English text, with very long lines
查看备份文件alldb.sql的部分内容:
[root@dbsvr1 ~]# grep -vE '^/|^-|^$' /root/alldb.sql | head -15
CREATE DATABASE /*!32312 IF NOT EXISTS*/ `home` /*!40100 DEFAULT CHARACTER SET latin1 */;
USE `home`;
DROP TABLE IF EXISTS `biao01`;
CREATE TABLE `biao01` (
`id` int(2) NOT NULL,
`name` varchar(8) DEFAULT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
LOCK TABLES `biao01` WRITE;
UNLOCK TABLES;
DROP TABLE IF EXISTS `biao02`;
CREATE TABLE `biao02` (
`id` int(4) NOT NULL,
`name` varchar(8) DEFAULT NULL,
PRIMARY KEY (`id`)
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
.. ..
注意:若数据库都使用MyISAM存储引擎,可以采用冷备份的方式,直接复制对应的数据库目录即可;恢复时重新复制回来就行。
(2)只备份指定的某一个库
将userdb库备份为userdb.sql文件:
[root@dbsvr1 ~]# mysqldump -u root -p userdb > userdb.sql
Enter password: //验证口令
查看备份文件userdb.sql的部分内容:
[root@dbsvr1 ~]# grep -vE '^/|^-|^$' /root/userdb.sql
DROP TABLE IF EXISTS `stu_info`;
CREATE TABLE `stu_info` (
`name` varchar(12) NOT NULL,
`gender` enum('boy','girl') DEFAULT 'boy',
`age` int(3) NOT NULL
) ENGINE=InnoDB DEFAULT CHARSET=latin1;
LOCK TABLES `stu_info` WRITE;
.. ..
(3)同时备份指定的多个库
同时备份mysql、userdb库,保存为mysql+userdb.sql文件:
[root@dbsvr1 ~]# mysqldump -u root -p -B mysql userdb > mysql+test+userdb.sql
Enter password: //验证口令
查看备份文件userdb.sql的部分内容:
[root@dbsvr1 ~]# grep '^CREATE DATA' /root/mysql+userdb.sql
CREATE DATABASE /*!32312 IF NOT EXISTS*/ `mysql` /*!40100 DEFAULT CHARACTER SET latin1 */;
CREATE DATABASE /*!32312 IF NOT EXISTS*/ `userdb` /*!40100 DEFAULT CHARACTER SET latin1 */;
注:以上操作备份的时候也可直接指定密码-p:数据库密码
就不需要再次确认输入密码
二:使用mysql命令从备份中恢复数据库、表
以恢复userdb库为例,可参考下列操作。通常不建议直接覆盖旧库,而是采用建立新库并导入逻辑备份的方式执行恢复,待新库正常后即可废弃或删除旧库。
(1)创建名为userdb2的新库
mysql> CREATE DATABASE userdb2;
Query OK, 1 row affected (0.00 sec)
(2)导入备份文件,在新库中重建表及数据
[root@dbsvr1 ~]# mysql -u root -p userdb2 < /root/userdb.sql
Enter password: //验证口令
(3)确认新库正常,启用新库
mysql> USE userdb2; //切换到新库
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
mysql> SELECT sn,username,uid,gid,homedir //查询数据,确认可用
-> FROM userlist LIMIT 10;
+----+----------+-----+-----+-----------------+
| sn | username | uid | gid | homedir |
+----+----------+-----+-----+-----------------+
| 1 | root | 0 | 0 | /root |
| 2 | bin | 1 | 1 | /bin |
| 3 | daemon | 2 | 2 | /sbin |
| 4 | adm | 3 | 4 | /var/adm |
| 5 | lp | 4 | 7 | /var/spool/lpd |
| 6 | sync | 5 | 0 | /sbin |
| 7 | shutdown | 6 | 0 | /sbin |
| 8 | halt | 7 | 0 | /sbin |
| 9 | mail | 8 | 12 | /var/spool/mail |
| 10 | operator | 11 | 0 | /root |
+----+----------+-----+-----+-----------------+
10 rows in set (0.00 sec)
(4)废弃或删除旧库
mysql> DROP DATABASE userdb;
Query OK, 2 rows affected (0.09 sec)
其他操作与内容补充:
(1)
//备份50上的所有库
[root@ip50 ~]# mysqldump -uroot -p123456 -A > /mysql.bak/mysql.sql
//将备份文件发到52主机上,恢复数据库
[root@ip52 ~]# mysql -uroot -p123456 < /root/mysql.sql
(2)
//备份50上的db1库
[root@ip50 ~]# mysqldump -uroot -p123456 db1 > /mysql.bak/db1.sql
//将备份文件发到52主机上,如果52主机的数据库没有db1库,需要先进去创建db1库,然后出来再创建
[root@ip52 ~]# mysql -uroot -p123456 db1 < /root/db1.sql
(3)
//备份50上的db1库中的user表
[root@ip50 ~]# mysqldump -uroot -p123456 db1 user> /mysql.bak/db1User.sql
//将备份文件发到52主机上恢复备份,如果52主机没有db1库,需要事先创建db1库
[root@ip52 ~]# mysql -uroot -p123456 db1 < /root/db1User.sql
(4)
//备份50上的db1跟db2库
[root@ip50 ~]# mysqldump -uroot -p123456 -B db1 db2 > /mysql.bak/dbtwo.sql
//将备份文件发到52主机上恢复备份,此操作不需要指定库名
[root@ip52 ~]# mysql -uroot -p123456 < /root/dbtwo.sql
使用binlog日志
二进制日志用途及配置方式
类型 | 用途 | 配置 |
---|---|---|
二进制文件 | 记录所有更改数据的操作 | log_bin[=dir/name] server_id=数字 //1~255之间的值都可以 max_binlog_size=数字m //可以控制bin-log日志大于多少之后自动创建新的编号的日志文件(默认是1G) |
启用binlog日志
- 采用binlog日志的好处
- 记录除查询之外的所有的SQL命令,
- 可用于数据恢复
- 配置mysql主从同步的必要条件
mysql> show master status; //显示当前服务器上的binlog日志信息,如果为空,证明服务未启用
启用binlog日志功能
[root@ip50 ~]# vim /etc/my.cnf
[mysqld]
server_id=50
log-bin
... ...
[root@ip50 ~]# systemctl restart mysqld
日志文件在/var/lib/mysql
目录下
- binlog相关文件
主机名-bin.index //记录已有日志文件名
主机名-bin.000001 //第1个二进制文件
主机名-bin.000002 //第2份二进制文件
… …
如果是日志文件未达到限制大小前想重新生成新的日志文件,可以手动操作
手动生成新的日志文件(几种方法):
- 重启mysql服务
systemctl restart mysqld - 执行SQL操作 mysql > flush logs;
//执行完db3库的完全备份后,生成新的日志文件
[root@ip50 ~]# mysqldump -uroot -p123456 --flush-logs db3 > /mysqlbak/db3.sql
-
mysqldump --flush-logs
-
mysql -uroot -p密码 -e ‘flush logs’
[root@ip50 ~]# mysql -uroot -p123456 -e "flush logs"
//在不退出mysql登录界面的情况执行系统命令
mysql> system ls /var/lib/mysql
清理binlog日志
- 删除早于指定版本的binlog日志
purge master logs to “binlog文件名”
mysql> purge master logs to "ip50-bin.000005"; //删除5之前的binlog日志(1~4)
- 删除所有binlog日志,重建新日志
reset master;
自定义日志存储目录及文件名
[root@ip50 ~]# mkdir /mysqlLog
[root@ip50 ~]# chown mysql:mysql /mysqlLog/
[root@ip50 ~]# vim /etc/my.cnf
[mysqld]
server_id=50
log-bin=/mysqlLog/host //host为文件名前缀
通过binlog日志恢复数据
-
使用mysqlbinlog 工具
格式:mysqlbinlog [选项] binlog日志文件名 -
恢复数据格式
mysqlbinlog binlog日志文件 | mysql -uroot -p密码
将50上的binlog文件发送到51主机,通过下面命令还原备份数据
如果51上的数据库没有该日志文件里边记录的对应的数据库跟表,那么51主机需要事先创建好库跟表
[root@ip51 ~]# mysqlbinlog /root/plj.000001 | mysql -uroot -p123456
分析binlog日志
- 查看日志当前记录格式
mysql> show variables like "binlog_format";
三种记录格式:
- statement:每一条修改数据的sql命令都会记录在binlog日志中
- row:不记录sql语句上下文相关信息,仅保存哪条记录被修改
- mixed:是以上两种格式的混合使用
修改日志记录格式
[root@ip50~]# vim /etc/mycnf
... ...
[mysqld]
server_id=50
log-bin=/mysqlLog/plj
binlog_format=mixed //配置为混合模式
... ...
systemctl restart mysqld
查看binlog新的日志,过滤插入数据指令
[root@ip50 ~]# mysqlbinlog /mysqlLog/plj.000002 | grep -i insert
常用选项
- –start-datetime=“yyyy-mm-dd hh:mm:ss”
- –stop-datetime=“yyyy-mm-dd hh:mm:ss”
- –start-position=数字
- –stop-position=数字
[root@ip51 ~]# mysqlbinlog --start-position=293 --stop-position=973 /root/plj.000002 | mysql -uroot -p123456
案例:
利用binlog恢复库表,要求如下:
启用binlog日志
创建db1库tb1表,插入3条记录
删除tb1表中刚插入的3条记录
使用mysqlbinlog恢复删除的3条记录
一:启用binlog日志
(1)调整/etc/my.cnf配置,并重启服务
[root@dbsvr1 ~]# vim /etc/my.cnf
[mysqld]
.. ..
log-bin-index=mysql-bin //启用二进制日志,并指定前缀
server_id=1
binlog_format=STATEMENT
//在Mysql5.7中,binlog日志格式默认为ROW,但它不记录sql语句上下文相关信息。需要将binlog日志格式修改为STATEMENT
.. ..
[root@dbsvr1 ~]# systemctl restart mysqld.service
(2)确认binlog日志文件
新启用binlog后,每次启动MySQl服务都会新生成一份日志文件:
[root@dbsvr1 ~]# ls /var/lib/mysql/mysql-bin.*
/var/lib/mysql/mysql-bin.000001 /var/lib/mysql/mysql-bin.index
其中mysql-bin.index文件记录了当前保持的二进制文件列表:
[root@dbsvr1 ~]# cat /var/lib/mysql/mysql-bin.index
./mysql-bin.000001
重启MySQL服务程序,或者执行SQL操作“FLUSH LOGS;”,会生成一份新的日志:
[root@dbsvr1 ~]# ls /var/lib/mysql/mysql-bin.*
/var/lib/mysql/mysql-bin.000001 /var/lib/mysql/mysql-bin.index
/var/lib/mysql/mysql-bin.000002
[root@dbsvr1 ~]# cat /var/lib/mysql/mysql-bin.index
./mysql-bin.000001
./mysql-bin.000002
二:利用binlog日志重做数据库操作
(1)执行数据库表添加操作
创建db1·库tb1表,表结构自定义:
mysql> CREATE DATABASE db1;
Query OK, 1 row affected (0.05 sec)
mysql> USE db1;
Database changed
mysql> CREATE TABLE tb1(
-> id int(4) NOT NULL,name varchar(24)
-> );
Query OK, 0 rows affected (0.28 sec)
插入3条表记录:
mysql> INSERT INTO tb1 VALUES
-> (1,'Jack'),
-> (2,'Kenthy'),
-> (3,'Bob');
Query OK, 3 rows affected (0.12 sec)
Records: 3 Duplicates: 0 Warnings: 0
确认插入的表记录数据:
mysql> SELECT * FROM tb1;
+----+--------+
| id | name |
+----+--------+
| 1 | Jack |
| 2 | Kenthy |
| 3 | Bob |
+----+--------+
3 rows in set (0.00 sec)
(2)删除前一步添加的3条表记录
执行删除所有表记录操作:
mysql> DELETE FROM tb1;
Query OK, 3 rows affected (0.09 sec)
确认删除结果:
mysql> SELECT * FROM tb1;
Empty set (0.00 sec)
三:通过binlog日志恢复表记录
binlog会记录所有的数据库、表更改操作,所以可在必要的时候重新执行以前做过的一部分数据操作,但对于启用binlog之前已经存在的库、表数据将不适用。
根据上述“恢复被删除的3条表记录”的需求,应通过mysqlbinlog工具查看相关日志文件,找到删除这些表记录的时间点,只要恢复此前的SQL操作(主要是插入那3条记录的操作)即可。
(1)查看mysql-bin.000002日志内容
[root@dbsvr1 ~]# mysqlbinlog /var/lib/mysql/mysql-bin.000002
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=1*/;
/*!50003 SET @OLD_COMPLETION_TYPE=@@COMPLETION_TYPE,COMPLETION_TYPE=0*/;
DELIMITER /*!*/;
# at 4
#170412 12:05:32 server id 1 end_log_pos 123 CRC32 0x6d8c069c Start: binlog v 4, server v 5.7.17-log created 170412 12:05:32 at startup
# Warning: this binlog is either in use or was not closed properly.
ROLLBACK/*!*/;
BINLOG '
jKftWA8BAAAAdwAAAHsAAAABAAQANS43LjE3LWxvZwAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
AAAAAAAAAAAAAAAAAACMp+1YEzgNAAgAEgAEBAQEEgAAXwAEGggAAAAICAgCAAAACgoKKioAEjQA
AZwGjG0=
'/*!*/;
# at 123
#170412 12:05:32 server id 1 end_log_pos 154 CRC32 0x17f50164 Previous-GTIDs
# [empty]
# at 154
#170412 12:05:59 server id 1 end_log_pos 219 CRC32 0x4ba5a976 Anonymous_GTID last_committed=0 sequence_number=1
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 219
#170412 12:05:59 server id 1 end_log_pos 310 CRC32 0x5b66ae13 Query thread_id=3 exec_time=0 error_code=0
SET TIMESTAMP=1491969959/*!*/;
SET @@session.pseudo_thread_id=3/*!*/;
SET @@session.foreign_key_checks=1, @@session.sql_auto_is_null=0, @@session.unique_checks=1, @@session.autocommit=1/*!*/;
SET @@session.sql_mode=1436549152/*!*/;
SET @@session.auto_increment_increment=1, @@session.auto_increment_offset=1/*!*/;
/*!\C utf8 *//*!*/;
SET @@session.character_set_client=33,@@session.collation_connection=33,@@session.collation_server=8/*!*/;
SET @@session.lc_time_names=0/*!*/;
SET @@session.collation_database=DEFAULT/*!*/;
CREATE DATABASE db1
/*!*/;
# at 310
#170412 12:06:23 server id 1 end_log_pos 375 CRC32 0x2967cc28 Anonymous_GTID last_committed=1 sequence_number=2
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 375
#170412 12:06:23 server id 1 end_log_pos 502 CRC32 0x5de09aae Query thread_id=3 exec_time=0 error_code=0
use `db1`/*!*/;
SET TIMESTAMP=1491969983/*!*/;
CREATE TABLE tb1(
id int(4) NOT NULL,name varchar(24)
)
/*!*/;
# at 502
#170412 12:06:55 server id 1 end_log_pos 567 CRC32 0x0b8cd418 Anonymous_GTID last_committed=2 sequence_number=3
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 567
#170412 12:06:55 server id 1 end_log_pos 644 CRC32 0x7e8f2fa0 Query thread_id=3 exec_time=0 error_code=0
SET TIMESTAMP=1491970015/*!*/;
BEGIN
/*!*/;
# at 644
#170412 12:06:55 server id 1 end_log_pos 772 CRC32 0x4e3f728e Query thread_id=3 exec_time=0 error_code=0 //插入表记录的起始时间点
SET TIMESTAMP=1491970015/*!*/;
INSERT INTO tb1 VALUES(1,'Jack'),(2,'Kenthy'), (3,'Bob')
/*!*/;
# at 772
#170412 12:06:55 server id 1 end_log_pos 803 CRC32 0x6138b21f Xid = 10
//确认事务的时间点
COMMIT/*!*/;
# at 803
#170412 12:07:24 server id 1 end_log_pos 868 CRC32 0xbef3f472 Anonymous_GTID last_committed=3 sequence_number=4
SET @@SESSION.GTID_NEXT= 'ANONYMOUS'/*!*/;
# at 868
#170412 12:07:24 server id 1 end_log_pos 945 CRC32 0x5684e92c Query thread_id=3 exec_time=0 error_code=0
SET TIMESTAMP=1491970044/*!*/;
BEGIN
/*!*/;
# at 945
#170412 12:07:24 server id 1 end_log_pos 1032 CRC32 0x4c1c75fc Query thread_id=3 exec_time=0 error_code=0 //删除表记录的时间点
SET TIMESTAMP=1491970044/*!*/;
DELETE FROM tb1
/*!*/;
# at 1032
#170412 12:07:24 server id 1 end_log_pos 1063 CRC32 0xccf549b2 Xid = 12
COMMIT/*!*/;
SET @@SESSION.GTID_NEXT= 'AUTOMATIC' /* added by mysqlbinlog */ /*!*/;
DELIMITER ;
# End of log file
/*!50003 SET COMPLETION_TYPE=@OLD_COMPLETION_TYPE*/;
/*!50530 SET @@SESSION.PSEUDO_SLAVE_MODE=0*/;
(2) 执行指定Pos节点范围内的sql命令恢复数据
根据上述日志分析,只要恢复从2014.01.12 20:12:14到2014.01.12 20:13:50之间的操作即可。可通过mysqlbinlog指定时间范围输出,结合管道交给msyql命令执行导入重做:
[root@dbsvr1 ~]# mysqlbinlog \
--start-datetime="2017-04-12 12:06:55" \
--stop-datetime="2017-04-12 12:07:23" \
/var/lib/mysql/mysql-bin.000002 | mysql -u root -p
Enter password: //验证口令
(3)确认恢复结果
mysql> SELECT * FROM db1.tb1;
+----+--------+
| id | name |
+----+--------+
| 1 | Jack |
| 2 | Kenthy |
| 3 | Bob |
+----+--------+
3 rows in set (0.00 sec)
innobackupex备份工具
常用的MySQL备份工具
物理备份缺点
- 跨平台性差
- 备份时间长、冗余备份、浪费存储空间
mysqldump备份缺点
- 效率较低,备份和还原速度慢
- 备份过程中,数据插入和更新操作会被挂起
XtraBackup工具
一款强大的在线热备份工具
- 备份过程中不锁库表,适合生产环境
- 由专业组织Percona提供(改进MySQL分支)
主要含两个组件
xtrabackup
:C程序,支持InnoDB/XtraDBinnobackupex
:以Perl脚本封装xtrabackup,还支持MyISAM
安装percona
yum -y install /root/libev-4.15-1.el6.rf.x86_64.rpm //依赖文件
yum -y install /root/percona-xtrabackup-24-2.4.7-1.el7.x86_64.rpm
innobackupex基本选项
常用选项 | 含义 |
---|---|
- -host | 主机名 |
- -user | 用户名 |
- -port | 端口号 |
- -password | 密码 |
- -databases | 数据库名 |
- -no-timestamp | 不用日期命名备份文件存储的子目录名 |
注:
–databases说明
- –databases=“库名” //单个库
- –databases=“库1 库2” //多个库
- –databases=“库.表” //单个表
innobackupex功能
完全被份、完全恢复、增量备份、增量恢复、恢复完全备份中的单张表
innobackupex基本选项
常用选项 | 含义 |
---|---|
- -redo-only | 日志合并 |
- -apply-log | 准备还原(回滚日志) |
- -copy-back | 恢复数据 |
- -incremental 目录名 | 增量备份 |
- -incremental-basedir=目录名 | 增量备份时,指定上一次备份数据存储的目录名 |
- -incremental-dir=目录名 | 准备恢复数据时,指定增量备份数据存储的目录名 |
- -export | 导出表信息 |
import | 导入表空间 |
完全备份语法格式
innobackupex --user root --password 密码 备份目录名
(1)备份当前主机的所有数据库,/allbak目录只需要指定就好,不需要提前创建
[root@ip50 ~]# innobackupex --user root --password 123456 --no-timestamp /allbak
(2)将备份文件发到51主机
[root@ip50 ~]# scp -r /allbak/ root@192.168.4.51:/root/
(3)51主机上查看信息文件,看备份类型
[root@ip51 ~]# cat /root/allbak/xtrabackup_checkpoints
backup_type = full-backuped //完全备份
from_lsn = 0
to_lsn = 3315431
last_lsn = 3315440
compact = 0
recover_binlog_info = 0
(4)准备还原,回滚日志
注意:做数据还原的主机必须先停止mysqld服务并删除mysql目录下的所有文件
[root@ip51 ~]# systemctl stop mysqld
[root@ip51 ~]# rm -rf /var/lib/mysql/*
//回滚日志
[root@ip51 ~]# innobackupex --apply-log /root/allbak/
(5)查看下备份文件标示为准备备份
[root@ip51 ~]# cat /root/allbak/xtrabackup_checkpoints
backup_type = full-prepared
from_lsn = 0
to_lsn = 3315431
last_lsn = 3315440
compact = 0
recover_binlog_info = 0
(6)将备份文件拷贝到系统目录下
[root@ip51 ~]# innobackupex --copy-back /root/allbak/
(7)由于复制过来的数据文件的默认权限都是root,需要改权限
[root@ip51 ~]# chown -R mysql:mysql /var/lib/mysql
(8)重启mysqld服务
[root@ip51 ~]# systemctl restart mysqld
(9)使用备份数据库的管理员跟密码登录数据库查看恢复数据
[root@ip51 ~]# mysql -uroot -p123456
增量备份的语法格式
innodbackupex --user root --password 密码 --incremental 目录名 --incremental-basedir=目录名 --no-timestamp
步骤:
(1)首次备份,备份所有数据
[root@ip50 ~]# innobackupex --user root --password 123456 /fullbck --no-timestamp
(2)数据库insert新的数据
(3)增量备份1
[root@ip50 ~]# innobackupex --user root --password 123456 --incremental /newdir --incremental-basedir=/fullbck --no-timestamp
(4)新插入数据
(5)增量备份2
[root@ip50 ~]# innobackupex --user root --password 123456 --incremental /new1dir --incremental-basedir=/newdir --no-timestamp
增量恢复语法格式
(1)准备恢复数据
innobackupex --apply-log --redo-only 完全备份目录
(2)合并日志
innobackupex --apply-log --redo-only 完全备份目录 --incremental-dir=目录名
(3)拷贝数据
innobackupex --copy-back 完全备份目录
增量备份步骤
(1)将50主机上的备份数据发送到51主机上
[root@ip50 ~]# scp -r /fullbck/ root@192.168.4.51:/root/
[root@ip50 ~]# scp -r /newdir/ root@192.168.4.51:/root/
[root@ip50 ~]# scp -r /new1dir/ root@192.168.4.51:/root/
(2)做数据还原的主机必须先停止mysqld服务并删除mysql目录下的所有文件
[root@ip51 ~]# systemctl stop mysqld
[root@ip51 ~]# rm -rf /var/lib/mysql/*
(3)准备恢复数据
[root@ip51 ~]# innobackupex --apply-log --redo-only /root/fullbck/
(4)合并第一次增量备份的日志到完全备份日志文件中
[root@ip51 ~]# innobackupex --apply-log --redo-only /root/fullbck/ --incremental-dir=/root/newdir/
(5)合并第二次增量备份的日志到完全备份日志文件中
[root@ip51 ~]# innobackupex --apply-log --redo-only /root/fullbck/ --incremental-dir=/root/new1dir/
(6)将备份文件拷贝到系统目录下
[root@ip51 ~]# innobackupex --copy-back /root/fullbck/
(7)系统目录授权
[root@ip51 ~]# chown -R mysql:mysql /var/lib/mysql
(8)重启服务
[root@ip51 ~]# systemctl start mysqld
(9)登录数据库验证数据
[root@ip51 ~]# mysql -uroot -p123456
恢复完全备份中的单张表
(1)在50中新建一张表,并且插入测试数据
(2)备份全部数据
[root@ip50 ~]# innobackupex --user root --password 123456 /backup --no-timestamp
(3)删除50上的新建的表
mysql> drop table db6.t2;
(4)把删除的表按照原表结构创建出来(字段名,属性,宽度要一致)
(5)删除表空间db6库里边的t2表
mysql> alter table db6.t2 discard tablespace;
(6)在备份文件中导出表信息
[root@ip50 ~]# innobackupex --apply-log --export /backup/
(7)把导出的表信息文件拷贝大批数据库目录下,并修改所有者和所属组为mysql
[root@ip50 ~]# cp /backup/db6/t2.{cfg,exp,ibd} /var/lib/mysql/db6/
[root@ip50 ~]# chown -R mysql:mysql /var/lib/mysql
(8)导入表信息
mysql> alter table db6.t2 import tablespace;
(9)删除数据库目录下的表信息文件
[root@ip50 ~]# rm -rf /var/lib/mysql/db6/t2.cfg
[root@ip50 ~]# rm -rf /var/lib/mysql/db6/t2.exp
(10)查看表记录
mysql> select * from db6.t2;
案例
装包
(1)了解软件包描述信息
[root@dbsvr1 pub]# rpm -qpi percona-xtrabackup-24-2.4.6-2.el7.x86_64.rpm
Name : percona-xtrabackup-24
Version : 2.4.6
Release : 2.el7
Architecture: x86_64
Install Date: (not installed)
Group : Applications/Databases
Size : 32416340
License : GPLv2
Signature : DSA/SHA1, 2017年02月27日 星期一 20时28分17秒, Key ID 1c4cbdcdcd2efd2a
Source RPM : percona-xtrabackup-24-2.4.6-2.el7.src.rpm
Build Date : 2017年02月27日 星期一 20时27分21秒
Build Host : vps-centos7-x64-01.ci.percona.com
Relocations : (not relocatable)
URL : http://www.percona.com/software/percona-xtrabackup
Summary : XtraBackup online backup for MySQL / InnoDB
Description :
Percona XtraBackup is OpenSource online (non-blockable) backup solution for InnoDB and XtraDB engines
(2)安装依赖包perl-DBD-MySQL perl-Digest-MD5 libev
使用RHEL 7自带的即可,yum方式安装:
[root@dbsvr1 pub]# yum -y install perl-DBD-MySQL perl-Digest-MD5
libev使用网上找的rpm包 libev-4.15-1.el6.rf.x86_64.rpm //该包由讲师提供
[root@dbsvr1 pub]#rpm –ivh libev-4.15-1.el6.rf.x86_64.rpm
如果未安装这些依赖包,则直接安装percona-xtrabackup时会报错:
代码
(3)安装percona-xtrabackup
[root@dbsvr1 pub]#rpm -ivh percona-xtrabackup-*.rpm
警告:percona-xtrabackup-24-2.4.6-2.el7.x86_64.rpm: 头V4 DSA/SHA1 Signature, 密钥 ID cd2efd2a: NOKEY
准备中... ################################# [100%]
正在升级/安装...
1:percona-xtrabackup-24-2.4.6-2.el7################################# [ 33%]
2:percona-xtrabackup-test-24-2.4.6-################################# [ 67%]
3:percona-xtrabackup-24-debuginfo-2################################# [100%]
(4)确认安装的主要程序/脚本
[root@dbsvr1 pub]# rpm -ql percona-xtrabackup-24-2.4.6-2.el7.x86_64
/usr/bin/innobackupex
/usr/bin/xbcloud
/usr/bin/xbcloud_osenv
/usr/bin/xbcrypt
/usr/bin/xbstream
/usr/bin/xtrabackup
/usr/share/doc/percona-xtrabackup-24-2.4.6
/usr/share/doc/percona-xtrabackup-24-2.4.6/COPYING
/usr/share/man/man1/innobackupex.1.gz
/usr/share/man/man1/xbcrypt.1.gz
/usr/share/man/man1/xbstream.1.gz
/usr/share/man/man1/xtrabackup.1.gz
二:innobackupex完整备份、增量备份操作
(1)做一个完整备份
默认情况下,备份文件存储的子目录会用日期命名,innobackupex
作为客户端工具,以mysql协议连入mysqld,将数据备份到/backup文件夹:
[root@dbsvr1 ~]# innobackupex --user=root --password=1234567 /backup/mysql –no-timestamp
170425 11:05:44 innobackupex: Starting the backup operation
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
Unrecognized character \x01; marked by <-- HERE after <-- HERE near column 1 at - line 1374.
170425 11:05:45 Connecting to MySQL server host: localhost, user: root, password: set, port: not set, socket: not set
Using server version 5.7.17
innobackupex version 2.4.6 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 8ec05b7)
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
InnoDB: Number of pools: 1
170425 11:05:45 >> log scanned up to (2543893)
xtrabackup: Generating a list of tablespaces
InnoDB: Allocated tablespace ID 2 for mysql/plugin, old maximum was 0
170425 11:05:45 [01] Copying ./ibdata1 to /backup/ibdata1
170425 11:05:45 [01] ...done
170425 11:05:46 [01] Copying ./mysql/plugin.ibd to /backup/mysql/plugin.ibd
170425 11:05:46 [01] ...done
170425 11:05:46 [01] Copying ./mysql/servers.ibd to /backup/mysql/servers.ibd
170425 11:05:46 [01] ...done
170425 11:05:46 [01] Copying ./mysql/help_topic.ibd to /backup/mysql/help_topic.ibd
170425 11:05:46 [01] ...done
170425 11:05:46 >> log scanned up to (2543893)
.. ..
170425 11:06:00 [01] Copying ./sys/x@0024waits_global_by_latency.frm to /backup/sys/x@0024waits_global_by_latency.frm
170425 11:06:00 [01] ...done
170425 11:06:00 [01] Copying ./sys/session_ssl_status.frm to /backup/sys/session_ssl_status.frm
170425 11:06:00 [01] ...done
170425 11:06:00 [01] Copying ./db1/db.opt to /backup/db1/db.opt
170425 11:06:00 [01] ...done
170425 11:06:00 [01] Copying ./db1/tb1.frm to /backup/db1/tb1.frm
170425 11:06:00 [01] ...done
170425 11:06:00 Finished backing up non-InnoDB tables and files
170425 11:06:00 Executing FLUSH NO_WRITE_TO_BINLOG ENGINE LOGS...
xtrabackup: The latest check point (for incremental): '2543884'
xtrabackup: Stopping log copying thread.
.170425 11:06:00 >> log scanned up to (2543893)
170425 11:06:00 Executing UNLOCK TABLES
170425 11:06:00 All tables unlocked
170425 11:06:00 [00] Copying ib_buffer_pool to /backup/ib_buffer_pool
170425 11:06:00 [00] ...done
170425 11:06:00 Backup created in directory '/backup/'
170425 11:06:00 [00] Writing backup-my.cnf
170425 11:06:00 [00] ...done
170425 11:06:00 [00] Writing xtrabackup_info
170425 11:06:00 [00] ...done
xtrabackup: Transaction log of lsn (2543884) to (2543893) was copied.
170425 11:06:01 completed OK
确认备份好的文件数据:
[root@dbsvr1 ~]#ls /backup/
backup-my.cnf ib_buffer_pool mysql sys xtrabackup_info
db1 ibdata1 performance_schema xtrabackup_checkpoints xtrabackup_logfile
(2)做一个增量备份(基于前一步的完整备份)
随意做一些新增或更改库表的操作,比如在db1库中新建一个mytb的表:
mysql> USE db1;
Database changed
mysql> CREATE TABLE mytb(id int(4), name varchar(24));
Query OK, 0 rows affected (0.38 sec)
mysql> INSERT INTO tb1 VALUES
-> (1,'bon'),
-> (2,'bo'),
Query OK, 2 rows affected (0.12 sec)
Records: 2 Duplicates: 0 Warnings: 0
mysql> SELECT * FROM tb1;
+------+------+
| id | name |
+------+------+
| 1 | bob |
| 2 | bo |
+------+------+
2 rows in set (0.00 sec)
以前一次保存到/backup的完整备份为基础,做一个增量备份,保存到/incr01/,指定增量备份参照的基本目录(完整备份目录)需要用到选项–incremental-basedir。相关操作如下:
[root@dbsvr1 ~]# innobackupex --user=root --password=12345678 --incremental /incr01 --incremental-basedir=/backup/ --no-timestamp
170425 11:30:14 innobackupex: Starting the backup operation
IMPORTANT: Please check that the backup run completes successfully.
At the end of a successful backup run innobackupex
prints "completed OK!".
Unrecognized character \x01; marked by <-- HERE after <-- HERE near column 1 at - line 1374.
170425 11:30:14 Connecting to MySQL server host: localhost, user: root, password: set, port: not set, socket: not set
Using server version 5.7.17
innobackupex version 2.4.6 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 8ec05b7)
incremental backup from 2543884 is enabled.
xtrabackup: uses posix_fadvise().
xtrabackup: cd to /var/lib/mysql
xtrabackup: open files limit requested 0, set to 1024
xtrabackup: using the following InnoDB configuration:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = ./
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
InnoDB: Number of pools: 1
170425 11:30:14 >> log scanned up to (2549933)
xtrabackup: Generating a list of tablespaces
InnoDB: Allocated tablespace ID 2 for mysql/plugin, old maximum was 0
xtrabackup: using the full scan for incremental backup
170425 11:30:15 [01] Copying ./ibdata1 to /incr01/ibdata1.delta
170425 11:30:15 [01] ...done
170425 11:30:15 >> log scanned up to (2549933)
170425 11:30:15 [01] Copying ./mysql/plugin.ibd to /incr01/mysql/plugin.ibd.delta
170425 11:30:15 [01] ...done
... ...
170425 11:30:35 Executing UNLOCK TABLES
170425 11:30:35 All tables unlocked
170425 11:30:35 [00] Copying ib_buffer_pool to /incr01/ib_buffer_pool
170425 11:30:35 [00] ...done
170425 11:30:35 Backup created in directory '/incr01/'
170425 11:30:35 [00] Writing backup-my.cnf
170425 11:30:35 [00] ...done
170425 11:30:35 [00] Writing xtrabackup_info
170425 11:30:35 [00] ...done
xtrabackup: Transaction log of lsn (2549924) to (2549933) was copied.
170425 11:30:35 completed OK!
确认备份好的文件数据:
[root@dbsvr1 ~]# ls /incr01/
backup-my.cnf ib_buffer_pool ibdata1.meta performance_schema xtrabackup_checkpoints xtrabackup_logfile
db1 ibdata1.delta mysql sys
对比完整备份、增量备份的大小:
[root@dbsvr1 ~]# du -sh /backup/ /incr01/
142M /backup/ //完整备份的大小
3.5M /incr01/ //增量备份的大小
三:恢复数据
通过XtraBackup工具备份的数据库目录,若要恢复到另一个MySQL服务器,需要先做一个“--apply-log --redo-only ”
的准备操作。
(1)准备恢复“完整备份”
完成准备以后,最终/backup可用来重建MySQL服务器。这种情况下,需要先做一个“--apply-log --redo-only
”的准备操作,以确保数据一致性:
[root@dbsvr1 ~]#innobackupex --user=root --password=12345678 --apply-log --redo-only /backup/
170425 11:42:19 innobackupex: Starting the apply-log operation
IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints "completed OK!".
innobackupex version 2.4.6 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 8ec05b7)
xtrabackup: cd to /backup/
xtrabackup: This target seems to be already prepared.
InnoDB: Number of pools: 1
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:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = .
xtrabackup: innodb_log_files_in_group = 2
xtrabackup: innodb_log_file_size = 50331648
xtrabackup: Starting InnoDB instance for recovery.
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
InnoDB: PUNCH HOLE support available
InnoDB: Mutexes and rw_locks use GCC atomic builtins
InnoDB: Uses event mutexes
InnoDB: GCC builtin __atomic_thread_fence() is used for memory barrier
InnoDB: Compressed tables use zlib 1.2.7
InnoDB: Number of pools: 1
InnoDB: Not using CPU crc32 instructions
InnoDB: Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100M
InnoDB: Completed initialization of buffer pool
InnoDB: page_cleaner coordinator priority: -20
InnoDB: Highest supported file format is Barracuda.
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
InnoDB: Starting shutdown...
InnoDB: Shutdown completed; log sequence number 2544177
InnoDB: Number of pools: 1
170425 11:42:20 completed OK!
准备恢复“增量备份”
[root@dbsvr1 ~]#innobackupex --user=root --password=12345678 --apply-log --redo-only /backup/ --incremental-dir=/incr01
170425 11:42:55 innobackupex: Starting the apply-log operation
IMPORTANT: Please check that the apply-log run completes successfully.
At the end of a successful apply-log run innobackupex
prints "completed OK!".
innobackupex version 2.4.6 based on MySQL server 5.7.13 Linux (x86_64) (revision id: 8ec05b7)
incremental backup from 2543884 is enabled.
xtrabackup: cd to /backup/
xtrabackup: This target seems to be already prepared with --apply-log-only.
InnoDB: Number of pools: 1
xtrabackup: xtrabackup_logfile detected: size=8388608, start_lsn=(2549924)
xtrabackup: using the following InnoDB configuration for recovery:
xtrabackup: innodb_data_home_dir = .
xtrabackup: innodb_data_file_path = ibdata1:12M:autoextend
xtrabackup: innodb_log_group_home_dir = /incr01/
xtrabackup: innodb_log_files_in_group = 1
xtrabackup: innodb_log_file_size = 8388608
xtrabackup: Generating a list of tablespaces
InnoDB: Allocated tablespace ID 2 for mysql/plugin, old maximum was 0
xtrabackup: page size for /incr01//ibdata1.delta is 16384 bytes
Applying /incr01//ibdata1.delta to ./ibdata1...
... ...
170425 11:43:09 [01] Copying /incr01/performance_schema/global_status.frm to ./performance_schema/global_status.frm
170425 11:43:09 [01] ...done
170425 11:43:09 [01] Copying /incr01/performance_schema/session_status.frm to ./performance_schema/session_status.frm
170425 11:43:09 [01] ...done
170425 11:43:09 [00] Copying /incr01//xtrabackup_info to ./xtrabackup_info
170425 11:43:09 [00] ...done
170425 11:43:10 completed OK!
(2)关闭mysql服务,并将/var/lib/mysql/下的文件删除,假设数据被删除。
[root@dbsvr1 ~]#systemctl stop mysqld
[root@dbsvr1 ~]#rm -rf /var/lib/mysql
(3)恢复“完整备份+增量备份”
完成准备以后,最终仍然是/backup用来重建MySQL服务器,但这种情况下需提前合并相关增量备份的数据
[root@dbsvr1 ~]# innobackupex --user=root --password=12345678 --copy-back /backup/
... ...
170425 11:51:39 [01] Copying ./performance_schema/global_status.frm to /var/lib/mysql/performance_schema/glo.frm
170425 11:51:39 [01] ...done
170425 11:51:39 [01] Copying ./performance_schema/session_status.frm to /var/lib/mysql/performance_schema/seus.frm
170425 11:51:39 [01] ...done
170425 11:51:39 [01] Copying ./ib_buffer_pool to /var/lib/mysql/ib_buffer_pool
170425 11:51:39 [01] ...done
170425 11:51:39 [01] Copying ./ibtmp1 to /var/lib/mysql/ibtmp1
170425 11:51:39 [01] ...done
170425 11:51:39 [01] Copying ./xtrabackup_info to /var/lib/mysql/xtrabackup_info
170425 11:51:39 [01] ...done
170425 11:51:39 completed OK!
(4)修改/var/lib/mysql/下文件属主与属组,查看数据:
恢复后,/var/lib/mysql下文件属组与属主皆为root,需要更改为mysql
[root@dbsvr1 ~]#chown -R mysql:mysql /var/lib/mysql
[root@dbsvr1 ~]#systemctl start mysqld.service
[root@dbsvr1 ~]#mysql -uroot -p12345678 -e "select * from db1.tb1"
mysql: [Warning] Using a password on the command line interface can be insecure.
+------+------+
| id | name |
+------+------+
| 1 | bob |
| 2 | bo |
+------+------+