Search Results for: mysql compressed backup

Percona XtraBackup 1.6.3

Percona is glad to announce the release of Percona XtraBackup 1.6.3 on 22 September, 2011 (Downloads are available here and from the Percona Software Repositories). This release is purely composed of bug fixes and is the current stable release of Percona Xtrabackup. If the innodb_file_per_table server option is being used and DDL operations, TRUNCATE TABLE, DROP/CREATE the_same_table or ALTER statements on InnoDB tables are […]

xtrabackup-1.1

Dear Community, It is time to announce the next version of backup software from Percona – XtraBackup 1.1. The list of changes in version 1.1 includes: Changelog: XtraBackup is built on a base of MySQL 5.1.44 with InnoDB plugin 1.0.6 Added –host option tar4ibd can treat over 64GB file tar4ibd is default method for stream, […]

xtrabackup-0.9.5rc

Dear Community, As of today release 0.9.5rc is available. In this release there are following changes: Changelog: Option –no-lock is added to innobackupex-1.5.1. Use it only while ALL your tables are InnoDB and you DO NOT CARE about binary log position of backup XtraBackup is ported for InnoDB Plugin 1.0.4. Barracuda file format as well […]

Compression for InnoDB backup

Playing with last version of xtrabackup and compress it I noticed that gzip is unacceptable slow for both compression and decompression operations. Actually Peter wrote about it some time ago, but I wanted to review that data having some new information. In current multi-core word the compression utility should utilize several CPU to speedup operation, […]

Thoughs on Innodb Incremental Backups

For normal Innodb “hot” backups we use LVM or other snapshot based technologies with pretty good success. However having incremental backups remain the problem. First why do you need incremental backups at all ? Why not just take the full backups daily. The answer is space – if you want to keep several generations to […]

Living with backups

Everyone does backups. Usually it’s some nightly batch job that just dumps all MySQL tables into a text file or ordinarily copies the binary files from the data directory to a safe location. Obviously both ways involve much more complex operations than it would seem by my last sentence, but it is not important right […]