NetApp EF-Series New SANtricity System Manager

NetApp EF-Series New SANtricity System Manager 


First access through the SANtricity Manager and also you could see all the storage systems which is managed by the SANtricity Manager.

To Manage the Storage System E2800 Series, This will open in System Manager.

You can view the complete dash board.

You can view the capacity, performance and complete storage hierarchy.

In Storage tab, You can create and manage Pools, volumes, host mappings and Data protection like snapshots and Mirroring.

Using Hardware tab, You can view the complete Hardware information of Storage Systems.

To view the disk shelves and Bay information.

Using this you can set all network management.

Setting Network Management ports.

Managing Disks.

Creating Pools and Volume Groups.

Creating New Pool.

Creating New Volumes.

Select the host and work load information.

 Volumes view with details.

For volume Mapping, Create new hosts.

Creating New Hosts.

Now Map the volume to the assigned Host.

ONTAP 9.1 SVM ROOT VOLUME PROTECTION

SVM ROOT VOLUME PROTECTION:

To protect the Storage Virtual Machine (SVM) namespace root volume, you can create a load-sharing mirror volume on every node in the cluster, including the node in which the root volume is located. Then you create a mirror relationship to each load-sharing mirror volume

and initialize the set of load-sharing mirror volumes.

Creating load-sharing mirror volumes

For protecting the root volume of a Storage Virtual Machine (SVM), you must create a FlexVol volume on every node of the cluster and designate it as a load-sharing mirror destination.

Creating load-sharing mirror relationships

You must create a load-sharing mirror relationship between the root volume of the Storage Virtual Machine (SVM) and each of the load-sharing mirrors created for the SVM root volume protection.

Create LS mirror relationship first.

Then initialize  the load share mirror set.

Now it is transferred and snapmirrored.

Check field type of volumes.

Restoring the SVM root volume by promoting a load-sharing mirror

If the Storage Virtual Machine (SVM) root volume becomes unavailable, read access is provided through the load-sharing mirror volumes. To enable write access to the SVM root volume, you must promote one of the load-sharing mirror volumes and rename it with the original SVM root volume name.

For restore, promote any other volume act as a SVM root volume.

Now check the volume type.

ONTAP 9.1 Volume Efficiency Features

De-duplication, data compression, and data compaction:

Ontap 9.1, using deduplication, data compression, and data compaction feature to increase storage efficiency of your storage systems.

You can run deduplication and data compression together or independently on a FlexVol volume or an Infinite Volume to achieve optimal space savings. Deduplication eliminates the duplicate data blocks and data compression compresses the data blocks to reduce the amount of physical storage required.

Data Compaction:

Inline data compaction stores multiple user data blocks and files within a single 4 KB block on a system running ONTAP. Inline data compaction is enabled by default on All Flash FAS (AFF) systems, and can be optionally enabled on volumes on FAS systems.

The volume space guarantee must be set to none.

Without data compaction, ONTAP stores each file in one or more 4 KB blocks on solid state drives (SSDs) and hard disk drives (HDDs). Data compaction increases storage efficiency by storing more data in less space.

The data compaction process has CPU overhead, and is best suited for faster controllers. Storage savings can be significant for environments with highly compressible I/O and small files or I/O.

If enabled, data to be written goes through inline zero deduplication, then inline compression, and then inline deduplication. Data compaction takes place after compression and deduplication, and is independent of these operations.

For example, assume files of the following sizes have been compressed and are ready to write to SSD:

 Without data compaction, each file would get its own 4 KB block, consuming 36 KB:

With data compaction, multiple files are written to each 4 KB block, consuming only 12 KB:

To enable the Compaction for FAS systems :

To check the compaction status of Aggregates and Volumes.

To enable the compaction of FAS systems.

To enable the volume efficiency of volume vol_db1.

To check the inline duplication, compression and compaction.

To enable the compression and inline compression.

Create a Flecvol using only SSD disks.

Enable compression and compaction.

§You can move between secondary compression and adaptive compression depending on the amount of data read.

§Adaptive compression is typically preferred when there are lot of random reads on the system and higher performance is required.

§Secondary compression is preferred when data is written sequentially, and higher compression savings are required.

Undo the compression first.

Now change the compression type.

There are two types of policies,

One is Scheduled and another one is Threshold.
Create a new threshold policy type.

Associate this policy to the volume.

To check space by volume efficiency.

To check the volume efficiency statistics.