MySQL备份与恢复之percona-xtrabackup实现增量备份及恢复(二)

2014-11-24 16:59:39 · 作者: · 浏览: 1
)

第十步,对全部的数据进行检查。可以看到增量备份和全备的文件占用磁盘大小有很大的差别,显然全备占用磁盘空间多,增量备份占用磁盘空间少

[root@serv01 databackup]# innobackupex --apply-log --redo-only /databackup/2013-09-10_22-12-50/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 2009-2012.  All Rights Reserved.
……
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
130910 22:23:35  InnoDB: Starting shutdown...
130910 22:23:36  InnoDB: Shutdown completed; log sequence number 2098700
130910 22:23:36  innobackupex: completed OK!

[root@serv01 databackup]# du -sh ./*
22M ./2013-09-10_22-12-50
1.5M  ./2013-09-10_22-15-45
1.5M  ./2013-09-10_22-19-21
1.5M  ./2013-09-10_22-21-42

第十一步,对第一次做的增量备份数据进行合并到全备份中去

[root@serv01 databackup]# innobackupex --apply-log --redo-only --incremental /databackup/2013-09-10_22-12-50/ --incremental-dir=/databackup/2013-09-10_22-15-45/

InnoDB Backup Utility v1.5.1-xtrabackup; Copyright 2003, 2009 Innobase Oy
and Percona Inc 2009-2012.  All Rights Reserved.
……
innobackupex: Copying '/databackup/2013-09-10_22-15-45/hello/db.opt' to '/databackup/2013-09-10_22-12-50/hello/db.opt'
130910 22:32:26  innobackupex: completed OK!

第十二步,对第二次做的增量备份数据进行合并到全备份中去

[root@serv01 databackup]# innobackupex --apply-log --redo-only --incremental /databackup/2013-09-10_22-12-50/ --incremental-dir=/databackup/2013-09-10_22-19-21/

第十三步,对第三次做的增量备份数据进行合并到全备份中去

[root@serv01 databackup]# innobackupex --apply-log --redo-only --incremental /databackup/2013-09-10_22-12-50/ --incremental-dir=/databackup/2013-09-10_22-21-42/

第十四步,恢复时需要停掉MySQL,所以我们停掉MySQL

[root@serv01 databackup]# /etc/init.d/mysqld stop
 ERROR! MySQL server PID file could not be found!
[root@serv01 databackup]# pkill -9 mysql

第十五步,恢复数据。注意这里指定的文件夹是2013-09-10_22-12-50

[root@serv01 databackup]# innobackupex --copy-back /databackup/2013-09-10_22-12-50/

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.

IMPORTANT: Please check that the copy-back run completes successfully.
           At the end of a successful copy-back run innobackupex
           prints "completed OK!".

Original data directory is not empty! at /usr/bin/innobackupex line 571.

#报以上错需要删除数据目录下的东西
[root@serv01 data]# pwd
/usr/local/mysql/data
[root@serv01 data]# ls
game     ib_logfile0  mysql             mysql-bin.000003  performance_schema   test
hello    ib_logfile1  mysql-bin.000001  mysql-bin.000004  serv01.host.com.err  xtrabackup_binlog_pos_innodb
ibdata1  mnt          mysql-bin.000002  mysql-bin.index   serv01.host.com.pid

[root@serv01 data]# rm -rf  *

#再次恢复数据,并更改数据库数据目录的拥有者和所属组
[root@serv01 databackup]# innobackupex --copy-back /databackup/2013-09-10_22-12-50/

[root@serv01 data]# ll
total 18464
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 game
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 hello
-rw-r-----. 1 root root 18874368 Sep 10 22:33 ibdata1
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 larrydb
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 mnt
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 mysql
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 performance_schema
drwxr-xr-x. 2 root root     4096 Sep 10 22:37 test
-rw-r--r--. 1 root root       24 Sep 10 22:37 xtrabackup_binlog_pos_innodb
  
[root@serv01 data]# cho