180 likes | 603 Views
cDOT Deployment: Lessons Learned From a PS Perspective May 2013. Overview. Transition Best Practices Architectural Best Practices What you can do to prepare How you can prepare the customer Q&A. Definition of Transition. How NetApp Defines Transition…
E N D
cDOT Deployment: Lessons LearnedFrom a PS PerspectiveMay 2013
Overview • Transition Best Practices • Architectural Best Practices • What you can do to prepare • How you can prepare the customer • Q&A NetApp Confidential - Internal Use Only
Definition of Transition • How NetApp Defines Transition… • All encompassing and not just the movement of bits • Data migration is subcomponent of Transition • Transitioning data, processes, & similar functionality to a new architecture • Impact to operations (staffing, monitoring and tools, education) • Adapting to new functionality
Transition Best Practices • Different architectures & feature parity considerations in 7toC transitions • Qualifying the environment • Transition Advisor - Automated profiling based on ASUPs • Still some manual checking & customer conversations • Data classification • Role of Qtrees in customers environment – NFS, Multiprotocol, & QSM • SAN data • NAS data • Understanding limits (Volume, LIF, SnapMirror, etc..) • SnapMirror & SnapVault considerations • Consolidation vs. multiple vservers • Tools and methodology
Transition Tools • Qualifying Tools • Pre Sales • Transition Advisor • System Performance Modeler (SPM) • Autosupport • Post Sales • Configuration Advisor (Installation) • 7-Mode Transition Tool (pre-check only)
Transition Tools – Continued • Data Movement Tools • NAS Migrations • 7-Mode Transition Tool (7MTT) – GUI & CLI • WFA Automation • NDMPCopy • Host-based (RSYNC, Securecopy, etc..) • SAN Migrations • DTA 2800 appliance (iSCSI/FCP) • Volume managers • Application Based (Storage vMotion, ASM, etc..) • Host-based (RSYNC, Securecopy, etc..)
Architectural Best Practices • Architecture • Could start out with a simple design and add features as needed - cDOT has a lot of flexibility! • Architecture can be as simple or as complex as the customer requires • Understand customer AND solution requirements • Naming conventions • If it can move, do not include the node name • Networking • Direct vs. Indirect - Most likely your original design will change over time • Failover groups & Fencing
What You Can Do to Prepare • Educate • NetAppU - New 8.2 courses & curriculums • Engagement Delivery Trails (EDT) • Practice transitions & learned skills • CIFS/NFS (SAN with scheduled sessions) • Lab on Demand • Workshops • Peer enablement • Enablement • Understand the customers environment/requirements • PS involved earlier in the Pre-Sales process • Involve NetApp to understand feature gaps and limitations • Leverage lab & simulators to prototype solutions • Empower • Review relevant TR articles applicable to solution
EDT Activity Overview • In LOD, discover 7-Mode Systems Configuration • Design Clustered ONTAP configuration to support customer requirements • Determine which tools will be used for the data migration • Develop the data migration plan • Implement Clustered ONTAP design on Clustered ONTAP cluster • Perform initial data migration • Perform final cut over • Validate your results NetApp Confidential – Limited Use
What You Can Do to Prepare the Customer • Educate • Allocate time for training: Before/During/After • Provide a customer TOI prior to deployment • 5 Day Admin Course • Enablement • Leverage transition tools to qualify environments • Preparing the customer environment (Monitoring, Scripts, etc.) • Clean up existing environment • Empower • Residencies for new transitions • Onsite labs for larger deployments or test Vserver • Provide relevant TR articles applicable to solution
Q & A Questions & Answers
Value of clustered Data ONTAP® Multiprotocol Access (NFS/CIFS/FC/iSCSI/FCoE) • Non-disruptive operations • Scale outNAS / SAN architecture • Unified Management • Virtualized Infrastructure • Consolidated Architecture • Leverages existing multi-protocol access and storage efficiencies Virtualized Storage and Network FC or SATA SAS FC SAS SATA SSD Third-Party Arrays with V-Series NetApp Storage Data ONTAP 8.1 Cluster-Mode System Legal Notices
Key Similarities • Provisioning (Aggregates, snapshots, storage efficiency) • Data Protection • Leveragessame current hardware • Management via System Manager • Disk to disk backup* * Note - SnapVault similar but has been completely redesign
Key Differences • Non disruptive operations and Tech Refreshes • Architecture • Vserver foundation • Virtualized Networking • Virtualized Storage • Scale out Namespaces • Cluster Interconnect • Monitoring • Unified Management • Centrally managed hardware/software • CLI: More powerful! Context driven/Object oriented • Some migration tools and methods