« Partners Love FlexPod - Success Stories | Main | Welcome Scott Baker and Virtualutopia »

March 25, 2011

Comments

Martin Gustafsson

One reason not to upgrade: SMB 2.0 isn't supported.

David Boll

Another good reason to upgrade, the volume deduplication limit jumps to 16TB for all platforms.

Morten Madsen

@Martin

SMB 2.0 IS supported on Ontap 8.0.1. We are currently running 8.0.1 and SMB2

Scott Chubb

@Martin,
You are correct only for 8.0, however 8.0.1 has full SMB 2.0 support.

Storagesavvy

Disclaimer: EMCer here - Compression, 64-Bit Aggregates, and DataMotion all sound like great features from an upgrade.

A Few Questions:
Can you convert existing 32-bit aggregates into 64-bit aggregates after the upgrade and then increase the size? Or do you need to create new aggregates on different spindles?

Can you use DataMotion to migrate existing LUNs from 32-bit Aggregates into 64-bit Aggregates to take advantage of compression for existing data?

Thanks!

Vaughn Stewart

@Richard (aka Storagesaavy) -

Thanks for following and the inquiry. As I mentioned in the summary we are enhancing a number of the technologies shared in this post and in-place upgrades from 32-bit to 64-bit aggregates is one.

Today customers can create 64-bit aggregates, and obviously if they are looking to leverage some of the new capabilities that is available from them they have a number of ways to non-disruptively migrate their datasets to them. As I focus on cloud, I'd suggest that Storage VMotion enhanced with VAAI is one such method.

As you brought up compression and are with EMC I feel compelled to clarify some terminology as I don't believe engineers from EMC & NetApp speak the same language. NetApp provides block level dedupe on all arrays, for all datasets accessed over any protocol. It's use enhances performance and we promote it's use globally.

Compression is a technology that enhances storage savings, but ideally should be used with datasets that have low IO requirements.

I make these distinctions as most I engage with from EMC do not believe NetApp can actually dedupe disk and array cache, and as such tend to rely on compression and as these EMCers are well versed to the limits/uses cases with compression they tend to apply those limits to NetApp's dedupe capabilities.

Our SAN & NAS customers love dedupe and are seeing phenomenal results, as such I'd suggest the larger data sets, larger pools of I/O, and increased drive capacities are the driver to 64 bit aggregates more than compression.

Storagesavvy

Thanks for the reply. I personally do understand the differences between EMC Compression and Deduplication and NetApp Deduplication and Compression features but it's always good to point out to customers. With ALL of the technologies from both vendors, as with anything in life, there are cases where the benefits outweigh the drawbacks and cases where the opposite is true. I was using compression as an example enhancement of the 64-bit aggregates, of course maximum usable capacity is another major one.

Lenny

Not supported on FAS2050s and if you have a large snapmirror relationships you're stuck on 7.x

ben

Any news about forthcoming Snaplock compliance support for the Ontap 8x platforms yet?

Vaughn Stewart

@Lenny - you are correct, 8.0.1 is not available on the older hardware platform

@Ben - Let me see if we I can share publicly.

Flemming Riis

Any news on when compression licenses is released to the general public

The comments to this entry are closed.

TRUSTe CLICK TO VERIFY