mysql innobackupex_Mysql备份 -----innobackupex

[root@Server data]# innobackupex --apply-log /data/2018-10-29_14-41-49/#prepare过程

xtrabackup: recognized server arguments:--innodb_checksum_algorithm=innodb --innodb_log_checksum_algorithm=innodb --innodb_data_file_path=ibdata1:12M:autoextend--innodb_log_files_in_group=2 --innodb_log_file_size=50331648 --innodb_fast_checksum=0 --innodb_page_size=16384 --innodb_log_block_size=512 --innodb_undo_directory=. --innodb_undo_tablespaces=0 --server-id=1 --redo-log-version=0 xtrabackup: recognized client arguments: --innodb_checksum_algorithm=innodb --innodb_log_checksum_algorithm=innodb --innodb_data_file_path=ibdata1:12M:autoextend--innodb_log_files_in_group=2 --innodb_log_file_size=50331648 --innodb_fast_checksum=0 --innodb_page_size=16384 --innodb_log_block_size=512 --innodb_undo_directory=. --innodb_undo_tablespaces=0 --server-id=1 --redo-log-version=0 181029 14:50:05 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 version2.4.12 based on MySQL server 5.7.19 Linux (x86_64) (revision id: 170eb8c)

xtrabackup: cd to/data/2018-10-29_14-41-49/xtrabackup: This target seems to be not prepared yet.

InnoDB: Number of pools:1xtrabackup: xtrabackup_logfile detected: size=8388608, start_lsn=(2048670711)

xtrabackup: using the following InnoDB configurationforrecovery:

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= 1xtrabackup: innodb_log_file_size= 8388608xtrabackup: using the following InnoDB configurationforrecovery:

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= 1xtrabackup: innodb_log_file_size= 8388608xtrabackup: Starting InnoDB instanceforrecovery.

xtrabackup: Using104857600 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 __sync_synchronize() is usedformemory barrier

InnoDB: Compressed tables use zlib1.2.3InnoDB: Number of pools:1InnoDB: 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:-20InnoDB: Highest supportedfileformat is Barracuda.

InnoDB: Log scan progressed past the checkpoint lsn2048670711InnoDB: Doing recovery: scanned up to log sequence number2048706153 (0%)

InnoDB: Database was not shutdown normally!InnoDB: Starting crash recovery.

InnoDB: Starting an apply batch of log records to the database...

InnoDB: Progressin percent: 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40

41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99InnoDB: Apply batch completed

InnoDB: xtrabackup: Last MySQL binlogfile position 11989, file name ./server-bin.000044InnoDB: Creating shared tablespacefortemporary tables

InnoDB: Settingfile './ibtmp1' size to 12 MB. Physically writing the file full; Please wait...

InnoDB: File'./ibtmp1' size is now 12MB.

InnoDB:96 redo rollback segment(s) found. 1redo rollback segment(s) are active.

InnoDB:32 non-redo rollback segment(s) are active.

InnoDB: Waitingforpurge to start

InnoDB:5.7.19 started; log sequence number 2048706153InnoDB: xtrabackup: Last MySQL binlogfile position 11989, file name ./server-bin.000044xtrabackup: starting shutdown with innodb_fast_shutdown= 1InnoDB: FTS optimize thread exiting.

InnoDB: Starting shutdown...

InnoDB: Shutdown completed; log sequence number2048707915InnoDB: Number of pools:1xtrabackup: using the following InnoDB configurationforrecovery:

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= 2xtrabackup: innodb_log_file_size= 50331648InnoDB: PUNCH HOLE support available

InnoDB: Mutexes and rw_locks use GCC atomic builtins

InnoDB: Uses event mutexes

InnoDB: GCC builtin __sync_synchronize() is usedformemory barrier

InnoDB: Compressed tables use zlib1.2.3InnoDB: Number of pools:1InnoDB: 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:-20InnoDB: Setting logfile ./ib_logfile101 size to 48MB

InnoDB: Setting logfile ./ib_logfile1 size to 48MB

InnoDB: Renaming logfile ./ib_logfile101 to ./ib_logfile0

InnoDB: New log files created, LSN=2048707915InnoDB: Highest supportedfileformat is Barracuda.

InnoDB: Log scan progressed past the checkpoint lsn2048708108InnoDB: Doing recovery: scanned up to log sequence number2048708117 (0%)

InnoDB: Database was not shutdown normally!InnoDB: Starting crash recovery.

InnoDB: xtrabackup: Last MySQL binlogfile position 11989, file name ./server-bin.000044InnoDB: Removed temporary tablespace datafile: "ibtmp1"InnoDB: Creating shared tablespacefortemporary tables

InnoDB: Settingfile './ibtmp1' size to 12 MB. Physically writing the file full; Please wait...

InnoDB: File'./ibtmp1' size is now 12MB.

InnoDB:96 redo rollback segment(s) found. 1redo rollback segment(s) are active.

InnoDB:32 non-redo rollback segment(s) are active.

InnoDB: Waitingforpurge to start

InnoDB:5.7.19 started; log sequence number 2048708117xtrabackup: starting shutdown with innodb_fast_shutdown= 1InnoDB: FTS optimize thread exiting.

InnoDB: Starting shutdown...

InnoDB: Shutdown completed; log sequence number2048713467

181029 14:50:09 completed OK!