We have come across a very bizarre issue whereby front-end data throughput to a Netapp Altavault appliance randomly reduces until the services have restarted.
In this video tutorial, I dive into my lab and guide you through the steps involved to successfully migrate a Microsoft SQL cluster from a Netapp 7-Mode system to Clustered Data Ontap, utilizing the Netapp 7-Mode Transition Tool.
I was looking through a bunch of syslog messages for our c-mode systems the other day and came across a repeated message which was:
The other day I was working on a customer VMware vCenter server along with some Netapp storage. The storage being NFS mounted to each ESXi server.
The Netapp 7MTT software helps you easily migrate from Data Ontap 7-Mode to Clustered Data Ontap via an easy to use step-by-step wizard.
One of the buzz words around Netapp Ontap 9 is the new feature of data compaction. Working along side other storage efficiency mechanisms such as dedupe and compression, data compaction is able to further reduce your data foot print.
Ontap 9 is still relatively new, only being released a few weeks ago and with all the hype around the new features and performance gains between previous versions, I really wanted to see this for myself.
If you have been working with Netapp Clustered Data Ontap for a while now you would no doubt have performed quite a few volume moves. However one limitation of the volume move command was that you couldn’t move the volume between storage virtual machines (SVM’s)
The Cisco Nexus 9K’s have been out for a little while now, however it has only been recently that the support for FCoE have come to these switches.
If you are taking non-zeroed disks from a later version of Netapp Data Ontap and placing them into a system running an earlier version of Data Ontap you may experience the following warning, error and critical messages in the log: