NetApp Transition Fundamentals

Print Slides https://www.brainshark.com/brainshark/viewer/PrintSlides.aspx?pi=854688475&sid=3158639...
NetApp Transition Fundamentals
Welcome to NetApp Transition Fundamentals. As storage administrators demand ever more

features from their enterprises, many customers are transitioning from Data ONTAP
operating in 7-Mode to the clustered Data ONTAP operating system. This course helps you
understand how to transition from a 7-Mode environment to the more flexible and scalable
storage of the clustered Data ONTAP operating system.
1 de 84 09/04/2018 12:59 p. m.
Course Objectives
This course focuses on enabling you to transition from Data ONTAP operating in 7-Mode to
clustered Data ONTAP, identify the technical considerations for migrating data to a clustered
Data ONTAP system, and analyze workload and environmental requirements and determine
which tools to use for migration.
2 de 84 09/04/2018 12:59 p. m.
Module 1 Transition Terms and Phases
In module 1, you learn the terms and phases we use to describe and categorize aspects of
transition.
3 de 84 09/04/2018 12:59 p. m.
Module Objectives
This module focuses on enabling you to define the terms that are relevant to a transition
from 7-Mode to clustered Data ONTAP and describe the activities that are involved in a
transition from 7-Mode to clustered Data ONTAP.
4 de 84 09/04/2018 12:59 p. m.
Definitions of Transition Terms
The words “transition” and “migration” mean different things. “Transition” refers to the
people, processes, and technological activities that are involved in moving from a 7-Mode
environment to a clustered Data ONTAP environment. “Migration” refers to the process of
copying or replicating data from a source storage system to a destination storage system.
Data-migration activities are a subset of transition activities. For a transition, you can
migrate data in one of two ways. For a copy-based transition, you copy data from the
source system disks to the destination disks. For a copy-free transition, you disconnect the
disks from the source system and then connect the disks to the destination system.
5 de 84 09/04/2018 12:59 p. m.
Definitions of Transition Terms
“Operationalization” refers to the transfer and modification of storage-system dependencies.

The dependencies can be related to people, processes, or technologies. “Applications” refers
to the applications that are deployed in the environment, such as databases, content-
management software, Microsoft Exchange, and applications that were created within your
company. For the purposes of transition, virtualized infrastructure is categorized as an
application. A workload is a primary (that is, client-generated) load that is placed on the
storage system. Applications generate workloads, but workloads are not necessarily
application-specific. For example, home directories are categorized as workloads. A storage
container is a storage object that is being moved from the source. The object can be a
storage system, an aggregate, a volume, a LUN, a qtree, a directory, or (sometimes) a file.
6 de 84 09/04/2018 12:59 p. m.
The Journey to Clustered Data ONTAP
The transition-fundamentals framework focuses on the knowledge that you need to

transition from 7-Mode to clustered Data ONTAP. Transition begins when you decide to adopt
clustered Data ONTAP and move your 7-Mode environment. As the transition activity
progresses, your NetApp environment becomes a mix of 7-Mode and clustered Data ONTAP.
After the transition activity is complete, your NetApp environment operates solely on
clustered Data ONTAP.
7 de 84 09/04/2018 12:59 p. m.
Three Phases of Transition
The topics in the transition-fundamentals framework can be organized into three phases:
identification, design, and implementation.
8 de 84 09/04/2018 12:59 p. m.
Three Phases of Transition: Identify
The identification phase focuses on business decisions. In the identification phase, you
identify which storage containers to transition and the order in which to transition them. To
perform the identification activities, you must know which applications and workloads are
deployed in your 7-Mode environment. You then consider how to group systems,
applications, and workloads. Groups are moved together, and you prioritize the movement
of groups based on business requirements.
9 de 84 09/04/2018 12:59 p. m.
Three Phases of Transition: Design
The design phase focuses on the planning activities that are related to the transition. During
the design phase, you create a detailed cluster architecture for the destination clustered
Data ONTAP system. You create the architecture based on the capabilities that the cluster
will need in order to support the migrated workloads and the potential future needs of the
storage system. You also analyze the 7-Mode environment and plan for migration.
10 de 84 09/04/2018 12:59 p. m.
Three Phases of Transition: Implement
The implementation phase focuses on the deployment and configuration of the destination
cluster and the migration of workloads and data from 7-Mode to clustered Data ONTAP.
Implementation activities also involve updates to the operating environment. The updates
ensure that the NetApp environment and all technologies that depend on it work as
expected.
11 de 84 09/04/2018 12:59 p. m.
Transition Fundamentals: Not a Process
The transition-fundamentals framework is not a process. The framework logically organizes

core topics that identify transition activities and indicates how you accomplish tasks.
Customers use their own workflows and processes to execute similar projects. The
transition-fundamentals framework can be used within a customer’s existing processes or
workflows. Although the framework is not a process, it provides a logical flow of transition
tasks and activities. When you apply the transition-fundamentals framework, start with the
identification activities, move to the design activities, and conclude with the implementation
activities. NetApp and its partners provide a standard process for delivering transition-
related services to customers. The process is called the “Unified Transition Methodology,” or
“UTM.”. The transition-fundamentals framework provides knowledge, and the UTM process
puts that knowledge into practice. UTM is not required or mandatory. The UTM process is
used by customers who engage with NetApp services to assist with their transition from
7-Mode to clustered Data ONTAP. UTM can be used to augment existing processes. You can
implement the UTM steps from “end-to-end.” Contact your NetApp representative for more
information about transitioning services. For additional UTM training, see the “Introduction
to the Unified Transition Methodology Framework” course. Some transition activities are
iterative. For example, when the first systems and workloads move to clustered Data
ONTAP, you might see all of the transition-fundamentals phases applied, from identification
through implementation. Other data migrations might then iterate through the
implementation activities, until all planned systems and workloads are transitioned to
clustered Data ONTAP.
12 de 84 09/04/2018 12:59 p. m.
NetApp Premier Transition Tool: 7MTT
For transition activities, NetApp provides the 7-Mode Transition Tool, or the 7MTT. The 7MTT
tool enables source discovery, automates data migration, and supports NFS and CIFS
migration as well as SAN migration. Recently added features include improvements to the
process of migrating SAN workloads to clustered Data ONTAP 8.3. For example, now, LUN
maps are maintained during the resynchronization, and the SAN Host Remediation Tool is
bundled with the 7MTT installation files. The transition of 7-Mode MetroCluster
configurations to clustered Data ONTAP 8.3 is also supported. When you use 7MTT, you can
choose copy-free transition, copy-based transition, or a combination of the two types of
transition.
13 de 84 09/04/2018 12:59 p. m.
Module Summary
This module focused on enabling you to define the terms that are relevant to a transition
from 7-Mode to clustered Data ONTAP and describe the activities that are involved in a
transition from 7-Mode to clustered Data ONTAP.
14 de 84 09/04/2018 12:59 p. m.
Module 2 Transition Phase: Identify
In module 2, you learn about the first phase of transition: identification of the current
environment and the scope of transition.
15 de 84 09/04/2018 12:59 p. m.
Module Objectives
This module focuses on enabling you to identify the tools that you use to discover an
environment, use those tools to discover an environment, and define the scope of a
transition.
16 de 84 09/04/2018 12:59 p. m.
Identification Phase
The first part of the identification phase is environment discovery. In environment discovery,
you identify the systems, workloads, applications, constituent groups, and business
requirements of your 7-Mode system. The second part of the identification phase is scope
definition. In scope definition, you identify the components of the 7-Mode environment that
will move to the new system and the order in which the components will move. Although
technical considerations affect some of the identification activities, your decisions are
primarily motivated by business considerations.
17 de 84 09/04/2018 12:59 p. m.
Environment Discovery
In environment discovery, you produce a list of applications and workloads and identify the
storage systems on which the applications and workloads depend. Collect enough
information that you can make an informed business decision about scope. Determine
business and cutover requirements for each application or workload. During this process,
engage with constituent groups that rely on the 7-Mode environment, so that you can
evaluate priorities and business requirements. If your systems report AutoSupport
information to NetApp, go to My AutoSupport and use the Transition Advisor tool to view
and identify the 7-Mode storage systems that are deployed.
18 de 84 09/04/2018 12:59 p. m.
Environment Discovery with 7MTT
You can also use the Collect and Assess functionality of the 7-Mode Transition Tool (or
7MTT) to collect information about your 7-Mode storage systems and clients. This tool helps
you prioritize by recommending the storage systems that are ready to move first and by
identifying the systems that require additional consideration. This step uses the
Interoperability Matrix Tool (IMT) as a cross reference. The 7MTT tool collects the technical
information that you need for transition planning and cluster design. You should use the
7MTT Collect and Assess functionality even if you don’t use 7MTT for data migration. To
collect information about affected systems, use the Inventory Collect tool. This tool
generates an inventory report workbook and an inventory report XML file. The workbook can
be imported into the 7MTT tool for transition assessment. You use the XML file if 7MTT
cannot be installed or run inside a data center, but 7MTT can be used in an offline
environment.
19 de 84 09/04/2018 12:59 p. m.
Scope Definition
When you define the scope of the transition, you create groups of storage systems,
applications, or workloads. The items within the groups move together to clustered Data
ONTAP. You can divide your environment in either of two ways. You can divide by the
7-Mode storage controllers and the workloads that they host. Or, you can divide by the
applications, workloads, or constituent groups that rely on the storage system. If you use
the second approach, only a subset of the storage containers on the 7-Mode system might
move with any particular group. When you group the systems, consider various issues. The
issues that you should consider include the cutover requirements for the applications,
workloads, or storage systems; the location of the dependent storage containers on the
7-Mode storage systems; the system warranties and technical-refresh schedules; and the
readiness of the storage system to move to clustered Data ONTAP. When you assess
readiness, consider the feature and functional differences that must be addressed before
the transition begins. Consider also that data protection adds restrictions, which affect the
workloads that can replicate first and how protection might change. Also identify FC zones
and decide whether to deploy the same switch or a new switch in the clustered
environment. After you establish the groups, prioritize them. Specify the order in which the
groups will be transitioned by assigning a priority number to each group.
20 de 84 09/04/2018 12:59 p. m.
Module Summary
This module focused on enabling you to identify the tools that you use to discover an
environment, use those tools to discover an environment, and define the scope of a
transition.
21 de 84 09/04/2018 12:59 p. m.
Module 3 Transition Phase: Design
In module 3, you learn about the second phase of transition: design. In the design phase,
you plan the transition and design the destination cluster.
22 de 84 09/04/2018 12:59 p. m.
Module Objectives
This module focuses on enabling you to describe the components of transition planning, use
planning tools, and identify the key factors that affect a transition. The module also focuses
on enabling you to design a clustered Data ONTAP system that supports current 7-Mode
workloads and expected future business requirements.
23 de 84 09/04/2018 12:59 p. m.
Design
The purpose of the design phase of transition fundamentals is to plan your transition activity
and determine the cluster requirements of the destination system. In transition planning,
you plan how to migrate data from the source 7-Mode systems to the destination clustered
Data ONTAP system. You plan the environmental updates that must be made to the areas of
the operating environment that are outside the storage system. And you plan how to train
administrators to use the features of the clustered Data ONTAP system. In cluster design,
you determine the architecture of the target clustered Data ONTAP system. You base your
determination on the 7-Mode environment that is being moved. You also consider the
expected future business requirements for the new or existing cluster.
24 de 84 09/04/2018 12:59 p. m.
Transition Planning
As part of transition planning, you document how you will move your 7-Mode environment
to clustered Data ONTAP. Your plan can be simple or complex. A system with a small
footprint might require only two high-availability (or HA) pairs of controllers. But an
environment with hundreds of systems and complex disaster-recovery relationships might
require a highly complex plan. For transition planning, you must perform a detailed
technical discovery and document your findings. You map the 7-Mode storage containers to
their clustered Data ONTAP equivalents and assess the 7-Mode features. You identify the
existing recovery and backup relationships. And you identify the migration method to use
for each storage container that you will move. During transition planning, you also list the
management applications that require updates. In some environments, management
activities involve scripts that use Data ONTAP CLI commands or APIs. If you use scripts, you
must document and assess the scripts to identify potential changes. Finally, you create a
plan for providing clustered Data ONTAP training to 7-Mode administrators.
25 de 84 09/04/2018 12:59 p. m.
Transition Planning
Whether you plan to migrate data by controller or by workload, identify all of the storage
containers that will be moved from the source system. Then, map the storage containers to
their destinations in clustered Data ONTAP. The information that you get helps you select an
appropriate migration method and identify cluster-design and configuration requirements.
26 de 84 09/04/2018 12:59 p. m.
Transition Planning
In addition to listing the storage containers of the source controller, list the Data ONTAP
features that are on the source system. Some features might be licensed or enabled on the
7-Mode system but not in use. For each discovered feature, determine whether the feature
is in use. Then assess the features to determine whether each feature will be used in the
clustered Data ONTAP system or is deprecated in the 7-Mode system. For each feature that
is in use, determine if clustered Data ONTAP has the same feature or another feature that
provides equivalent functionality. In rare cases, no equivalent to a deprecated 7-Mode
feature is available in clustered Data ONTAP. Refer to “Technical Report 4052: Successfully
Transitioning to Clustered Data ONTAP” for detailed information about 7-Mode feature
assessment.
27 de 84 09/04/2018 12:59 p. m.
Transition Planning
You can complete a technical discovery manually. However, NetApp provides tools for
automating technical discovery. You should use the 7MTT Collect and Assess feature for all
discovery and transition-planning activities. The collection component discovers information
from Windows, Linux, and VMware ESX hosts and from your 7-Mode storage system. The
discovery component provides information about storage configuration for 7-Mode features
and functionality, and also about common enterprise applications and SAN host specifics.
The assessment component determines if a feature or its functionality differs between
7-Mode and clustered Data ONTAP. The Collect and Assess feature also compares HBA
model numbers and firmware against the Interoperability Matrix Tool (the IMT). The output
of the 7MTT Collect and Assess feature is an executive summary and a workbook. The
summary and workbook provide detailed information about the configuration elements that
are discovered.
28 de 84 09/04/2018 12:59 p. m.
Transition Planning
If security restrictions or other considerations prevent you from installing 7MTT in your
operating environment, use the Inventory Collect tool to execute the collection component
of the 7MTT Collect and Assess feature. When the Inventory Collect tool executes the
collection component, the output is an XML file that you can import into 7MTT offline. 7MTT
then executes the assessment component of the 7MTT Collect and Assess feature against
the XML file. The Transition Advisor tool enables you to assess the features and functions of
7-Mode systems that report weekly AutoSupport information to NetApp. When you use the
Transition Advisor tool to complete an assessment, a report is generated. The report
indicates the functionality changes that need to be made and provides recommendations
about these changes.
29 de 84 09/04/2018 12:59 p. m.
Transition Planning
When you conduct the discovery and planning process, you must include the storage
containers that are in disaster-recovery and backup-related configurations. Each scenario
includes a source storage container and a destination storage container. The containers are
in either a SnapMirror relationship or a SnapVault relationship. NetApp defines 10 common
scenarios for disaster-recovery and backup-related configurations. NetApp also provides
recommendations about how to move data from the source to the destination and how to
transition relationships. We examine two scenarios: a basic disaster-recovery configuration
(that is, source and destination volumes that are in a SnapMirror relationship) and a qtree-
to-qtree migration.
30 de 84 09/04/2018 12:59 p. m.
Transition Planning
To fully understand the transition scenarios in this course, you must first understand the
SnapMirror relationships in clustered Data ONTAP. The first type of SnapMirror relationship is
the data-protection relationship. In a data-protection relationship, the destination container
is a mirror copy of the source container. This type of relationship is used for disaster
recovery. The second type of SnapMirror relationship is a SnapVault “XDP” relationship. In
an XDP relationship, the destination container contains multiple Snapshot copies of the
source container. This type of relationship is used for data archiving. The third type of
SnapMirror relationship is a transition-data-protection (or TDP) relationship. In a TDP
relationship, the mirror relationship is supported only during the migration of data from the
source system to the destination system. The relationship is one-way and exists only during
the transition.
31 de 84 09/04/2018 12:59 p. m.
Scenario 1: Copy-Based Basic Disaster Recovery
The basic disaster-recovery scenario addresses the most common case: a source volume
and a destination volume within a volume SnapMirror relationship. To directly transition a
7-Mode SnapMirror relationship to a clustered Data ONTAP system, you can either use 7MTT
or use a manual SnapMirror TDP relationship. The steps that the 7MTT uses can be
performed manually. Data-migration activities start with the creation of a TDP relationship
from the 7-Mode SnapMirror destination to the clustered Data ONTAP destination. Baseline
and incremental updates are then performed. When the baseline and incremental updates
are finished, 7MTT breaks the 7-Mode SnapMirror relationship and sends a final update to
the clustered Data ONTAP destination. Then, the tool breaks the TDP relationship between
the source 7-Mode system and the destination clustered Data ONTAP system and
establishes a TDP relationship between the 7-Mode source and the clustered Data ONTAP
destination. 7MTT starts the TDP relationship between the 7-Mode SnapMirror source and
the clustered Data ONTAP source. When the baseline and incremental updates are finished
and you are ready to start the storage cutover, you must disconnect the clients. To complete
the migration, 7MTT performs the final incremental updates, breaks the TDP relationship,
and takes the 7-Mode source offline. Then 7MTT upgrades the volumes to clustered Data
ONTAP volumes, establishes a SnapMirror relationship between the clustered Data ONTAP
nodes, and initiates a resynchronization. No baseline transfer is required, because both the
source and the destination share a common Snapshot copy. You can then manually
reconnect the clients.
32 de 84 09/04/2018 12:59 p. m.
Scenario 2: Bidirectional Disaster Recovery
To easily migrate volumes, associated Snapshot copies, and SnapMirror relationships, use
7MTT or use a manual SnapMirror TDP relationship. Although the relationships between the
controllers are bidirectional, from a volume-level perspective, the relationships are
independent and can move independently. In scenario 2, the secondary volume moves to
clustered Data ONTAP first, followed by the primary volume. The steps for performing this
transfer and for performing the transfer in scenario 1 are the same. You apply the same
steps for each independent SnapMirror relationship. A project in 7MTT can migrate the
volumes, the SnapMirror relationships, and the Snapshot copies that are associated with the
relationships. In scenario 1 and scenario 2, the same SnapMirror relationships are
transferred to the clustered Data ONTAP system.
33 de 84 09/04/2018 12:59 p. m.
Scenario 3: Backup
In a backup scenario, existing transition tools can move data. However, you must create a
SnapVault relationship in the clustered Data ONTAP system. The primary data is migrated,
but not all of the SnapVault Snapshot copies that are stored in the 7-Mode secondary
volume are migrated. The new clustered Data ONTAP primary-to-secondary SnapVault
relationship requires a baseline transfer. Because the 7-Mode SnapVault secondary volume
is not migrated, you must consider the retention policy of the 7-Mode SnapVault volume, to
determine how to address recovery scenarios. If the retention policy specifies a retention
period of less than three months, maintain the 7-Mode repository while you build a
retention cycle of three months in the clustered Data ONTAP SnapVault secondary volume.
If the retention policy specifies more than three months, move the 7-Mode SnapVault
secondary data to a new clustered Data ONTAP volume. The new volume is not the
clustered Data ONTAP secondary volume, which is in an active SnapVault relationship. The
retention volume does not contain new data and data is not added to it. The retention
volume is used only for recovery.
34 de 84 09/04/2018 12:59 p. m.
Scenario 4: Copy-Free Basic Disaster Recovery
This diagram shows how to use 7MTT for a copy-free transition of one HA pair that has a
SnapMirror relationship established. The first step is to complete initial verification and
configure the project in 7MTT. If verification is successful, perform the export step and halt
the 7-Mode controllers. The next step is to physically disconnect the disk shelves from the
7-Mode systems and connect them to the cluster HA pairs. This may require only recabling
if the cluster is located close enough, or physically relocating and then recabling the shelves
to the cluster. After the cabling has been verified, import the data and the configuration.
Next, reconnect the clients and run all of the pre-commit tests. If testing is unsuccessful,
revert the transition. If all tests are successful, complete the migration by completing the
commit step. Copy-free transitions support the moving of SnapMirror relationships from
7-Mode systems to a new clustered system. You perform the steps as described here for
both the primary and the secondary systems, and then resynchronize the SnapMirror
relationships.
35 de 84 09/04/2018 12:59 p. m.
Copy-Free Transition
If you plan to perform a copy-free transition, remember these guidelines. Verify that copy-
free transition is supported for the controller models where the 7-Mode system is running
and the controller in the clustered system that you are transitioning to. Also ensure that the
versions of Data ONTAP on both sides of the transition are supported. You can perform a
“CFT-revert” at any time before you commit changes. If you perform a revert, all data that
was written during the pre-commit testing is lost. You can use copy-free and copy-based
transitions in the same transition project. Some data or applications may need to be
migrated first by replication or copying. Other data can be migrated by moving the disks to
the new systems in a second step.
36 de 84 09/04/2018 12:59 p. m.
Transition Planning
In Data ONTAP operating in 7-Mode, qtrees can be used in three ways: for quotas, for
exports, and for replication. In clustered Data ONTAP, qtrees can be used for quotas and
exports, but not for replication. In clustered Data ONTAP, replication is volume-based.
37 de 84 09/04/2018 12:59 p. m.
Transition Planning
You choose how to move qtrees to clustered Data ONTAP based on how you use them
currently in the 7-Mode environment and based on the organizational model that you want
in clustered Data ONTAP. You can migrate qtrees in three ways. For qtree-to-qtree
migration, the volumes that contain qtrees are migrated directly to clustered Data ONTAP.
The organizational structure remains the same. Each qtree in a 7-Mode environment
becomes a single qtree in clustered Data ONTAP. The ratio of qtrees to qtrees is one to one.
For qtree-to-volume migration, each source qtree in 7-Mode is migrated to a single volume
in clustered Data ONTAP. The resulting ratio of qtrees to volumes is one to one. For qtree
consolidation, qtrees with common requirements are grouped and reorganized during
migration. Qtrees are most often grouped to meet replication requirements. Each group of
qtrees in the 7-Mode environment becomes a single volume in clustered Data ONTAP. The
resulting ratio of qtrees to volumes is many to one.
38 de 84 09/04/2018 12:59 p. m.
Transition Planning
In general, reorganize qtrees when the qtrees will be moved to clustered Data ONTAP and
the destination qtree structure will be different from the source qtree structure. However, if
you use qtrees only for quotas, you do not need to reorganize the qtrees. Instead, use the
qtree-to-qtree approach. When you use qtrees for replication and also use a qtree
SnapMirror relationship, you must reorganize the qtrees. You base the reorganization on the
replication requirements for each qtree. However, you must also consider the number of
qtrees in use in the 7-Mode system. For tens to hundreds of qtrees, use the qtree-to-
volume migration approach. For hundreds to thousands of qtrees, use the qtree
consolidation approach. If the number of volumes to be created exceeds the maximum
volume count in clustered Data ONTAP, you must use the consolidation approach.
39 de 84 09/04/2018 12:59 p. m.
Transition Planning
Consider other factors when migrating qtrees, such as how the data will be migrated and
what the quality of service (or QoS) requirements for the migrated workloads are. In
clustered Data ONTAP, QoS does not work at the qtree level. Also consider how the data
might need to move in the clustered Data ONTAP system. Volume-move operations in
clustered Data ONTAP are nondisruptive, but they occur at the volume level. Consider this if
you think that different qtree data may need to move independently. In the clustered Data
ONTAP system, reorganization must not cause maximum volume counts to be exceeded.
Finally, consider the future growth of the data that is in the 7-Mode qtrees. After migrating
the dataset to clustered Data ONTAP, switch to a volume provisioning approach for all new
or incremental dataset requirements.
40 de 84 09/04/2018 12:59 p. m.
Scenario 1: Qtree-to-Qtree Migration
Now, we examine the qtree migration scenarios that we discussed earlier. The first scenario
is qtree-to-qtree migration, in which the source 7-Mode qtree structure is retained on the
destination clustered Data ONTAP system. No additional planning is required to determine
how the qtree should be reorganized on the destination clustered Data ONTAP system. This
example shows a SnapMirror relationship, but you can use any migration method to move
the data to the clustered Data ONTAP environment. You should use 7MTT as a replication-
based migration method, because it retains storage efficiency savings and Snapshot copies
at the destination clustered Data ONTAP system.
41 de 84 09/04/2018 12:59 p. m.
Scenario 2: Qtree-to-Volume Migration
The second scenario is one in which each source 7-Mode qtree is migrated to a single
clustered Data ONTAP volume. This approach works best for migrating tens to a couple of
hundred qtrees. The destination clustered Data ONTAP system can easily accommodate the
movement of several hundred qtrees to individual volumes. Leave space for expansion in
the destination cluster. Before you can migrate qtrees to clustered Data ONTAP volumes,
you must break the source 7-Mode qtrees into individual volumes while you are still in the
7-Mode environment. This approach is known as the qtree staging approach. While you
break qtrees into volumes, you need to use staging volumes. The staging volumes can be
on the same 7-Mode controller or on a different 7-Mode controller, wherever there is space
for the data during this breakout activity.
42 de 84 09/04/2018 12:59 p. m.
Scenario 3: Qtree Consolidation
In a qtree consolidation scenario, source 7-Mode qtrees with common dataset requirements
are grouped (or consolidated). Those source qtrees are then migrated to volumes in
clustered Data ONTAP. Common dataset requirements include replication and export
requirements. The same qtree staging approach that was depicted in the previous scenario
is required to move qtrees to clustered Data ONTAP.
43 de 84 09/04/2018 12:59 p. m.
Data Migration Methods
You can use these migration methods, which have been categorized by their benefits and
capabilities. The copy-based, or replication-based, migration method uses NetApp
SnapMirror technology. It is available with both 7MTT and TDP SnapMirror. The key benefit
of copy-based migration is that Snapshot copies and storage efficiency savings are retained
throughout the migration. The benefit holds except for the special cases of qtree-to-volume
and qtree-reorganization scenarios. Starting with 7MTT version 2.2, you can perform copy-
free transition. After completing all of the preparation steps, you manually disconnect the
disk shelves from the 7-Mode controllers and reconnected them to the controllers that run
clustered Data ONTAP. The application-based migration method uses the native application
replication, mirroring, or copying feature to migrate data to clustered Data ONTAP. Two key
examples of application-based migration methods are Oracle Automatic Storage
Management and Microsoft Exchange Database Availability Group. Virtualized environment
tools for the movement of data are also grouped into this category, for the purpose of
transition. The appliance-based migration method uses hardware to migrate data to
clustered Data ONTAP. For appliance-based migration, you can use Data Transport Appliance
2800. Host-based methods are a good option for qtree transitions, because no staging is
needed. You can use a NetApp host-based migration method called XCP for transitions
between NetApp systems and from third-party systems to NetApp systems. Host-based
methods are better suited for high-file-count environments, because they are much faster
than traditional copy tools. You can also use a third-party host-based tool such as Rsync,
NDMP Copy, or logical volume manager (LVM) to migrate data to clustered Data ONTAP. The
foreign LUN import feature can now be used to migrate SAN LUNs from 7-Mode to clustered
Data ONTAP.
44 de 84 09/04/2018 12:59 p. m.
45 de 84 09/04/2018 12:59 p. m.
Migration Tools Decision Tree
The migration tools decision tree helps you to decide which migration tool to use for each
storage container. As you review the decision tree, notice that you should usually use 7MTT.
However, 7MTT occasionally doesn’t do what you need it to do. For example, 7MTT only
works with 7-Mode source systems. So if you are transitioning from third-party FAS storage,
you need to use a different tool. A common practice is to use Storage vMotion in VMware to
nondisruptively move the data. Starting from the top, if you are transitioning a virtualized
workload, you need a virtual migration option, such as VMware, Hyper-V, or Citrix. If the
workload is application-based, you should use the tools for that application. Regarding
protocols, you must migrate third-party NAS workloads with tools like XCP, PeerSync, or
StorageX. For pure CIFS workloads you may choose to use Secure Copy to migrate the
data. For third-party SAN workloads, there is the DTA2800, Workflow Automation, or
Foreign LUN Import. NetApp SAN and NAS workloads can use the 7MTT tool. Some NAS
exceptions exist and those can use one of the other NAS migration methods mentioned
earlier. If you can use 7MTT, you can choose copy-based transition, copy-free transition, or a
combination of both types of transition.
46 de 84 09/04/2018 12:59 p. m.
Why Choose XCP?
XCP is a high-performance NFSv3 migration tool that performs fast and reliable migrations
from third-party storage to NetApp storage. You can also use XCP for NetApp to NetApp
transitions. The tool supports discovery, logging, and reporting, as well as a variety of
sources and targets. XCP performance is up to 25 times that of comparable tools. XCP offers
unique capabilities that accelerate and improve file-tree processing and data migration. XCP
can also operate at multiple levels of granularity. For example, XCP can work at the qtree or
subdirectory level or use criteria-based filtering. The tool is easy to deploy—it is 64-bit Linux
host-based software. Refer to the Quick Start Guide for the minimum system requirements.
The XCP 1.0 core commands are shown here. The xcp show command provides access to
the sources and targets, so that scoping and migration can proceed. Starting from any
directory, xcp scan recursively reads all of the directories and can produce listings and
reports in human-readable and machine-readable formats. The xcp copy command is easy
to use. It uses the NFSv3 feature set to ensure that the target exactly matches the source,
including hard links, symlinks, special file types, permissions, and other attributes. By
default, xcp verify does a full comparison of target files and directories (including attributes
and every byte of data). By default, the command also has options for fast verification,
selective verification, and incremental data verification after synchronization to minimize
cutover times. Use the resume option to restart an interrupted job. The job restarts from
the point where it stopped. After a baseline copy, xcp sync does a full scan of the source to
find all of the changes and then copies new data and performs all other operations to
update the target and make it exactly match the source again. The time to check for
changes depends on the source server’s performance capability. Although XCP is a free tool,
it requires a license to work. XCP logs and reports provide information about operations,
47 de 84 09/04/2018 12:59 p. m.
sources, targets, file count, data amount, and system performance.
48 de 84 09/04/2018 12:59 p. m.
XCP Licensing
XCP licenses are configurable to match customer needs and environment. Standard licenses
require the XCP host to be connected to the Internet so it can access the NetApp site for
activation and license control. There’s also the option to request offline licenses for closed
environments that can’t access the Internet. Standard licenses are instantly available, while
offline licenses go through an approval process. Refer to the NetApp web page at
xcp.netapp.com for information and download links.
49 de 84 09/04/2018 12:59 p. m.
Foreign LUN Import for Migration
The Data ONTAP 8.3 operating system introduced the foreign LUN import feature. This
array-based migration feature enables customers to migrate data between storage systems.
In some instances, foreign LUN import can now be used to transition 7-Mode LUNs to
clustered Data ONTAP. It is especially useful in cases that involve unaligned I/O or a 32-bit
to 64-bit aggregate upgrade, or both. For more information about foreign LUN import, see
TR-4380 SAN Migration Using Foreign LUN Import Methodology. Section 8 is specific to
7-Mode to cluster transitions.
50 de 84 09/04/2018 12:59 p. m.
7-Mode Transition Tool
NetApp developed the 7-Mode Transition Tool as the premier tool for transitioning 7-Mode
storage systems to clustered Data ONTAP. 7MTT simplifies the data migration process for
both SAN and NAS environments. 7MTT can preserve Snapshot copies, deduplication and
compression savings, system configurations, and SnapMirror relationships. For SAN
transitions, LUN maps are now also supported through the break and resynchronization
process.
51 de 84 09/04/2018 12:59 p. m.
New 7MTT Features and Functionality
7MTT has many enhancements that facilitate a smooth transition from Data ONTAP
operating in 7-Mode to clustered Data ONTAP. The tool can now transition workloads to
clustered Data ONTAP 8.3 versions, using a copy-based method, a copy-free method, or a
combination of both. The supported source and destination versions of Data ONTAP are
available in the IMT. Improvements to SAN transitions include pre-cutover testing,
staggered primary and secondary disaster-recovery relationships, additional information
about host-side LUN changes, and automated collection of zoning information from
switches. The 7MTT GUI now supports 60 active projects. The tool also has more CIFS
protocol precheck messages. And the tool now provides login capability for users who are
not members of the Administrator group.
52 de 84 09/04/2018 12:59 p. m.
Cluster Design
Cluster design differs, depending on whether a production cluster system exists or a new
clustered system will be installed. In either case, cluster design should consider
configuration elements for the destination cluster and a 7-Mode workload characterization
and utilization assessment. Transition planning should yield a list of 7-Mode storage
containers that are moving and how the containers map into the destination cluster. The
mapping dictates which configuration elements must be created on the cluster. The mapping
must specify the destination storage virtual machine (SVM) and aggregates that the storage
container will move to. For subvolume storage containers, further granularity is required,
such as the creation of directories and qtrees. To properly size the destination cluster, you
must complete a workload characterization and utilization assessment of the source 7-Mode
storage system. You must consider many workload metrics, such as throughput, latency,
operation size, randomness, concurrency, and caching. Utilization assessment is the task of
determining CPU and disk utilization for a controller or node. For detailed information about
these activities, see the Workload Characterization and Utilization Assessment sections of
technical report 4052: “Successfully Transitioning to Clustered Data ONTAP.”
53 de 84 09/04/2018 12:59 p. m.
Cluster Design Considerations
The workload characterization and utilization assessment for the 7-Mode storage system is
used to either size a new cluster or determine if sufficient free space exists in an existing
cluster. The same methods that are referenced for the utilization assessment and workload
characterization of the 7-Mode storage system can also be applied to a clustered Data
ONTAP system, with some slight modifications. If the transition activity is targeted at an
existing cluster, key design, architecture, and best practice decisions have probably already
been made. However, if a new cluster is being deployed, the decisions made now will
determine the operational health of the cluster not only during transition, but also after
transition. Even if you are transitioning to an existing cluster, review the existing design and
architecture to understand how the transitioned 7-Mode workloads and data will align with
the existing cluster configuration. Key considerations for a new cluster are disaster-recovery
and backup relationships, cluster maximums, and physical location. Other key areas to
investigate are how workloads and data from the 7-Mode system will be deployed in SVMs
and what type of namespace they will have. For more information about how to design a
cluster, refer to the Cluster Design Considerations and the Product Feature Considerations
sections of technical report 4052: “Successfully Transitioning to Clustered Data ONTAP.”
54 de 84 09/04/2018 12:59 p. m.
Module Summary
This module focused on enabling you to describe the components of transition planning, use
planning tools, and identify the key factors that affect a transition. The module also focused
on enabling you to design a clustered Data ONTAP system that supports current 7-Mode
workloads and expected future business requirements.
55 de 84 09/04/2018 12:59 p. m.
Module 4 Transition Phase: Implement
In module 4, you learn about the third and final phase of transition: implementation. In the
implementation phase, you deploy transition tools, migrate data, and update the
environment.
56 de 84 09/04/2018 12:59 p. m.
Module Objectives
This module focuses on enabling you to deploy transition tools and migrate data, describe
key cutover tasks, and minimize downtime during cutover.
57 de 84 09/04/2018 12:59 p. m.
Implementation Activities
The implementation phase of transition fundamentals includes activities in which you

execute your plans. Implementation activities include deploying a new cluster or configuring
an existing cluster to be the target of the planned data migrations. Implementation
activities include the acquisition and deployment of transition tools and movement of data
and workloads to clustered Data ONTAP. Finally, implementation activities include updating
of the environment as necessary to complete the transition.
58 de 84 09/04/2018 12:59 p. m.
Deployment of a New Cluster
One of the main objectives of the implementation phase is to deploy and configure the
cluster. This process includes verifying the cluster configuration and off-box dependencies.
Several activities occur when you deploy a new cluster. First, you procure, qualify, stage,
and install hardware. Next, you configure clustered Data ONTAP protocols, services, and
features. Finally, you create and configure storage virtual machines, aggregates, volumes,
and any other storage objects that are needed to support movement of the 7-Mode storage
containers to clustered Data ONTAP. If you will use the copy-free transition feature of 7MTT,
you must allocate one HA pair for that purpose, and only configure an SVM. This type of
transition has to be to a cluster HA pair that is not serving other data at the time of
transition.
59 de 84 09/04/2018 12:59 p. m.
Configuration of an Existing Cluster
If you are transitioning data to an existing cluster, you perform slightly different activities
than when you transition to a new cluster. [1]The introduction of new hardware may not be
necessary, unless the performance assessment indicated that you must nondisruptively
expand the existing cluster capabilities, or if staging of hardware is required for qtree
breakout. [2]Primary configurations of clustered Data ONTAP protocols, services, and
features are now done. However, new workloads may have new requirements that require
you to update protocols and services. [3] If you use copy-free transition, you must add an
HA pair to an existing cluster or remove all workloads from one HA pair in the cluster.
60 de 84 09/04/2018 12:59 p. m.
Data Migration
During the data migration part of the implementation phase, you move data from one
storage system to another storage system. Depending on the migration method that you
use, the migration might be disruptive or nondisruptive. Transition planning activities
provide a migration method for each storage container that is being moved to clustered
Data ONTAP. Transition planning activities also provide the cutover considerations and
timing that are associated with the method that you use. Your implementation goal is to
migrate data and perform cutover as planned and to verify data access and configuration
after migration is complete.
61 de 84 09/04/2018 12:59 p. m.
Copy-Based Migration and Cutover
Some application-based migration methods offer nondisruptive data migration capabilities.

These application-based methods are beyond the scope of this training. More details and
available options in this category are described in Technical Report 4336: “Enterprise
Application Transition to Clustered Data ONTAP.” Replication-based, appliance-based, and
host-based methods are usually disruptive. The diagram shows the standard steps that are
involved in most disruptive data migrations. Customer service continuity determines the
importance of cutover; the customer in this case relies on the availability of the storage or
applications. If service continuity is disrupted, cutover activities and cutover window
become critical. This is not present with nondisruptive cutover.
62 de 84 09/04/2018 12:59 p. m.
Cutover Timing Considerations
Most cutover activity is disruptive in some way. The following key tasks contribute to the
timing of the cutover window: You must disconnect clients and shut down application
services, so that no additional writes occur on the source storage container. As a result of
data migration, shares or mounts might need to change. Verify that no remaining activity
exists on the source system: that no CIFS sessions, NFS mounts, or LUNs are actively being
accessed. 7MTT does not do this verification for you, so if you do not perform this
verification, data inconsistency is possible. Perform a final incremental data transfer that
synchronizes the destination file system with the source file system. The timing of this step
depends heavily on the change rate in the source file system. If you use 7-Mode Transition
Tool (or 7MTT) incremental transfers, you can reduce the size of this final transfer, which
reduces the cutover outage time. Remember that from 7MTT, you can configure how often
incremental transfers occur. Most configurations should already be applied to the destination
cluster. However, certain configuration elements need to be set during the cutover. For
example, if a storage IP address is being moved, this action must occur after the final
update and before clients are reconnected. Finally, reconnect the clients and restart the
application services. The timing of these tasks is tied to the number of clients in the system
and the tools and processes that you use to reconnect the clients. The timing also depends
on the applications services themselves and how quickly they can resume service.
63 de 84 09/04/2018 12:59 p. m.
7MTT consists of both the Collect and Assess feature (which was discussed in the module
about the identification phase) and a fully featured data migration capability. 7MTT supports
migration of data from 7-Mode storage systems to clustered Data ONTAP 8.2 and 8.3. 7MTT
also supports the migration of 7-Mode volume SnapMirror relationships to clustered Data
ONTAP. Recently the capability to do a copy-free transition has also been added. 7MTT
supports the migration of SAN workloads from the 7-Mode storage system to clustered Data
ONTAP 8.3. Newer versions of 7MTT also support the copy-based migration of 7-Mode
MetroCluster storage systems to clustered Data ONTAP 8.3.
64 de 84 09/04/2018 12:59 p. m.
Some of the key benefits of using 7MTT are as follows: 7MTT conducts a comprehensive
precheck process to determine that the source 7-Mode storage system and volumes are
ready for the data migration activity. 7MTT supports the migration of both CIFS and NFS
volumes. Most data migration tools support CIFS or NFS, but not both. 7MTT supports the
migration of SAN volumes and key SAN configuration items, including host, LUN, HBA, and
HBA port details. In addition, storage efficiency configurations such as Snapshot copies,
deduplication, and compression are migrated to clustered Data ONTAP. 7MTT migrates key
7-Mode storage system configurations automatically. 7MTT migrates 7-Mode volume
SnapMirror relationships to clustered Data ONTAP. Another key benefit of 7MTT is that it
enhances the coordination of the cutover phase. 7MTT enhances coordination by automating
the cutover of storage while signaling the proper timing for the disconnection and
reconnection of clients. Finally, 7MTT guides the user through the end-to-end data migration
process. The default UI for 7MTT is a web interface (or GUI). A CLI is also available. The CLI
enables you to write scripts for controlling 7MTT.
65 de 84 09/04/2018 12:59 p. m.
Copy-Based or Copy-Free Transition?
When you use 7MTT for a transition, you can choose copy-based transition or copy-free
transition. The differences between the two methods are listed here. If you require granular
movement and SnapMirror replication, use copy-based transition. Copy-based transition also
enables you to perform cutover by volumes. However, if the shelves are compatible, you do
not need to reorganize the data, and you do not require granular movement, use copy-free
transition. For copy-free transition, everything is moved simultaneously and cutover is done
by HA pair. Both solutions preserve all data protection and storage efficiency rules
throughout.
66 de 84 09/04/2018 12:59 p. m.
If you use the 7MTT copy-free transition option, you can obtain benefits such as the ability
to reuse existing storage shelves. You also do not need to copy data and configuration
information over a network. SnapMirror relationships are transitioned. The relationships only
require a resynchronization, not a rebaseline. Copy-free transition enables a large amount
of data to be moved during a single maintenance window.
67 de 84 09/04/2018 12:59 p. m.
Before you choose the 7MTT copy-free transition feature, consider the hardware
requirements of the feature. No entry-level 7-Mode system can be the source. The only
FAS3000 system that is supported is the FAS3070. FAS3100 and FAS3200 systems are
supported, as well as high-end FAS6000 and FAS6200 systems. FAS8000 systems as a
7-Mode source for copy-free transition, require Data ONTAP 8.3.2 GA or later on the
destination cluster. Initially the only destination cluster systems that are supported are
FAS8000 series systems. Because copy-free transition requires that the disk shelves to be
moved to the cluster, only the shelves and shelf modules listed here are supported.
68 de 84 09/04/2018 12:59 p. m.
Aside from platform support, you must also consider other aspects of copy-free transition
before using it as a transition method. Each 7-Mode HA pair must be transitioned to a
clustered Data ONTAP HA pair. You cannot consolidate data from several 7-Mode HA pairs to
one HA pair that runs clustered Data ONTAP. The relationship must be 1:1. Each 7-Mode
node or vFiler unit migrates to a separate SVM in the cluster. Copy-free transition also does
not reorganize any volume data. Copy-free transition occurs as one large cutover event;
copy-based transition can occur as multiple smaller cutovers. Some 7-Mode features are not
supported for copy-free transition. Features that are not supported include traditional
volumes, MetroCluster software, SnapLock software, and 32-bit aggregates and volumes.
69 de 84 09/04/2018 12:59 p. m.
Copy-Free Migration and Cutover
NetApp 7MTT copy-free migration steps are as outlined in the diagram. 7MTT automates
many steps, but you must still perform some steps manually, both before and during the
cutover window. After the clients have been reconnected, there is a rollback window. But if
you perform rollback, new data that was written is lost. If no rollback is needed, the project
is committed, and the migration is considered complete.
70 de 84 09/04/2018 12:59 p. m.
Copy-Based Transition
For copy-based transitions, 7MTT automates most migration activities while minimizing the
outage window. The 7MTT data-migration process consists of four main phases: preparation,
baseline data copying, pre-cutover, and cutover. In the preparation phase, prechecks are
run against the source 7-Mode storage systems. Precheck processes include confirming that
the volumes and configurations are ready for migration to clustered Data ONTAP. The
destination cluster is also verified ton confirm that it is configured to properly support the
data migration activity. Examples of verification activities are: verifying that volumes are
online and verifying that there is network access between the source and destination
systems. In the baseline data copying phase, new volumes are created and a SnapMirror
baseline transfer is executed between the 7-Mode source volumes and the clustered Data
ONTAP destination volumes. After the baseline transfer is complete, incremental transfers
are initiated at regular intervals. A user can configure the timing of these intervals. In the
pre-cutover phase, configuration information is applied to the clustered Data ONTAP system,
storage virtual machines, and volumes. During this phase, incremental transfers continue.
Also, an option is available for testing the clustered Data ONTAP volumes that are being
transitioned before storage cutover. In the final phase, cutover, clients are manually
disconnected and a final incremental transfer is completed. The SnapMirror relationship
between the 7-Mode storage system and the clustered Data ONTAP system, which was
being used for data migration, is broken. Clients can then be manually reconnected to the
clustered Data ONTAP system. Finally, you should verify client access on the clustered Data
ONTAP system.
71 de 84 09/04/2018 12:59 p. m.
Combined Copy-Free and Copy-Based Transition
For some transition situations, you might need to use both copy-based transition and copy-
free transition to accomplish the full migration. For example, if some of your volumes have
strict cutover requirements, copy-based transition is a better option. But after those
volumes are migrated, you can use copy-free transition to migrate the remaining data. The
volumes that you use copy-based transition to migrate must target a different HA pair in the
cluster than the pair that is the target for copy-free transition. SnapMirror primary and
secondary relationships during migration are not the same for copy-based transition and
copy-free transition. When you use copy-based transition, a relationship exists between the
7-Mode primary and the clustered Data ONTAP secondary during the migration. If you use
copy-free transition, there is no relationship.
72 de 84 09/04/2018 12:59 p. m.
Other NetApp Tools and Features
A few more tools and Data ONTAP features are useful during a transition. You can download
and run the SAN host remediation tool (the SAN HRT) on a Windows system. The tool
provides automated procedures for planning remediation and remediating hosts as part of
the 7MTT workflow. The LUN identifiers change during 7MTT transition of a LUN from Data
ONTAP 7-Mode to clustered Data ONTAP. The changes to the LUN identifiers break the host
storage stack after transition. The break in the stack results in a service outage. SAN HRT
provides an automated method of remediating the hosts in advance, which enables you to
avoid additional downtime. The foreign LUN import feature of clustered Data ONTAP can be
used as a migration tool when 7MTT is not appropriate. For example, if LUNs are hosted on
a 32-bit aggregate or if LUNs have unaligned I/O, use the foreign LUN import feature. In a
transition scenario, the “foreign LUNs” are those on the 7-Mode system that are being
exported to the clustered Data ONTAP system. Starting with Config Advisor 4.4, the Config
Advisor tool includes a transition profile. Select the Transition profile, complete the fields
that identify all of the cluster components, and run the tool to verify the cabling.
73 de 84 09/04/2018 12:59 p. m.
Module Summary
This module focused on enabling you to deploy transition tools and migrate data, describe
key cutover tasks, and minimize downtime during cutover.
74 de 84 09/04/2018 12:59 p. m.
Knowledge Check
Knowledge Check
75 de 84 09/04/2018 12:59 p. m.
Knowledge Check
76 de 84 09/04/2018 12:59 p. m.
Knowledge Check
77 de 84 09/04/2018 12:59 p. m.
Knowledge Check
78 de 84 09/04/2018 12:59 p. m.
Knowledge Check
79 de 84 09/04/2018 12:59 p. m.
Knowledge Check
80 de 84 09/04/2018 12:59 p. m.
Knowledge Check
81 de 84 09/04/2018 12:59 p. m.
Resources
This list provides additional resources that are related to transition fundamentals.
82 de 84 09/04/2018 12:59 p. m.
Resources
83 de 84 09/04/2018 12:59 p. m.
Course Summary
This course focused on enabling you to transition from Data ONTAP operating in 7-Mode to
clustered Data ONTAP, identify the technical considerations for migrating data to a clustered
Data ONTAP system, and analyze workload and environmental requirements and determine
which tools to use for migration. Thank you.
84 de 84 09/04/2018 12:59 p. m.

NetApp Transition Fundamentals

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

NetApp Transition Fundamentals

Uploaded by

Copyright:

Available Formats

Print Slides https://www.brainshark.com/brainshark/viewer/PrintSlides.aspx?pi=854688475&sid=3158639...

NetApp Transition Fundamentals

Welcome to NetApp Transition Fundamentals. As storage administrators demand ever more

Module 1 Transition Terms and Phases

Definitions of Transition Terms

Definitions of Transition Terms

“Operationalization” refers to the transfer and modification of storage-system dependencies.

The Journey to Clustered Data ONTAP

The transition-fundamentals framework focuses on the knowledge that you need to

Three Phases of Transition

Three Phases of Transition: Identify

Three Phases of Transition: Design

Three Phases of Transition: Implement

Transition Fundamentals: Not a Process

The transition-fundamentals framework is not a process. The framework logically organizes

NetApp Premier Transition Tool: 7MTT

Module 2 Transition Phase: Identify

Environment Discovery with 7MTT

Module 3 Transition Phase: Design

Scenario 1: Copy-Based Basic Disaster Recovery

Scenario 2: Bidirectional Disaster Recovery

Scenario 4: Copy-Free Basic Disaster Recovery

Scenario 1: Qtree-to-Qtree Migration

Scenario 2: Qtree-to-Volume Migration

Scenario 3: Qtree Consolidation

Data Migration Methods

Migration Tools Decision Tree

Why Choose XCP?

sources, targets, file count, data amount, and system performance.

Foreign LUN Import for Migration

7-Mode Transition Tool

New 7MTT Features and Functionality

Cluster Design Considerations

Module 4 Transition Phase: Implement

The implementation phase of transition fundamentals includes activities in which you

Deployment of a New Cluster

Configuration of an Existing Cluster

Copy-Based Migration and Cutover

Some application-based migration methods offer nondisruptive data migration capabilities.

Cutover Timing Considerations

7-Mode Transition Tool

7-Mode Transition Tool

Copy-Based or Copy-Free Transition?

Copy-Free Migration and Cutover

Combined Copy-Free and Copy-Based Transition

Other NetApp Tools and Features

You might also like