Storagebod Rotating Header Image

Dedupe or Duped?

I must say that I am extremely underwhelmed by EMC's Celerra 'announcements'; very 'meh'! What I found especially interesting is the fact that EMC are not recommending the use of the inbuilt dedupe for VMWare installs. We all know that NetApp have set great stall by their use of dedupe and thin provisioning for virtualised servers, their infamous and unambitious guarantee is predicated that you will use it for VMWare (not for high performance workloads such as Oracle tho').

So I am wondering why EMC don't recommend using their dedupe for VMWare? Is it worse than NetApps? Does it eat more performance on the head? Is it because their dedupe works across the whole data-store unlike NetApps which is currently limited to an aggregrate ISTR? I guess if that's the case you could end up with alot more VMWare images linked to a single set of disk blocks.

Hopefully there will be a friendly EMCer along to explain in a bit?

And what's this Recoverpoint compression? I thought Recoverpoint compression was only for the journal storage and was related to the CDP capabilities? We aren't talking about using compression a la Storwize are we?


3 Comments

  1. Ummm…
    With all due respect to the Fourth Estate, errors are often introduced in the quest to get a scoop on a story. Sources may misinterpret or misunderstand, or inappropriate conclusions may be drawn from incomplete information.
    I suggest you hold off your analysis until you see the formal announcement from EMC.

  2. Martin G says:

    I guessed that might be the case…but I’m still interested to see whether EMC recommend dedupe for vmware or not!

  3. Storagezilla says:

    “I thought Recoverpoint compression was only for the journal storage and was related to the CDP capabilities?”
    RecoverPoint compression is also used for reduction of data transmitted across the WAN when using CRR.

Leave a Reply

Your email address will not be published. Required fields are marked *