Hello
With classic or 7G Data ONTAP, all of the administration is stored in flat files on each storage system.
Using Clustered Data ONTAP, all of the administrative information is stored in relational databases that are shared by all systems in the cluster.
This feels more elegant to me because it means that if I want to create a user to perform a function such as backup operator, in 7G, I had to do so on every storage system, in cDOT, I create the user once for all the systems.
The same holds true for what we used to call exports and now call export policies. You create them once per cluster even if you have 20 storage systems in a cluster.
And what is
really handy and nice is the tab for completion. Once you get used to tabbing through a command line, you want to use that on your 7-Mode systems.
But you might feel like it is necessary when simple command like:
ping nodename
becomes
network ping -node local -destination node name
Ramp up takes some time.
In my opinion, Clustered Data ONTAP is a paradigm shift. You can simple map the commands one to one between 7G and cDOT because the implications are different but once you get used to it, it is very hard to go back. You feel like you are traveling back to the early 90s when you use the 7G systems.
That is my take on it.
--April
On Wednesday, November 6, 2013 1:15 PM, tmac <tmacmd@gmail.com> wrote:
The tool appears to be directed to
small installations.
If you have large/complex systems, it would be best to enlist the NetApp PS crew.
I used the the tool that preceeded the 7MTT...the Volume Transition Wizard...which by
the way may panic a destination running 8.2...found out the hard way! The VTW worked
OK prior to 8.2.
It was easy to setup per volume. I have not played much at all with the new tool as now that
I am migrated, I really have no use for it ;)