Storage Fail over

An HA pair is two storage systems (nodes) whose controllers are connected to each other directly. In this configuration, one node can take over its partner’s storage to provide continued data service if the partner goes down. You can configure the HA pair so that each node in the pair shares access to a common set of storage, subnets, and tape drives, or each node can own its own distinct set of storage. The controllers are connected to each other through an HA interconnect. This allows one node to serve data that resides on the disks of its failed partner node. Each node continually monitors its partner, mirroring the data for each other’s nonvolatileRead More

Flash Pool

A Flash Pool is the newest addition to the NetApp® Virtual Storage Tier. It is a technology that allows Flash technology in the form of solid-state disks (SSDs) and traditional hard disk drives (HDDs) to be combined to form a single Data ONTAP® aggregate. When SSD and HDD technologies are combined in a Data ONTAP aggregate, the NetApp storage system takes advantage of the latency and throughput benefits of SSD while maintaining the mass storage capacity of HDD. Requirements for using Flash Pools   The Flash Pool technology has some configuration requirements that you should be aware of before planning to use it in your storage architecture. Flash Pools cannot be used in theRead More

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 guaranteeRead More

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 rootRead More

How to upload a core file for analysis

This article describes the procedure to be followed to upload a clustered Data ONTAP 8.x core file for analysis. A clustered Data ONTAP 8.x node has experienced a panic or a forced panic has been triggered. The core needs to be uploaded to NetApp for analysis. PROCEDURE There are three methods for transferring a core from a clustered Data ONTAP node to NetApp. To determine the core name, run the core show command to find the appropriate file: Note: Verify that the core has been saved before starting the upload process.  If not, use the command coredump status to view the current status. ::> core show Node    Core Name                             Saved    PanicRead More