Shulou(Shulou.com)06/01 Report--

This article will explain in detail what the features of ONTAP 9.2 are, and the content of the article is of high quality, so the editor will share it with you for reference. I hope you will have a certain understanding of the relevant knowledge after reading this article.

Well, that is, the half-yearly version, the pace is still quite fast.

However, the launch of ONTAP 9.2 coincides with NetApp's 25th birthday, so NetApp still pays more attention to it, after all, it is a birthday present.

You see, as a birthday present, there is actually that HCI, the computing node and storage node of the NetApp HCI in front of me are separated, which is also called super fusion? The propaganda idea is a bit like the parameter emperor Pivot3! A comment has been made on the article.

There are still some interesting new features in ONTAP 9.2, let's take a look at them today.

Support minimum QoS policy

As we all know, there are very few storage products that support the minimum QoS configuration, and only SolidFire and Huawei OceanStor v3 are common. I mentioned in my article that not all QoS can ensure the performance of critical business. The minimum QoS policy can ensure the minimum performance of critical business, while the maximum configuration can only prevent the destruction of bad neighbors and cannot guarantee the minimum performance.

After NetApp acquired SolidFire, it found this minimum QoS strategy useful, so it is now implemented in ONTAP 9.2.

At present, this minimum QoS strategy only supports all-flash SAN environments, that is, it is not available on NAS and hybrid arrays.

Cross-volume online re-deletion

Before ONTAP 9.2, although ONTAP supports online re-deletion and post-delete re-deletion, the re-delete domain is only in one volume. That is, its re-deletion can not cross the volume, this re-deletion efficiency is too low. For example, the duplicate data in the following two volumes cannot be re-deleted.

ONTAP 9.2 now supports aggregating online re-deletions, which can span volumes. That is, the duplicate data of the following two volumes can be re-deleted.

However, there are still some restrictions on this. Currently, only AFF systems are supported, that is, they must be re-deleted online, and the maximum capacity of a single Aggregate is only 800TB.

Let's compare the implementations of other AFA products: EMC's XtremIO re-deletion cannot be turned off, so its re-delete domain is global. The re-deletion of Huawei's Dorado v3 can be based on the LUN granularity switch, but the re-delete domain is a storage pool, that is, it can span volumes, and there is no size limit. Currently, Dorado v3 can only configure one storage pool, so you can understand that the deletion domain is also global.

FabricPool migrates to Cloud

A few months ago, EMC's VMAX3 supported snapshots (block's) directly to the public cloud. Now, ONTAP 9.2 introduces the FabricPool feature, which also supports the public cloud as a layer of block storage. Users can migrate cold data to the cloud, but keep pointers locally. In the past, this feature was more targeted at files, but now it also supports block devices.

However, this feature can only be implemented in a full SSD configuration, which probably requires a fast Cache.

Is not a little strange, the future storage will be divided into two layers, one layer is very fast SSD, and then the second layer is very slow public cloud. Just like the Liu Guoliang incident of the Chinese table tennis team, although the flattening management is good, is it too sudden? EMC does not seem to require all-flash memory, I remember, that is, other people can have more levels.

Anyway, it is estimated that this feature can be used in the following three scenarios.

1. Hit the snapshot to the cloud to save the space of the main storage and achieve the purpose of backup at the same time.

2. When doing array replication, the second storage can directly utilize the capacity of the cloud and reduce the investment.

3. When doing HA, the second site can also make use of cloud space.

Support for SLO configuration similar to EMC VMAX3

As you all know, EMC VMAX3 supports configuration based on the level of service (see EMC releases new high-end storage VMAX3, Don't cry, HDS), and now ONTAP 9.2 also introduces this feature. That is, the user only needs to tell you the performance and capacity you need, and ONTAP finds the right node (in a scale-out cluster) to provide the LUN. However, the principle is different, EMC VMAX3 mainly uses its FAST feature to adjust the service level, while NetApp feels that it is more likely to match SLA requirements by finding different nodes.

Of course, SLO configuration of NAS is also supported. I like this configuration. It's much easier to manage. Huawei's OceanStor DJ can also provide this feature, but DJ is mainly aimed at multi-array scenarios, if only the QoS management of a single array can be configured according to the level of service.

Software-only ONTAP Select enhancement

ONTAP Select 9.2 is a pure software form with a lot of enhancements. For example, HA supports 2 nodes (4 nodes are originally needed) and vNAS is supported, that is, NAS features are provided by VM running ONTAP, but storage resources are provided by external storage or vSAN.

What are the features of ONTAP 9.2 to share here, I hope the above content can be of some help to you, can learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.