If you ever wondered how big is that or another index in InnoDB … you had to calculate it yourself by multiplying size of row (which I should add is harder in the case of a VARCHAR – since you need to estimate average length) on count of records. And it still would be quite […]
Dear Community, The release 0.9 of the opensource backup tool for InnoDB and XtraDB is available for download. Changelog: tar4ibd could not treat over 8GB file, now max 64GB prepare-speed-hack is added Fixed bugs: Bug #386179: “InnoDB: Error: space id in fsp header 143088, but in the page header 0″ Bug #394374: “Can’t compile with […]
We’ve written about replication slaves lagging behind masters before, but one of the other side effects of the binary log being serialized, is that it also limits the effectiveness of using it for incremental backup.Â Let me make up some numbers for the purposes of this example: We have 2 Servers in a Master-Slave topology. […]
Speed of InnoDB recovery is known and quite annoying problem. It was discussed many times, see: http://bugs.mysql.com/bug.php?id=29847 http://dammit.lt/2008/10/26/innodb-crash-recovery/ This is problem when your InnoDB crashes, it may takes long time to start. Also it affects restoring from backup (both LVM and xtrabackup / innobackup) In this is simple test, I do crash mysql during in-memory […]
Dear community, The release 0.8 of the opensource backup tool for InnoDB and XtraDB is available for download. Key features: New mode of innobackupex –stream=tar4ibd; new command tar4ibd based on libtar-1.2.11 Experimental option –export is added (see Vadim’s post “Impossible – possible, moving InnoDB tables between servers”for details) tar4ibd is made to be sure that […]
We announce next version of our xtrabackup tool and we consider it stable enough to put label RC on it. Changelist includes: – use O_DIRECT by default for handling InnoDB files – use posix fadvise call to disable OS caching of copying files – disable recovery of double buffer Also we added binary builds for […]
Using xtrabackup for copying files can really saturate your disks, and that why we made special option
to limit rate of IO per second. But it really works when you do local copy. What about stream backup ? Even you copy just to remote box with
innobackupex --stream=tar | ssh remotebox "tar xfi -"
, read may be so intensive so […]
We announce next beta version of our xtrabackup tool. Changelist includes: – set innodb_fast_shutdown=1 on xtrabackup shutdown – set innodb_write_io_threads=10 by default for fast buffer_pool flushing during recovery – build xtrabackup with –with-extra-charsets=complex Bug #357653: innobackupex-1.5.1 –copy-back fails Bug #358194: 2nd-phase is very slow Bug #358266: xtrabackup-0.5 dies with SEGV on bad command line arguments […]
I am happy to announce next build of our backup tool. This version contains several bugfixes and introduces initial implementation of incremental backup. Incremental backup works in next way. When you do regular backup, at the end of procedure you can see output:
The latest check point (for incremental): '1319:813219999'
>> log scanned up to (1319 813701532)
Transaction log of lsn (1318 3034677302) to (1319 813701532) was copied.
090404 06:03:29 innobackupex: All tables unlocked
090404 06:03:29 innobackupex: Connection to database server closed
innobackupex: Backup created in directory '/mnt/data/tmp'
innobackupex: MySQL binlog position: filename 'db02-bin.001271', position 247627478
090404 06:07:58 innobackupex: innobackup completed OK!
innobackupex: You must use -i (--ignore-zeros) option for extraction of the tar stream.
which gives start point 1319:813219999 for further incremental backup. This point […]
We added some new features to our backup tool, namely: Now we can handle log file taken during backup with size exceeding 4GB, it may happen if backup takes too long and you have a lot of updates on InnoDB tables Progress meter during recovery step, now you can see what percentage of log file […]