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

Generation of NetApp

Last week I had to install some NetApp systems and migrate data to it. The first NetApp was a FAS2650 Installation was going smooth and after 2 hours, the system was fully up and running. I had to migrate all the data from a FAS 2040, so reconfigure the system and prepare for migration was the last to do that day. Looking at the next day, I had to replace a FAS 2240-2 with a FAS2552. Hmmm, really a week of now you see them, now you don’t. Mostly I work with the larger system, but it’s nice to see that even the smaller system work the same, do the sameRead More

Upgrade UCS Firmware

Recently I was performing an upgrade to a UCS environment to support some new B200 M4 blades. The current firmware version only supported the B200 M3 blades. With UCS firmware there is a specific order to follow during the upgrade process. The order to follow is: Upgrade UCS Manager Upgrade Fabric Interconnect B (subordinate) & Fabric B I/O modules Upgrade Fabric Interconnect A (primary) & Fabric A I/O modules Upgrade Blade firmware by placing each ESXi Host During the upgrade process, and particularly during the Fabric Interconnect and I/O module upgrades you will see a swarm of alerts coming from UCSM. This is expected as some of the links will beRead More