MySQL backup soon becomes an important matter when the database is used in production. The pain-point comes from the fact that while backuping the database is not available to respond to client requests anymore. With mysqldump - the standard tool for performing MySQL backups - and a large database the operation can go over many tenth of minutes if not hours. If I am running my business on line this is simply not acceptable.

The classical approach to workaround this problem is to take advantage of MySQL replication. I set up a master/slave configuration where the slave acts as copy of the master. Then, when needed, I run mysqldump on the slave without any service interruption on the master.

But ZFS snapshosts bring a new straightforward approach that avoids the pain and the complexity of a master/slave replication.

Snapshots are a key feature of ZFS that allows me to save a copy of …

Save the date - October 14th, 3pm Paris & Berlin, 2pm London, 4pm Jerusalem  -  for this free live webinar where you'll have a chance to ask questions to our experts.

This webinar focuses on how ZFS, SSDs and the Open Storage line of products from Sun are changing the rules in the database storage industry. You will learn how to increase data security, scalability, and reduce the price/performance ratio with these technologies. This webinar includes ZFS best practises for databases backup and performance.

To register, click here.

Just in case you missed the live event, we have a recording of the ZFS + SSD for databases webcast

Listen Now

You can also download the slides from Slide share. Download Slides

Over the last month I have been working on a ZFS Tuning for Databases presentation. I'll be presenting it live tomorrow 8/26/09 at 8 AM PST.

This based on a lot of work done at Sun as well as in the community. With the massive adoption of Solid State Devices (SSDs) (thank you iPOD) the storage market just got a whole lot more interesting. Incorporating SSDs into a ZFS pool is a breeze. This presentation is meant to help you get the best out of the ZFS + SSD combination for databases. We look into Postgres, MySQL and Oracle. I also provide a quick into into Sun's unified storage 7000 series systems.

If you are interested do Register Now

Last weekend, my brother and I attended SELF 2009. A few thoughts on it:

The mixture of sessions was interesting. There were some really good ones. I think the best session I attended was an OpenSolaris/NetBeans/Glassfish/Virtualbox/ZFS session, given by a Sun employee. He was an excellent presenter, and really showed off the strengths of the technologies in a nice way. He started up enough VMs to make his OpenSolaris laptop chew into swap, and I thought it was fun to see how it dealt with that. I’ve heard Solaris and OpenSolaris do a lot better at avoiding and managing swapping than GNU/Linux, but I couldn’t make any opinion from watching. I did think it was odd to have this session at a “Linux” (yes, they left off the GNU) conference. But I thought the session was a good addition to the conference. In other sessions, and in the hallways and expo, there was a lot more …

One of the cool things about talking about MySQL performance with ZFS is that there is not much tuning to be done Tuning with ZFS is considered evil, but a necessity at times. In this blog I will describe some of the tunings that you can apply to get better performance with ZFS as well as point out performance bugs which when fixed will nullify the need for some of these tunings.

For the impatient, here is the summary. See below for the reasoning behind these recommendations and some gotchas.

1. Match ZFS recordsize with Innodb page size (16KB for Innodb Datafiles, and 128KB for Innodb log files).
2. If you have a write heavy workload, use a Seperate ZFS Intent Log.
3. If your database working set size does not fit in memory, …

One of the cool things about talking about MySQL performance with ZFS is that there is not much tuning to be done Tuning with ZFS is considered evil, but a necessity at times. In this blog I will describe some of the tunings that you can apply to get better performance with ZFS as well as point out performance bugs which when fixed will nullify the need for some of these tunings.

For the impatient, here is the summary. See below for the reasoning behind these recommendations and some gotchas.

1. Match ZFS recordsize with Innodb page size (16KB for Innodb Datafiles, and 128KB for Innodb log files).
2. If you have a write heavy workload, use a Seperate ZFS Intent Log.
3. If your database working set size does not fit in memory, …

One of the cool things about talking about MySQL performance with ZFS is that there is not much tuning to be done Tuning with ZFS is considered evil, but a necessity at times. In this blog I will describe some of the tunings that you can apply to get better performance with ZFS as well as point out performance bugs which when fixed will nullify the need for some of these tunings.

For the impatient, here is the summary. See below for the reasoning behind these recommendations and some gotchas.

1. Match ZFS recordsize with Innodb page size (16KB for Innodb Datafiles, and 128KB for Innodb log files).
2. If you have a write heavy workload, use a Seperate ZFS Intent Log.
3. If your database working set size does not fit in memory, …

A couple of weeks ago I wrote a post titled Dear IBM , I was too late .. I was on holliday last week when people started sending me text messages , such as .. "Game Over MySQL , Long live Ingress" or "No Eclipse for IBM", etc ...

I had ideas regarding the future of certain Sun products at IBM, now the game has changed .. it'ss how they will live on at Oracle :)

Similar Questions arise .. like indeed the future of MySQL, the future of Solaris etc ...

So regarding the future of MySQL , I don't worry at all, on the contrary ..
Oracle tried buying mysql before they already have Innodb .. they didn't kill it .. the MySQL offering is complementary to the Oracle offering, now they can tackle both markets.
And as already mentionned when writing my IBM letter ..

As for MySQL, Jeremey has some good insights.. the fact that …