In a surprise reverse of their longstanding “inline is the ONLY way to go and anyone that does post processing is stupid” position, Data Domain today announced that Post Process is A-OK with them. Or at least that’s how I’m reading the acquisition of Data Domain for $1.5B by NetApp. Click Read More to see more.
NetApp announced on a concall today that they are acquiring Data Domain for $1.5B. Nice multiple. That’ll be nice for all the other dedupe players who are waiting for IPO or acquisition.
But I envision some significant changes in future backup school presentations by “A Damnation Tapped.” (That’s the best anagram I could find that includes both companies’ names.) ASIS (Advanced Single Instance Storage: dedupe on primary data on a filer) & NetApp’s NearStore VTL both do post-process dedupe. Data Domain does inline dedupe. I can’t see “A Damnation Tapped” saying in their sales presentations that post-process is bad. Therefore, they’ll be saying that it’s OK, which was the point of my blog entry. (It made a nice headline anyway.)
Also, I question the long-term viability of the NearStore VTL. (I don’t think ASIS is going anywhere.) Once the acquisition is complete, NetApp will have two products that both backup data at similar speeds and dedupe said data. One does replication and has no back-end tape, and the other has back-end tape and no replication. Both limitations can be addressed with a few months of dedupe. Surely they won’t fix the limitations in both. Surely they won’t dump the Data Domain product they just acquired. So what’s left? The NearStore VTL. That’s where I’m at. I know that right now there are reasons to choose NearStore VTL over Data Domain, but they can close those gaps with development. Once they do that, I think that product is going bye-bye.
As to ASIS, it’s the only product that is deduping VMware datastores with little or no performance impact — and it’s included with WAFL at no extra charge. That’s going nowhere. Even if it does nothing but that, it’s going nowhere.
----- Signature and Disclaimer -----
Written by W. Curtis Preston (@wcpreston). For those of you unfamiliar with my work, I've specialized in backup & recovery since 1993. I've written the O'Reilly books on backup and have worked with a number of native and commercial tools. I am now Chief Technical Architect at Druva, the leading provider of cloud-based data protection and data management tools for endpoints, infrastructure, and cloud applications. These posts reflect my own opinion and are not necessarily the opinion of my employer.