阿里云Mysql數據庫物理全備文件恢運彩 棄賽復到自建數據庫Mysql報錯_InnoDB_Log_file_./…xtrabacku

Posted on By BETS88小編
報錯信息：……InnoDB Log file .ib_logfile1 is of different size 50331648 bytes than other log files 12058624 bytes!InnoDB Plugin initialization aborted ith error Generic errorxtrabackup innodb_init() Error occured.環境介紹： CentOS 7.5 Mysql 5.7.30 percona-xtrabackup-24過程回溯：[roottest2 ~]# chon -R mysqlmysql varlibmysql[roottest2 ~]# ll varlibmysql總用量 293172-r-r—– 1 mysql mysql 56 7月 10 1641 auto.cnf-r-r—- 1 mysql mysql 543 7月 10 1650 backup-my.cnf-r——- 1 mysql mysql 1680 7月 10 1641 ca-key.pem-r-r–r– 1 mysql mysql 1112 7月 10 1641 ca.pem-r-r–r– 1 mysql mysql 1112 7月 10 1641 client-cert.pem-r——- 1 mysql mysql 1680 7月 10 1641 client-key.pemdrxr-xr-x 2 mysql mysql 46 7月 10 1648 crmdbdrxr-xr-x 2 mysql mysql 46 7月 10 1648 crmdb_test-r-r—– 1 mysql mysql 425 7月 10 1641 ib_buffer_pool-r-r—- 1 mysql mysql 2715200 7月 8 1231 ibdata1-r-r—– 1 mysql mysql 50331648 7月 10 1641 ib_logfile1-r-r—– 1 mysql mysql 12582912 7月 10 1641 ibtmp1drxr-x— 2 mysql mysql 46 7月 10 1648 mysqlsrxrxrx 1 mysql mysql 0 7月 10 1641 mysql.sock-r——- 1 mysql mysql 5 7月 10 1641 mysql.sock.lockdrxr-x— 2 mysql mysql 8192 7月 10 1648 performance_schema-r——- 1運彩線上下單 mysql mysql 1680 7月 10 1641 private_key.pem-r-r–r– 1 mysql mysql 452 7月 10 1641 public_key.pem-r-r–r– 1 mysql mysql 1112 7月 10 1641 server-cert.pem-r——- 1 mysql mysql 1680 7月 10 1641 server-key.pemdrxr-x— 2 mysql mysql 8192 7月 10 1648 sys-r-r—- 1 mysql mysql 119 7月 8 1331 xtrabackup_binlog_info-r-r—- 1 mysql mysql 147 7月 8 1331 xtrabackup_checkpoints-r-r—- 1 mysql mysql 845 7月 8 1331 xtrabackup_info-r-r—- 1 mysql mysql 10747904 7月 10 1716 xtrabackup_logfile-r-r—- 1 mysql mysql 74 7月 8 1331 xtrabackup_slave_filename_info-r-r—- 1 mysql mysql 162 7月 8 1331 xtrabackup_slave_info[roottest2 ~]# innobackupex –defaults-file=varlibmysqlbackup-my.cnf –apply-log varlibmysqlxtrabackup recognized server arguments –innodb_checksum_algorithm=crc32 –innodb_data_file_path=ibdata1200Mautoextend –innodb_log_files_in_group=2 –innodb_log_file_size=1048576000 –innodb_page_size=16384 –innodb_undo_directory=. –innodb_undo_tablespaces=0 –server-=2931342899xtrabackup recognized client arguments202410 172040 innobackupex Starting the apply-log operationIMPORTANT Please check that the運彩 比數 apply-log run pletes successfully. At the end of a successful apply-log run innobackupex prints “pleted OK!”.innobackupex version 2.4.20 based on MySQL server 5.7.26 Linux (x86_64) (revision c8b4056)xtrabackup cd to varlibmysqlxtrabackup This target seems to be not prepared yet.InnoDB Number of pools 1xtrabackup xtrabackup_logfile detected size=12058624, start_lsn=(10489267059)xtrabackup using the folloing InnoDB configuration for recovery innodb_data_home_dir = .xtrabackup innodb_data_file_path = ibdata1200M innodb_log_group_home_dir = .xtrabackup innodb_log_files_in_group = 1xtrabackup innodb_log_file_size = 12058624xtrabackup using the folloing InnoDB configuration for recovery innodb_data_home_dir = .xtrabackup innodb_data_file_path = ibdata1200M innodb_log_group_home_dir = .xtrabackup innodb_log_files_in_group = 1xtrabackup innodb_log_file_size = 12058624xtrabackup Starting InnoDB instance for recovery.xtrabackup Using 104857600 bytes for buffer pool (set by –use-memory parameter)InnoDB PUNCH HOLE support availableInnoDB Mutexes and r_locks use GCC atomic builtinsInnoDB Uses event mutexesInnoDB GCC builtin __atomic_thread_fence() is used for memory barrierInnoDB Compressed tables use zlib 1.2.7InnoDB Number of pools 1InnoDB Using CPU crc32 instructionsInnoDB Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100MInnoDB Completed initialization of buffer poolInnoDB page_cleaner coordinator priority -20InnoDB Log file .ib_logfile1 is of different size 50331648 bytes than other log files 12058624 bytes!InnoDB Plugin initialization aborted ith error Generic errorxtrabackup innodb_init() Error occured.解決想法： 移除所有ib_logfile*的文件，最好是挪動到其他文件夾，不要直接刪除。[roottest2 ~]# mv varlibmysqlib_logfile1 rootcrmdb 將_logfile1挪動至其他文件夾[roottest2 ~]# innobackupex –defaults-file=varlibmysqlbackup-my.cnf –apply-log varlibmysqlxtrabackup recognized server arguments –innodb_checksum_algorithm=crc32 –innodb_data_file_path=ibdata1200Mautoextend –innodb_log_files_in_group=2 –innodb_log_file_size=1048576000 –innodb_page_size=16384 –innodb_undo_directory=. –innodb_undo_tablespaces=0 –server-=2931342899xtrabackup recognized client arguments202410 173803 innobackupex Starting the apply-log operationIMPORTANT Please check that the apply-log run pletes successfully. At the end of a successful apply-log run innobackupex prints “pleted OK!”.innobackupex version 2.4.20 based on MySQL server 5.7.26 Linux (x86_64) (revision c8b4056)xtrabackup cd to varlibmysqlxtrabackup This target seems to be not prepared yet.InnoDB Number of pools 1xtrabackup xtrabackup_logfile detected size=13565952, start_lsn=(10489267059)xtrabackup using the folloing InnoDB configuration for recovery innodb_data_home_dir = .xtrabackup innodb_data_file_path = ibdata1200M innodb_log_group_home_dir = .xtrabackup innodb_log_files_in_group = 1xtrabackup innodb_log_file_size = 13565952xtrabackup using the folloing InnoDB configuration for recovery innodb_data_home_dir = .xtrabackup innodb_data_file_path = ibdata1200M innodb_log_group_home_dir = .xtrabackup innodb_log_files_in_group = 1xtrabackup innodb_log_file_size = 13565952xtrabackup Starting InnoDB instance for recovery.xtrabackup Using 104857600 bytes for buffer pool (set by –use-memory parameter)InnoDB PUNCH HOLE support availableInnoDB Mutexes and r_locks use GCC atomic builtinsInnoDB Uses event mutexesInnoDB GCC builtin __atomic_thread_fence() is used for memory barrierInnoDB Compressed tables use zlib 1.2.7InnoDB Number of pools 1InnoDB Using CPU crc32 instructionsInnoDB Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100MInnoDB Compl運彩 場中eted initialization of buffer poolInnoDB page_cleaner coordinator priority -20InnoDB Highest supported file format is Barracuda.InnoDB Log scan progressed past the checkpoint lsn 10489267059InnoDB Doing recovery scanned up to log sequence number 104945568 (43)InnoDB Doing recovery scanned up to log sequence number 10498831278 (79)InnoDB Database as not shutdon normally!InnoDB Starting crash recovery.InnoDB Starting an apply batch of log records to the database…InnoDB Progress in percent 0 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 pletedInnoDB xtrabackup Last MySQL binlog file position 593541, file name mysql-bin.001448InnoDB Removed temporary tablespace data file “ibtmp1″InnoDB Creating shared tablespace for temporary tablesInnoDB Setting file ‘.ibtmp1’ size to 12 MB. Physically riting the file full; Please ait …InnoDB File ‘.ibtmp1’ size is no 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 startInnoDB 5.7.26 started; log sequence number 10498831278InnoDB page_cleaner 1000ms intended loop took 46390ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)InnoDB xtrabackup Last MySQL binlog file position 593541, file name mysql-bin.001448xtrabackup starting shutdon ith innodb_fast_shutdon = 1InnoDB FTS optimize thread exiting.InnoDB Starting shutdon…InnoDB Shutdon pleted; log sequence number 10498832727InnoDB Number of pools 1xtrabackup using the folloing InnoDB conlol 賠率figuration for recovery innodb_data_home_dir = .xtrabackup innodb_data_file_path = ibdata1200M innodb_log_group_home_dir = .xtrabackup innodb_log_files_in_group = 2xtrabackup innodb_log_file_size = 1048576000InnoDB PUNCH HOLE support availableInnoDB Mutexes and r_locks use GCC atomic builtinsInnoDB Uses event mutexesInnoDB GCC builtin __atomic_thread_fence() is used for memory barrierInnoDB Compressed tables use zlib 1.2.7InnoDB Number of pools 1InnoDB Using CPU crc32 instructionsInnoDB Initializing buffer pool, total size = 100M, instances = 1, chunk size = 100MInnoDB Completed initialization of buffer poolInnoDB page_cleaner coordinator priority -20InnoDB Setting log file .ib_logfile101 size to 1000 MBInnoDB Progress in MB 100 200 300 400 500 600 700 800 900 1000InnoDB Setting log file .ib_logfile1 size to 1000 MBInnoDB Progress in MB 100 200 300 400 500 600 700 800 900 1000InnoDB Renaming log file .ib_logfile101 to .ib_logfile0InnoDB Ne log files created, LSN=10498832727InnoDB Highest supported file format is Barracuda.InnoDB Log scan progressed past the checkpoint lsn 10498832908InnoDB Doing recovery scanned up to log sequence number 10498832917 (0)InnoDB Database as not shutdon normally!InnoDB Starting crash recovery.InnoDB xtrabackup Last MySQL binlog file position 593541, file name mysql-bin.001448InnoDB Removed temporary tablespace data file “ibtmp1″InnoDB Creating shared tablespace for temporary tablesInnoDB Setting file ‘.ibtmp1’ size to 12 MB. Physically riting the file full; Please ait …InnoDB File ‘.ibtmp1’ size is no 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 page_cleaner 1000ms intended loop took 35376ms. The settings might not be optimal. (flushed=0 and evicted=0, during the time.)InnoDB 5.7.26 started; log sequence number 10498832917xtrabackup starting shutdon ith innodb_fast_shutdon = 1InnoDB FTS optimize thread exiting.InnoDB Starting shutdon…InnoDB Shutdon pleted; log sequence number 10498832936202410 173928 pleted OK! 可以看到這時再執行 innobackupex 覆原數據，就執行勝利了。留心： 數據覆原勝利后，由于我是覆原的RDS全備文件，所以我們自建的Mysql數據庫密鑰會被蓋住成RDS的數據庫密鑰，假如健忘密鑰，可以暫時在Mysql部署文件中參加skip-grant-tables部署，無密鑰進入數據庫，驗證數據覆原場合。[roottest2 ~]# vim etcmy.cnf…skip-grant-tables[roottest2 ~]# systemctl start mysqld[roottest2 ~]# mysql -urootWele to the MySQL monitor. Commands end ith ; or \g.Your MySQL connection is 3Server version 5.7.30 MySQL Community Server (GPL)Copyright (c) 2024, 2024, Oracle andor its affiliates. All rights reserved.Oracle is a registered trademark of Oracle Corporation andor itsaffiliates. Other names may be trademarks of their respectiveoners.Type ‘help;’ or ‘\h’ for help. Type ‘\c’ to clear the current input statement.mysql> use crmdb;Reading table information for pletion of table and column namesYou 運彩 足球 延長can turn off this feature to get a quicker startup ith -ADatabase changedmysql> sho tables;+————————+| Tables_in_crmdb |+————————+| 產物表_rso_product || calllist || cus_manage_set || dictionary || importtel || imptable || imptable2 || log || rso_product || rxpbls || sys_app_user || sys_dept || sys_dictionaries || sys_gl_qx || sys_menu || sys_role || sys_user || sys_user_qx || tb_pictures || test || tmp_ybc || user |mysql> select * from user;+——–+———-+———-+——+——+————+| user | userName | passord | name | sex | department |+——–+———-+———-+——+——+————+| 1 | admin | admin | NULL | NULL | NULL || 2 | 111111 | 111111 | NULL | NULL | NULL || 3 | 222222 | 222222 | NULL | NULL | NULL || 4 | 333333 | 333333 | NULL | NULL | NULL || 5 | 444444 | 444444 | NULL | NULL | NULL || 6 | 555555 | 555555 | NULL | NULL | NULL |+——–+———-+———-+——+——+————+6 ros in set (0.00 sec) 數據覆原勝利！！！

假如你覺得這篇詞章還不錯，就請動動你的發達手為本文留個言，點個在看，或者轉發一下吧，由於這將是我連續輸出更多優質詞章的最強動力！

運彩討論區 Tags:, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ,
GIF图片        
Floating Ad