Many InnoDB scalability problems seem fixed in InnoDB-plugin-1.0.3 and I expect InnoDB-plugin will run fine on 16-24… features I would like to see soon: Fast recovery. Both recovery after crash and recovery from backup can take unacceptable long time, especially if… – copying whole 500GB backup while you need to restore only single 20GB table is very non-productive Open InnoDB tables in parallel…
Post: xtrabackup-0.4, going beta, progress meter
March 30, 2009 By 7 Comments
… may happen if backup takes too long and you have a lot of updates on InnoDB tables Progress meter during recovery step, now… recovery: scanned up to log sequence number 1316 3688693248 (34 %) … InnoDB: Doing recovery: scanned up to log sequence number 1316 4113366528 (68 %) InnoDB: Doing recovery…
Post: Why you can't rely on a replica for disaster recovery
July 31, 2010 By 25 Comments
… point of view, though, it was still completely corrupted. The “InnoDB file” contained blocks of data that were obviously from other… qualified advice and 2) don’t trust the advice; backups and disaster recovery plans must be tested periodically. This case illustrates an… and drop the table off your “backup.” I still see people using a replica as a backup, and I know it’s…
Post: A recovery trivia or how to recover from a lost ibdata1 file
June 3, 2011 By 8 Comments
… at least be able to recover the data with the Innodb recovery tool of Aleksandr Kuzminsky a colleague on the Percona European…;” sleep 1 let CURRENT_ID+=1 done I did a backup of /var/lib/mysql before the first run to make… one table. For that one, I had to use the Innodb recovery tools but even then, I had a hard time. I…
Post: Faster Point In Time Recovery with LVM2 Snaphots and Binary Logs
February 23, 2012 By 3 Comments
…e. updates on CentOS. If you are using InnoDB, it is also important that your transaction logs…volume, if not, you could potentially trigger crash recovery when an LSN mismatch occurs and still end…still a valid backup method of course on top of your regularly tested (offsite) backups. Another ideal …
Post: No more MySQL Crash Safe Replication in 5.0 ?
January 29, 2008 By 7 Comments
… only Innodb tables – Innodb when Innodb does crash recovery it would print position in master log files up to which replication was done: InnoDB: In… somewhat similar functionality works as expected. Innodb during recovery also prints position in the MySQL binary log: InnoDB: Last MySQL binlog file position… cases – for example when you’re taking LVM snapshot (for backup or to clone slave from the master) and can’t…
Post: Filtered MySQL Replication
November 7, 2007 By 8 Comments
… recovery while recovering from backup. There are however some cases when you really do not need events in binary log – even for backup recovery… to perform mapping between master positions which you get with backup to distribution slave position. You can also clone other slaves… altering tables. If you have Innodb tables you’re normally OK because you can use –skip-innodb on the filtering slave and…
Post: Ultimate MySQL variable and status reference list
January 8, 2011 By 4 Comments
…Com_backup_…innodb_change_bufferingblogpercona.commanual innodb_checksumsblogpercona.commanual innodb_commit_concurrencyblogpercona.commanual innodb_concurrency_ticketsblogpercona.commanual innodb_data_file_pathblogpercona.commanual Innodb_data_fsyncsblogpercona.commanual innodb…rpl_recovery_…
Comment: 10 things you need to know about backup solutions for MySQL
March 4, 2009 By 23 Comments
You can take InnoDB backups by copying the files, as long as a) MySQL is … InnoDB‘s background I/O. Gil, the way to test that you have a recoverable backup is to start MySQL on the backup, and let InnoDB‘s recovery process run. If it completes…
Post: Recovery deleted ibdata1
August 10, 2012 By 9 Comments
… the InnoDB main table space – ibdata1 – and redo logs – ib_logfile*. MySQL keeps InnoDB files open all the time. The following recovery technique… loss. For the same reason we can’t make MySQL backup by just copying the files. So, we have to make… system checks that InnoDB files ibdata and ib_logfile* do exist Do not restart MySQL until the further recovery strategy is clear…
