Jump in! The water is just fine… or is it?
NetApp’s Clustered Data ONTAP (cDOT) is the place to be from a technology and performance point of view. As NetApp administrators quickly become aware, the transition away from 7-mode is not as simple as flip of a switch. NetApp’s CEO Thomas Georgens understands this, “The complexity and duration of clustered ONTAP transitions have implications on several dimensions.”
The technical literature on this transition talks about three main stages: Identify, Design, and Implement. That first step, “Identify”, is by far the most important in determining your data migration plan and costs, and it is by far the most time consuming.
My fellow NetApp Admin, as the migration process begins to take form, you soon will be asking yourself:
- How do I even begin to identify all the dependencies between NetApp nodes?
- I have so many SnapMirrors (SM) and SnapVault (SV) interdependencies. Are there “low hanging fruit” that need to be addressed first?
- What nodes are hidden hubs to SnapMirror and SnapVault relationships?
- Which nodes are too critical and should be done last?
- My data migration costs are too high! Where is my stale or unmodified data and how do I avoid moving it?
Catalogic ECX can help you!
As an integrated Copy Data Management platform, Catalogic ECX does what other solutions only dream about: ECX creates an actionable catalog of all the ONTAP objects and the relationships between these objects. See a demo of how ECX’s management, orchestration, and analytics engine.
Here are 3 ways that ECX can help:
We’ve just added NetApp Transition Dependency report (See Figure 1) that will further empower you in your 7-mode to cDOT transition.
This report can help cutting the time, cost, and staff needs for your transition, understanding all your ONTAP relationships is the key.
It provides both a summary and detailed view of all the SnapMirror and SnapVault relationships for your whole environment.
The Summary View (Figure 1) gives all the relationships (with a count) to clearly show the weight of the dependencies between different nodes.
The Detailed View (Figure 2) further empowers you by delineating exactly the relationships source and destination for SnapMirror and SnapVault.
NetApp Admins know that NetApp’s initial successes were around the NAS functionality. Those who embraced NetApp early on are still heavy users of this functionality, therefore this becomes another area where migrating to cDOT is costly.
Think of it this way. If you were moving to a new house, you wouldn’t want to move 100% of your current house! Moving all the “extra” stuff costs time and money… You first throw away, you donate, you purge as much as possible.
Why aren’t you doing the same with your NetApp files?
With our catalog, we have a set of File Analytics capabilities; one example is our Files By Age report. (Figure 3)
You can find files based on created/accessed/modified date and get a summary view of the date distribution, and also export a list of those files with full path.
ECX helps you decide which data should be moved or deleted.
With our VM workflows deployed ahead of the migration, (Figure 4) there is no need to rework any policies and that it would just automagically work. Less procedures to change, less risk and therefore makes planning less painful.
ECX snapshot management for your NetApp and VMware environment (both on NetApp or any other vendor) automates the creation of copies. Because the NetApp workflows work for both 7-mode and cDOT, migrating your processes will be much easier.
In summary, when it’s time to migrate to cDOT, and before jumping into anything, the key is to know what you’re getting into.
Specifically for cDOT, the initial identification phase really sets up the tone for the rest of the project. Catalogic ECX is the key to answering many of those vital questions.
Your next steps should be:
Go ahead, leverage Catalogic ECX, then be ready to jump in and join the cDOT party!