使用XtraBackup 备份MySQL数据库

142536a

#使用--apply-log应用日志，　　
[root@rhel7 ~]# innobackupex --apply-log /mysqlbackup/2016-12-13_12-27-13/
　　
161213 12:36:24 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.5 based on MySQL server 5.7.13 Linux (x86_64) (revision id: e41c0be)
　　
xtrabackup: cd to /mysqlbackup/2016-12-13_12-27-13/
　　
xtrabackup: This target seems to be not prepared yet.
　　
InnoDB: Number of pools: 1
　　
xtrabackup: xtrabackup_logfile detected: size=8388608, start_lsn=(2671634)
　　
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 = 1
　　
xtrabackup:   innodb_log_file_size = 8388608
　　
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 = 1
　　
xtrabackup:   innodb_log_file_size = 8388608
　　
xtrabackup: Starting InnoDB instance for recovery.
　　
xtrabackup: Using 104857600 bytes for buffer pool (set by --use-memory parameter)
　　
InnoDB: PUNCH HOLE support not available
　　
InnoDB: Mutexes and rw_locks use GCC atomic builtins
　　
InnoDB: Uses event mutexes
　　
InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
　　
InnoDB: Compressed tables use zlib 1.2.3
　　
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.
　　
InnoDB: Log scan progressed past the checkpoint lsn 2671634
　　
InnoDB: Doing recovery: scanned up to log sequence number 2671643 (0%)
　　
InnoDB: Doing recovery: scanned up to log sequence number 2671643 (0%)
　　
InnoDB: Database was not shutdown normally!
　　
InnoDB: Starting crash recovery.
　　
InnoDB: Creating shared tablespace for temporary tables
　　
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
　　
InnoDB: File './ibtmp1' size is now 12 MB.
　　
InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active.
　　
InnoDB: 32 non-redo rollback segment(s) are active.
　　
InnoDB: Waiting for purge to start
　　
InnoDB: 5.7.13 started; log sequence number 2671643
　　

　　
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
　　
InnoDB: FTS optimize thread exiting.
　　
InnoDB: Starting shutdown...
　　
InnoDB: Shutdown completed; log sequence number 2671671
　　
InnoDB: Number of pools: 1
　　
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
　　
InnoDB: PUNCH HOLE support not available
　　
InnoDB: Mutexes and rw_locks use GCC atomic builtins
　　
InnoDB: Uses event mutexes
　　
InnoDB: GCC builtin __sync_synchronize() is used for memory barrier
　　
InnoDB: Compressed tables use zlib 1.2.3
　　
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: Setting log file ./ib_logfile101 size to 48 MB
　　
InnoDB: Setting log file ./ib_logfile1 size to 48 MB
　　
InnoDB: Renaming log file ./ib_logfile101 to ./ib_logfile0
　　
InnoDB: New log files created, LSN=2671671
　　
InnoDB: Highest supported file format is Barracuda.
　　
InnoDB: Log scan progressed past the checkpoint lsn 2672140
　　
InnoDB: Doing recovery: scanned up to log sequence number 2672149 (0%)
　　
InnoDB: Doing recovery: scanned up to log sequence number 2672149 (0%)
　　
InnoDB: Database was not shutdown normally!
　　
InnoDB: Starting crash recovery.
　　
InnoDB: Removed temporary tablespace data file: "ibtmp1"
　　
InnoDB: Creating shared tablespace for temporary tables
　　
InnoDB: Setting file './ibtmp1' size to 12 MB. Physically writing the file full; Please wait ...
　　
InnoDB: File './ibtmp1' size is now 12 MB.
　　
InnoDB: 96 redo rollback segment(s) found. 1 redo rollback segment(s) are active.
　　
InnoDB: 32 non-redo rollback segment(s) are active.
　　
InnoDB: Waiting for purge to start
　　
InnoDB: 5.7.13 started; log sequence number 2672149
　　
xtrabackup: starting shutdown with innodb_fast_shutdown = 1
　　
InnoDB: FTS optimize thread exiting.
　　
InnoDB: Starting shutdown...
　　
InnoDB: Shutdown completed; log sequence number 2672168
　　
161213 12:36:30 completed OK!
　　
#查看prepare后数据目录的大小
　　
[root@rhel7 ~]# ls -l /mysqlbackup/
　　
total 4
　　
drwxr-x---. 7 root root 4096 Dec 13 12:36 2016-12-13_12-27-13
　　
[root@rhel7 ~]# du -sm /mysqlbackup/*
　　
206/mysqlbackup/2016-12-13_12-27-13