Jeff Browning explains NetApp Snapshots and the trade off’s in this blog entry very well.

It is worth reading the whole blog, his explanations are better than anything I could write.

Here are some short excerpts…

“NetApp’s snapshots actually occurred as a result of serendipity (i.e. a happy accidental discovery). The design of NetApp snapshots is as an artifact of the design of NetApp’s file system called WAFL (Write Anywhere File Layout).”

“WAFL is so named because it never overwrites existing blocks in place when updates occur. Instead it writes new blocks containing the updated data, and then frees the old blocks. Therefore, a snapshot can be assembled by simply retaining the old blocks rather than freeing them. No additional I/O is required to do this, which leads to NetApp’s accurate claim that their snapshots have no write penalty.”

“What is extremely clear, though, is the choice to drink Kool-Aid – anyone’s Kool-Aid – is a fool’s choice. You need to look carefully at both types of snapshots and make an informed choice about which is appropriate for you in the context of your particular “workload. Snapshots are wonderful, and they benefit the Oracle user greatly. But they are not without risks and trade offs. To contend otherwise would be dishonest.

Recently, Jeff Browning’s posts have provided a real insight into the way NetApp technology and sales departments compete for a customer’s attention while serving their Kool-Aid.

This entry was posted in Uncategorized. Bookmark the permalink.