Using MySQL Enterprise Backup Tools

最新推荐文章于 2025-06-13 07:00:54 发布
最新推荐文章于 2025-06-13 07:00:54 发布
阅读量1.3k 收藏 2
点赞数
CC 4.0 BY-SA版权
文章标签： 数据库 运维
版权声明：本文为博主原创文章，遵循 CC 4.0 BY-SA 版权协议，转载请附上原文出处链接和本声明。
本文链接：https://blog.csdn.net/weixin_34168880/article/details/85069156
本文详细介绍了MySQLEnterpriseBackup的安装步骤及如何进行全量备份、增量备份，并提供了备份脚本及恢复流程。

摘要生成于 C知道 ，由 DeepSeek-R1 满血版支持， 前往体验 >

本文主要介绍MySQL Enterprise Backup的安装以及使用。

1、安装

从官方网站下载MySQL Enterprise Backup安装包，推荐下载rpm软件包。

[root@mydb01 ~]# rpm -qpl meb-4.1.1-el7.x86_64.rpm 
warning: meb-4.1.1-el7.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 5072e1f5: NOKEY
/opt
/opt/mysql
/opt/mysql/meb-4.1
/opt/mysql/meb-4.1/LICENSE.mysql
/opt/mysql/meb-4.1/LICENSE.third_party
/opt/mysql/meb-4.1/README.txt
/opt/mysql/meb-4.1/bin/mysqlbackup
/opt/mysql/meb-4.1/manual.html
/opt/mysql/meb-4.1/mvl.css
[root@mydb01 ~]# yum -y install meb-4.1.1-el7.x86_64.rpm
[root@mydb01 ~]# vi .bash_profile
export PATH=$PATH:$HOME/bin:/opt/mysql/meb-4.1/bin

2、备份

如果不想用root用户进行备份操作，则使用下面的语句创建专用的备份用户并赋予相关权限：

mysql> CREATE USER 'bakuser'@'localhost' IDENTIFIED BY 'abcABC@12';
mysql> GRANT RELOAD ON *.* TO 'bakuser'@'localhost';
mysql> GRANT CREATE, INSERT, DROP, UPDATE ON mysql.ibbackup_binlog_marker TO 'bakuser'@'localhost';
mysql> GRANT CREATE, INSERT, DROP, UPDATE ON mysql.backup_progress TO 'bakuser'@'localhost';
mysql> GRANT CREATE, INSERT, SELECT, DROP, UPDATE ON mysql.backup_history TO 'bakuser'@'localhost';
mysql> GRANT REPLICATION CLIENT ON *.* TO 'bakuser'@'localhost';
mysql> GRANT SUPER ON *.* TO 'bakuser'@'localhost';
mysql> GRANT CREATE TEMPORARY TABLES ON mysql.* TO 'bakuser'@'localhost';
mysql> FLUSH PRIVILEGES;

2.1 全量备份

[root@mydb01 ~]# mysqlbackup --defaults-file=/etc/my.cnf --user=root --password --host=127.0.0.1 --with-timestamp --backup-dir=/u02/full backup-and-apply-log
MySQL Enterprise Backup version 4.1.1 Linux-4.1.12-61.1.16.el7uek.x86_64-x86_64 [2018/04/24 07:54:03] 
Copyright (c) 2003, 2018, Oracle and/or its affiliates. All Rights Reserved.
[Build ID : 12942442.c465cfd7261c781502aec204494abf138f9d59e6]

180627 11:00:02 MAIN    INFO: A thread created with Id '140048649107264' 
180627 11:00:02 MAIN    INFO: Starting with following command line ...
 mysqlbackup --defaults-file=/etc/my.cnf --user=root --password 
        --host=127.0.0.1 --backup-dir=/u02/full backup-and-apply-log 

180627 11:00:02 MAIN    INFO: 
Enter password: 
180627 11:00:04 MAIN    INFO: Not using SSL.
180627 11:00:04 MAIN    INFO: MySQL server version is '5.7.22-log'
180627 11:00:04 MAIN    INFO: MySQL server compile os version is 'Linux'
180627 11:00:04 MAIN    INFO: SSL: SSL version used for connection is 'TLSv1.1'
180627 11:00:04 MAIN    INFO: Got some server configuration information from running server.

180627 11:00:04 MAIN    INFO: Server system variable 'old_alter_table' was set to '0'. Setting it to '1'.
IMPORTANT: Please check that mysqlbackup run completes successfully.
           At the end of a successful 'backup-and-apply-log' run mysqlbackup
           prints "mysqlbackup completed OK!".

180627 11:00:05 MAIN    INFO: 0 active keyring plugins found.
180627 11:00:05 MAIN    INFO: KEF target path:'/u02/full/2018-06-27_11-00-05/meta/keyring_kef'
180627 11:00:05 MAIN    INFO: TDE Keyring service initialized.
180627 11:00:05 MAIN    INFO: MEB logfile created at /u02/full/2018-06-27_11-00-05/meta/MEB_2018-06-27.11-00-05_backup_apply_log.log

--------------------------------------------------------------------
                       Server Repository Options:
--------------------------------------------------------------------
  datadir                        = /var/lib/mysql/
  innodb_data_home_dir           = 
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /var/lib/mysql/
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_undo_directory          = /var/lib/mysql/
  innodb_undo_tablespaces        = 0
  innodb_undo_logs               = 128
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = 16384
  innodb_checksum_algorithm      = crc32

--------------------------------------------------------------------
                       Backup Config Options:
--------------------------------------------------------------------
  datadir                        = /u02/full/2018-06-27_11-00-05/datadir
  innodb_data_home_dir           = /u02/full/2018-06-27_11-00-05/datadir
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /u02/full/2018-06-27_11-00-05/datadir
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_undo_directory          = /u02/full/2018-06-27_11-00-05/datadir
  innodb_undo_tablespaces        = 0
  innodb_undo_logs               = 128
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = 16384
  innodb_checksum_algorithm      = crc32

180627 11:00:05 MAIN    INFO: Unique generated backup id for this is 1530068404×××868

180627 11:00:05 MAIN    INFO: Creating 14 buffers each of size 16777216.
180627 11:00:05 MAIN    INFO: Full Backup operation starts with following threads
                1 read-threads    6 process-threads    1 write-threads
180627 11:00:05 MAIN    INFO: Found checkpoint at lsn 75536184611.
180627 11:00:05 MAIN    INFO: Starting log scan from lsn = 75536184320 at offset = 41777664 and checkpoint = 75536184611 in file /var/lib/mysql/ib_logfile0.
180627 11:00:05 MAIN    INFO: System tablespace file format is Antelope.
180627 11:00:05 MAIN    INFO: Starting to copy all innodb files...
180627 11:00:05 RDR1    INFO: A thread created with Id '140048264505088' 
180627 11:00:05 PCR2    INFO: A thread created with Id '140048247719680' 
180627 11:00:05 PCR3    INFO: A thread created with Id '140048239326976' 
180627 11:00:05 PCR5    INFO: A thread created with Id '140048222541568' 
180627 11:00:05 PCR4    INFO: A thread created with Id '140048230934272' 
180627 11:00:05 WTR1    INFO: A thread created with Id '140048003491584' 
180627 11:00:05 RLR1    INFO: A thread created with Id '140047995098880' 
180627 11:00:05 PCR6    INFO: A thread created with Id '140048011884288' 
180627 11:00:05 PCR1    INFO: A thread created with Id '140048256112384' 
180627 11:00:05 RLW1    INFO: A thread created with Id '140047986706176' 
180627 11:00:05 RLP1    INFO: A thread created with Id '140047978313472' 
180627 11:00:05 RDR1    INFO: Copying /var/lib/mysql/ibdata1 (Barracuda file format).
......
180627 11:15:43 RDR1    INFO: Completed the copy of binlog files...
180627 11:15:43 RDR1    INFO: Opening backup source directory '/var/lib/mysql'
180627 11:15:43 RDR1    INFO: Starting to backup all non-innodb files  in 
        subdirectories of '/var/lib/mysql'
180627 11:15:43 RDR1    INFO: Copying the database directory '.oracle_jre_usage'
180627 11:15:43 RDR1    INFO: Copying the database directory 'hjy_zxzy'
180627 11:15:43 RDR1    INFO: Copying the database directory 'lepus'
180627 11:15:43 RDR1    INFO: Copying the database directory 'mysql'
180627 11:15:44 RDR1    INFO: Copying the database directory 'performance_schema'
180627 11:15:44 RDR1    INFO: Copying the database directory 'sys'
180627 11:15:44 RDR1    INFO: Completing the copy of all non-innodb files.
180627 11:15:44 RDR1    INFO: Requesting completion of redo log copy. Rapid: 0
180627 11:15:44 RLR1    INFO: Signaled '1' to complete log copy.
180627 11:15:44 RLR1    INFO: Signaled '1' to complete log copy.
180627 11:15:44 RLR1    INFO: Signaled '1' to complete log copy.
180627 11:15:44 RLR1    INFO: Redo log reader waited = 913270.00 ms for logs to generate.
180627 11:15:44 RLW1    INFO: A copied database page was modified at 75536184611.
          (This is the highest lsn found on page)
          Scanned log up to lsn 75536184696.
          Was able to parse the log up to lsn 75536184696.
180627 11:15:45 RDR1    INFO: All tables unlocked
180627 11:15:45 RDR1    INFO: All MySQL tables were locked for 2.455 seconds.
180627 11:15:45 RDR1    INFO: Setting server system variable 'old_alter_table' back to '0'.
180627 11:15:45 RDR1    INFO: Reading all global variables from the server.
180627 11:15:45 RDR1    INFO: Completed reading of all global variables from the server.
180627 11:15:45 RDR1    INFO: Writing config file for server '5.7.22-log'.
180627 11:15:45 RDR1    INFO: Creating server config files server-my.cnf and server-all.cnf in /u02/full/2018-06-27_11-00-05
180627 11:15:45 MAIN    INFO: Full Backup operation completed successfully.
180627 11:15:45 MAIN    INFO: Backup created in directory '/u02/full/2018-06-27_11-00-05'
180627 11:15:45 MAIN    INFO: MySQL binlog position: filename master-bin.005828, position 154

-------------------------------------------------------------
   Parameters Summary         
-------------------------------------------------------------
   Start LSN                  : 75536184320
   End LSN                    : 75536184696
-------------------------------------------------------------

180627 11:15:45 MAIN    INFO: Creating 14 buffers each of size 65536.
180627 11:15:45 MAIN    INFO: Apply-log operation starts with following threads
                1 read-threads    1 process-threads    6 apply-threads
180627 11:15:45 MAIN    INFO: Using up to 100 MB of memory.
180627 11:15:45 MAIN    INFO: ibbackup_logfile's creation parameters:
          start lsn 75536184320, end lsn 75536184696,
          start checkpoint 75536184611.
180627 11:15:47 ALW1    INFO: A thread created with Id '140047978313472' 
180627 11:15:47 ALW3    INFO: A thread created with Id '140047995098880' 
180627 11:15:47 ALW4    INFO: A thread created with Id '140048003491584' 
180627 11:15:47 ALW2    INFO: A thread created with Id '140047986706176' 
180627 11:15:47 RDR1    INFO: A thread created with Id '140048500758272' 
180627 11:15:47 ALW6    INFO: A thread created with Id '140048509150976' 
180627 11:15:47 ALW5    INFO: A thread created with Id '140048517543680' 
180627 11:15:47 PCR1    INFO: A thread created with Id '140048492365568' 
180627 11:15:47 PCR1    INFO: InnoDB: Doing recovery: scanned up to log sequence number 75536184696.
180627 11:15:47 PCR1    INFO: 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 99 
180627 11:15:47 PCR1    INFO: InnoDB: Setting log file size to 50331648.
180627 11:15:47 PCR1    INFO: InnoDB: Setting log file size to 50331648.
180627 11:15:47 PCR1    INFO: We were able to parse ibbackup_logfile up to
          lsn 75536184696.
180627 11:15:47 PCR1    INFO: Last MySQL binlog file position 0 154, file name master-bin.005828
180627 11:15:47 PCR1    INFO: The first data file is '/u02/full/2018-06-27_11-00-05/datadir/ibdata1'
                              and the new created log files are at '/u02/full/2018-06-27_11-00-05/datadir'
180627 11:15:47 MAIN    INFO: Apply-log operation completed successfully.
180627 11:15:47 MAIN    INFO: Full backup prepared for recovery successfully.

mysqlbackup completed OK!

--defaults-file：指定MySQL的配置文件
--user：指定备份用户
--password：备份用户的密码
--host：MySQL实例运行的主机
--backup-dir：MySQL备份文件的存放路径
--with-timestam：加上时间戳

2.2 增量备份

[root@mydb01 ~]# mysqlbackup --defaults-file=/etc/my.cnf --user=root --password --host=127.0.0.1 --with-timestamp --incremental-backup-dir=/u02/incr --start-lsn=75536184696 --incremental backup
MySQL Enterprise Backup version 4.1.1 Linux-4.1.12-61.1.16.el7uek.x86_64-x86_64 [2018/04/24 07:54:03] 
Copyright (c) 2003, 2018, Oracle and/or its affiliates. All Rights Reserved.
[Build ID : 12942442.c465cfd7261c781502aec204494abf138f9d59e6]

180627 11:47:55 MAIN    INFO: A thread created with Id '140596443768640' 
180627 11:47:55 MAIN    INFO: Starting with following command line ...
 mysqlbackup --defaults-file=/etc/my.cnf --user=root --password 
        --host=127.0.0.1 --incremental-backup-dir=/u02/incr 
        --start-lsn=75536184696 --incremental backup 

180627 11:47:55 MAIN    INFO: 
Enter password: 
180627 11:47:58 MAIN    INFO: Not using SSL.
180627 11:47:58 MAIN    INFO: MySQL server version is '5.7.22-log'
180627 11:47:58 MAIN    INFO: MySQL server compile os version is 'Linux'
180627 11:47:58 MAIN    INFO: SSL: SSL version used for connection is 'TLSv1.1'
180627 11:47:58 MAIN    INFO: Got some server configuration information from running server.

180627 11:47:58 MAIN    INFO: Server system variable 'old_alter_table' was set to '0'. Setting it to '1'.
180627 11:47:58 MAIN WARNING: Binlog files will not be copied for this backup as --incremental-base is not specified.
IMPORTANT: Please check that mysqlbackup run completes successfully.
           At the end of a successful 'backup' run mysqlbackup
           prints "mysqlbackup completed OK!".

180627 11:47:58 MAIN    INFO: 0 active keyring plugins found.
180627 11:47:58 MAIN    INFO: KEF target path:'/u02/incr/2018-06-27.11-47-58/meta/keyring_kef'
180627 11:47:58 MAIN    INFO: TDE Keyring service initialized.
180627 11:47:58 MAIN    INFO: MEB logfile created at /u02/incr/2018-06-27.11-47-58/meta/MEB_2018-06-27.11-47-58_inc_backup.log

--------------------------------------------------------------------
                       Server Repository Options:
--------------------------------------------------------------------
  datadir                        = /var/lib/mysql/
  innodb_data_home_dir           = 
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /var/lib/mysql/
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_undo_directory          = /var/lib/mysql/
  innodb_undo_tablespaces        = 0
  innodb_undo_logs               = 128
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = 16384
  innodb_checksum_algorithm      = crc32

--------------------------------------------------------------------
                       Backup Config Options:
--------------------------------------------------------------------
  datadir                        = /u02/incr/2018-06-27.11-47-58/datadir
  innodb_data_home_dir           = /u02/incr/2018-06-27.11-47-58/datadir
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /u02/incr/2018-06-27.11-47-58/datadir
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_undo_directory          = /u02/incr/2018-06-27.11-47-58/datadir
  innodb_undo_tablespaces        = 0
  innodb_undo_logs               = 128
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = 16384
  innodb_checksum_algorithm      = crc32

180627 11:47:58 MAIN    INFO: Unique generated backup id for this is 15300712787259227

180627 11:47:58 MAIN    INFO: Creating 14 buffers each of size 17301504.
180627 11:47:58 MAIN    INFO: Incremental Backup operation starts with following threads
                1 read-threads    6 process-threads    1 write-threads
180627 11:47:58 MAIN    INFO: Found checkpoint at lsn 75536192617.
180627 11:47:58 MAIN    INFO: Starting log scan from lsn = 75536192512 at offset = 41785856 and checkpoint = 75536192617 in file /var/lib/mysql/ib_logfile0.
180627 11:47:58 MAIN    INFO: System tablespace file format is Antelope.
180627 11:47:58 MAIN    INFO: Starting to copy all innodb files...
180627 11:47:58 RDR1    INFO: A thread created with Id '140596051826432' 
180627 11:47:58 PCR1    INFO: A thread created with Id '140596043433728' 
180627 11:47:58 WTR1    INFO: A thread created with Id '140595922188032' 
180627 11:47:58 RDR1    INFO: Copying /var/lib/mysql/ibdata1 (Barracuda file format).
180627 11:47:58 RLW1    INFO: A thread created with Id '140595905402624' 
180627 11:47:58 PCR2    INFO: A thread created with Id '140596035041024' 
180627 11:47:58 PCR5    INFO: A thread created with Id '140595938973440' 
180627 11:47:58 PCR4    INFO: A thread created with Id '140595947366144' 
180627 11:47:58 RLP1    INFO: A thread created with Id '140595553105664' 
180627 11:47:58 PCR6    INFO: A thread created with Id '140595930580736' 
180627 11:47:58 RLR1    INFO: A thread created with Id '140595913795328' 
180627 11:47:58 PCR3    INFO: A thread created with Id '140595955758848' 
......
180627 11:53:07 RDR1    INFO: Completing the copy of innodb files.
180627 11:53:07 RDR1    INFO: Requesting a dump of the InnoDB buffer pool
180627 11:53:07 RDR1    INFO: Waiting for the dump of the InnoDB buffer pool to complete
180627 11:53:07 RDR1    INFO: The dump of the InnoDB buffer pool completed
180627 11:53:07 RDR1    INFO: Preparing to lock tables: Connected to mysqld server.
180627 11:53:07 RDR1    INFO: Starting to lock all the tables...
180627 11:53:07 RDR1    INFO: Flushing the default MyISAM key cache.
180627 11:53:07 RDR1    INFO: All tables are locked and flushed to disk
180627 11:53:07 RDR1    INFO: Completed the copy of binlog files...
180627 11:53:07 RDR1    INFO: Opening backup source directory '/var/lib/mysql'
180627 11:53:07 RDR1    INFO: Starting to backup all non-innodb files  in 
        subdirectories of '/var/lib/mysql'
180627 11:53:07 RDR1    INFO: Copying the database directory '.oracle_jre_usage'
180627 11:53:07 RDR1    INFO: Copying the database directory 'hjy_zxzy'
180627 11:53:08 RDR1    INFO: Copying the database directory 'lepus'
180627 11:53:08 RDR1    INFO: Copying the database directory 'mysql'
180627 11:53:08 RDR1    INFO: Copying the database directory 'performance_schema'
180627 11:53:08 RDR1    INFO: Copying the database directory 'sys'
180627 11:53:08 RDR1    INFO: Completing the copy of all non-innodb files.
180627 11:53:08 RDR1    INFO: Requesting completion of redo log copy. Rapid: 0
180627 11:53:08 RLR1    INFO: Signaled '1' to complete log copy.
180627 11:53:08 RLR1    INFO: Signaled '1' to complete log copy.
180627 11:53:08 RLR1    INFO: Signaled '1' to complete log copy.
180627 11:53:08 RLR1    INFO: Redo log reader waited = 303270.00 ms for logs to generate.
180627 11:53:08 RLW1    INFO: A copied database page was modified at 75536192493.
          (This is the highest lsn found on page)
          Scanned log up to lsn 75536192626.
          Was able to parse the log up to lsn 75536192626.
180627 11:53:09 RDR1    INFO: All tables unlocked
180627 11:53:09 RDR1    INFO: All MySQL tables were locked for 1.994 seconds.
180627 11:53:09 RDR1    INFO: Setting server system variable 'old_alter_table' back to '0'.
180627 11:53:09 RDR1    INFO: Reading all global variables from the server.
180627 11:53:09 RDR1    INFO: Completed reading of all global variables from the server.
180627 11:53:09 RDR1    INFO: Writing config file for server '5.7.22-log'.
180627 11:53:09 RDR1    INFO: Creating server config files server-my.cnf and server-all.cnf in /u02/incr/2018-06-27.11-47-58
180627 11:53:09 MAIN    INFO: Incremental Backup operation completed successfully.
180627 11:53:09 MAIN    INFO: Backup created in directory '/u02/incr/2018-06-27.11-47-58'
180627 11:53:09 MAIN    INFO: Backup contains changes from lsn 75536184697 to lsn 75536192626
180627 11:53:09 MAIN    INFO: MySQL binlog position: filename master-bin.005828, position 809

-------------------------------------------------------------
   Parameters Summary         
-------------------------------------------------------------
   Start LSN                  : 75536184697
   End LSN                    : 75536192626
-------------------------------------------------------------

mysqlbackup completed OK! with 1 warnings

--defaults-file：指定MySQL的配置文件
--user：指定备份用户
--password：备份用户的密码
--host：MySQL实例运行的主机
--incremental-backup-dir：MySQL增量备份文件的存放路径
--with-timestam：加上时间戳
--start-lsn：指上次备份完成后的LSN，可以在备份目录里的meta/backup_variables.txt文件中找到。
在初始备份过程中，系统会在mysql数据库中创建backup_history以及backup_progress两张表，备份的相关信息都会记录在这两张表中。

3、恢复

3.1 合并增量备份

如果mysql的备份有全量备份以及增量备份，在恢复之前必须整合增量备份到全量备份。

[root@mydb01 ~]# mysqlbackup --incremental-backup-dir=/u02/incr/2018-06-27.11-47-58 --backup-dir=/u02/full/2018-06-27_11-00-05/ apply-incremental-backup
MySQL Enterprise Backup version 4.1.1 Linux-4.1.12-61.1.16.el7uek.x86_64-x86_64 [2018/04/24 07:54:03] 
Copyright (c) 2003, 2018, Oracle and/or its affiliates. All Rights Reserved.
[Build ID : 12942442.c465cfd7261c781502aec204494abf138f9d59e6]

180627 12:30:14 MAIN    INFO: A thread created with Id '140486177048384' 
180627 12:30:14 MAIN    INFO: Starting with following command line ...
 mysqlbackup --incremental-backup-dir=/u02/incr/2018-06-27.11-47-58
        --backup-dir=/u02/full/2018-06-27_11-00-05/ apply-incremental-backup 

180627 12:30:14 MAIN    INFO: 
IMPORTANT: Please check that mysqlbackup run completes successfully.
           At the end of a successful 'apply-incremental-backup' run mysqlbackup
           prints "mysqlbackup completed OK!".

180627 12:30:14 MAIN    INFO: MySQL server version is '5.7.22-log'
180627 12:30:14 MAIN    INFO: Restoring ...5.7.22-log version
180627 12:30:14 MAIN    INFO: MySQL server version is '5.7.22-log'
180627 12:30:14 MAIN    INFO: Restoring ...5.7.22-log version
180627 12:30:14 MAIN    INFO: KEF source path:'/u02/incr/meta'
180627 12:30:14 MAIN    INFO: KEF target path:'/u02/full/20180627/meta'
180627 12:30:14 MAIN    INFO: TDE Keyring service initialized.
180627 12:30:14 MAIN    INFO: MEB logfile created at /u02/full/20180627/meta/MEB_2018-06-27.12-30-14_apply_inc.log

--------------------------------------------------------------------
                       Backup Config Options:
--------------------------------------------------------------------
  datadir                        = /u02/full/20180627/datadir
  innodb_data_home_dir           = /u02/full/20180627/datadir
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /u02/full/20180627/datadir
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = 16384
  innodb_checksum_algorithm      = crc32

180627 12:30:14 MAIN    INFO: Creating 14 buffers each of size 17301504.
180627 12:30:14 MAIN    INFO: Apply-Incremental-Pages operation starts with following threads
                1 read-threads    1 write-threads
180627 12:30:14 MAIN    INFO: Starting to copy all innodb files...
180627 12:30:14 MAIN    INFO: Starting deletion of obsolete ibd files in backup-dir...
180627 12:30:14 MAIN    INFO: Deleting dropped ibd files.
180627 12:30:14 MAIN    INFO: Deletion of obsolete ibd files in backup-dir is completed.
180627 12:30:14 MAIN    INFO: Deleting non-innodb files in backup-dir...
180627 12:30:14 RDR1    INFO: A thread created with Id '140485805418240' 
180627 12:30:14 WTR1    INFO: A thread created with Id '140485797025536' 
180627 12:30:14 RDR1    INFO: Applying diff pages  from `/u02/incr/datadir/ibdata1` to `/u02/full/20180627/datadir/ibdata1`.
180627 12:30:14 RDR1    INFO: Applying incremental pages to innodb data files...
180627 12:30:14 RDR1    INFO: Applying diff pages  from `/u02/incr/datadir/lepus/chapter.ibd` to `/u02/full/20180627/datadir/lepus/chapter.ibd`.
180627 12:30:14 RDR1    INFO: Applying diff pages  from `/u02/incr/datadir/mysql/innodb_index_stats.ibd` to `/u02/full/20180627/datadir/mysql/innodb_index_stats.ibd`.
180627 12:30:14 RDR1    INFO: Applying diff pages  from `/u02/incr/datadir/mysql/innodb_table_stats.ibd` to `/u02/full/20180627/datadir/mysql/innodb_table_stats.ibd`.
180627 12:30:14 RDR1    INFO: This incremental backup does not have binlogs. Applying this incremental backups ignore binlogs for all .
180627 12:30:14 RDR1    INFO: Completed the copy of binlog files...
180627 12:30:14 RDR1    INFO: Starting to copy all non-innodb files in 
        subdirectories of '/u02/incr/datadir'
180627 12:30:14 RDR1    INFO: Copying the database directory '.oracle_jre_usage'
180627 12:30:14 RDR1    INFO: Copying the database directory 'hjy_zxzy'
180627 12:30:14 RDR1    INFO: Copying the database directory 'lepus'
180627 12:30:14 RDR1    INFO: Copying the database directory 'mysql'
180627 12:30:14 RDR1    INFO: Copying the database directory 'performance_schema'
180627 12:30:14 RDR1    INFO: Copying the database directory 'sys'
180627 12:30:14 RDR1    INFO: Completing the copy of all non-innodb files.
180627 12:30:14 RDR1    INFO: Copying server configuration files to backup_dir.
180627 12:30:14 MAIN    INFO: No Keyring file to process.
180627 12:30:14 MAIN    INFO: Apply-Incremental-Pages operation completed successfully.

180627 12:30:14 MAIN    INFO: Creating 14 buffers each of size 65536.
180627 12:30:14 MAIN    INFO: Apply-log operation starts with following threads
                1 read-threads    1 process-threads    6 apply-threads
180627 12:30:14 MAIN    INFO: Using up to 100 MB of memory.
180627 12:30:14 MAIN    INFO: ibbackup_logfile's creation parameters:
          start lsn 75536192512, end lsn 75536192626,
          start checkpoint 75536192617.
180627 12:30:15 ALW1    INFO: A thread created with Id '140485797025536' 
180627 12:30:15 ALW2    INFO: A thread created with Id '140485805418240' 
180627 12:30:15 ALW3    INFO: A thread created with Id '140486043895552' 
180627 12:30:15 ALW6    INFO: A thread created with Id '140486018717440' 
180627 12:30:15 ALW4    INFO: A thread created with Id '140486035502848' 
180627 12:30:15 ALW5    INFO: A thread created with Id '140486027110144' 
180627 12:30:15 PCR1    INFO: A thread created with Id '140486001932032' 
180627 12:30:15 RDR1    INFO: A thread created with Id '140486010324736' 
180627 12:30:15 PCR1    INFO: InnoDB: Doing recovery: scanned up to log sequence number 75536192626.
180627 12:30:15 PCR1    INFO: 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 99 
180627 12:30:15 PCR1    INFO: InnoDB: Setting log file size to 50331648.
180627 12:30:15 PCR1    INFO: InnoDB: Setting log file size to 50331648.
180627 12:30:16 PCR1    INFO: We were able to parse ibbackup_logfile up to
          lsn 75536192626.
180627 12:30:16 PCR1    INFO: Last MySQL binlog file position 0 809, file name master-bin.005828
180627 12:30:16 PCR1    INFO: The first data file is '/u02/full/20180627/datadir/ibdata1'
                              and the new created log files are at '/u02/full/20180627/datadir'
180627 12:30:16 MAIN    INFO: No Keyring file to process.
180627 12:30:16 MAIN    INFO: Apply-log operation completed successfully.
180627 12:30:16 MAIN    INFO: Full backup prepared for recovery successfully.

mysqlbackup completed OK!

--incremental-backup-dir：指增量备份的目录
--backup-dir：指全量备份的目录

3.2 使用全备份恢复

[root@mydb01 lib]# mysqlbackup --user=root --datadir=/var/lib/mysql --backup-dir=/u02/full/2018-06-27_11-00-05 copy-back
MySQL Enterprise Backup version 4.1.1 Linux-4.1.12-61.1.16.el7uek.x86_64-x86_64 [2018/04/24 07:54:03] 
Copyright (c) 2003, 2018, Oracle and/or its affiliates. All Rights Reserved.
[Build ID : 12942442.c465cfd7261c781502aec204494abf138f9d59e6]

180627 12:32:19 MAIN    INFO: A thread created with Id '140697770657600' 
180627 12:32:19 MAIN    INFO: Starting with following command line ...
 mysqlbackup --user=root --datadir=/var/lib/mysql 
        --backup-dir=/u02/full/2018-06-27_11-00-05 copy-back 

180627 12:32:19 MAIN    INFO: 
IMPORTANT: Please check that mysqlbackup run completes successfully.
           At the end of a successful 'copy-back' run mysqlbackup
           prints "mysqlbackup completed OK!".

180627 12:32:19 MAIN    INFO: MySQL server version is '5.7.22-log'
180627 12:32:19 MAIN    INFO: Restoring ...5.7.22-log version
180627 12:32:19 MAIN WARNING: If you restore to a server of a different version, the innodb_data_file_path parameter might have a different default. In that case you need to add 'innodb_data_file_path=ibdata1:12M:autoextend' to the target server configuration.
180627 12:32:19 MAIN WARNING: If you restore to a server of a different version, the innodb_log_files_in_group parameter might have a different default. In that case you need to add 'innodb_log_files_in_group=2' to the target server configuration.
180627 12:32:19 MAIN WARNING: If you restore to a server of a different version, the innodb_log_file_size parameter might have a different default. In that case you need to add 'innodb_log_file_size=50331648' to the target server configuration.
180627 12:32:19 MAIN    INFO: KEF source path:'/u02/full/2018-06-27_11-00-05/meta'
180627 12:32:19 MAIN    INFO: KEF target path:'/var/lib/mysql'
180627 12:32:19 MAIN    INFO: TDE Keyring service initialized.
180627 12:32:19 MAIN    INFO: MEB logfile created at /u02/full/2018-06-27_11-00-05/meta/MEB_2018-06-27.12-32-19_copy_back.log

--------------------------------------------------------------------
                       Server Repository Options:
--------------------------------------------------------------------
  datadir                        = /var/lib/mysql
  innodb_data_home_dir           = /var/lib/mysql
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /var/lib/mysql
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = Null
  innodb_checksum_algorithm      = crc32

--------------------------------------------------------------------
                       Backup Config Options:
--------------------------------------------------------------------
  datadir                        = /u02/full/2018-06-27_11-00-05/datadir
  innodb_data_home_dir           = /u02/full/2018-06-27_11-00-05/datadir
  innodb_data_file_path          = ibdata1:12M:autoextend
  innodb_log_group_home_dir      = /u02/full/2018-06-27_11-00-05/datadir
  innodb_log_files_in_group      = 2
  innodb_log_file_size           = 50331648
  innodb_buffer_pool_filename    = ib_buffer_pool
  innodb_page_size               = 16384
  innodb_checksum_algorithm      = crc32

180627 12:32:19 MAIN    INFO: Creating 14 buffers each of size 16777216.
180627 12:32:19 MAIN    INFO: Copy-back operation starts with following threads
                1 read-threads    1 write-threads
180627 12:32:19 MAIN    INFO: Starting to copy all innodb files...
180627 12:32:19 RDR1    INFO: A thread created with Id '140697406367488' 
180627 12:32:19 WTR1    INFO: A thread created with Id '140697397974784' 
180627 12:32:19 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/ibdata1.
......
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/lepus/questions.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/engine_cost.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/gtid_executed.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/innodb_index_stats.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/innodb_table_stats.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/server_cost.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/slave_master_info.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/slave_relay_log_info.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/mysql/slave_worker_info.ibd.
180627 12:41:55 RDR1    INFO: Copying /u02/full/2018-06-27_11-00-05/datadir/sys/sys_config.ibd.
180627 12:41:55 RDR1    INFO: Could not find binlog index file. binlogs will not be copied for this backup.
 Point-In-Time-Recovery will not be possible.
 If this is online backup then server may not have started with --log-bin.
 You may specify its location with --log-bin-index option.
180627 12:41:55 RDR1    INFO: Completed the copy of binlog files...
180627 12:41:55 RDR1    INFO: Copying the database directory '.oracle_jre_usage'
180627 12:41:55 RDR1    INFO: Copying the database directory 'hjy_zxzy'
180627 12:41:55 RDR1    INFO: Copying the database directory 'lepus'
180627 12:41:55 RDR1    INFO: Copying the database directory 'mysql'
180627 12:41:55 RDR1    INFO: Copying the database directory 'performance_schema'
180627 12:41:55 RDR1    INFO: Copying the database directory 'sys'
180627 12:41:55 RDR1    INFO: Completing the copy of all non-innodb files.
180627 12:41:55 RDR1    INFO: Copying the log file 'ib_logfile0'
180627 12:41:55 RDR1    INFO: Copying the log file 'ib_logfile1'
180627 12:41:55 MAIN    INFO: No Keyring file to process.
180627 12:41:55 MAIN    INFO: MySQL server version is '5.7.22-log'
180627 12:41:55 MAIN    INFO: MySQL server compile os version is 'Linux'
180627 12:41:55 MAIN    INFO: Writing config file for server '5.7.22-log'.
180627 12:41:55 MAIN    INFO: Creating server config files server-my.cnf and server-all.cnf in /var/lib/mysql
180627 12:41:55 MAIN    INFO: Variable 'datadir'='/var/lib/mysql/'->'/var/lib/mysql' option 'datadir' type 0
180627 12:41:55 MAIN    INFO: Variable 'datadir'='/var/lib/mysql/'->'/var/lib/mysql' option 'datadir' type 0
180627 12:41:55 MAIN    INFO: Variable 'innodb_buffer_pool_filename'='ib_buffer_pool'->'ib_buffer_pool' option 'innodb_buffer_pool_filename' type 9
180627 12:41:55 MAIN    INFO: Variable 'innodb_buffer_pool_filename'='ib_buffer_pool'->'ib_buffer_pool' option 'innodb_buffer_pool_filename' type 9
180627 12:41:55 MAIN    INFO: Variable 'innodb_checksum_algorithm'='crc32'->'crc32' option 'innodb_checksum_algorithm' type 11
180627 12:41:55 MAIN    INFO: Variable 'innodb_checksum_algorithm'='crc32'->'crc32' option 'innodb_checksum_algorithm' type 11
180627 12:41:55 MAIN    INFO: Variable 'innodb_checksums'='ON'->'ON' option 'innodb_checksums' type 12
180627 12:41:55 MAIN    INFO: Variable 'innodb_checksums'='ON'->'ON' option 'innodb_checksums' type 12
180627 12:41:55 MAIN    INFO: Variable 'innodb_data_file_path'='ibdata1:12M:autoextend'->'ibdata1:12M:autoextend' option 'innodb_data_file_path' type 2
180627 12:41:55 MAIN    INFO: Variable 'innodb_data_file_path'='ibdata1:12M:autoextend'->'ibdata1:12M:autoextend' option 'innodb_data_file_path' type 2
180627 12:41:55 MAIN    INFO: Variable 'innodb_data_home_dir'=''->'/var/lib/mysql' option 'innodb_data_home_dir' type 1
180627 12:41:55 MAIN    INFO: Variable 'innodb_log_file_size'='50331648'->'50331648' option 'innodb_log_file_size' type 5
180627 12:41:55 MAIN    INFO: Variable 'innodb_log_file_size'='50331648'->'50331648' option 'innodb_log_file_size' type 5
180627 12:41:55 MAIN    INFO: Variable 'innodb_log_files_in_group'='2'->'2' option 'innodb_log_files_in_group' type 4
180627 12:41:55 MAIN    INFO: Variable 'innodb_log_files_in_group'='2'->'2' option 'innodb_log_files_in_group' type 4
180627 12:41:55 MAIN    INFO: Variable 'innodb_log_group_home_dir'='./'->'/var/lib/mysql' option 'innodb_log_group_home_dir' type 3
180627 12:41:55 MAIN    INFO: Variable 'innodb_log_group_home_dir'='./'->'/var/lib/mysql' option 'innodb_log_group_home_dir' type 3
180627 12:41:55 MAIN    INFO: Variable 'innodb_page_size'='16384'->'16384' option 'innodb_page_size' type 10
180627 12:41:55 MAIN    INFO: Variable 'innodb_page_size'='16384'->'16384' option 'innodb_page_size' type 10
180627 12:41:55 MAIN    INFO: Variable 'innodb_undo_directory'='./'->'/var/lib/mysql' option 'innodb_undo_directory' type 6
180627 12:41:55 MAIN    INFO: Variable 'innodb_undo_directory'='./'->'/var/lib/mysql' option 'innodb_undo_directory' type 6
180627 12:41:55 MAIN    INFO: Variable 'innodb_undo_logs'='128'->'128' option 'innodb_undo_logs' type 8
180627 12:41:55 MAIN    INFO: Variable 'innodb_undo_logs'='128'->'128' option 'innodb_undo_logs' type 8
180627 12:41:55 MAIN    INFO: Variable 'innodb_undo_tablespaces'='0'->'0' option 'innodb_undo_tablespaces' type 7
180627 12:41:55 MAIN    INFO: Variable 'innodb_undo_tablespaces'='0'->'0' option 'innodb_undo_tablespaces' type 7
180627 12:41:55 MAIN    INFO: Copy-back operation completed successfully.
180627 12:41:55 MAIN    INFO: Finished copying backup files to '/var/lib/mysql'

mysqlbackup completed OK!

3.3 启动MySQL服务

恢复后的数据库文件的属主是root用户，必须改成mysql用户才能启动MySQL服务。

[root@mydb01 ~]# chown -R mysql:mysql /var/lib/mysql
[root@mydb01 ~]# systemctl start mysqld
[root@mydb01 ~]# systemctl status mysqld
● mysqld.service - MySQL Server
   Loaded: loaded (/usr/lib/systemd/system/mysqld.service; enabled; vendor preset: disabled)
   Active: active (running) since Wed 2018-06-27 13:00:15 CST; 2h 29min ago
     Docs: man:mysqld(8)
           http://dev.mysql.com/doc/refman/en/using-systemd.html
  Process: 6482 ExecStart=/usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid $MYSQLD_OPTS (code=exited, status=0/SUCCESS)
  Process: 6464 ExecStartPre=/usr/bin/mysqld_pre_systemd (code=exited, status=0/SUCCESS)
 Main PID: 6485 (mysqld)
   CGroup: /system.slice/mysqld.service
           └─6485 /usr/sbin/mysqld --daemonize --pid-file=/var/run/mysqld/mysqld.pid

Jun 27 13:00:14 mydb01 systemd[1]: Starting MySQL Server...
Jun 27 13:00:15 mydb01 systemd[1]: Started MySQL Server.

4、备份脚本

4.1 全量备份脚本

#!/bin/bash
BACKUP_DIR=/u02/full
BACKUP_PASS=abcABC@12
BACKUP_USER=root
/opt/mysql/meb-4.1/bin/mysqlbackup --defaults-file=/etc/my.cnf --host=127.0.0.1 --user=$BACKUP_USER --password=$BACKUP_PASS --with-timestamp --backup-dir=$BACKUP_DIR backup-and-apply-log

4.2 增量备份脚本

#!/bin/bash
BACKUP_DIR=/u02/incr
BACKUP_PASS=abcABC@12
BACKUP_USER=root
/opt/mysql/meb-4.1/bin/mysqlbackup --defaults-file=/etc/my.cnf --host=127.0.0.1 --user=$BACKUP_USER --password=$BACKUP_PASS --incremental=optimistic --incremental-base=history:last_backup --incremental-backup-dir=/u02/incr --with-timestamp backup

4.3 全备份成功发邮件脚本

#!/bin/bash

BACKUP_DIR=/u02/full
BACKUP_PASS=abcABC@12
BACKUP_USER=root

DATE_DAY=$(date +"%Y-%m-%d")
DATE_HOUR=$(date +"%H")

EMAIL_RECIPIENT=root@localhost

/opt/mysql/meb-4.1/bin/mysqlbackup --defaults-file=/etc/my.cnf --host=127.0.0.1 --user=$BACKUP_USER --password=$BACKUP_PASS --with-timestamp --backup-dir=$BACKUP_DIR backup-and-apply-log

NO_OF_COMPLETE_OK_MESSAGES=$(cat $BACKUP_DIR/${DATE_DAY}_${DATE_HOUR}*/meta/MEB_${DATE_DAY}.${DATE_HOUR}*.log | grep "mysqlbackup completed OK" | wc -l)

# Note that the string "mysqlbackup completed OK" must occur 2 times in the log in order for the backup to be OK
if [ $NO_OF_COMPLETE_OK_MESSAGES -eq 2 ]; then
        # Backup successful, find backup directory
        echo "Backup succeeded"
        exit 0
else
        echo "MySQL backup failed, please check logfile" | mail -s "ERROR: MySQL Backup Failed!" ${EMAIL_RECIPIENT}
        exit 1
fi
MySQL Enterprise Backup (MEB) for MySQL 8.0 深入解析及企业级备份恢复演练
专注于数据库技术分享，包含但不限于Oracle，MySQL，PostgreSQL，ElasticSearch及国产数据库等
03-13 2574
MySQL 8.0环境下执行全量备份和增量备份，并进行恢复的详细演练为例，介绍整个过程。MEB还支持诸如并行备份、备份过滤、跨平台备份与恢复等功能，同时在遇到问题时，可通过查看详细的日志信息进行故障排查。首先准备好全量备份，停止MySQL服务，移动现有数据，然后应用重做日志，最后重启MySQL服务加载恢复后的数据。此命令将启动一个全量备份任务，包含对所有InnoDB表空间的备份，并应用重做日志至备份时刻，确保数据一致性。增量备份基于之前的全量备份，仅备份自上次全量或增量备份以来变化的数据。
MySQL运维DBA-MySQL8数据备份和恢复-006篇-mysqldump man帮助手册
老韩的Linux云计算架构师进阶之路
02-27 762
MySQL8数据备份和恢复-001-mysqldump man帮助手册。
MySQL Enterprise Backup 8.0 TAR for Generic Linux x86 (64bit)
11-25
MySQL Enterprise Backup 8.0 TAR for Generic Linux x86 (64bit)
meb-deb:将 MySQL Enterprise Backup 打包为 deb 包
06-25
从 MySQL Enterprise Backup tarball 创建一个 Debian/Ubuntu .deb 包 官方 deb 包有一个功能请求： 要求 MySQL 企业备份 tarball 制作 用法 将 tarball 复制到 meb-deb 目录并运行make 。 如果您下载了 Vxxxxx-xx.zip 文件，那么您应该解压缩该 zip。 包装布局 文件安装在/opt/mysql下（例如/opt/mysql/meb-3.11.1-ubuntu12.04-x86-64bit/bin/mysqlbackup） 这是为了允许在同一台机器上安装多个版本，这可能是恢复旧备份所需要的。 安装后脚本使用 update-alternatives 创建 /usr/bin/mysqlbackup
MySQL(74)如何使用MySQL Enterprise Backup工具？
qq_43012298的博客
06-13 767
摘要：MySQL Enterprise Backup（MEB）是Oracle提供的专业数据库备份工具，支持物理和逻辑备份，适用于大规模数据库。本文详细介绍了MEB的安装配置、完全/增量备份操作（含代码示例）、数据恢复流程（需停止MySQL服务）、备份验证方法以及定时自动备份实现（通过crontab调度）。关键步骤包括备份镜像生成、增量基准选择、恢复顺序控制（先全量后增量）以及自动化脚本编写，帮助用户构建安全高效的MySQL备份方案。（150字）
mysql ： MySQL Enterprise Backup 的使用方法
weixin_34388207的博客
12-12 1183
mysql ： MySQL Enterprise Backup 的使用方法对于mysql的热备使用的最多应该 Xtrabackup工具了,但是这个工具没有window版本的,我们公司的mysql安装在window上,刚开始的时候使用自带的mysqldump备份对系统还没什么影响,以后数据量大了,估计系统承受不了,这下我就不得不研究MySQL Enterprise Backup...
MySQL 8 Cookbook epub 格式
09-03
Design and administer enterprise-grade MySQL 8 solutions Key Features Store, retrieve, and manipulate your data using the latest MySQL 8 features Practical recipes on effective administration in ...
Monitoring MySQL Database Performance with Python: Essential Tools and Professional Techniques
# Utilizing Python for MySQL Database Performance Monitoring: Essential Tools and Expert Tips Monitoring is an indispensable part of maintaining stable system operations, especially at the database ...
xtra_backup
12-28
### Percona XtraBackup MySQL Backup Tool Usage and Download Percona XtraBackup is a powerful tool designed to perform non-blocking backups of MySQL databases, including InnoDB and MyISAM tables. This...
MySQL 5.6 Reference Manual
11-30
Table of Contents Preface, Notes, Licenses . . . . . . . . ....1. Licenses for Third-Party Components ....1.1. FindGTest.cmake License ....1.2. LPeg Library License ....1.3. LuaFileSystem Library License ....
mysql-enterprise-backup-4.1-en.pdf
05-16
MySQL Enterprise Backup是一款专门用于备份MySQL数据库发工具。它是一个跨平台的高性能备份工具，它具有丰富的功能，包括：热备份，增量备份，选择备份，直接备份到云，加密，压缩备份等。
mysql enterprise backup 使用_mysql enterprise backup入门使用
weixin_34792272的博客
01-27 173
**************************************************************--1.全备**************************************************************#mysqlbackup --defaults-file=/usr/local/mysql/my.cnf --host=127.0.0.1...
MySQL8.0之XtraBackup 增量恢复
eagle89的专栏
04-07 3767
Percona XtraBackup的工作原理： 1.XtraBackup复制InnoDB数据文件，这会导致内部不一致的数据，但是它会对文件执行崩溃恢复，以使其再次成为一个一致的可用数据库 2.这样做的可行性是因为InnoDB维护一个REDO日志，也称为事务日志。REDO日志包含了InnoDB数据每次更改的记录。当InnoDB启动时，REDO日志会检查数据文件和事务日志，并执行两个步骤。它将已...
最新XtraBackup8，2024年最新字节软件测试高工面试
2401_84563438的博客
05-12 459
其实安装xtrabackup，除三个主要软件包外，还有以下组件，只不过在使用yum安装xtrabackup的时候，都作为依赖包安装了，若是离线安装，以下组件缺一不可。共有三种方式安装XtraBackup，分别是存储库安装，rpm或apt安装，源代码安装。以下为安装Xtrabackup的组件共享，若linux下载速度慢，可使用百度云盘下载。以上存储库方式安装就完成，使用xtrabackup --help即可查看命令帮助。手动方式需要把组件安装完成后，才能成功安装xtrabackup。安装依赖组件libev。
mysql enterprise backup入门使用
yangzhawen
04-01 3785
mysqlbackup即mysql enterprise backup入门使用
使用mysql企业版备份软件来设置一个从库：Setting Up a New Replication Slave
gwl7878的博客
09-06 346
Setting Up a New Replication Slave If you use MySQL replication, MySQL Enterprise Backup allows you to set up a slave database without stopping the master, by backing up the master and restoring tha
Mysql 使用企业级MEB进行数据库物理备份与恢复
11-15 971
在免费下载并使用的MySQL开源社区版本中，默认并不包含MEB（MySQL Enterprise Backup，MySQL企业版备份工具）物理热备工具，因为它是一款Oracle自研的企业级软件，用户需要付费才能使用。该工具功能强大，能够为MySQL数据库全局、增量、部分、流、压缩和加密备份与恢复等场景提供优秀的解决方案。对于甲骨文公司的付费用户而言，使用MEB工具来满足企业自身的备份与恢复需求，不失为一种明智的选择。
MYSQL(8.0版本)配置环境
KUUU123的博客
09-12 3129
当我们学习或者工作时拿到一部新的电脑，就需要安装各种环境配置，很麻烦，本文介绍了如何安装MySQL，60岁老太也能学会的操作步骤提示：以下是本篇文章正文内容，下面案例可供参考60岁老太也能学会，不懂就问。
MySqlBackup.NET使用不了MySqlBackup方法
最新发布
07-27
<think>首先，用户的问题是：在使用MySqlBackup.NET时无法调用MySqlBackup方法，需要解决方法或排查问题。用户提到了引用[1]到[4]，这些是关于MySqlBackup.Net的使用教程、常见问题解决方案等信息。 关键点： - MySqlBackup.Net是一个.NET工具，用于备份和恢复MySQL数据库。 - 用户遇到了无法调用MySqlBackup方法的问题。 - 我需要基于提供的引用和一般知识来提供解决方法。 从引用中提取相关信息： - 引用[1]：提到安装和快速启动，但没有直接解决无法调用方法的问题。 - 引用[2]：提到常见问题解决方案，包括依赖库的正确引用。 - 引用[3]：描述工具的基本信息。 - 引用[4]：提供了一个C#代码示例，使用MySqlBackup类来备份数据库。 在引用[4]中，有一个代码示例： ```csharp using (MySqlConnection conn = new MySqlConnection(constring)) { using (MySqlCommand cmd = new MySqlCommand()) { using (MySqlBackup mb = new MySqlBackup(cmd)) { cmd.Connection = conn; conn.Open(); mb.ExportToFile(file); conn.Close(); } } } ``` 这表明MySqlBackup方法是通过创建MySqlBackup对象并调用其方法如ExportToFile来使用的。用户说“无法调用MySqlBackup方法”，可能指的是无法实例化MySqlBackup类或调用其方法。 可能的原因和解决方法： 1. **依赖库未正确引用**：这是引用[2]中提到的常见问题。MySqlBackup.Net依赖于MySql.Data库。用户需要确保项目中引用了MySql.Data和MySqlBackup.Net的NuGet包。 - 解决方案：检查项目引用，安装必要的NuGet包。例如，通过NuGet包管理器安装MySql.Data和MySqlBackup.Net。 2. **命名空间未导入**：在代码中，可能需要使用正确的命名空间。MySqlBackup类通常在MySql.Data.MySqlClient命名空间中。 - 解决方案：在代码文件顶部添加`using MySql.Data.MySqlClient;`或`using MySqlBackup;`（取决于具体实现）。引用[4]中使用了`using MySqlBackup;`。 3. **版本兼容性问题**：MySqlBackup.Net可能与特定版本的MySql.Data不兼容。 - 解决方案：确保安装兼容的版本。参考官方文档或NuGet页面。 4. **代码错误**：用户代码中可能有语法错误或逻辑错误。 - 解决方案：检查代码是否正确。例如，在引用[4]中，MySqlBackup是通过传递MySqlCommand对象来创建的。 5. **权限问题**：引用[4]提到“最好不要备份到C盘”，因为权限问题。但用户的问题是关于调用方法，不是备份路径。 - 这可能相关，如果调用方法时涉及文件操作。 6. **其他常见问题**： - 确保MySQL连接字符串正确。 - 确保数据库服务正在运行。 - 检查异常信息：捕获异常并查看错误消息，这可以提供线索。 结构化回答： - 回答要清晰、逐步解决。 - 使用中文。 - 遵循系统指令：行内数学表达式用$...$，但这里可能不需要数学。 - 生成相关问题。 - 在引用段落末尾添加引用标识。 回答结构： 1. **确认问题**：简述用户的问题。 2. **可能原因**：列出常见原因。 3. **解决步骤**：提供逐步的解决方法。 4. **代码示例**：如果需要，提供代码。 5. **相关问题**：生成相关问题。 生成相关问题： - 基于用户的问题，生成相关问题，如： 1. 如何安装MySqlBackup.Net？ 2. MySqlBackup.Net的常见错误有哪些？ 3. 如何优化MySqlBackup.Net的性能？ 4. MySqlBackup.Net与其他备份工具的比较？ 5. 如何在ASP.NET中使用MySqlBackup.Net？ 确保回答真实可靠：基于引用和一般知识。</think>### MySqlBackup.Net 无法调用 MySqlBackup 方法的解决方法 在使用 MySqlBackup.Net 时，无法调用 `MySqlBackup` 方法（如实例化类或调用 `ExportToFile` 等方法）是一个常见问题，通常由依赖库引用错误或配置问题引起。以下我将基于官方文档和常见实践，逐步分析原因并提供解决方法。整个过程需确保您的开发环境（如 Visual Studio）已正确设置。 #### 可能原因分析 1. **依赖库未正确引用**：MySqlBackup.Net 依赖于 MySql.Data 库，如果项目中未安装或版本不兼容，会导致 `MySqlBackup` 类无法识别[^2]。 2. **命名空间未导入**：代码中未添加必要的 `using` 指令，导致编译器无法找到 `MySqlBackup` 类。 3. **NuGet 包未安装或版本冲突**：MySqlBackup.Net 的 NuGet 包未安装，或与 .NET 框架版本不兼容。 4. **连接字符串或权限问题**：数据库连接无效，或在调用方法时因权限不足引发异常（如备份路径权限问题）[^4]。 5. **代码语法错误**：实例化 `MySqlBackup` 对象时参数传递错误，或未正确处理对象生命周期。 #### 逐步解决方法 请按顺序执行以下步骤，每一步都验证问题是否解决： 1. **安装必要的 NuGet 包** MySqlBackup.Net 需要 MySql.Data 作为基础依赖。在 Visual Studio 中： - 打开 NuGet 包管理器控制台（工具 → NuGet 包管理器 → 包管理器控制台）。 - 运行以下命令安装最新兼容版本： ```powershell Install-Package MySqlBackup.Net Install-Package MySql.Data ``` - 验证安装：在解决方案资源管理器中，检查引用是否包含 `MySqlBackup` 和 `MySql.Data`。如果未出现，重启 Visual Studio 后重试[^2][^3]。 2. **导入正确的命名空间** 在代码文件顶部添加以下 `using` 指令： ```csharp using MySql.Data.MySqlClient; // 提供 MySqlConnection 和 MySqlCommand using MySqlBackup; // 提供 MySqlBackup 类 ``` 如果 `MySqlBackup` 仍无法识别，检查 NuGet 包是否成功安装，或尝试清理项目（生成 → 清理解决方案）后重新生成。 3. **检查代码实现** 确保实例化 `MySqlBackup` 对象时传递有效的 `MySqlCommand` 对象。参考以下正确示例（基于引用[4]修改）： ```csharp protected void BackupButton_Click(object sender, EventArgs e) { string constring = "server=localhost;port=3306;user=root;password=your_password;database=your_db;Allow User Variables=True"; string backupPath = "D:\\backup.sql"; // 避免C盘，确保路径有写入权限[^4] using (var conn = new MySqlConnection(constring)) { using (var cmd = new MySqlCommand()) { cmd.Connection = conn; conn.Open(); // 正确实例化 MySqlBackup using (var mb = new MySqlBackup(cmd)) { mb.ExportToFile(backupPath); // 调用方法 } conn.Close(); } } } ``` - **关键点**：`MySqlBackup` 构造函数必须传入 `MySqlCommand` 对象，且命令对象需关联到已打开的连接。 - 如果方法调用失败，添加异常捕获以获取错误详情： ```csharp try { using (var mb = new MySqlBackup(cmd)) { mb.ExportToFile(backupPath); } } catch (Exception ex) { Console.WriteLine($"错误: {ex.Message}"); // 输出异常信息 } ``` 4. **验证依赖版本兼容性** - 打开项目文件（.csproj），检查包版本。推荐组合： - MySqlBackup.Net ≥ 2.3.8 - MySql.Data ≥ 8.0.0（与 .NET Core 3.1+ 或 .NET Framework 4.6.1+ 兼容） - 如果版本冲突，更新包：`Update-Package MySql.Data` 和 `Update-Package MySqlBackup.Net`[^3]。 5. **检查权限和连接** - 确保数据库服务正在运行，且连接字符串正确（测试连接：`conn.Open();` 是否成功）。 - 备份路径需有写入权限：避免系统保护目录（如 C:\），使用 `D:\` 或自定义路径[^4]。 - 在 Windows 中，右键备份文件夹 → 属性 → 安全 → 添加用户权限（如 IIS 用户或应用程序池标识）。 #### 附加建议 - **日志与调试**：启用 MySqlBackup.Net 的日志功能（如果支持），或在代码中输出中间状态。 - **官方资源**：参考 [MySqlBackup.Net GitHub 仓库](https://github.com/MySqlBackupNET/MySqlBackup.Net) 获取最新文档和示例。 - **备选方案**：如果问题持续，考虑使用命令行工具 `mysqldump` 作为临时替代，但 MySqlBackup.Net 提供更高效的集成[^1]。 通过以上步骤，大多数调用问题可解决。如果仍遇到错误，请提供异常信息或开发环境详情，以便进一步分析。
评论 2
添加红包

请填写红包祝福语或标题

个

红包个数最小为10个

元

红包金额最低5元

当前余额3.43元 前往充值 >
需支付：10.00元
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付元
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明：

1.余额是钱包充值的虚拟货币，按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载，可以购买VIP、付费专栏及课程。

余额充值