How to use MYSQLBACKUP

DBA Notes: 2011/09/16

Cheng Li

 

How to use MYSQL Enterprise backup (MEB)

 

MySQL enterprise backup, MEB, is a superset of the InnoDB Hot Backup product. The ibbackup command is available on all platforms, with the same options as before plus some new ones. In particular, the --incremental option enables incremental backups of InnoDB tables.

 

[mysql@ctmitsdb ~]$ mysqlbackup /home/mysql/data/.my.cnf /home/mysql/backups

mysqlbackup: Starting mysqlbackup with following arguments:
mysqlbackup /home/mysql/data/.my.cnf /backups
mysqlbackup: The unique backup id generated for the current backup operation is 101620
mysqlbackup: IMPORTANT: Please check that backup run completes successfully.
At the end of a successful 'backup' run mysqlbackup
prints "mysqlbackup completed OK!".

 

 [mysql@ctmitsdb ~]$ tail -40  mysql_fullbackup.log

 

110915 17:54:14 mysqlbackup: INFO: Copying /home/mysql/data/mysql/ibbackup_binlog_marker.ibd (Antelope file format).
 mysqlbackup: INFO: A copied database page was modified at 6879155536.
          (This is the highest lsn found on page)
          Scanned log up to lsn 6879155751.
          Was able to parse the log up to lsn 6879155751.
          Maximum page number for a log record 3579
110915 17:54:14 mysqlbackup: INFO: All tables unlocked
 mysqlbackup: INFO: All MySQL tables were locked for 456.000 seconds
110915 17:54:14 mysqlbackup: INFO: Full backup completed!
 mysqlbackup: INFO: MySQL binlog position: filename ctmitsdb-bin.000038, position 87250992
 mysqlbackup: INFO: Backup created in directory '/home/mysql/backup/2011-09-15_17-45-35'
110915 17:54:14 mysqlbackup: INFO:  ibbackup_logfile's creation parameters:
          start lsn 6879142400, end lsn 6879155751,
          start checkpoint 6879142785.
InnoDB: Starting an apply batch of log records to the database...
InnoDB: Progress in percents: 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 Setting log file size to 0 268435456
InnoDB: Progress in MB: 100 200
Setting log file size to 0 268435456
InnoDB: Progress in MB: 100 200
Setting log file size to 0 268435456
InnoDB: Progress in MB: 100 200
 mysqlbackup: INFO: We were able to parse ibbackup_logfile up to
          lsn 6879155751.
ibbackup: Last MySQL binlog file position 0 87250992, file name /home/mysql/data/archive/ctmitsdb-bin.000038
 mysqlbackup: INFO: The first data file is '/home/mysql/backup/2011-09-15_17-45-35/datadir/ibdata1'
          and the new created log files are at '/home/mysql/backup/2011-09-15_17-45-35/datadir/'
 mysqlbackup: INFO: System tablespace file format is Antelope.
110915 17:54:34 mysqlbackup: INFO: Full backup prepared for recovery successfully!

 --------------------------------------------------------
   Parameters Summary
---------------------------------------------------------
   Start LSN                  : 6879142400
   End LSN                    : 6879155751
--------------------------------------------------------

 mysqlbackup completed OK!

 

Reference:

Whitepaper: mysql-enterprise-backup-3.5-en.a4

Software: meb-3.5.4-rhel5.x86_64.rpm

fj.pngU2727P2DT20110915091247.jpg

来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/26136400/viewspace-707666/,如需转载,请注明出处,否则将追究法律责任。

转载于:http://blog.itpub.net/26136400/viewspace-707666/

先展示下效果 https://pan.quark.cn/s/5061241daffd 在使用Apache HttpClient库发起HTTP请求的过程中,有可能遇到`HttpClient`返回`response`为`null`的现象,这通常暗示着请求未能成功执行或部分资源未能得到妥善处理。 在本文中,我们将详细研究该问题的成因以及应对策略。 我们需要掌握`HttpClient`的运作机制。 `HttpClient`是一个功能强大的Java库,用于发送HTTP请求并接收响应。 它提供了丰富的API,能够处理多种HTTP方法(例如GET、POST等),支持重试机制、连接池管理以及自定义请求头等特性。 然而,一旦`response`对象为`null`,可能涉及以下几种情形:1. **连接故障**:网络连接未成功建立或在请求期间中断。 需要检查网络配置,确保服务器地址准确且可访问。 2. **超时配置**:若请求超时,`HttpClient`可能不会返回`response`。 应检查连接和读取超时设置,并根据实际需求进行适当调整。 3. **服务器故障**:服务器可能返回了错误状态码(如500内部服务器错误),`HttpClient`无法解析该响应。 建议查看服务器日志以获取更多详细信息。 4. **资源管理**:在某些情况下,如果请求的响应实体未被正确关闭,可能导致连接被提前释放,进而使后续的`response`对象为`null`。 在使用`HttpClient 3.x`版本时,必须手动调用`HttpMethod.releaseConnection()`来释放连接。 而在`HttpClient 4.x`及以上版本中,推荐采用`EntityUtils.consumeQuietly(respons...
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

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

抵扣说明:

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

余额充值