You are invited to: The New England Open Solaris User Group (NEOSUG) Meeting
When: June 23rd, 2009 6:00PM to 9:00 PM
Where: Sun Microsystems Burlington Campus; 1 Network Drive, Burlington, MA
RSVP: To Linda Wendlandt: lwendlandt at cptech dot com lwendlandt@cptech.com
Registration Required! – so we can plan food and drink
In a previous post I discussed the topic of deduplication for capacity optimization. Removing redundant data blocks on disk is the first, and most obvious, phase of deduplication in the marketplace. It helps to drive down the most obvious cost – the cost per GB of disk capacity. This market has grown quickly over the last few years. Both startups and established storage vendors have products that compete in the space. They are most commonly marketed as virtual tape library (VTL) or disk-to-disk backup solutions.
Does that mean that deduplication is a point solution for highly sequential workloads? No. There is another somewhat less obvious benefit of deduplication.
What storage administrator does not ask for more cache in the storage array? If I can afford 8GB, I want 16GB. If the system supports 16GB, I want 32GB. Whether it is for financial or technical reasons, cache is always limited. What about deduplicating the data in cache? When the workload is streaming sequential backup data from disk, this may not be very helpful. However, in a primary storage system with a more varied workload, this becomes very interesting.