My colleague Aleksandr Kuzminsky will be speaking at WebConf Riga 2010 next month on XtraBackup: Hot Backups and More and Recovery of Lost or Corrupted InnoDB Tables. WebConf is the first big conference of its kind in the Baltic states (Estonia, Latvia, Lithuania) and we are very happy to be participating. In addition to Aleksandr’s [...]
Percona talks at OpenSQL Camp this weekend
August 19, 2010 By 3 Comments
Four Perconians (perconites?) will be at OpenSQL Camp in Sankt Augustin, Germany this weekend presenting talks on: Recovery of Lost or Corrupted InnoDB Tables Keep your MySQL backend online no matter what XtraDB — InnoDB on steroids Xtrabackup for MySQL If you would like to stop by and say hello, we are Aleksandr, Istvan, Morgan [...]
Recover BLOB fields
July 1, 2010 By 4 Comments
For a long time long types like BLOB, TEXT were not supported by Percona InnoDB Recovery Tool. The reason consists in a special way InnoDB stores BLOBs. An InnoDB table is stored in a clustered index called PRIMARY. It must exist even if a user hasn’t defined the primary index. The PRIMARY index pages are [...]
Presentations Announcement: 2010 O’Reilly MySQL Conference & Expo
April 29, 2010 By 4 Comments
The Percona team participated at this year’s O’Reilly MySQL Conference & Expo held April 12-15, 2010 in Santa Clara, California. We gave a lot of talks on…
Author: Peter Zaitsev, Justin Swanhart
MySQL Graphing and Trending with Cacti
Author: Baron Schwartz
Percona‘s Performance and Feature Enhancements to MySQL and InnoDB
Author: Bill Schuler, Baron Schwartz…a Bottleneck
Author: Morgan Tocker
XtraBackup Hot Backups and More
Author: Vadim Tkachenko, Morgan Tocker
You can also read more about this conference on Percona site.
Percona sessions at the MySQL conference
March 15, 2010 By 6 Comments
Many Percona employees will be at the 2010 MySQL conference. We’ll be giving a lot of informative technical talks on various topics. Here’s a list: Morgan Tocker, Baron Schwartz: Diagnosing and Fixing MySQL Performance Problems Peter Zaitsev: Scaling Applications with Caching, Sharding and Replication Baron Schwartz: EXPLAIN Demystified Vadim Tkachenko: An Overview of Flash Storage [...]
Recovering CREATE TABLE statement from .frm file
December 17, 2008 By 5 Comments
So lets say you have .frm file for the table and you need to recover CREATE TABLE statement for this table. In particular when we do Innodb Recovery we often get .frm files and some mess in the Innodb tablespace from which we have to get data from. Of course we could relay on old [...]
How Percona does a MySQL Performance Audit
November 24, 2008 By 17 Comments
Our customers or prospective customers often ask us how we do a performance audit (it’s our most popular service). I thought I should write a blog post that will both answer their question, so I can just reply “read all about it at this URL” and share our methodology with readers a little bit. This [...]
Rendundant Array of Inexpensive Servers
August 21, 2008 By 15 Comments
So you need to design highly available MySQL powered system… how do you approach that ? Too often I see the question is approached by focusing on expensive hardware which in theory should be reliable. And this really can work quite well for small systems. It is my experience – with quality commodity hardware (Dell,HP,IBM [...]
Recovery beyond data restore
August 2, 2008 By 11 Comments
Quite frequently I see customers looking at recovery as on ability to restore data from backup which can be far from being enough to restore the whole system to operating state, especially for complex systems. Instead of looking just at data restore process you better look at the whole process which is required to bring [...]
Recovering Innodb table Corruption
July 4, 2008 By 21 Comments
Assume you’re running MySQL with Innodb tables and you’ve got crappy hardware, driver bug, kernel bug, unlucky power failure or some rare MySQL bug and some pages in Innodb tablespace got corrupted. In such cases Innodb will typically print something like this: InnoDB: Database page corruption on disk or a failed InnoDB: file read of [...]
