7-Mode Transition Tool 3.0 Copy-Free Transition

7-Mode Transition Tool 3.0
Copy-Free Transition Guide
For Transitioning to ONTAP®
September 2016 | 215-11373_B0
doccomments@netapp.com
Table of Contents | 3
Contents
Transition overview ...................................................................................... 6
Copy-free transition by using 7-Mode Transition Tool ............................................... 6
Transition terminology ................................................................................................ 8
Collecting and assessing the inventory information .................................. 9
Storage, host, and FC switches version requirements for transition assessment ...... 10
Preparing the 7-Mode systems and hosts for transition assessment .......................... 10
Assessing controllers and hosts ................................................................................. 11
Generating an assessment report by adding systems to the 7-Mode
Transition Tool ......................................................................................... 12
Generating an assessment report by importing the inventory report XML ... 14
Generating an FC zone plan ...................................................................................... 15
Supported configurations for generating an FC zone plan ............................ 16
How you can use the assessment executive summary for transition assessment ...... 17
Copy-free transition workflow .................................................................. 19
Phases of copy-free transition ................................................................................... 19
Preparing for copy-free transition ............................................................ 23
Requirements for copy-free transition ....................................................................... 23
Tools and documentation required for copy-free transition ...................................... 25
Port requirements for communicating with the 7-Mode Transition Tool .................. 25
Preparing the 7-Mode HA pair for transition ............................................................ 26
Setting up the SP or RLM on the 7-Mode systems for copy-free transition ............. 27
Preparing the network for transition .......................................................................... 29
Considerations for transitioning 7-Mode IP addresses ................................. 30
Preparing the cluster for transition ............................................................................ 30
Gathering cabling information for transition ............................................................ 31
Copy-free transition cabling worksheet ........................................................ 33
Preparing 7-Mode aggregates and volumes for transition ......................................... 34
Restrictions for transitioning 7-Mode aggregates and volumes .................... 35
Preparing for transitioning 7-Mode systems with 32-bit aggregates ............ 36
Aggregate space requirements for transition ................................................. 38
Preparing to transition name services ........................................................................ 40
Name services transition: supported and unsupported configurations,
and required manual steps ....................................................................... 40
Considerations for transitioning DNS, NIS, and LDAP configurations ....... 41
Considerations for transitioning netgroups and UNIX users and groups ...... 42
Preparing for NFS transition ..................................................................................... 42
Prerequisites for transitioning NFS configurations ....................................... 43
NFS transition: supported and unsupported configurations, and required
manual steps ............................................................................................ 43
How NFS exports are transitioned ................................................................ 45
Preparing for CIFS transition .................................................................................... 48
4 | Copy-Free Transition Guide
Prerequisites for transitioning CIFS configurations ...................................... 48
CIFS transition: supported and unsupported configurations, and required
manual steps ............................................................................................ 50
Considerations for transitioning CIFS local users and groups ...................... 52
Preparing for SAN transition ..................................................................................... 52
Creating SAN LIFs before transition ............................................................ 52
Configuring zones by using the FC zone plan .............................................. 53
Preparing SAN hosts for transition ............................................................... 54
SAN transition: supported and unsupported configurations, and required
manual steps ............................................................................................ 54
Space considerations when transitioning SAN volumes ............................... 55
Preparing data protection features for transition ....................................................... 56
Preparing the cluster for transitioning volume SnapMirror relationships ..... 56
Data protection transition: supported and unsupported configurations ......... 56
Transitioning 7-Mode aggregates using copy-free transition ................. 58
Planning a copy-free transition project ..................................................................... 59
Copy-free transition project planning worksheets ......................................... 60
Adding controllers and clusters ..................................................................... 63
Creating a copy-free transition project .......................................................... 63
Selecting the target cluster nodes for transition ............................................ 64
Mapping SVMs and volumes ........................................................................ 64
Selecting LIFs for transition .......................................................................... 66
Customizing the transition of 7-Mode configurations .................................. 66
Running prechecks ........................................................................................ 71
Applying SVM configurations .................................................................................. 73
Verifying that 7-Mode systems are ready for cutover ............................................... 74
Exporting storage configurations and halting 7-Mode systems ................................ 75
Disconnecting disk shelves from the 7-Mode system and connecting to cluster
nodes .................................................................................................................... 76
Importing 7-Mode data to ONTAP ........................................................................... 78
Completing the transition .......................................................................... 80
Restrictions during preproduction testing ................................................................. 80
Rehosting transitioned volumes to a different SVM ................................................. 82
Verifying the transitioned configurations .................................................................. 85
Performing manual configuration tasks after transition ............................................ 85
Testing the workloads and applications ..................................................................... 86
Committing the copy-free transition project ............................................................. 87
Transitioning a SnapMirror relationship ................................................. 88
Transitioning HA pairs in a SnapMirror relationship in a staggered
configuration ........................................................................................................ 88
Transitioning primary and secondary systems in a SnapMirror relationship in
parallel ................................................................................................................. 90
Troubleshooting transition issues .............................................................. 92
Continuing with the transition if ignorable errors occur ........................................... 92
Ignorable error categories .............................................................................. 92
Table of Contents | 5
Downloading transition log files ............................................................................... 95
Log files for the 7-Mode Transition Tool .................................................................. 96
Recovering from a failed LUN transition .................................................................. 97
Failed to boot the 7-Mode controller in maintenance mode ..................................... 98
Performing a transition rollback to 7-Mode ............................................ 99
When to roll back a transition and when to call technical support ........................... 99
Rolling back a copy-free transition project ............................................................... 99
Manually rolling back the transition ........................................................... 101
Copyright information ............................................................................. 103
Trademark information ........................................................................... 104
How to send comments about documentation and receive update
notifications .......................................................................................... 105
Index ........................................................................................................... 106
6
Transition overview
Transitioning to clustered Data ONTAP involves identifying your current environment, defining the
transition scope, designing the optimal configuration of the destination systems, planning how to
migrate data and configurations, as well as making necessary environmental updates.
You must first collect information about the current environment, including both the current storage
environment as well as the hosts and applications. After collecting the storage inventory, you can
assess the current features and functionality that are used and identify any differences in the clustered
Data ONTAP version selected. You can use 7-Mode Transition Tool to perform these tasks.
You can then define your migration project. This involves identifying what volumes and workloads
you want to migrate together, then you can design your cluster, and plan your transition. You can
begin planning your migration by first selecting the optimal migration method. When designing your
cluster, you can use the information gathered about your storage environment to map existing
configuration items to their equivalent items in clustered Data ONTAP. For example, a 7-Mode
volume should be mapped to a Storage Virtual Machine (SVM) and a volume in clustered Data
ONTAP and an IP address that will be transitioned should be mapped to LIFs. You should also
determine if any environmental changes have to be made on the clustered Data ONTAP system.
Implementation includes deploying and configuring the cluster, migrating data, applying
configuration changes, disconnecting clients and reconnecting to the destination clustered Data
ONTAP system, verifying access, as well as performing any necessary environmental changes.
Related information
NetApp Documentation: ONTAP 9
NetApp Technical Report 3982: NetApp Clustered Data ONTAP 8.2 Introduction
Copy-free transition by using 7-Mode Transition Tool
The 7-Mode Transition Tool enables you to collect inventory and to assess 7-Mode controllers, hosts,
switches, and applications for transition. After assessment, you can use a copy-free transition to
migrate your data and configurations to clustered Data ONTAP. In copy-free transition, you
disconnect all the disk shelves from a 7-Mode HA pair and connect them to an HA pair in the target
cluster.
Copy-free transition significantly reduces the migration cost by enabling the reuse of 7-Mode disk
shelves. The overall duration for performing the transition is faster because data copy is not required.
The unit of a copy-free transition is an HA pair. You must move all the disk shelves from the 7-Mode
HA pair to the target cluster nodes.
The metadata of the 7-Mode aggregates and volumes is converted to the clustered Data ONTAP
format by the 7-Mode Transition Tool. The time taken for this conversion does not depend on the size
of the aggregates and volumes. For example, the time taken to convert a 10 GB aggregate to the
clustered Data ONTAP format is the same as the time required to convert a 100 TB aggregate.
Copy-free transition involves a disruption to data access. However, the total time taken to perform the
data migration is faster because no data copy is required.
The following illustration shows the before and after scenarios for copy-free transition from a 7Mode HA pair to a two-node cluster:
Transition overview | 7
The 7-Mode Transition Tool runs on a Windows system and provides web interface for managing
transition operations.
Collecting and assessing Data ONTAP systems, hosts, switches, and applications
You can perform the following collect and assess tasks by using the 7-Mode Transition Tool:
•
Collecting inventory information from Data ONTAP systems (7-Mode controllers and nodes in
the cluster), hosts, switches, and host applications.
•
Generating the FC Zone plan to configure the zones for SAN FC transition.
•
Assessing the features and functionalities of the 7-Mode systems, and identify how these features
and functionalities work in the clustered Data ONTAP version selected for the transition.
Moving data and configurations from 7-Mode to Clustered Data ONTAP
Copy-free transition reuses the 7-Mode disk shelves to copy 7-Mode data from 7-Mode to clustered
Data ONTAP. You can perform the following tasks by using the 7-Mode Transition Tool for copyfree migration:
•
Planning your transition to map the 7-Mode controllers or vFiler units to the target SVMs, and
design the namespace.
•
Running prechecks to verify the compatibility of the 7-Mode systems and target cluster nodes for
transition.
•
Importing 7-Mode disk shelves in the following ways:
◦
From a 7-Mode HA pair to a new HA pair in a new cluster
◦
From a 7-Mode HA pair to a new HA pair in an existing cluster that has additional dataserving nodes
◦
From a 7-Mode HA pair to an HA pair that has data aggregates in an existing cluster that is
serving data
8 | Copy-Free Transition Guide
◦
From an HA pair that contains volumes in a volume SnapMirror relationship to an HA pair in
a new or existing cluster
You must manually create the cluster peer relationship after transition; however, a rebaseline
transfer is not required, and you can retain the SnapMirror relationship after transition.
•
Transitioning 7-Mode configurations to SVMs.
Copy-free transition supports the transition of NAS and SAN configurations.
•
Rolling back storage and configurations to 7-Mode if transition to clustered Data ONTAP fails.
The tool generates the list of steps that are required to roll back to 7-Mode. You must manually
perform these rollback steps on the 7-Mode systems and the cluster.
Transition terminology
Understanding the transition terminology related to the 7-Mode Transition Tool helps you to
understand the transition process.
Collect and assess
Before transitioning data and configurations to clustered Data ONTAP, you must collect
information about the storage environment that includes storage systems, hosts, and
applications. You must then assess the features and functionalities of these systems, and
identify how these features and functionalities work in the clustered Data ONTAP version
selected for transition.
Migrate
Refers to transitioning data and configurations from the 7-Mode volumes to clustered Data
ONTAP. Migration should be performed after assessing the 7-Mode controllers.
Project
In the 7-Mode Transition Tool, a project enables you to configure and manage the
transition of a group of volumes.
Project group
In the 7-Mode Transition Tool, a project group is a logical container that you can use to
hold related migration projects. There is always one default group with Default_Group
name that exists in the system.
9
Collecting and assessing the inventory
information
You can collect inventory information from controllers, hosts, and FC switches; assess features and
functionalities of these systems; and identify how these features and functionalities work in the
clustered Data ONTAP version that is selected for transition.
Depending on whether you can install 7-Mode Transition Tool in your environment due to security
reasons, you can either use 7-Mode Transition Tool to collect the inventory information or import the
inventory XML report generated by Inventory Collect Tool and then perform the assessment.
Note: You must use Inventory Collect Tool 3.0 to collect the inventory.
To assess for a copy-free transition, you must select both of the nodes of the source 7-Mode HA pair.
Although the assessment is done on a per-node basis, if a single node is not qualified for transition,
the entire HA pair cannot be transitioned.
10 | Copy-Free Transition Guide
Storage, host, and FC switches version requirements for
transition assessment
You must be aware of the versions of Data ONTAP operating in 7-Mode, hosts, and FC switches that
are supported for transition assessment.
For the list of 7-Mode versions, hosts, and FC switches that are supported for assessment by the 7Mode Transition Tool, see the NetApp Interoperability Matrix Tool.
NetApp Interoperability Matrix Tool
Preparing the 7-Mode systems and hosts for transition
assessment
You must ensure that the 7-Mode systems and hosts meet certain network and protocol requirements
for successfully generating an assessment report.
Steps
1. Enable HTTPS on the 7-Mode system:
options httpd.admin.ssl.enable on
2. Enable TLS on the 7-Mode system:
options tls.enable on
Important: The best practice is to enable TLS because of the security vulnerabilities in SSLv3.
3. Enable SSL and disable SSLv2 and SSLv3 on the 7-Mode system:
a. Set up and start SSL:
secureadmin setup ssl
b. Enable SSL:
options ssl.enable on
c. Disable SSLv2 and SSLv3:
options ssl.v2.enable off
options ssl.v3.enable off
Important: The best practice is to disable SSLv2 and SSLv3 to avoid security
vulnerabilities.
4. Enable SSH on the 7-Mode system:
a. Set up SSH on the 7-Mode system:
secureadmin setup -f ssh
The -f option forces the setup to run even if the SSH server is already configured.
b. Enable SSH:
secureadmin enable ssh2
c. Enable password authentication on the SSH server:
Collecting and assessing the inventory information | 11
options ssh.passwd_auth.enable
d. Enable SSH access to the host:
options ssh.access
5. Prepare your Windows host systems:
•
Enable WMI access.
For more information about enabling WMI access, see the host documentation.
•
If you have Windows Server 2003, verify that you have installed the Microsoft Fibre Channel
Information Tool (fcinfo) package and run the tool once on your Windows host system.
This tool enables you to collect the HBA configuration information of the host.
•
If the system on which the 7-Mode Transition Tool is run does not belong to a domain, verify
the following:
◦
The host system belongs to a domain.
◦
If the host has a local user, and the user name for that user is in the following format:
SystemName\Username
6. Enable SSH on the Linux or ESXi host.
For more information about enabling SSH, see the host documentation.
7. Verify that you have installed the latest NetApp Host Utilities software for each host.
For information about downloading and installing the NetApp Host Utilities software, see the
NetApp Support Site.
8. Verify that all the hosts and storage systems can be reached by the Windows system from which
the 7-Mode Transition Tool is run.
Related information
Documentation on the NetApp Support Site: mysupport.netapp.com
Assessing controllers and hosts
You can collect and assess information about the controllers and hosts by using either the 7-Mode
Transition Tool or the Inventory Collect Tool, depending on the security regulations in your
environment.
About this task
•
The 7-Mode Transition Tool collects inventory information about controller and hosts by adding
the systems or by using the inventory report generated by the Inventory Collect Tool.
The 7-Mode Transition Tool then assesses inventory information and creates the transition
assessment report.
•
You must be aware of the following considerations when performing transition assessment:
◦
You should not perform both assessment and migration operations simultaneously on a
controller.
◦
You should avoid performing assessment operations on active storage controllers during peak
hours.
12 | Copy-Free Transition Guide
Choices
• Generating an assessment report by adding systems to the 7-Mode Transition Tool on page 12
• Generating an assessment report by importing the inventory report XML on page 14
Generating an assessment report by adding systems to the 7-Mode
Transition Tool
You can collect inventory information for controllers, hosts, and FC switches by adding the systems
to the 7-Mode Transition Tool. You can then create an assessment report to assess the features and
functionalities of those systems, and to identify how they work in the clustered Data ONTAP version
selected for transition.
Before you begin
•
The user name for the storage system and hosts must have sufficient privileges to execute the
commands listed in the readme file.
The readme file is located at 7-Mode Transition Tool_installed_location\bin\ict.
•
You must have prepared the 7-Mode systems, hosts, and FC switches for transition assessment.
•
For assessing Windows systems, you must have a domain user account.
•
If you are adding multiple systems for assessment, you must create a text file that is encoded in
the ASCII or UTF-8 format and must contain the system details in the form of one system per
line.
Each system details must be in the following format:
(ontap|windows|vmware|linux|cisco|brocade)://[(user|domain_user)
[:password]@](host_name|ip)
•
The controller or host must be accessible by the system on which the 7-Mode Transition Tool is
installed and run.
•
All features must be configured or their license enabled so that the workbook can contain
inventory information about these features.
•
The user name for the storage system must have sufficient administrative privileges to collect
inventory information.
•
All host names and storage system configurations, such as CIFS share names, user names, and
group names, must be in the UTF-8 format.
About this task
If the 7-Mode Transition Tool service or the system on which this tool is installed is restarted, then
the system details added to the tool are lost and the system must be added to the tool again.
Steps
1. If you want to use the latest Interoperability Matrix (IMT) data for transition assessment, perform
the following steps:
a. Download the IMT data from the Interoperability Matrix and save it:
i. From the Reports menu, click Complete Daily Exports.
ii. In the Complete Daily Exports dialog box, enter FAS in the search field.
iii. Download the FAS SAN Host excel file and save it.
Collecting and assessing the inventory information | 13
IMT database
b. From the CLI, import the IMT data by using the transition imt import command.
c. Verify that the import is successful by using the transition imt show command.
Troubleshooting: If the IMT data import operation fails due to some reason, you can revert
to the previous data by using the transition imt restore command.
2. Log in to the 7-Mode Transition Tool, and then click Collect & Assess in the home page.
3. Click Add Systems.
4. In the Add System window, perform one of the following actions:
•
Add a single system:
a. Enter the fully qualified domain name (FQDN) or IP address of the system.
b. Enter the user name and password for the specified system.
c. Select the system type:
•
◦
Data ONTAP storage systems
◦
Hosts: Microsoft Windows, Red Hat Linux Enterprise, and VMware ESXi
◦
FC switches: Cisco and Brocade
Add multiple systems by clicking Browse, and then selecting the text file that contains the
credentials for multiple systems.
5. Click Add.
If the assessment status of a system is Ready, then you can perform transition assessment for that
system.
6. Generate the transition assessment report by performing the following steps:
a. Select the systems for transition assessment.
b. Click Create Transition Assessment Report.
c. In the Create Transition Assessment Report dialog box, select the Data ONTAP version of
the target cluster.
d. Specify a prefix for the file name of the reports.
e. Click Generate Report.
The assessment workbook (report name appended with “AssessmentWorkbook”) and assessment
executive summary (report name appended with “AssessmentExecutiveSummary”) reports are
generated in XML format.
You can access the assessment workbook, assessment summary, and the inventory XML files that
are used to generate the assessment report from the ...etc/webapp/transition-gui/tmc
folder.
7. View the assessment workbook in Microsoft Excel and assessment executive summary in
Microsoft Word by using Microsoft Office 2007 or later versions.
In the assessment workbook, see the Transition Feasibility (CFT), Config Precheck Summary,
Config Precheck Details, and CFT Precheck Summary tabs for copy-free transition assessment
details.
14 | Copy-Free Transition Guide
In the assessment executive summary, see the Copy-Free Transition Feasibility section for
controller-level assessment details.
You might have to enable macros in Excel to view the assessment workbook.
In the data collection summary of the assessment workbook, if the access status of a system is
FAILED, then the inventory information for that system is invalid. In the assessment executive
summary, the value of some of the fields of this system is displayed as Not Assessed.
Generating an assessment report by importing the inventory report XML
You can import the inventory XML report generated by the Inventory Collect Tool to assess the
features and functionalities of hosts and controllers. You can then identify how these host and
controllers work in the clustered Data ONTAP version selected for transition by creating an
assessment report.
Before you begin
•
You must have run the Inventory Collect Tool and generated the inventory report XML file.
Note: To assess for copy-free transition, you must use Inventory Collect Tool 3.0 to collect
inventory.
•
You must have prepared the 7-Mode systems and hosts for transition assessment.
About this task
The systems that you want to assess need not be reachable while importing the inventory report and
performing transition assessment.
Steps
1. Log in to the 7-Mode Transition Tool, and click Collect and Assess in the home page.
2. Click Import Inventory Report XML.
3. Click Browse, and then select the XML report generated by the Inventory Collect Tool.
4. Click Import.
The assessment status of the system shows Imported;Ready.
5. Select the system for which you want to perform transition assessment.
6. Click Create Transition Assessment Report.
7. In the Create Transition Assessment Report dialog box, select the Data ONTAP version of the
target cluster.
8. Optional: Specify a prefix for the file name of the reports.
9. Click Generate Report.
The AssessmentWorkbook and AssessmentExecutiveSummary reports are generated in XML
format.
10. View the AssessmentWorkbook in Microsoft Excel and AssessmentExecutiveSummary in
Microsoft Word by using Microsoft Office 2007 or later versions.
To view the AssessmentWorkbook in Microsoft Excel, you might have to enable macros in Excel.
Collecting and assessing the inventory information | 15
Generating an FC zone plan
For FC switches, you must generate an FC zone plan as part of the transition assessment report to
configure the zones for grouping the initiator hosts and targets after the migration.
Before you begin
•
The 7-Mode system, hosts, and the cluster must be connected to the same switch.
Supported configurations for generating an FC zone plan on page 16
•
You must have created the required target SVMs and FC LIFs on the cluster.
•
The FC LIFs that are created on the target SVMs will have WWPN, which are different from 7Mode WWPNs. Therefore, perform FC zoning while you transition SAN for FCP.
Steps
1. In the Collect and Assess section, click Add Systems.
2. In the Add System window, perform one of the following actions:
•
Add a single system:
a. Enter the FQDN or IP address of the system.
b. Enter the user name and password for the specified system.
c. Select the system type:
•
◦
Data ONTAP storage systems
◦
Hosts: Microsoft Windows, Red Hat Linux Enterprise, and VMware ESXi
◦
FC switches: Cisco and Brocade
Add multiple systems by clicking Browse, and then selecting the text file that contains the
credentials for multiple systems.
3. Click Add.
If the assessment status of a system is Ready, then you can perform transition assessment for that
system.
4. Generate the transition assessment report with the FC zone plan:
a. Select the systems, including the required FC switches, for transition assessment.
b. Click Create Transition Assessment Report.
c. In the pair systems and start FC zone planner dialog box, select the 7-Mode systems
(single controller or HA pair), the switch connected to the cluster, and an SVM in the cluster.
If you plan to consolidate the FC LUNs to a single SVM by rehosting transitioned volumes,
select the 7-Mode HA pair and the target SVM.
Note: It is a best practice to consolidate the FC LUNs to a single SVM for preserving the 7-
Mode single-system image (SSI) configuration.
If you do not plan to consolidate the FC LUNs, you must generate the FC zone plan for each
7-Mode controller and the corresponding target SVM.
d. Click FC Zoning for paired systems.
16 | Copy-Free Transition Guide
e. In the Create Transition Assessment Report dialog box, select the Data ONTAP version of
the target cluster.
f. Specify a prefix for the file name of the reports.
g. Click Generate Report.
Result
The FC zone plan is generated as a .zip file. The plan contains zones created per the igroup
configurations on the 7-Mode systems. Each zone contains a single initiator WWPN and multiple
SVM target WWPNs.
After you finish
You must use the FC zone plan for configuring the zones to group the initiator hosts and targets for
providing data access from the cluster.
Supported configurations for generating an FC zone plan
You must be aware of the supported configurations of 7-Mode systems, hosts, FC switches, and the
cluster to generate the FC zone plan. You should use the plan to configure zones for the cluster after
migration.
The 7-Mode systems (single controller or an HA pair), hosts, and cluster can be connected either to
the switches in the same fabric or different fabrics, depending on the data center requirements.
The following figure illustrates a configuration in which the 7-Mode systems, hosts, and cluster are
connected to the switches in the same fabric:
The following figure illustrates a configuration in which the 7-Mode systems and cluster are
connected to switches in different fabrics:
Collecting and assessing the inventory information | 17
How you can use the assessment executive summary for
transition assessment
The transition executive summary provides a summary of the 7-Mode controllers, hosts, and FC
switches in your environment. It provides an assessment report of the current features and
functionality that are used and recommends the transition methodology for each volume within your
storage environment. You can use the summary to plan your transition.
The executive summary has the following main sections:
Target cluster
This section lists the clustered Data ONTAP version of the target cluster that you selected during
assessment.
Data collection summary
You can view the list of 7-Mode controllers, hosts, and switches for which you have collected
information. You can view the Data ONTAP version and model details of the 7-Mode controller. You
can also view the OS type, version, and model of the hosts.
Transition feasibility and recommended transition methodology
This section provides a summary of the prechecks that are run on each controller and the feasibility
of transition at the controller and volume level. The volumes that belong to vFiler units that are in the
stopped or inconsistent state or the volumes that are offline or restricted are not included for
assessment. The report displays the count of errors and warnings reported in the precheck against
each controller. You should review these errors and warnings and resolve any issues before
transitioning. Details of these prechecks are available in the Config Precheck Summary tab of the
assessment workbook.
Copy-free transition feasibility: This section lists the number of controller-level prechecks that
resulted in errors and warnings for copy-free transition. If a precheck fails for any one controller in
the HA pair, you cannot transition the HA pair by using copy-free transition. You must resolve all
errors and warnings before transitioning the HA pair. Details of these prechecks are available in the
CFT Precheck Summary tab of the assessment workbook.
Based on the volume and controller configurations and the precheck summary, the executive
summary provides a recommendation about the best transition methodology for each assessed
18 | Copy-Free Transition Guide
volume. For example, you cannot transition 7-Mode SnapLock volumes, traditional volumes, or
FlexCache volumes because these features are not supported in clustered Data ONTAP.
For most of the configurations, 7-Mode Transition Tool is the recommended tool for transition.
However, there are some workloads that cannot be transitioned by 7-Mode Transition Tool for which
you should use an application-based or host-based migration method.
NetApp Technical Report 4052: Successfully Transitioning to Clustered Data ONTAP (Data ONTAP
8.2.x and 8.3)
Storage inventory
This section provides the following information:
•
Storage objects: Provides information about the number of storage objects, such as volumes,
qtrees, LUNs, vFiler units, SnapMirror relationships, shares, and exports, in each controller.
•
Storage utilization: Provides information about the used space, available space, and space utilized
by the 7-Mode controllers.
•
Licenses: Provides the list of feature licenses enabled on each controller.
•
Protocol configuration: Provides details about the protocols configured on the controllers, such as
CIFS, NFS, and SAN protocols, and the versions.
•
SnapMirror interconnectivity: Provides information about the controllers or volumes that are
either the source or destination of a SnapMirror relationship.
You can use this information to identify controllers that are in SnapMirror relationships with the
controllers listed in the report, but are not included for assessment.
•
SnapVault interconnectivity: Provides information about the controllers, volumes, or qtrees that
are either the source or destination of a SnapVault relationship with the specified controller,
volumes, or qtrees in the controller.
Data collection errors
This section provides details about controller and host information that could not be collected by the
7-Mode Transition Tool and the reason for the failure. Details of the data collection errors are
available in the Data Collection Errors tab of the assessment workbook. You can resolve these errors
and assess the systems again.
19
Copy-free transition workflow
The copy-free transition workflow includes preparing for the transition, performing the transition,
and completing the transition. Some of these tasks must be done manually on the 7-Mode systems
and the cluster.
Phases of copy-free transition
Copy-free transition using the 7-Mode Transition Tool consists of the following phases: planning,
SVM provisioning, exporting and halting, cabling, importing, preproduction testing, starting
production, and committing. You should understand the phases to manage the transition effectively.
Copy-free transition is a disruptive operation. Therefore, you must plan for the downtime for the
applications and workload running on the 7-Mode storage systems.
20 | Copy-Free Transition Guide
In most cases, the storage cutover time can be 3 through 8 hours. Cutover time includes the time
taken by the tool to perform two automated operations—the export and halt operation and the import
operation—as well as the time taken for manually cabling the disk shelves to the new controllers. The
export and halt operation and the import operation together can up to 2 hours.
Note: For scaled configurations, the export and halt operation and the import operation together
can take more than 2 hours. 7-Mode Transition Tool detects such conditions and provides a
warning.
Cabling of the disk shelves can take from 1 hour through 6 hours. This cutover time guidance does
not include the time for the required preproduction testing and assumes an error-free transition
without unexpected failures such as disk failure.
Planning the project
You can plan the following details about the source and target of a copy-free transition project:
•
7-Mode HA pair and vFiler unit details
•
Target cluster nodes and mapping of source controllers to target nodes
•
7-Mode controller or vFiler unit to SVM mapping
•
IP addresses to transition (new LIFs or existing 7-Mode IP addresses) and the IPspaces and
broadcast domains on the SVM
Note: The 7-Mode Transition Tool does not support the transition of FC and iSCSI LIFs. These
LIFs must be manually configured on the SVMs before transition.
In this phase, prechecks are run to verify whether the 7-Mode HA pair is ready to be migrated to
clustered Data ONTAP. The 7-Mode Transition Tool also verifies that the cluster is configured
properly and can support the transition.
You must resolve any errors before continuing with the transition. Although the tool allows you to
continue without resolving warnings, it is a best practice to address any warnings before continuing
with the transition. You can run the prechecks multiple times to verify that all the errors have been
resolved.
SVM provisioning
After planning your transition project, you must perform some manual tasks, such as adding licenses,
creating the CIFS server, and creating SAN LIFs, to prepare the cluster and SVMs for transition.
You can then apply the configurations on the SVMs by using the tool. All the 7-Mode controller or
vFiler unit level configurations are transitioned to the mapped SVM. Volume and LUN
configurations are not transitioned during this phase; they are transitioned in the import phase.
At the end of this phase, you should manually verify the configurations applied to SVMs and make
the necessary changes.
Copy-free transition workflow | 21
Exporting storage configurations and halting 7-Mode systems
This phase starts the cutover window for copy-free transition. Client access must be manually
disconnected. However, all the NAS and SAN services must be up and running on the 7-Mode HA
pair. This is because the 7-Mode Transition Tool requires all services to be up and running for
collecting the volume-level configurations from the 7-Mode systems.
The tool performs the following operations in the export phase:
•
Collects all volume and storage configurations
•
Creates a Snapshot copy of each transitioning aggregate
This Snapshot copy is used for rolling back to 7-Mode, if required.
•
Boots the 7-Mode controllers in maintenance mode
•
Removes disk ownership from the disks attached to the 7-Mode controllers
•
Disables disk autoassignment on the target cluster nodes
Cabling the 7-Mode disk shelves
You must perform the tasks in this phase manually. You must ensure that the disk shelf IDs are
unique across the 7-Mode controllers and target cluster nodes.
Note: If there are duplicate shelf IDs, you must change the disk shelf IDs and power cycle the disk
shelves.
You must disconnect all the 7-Mode disk shelves and hot-add them to the target cluster nodes. After
the disk shelves are connected to the target cluster nodes, you must power cycle the disk shelves.
It is a best practice to manually verify the cabling by using Config Advisor. Config Advisor is a
configuration validation and health check tool for NetApp systems. It can be deployed at both secure
sites and non-secure sites for data collection and system analysis.
You can then verify the cabling by using the 7-Mode Transition Tool to proceed with the transition.
The 7-Mode Transition Tool performs only a subset of the cabling checks that are performed by
Config Advisor.
Importing 7-Mode data and configurations
All the storage objects (aggregates, volumes, and LUNs) and the associated configurations are
transitioned during this phase.
The tool performs the following operations in the import phase:
•
7-Mode disks are assigned to the mapped target cluster nodes.
•
All 7-Mode aggregates, volumes, and LUNs are converted to the clustered Data ONTAP format.
•
LIFs are configured on the SVMs in the administrative up state.
•
All volume-level and LUN-level configurations are applied.
Preproduction testing
You must manually test all the transitioned aggregates, volumes, and configurations that are applied
to the target SVMs during this phase. You must also perform all manual tasks for completing your
configuration—for example, configuring hosts and performing host remediation for SAN hosts.
You cannot perform certain operations on the transitioned aggregates or volumes during this phase.
There are also certain operations that are not recommended during the testing phase. This is to ensure
a successful rollback operation in case you decide to roll back to 7-Mode.
22 | Copy-Free Transition Guide
You must also manually test all applications and workloads thoroughly before starting data access in
a production environment.
Important: The aggregates might run out of space because of the aggregate Snapshot copies and
the write operations that are performed during the testing. If the free physical space is less than 5%
of the total space, the aggregates are taken offline. You must regularly monitor the free physical
space available in the transitioned aggregates to avoid space issues.
Starting production
After testing all workloads and applications, you can start client access to the transitioned data in the
production environment. This stage of transition—where production is started but the project is not
yet committed—is the final stage of transition when you can decide to roll back to 7-Mode. You must
not prolong this phase because of the following reasons:
•
The probability of running out of space in the transitioned aggregates increases as new data is
written to the volumes.
•
Any new data written to the volumes during this stage will not be available after rollback.
Committing the project
In this final stage of transition, the aggregate-level Snapshot copies that were created during the
export phase are deleted.
You cannot roll back to 7-Mode after you commit the 7-Mode aggregates and complete the transition.
Related information
NetApp Downloads: Config Advisor
23
Preparing for copy-free transition
Before starting the copy-free transition, you must identify the 7-Mode HA pair to transition,
understand the requirements and restrictions for migration, and prepare the 7-Mode systems and
cluster for transition. You must also be aware of the Data ONTAP features that are supported and
unsupported for transition.
Related information
NetApp Interoperability Matrix Tool
Requirements for copy-free transition
You must be aware of the requirements for the 7-Mode systems, clusters, ONTAP versions, and disk
shelves for copy-free transition.
Platform models
Copy-free transition is supported only on mid-end and high-end FAS systems and IBM N
series systems. To view the supported platforms for 7-Mode and the target cluster nodes,
see the Interoperability Matrix Tool.
24 | Copy-Free Transition Guide
NetApp Interoperability Matrix Tool
Data ONTAP operating in 7-Mode
At the time of this publication, copy-free transition is supported on 7-Mode systems
running Data ONTAP 8.1.4P4 - 8.1.4P9 and Data ONTAP 8.2.1 or later. For the latest
information about the Data ONTAP versions supported for copy-free transition, see the
Interoperability Matrix Tool.
NetApp Interoperability Matrix Tool
Clustered Data ONTAP
The target cluster must be running ONTAP 8.3.2 or later.
HA configuration
The 7-Mode controllers and target cluster nodes must be in an HA configuration. The HA
pairs must be healthy, and none of the nodes must be in takeover mode. Stand-alone
controllers are not supported for copy-free transition.
Disk shelf models
The following disk shelf models are supported:
•
DS4486
•
DS4246
•
DS4243
•
DS2246
•
DS14mk4 FC (not supported in ONTAP 9.0)
•
DS14mk2 AT (not supported in ONTAP 9.0)
Note: DS14mk2 FC is not supported.
Disk firmware
You must download and install the latest disk qualification package, disk firmware, and
disk shelf and ACP firmware on the 7-Mode systems and target cluster nodes.
NetApp Downloads: Disk Qualification Package
NetApp Downloads: Disk Drive and Firmware
NetApp Downloads: Disk Shelf Firmware
Tool to verify cabling
After connecting the 7-Mode disk shelves to the target cluster nodes during the transition,
you must use Config Advisor to verify the cabling.
NetApp Downloads: Config Advisor
Note: The Copy-Free Transition Cabling Guide, which is available in the 7-Mode Transition Tool
package, is not updated with the latest supported 7-Mode and ONTAP versions, platform models,
and disk shelf models. For the latest supported versions, see the Interoperability Matrix Tool.
NetApp Interoperability Matrix Tool
Preparing for copy-free transition | 25
Tools and documentation required for copy-free transition
You should use Config Advisor to verify the cabling of the disk shelves. Additional documentation is
also available for cabling and SAN host remediation.
Config Advisor
You should use the “Transition” execution profile in Config Advisor to verify the cabling after the 7Mode disk shelves are connected to the target cluster nodes.
NetApp Downloads: Config Advisor
Documentation
•
7-Mode Transition Tool Copy-Free Transition Cabling Guide
Provides quick reference information for cabling the disk shelves during copy-free transition.
You can download this guide from the 7-Mode Transition Tool home page.
•
SAN host transition and remediation
Describes the pre-transition and post-transition steps that have to be performed on SAN hosts
when transitioning using copy-free transition.
Port requirements for communicating with the 7-Mode
Transition Tool
The 7-Mode Transition Tool communicates with the 7-Mode system and the cluster over certain
ports. You must ensure that these ports on the 7-Mode system and the cluster are open to allow
communication with the 7-Mode Transition Tool.
Ports that must be open on the 7-Mode systems
7-Mode Transition Tool communicates with the 7-Mode systems by using HTTPS on port 443.
Ports that must be open on the cluster
7-Mode Transition Tool communicates with the cluster by using HTTPS on port 443.
Ports that must be open on the 7-Mode Transition Tool
The port 8443 must be open for the web interface.
To transition netgroups and CIFS local users and groups, the following requirements must be met:
•
Port 8088 must be available.
For an alternative to port 8088, you must change the port specified by the tool.http.port
parameter in the transition-tool.conf file of the 7-Mode Transition Tool install directory.
Note: You must restart the 7-Mode Transition Tool service after changing the port in the
configuration file.
•
The firewall should be configured in such a way that the SVM data LIFs are able to communicate
with the 8088 port or the port specified by the tool.http.port parameter in the transitiontool.conf file.
•
The IP address of the system where the 7-Mode Transition Tool is installed must be pingable
from the SVM data LIF.
26 | Copy-Free Transition Guide
Related information
7-Mode Transition Tool installation and administration
Preparing the 7-Mode HA pair for transition
Before starting a transition, you must complete certain tasks on the 7-Mode system, such as enabling
the 7-Mode system to communicate with the target cluster, and enabling HTTPS and TLS.
Before you begin
The HA pair must be healthy and none of the nodes must be in the takeover mode, which can be
verified by using the cf status command. You can also use the NetApp AutoSupport tool to detect
any errors or at risk conditions.
Steps
1. If HTTPS is not enabled on the storage system, enable HTTPS:
options httpd.admin.ssl.enable on
HTTPS is enabled by default.
2. Enable TLS on the 7-Mode storage systems for enabling the 7-Mode Transition Tool to
communicate with the 7-Mode systems:
a. If SSL is not already enabled on the storage system, set up and start SSL:
secureadmin setup ssl
SSL is set up for the storage systems by default. If SSL has been previously set up for the
storage system, you are asked whether you want to continue. You can exit the SSL setup if
you do not want to make any changes.
b. Enable SSL:
options ssl.enable on
This option must be enabled for allowing communication over TLS.
c. Enable TLS:
options tls.enable on
d. Disable SSLv2 and SSLv3 on the 7-Mode system:
options ssl.v2.enable off
options ssl.v3.enable off
The 7-Mode Transition Tool uses TLS or SSL protocols for communicating with the 7-Mode
storage systems. The tool communicates with the storage system using the TLS protocol if TLS is
enabled on the storage system. If TLS is disabled and SSLv3 is enabled on a storage system, the
tool uses SSLv3 to communicate with the storage system.
Important: The best practice is to enable TLS and disable SSLv2 and SSLv3 in order to avoid
security vulnerabilities.
Preparing for copy-free transition | 27
Setting up the SP or RLM on the 7-Mode systems for copyfree transition
If the Service Processor (SP) or the Remote LAN Module (RLM) is not already configured on the 7Mode storage systems or if you have configured the SP or RLM with an IPv6 address, you must
configure the SP or RLM with an IPv4 address.
Before you begin
•
SSHv2 must be supported on the host on which the 7-Mode Transition Tool is installed.
•
You must have access to the SP or RLM “naroot” account or a Data ONTAP user account with
the credentials of the “admin” role or a role with “login-sp” capability.
About this task
7-Mode Transition Tool accesses the 7-Mode systems when the systems are halted during transition
by using a remote management device that can be the SP or RLM, whichever is available on your
system based on the platform model. You must configure the SP or RLM with an IPv4 address. IPv6
configuration is not supported for transition.
Choices
•
Configure the SP and provide SP access to the host on which 7-Mode Transition Tool is installed.
1. Configure and enable the SP network with an IPv4 address:
sp setup
Example
system1> sp setup
The Service Processor (SP) provides remote management capabilities
including console redirection, logging and power control.
It also extends autosupport by sending
additional system event alerts. Your autosupport settings are use
for sending these alerts via email over the SP LAN interface.
Would you like to configure the SP? y
Would you like to enable DHCP on the SP LAN interface? n
Please enter the IP address of the SP []: 192.168.123.98
Please enter the netmask of the SP []: 255.255.255.0
Please enter the IP address for the SP gateway []: 192.168.123.1
Do you want to enable IPv6 on the SP ? n
Verifying mailhost settings for SP use...
2. Verify the SP network configuration settings:
sp status
Example
system1> sp status
Service Processor
Status: Online
Firmware Version:
1.2
Mgmt MAC Address:
00:A0:98:01:7D:5B
Ethernet Link:
up
Using DHCP:
no
IPv4 configuration:
IP Address:
192.168.123.98
Netmask:
255.255.255.0
Gateway:
192.168.123.1
28 | Copy-Free Transition Guide
3. Provide SP access to the host on which the 7-Mode Transition Tool is installed:
options sp.ssh.access host=7mtt_host
7mtt_host is the host name or IP address of the host on which the 7-Mode Transition Tool is
installed.
Note: When you configure the SP, all hosts are granted access by default. You must perform
this step if you want to restrict the access to specific hosts.
4. From the host on which the 7-Mode Transition Tool is installed, log in to the SP:
ssh username@SP_IP_address
When prompted, enter the password for the user name.
The SP prompt is displayed, indicating that you have access to the SP CLI.
•
Configure the RLM and provide RLM access to the host on which the 7-Mode Transition Tool is
installed.
1. Configure the RLM network with an IPv4 address:
rlm setup
In the RLM CLI wizard, you must enter the IP address, network mask, and gateway for the
RLM.
Example
system> rlm setup
The Remote LAN Module (RLM) provides remote management
capabilities
including console redirection, logging and power control.
It also extends autosupport by sending
additional system event alerts. Your autosupport settings
are used
for sending these alerts via email over the RLM LAN
interface.
Would you like to configure the RLM? y
Would you like to enable DHCP on the RLM LAN interface? n
Please enter the IP address for the RLM []:192.168.123.98
Please enter the netmask for the RLM []:255.255.255.0
Please enter the IP address for the RLM gateway []:192.168.123.1
Do you want to enable IPv6 on the RLM ? n
Verifying mailhost settings for RLM use...
2. Verify that the RLM network configuration is correct:
rlm status
Example
system> rlm status
Remote LAN Module
Status: Online
Part Number:
110-00030
Revision:
A0
Serial Number:
123456
Firmware Version:
4.0
Mgmt MAC Address:
00:A0:98:01:7D:5B
Ethernet Link:
up, 100Mb, full duplex, auto-neg
complete
Using DHCP:
no
IPv4 configuration:
IP Address:
192.168.123.98
Netmask:
255.255.255.0
Gateway:
192.168.123.1
Preparing for copy-free transition | 29
3. Provide RLM access to the host on which the 7-Mode Transition Tool is installed:
options rlm.ssh.access host=7mtt_host
7mtt_host is the host name or IP address of the host on which the 7-Mode Transition Tool is
installed.
Note: When you configure the RLM, all hosts are granted access by default. You must
perform this step if you want to restrict the access to specific hosts.
4. From the host on which the 7-Mode Transition Tool is installed, log in to the RLM:
ssh username@RLM_IP_address
When you are prompted, you must enter the password for the user name.
The RLM prompt is displayed, indicating that you have access to the RLM CLI.
Related information
Find a System Administration Guide for your version of Data ONTAP 8
Preparing the network for transition
You must prepare the data network of the cluster for transition by creating logical ports (VLANs and
interface groups).
Before you begin
The NTP server must be configured and the time must be synchronized across the 7-Mode systems
and cluster.
Steps
1. Create VLANs or interface groups on the target cluster nodes, if required.
To provide network connectivity after transition, you should transition the 7-Mode IP addresses to
a similar network topology in clustered Data ONTAP. For example, if the 7-Mode IP addresses
are configured on physical ports, the IP addresses should be transitioned to appropriate physical
ports in clustered Data ONTAP. Similarly, IP addresses configured on VLAN ports or interface
groups should be transitioned to appropriate VLAN ports or interface groups in clustered Data
ONTAP.
ONTAP 9 man page: network port vlan create
ONTAP 9 man page: network port ifgrp create
2. If you want SVMs in the non-default IPspace, create the required IPspaces.
The 7-Mode IP addresses or the new LIFs that are selected for transition are created in the
IPspace of the mapped SVM.
Note: IPv6 addresses cannot be transitioned and must be configured manually post-transition.
ONTAP 9 man page: network ipspace create
Related information
Network and LIF management
30 | Copy-Free Transition Guide
Considerations for transitioning 7-Mode IP addresses
You must be aware of certain considerations when transitioning 7-Mode IP addresses to Storage
Virtual Machines (SVMs) in clustered Data ONTAP.
•
You can transition existing 7-Mode IP addresses or specify new IP addresses to be configured on
the SVM by using the 7-Mode Transition Tool.
◦
Existing 7-Mode IP addresses are created on the SVM in the administrative down state in the
apply configuration (precutover) phase.
◦
New IP addresses are created on the SVM in the administrative up state in the apply
configuration (precutover) phase.
•
IPv6 addresses cannot be transitioned and must be manually configured after the transition.
•
iSCSI and FC LIFs are not transitioned and must be manually configured after the transition.
Preparing the cluster for transition
Before transition, you must prepare the cluster to communicate with the 7-Mode Transition Tool and
prepare the SVMs for transition. You can transition to a target HA pair that has data aggregates.
Before you begin
•
The cluster must already be set up and the target cluster nodes must be joined to the cluster.
Software setup
•
The SVMs must be created and assigned to an IPspace.
•
You can transition the 7-Mode disk shelves to a target HA pair that has preexisting data
aggregates and volumes.
For a two-node cluster, you must have a data aggregate to host the root volumes of the target
SVMs. For a cluster with four or more nodes, the root volumes of the SVMs can be hosted either
on the target nodes of the transition or on other nodes in the cluster.
Steps
1. From an administration host, verify that the cluster is reachable by using the cluster-management
LIF:
ssh username@cluster_mgmt_IP
2. Enable SSLv3 or FIPS on the cluster:
If you want to enable...
Enter...
SSLv3
system services web modify -sslv3-enabled true
FIPS 140-2 compliance
system services web modify -ssl-fips-enabled true
When FIPS 140-2 compliance is enabled, SSLv3 is disabled. Data ONTAP prevents you from
enabling SSLv3 when FIPS 140-2 compliance is enabled. If you enable FIPS 140-2 and then
subsequently disable it, SSLv3 remains disabled.
Important: The best practice is to enable FIPS because of the security vulnerabilities in SSLv3.
3. Verify that HTTPS is allowed on the cluster-management LIF:
a. View the firewall policy for the cluster-management LIF by using the network interface
show command.
Preparing for copy-free transition | 31
Example
cluster1::> network interface show -vserver cluster1 -lif
cluster_mgmt -fields firewall-policy
vserver lif
firewall-policy
------- ------------ --------------cluster1 cluster_mgmt mgmt
b. Verify that the firewall policy associated with the cluster-management LIF allows HTTPS
access by using the system services firewall policy show command.
Example
cluster1::> system services
Policy
Service
---------------- ---------mgmt
dns
http
https
ndmp
ntp
rsh
snmp
ssh
telnet
9 entries were displayed.
firewall policy show -policy mgmt
Action IP-List
------ -------------------allow
allow
allow
allow
allow
deny
allow
allow
deny
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
0.0.0.0/0,
::/0
::/0
::/0
::/0
::/0
::/0
::/0
::/0
::/0
System administration
Related information
NetApp Documentation: Product Library A-Z
Gathering cabling information for transition
Before starting copy-free transition, you must gather information about the adapters, ports, disk
shelves, and storage connectivity of your 7-Mode controllers, and then plan how to connect the 7Mode disk shelves to the target cluster nodes.
Before you begin
You must have printed the copy-free transition cabling worksheet.
Copy-free transition cabling worksheet on page 33
Steps
1. Use Config Advisor to perform a health check on the 7-Mode storage and cabling and collect
cabling data.
You should use the 7-Mode Install Checks option from the “Data ONTAP 7 and 8 (7Mode)” execution profile.
2. Gather the required information about each 7-Mode controller by using the following command:
sysconfig slot_number
You can use the output of this command to identify which ports are used for disk shelf
connectivity.
32 | Copy-Free Transition Guide
Example
host1> sysconfig 3
slot 3: SAS Host Adapter 3a
24 Disks:
1 shelf with IOM3
slot 3: SAS Host Adapter 3b
24 Disks:
1 shelf with IOM3
slot 3: SAS Host Adapter 3c
24 Disks:
1 shelf with IOM3
slot 3: SAS Host Adapter 3d
24 Disks:
1 shelf with IOM3
13440.0GB
13440.0GB
13440.0GB
13440.0GB
3. From the cluster, run the following nodeshell command on each node:
system node run -node node_name -command sysconfig -a
You can use the output of this command to obtain information about the available ports and
expansion card slots.
4. On the target cluster nodes, plan the ports to be used for connecting the 7-Mode disk shelves:
a. Review the available (open) ports.
b. Review the expansion card slots.
c. Plan the expansion card configuration.
You can plan to move the expansion cards from the 7-Mode systems if they are also supported
on the destination platform and clustered Data ONTAP version. You can also plan for PAM
cards, if required.
NetApp Hardware Universe
d. Plan the destination ports to use for the disk shelf cabling.
The selection of the destination ports depends on some of the following factors:
•
Separate or existing disk shelf stack
•
Port availability
•
SAS or FC connections
•
Availability of on-board ports or expansion cards
5. Go to the data center to physically record the port connections on the 7-Mode controllers and
target cluster nodes in the cabling worksheet:
a. Record the used ports on the 7-Mode controllers in the cabling worksheet.
b. Record the used ports on the target cluster nodes in the cabling worksheet.
c. Record the destination ports to be used for connecting the 7-Mode disk shelves, as planned in
Step 4.
d. Ensure that you have the right cables for connecting the disk shelves.
You should identify any issues with cabling based on the new disk shelf stack location.
e. Plan for longer cable lengths due to ladder racking or data center requirements.
f. Label each disk shelf stack and cable on the 7-Mode controllers.
The best practice is to label the 7-Mode disk shelf stacks in case you want to roll back the
transition and have to reconnect the disk shelves to the 7-Mode controllers.
Preparing for copy-free transition | 33
Related information
SAS Disk Shelves Universal SAS and ACP Cabling Guide
SAS Disk Shelves Installation and Service Guide for DS4243, DS2246, DS4486, and DS4246
DiskShelf14mk2 AT Hardware Service Guide
DS14mk2 FC, and DS14mk4 FC Hardware Service Guide
Copy-free transition cabling worksheet
You can use the copy-free transition cabling worksheet to plan your cabling. You must record
information about the ports and disk shelves connected to the 7-Mode controllers and target cluster
nodes. You should also record the ports to use for connecting the 7-Mode disk shelves to the target
cluster nodes.
•
Module A/B Ports: Port connections for module A/B
•
Shelf Type/Asset Tag: Disk shelf type
•
Shelf IDs: Disk shelf IDs
34 | Copy-Free Transition Guide
Sample cabling worksheet
7-Mode cabling
Clustered Data ONTAP cabling
Controller A (host name): 7hostA
Node A (host name): cluster1-01
Location: Colorado Floor: Third Rack: 8
Location: Colorado Floor: Fifth Rack: 3
Module
A Ports
Module
B Ports
Shelf
Type/
Asset
Tag
Shelf IDs
Module
A Ports
Module
B Ports
Shelf
Type/
Asset
Tag
1a
0a
DS4243/
1502547
10-13
1a
0a
DS4243/ 10-11
174243-2
1b
0b
DS4243/
1512052
30-37
1b
0b
DS4243/ 20-23
150254-7
1c
(offline)
0c
(offline)
n/a
n/a
1c
0c
DS4243/ 30-37
151205-2
1d
0d
DS4243/
1439214
14-15
1d
0d
DS4243/ 14-15
143921-4
Shelf
IDs
Controller B (host name): 7hostB
Node B (host name):cluster1-02
Location: Colorado Floor: Third Rack: 8
Location: Colorado Floor: Fifth Rack: 3
Module
A Ports
Module
B Ports
Shelf
Type/
Asset
Tag
Shelf IDs
Module
A Ports
Module
B Ports
Shelf
Type/
Asset
Tag
1a
0a
DS4243/
1742636
10-13
1a
0a
DS4243/ 10-11
174233-2
1b
(offline)
0b
(offline)
n/a
n/a
1b
0b
DS4243/ 20-23
174263-6
1c
0c
DS4243/
1742749
30-37
1c
0c
DS4243/ 30-37
174274-9
1d
0d
DS4243/
1742856
14-15
1d
0d
DS4243/ 14-15
174285-6
Shelf
IDs
Preparing 7-Mode aggregates and volumes for transition
Before transition, you must ensure that the 7-Mode aggregates and volumes are eligible for transition
and perform some manual steps before transition. For example, some volume types cannot be
transitioned and any 32-bit data must be removed from the 7-Mode systems before transition.
Preparing for copy-free transition | 35
Restrictions for transitioning 7-Mode aggregates and volumes
You must be aware of certain restrictions for transitioning 7-Mode aggregates and volumes. Some of
the restrictions are due to features that are not supported in clustered Data ONTAP. For some
restrictions, you can perform a corrective action that enables you to continue with the transition.
Volume types
The following types of volumes are not supported for transition because these are not supported in
clustered Data ONTAP:
•
Traditional volumes
You can use host-based transition methods to transition traditional volumes.
NetApp Technical Report 4052: Successfully Transitioning to Clustered Data ONTAP (Data
ONTAP 8.2.x and 8.3)
•
SnapLock volumes
•
FlexCache volumes
Aggregate and volume states
Transition is blocked if any of the 7-Mode aggregates and volumes selected for the transition are in
one of the following states:
•
Offline
•
Restricted
•
Inconsistent (wafl inconsistent)
FlexClone volumes
The clone hierarchy and storage efficiency are preserved during the copy-free transition. However,
you must ensure that the parent FlexVol volume and all its FlexClone volumes belong to the same
vFiler unit. If the FlexClone volumes are in different vFiler units from the parent volume, you must
choose one of the following actions:
•
Move the FlexClone volumes to the vFiler unit that owns the parent FlexVol volume.
•
Split the clones from the parent FlexClone volume, and then transition these volumes as FlexVol
volumes.
Volume with qtrees that belong to a different vFiler unit
You cannot transition volumes with qtrees, where the qtrees are owned by a different vFiler unit than
that of the volume. Before transition, you must ensure that each volume and all its qtrees belong to
the same vFiler unit by performing one of the following actions:
•
Move the qtrees to the vFiler unit that owns the volume.
•
Delete the qtrees.
Inode to parent pathname translation setting
The inode to parent pathname translations must be enabled on each volume. You can enable the
parent to pathname translations by turning off the no_i2p option:
vol options vol_name no_i2p off
36 | Copy-Free Transition Guide
You do not have to wait for the i2p scan to finish and you can continue with the transition
preparation.
Preparing for transitioning 7-Mode systems with 32-bit aggregates
32-bit aggregates, volumes, and Snapshot copies are not supported in clustered Data ONTAP 8.3 and
later. Therefore, you must expand the 32-bit aggregates to 64-bit, and then find and remove any 32bit volumes and Snapshot copies from the 7-Mode system before transition.
Choices
•
32-bit aggregates
1. Expanding an aggregate to the 64-bit format on page 36
2. Finding and removing 32-bit volumes and Snapshot copies on page 37
•
32-bit volumes or Snapshot copies
Even if you have only 64-bit aggregates and volumes, some 32-bit or mixed-format FlexVol
volumes or Snapshot copies might remain. You must remove these volumes and Snapshot copies
before transition.
Finding and removing 32-bit volumes and Snapshot copies on page 37
Related information
NetApp Technical Report 3978: In-Place Expansion of 32-Bit Aggregates to 64-Bit Overview and
Best Practices
Expanding an aggregate to the 64-bit format
If your system contains 32-bit aggregates, you must expand them to the 64-bit format on your 7Mode system before transitioning to Data ONTAP 8.3 or later versions, because those versions of
Data ONTAP do not support the 32-bit format.
Before you begin
•
If the aggregate contains destination volumes for a SnapMirror relationship with a 32-bit source
volume, the aggregate containing the source volume must be expanded before expanding the
aggregate containing the destination volume.
About this task
For volumes in a SnapMirror relationship, the destination volume inherits the format of the source
volume while the mirror is intact. If the aggregate you are expanding contains a destination volume
whose source is a 32-bit volume and you break the mirror before expanding the aggregate, the
destination volume is expanded to the 64-bit format. However, if you reestablish the mirror and the
source volume is still 32-bit, the destination volume returns to the 32-bit format. For this reason, you
must expand the aggregate containing the source volume before reestablishing the SnapMirror
relationship if you want to expand all 32-bit volumes in the aggregate to the 64-bit format.
Steps
1. Enter advanced privilege mode:
priv set advanced
2. Initiate the expansion:
aggr 64bit-upgrade start aggr_name
Preparing for copy-free transition | 37
3. Perform the appropriate action:
If the command...
Then...
Initiates successfully
Proceed to the next step.
Indicates that one or more
volumes could not be
expanded because they did
not have enough space
Retry the command, adding the grow-all option.
Indicates that the expansion
could not be completed for
some other reason
Perform the appropriate action, based on the issue outlined in the error
message.
4. Display the status of the expansion:
aggr 64bit-upgrade status aggr_name
The current status of the expansion is displayed. When the message indicates that there is no
upgrade in progress, the expansion is complete.
5. Optional: Confirm that all volumes in the aggregate are 64-bit format:
aggr 64bit-upgrade status aggr_name -all
6. Return to administrative privilege mode:
priv set admin
Result
The aggregate is expanded to the 64-bit format. However, even if all volumes are expanded, some 32bit Snapshot copies might remain. The presence of 32-bit Snapshot copies in the source volumes
prevents an upgrade or transition to Data ONTAP 8.3 or later.
Finding and removing 32-bit volumes and Snapshot copies
Even if you have expanded all of your aggregates to the 64-bit format, some 32-bit or mixed-format
FlexVol volumes or Snapshot copies can remain. These volumes and Snapshot copies must be
removed before your data can be accessed by a cluster running Data ONTAP 8.3 or later.
Before you begin
•
You must have expanded all 32-bit aggregates on the system to the 64-bit format.
About this task
You must repeat the steps in this task for each aggregate that contains 32-bit volumes and Snapshot
copies.
Steps
1. Enter advanced mode:
priv set advanced
2. Display the format of all volumes in the aggregate:
aggr 64bit-upgrade status aggr_name -all
Each volume in the aggregate is displayed with its format.
3. For each 32-bit or mixed-format volume, determine the reason that the volume has not been
expanded to the 64-bit format, and then take the appropriate action.
38 | Copy-Free Transition Guide
If you cannot determine the reason that the volume was not expanded, retry the aggregate
expansion.
If the volume…
Then…
Is the destination of a
SnapMirror relationship
Expand the aggregate containing the source volume to the 64-bit format.
Is a read-only volume (but
not a SnapMirror destination)
Make the volume writable and retry the expansion, or destroy the
volume.
Did not expand because of
insufficient free space in the
volume or aggregate
Increase the free space in the volume or aggregate and retry the
expansion.
All 32-bit and mixed-format volumes in the aggregate are now 64-bit. You can confirm this by
repeating the previous step.
4. Display the format of all Snapshot copies on the system:
snap list -fs-block-format
5. Remove the 32-bit Snapshot copies by using the snap delete command.
Attention: This action deletes the data in the Snapshot copies. You must be certain that you do
not need to retain the Snapshot copies before you delete them. Alternatively, you can wait for
the 32-bit Snapshot copies to be aged out. The amount of time this takes depends on your
Snapshot copy schedule.
If a Snapshot copy is the base Snapshot copy for a FlexClone volume, you must split the
FlexClone volume from its parent before you can remove the Snapshot copy.
All 32-bit Snapshot copies are removed. You can confirm this by repeating the previous step.
6. Return to the administrative privilege level:
priv set admin
Aggregate space requirements for transition
Before transition, you must ensure that the 7-Mode aggregates have adequate free space. The 7-Mode
Transition Tool performs various space checks on the aggregates based on the physical space, logical
space, space occupied by Snapshot copies, and space guarantee settings. You must also be aware of
the space considerations with Flash Pool aggregates.
Physical space in the aggregates
Transition is blocked if the free space is less than 5% of the physical space in the 7-Mode aggregates.
The best practice is to have at least 20% free space in the 7-Mode aggregates before transition.
The additional space is required in the aggregates for the following reasons:
•
Creating the aggregate-level Snapshot copy for each 7-Mode aggregate during the export phase
•
Testing the workload on the transitioned aggregates with new data in the preproduction testing
phase
If you do not have additional space, you can add disks to the 7-Mode systems before transition. If
adding disks is not feasible or if you can ensure that only limited amount of data is written on the
transitioned volumes during the preproduction phase, the 7-Mode Transition Tool allows you to
acknowledge this error and continue with the transition. However, you must continue to monitor the
aggregate space during the transition and ensure that the aggregates do not grow in the preproduction
testing phase.
Preparing for copy-free transition | 39
Logical space in the aggregates
If the logical space in the 7-Mode aggregates is more than 97% full, 7-Mode Transition Tool throws a
blocking error during precheck. You can ignore this error during the planning phase and continue
with the transition; however, you must ensure that the logical space used is less than 97% before the
export and halt operation by either reducing the size of the volumes in such aggregates or adding
more disks to the aggregates. You cannot ignore this error in the export and halt phase.
Snapshot spill
If the Snapshot copies in the 7-Mode aggregates occupy more space than the allocated space for
Snapshot copy reserve, the creation of aggregate-level Snapshot copies in the export and halt
operation might fail. 7-Mode Transition Tool throws a blocking error during precheck for this
condition. In such conditions, you must delete all the existing aggregate-level Snapshot copies during
the planning phase.
If you do not want to delete the existing Snapshot copies, you can ignore this error during the
planning phase and continue with the transition; however, you must ensure that the Snapshot copy
used capacity percentage is less than 100% before the export and halt operation.
Space guarantee settings
7-Mode Transition Tool throws a blocking error during precheck if the 7-Mode controllers have
volumes with the following space guarantee settings:
•
Volume-guaranteed volumes with guarantee disabled
•
File-guaranteed volumes
Volume-guaranteed volumes with guarantee disabled
In some cases, the space guarantee is disabled for the volume guaranteed volumes because
of lack of space in the aggregates.
You must create sufficient free space on the 7-Mode aggregates and then enable space
guarantee for such 7-Mode volumes by using the following 7-Mode command:
vol options volume_name guarantee volume
If you do not want to perform any corrective actions on 7-Mode, you can ignore this error.
After the transition, examine the volumes for which guarantee is disabled and enable the
guarantee manually by using the following command:
volume modify -vserver -volume -space-guarantee volume
File-guaranteed volumes
File guarantee is not supported in clustered Data ONTAP.
If you have file-guaranteed volumes, you must perform one of the following actions:
•
If the 7-Mode volumes contain space-reserved LUNs or files, change the space
guarantee type of the volumes to volume by using the 7-Mode command:
vol options volume_name guarantee volume
You must ensure that there is enough free space on the 7-Mode aggregates before
running this command.
•
If the 7-Mode volumes do not contain any space-reserved LUNs or files, change the
space guarantee of the volumes to none by using the following 7-Mode command:
vol options volume_name guarantee none
If you do not want to perform any corrective actions on 7-Mode, you can ignore this error
and continue with the transition.
40 | Copy-Free Transition Guide
During the transition, if these volumes contain space-reserved LUNs or files, their space
guarantee will be automatically converted to volume, but the space guarantee will be
disabled initially. You must create sufficient free space on the aggregates and then
manually enable the guarantee by using the following command:
volume modify -vserver -volume -space-guarantee volume
If the volumes do not contain any space-reserved LUNs or files, their space guarantee will
be automatically converted to none during the transition.
Additional consideration for Flash Pool aggregates
Transition is not supported if the free space in the SSDs of Flash Pool aggregates is less than 5% of
the total disk space of the SSDs. You must either disable the SSD cache or add more SSDs to
continue with the transition.
Related references
Ignorable error categories on page 92
Related information
Disk and aggregate management
Preparing to transition name services
Name service configurations that include DNS, LDAP, NIS, hosts, name services switch, UNIX users
and groups, and netgroups configurations are transitioned by the 7-Mode Transition Tool. You must
be aware of some considerations before transitioning name services configurations.
Name services transition: supported and unsupported configurations, and
required manual steps
You must be aware of the name services configurations that are transitioned by the 7-Mode
Transition Tool. Some name services configurations are not transitioned to clustered Data ONTAP
because either these are not supported in clustered Data ONTAP or these must be manually
transitioned.
You should verify all the precheck error and warning messages to evaluate the impact of such
configurations on transition.
Configurations that are transitioned
At a high level, the following name services configurations are transitioned by the 7-Mode Transition
Tool:
•
DNS configuration (/etc/resolv.conf)
•
LDAP configuration
•
NIS configuration
•
Name service switch configuration (/etc/nsswitch.conf and /etc/resolv.conf)
•
Hosts configuration (/etc/hosts)
•
UNIX users and groups (/etc/passwd and /etc/group)
•
Netgroups configuration (/etc/netgroup)
Preparing for copy-free transition | 41
See the precheck results for details about these name services configurations.
Unsupported configurations in clustered Data ONTAP
•
NIS slave
•
NIS broadcast
•
NIS groups caching
•
Dynamic DNS
•
DNS cache
•
Shadow database
•
Host database sources other than file or DNS
Clustered Data ONTAP supports only file and DNS for host lookup; other database sources are
not supported. Host lookup order in the /etc/nsswitch.conf is ignored during transition.
Configurations that must be manually configured
You must manually configure the following LDAP options on the SVMs:
•
ldap.usermap.attribute.unixaccount
•
ldap.password
•
ldap.usermap.base
•
ldap.ssl.enable
Related tasks
Customizing the transition of 7-Mode configurations on page 66
Related information
NFS management
Network and LIF management
Considerations for transitioning DNS, NIS, and LDAP configurations
You must be aware of how the DNS, NIS, and LDAP configurations in 7-Mode are transitioned and
applied in clustered Data ONTAP.
Considerations for DNS transition
A maximum of six domain names and three name servers for DNS configurations per SVM are
supported in clustered Data ONTAP. If the unique number of domain names or name servers across
7-Mode and target SVM exceed the supported limit, the 7-Mode Transition Tool produces a blocking
error. To continue with the transition, ignore the transition of DNS configuration from the tool.
Note: If you ignore the transition of DNS configuration, you must manually configure it on the
target SVM.
Considerations for NIS transition
•
The length of the NIS domain name on the 7-Mode system must not exceed 64 characters.
•
The nis.servers option on the 7-Mode system must be configured only with IP addresses, and
not an FQDN.
42 | Copy-Free Transition Guide
You must configure the nis.servers option on the 7-Mode system with IP addresses before
transition.
Considerations for LDAP transition
•
If separate base and scope values are specified for user mapping (ldap.usermap.base) and
user password (ldap.base.passwd) lookups in the 7-Mode system, the base and scope values
for only the user password are transitioned.
The base and scope values are used for user mapping and user password lookups in clustered
Data ONTAP, which can cause security issues. You must manually add the base and scope values
for user mapping to the user distinguished name (DN) option in clustered Data ONTAP after
transition, if required.
Considerations for transitioning netgroups and UNIX users and groups
Netgroup configuration is transitioned only if the 7-Mode /etc/netgroup file is less than 5 MB in
size. UNIX users and groups are transitioned only if the total number of UNIX users and groups on
the SVM do not exceed the limits for users and groups in clustered Data ONTAP.
Considerations for netgroups
If the /etc/netgroup file on 7-Mode is greater than 5 MB, the netgroup configuration is not
transitioned. You must perform one of the following actions to continue with the transition:
•
Exclude the transition of netgroups.
Customizing the transition of 7-Mode configurations on page 66
•
Move the netgroup configuration to NIS or LDAP servers before transition.
Considerations for UNIX users and groups
If the total number of transitioning UNIX users and groups exceed the limit of UNIX users and
groups in clustered Data ONTAP, the 7-Mode Transition Tool blocks the transition. You must
perform one of the following actions to continue with the transition:
•
Exclude the transition of UNIX users and groups.
Customizing the transition of 7-Mode configurations on page 66
•
Move the UNIX users and groups to NIS or LDAP servers before transition.
Related information
NFS management
Preparing for NFS transition
If NFS is licensed and NFS service is running on the systems operating in 7-Mode, you must
manually prepare the cluster and target SVMs for transitioning NFS configurations. You must also be
aware of what configurations are transitioned.
Some NFS configurations operating in 7-Mode are not supported in clustered Data ONTAP. Some
configurations are not transitioned by the 7-Mode Transition Tool and must be manually applied to
the SVMs.
Preparing for copy-free transition | 43
Prerequisites for transitioning NFS configurations
NFS configurations are transitioned by the 7-Mode Transition Tool only when certain prerequisites
are met on the 7-Mode system and the cluster. If any of the conditions are not met, the tool does not
transition the configuration.
7-Mode prerequisites
•
NFS must be licensed.
•
If MultiStore is licensed, NFS must be enabled on all the vFiler units.
•
NFS service must be running on the 7-Mode systems during transition.
Even after client access is disconnected and you prepare to start the export phase, the service must
be running on the 7-Mode systems.
•
If you want to transition in-memory export rules, you must add them to the /etc/exports file
before transition.
The 7-Mode Transition Tool transitions only the persistent export rules that are defined in
the /etc/exports file.
Cluster prerequisites
•
NFS must be licensed.
Related information
NetApp Documentation: ONTAP 9
NFS transition: supported and unsupported configurations, and required
manual steps
Some NFS configurations are not transitioned to clustered Data ONTAP because they are not
supported in clustered Data ONTAP, there are functionality differences from 7-Mode, or they must be
manually transitioned. You should verify all of the precheck errors and warning messages to evaluate
the impact of such configurations on transition.
Supported configurations for transition
At a high level, the following NFS configurations are transitioned by the 7-Mode Transition Tool:
•
NFS options:
◦
nfs.udp.xfersize
◦
nfs.v4.id.domain
◦
nfs.v4.acl.max.aces
◦
nfs.tcp.xfersize
◦
nfs.rpcsec.ctx.high
◦
nfs.rpcsec.ctx.idle
◦
nfs.response.trigger
◦
wafl.default_nt_user
◦
nfs.mount_rootonly
44 | Copy-Free Transition Guide
◦
nfs.tcp.enable
◦
nfs.udp.enable
◦
nfs.response.trace
◦
nfs.v4.read_delegation
◦
nfs.v4.write_delegation
◦
nfs.v4.acl.enable
◦
nfs.vstorage.enable
◦
nfs.v3.enable
◦
nfs.v4.enable
•
NFS export rule:
If the export rule is configured with the -actual option, the exported path (alias path) is ignored
and the export rule is configured with the actual path.
•
Export rules with Kerberos security krb5p
See the precheck results for details about these NFS configurations.
Unsupported configurations in clustered Data ONTAP
The following NFS configurations are not supported in clustered Data ONTAP:
•
Subvolume NFS exports other than qtree-level NFS exports
•
WebNFS
•
PC-NFS
•
NFSv2
•
Fencing of NFS clients from one or more file system paths
•
Some NFS options
See the precheck warning messages for a complete list of unsupported options.
Configurations that must be manually transitioned
There are some NFS configurations that are supported in clustered Data ONTAP, but are not
transitioned by the 7-Mode Transition Tool.
The following NFS configurations generate a warning message in the precheck operation, and you
must manually apply the configurations on the SVMs:
•
NFS audit configuration
•
NFS options:
◦
rpc.nsm.tcp.port
◦
rpc.nsm.udp.port
◦
rpc.mountd.tcp.port
◦
rpc.mountd.udp.port
◦
nfs.export.neg.timeout
Preparing for copy-free transition | 45
◦
nfs.export.pos.timeout
◦
nfs.export.harvest.timeout
ONTAP 9 man page: vserver nfs modify
•
Kerberos configuration
Configurations that are functionally different in clustered Data ONTAP
The following NFS configurations are functionally different in clustered Data ONTAP:
•
NFS export rules
•
NFS export access cache
•
NFS diagnostic commands
•
Support for the showmount command
•
NFS Kerberos encryption
•
NLM version support
Related tasks
Customizing the transition of 7-Mode configurations on page 66
Related information
NFS management
How NFS exports are transitioned
You must be aware of how NFS exports are configured on the SVM after transition. You might have
to perform some manual steps if the 7-Mode export configurations are not supported in clustered
Data ONTAP.
You must be aware of the following considerations about NFS exports transition:
•
If the SVM root volume is not exported to allow read-only access to all NFS clients, the 7-Mode
Transition Tool creates a new export policy that allows read-only access for all the NFS clients
and exports the root volume of the SVM with the new export policy.
To ensure that all the transitioned volumes or qtrees are mountable, the root volume of the SVM
must be allowed read-only access for all the NFS clients.
•
When 7-Mode volumes with export configurations that are not supported in clustered Data
ONTAP are transitioned, these volumes are exported to disallow access to all NFS clients.
Export policies for these volumes must be configured manually after transition to provide the
required access permissions.
•
When 7-Mode qtrees with export configurations that are not supported in clustered Data ONTAP
are transitioned, they inherit the export policy of the parent volume.
Export policies for these qtrees must be configured manually after transition to provide the
required access permissions.
•
In clustered Data ONTAP, for an NFS client to mount a qtree, the NFS client must have read-only
permissions at all the parent junction paths up to the SVM's root volume junction path (that is, /).
For NFS clients to mount qtrees, the qtrees must belong to a volume that has read-only
permission. Without the read-only permissions at the volume level, the NFS clients cannot mount
the qtree.
46 | Copy-Free Transition Guide
•
If the same host is specified in the combination of read-only, read-write, and root access
permission lists, you must evaluate the transitioned export rules after transition to determine
appropriate access privilege for the hosts.
NetApp Technical Report 4067: Clustered Data ONTAP Best Practice and NFS Implementation
Guide
Example: Modifying the export policy of a volume to allow access to a qtree
Consider the following export rule configured in the 7-Mode storage system (192.168.26.18)
that allows read/write access to the volume volstd10 and qtree qtree1 for the NFS client
192.168.10.10:
/vol/volstd10/qtree1 -sec=sys,rw=192.168.10.10,nosuid
/vol/volstd10 -sec=sys,rw=192.168.11.11,nosuid
After transition, the export policy of the volume volsdt10 in clustered Data ONTAP is as
shown below:
cluster-01::> export-policy rule show -vserver std_22 -policyname
std_2226 -instance
(vserver export-policy rule show)
Vserver: std_22
Policy Name: std_2226
Rule Index: 1
Access Protocol: any
Client Match Hostname, IP Address, Netgroup, or Domain:
192.168.11.11
RO Access Rule: sys
RW Access Rule: sys
User ID To Which Anonymous Users Are Mapped:65534
Superuser Security Types: none
Honor SetUID Bits in SETATTR: false
Allow Creation of Devices: true
cluster-01::>
After transition, the export policy of the qtree qtree1 in clustered Data ONTAP is as shown
below:
cluster-01::> export-policy rule show -vserver std_22 -policyname
std_2225 -instance
(vserver export-policy rule show)
Vserver:
Policy Name:
Rule Index:
Access Protocol:
Client Match Hostname, IP Address, Netgroup,
192.168.10.10
RO Access Rule:
RW Access Rule:
User ID To Which Anonymous Users Are Mapped:
Superuser Security Types:
Honor SetUID Bits in SETATTR:
Allow Creation of Devices:
cluster-01::>
std_22
std_2225
1
any
or Domain:
sys
sys
65534
none
false
true
For the NFS client 192.168.10.10 to access the qtree, the NFS client 192.168.10.10 must have
read-only access to the qtree's parent volume.
The following output shows that the NFS client is denied access while mounting the qtree:
Preparing for copy-free transition | 47
[root@192.168.10.10 ]# mount 192.168.35.223:/vol/volstd10/qtree1
transition_volume_qtreemount:192.168.35.223:/vol/volstd10/qtree1
failed, reason
given by server: Permission denied [root@192.168.10.10 ]#
You must manually modify the export policy of the volume to provide read-only access to the
NFS client 192.168.10.10.
cluster-01::> export-policy rule create -vserver std_22 -policyname
std_2226 -clientmatch
192.168.10.10 -rorule sys -rwrule never -allow-suid false -allowdev true -superuser none -protocol nfs
(vserver export-policy rule create)
cluster-01::> export-policy rule show -vserver std_22 -policyname
std_2226 -instance
(vserver export-policy rule show)
Vserver:
Policy Name:
Rule Index:
Access Protocol:
Client Match Hostname, IP Address, Netgroup,
192.168.11.11
RO Access Rule:
RW Access Rule:
User ID To Which Anonymous Users Are Mapped:
Superuser Security Types:
Honor SetUID Bits in SETATTR:
Allow Creation of Devices:
std_22
std_2226
1
any
or Domain:
Vserver:
Policy Name:
Rule Index:
Access Protocol:
Client Match Hostname, IP Address, Netgroup,
192.168.10.10
RO Access Rule:
RW Access Rule:
User ID To Which Anonymous Users Are Mapped:
Superuser Security Types:
Honor SetUID Bits in SETATTR:
Allow Creation of Devices:
std_22
std_2226
2
nfs
or Domain:
sys
sys
65534
none
false
true
sys
never
65534
none
false
true
cluster-01::>
Example: How qtree export rules differ in 7-Mode and clustered Data ONTAP
In the 7-Mode storage system, when an NFS client accesses a qtree through the mount point of
its parent volume, the qtree export rules are ignored and the export rules of its parent volume
are in effect. However, in clustered Data ONTAP, qtree export rules are always enforced
whether NFS client mounts to the qtree directly or it accesses the qtree through the mount
point of its parent volume. This example is specifically applicable for NFSv4.
The following is an example of an export rule on the 7-Mode storage system (192.168.26.18):
/vol/volstd10/qtree1 -sec=sys,ro=192.168.10.10,nosuid
/vol/volstd10
-sec=sys,rw=192.168.10.10,nosuid
On the 7-Mode storage system, the NFS client 192.168.10.10 has only read-only access to the
qtree. However, when the client accesses the qtree through the mount point of its parent
volume, the client can write to the qtree because the client has read/write access to the volume.
48 | Copy-Free Transition Guide
[root@192.168.10.10]#
transition_volume
[root@192.168.10.10]#
[root@192.168.10.10]#
[root@192.168.10.10]#
[root@192.168.10.10]#
new_folder
[root@192.168.10.10]#
mount 192.168.26.18:/vol/volstd10
cd transition_volume/qtree1
ls transition_volume/qtree1
mkdir new_folder
ls
In clustered Data ONTAP, the NFS client 192.168.10.10 has only read-only access to the qtree
qtree1 when the client accesses the qtree directly or through the mount point of the qtree's
parent volume.
After transition, you must evaluate the impact of enforcing the NFS export policies, and if
necessary modify the processes to the new way of enforcing NFS export policies in clustered
Data ONTAP.
Related information
NFS management
Preparing for CIFS transition
If CIFS is licensed and CIFS service is running on the 7-Mode systems, you must manually perform
some tasks, such as adding the CIFS license and creating a CIFS server, on the target cluster and
SVMs for transitioning CIFS configurations.
You must also be aware of what configurations are transitioned. Some CIFS configurations operating
in 7-Mode are not supported in clustered Data ONTAP. Some configurations are not transitioned by
the 7-Mode Transition Tool and must be manually applied to the SVMs.
Prerequisites for transitioning CIFS configurations
CIFS configurations are transitioned by the 7-Mode Transition Tool only when certain prerequisites
are met on the 7-Mode system and cluster. If any of the conditions are not met, the tool does not
transition the configuration.
7-Mode prerequisites
•
The CIFS license must be added.
•
If MultiStore license is enabled, CIFS must be added to the list of allowed protocols for the vFiler
unit that owns the transitioning volumes.
•
CIFS must be set up and running during transition.
Even after client access is disconnected and you prepare to start the export phase, the CIFS
service must be running on the 7-Mode systems.
•
The authentication type for CIFS must be Active Directory (AD) or Workgroup.
Cluster prerequisites
•
The CIFS license must be added.
•
The CIFS server must be created on the target SVMs before the SVM provision phase with a new
identity (different from 7-Mode).
•
DNS must be configured for the SVM.
Preparing for copy-free transition | 49
•
•
The CIFS authentication methods that are supported in different Data ONTAP versions are:
◦
Clustered Data ONTAP 8.2.x and 8.3.x supports AD authentication.
◦
ONTAP 9.0 supports AD authentication and Workgroup authentication.
The following table identifies which authentication method must be used on the target SVM:
7-Mode authentication
method
Clustered Data ONTAP
8.2.x and 8.3.x
authentication method
ONTAP 9.0 authentication
method
AD
AD
AD
Workgroup
AD
Workgroup or AD
•
You can transition the CIFS configuration from 7-Mode to clustered Data ONTAP if the AD
domains do not match between the 7-Mode CIFS server and the target SVM CIFS server. The
tool triggers an ignorable blocking error when an AD domain name mismatch is detected. To
proceed with the transition, you can acknowledge the blocking error.
•
The CIFS server must be manually configured before the apply configuration (precutover) phase.
You can create the CIFS server on the SVM in the following two ways:
If you want to…
Do the following…
Transfer or preserve the
CIFS server identity to the
target SVM
◦
You must plan to transition all of the volumes in the source
7-Mode system or vFiler unit in a single project.
This is required because the 7-Mode system loses the
original CIFS server identity after the transition and cannot
serve clients. The maximum number of volumes that can be
transitioned in one project is 160; therefore, to preserve the
CIFS server identity, the 7-Mode system can have a
maximum of 160 volumes and all these volumes must be
transitioned in a single project.
◦
Before the “apply configuration” (precutover) phase, you
must reconfigure the CIFS server on the 7-Mode by using a
temporary CIFS identity.
This allows the original CIFS server identity to be
configured on the SVM. You must ensure that the CIFS
server is running on the 7-Mode system during the “apply
configuration” phase (precutover) operation with the new
temporary identity. This is required to read CIFS
configurations from 7-Mode during precutover.
◦
You must configure the CIFS server on the target SVM with
the original 7-Mode CIFS identity.
After ensuring these conditions, you can perform the precutover
operation. You must then plan to perform the storage cutover
immediately after precutover for enabling client access to the
clustered Data ONTAP volumes.
50 | Copy-Free Transition Guide
If you want to…
Do the following…
Use a new identity
◦
Before the apply configuration (precutover) phase, you must
configure the CIFS server on the target SVM with a new
CIFS identity.
◦
You must ensure that the CIFS server is up and running on
the 7-Mode system during the“apply configuration”
(precutover) phase operation.
This is required to read CIFS configurations from 7-Mode
during “apply configuration” phase (precutover).
After ensuring these conditions, you can perform the precutover
operation. You can then test the SVM configurations and then
plan to perform the storage cutover.
CIFS transition: supported and unsupported configurations, and required
manual steps
Some CIFS configurations are not transitioned to clustered Data ONTAP because either they are not
supported in clustered Data ONTAP or they must be manually transitioned. You should verify all
precheck error and warning messages to evaluate the impact of such configurations on transition.
Configurations that are supported for transition
At a high level, the 7-Mode Transition Tool transitions the following CIFS configurations:
•
CIFS preferred DC configuration
•
User mapping configuration
◦
/etc/usermap.cfg
◦
wafl.nt_admin_priv_map_to_root
•
CIFS local users and groups
•
Symlink and widelink configuration (/etc/symlink.translations)
•
CIFS audit configuration
•
CIFS shares
•
CIFS share ACLs
•
CIFS home directory configuration
•
CIFS options:
•
◦
cifs.gpo.enable
◦
cifs.smb2.enable
◦
cifs.smb2.signing.required
◦
cifs.wins_servers
◦
cifs.grant_implicit_exe_perms
◦
cifs.restrict_anonymous
FPolicy native file blocking configuration
Preparing for copy-free transition | 51
See the precheck results for details about these CIFS configurations.
Configurations that are not supported in clustered Data ONTAP
The following 7-Mode configurations are not supported in clustered Data ONTAP. Therefore, these
configurations cannot be transitioned.
•
NT4, and password authentication types
•
Separate options for SMB1 and SMB2 signing
•
CIFS statistics on a per-client basis
•
SMB2 client for communicating with external servers, such as domain controllers
•
Authentication for clients earlier than Windows NT
•
Auditing of account management events for local users and groups
•
Usermap entries with IP addresses, host names, network names, or network names with subnet
specified in dotted notation
•
CIFS shares with access restriction for machine accounts
Machine accounts can access all shares after transition.
Configurations that must be manually transitioned
Some CIFS configurations are supported in clustered Data ONTAP, but are not transitioned by 7Mode Transition Tool.
The following CIFS configurations generate a warning message in the precheck. You must manually
apply these configurations on the SVMs:
•
Antivirus settings
•
FPolicy configuration
7-Mode FPolicy and antivirus servers do not work with clustered Data ONTAP. You must contact
the server vendors for upgrading these servers. However, you must not decommission the 7-Mode
FPolicy and antivirus servers until you commit the transition. These are required in case you
decide to roll back the transition.
•
BranchCache configuration
•
Character mapping configuration (charmap)
•
Forcegroup attribute of CIFS shares to create files with a specified UNIX group as owning group
•
Maxusers attribute of CIFS shares to specify the maximum number of simultaneous connections
allowed to a 7-Mode CIFS share
•
Storage-Level Access Guard (SLAG) configurations
•
Share-level ACLs with UNIX-style permission
•
Share ACLs for UNIX users and groups
•
LAN Manager authentication level
•
NetBIOS aliases
•
CIFS search domains
•
Some CIFS options
See the precheck results for details about these options.
52 | Copy-Free Transition Guide
Related tasks
Customizing the transition of 7-Mode configurations on page 66
Considerations for transitioning CIFS local users and groups
You must be aware of the considerations for running the transition operations when migrating CIFS
local users and groups.
•
Transition of CIFS data-serving volumes from a 7-Mode controller or a vFiler unit that has local
users and groups to an SVM that has non-BUILTIN CIFS local users and groups is not supported.
The SVM must have only BUILTIN CIFS local users and groups for transition.
•
You must ensure that the number of local users and groups in 7-Mode does not exceed the local
users and groups limit for ONTAP.
You must contact technical support if the number of local users and groups in 7-Mode exceeds the
limit defined in ONTAP.
•
A local user account with an empty password or local user accounts with passwords containing
more than 14 characters on the 7-Mode system are transitioned to ONTAP with the password
cifsUser@1.
After the transition is complete, you can access these users from the Windows system by using
the password cifsUser@1. You must then manually change the password for such CIFS local
users on the SVM by using the following command:
cifs users-and-groups local-user set-password -vserver svm_name -username user_name
.
•
The SVM to which the local users and groups are transitioned must have a data LIF.
•
If a local group has multiple member system identifiers (SIDs) mapped to a single domain user or
group on the 7-Mode system, the 7-Mode Transition Tool blocks the transition of local users and
groups to ONTAP during the precheck phase.
If you see this error during the precheck phase, you must manually remove the additional SIDs
that are mapped to a single domain user or group on the 7-Mode system. You must then rerun the
precheck operation with only a single SID mapped to the domain user or group.
Related information
CIFS management
Preparing for SAN transition
Before transitioning a SAN environment, you must understand what configurations are supported for
SAN transition, create SAN LIFs on the SVMs, and prepare the SAN hosts for transition.
Creating SAN LIFs before transition
Because FC and iSCSI LIFs are not transitioned by the 7-Mode Transition Tool, you must create
these LIFs on the SVMs before transition. You must configure SAN LIFs on both the node that owns
the LUN and the node's HA partner.
Before you begin
The required SAN (FC or iSCSI) license must be added to the cluster.
Preparing for copy-free transition | 53
About this task
For redundancy, you must create SAN LIFs on both the node hosting the LUNs as well as its HA
partner.
Steps
1. Create an FC or iSCSI LIF on the target node to which the LUNs are transitioned, depending on
the protocol used.
If you want to reuse the 7-Mode IP address for iSCSI LIFs, you must create the LIFs in
administrative down state. You can bring these LIFs to the administrative up state after the
cutover operation.
ONTAP 9 man page: network interface create
2. Create a LIF on the HA partner of the node.
3. Verify that you have set up your LIFs correctly.
ONTAP 9 man page: network interface show
Related information
SAN administration
Configuring zones by using the FC zone plan
Before transitioning a SAN FC environment, you must configure zones by using the FC zone planner
to group the initiator hosts and targets.
Before you begin
•
The FC zone planner must be generated by using the Collect and Access feature of the 7-Mode
Transition Tool
•
The FC zone script file must be accessible.
Steps
1. If there are any changes to the igroup configurations on the 7-Mode systems, modify and
regenerate the FC zone plan.
Generating an assessment report by adding systems to the 7-Mode Transition Tool on page 12
2. Log in to the CLI of the switch.
3. Copy and execute the required zone commands one at a time.
Example
The following example runs the zone commands on the switch:
switch1:admin>config terminal
# Enable NPIV feature
feature npiv
zone name auto_transition_igroup_d31_194bf3 vsan 10
member pwwn 21:00:00:c0:dd:19:4b:f3
member pwwn 20:07:00:a0:98:32:99:07
member pwwn 20:09:00:a0:98:32:99:07
.......
.......
.......
copy running-config startup-config
54 | Copy-Free Transition Guide
4. Verify the data access from the cluster by using the test initiator hosts.
5. After the verification is complete, perform the following steps:
a. Disconnect the test initiator hosts.
b. Remove the zone configuration.
Preparing SAN hosts for transition
Before transitioning a SAN environment, you must perform some manual steps to prepare the SAN
hosts for transition.
Before you begin
You must have generated the inventory workbook for the SAN hosts by using the Inventory Collect
Tool.
Host and storage transition information collection
Steps
1. Verify that the host is supported for transition.
NetApp Interoperability Matrix Tool
2. Perform the pretransition steps on the host.
SAN host transition and remediation
SAN transition: supported and unsupported configurations, and required
manual steps
You must be aware of the SAN configurations that are transitioned by the 7-Mode Transition Tool.
You should also be aware of the 7-Mode SAN features that are not supported in clustered Data
ONTAP, so that you can take any necessary actions before the transition.
You should verify all of the precheck error and warning messages to evaluate the impact of such
configurations on transition.
Configurations that are transitioned
The following SAN configurations are transitioned by 7-Mode Transition Tool:
•
FC and iSCSI services
•
igroups and LUN maps
Note: The 7-Mode igroups that are not mapped to any LUNs are not transitioned to the target
SVMs.
Unsupported configurations in clustered Data ONTAP
The unsupported configurations in clustered Data ONTAP are as follows:
•
Snapshot copy-backed LUN clones
Snapshot copy-backed LUN clones present in the Snapshot copies are not supported for any
restore operation. These LUNs are not accessible in clustered Data ONTAP. You must split or
delete the 7-Mode Snapshot copy backed LUN clones before transition.
•
LUNs with ostype of vld, image, or any user-defined string
You must either change the ostype of such LUNs or delete the LUNs before transition.
Preparing for copy-free transition | 55
•
LUN clone split
You must either wait for the active LUN clone split operations to complete or abort the LUN
clone split and delete the LUN before transition.
The following 7-Mode features enable you to continue with the transition process, but are not
supported in clustered Data ONTAP:
•
The lun share command
Sharing a LUN over NAS protocols
•
SnapValidator
Configurations that must be manually transitioned
The following configurations must be transitioned manually:
•
SAN LIFs
You must manually create the LIFs before transition.
•
Portsets
You must manually configure igroups that are bound to a portset after transition.
•
iSCSI access list information
•
iSNS configuration
•
iSCSI CHAP and RADIUS configurations
Related information
NFS management
Network and LIF management
Space considerations when transitioning SAN volumes
You must ensure that sufficient space is available in the volumes during transition. In addition to the
space required for storing data and Snapshot copies, the transition process also requires 1 MB of
space per LUN for updating certain filesystem metadata.
You can use the df -h command on the 7-Mode volume to verify whether free space of 1 MB per
LUN is available in the volume. The volume should also have free space equivalent to the amount of
data that is expected to be written to the volume before the hosts are quiesced. If the volume does not
have sufficient free space available, the required amount of space must be added to the 7-Mode
volume.
If transition fails during the import phase due to lack of space on the volume, the following EMS
message is generated: LUN.vol.proc.fail.no.space: Processing for LUNs in volume
vol_name failed due to lack of space.
If there are volumes containing space-reserved LUNs, growing the volume by 1MB per LUN might
not provide sufficient space. In such cases, the amount of space that has to be added is the size of the
Snapshot reserve for the volume. After space is added to the volume, you can use the lun
transition start command to transition the LUNs.
Related tasks
Recovering from a failed LUN transition on page 97
Related information
NetApp Documentation: ONTAP 9
NetApp Technical Report 3784: Data Protection Handbook
56 | Copy-Free Transition Guide
Preparing data protection features for transition
You must perform some manual steps for transitioning 7-Mode SnapMirror relationships. You must
also be aware of the data protection relationships that are supported and unsupported for transition.
Preparing the cluster for transitioning volume SnapMirror relationships
For transitioning 7-Mode volume SnapMirror relationships, you must add the SnapMirror license to
the source and destination clusters. You must also create a cluster peer relationship between the
clusters to which the primary and secondary volumes of the SnapMirror relationships are transitioned
and create the SnapMirror schedules.
Before you begin
You must have recorded the SnapMirror schedules defined in the /etc/snapmirror.conf file of
the 7-Mode secondary system.
Steps
1. Add the SnapMirror license on both the source and destination clusters:
system license add license_code
ONTAP 9 man page: system license add
2. From each cluster, create the cluster peer relationship.
Cluster peering express configuration
3. Create schedules on the secondary SVMs that match the schedules in the 7-Mode secondary
system.
ONTAP 9 man page: job schedule cron create
Data protection transition: supported and unsupported configurations
You can transition a volume that is part of a SnapMirror relationship. However, some data protection
and disaster recovery configurations are not supported for transition and therefore you have to
perform some manual steps for transitioning these configurations.
Supported configurations
You can transition volume SnapMirror relationships by using the 7-Mode Transition Tool. You can
perform a copy-free transition of primary and secondary HA pairs. You must then manually set up
the volume SnapMirror relationships after transition.
Transitioning a SnapMirror relationship on page 88
Unsupported configurations
•
SnapVault relationships
Volumes that are the source of a SnapVault relationship can be migrated; however, the SnapVault
relationship is not transitioned. A volume that is the destination of a SnapVault relationship can
be migrated only after the SnapVault backups are stopped.
NetApp Technical Report 4052: Successfully Transitioning to Clustered Data ONTAP (Data
ONTAP 8.2.x and 8.3)
•
Qtree SnapMirror relationships
Volumes with qtrees that are the source of a qtree SnapMirror relationship can be transitioned, but
the qtree SnapMirror relationship is not transitioned. A volume with a qtree that is the destination
Preparing for copy-free transition | 57
of a qtree SnapMirror relationship can be migrated only after the qtree SnapMirror relationship is
broken.
•
Disaster recovery vFiler unit
Volumes that are the source of a disaster recovery vFiler unit can be migrated; however, the
disaster recovery vFiler unit is not transitioned. A volume that is the destination of a disaster
recovery vFiler unit can be migrated only after the disaster recovery relationship is deleted.
•
NDMP configuration
After the transition is complete, you must manually set up backup policies for the transitioned
volumes in clustered Data ONTAP.
Data protection using tape backup
•
Synchronous SnapMirror relationships
This feature is not supported in clustered Data ONTAP; however, the volumes that are part of the
relationship can be transitioned.
Related tasks
Customizing the transition of 7-Mode configurations on page 66
58
Transitioning 7-Mode aggregates using copy-free
transition
The copy-free transition workflow involves planning a project, applying 7-Mode configurations to
the SVMs, exporting the 7-Mode system information and halting the 7-Mode system, manually
cabling the disk shelves to cluster nodes, and importing the 7-Mode data and configurations.
Before you begin
You must have prepared the 7-Mode system and the cluster for copy-free transition.
About this task
The storage cutover time can be 4-8 hours or less. The cutover time includes the time taken by the
tool to perform two automated operations—the export and halt and import operations— as well as
the time taken for manually cabling the disk shelves to the new controllers.
The export and import operations take about 2 hours or less. Cabling can take 2-6 hours or less.
Steps
1. Planning a copy-free transition project on page 59
Transitioning 7-Mode aggregates using copy-free transition | 59
Planning a copy-free transition project involves selecting the source 7-Mode controllers and target
cluster nodes, mapping 7-Mode volumes to a Storage Virtual Machine (SVM), selecting the LIFs
to be transitioned, and running prechecks.
2. Applying SVM configurations on page 73
You must manually apply some configurations before the SVM provision phase. You can then
apply all configurations that are defined in the 7-Mode controller (files in the /etc directory) or at
the vFiler unit level to the mapped SVMs by using the tool.
3. Verifying that 7-Mode systems are ready for cutover on page 74
Before disconnecting client access, you can verify the readiness of the 7-Mode system for storage
cutover, such as verifying whether the SP or RLM is configured on the 7-Mode system and
whether the disk shelves, aggregates, and volumes are ready for transition. You can manually fix
any issues before the export operation, thereby reducing the downtime.
4. Exporting storage configurations and halting 7-Mode systems on page 75
The cutover window for the transition starts from the export phase. In this phase, the tool collects
system information, disk shelf details, and storage configurations from the 7-Mode systems, and
then halts the 7-Mode storage systems.
5. Disconnecting disk shelves from the 7-Mode system and connecting to cluster nodes on page 76
Cabling the 7-Mode disk shelves to the target cluster nodes is a manual process. After cabling the
disk shelves, it is a best practice to verify the cabling by using Config Advisor. You can then
verify the cabling by using the 7-Mode Transition Tool. The tool performs only a subset of the
checks that are performed by Config Advisor.
6. Importing 7-Mode data to ONTAP on page 78
After verifying the cabling and resolving any issues, you can run the import operation. In this
phase, the disk ownership is assigned to the mapped cluster nodes, and the 7-Mode aggregates,
volumes, and LUNs are converted to the ONTAP format. All the volume-level and LUN-level
configurations are also applied.
Planning a copy-free transition project
Planning a copy-free transition project involves selecting the source 7-Mode controllers and target
cluster nodes, mapping 7-Mode volumes to a Storage Virtual Machine (SVM), selecting the LIFs to
be transitioned, and running prechecks.
About this task
You can create multiple projects with the same target cluster HA pair nodes. You can then run
prechecks and apply the SVM configurations on all these projects. However, only one project can be
in the critical section window at a given time. A project is in the critical section window if the project
is in any of the phases from export to commit, or if a rollback operation has been initiated for the
project. You can proceed with the export and halt operation for another project only after the commit
or rollback operation is completed for the project in the critical section window.
Steps
1.
2.
3.
4.
5.
6.
7.
8.
Completing the copy-free transition planning worksheet on page 60
Adding controllers and clusters on page 63
Creating a copy-free transition project on page 63
Selecting the target cluster nodes for transition on page 64
Mapping SVMs and volumes on page 64
Selecting LIFs for transition on page 66
Customizing the transition of 7-Mode configurations on page 66
Running prechecks on page 71
60 | Copy-Free Transition Guide
Copy-free transition project planning worksheets
You can use the copy-free transition planning worksheets to record information about node mapping,
SVM mapping, volume mapping, and LIFs to transition. The worksheets are useful when creating a
transition project by using the 7-Mode Transition Tool. You should be aware of the guidelines for
completing the worksheets.
You can follow these guidelines to complete the worksheets:
•
Map each vFiler unit to an SVM.
If there are no vFiler units in the 7-Mode controller, map the controller to a single SVM.
•
Record the 7-Mode volume name and the corresponding clustered Data ONTAP volume name.
The clustered Data ONTAP volume name might be different from the 7-Mode volume name.
•
Identify the LIFs to be configured on each SVM.
The IP addresses for the LIFs can either be existing on the 7-Mode system or can be new LIFs.
Node mapping
Mapped cluster node
7-Mode controller
SVM and volume mapping
7-Mode
controller
vFiler unit or
controller
Mapped SVM
7-Mode volume
SVM volume
Transitioning 7-Mode aggregates using copy-free transition | 61
LIF mapping (7-Mode IP addresses)
7-Mode
controller
vFiler
unit or
controller
Mapped
SVM
7-Mode
IP
address
Netmask
Default
gateway
Home
node
Home
port
LIF mapping (new LIFs)
SVM
New IP address
Netmask
Default
gateway
Home node
Home port
Example
The following table shows an example of completed worksheets for a 7-Mode HA pair with
the controllers hostA_7mode and hostB_7mode.
Node mapping
7-Mode controller
Mapped cluster node
hostA_7mode
cluster1_01
hostB_7mode
cluster1_02
SVM and volume mapping
62 | Copy-Free Transition Guide
7-Mode
controller
Mapped
cluster node
vFiler unit or
controller
Mapped
SVM
7-Mode
volume
SVM
volume
hostA_7mod
e
cluster1_01
vfilerA
svm1
volA
volA
volB
volB
vol1
vol_nfs
vol2
vol_cifs
vol3
vol3
vol4
vol4
vol5
vol5
vol6
vol6
vfilerB
hostB_7mod
e
cluster1_02
svm2
Not applicable
svm3
LIF mapping (7-Mode IP addresses)
7Mode
contr
oller
vFile
r
unit
or
contr
oller
Mapp
ed
SVM
Existing 7Mode IP
Netmask
Default
gateway
Home
node
Hom
e
port
hostA
_7mo
de
vfiler
A
svm1
192.0.2.129
255.255.255.128
192.40.0.1
cluster
1_01
e0a
192.0.2.135
255.255.255.128
192.40.0.1
cluster
1_02
e0b
192.0.2.110
255.255.255.128
192.40.0.1
cluster
1_01
e0c
192.0.2.111
255.255.255.128
192.40.0.1
cluster
1_02
e0d
hostB
_7mo
de
vfiler
B
svm2
Not
appli
cable
svm3
-
LIF mapping (new LIFs)
SVM
New IP
address
svm1
-
Netmask
Default
gateway
Home node
Home
port
192.0.2.130
255.255.255.128
192.40.0.1
cluster1_01
e1c
192.0.2.131
255.255.255.128
192.40.0.1
cluster1_02
e1d
192.0.2.136
255.255.255.128
192.40.0.1
cluster1_01
e0c
192.0.2.137
255.255.255.128
192.40.0.1
cluster1_02
e0d
svm2
svm3
Transitioning 7-Mode aggregates using copy-free transition | 63
Adding controllers and clusters
Before you start the transition, you must add the 7-Mode controllers, including both nodes of a 7Mode HA pair, and the clusters that are required for the transition. You should add the clusters using
the cluster-management interface.
About this task
•
For a copy-free transition, you must add the cluster, and not the cluster nodes that are the target of
transition.
•
The 7-Mode controllers and clusters information that you provide is not persistent.
If the 7-Mode Transition Tool service is restarted, the tool prompts in the project dashboard for
information about controllers and cluster that are part of active projects.
Steps
1. From the top pane, click Storage Systems.
2. In the Hostname field, enter the FQDN or IP address of the 7-Mode controller or the clustered
Data ONTAP system.
For a cluster, you can specify the IP address or FQDN of the cluster-management interface. For a
7-Mode controller, you must specify the IP address of the default vFiler unit, because the IP
addresses of individual vFiler units are not accepted.
3. Enter the administrator credentials for the specified host, and then click Add.
The 7-Mode controllers are added to the “7-Mode Controllers” table and clusters are added to the
“Clustered Data ONTAP Systems” table.
4. Repeat Steps 2 and 3 to add all of the controllers and clusters that you require for the transition.
5. If the Status column indicates that the credentials of the system are missing or the credentials
have changed from what was initially entered in the tool, click the
credentials again.
icon, and then enter the
6. Click Next.
The Select Source Systems screen is displayed.
Creating a copy-free transition project
The first step in planning a transition project is to select the source 7-Mode HA pair from which you
want to transition the disk shelves, aggregates, volumes, and configurations, and then create a
transition project.
Before you begin
•
The 7-Mode controllers in the HA pair must be running a supported Data ONTAP version on a
platform that is supported for a copy-free transition.
NetApp Interoperability Matrix Tool
•
Both controllers in the HA configuration must be healthy.
Steps
1. Select the Copy-Free Transition migration method from the homepage and click Start
Planning.
64 | Copy-Free Transition Guide
If the controller and cluster required for a new project are not added, you can enter the details in
the Enter Device Credentials pane.
2. Select the source 7-Mode HA pair that you want to transition.
3. Click Create Project.
a. In the Project Details window, provide a name for the project.
b. Select a project group to which the project should be added.
You can either create a new project group or add the project to the default group.
Creating a project group enables you to group and monitor related projects.
c. Click Save.
The Select Target Cluster screen is displayed.
Selecting the target cluster nodes for transition
You can select the target cluster HA pair and map each 7-Mode controller in the HA pair to a
corresponding target cluster node. The mapped node specifies the cluster node to which the disk
shelves from the corresponding 7-Mode controller must be connected.
Before you begin
The target cluster must be running Data ONTAP 8.3.2 or later.
About this task
You can transition the 7-Mode disk shelves to a target HA pair that has preexisting data aggregates
and volumes.
For a two-node cluster, you must have a data aggregate to host the root volumes of the target SVMs.
For a cluster with four or more nodes, the root volumes of the SVMs can be hosted either on the
target nodes of the transition or on other nodes in the cluster.
Steps
1. Select the target HA pair to which the 7-Mode disk shelves must be connected.
The tool automatically maps each 7-Mode storage system to a target cluster node.
Note: The disk and aggregate ownership from each 7-Mode controller is transferred to its
corresponding mapped target cluster node during the import phase.
2. Optional: Click Swap Node Mapping to change the automatic assignment of source-to-target
node mapping.
3. Click Save and Continue.
The SVM and Volume Mapping screen is displayed.
Mapping SVMs and volumes
You should map each 7-Mode controller in the HA pair to a target SVM. If you have vFiler units, you
should select a target SVM for each vFiler unit. The volumes from the 7-Mode controller or vFiler
unit are transitioned to the mapped SVM.
Before you begin
You must have created the SVMs on the target cluster.
Cluster management using System Manager
Transitioning 7-Mode aggregates using copy-free transition | 65
System administration
About this task
A vFiler unit can be mapped only to a single SVM. Volumes from any other 7-Mode controller or
vFiler unit cannot be transitioned to a mapped SVM.
Steps
1. In the SVM and Volume Mapping tab, select the target SVM to which you want to transition the
volumes from each 7-Mode controller or vFiler unit.
The target SVM can be in the default or non-default IPspace.
2. Depending on whether you want to apply the same junction path policy for the volumes in all the
SVMs or a different junction path policy for the volumes in each SVM, choose one of the
following actions:
If you want to…
Then…
Apply the same junction path
policy to all the SVMs
a.
Click Apply.
b.
Select an option for the junction path policy.
c.
Click OK.
Specify the junction path
policy for each SVM
Select the junction path policy from the drop-down list for each target
SVM.
The junction path policy specifies the path with which the target clustered Data ONTAP volumes
must be mounted for client access. You can add one of the following values for the junction path
policy:
Preserve 7-Mode mount paths
Retains the same junction paths as that being used on the source 7-Mode volumes and the
volumes are mounted with junction paths in the format /vol/source_volume_name
after transition.
Use clustered Data ONTAP volume name
All the target clustered Data ONTAP volumes are mounted with junction paths with the
clustered Data ONTAP volume name in the format /target_volume_name after
transition.
Use 7-Mode volume name
All the target clustered Data ONTAP volumes are mounted with junction paths with the 7Mode volume name in the format /source_volume_name after transition.
3. Optional: Click
to modify the name of the target clustered Data ONTAP volume.
By default, the target clustered Data ONTAP volume has the same name as the 7-Mode volume. If
a volume with the same name as the 7-Mode volume already exists on the SVM, the target
volume is automatically assigned a new name.
4. Click Save Mapping for each mapped SVM.
5. Click Next.
The Networking screen is displayed.
66 | Copy-Free Transition Guide
Selecting LIFs for transition
You can optionally specify the LIFs that you want to configure on the SVMs after transition. These
LIFs can be existing IP addresses on the 7-Mode systems or they can be new LIFs. Only NAS LIFs
are transitioned. FC and iSCSI LIFs must be manually configured before the SVM provision phase.
About this task
The LIFs that are selected for transition are configured on the SVMs during the SVM provision phase
in the following ways:
•
Existing 7-Mode IP addresses that are selected for transition are created in the administrative
down state.
These IP addresses can continue to serve data in 7-Mode until the cutover starts. During the
import phase, these IP addresses are configured in the administrative up state.
•
New IP addresses are created in the administrative up state.
You can use these LIFs to test the connectivity of the SVMs to the name servers after the SVM
provision phase.
Steps
1. In the LIF configuration tab, choose one of the following options:
If you want to transition...
Then...
An existing IP address on the
7-Mode system
a.
Click Select 7-Mode LIF.
b.
Select the IP address that you want to transition, and then specify the
target SVM and other network parameters.
c.
Click Save.
a.
Click Add New LIF.
b.
Specify the IP address that you want to configure, the target SVM,
and other network parameters.
c.
Click Save.
A new IP address
Note: The target ports must be in the same IPspace as the target SVM.
2. Click Next.
The Plan Configuration tab is displayed.
Customizing the transition of 7-Mode configurations
When planning the transition of configurations from 7-Mode to clustered Data ONTAP, you can
customize the configuration transition in two ways. Firstly, you can ignore or skip the transition of
one or more configurations. Secondly, you can consolidate the 7-Mode NFS export rules, and reuse
an existing NFS export policy and Snapshot policy on the target SVM.
About this task
The 7-Mode Transition Tool does not perform prechecks for the configuration that is excluded.
By default, all 7-Mode configurations are selected for transition.
Transitioning 7-Mode aggregates using copy-free transition | 67
It is a best practice to run the prechecks with all configurations first, and then exclude one or more
configurations in the subsequent run of the prechecks. This helps you to understand which
configurations are excluded from transition and which prechecks are skipped subsequently.
Steps
1. From the Plan Configuration page, select the Select Target SVM pane.
2. Select the following options from the SVM Configuration pane.:
•
For excluding the transition of configurations, clear the check box for those configurations.
•
For consolidating similar 7-Mode NFS export rules to a single export policy in clustered Data
ONTAP, which can then be applied to the transitioned volume or qtree, select the Consolidate
NFS Export Policies on 7-Mode check box.
•
For reusing an existing NFS export policy on the SVM that matches the export policy that will
be created by the tool, which can be applied to the transitioned volumes or qtrees, select the
Reuse Export Policies of SVM check box.
•
For consolidating similar 7-Mode Snapshot schedules to a single Snapshot policy in clustered
Data ONTAP, which can then be applied to the transitioned volume, select the Consolidate 7Mode Snapshot Policies check box.
•
For reusing an existing Snapshot policy on the SVM that matches the Snapshot policy that
will be created by the tool, which can be applied to the transitioned volumes, select the Reuse
Snapshot Policies of SVM check box.
3. Repeat steps 1 and 2 for each target SVM.
4. Click Save and go to Dashboard.
Related concepts
NFS transition: supported and unsupported configurations, and required manual steps on page 43
CIFS transition: supported and unsupported configurations, and required manual steps on page 50
Data protection transition: supported and unsupported configurations on page 56
Name services transition: supported and unsupported configurations, and required manual steps on
page 40
Examples of consolidating NFS export rules and Snapshot schedules for transition
You might want to review examples of how similar 7-Mode export rules and 7-Mode Snapshot
schedules are consolidated to a single NFS export policy and a single Snapshot policy in clustered
Data ONTAP. You might also want to understand how the consolidated policies are assigned to the
transitioned volumes or qtrees with or without reusing a matching existing policy on the target SVM.
Example of consolidating NFS export rules for transition
NFS export rules in 7-Mode and clustered Data ONTAP before transition
7-Mode export rules
/vol/vol1
/vol/vol2
/vol/vol3
-sec=sys,rw,nosuid
-sec=sys,rw,nosuid
-sec=sys,rw,nosuid
Export policies existing in clustered Data ONTAP
68 | Copy-Free Transition Guide
cluster-2::> vserver export-policy show -vserver vs1
Vserver
Policy Name
--------------- ------------------vs1
default
vs1
export_policy_1
The existing export policy export_policy_1 has the following export rule:
cluster-2::> vserver export-policy rule show -vserver vs1 -policyname
export_policy_1
Policy
Rule
Access
Client
RO
Vserver
Name
Index
Protocol Match
Rule
------------ --------------- ------ -------- --------------------- --------vs1
export_policy_1 1
nfs
0.0.0.0/0
sys
Export policies in clustered Data ONTAP after transition with consolidation (no reuse)
Volumes vol1, vol2, and vol3 have similar export rules in 7-Mode; therefore, a new
consolidated export policy, transition_export_policy_1, is assigned to these volumes after
transition:
cluster-2::> vserver export-policy show -vserver vs1
Vserver
Policy Name
--------------- ------------------vs1
default
vs1
export_policy_1
vs1
transition_export_policy_1
3 entries were displayed.
cluster-2::> vserver export-policy rule show -vserver vs1 -policyname
transition_export_policy_1
Policy
Rule
Access
Client
RO
Vserver
Name
Index
Protocol Match
Rule
------------ --------------- ------ -------- --------------------- --------vs1
transition_export_policy_1
1
nfs
0.0.0.0/0
sys
cluster-2::> volume show -vserver vs1 -volume vol1,vol2,vol3 fields policy
vserver volume policy
------- ------ -------------------------vs1
vol1
transition_export_policy_1
vs1
vol2
transition_export_policy_1
vs1
vol3
transition_export_policy_1
3 entries were displayed.
Export policies in clustered Data ONTAP after transition with consolidation and reuse
Volumes vol1, vol2, and vol3 have similar export rules in 7-Mode; therefore, a consolidated
export policy is assigned to these volumes after transition. The export policy, export_policy_1,
which matches the 7-Mode export rules, already exists on the SVM. Therefore, the policy is
applied to these volumes:
cluster-2::> vserver export-policy show -vserver vs1
Vserver
Policy Name
--------------- ------------------vs1
default
vs1
export_policy_1
2 entries were displayed.
Transitioning 7-Mode aggregates using copy-free transition | 69
cluster-2::> vserver export-policy rule show -vserver vs1 policyname export_policy_1
Policy
Rule
Access
Client
RO
Vserver
Name
Index
Protocol Match
Rule
------------ --------------- ------ -------- ----------------------------vs1
export_policy_1 1
nfs
0.0.0.0/0
sys
cluster-2::> volume show -vserver vs1 -volume vol1,vol2,vol3 fields policy
vserver volume policy
------- ------ -------------------------vs1
vol1
export_policy_1
vs1
vol2
export_policy_1
vs1
vol3
export_policy_1
3 entries were displayed.
Example of consolidating Snapshot policies for transition
Snapshot schedules in 7-Mode and clustered Data ONTAP before transition
7-Mode schedule
7-Mode volume
7-Mode Snapshot schedule
vol1
0 2 4@8,12,16,20 (weekly Snapshot copies: 0, daily
Snapshot copies: 2, hourly Snapshot copies: 6 at 2, 4,
8, 12, 16, 20 hours)
vol2
0 2 4@8,12,16,20
vol3
0 2 4@8,12,16,20
vol4
1 2 3@8,12,16 (weekly Snapshot copies: 1, daily
Snapshot copies: 2, hourly Snapshot copies: 3 at
8,12,16 hours)
vol5
2 2 3@8,12,16 (weekly Snapshot copies: 2, daily
Snapshot copies: 2, hourly Snapshot copies: 3 at
8,12,16 hours)
Snapshot policies existing in clustered Data ONTAP
Snapshot policy name
Policy details
ScheduleWeekly
Weekly, count: 1
ScheduleDailyHourly4
Schedule details
ScheduleHourly1
•
Schedule1: daily, count1: 2
•
Schedule2: hourly, count2: 4 every 8, 12, 16, 20
hours
Hourly at 8, 12, 16, 20 hours, count: 4
Snapshot policy in clustered Data ONTAP after transition with consolidation (no reuse)
70 | Copy-Free Transition Guide
7-Mode
volume
7-Mode Snapshot
schedule
Snapshot policy in clustered Data ONTAP
vol1
0 2 4@8,12,16,20
(weekly Snapshot
copies: 0, daily
Snapshot copies: 2,
hourly Snapshot
copies: 4 at 8, 12, 16,
20 hours)
Consolidated policy for vol1, vol2, and vol3
vol2
0 2 4@8,12,16,20
vol3
0 2 4@8,12,16,20
vol4
1 2 3@8,12,16
(weekly Snapshot
copies: 1, daily
Snapshot copies: 2,
hourly Snapshot
copies: 3 at 8,12,16
hours)
vol5
2 2 3@8,12,16
(weekly Snapshot
copies: 2, daily
Snapshot copies: 2,
hourly Snapshot
copies: 3 at 8,12,16
hours)
•
Name: transition_snapshot_policy_0
•
Schedule details
◦
Schedule1: daily, count1: 2
◦
Schedule2: hourly, count2: 4 every 8, 12,
16, 20 hours
•
Name: transition_snapshot_policy_1
•
Schedule details
◦
Schedule1: weekly, count1: 1
◦
Schedule2: daily, count2: 2
◦
Schedule3: hourly, count3: 3 every 8,12,16
hours
•
Name: transition_snapshot_policy_2
•
Schedule details
◦
Schedule1: weekly, count1: 2
◦
Schedule2: daily, count2: 2
◦
Schedule3: hourly, count3: 3 every 8,12,16
hours
Snapshot policy in clustered Data ONTAP after transition with consolidation and reuse
7-Mode
volume
7-Mode Snapshot
schedule
Snapshot policy in clustered Data ONTAP
vol1
0 2 4@8,12,16,20
(weekly Snapshot
copies: 0, daily
Snapshot copies: 2,
hourly Snapshot
copies: 4 at 2, 4, 8, 12,
16, 20 hours)
Consolidated policy for vol1, vol2, and vol3 for
which the existing clustered Data ONTAP policy is
reused
Name: ScheduleDailyHourly4
vol2
0 2 4@8,12,16,20
vol3
0 2 4@8,12,16,20
Transitioning 7-Mode aggregates using copy-free transition | 71
7-Mode
volume
7-Mode Snapshot
schedule
Snapshot policy in clustered Data ONTAP
vol4
1 2 3@8,12,16
(weekly Snapshot
copies: 1, daily
Snapshot copies: 2,
hourly Snapshot
copies: 3 at 8,12,16
hours)
•
Name: transition_snapshot_policy_1
•
Schedule details
vol5
2 2 3@8,12,16
(weekly Snapshot
copies: 2, daily
Snapshot copies: 2,
hourly Snapshot
copies: 3 at 8,12,16
hours)
◦
Schedule1: weekly, count1: 1
◦
Schedule2: daily, count2: 2
◦
Schedule3: hourly, count3: 3 every 8,12,16
hours
•
Name: transition_snapshot_policy_2
•
Schedule details
◦
Schedule1: weekly, count1: 2
◦
Schedule2: daily, count2: 2
◦
Schedule3: hourly, count3: 3 every 8,12,16
hours
Running prechecks
You can run prechecks to identify any issues before you start a transition. Prechecks verify that the 7Mode sources, clustered Data ONTAP targets, and configurations are valid for your transition. You
can run prechecks any number of times.
About this task
The prechecks run more than 200 different checks. For example, the tool checks for items such as if
volumes are online and network access exists between the systems.
Steps
1. From Dashboard, select the project for which you want to run the prechecks.
2. Click Run Prechecks.
After the prechecks are complete, the result summary is displayed in the dialog box.
Note: The prechecks usually take only a few minutes to run, but the duration of the precheck
phase depends on the number and type of errors or warnings that you resolve.
3. Choose an option under Apply Type Filter to filter the results:
•
To view all messages related to security, select Error, Warning, Informational, and Security
Only.
•
To view all error messages related to security, select Error and Security Only.
•
To view all warning messages related to security, select Warning and Security Only.
•
To view all informational messages related to security, select Informational and Security
Only.
72 | Copy-Free Transition Guide
4. To save the raw results in comma-separated values (CSV) format and export the results, click
Save As CSV.
You can view the transition operations that have been performed during the transition along with
the operation type, status, start time, end time, and results in the Operation History tab on the
Dashboard pane.
After you finish
You must resolve all the errors detected by the prechecks before you start data copy. It is also a best
practice to resolve all warnings prior to proceeding with the migration process. Resolution can be
resolving the source issue of the warning message, implementing a workaround, or accepting the
result of the issue.
Severity levels for precheck messages
You can verify whether the 7-Mode volumes can be transitioned by running the transition precheck
operation. Transition precheck reports all the transition issues. Transition issues are assigned different
severity levels, depending on the impact of the issue on the transition process.
The issues detected by the prechecks are classified into the following categories:
Error
Configurations that cannot be transitioned.
You cannot continue the transition if there is even one error. The following are some
example configurations on the 7-Mode system that cause an error:
•
Traditional volumes
•
SnapLock volumes
•
Offline volumes
Warning
Configurations that can cause minor problems after transition.
Features that are supported in clustered Data ONTAP, but are not transitioned by the 7Mode Transition Tool, also generate a warning message. You can continue the transition
with these warnings. However, after the transition you might lose some of these
configurations or might have to complete some manual tasks for enabling these
configurations in clustered Data ONTAP.
The following are some example configurations on the 7-Mode system that generate a
warning:
•
IPv6
•
NFSv2
•
NDMP configurations
•
Interface groups and VLANs
•
Routing Information Protocol (RIP)
Information
Configurations that have been successfully transitioned.
Transitioning 7-Mode aggregates using copy-free transition | 73
Applying SVM configurations
You must manually apply some configurations before the SVM provision phase. You can then apply
all configurations that are defined in the 7-Mode controller (files in the /etc directory) or at the
vFiler unit level to the mapped SVMs by using the tool.
Before you begin
If you do not want to transition all configurations to the target SVMs, you must have set the
properties for the configurations to be excluded on the SVMs.
Customizing the transition of 7-Mode configurations on page 66
About this task
•
Configurations such as NFS exports, CIFS shares, and LUN mapping are not applied to the SVM
in the SVM provision phase.
•
The following configurations are applied by the tool on the SVMs in the SVM provision phase:
Name services
◦
DNS configuration
◦
LDAP configuration
◦
NIS configuration
◦
Name service switch configuration
◦
Hosts configuration
◦
UNIX users and groups
◦
Netgroups configuration
Networking
◦
Existing 7-Mode IP addresses that are selected for transition are created in the
administrative down state.
During the import phase, these IP addresses are configured in the administrative up
state.
◦
New IP addresses are created in the administrative up state.
NFS
NFS options
CIFS
◦
CIFS preferred DC configuration
◦
User mapping configuration
◦
Widelinks configuration
◦
CIFS options
◦
Audit configuration
SAN
FC and iSCSI services
74 | Copy-Free Transition Guide
•
Important: You cannot rerun this operation after it is completed successfully.
Therefore, if you make any changes to the 7-Mode controller-level configurations after this
operation, you must manually transition the configurations to the target SVMs before the
export phase. For example, if you add a new vFiler unit to the 7-Mode controller and map it to
an SVM after this operation, you must manually transition the configurations of that vFiler unit
to the mapped SVM. Another example is if you add some UNIX users on the 7-Mode
controller after the SVM provision phase, you must create these UNIX users manually on the
mapped SVMs.
Steps
1. Click Apply SVM Config to apply the 7-Mode configurations to the target SVMs.
A confirmation message that lists important considerations for this operation is displayed.
2. Click Yes to continue.
3. After the operation is complete, perform the following steps:
a. Optional: Click Save as CSV to save the operation results in a file.
b. Optional: Click Collect Project Logs to create a backup of all of the transition log files.
It is a best practice to save the log files after each transition operation.
c. Click Close to close the operation results window.
If the operation takes a long time to complete, you can click Run in Background to exit the
operation results window. You should not edit the project or perform any other task when the
operation is running in the background. You can then view the operations results from the
Operation History tab.
4. Verify and test the configurations that are applied to the target SVMs manually and make the
required changes.
5. Manually verify the connectivity to external name servers.
Verifying that 7-Mode systems are ready for cutover
Before disconnecting client access, you can verify the readiness of the 7-Mode system for storage
cutover, such as verifying whether the SP or RLM is configured on the 7-Mode system and whether
the disk shelves, aggregates, and volumes are ready for transition. You can manually fix any issues
before the export operation, thereby reducing the downtime.
About this task
You can run this operation multiple times before the export and halt operation is initiated.
Steps
1. Optional: Click Check Readiness to verify that the 7-Mode systems are ready for cutover.
Although this operation is optional, it is a best practice to verify the readiness of the systems and
fix issues before the export operation in order to minimize the storage cutover window.
2. Wait for the operation to complete and do the following:
a. Optional: Click Save as CSV to save the operation results in a file.
b. Optional: Click Collect Tool Logs to take a backup of all the transition log files.
Transitioning 7-Mode aggregates using copy-free transition | 75
It is a best practice to save the log files after each transition operation.
c. Click Close to close the operation results window.
If the operation takes a long time to complete, you can click Run in Background to exit the
operation results window. You should not edit the project or perform any other task when the
operation is running in the background. You can then view the operations results from the
Operation History tab.
Exporting storage configurations and halting 7-Mode
systems
The cutover window for the transition starts from the export phase. In this phase, the tool collects
system information, disk shelf details, and storage configurations from the 7-Mode systems, and then
halts the 7-Mode storage systems.
Before you begin
•
The Service Processor (SP) or Remote LAN Module (RLM) must be configured with an IPv4
address on the 7-Mode system.
Find a System Administration Guide for your version of Data ONTAP 7G
•
All clients must be disconnected from the 7-Mode systems (by unmounting NFS exports,
disconnecting CIFS shares, and shutting down SAN hosts), but the applicable NAS and SAN
services must be running on the 7-Mode systems.
Important: You must not stop any protocol services because they are required for collecting the
protocol configurations from the 7-Mode storage systems.
About this task
•
Any data written to the 7-Mode volumes during this operation is lost.
•
You must not perform any management operations on the 7-Mode systems during this operation.
•
The tool performs the following operations in the export phase:
◦
Collects all volume and storage configurations
◦
Creates a Snapshot copy of each transitioning aggregate
If you decide to revert to 7-Mode at any stage of transition, these Snapshot copies are used by
the tool for the revert operation.
◦
Boots the 7-Mode controllers in maintenance mode
◦
Removes disk ownerships from the 7-Mode controllers
◦
Disables disk autoassignment on the target cluster nodes
Steps
1. Click Export & Halt.
A message that lists important considerations for this operation is displayed.
2. Click the Confirm that the client access is disconnected check box.
3. Click Yes to continue with the export and halt operation.
The operation results are displayed.
76 | Copy-Free Transition Guide
4. Wait for the operation to complete and perform the following steps to save the operation results
and collect the tool logs:
a. Optional: Click Save as CSV to save the operation results in a file.
b. Optional: Click Collect Tool Logs to create a backup of all the transition log files.
It is a best practice to save the log files after each transition operation.
c. Click Close to close the operation results window.
If the operation takes a long time to complete, you can click Run in Background to exit the
operation results window. You should not edit the project or perform any other task when the
operation is running in the background. You can then view the operations results from the
Operation History tab.
Disconnecting disk shelves from the 7-Mode system and
connecting to cluster nodes
Cabling the 7-Mode disk shelves to the target cluster nodes is a manual process. After cabling the
disk shelves, it is a best practice to verify the cabling by using Config Advisor. You can then verify
the cabling by using the 7-Mode Transition Tool. The tool performs only a subset of the checks that
are performed by Config Advisor.
Before you begin
You must have recorded the information about disk shelf connectivity to the 7-Mode controller ports.
About this task
You must be aware of some of the considerations for connecting SAS disk shelves:
•
You must follow the rules for cabling SAS square and circle ports.
•
IOM6 and IOM3 shelves can be mixed in the same stack, but there should be no more than a
single transition between shelves that are using different IOM types.
For example, IOM6e (controller)—IOM6 (shelf)—IOM3 (shelf)—IOM3 (shelf) is a supported
configuration. But IOM6e (controller)—IOM3 (shelf)—IOM6 (shelf)—IOM3 (shelf) is not a
supported configuration.
Steps
1. Check the disk shelf IDs in the 7-Mode HA pair and the target cluster nodes:
a. If there are duplicate shelf IDs (if the 7-Mode disk shelf IDs are used for the disk shelves in
the target cluster nodes), change the disk shelf IDs.
•
For SAS disk shelves, a valid shelf ID is 00 through 99.
•
SAS shelf IDs must be unique within the HA pair.
SAS Disk Shelves Installation and Service Guide for DS4243, DS2246, DS4486, and DS4246
•
For FC disk shelves, a valid shelf ID is 1 through 7.
•
FC shelf IDs must be unique within each FC loop.
DS14mk2 FC, and DS14mk4 FC Hardware Service Guide
b. Power cycle the disk shelves for the new IDs to take effect.
Transitioning 7-Mode aggregates using copy-free transition | 77
2. Power off the 7-Mode disk shelves.
3. Depending on whether additional ports are available on the target cluster nodes, choose one of the
following options:
If...
Then...
Additional ports are available
to connect the disk shelves
Connect the disk shelves in a new stack to the target cluster nodes in a
multipath configuration.
Note: It is the best practice to connect the disk shelves to a separate
stack. The 7-Mode Transition Tool detects the availability of the
required number of ports on the target cluster nodes when prechecks
are run.
Ports are not available to
connect the disk shelves
Perform one of the following actions:
•
Add a new expansion card and connect the disk shelves in a new
stack to the target cluster nodes in a multipath configuration.
You must have verified that the expansion card is supported on the
destination platform.
•
Connect the disk shelves to an existing stack in a multipath
configuration.
SAS Disk Shelves Universal SAS and ACP Cabling Guide
SAS Disk Shelves Installation and Service Guide for DS4243, DS2246, DS4486, and DS4246
DiskShelf14mk2 AT Hardware Service Guide
DS14mk2 FC, and DS14mk4 FC Hardware Service Guide
4. Power on the disk shelves.
Important: You must wait for at least 70 seconds before you proceed.
5. Use Config Advisor to verify the connections.
You must fix any cabling issues identified by Config Advisor.
NetApp Downloads: Config Advisor
6. From the 7-Mode Transition Tool, click Verify Cabling.
A message listing the important considerations for this operation is displayed.
Troubleshooting: If there are missing disks in an aggregate, the aggregate becomes degraded
and the cabling verification fails. If the number of missing disks is within a permissible limit,
you can continue the transition with the degraded aggregates by running the following
command from the 7-Mode Transition Tool CLI:
transition cft aggregate degraded-transition -p project_name -n 7mode_host_name -a 7-mode_aggregate_name -i acknowledge
You can then rerun the cabling verification operation and continue with the transition. You
must ensure that there are enough spare disks in the target cluster node to reconstruct these
RAID groups after the aggregates are transitioned.
7. Click Yes to continue.
8. Wait for the operation to complete and perform the following steps to save the operation results
and collect the tool logs:
a. Optional: Click Save as CSV to save the operation results in a file.
78 | Copy-Free Transition Guide
b. Optional: Click Collect Tool Logs to create a backup of all the transition log files.
It is a best practice to save the log files after each transition operation.
c. Click Close.
If the operation takes a long time to complete, you can click Run in Background to exit the
operation results window. You should not edit the project or perform any other task when the
operation is running in the background. You can then view the operations results from the
Operation History tab.
Related tasks
Gathering cabling information for transition on page 31
Importing 7-Mode data to ONTAP
After verifying the cabling and resolving any issues, you can run the import operation. In this phase,
the disk ownership is assigned to the mapped cluster nodes, and the 7-Mode aggregates, volumes,
and LUNs are converted to the ONTAP format. All the volume-level and LUN-level configurations
are also applied.
About this task
The following operations are performed by the tool in this phase:
•
7-Mode disks are assigned to the mapped target cluster nodes.
•
All the 7-Mode aggregates, volumes, and LUNs are converted to the ONTAP format.
•
The 7-Mode IP addresses that were selected for transition are configured on the SVMs in the
administrative up state.
•
The following configurations are applied:
◦
NFS export rules
◦
CIFS shares
◦
CIFS ACLs configuration
◦
CIFS home directory configuration
◦
CIFS symbolic links
◦
Quota configuration
◦
Snapshot copy schedules
◦
LUN maps and igroups
Steps
1. Click Import.
Troubleshooting: If there are missing disks in an aggregate, the aggregate becomes degraded
and the import operation fails. If the number of missing disks is within a permissible limit, you
can continue the transition with the degraded aggregates by running the following command
from the 7-Mode Transition Tool CLI:
transition cft aggregate degraded-transition -p project-name -n 7mode-host-name -a 7-mode-aggregate-name -i acknowledge
Transitioning 7-Mode aggregates using copy-free transition | 79
You can then rerun the cabling verification operation and continue with the transition. You
must make sure that there are enough spare disks in the target cluster node to reconstruct these
RAID groups after the aggregates are transitioned.
A warning message is displayed, listing the important considerations for this operation.
2. Click Yes to continue.
The operation results are displayed.
3. Wait for the operation to complete and do the following:
a. Optional: Click Save as CSV to save the operation results in a file.
b. Optional: Click Collect Tool Logs to take a backup of all the transition log files.
It is a best practice to save the log files after each transition operation.
c. Click Close to close the operation results window.
If the operation takes a long time to complete, you can click Run in Background to exit the
operation results window. You should not edit the project or perform any other task when the
operation is running in the background. You can then view the operations results from the
Operation History tab.
80
Completing the transition
Completing the transition involves manually verifying the transitioned volumes and configurations,
testing your workload, starting production, and then committing the copy-free transition project.
Because rollback is not allowed after the commit operation, you should verify all workloads and start
production for a brief duration to evaluate if rollback is required.
Steps
1. Reviewing the restrictions during preproduction testing on page 80
Some operations are blocked and some operations are not recommended during preproduction
testing. These restrictions are imposed for allowing a rollback to 7-Mode if you do not want to
commit the transition.
2. Rehosting transitioned volumes to a different SVM on page 82
Volume rehost enables you to migrate a transitioned volume from one SVM to another SVM
without data copy. The rehost operation enables you to consolidate all volumes that have FC
LUNs to a single SVM, thereby preserving the 7-Mode single-system image (SSI) semantics. You
can also rehost transitioned NAS volumes.
3. Verifying the transitioned configurations on page 85
After successfully importing the 7-Mode volumes and configurations, you must manually verify
the transitioned aggregates, volumes, LUNs, and configurations.
4. Performing manual configuration tasks after transition on page 85
You must manually perform some configuration tasks that are required for the workloads and
applications that are accessing the transitioned volumes. You can obtain the list of manual tasks
from the precheck results.
5. Testing the workloads and applications on page 86
You should manually test all workloads and applications in the preproduction environment. You
can then start production for a brief duration to evaluate if rollback is required before committing
the project.
6. Committing the copy-free transition project on page 87
The final step in transition is to commit the copy-free transition project. After committing the
aggregates, you cannot perform a rollback to 7-Mode.
Restrictions during preproduction testing
Some operations are blocked and some operations are not recommended during preproduction
testing. These restrictions are imposed for allowing a rollback to 7-Mode if you do not want to
commit the transition.
Operations that are blocked
Operation
Description
Automatically deleting (autodelete)
aggregate Snapshot copies
Because the 7-Mode aggregate-level Snapshot copies created
during the export operation are required in case of a
rollback, the Snapshot copies are not deleted automatically
when the used space in the aggregate grows.
Important: You must monitor the free physical space in
the aggregate and ensure that the aggregates do not run
out of space during the testing.
Completing the transition | 81
Operation
Description
Moving volumes to another
aggregate
•
You cannot move volumes to the transitioned aggregates.
•
You can move volumes from the transitioned aggregates
to aggregates in the cluster.
•
You cannot copy or move LUNs to the transitioned
volumes.
•
You can copy or move LUNs from the transitioned
volumes to other volumes in the cluster.
Copying or moving LUNs across
volumes
Creating an aggregate
This operation is restricted on the target cluster HA pair.
You can create aggregates on other nodes in the cluster.
Destroying an aggregate
Because the 7-Mode aggregate-level Snapshot copies created
during the export operation are required in case of a
rollback, the transitioned aggregates cannot be destroyed.
Setting up a transitioned aggregate
as the root aggregate
The transitioned aggregates cannot be selected as root
aggregates. Additionally, you cannot modify the HA policy
of the transitioned aggregates to CFO.
Performing file copy operations
•
You cannot move or copy files (single file copy-ondemand) to the transitioned volumes.
•
You can move or copy files from the transitioned
volumes to other volumes in the cluster.
Mirroring an existing aggregate
The operation is blocked on all the aggregates in the cluster.
Upgrading or reverting the Data
ONTAP version on the target
cluster nodes
You must commit the project before upgrading or reverting
the target cluster nodes.
Adding disks
You cannot run the storage aggregate add-disks
command in the admin privilege level. However, you can run
this command in the advanced privilege level.
Important: You must ensure that only the spare disks
from the 7-Mode disk shelves are added for increasing the
space in the transitioned aggregates. You must add spare
disks by using the -disklist parameter (the diskcount parameter must not be used).
ONTAP 9 man page: storage aggregate add-disks
Designating a transitioned volume
as the SVM root volume
You cannot run the volume make-vsroot command on
the transitioned volumes.
Operations that are not recommended
Operation
Corrective action before rollback
Relocating aggregates
The ownership of the transitioned
aggregate is changed to its HA
partner.
Swap the aggregate ownership before rollback because the
7-Mode Transition Tool maps the aggregates to the 7Mode controllers based on the target node mapping
information saved in the project.
82 | Copy-Free Transition Guide
Operation
Corrective action before rollback
Creating volumes on the transitioned
aggregates
You must delete these volumes or move them to different
aggregates.
Renaming aggregates or volumes
Rename the aggregates or volumes to their original
names.
Changing the RAID type
The RAID type must match the 7-Mode RAID type if you
decide to roll back to 7-Mode.
Rehosting transitioned volumes to a different SVM
Volume rehost enables you to migrate a transitioned volume from one SVM to another SVM without
data copy. The rehost operation enables you to consolidate all volumes that have FC LUNs to a single
SVM, thereby preserving the 7-Mode single-system image (SSI) semantics. You can also rehost
transitioned NAS volumes.
Before you begin
•
The volume that you want to rehost must be online.
•
Volume management operations, such as volume move or LUN move, must not be running.
•
Data access to the volume that is being rehosted must be stopped.
Rehosting is a disruptive operation.
About this task
The following volume policies, policy rules, and configurations are lost from the source volume and
must be manually reconfigured on the rehosted volume after the rehost operation:
•
Volume and qtree export policies
•
Antivirus policies
•
Volume efficiency policy
•
Quality of Service (QoS) policies
•
Snapshot policies
•
Quota rules
•
CIFS shares
•
igroups associated with a portset
Choices
•
Rehosting FC and iSCSI volumes
1. Switch to the advanced privilege level:
set -privilege advanced
2. Rehost the volume on the destination SVM:
Completing the transition | 83
•
If you want to...
Run the following command...
Unmap the LUNs after rehosting
volume rehost -vserver source_svm
-volume vol_name -destinationvserver destination_svm -force–
unmap-luns true
Remap the LUNs to the same igroups after
rehosting
volume rehost -vserver source_svm
-volume vol_name -destinationvserver destination_svm -autoremap-luns true
Rehosting NFS volumes
1. Record information about the NFS export policies.
2. Unmount the volume from the parent volume.
ONTAP 9 man page: volume unmount
3. Switch to the advanced privilege level:
set -privilege advanced
4. Rehost the volume on the destination SVM:
volume rehost -vserver source_svm -volume vol_name -destinationvserver destination_svm
The default export policy of the destination SVM is applied to the rehosted volume.
5. Optional: Create the export policy.
ONTAP 9 man page: vserver export-policy create
6. Update the export policy of the rehosted volume to a user-defined export policy.
ONTAP 9 man page: volume modify
7. Mount the volume under the appropriate junction path in the destination SVM.
ONTAP 9 man page: volume mount
8. Verify that the NFS service is running on the destination SVM.
ONTAP 9 man page: vserver nfs status
9. Resume NFS access to the rehosted volume.
Because the volume access path (LIFs and junction path) has undergone changes, you must
update the NFS client credentials and LIF configurations to reflect the destination SVM LIFs.
NFS management
•
Rehosting CIFS volumes
1. Record information about the CIFS shares.
2. Unmount the volume from the parent volume.
ONTAP 9 man page: volume unmount
3. Switch to the advanced privilege level:
set -privilege advanced
4. Rehost the volume on the destination SVM:
volume rehost -vserver source_svm -volume vol_name -destinationvserver destination_svm
84 | Copy-Free Transition Guide
5. Mount the volume under the appropriate junction path in the destination SVM.
ONTAP 9 man page: volume mount
6. Create CIFS shares for the rehosted volume.
ONTAP 9 man page: vserver cifs share create
7. If the DNS domains differ between the source and destination SVMs, create new users and
groups.
8. Update the CIFS client with the new destination SVM LIFs and junction path to the rehosted
volume.
CIFS management
•
Rehosting volumes in SnapMirror relationships
1. Record the SnapMirror relationship type.
ONTAP 9 man page: snapmirror show
2. From the destination cluster, delete the SnapMirror relationship.
ONTAP 9 man page: snapmirror delete
Important: You must not break the SnapMirror relationship; otherwise, the data protection
capability of the destination volume is lost and the relationship cannot be reestablished after
the rehosting operation.
3. From the source cluster, release the SnapMirror relationship information:
You set the -relationship-info-only parameter to true so that the Snapshot copies are
not deleted and only the source relationship information is removed.
ONTAP 9 man page: snapmirror release
4. Switch to the advanced privilege level:
set -privilege advanced
5. Rehost the volume on the destination SVM:
volume rehost -vserver source_svm -volume vol_name -destinationvserver destination_svm
6. Create the SVM peer relationship between the source and destination SVMs.
ONTAP 9 man page: vserver peer create
7. Create the SnapMirror relationship between the source and destination volumes.
ONTAP 9 man page: snapmirror create
The rehosted volume can be the source or destination of the SnapMirror relationship.
8. Resynchronize the data protection relationship.
ONTAP 9 man page: snapmirror resync
Data protection using SnapMirror and SnapVault technology
After you finish
You must manually create the autovolume workloads for the rehosted volumes by performing the
following steps:
1. Create a user-defined policy group for the SVM:
Completing the transition | 85
qos policy-group create -vserver destination-vserver -policy-group
policy-group-name
ONTAP 9 man page: qos policy-group create
2. Assign the QoS policy group to the rehosted volume:
volume modify -vserver destination-vserver -volume rehosted-volume -qospolicy-group policy-group-name
ONTAP 9 man page: volume modify
You must manually reconfigure the policies and the associated rules on the rehosted volume.
Note: If the rehosting operation fails, you might need to reconfigure the volume policies and the
associated rules on the source volume.
Related information
ONTAP 9 man page: volume rehost
Verifying the transitioned configurations
After successfully importing the 7-Mode volumes and configurations, you must manually verify the
transitioned aggregates, volumes, LUNs, and configurations.
Steps
1. Verify that the 7-Mode aggregates, volumes, and LUNs as well as the CIFS shares, NFS exports,
and LUN mappings are transitioned.
2. Verify that all the 7-Mode configurations are retained.
Performing manual configuration tasks after transition
You must manually perform some configuration tasks that are required for the workloads and
applications that are accessing the transitioned volumes. You can obtain the list of manual tasks from
the precheck results.
Step
1. Perform the tasks listed in the precheck results for configuring features that were not transitioned
by the tool or that require customization for your environment.
Name services transition: supported and unsupported configurations, and required manual steps
on page 40
NFS transition: supported and unsupported configurations, and required manual steps on page 43
CIFS transition: supported and unsupported configurations, and required manual steps on page 50
SAN transition: supported and unsupported configurations, and required manual steps on page 54
Transitioning a SnapMirror relationship on page 88
86 | Copy-Free Transition Guide
Testing the workloads and applications
You should manually test all workloads and applications in the preproduction environment. You can
then start production for a brief duration to evaluate if rollback is required before committing the
project.
Before you begin
The transitioned aggregates must have at least 5% free physical space.
Note: The best practice is to have at least 20% free space in the transitioned aggregates.
About this task
Some operations are restricted during preproduction testing.
Restrictions during preproduction testing on page 80
Steps
1. Connect clients to the transitioned volumes.
2. If you have SAN workloads, perform the post-transition host remediation tasks on the SAN hosts.
SAN host transition and remediation
3. Test all the workloads and applications that use the transitioned data and configurations.
4. Verify that the transitioned aggregates are not running out of space by monitoring the free
physical space in the transitioned aggregates from the Aggregates tab in the 7-Mode Transition
Tool dashboard.
Troubleshooting: If you run out of space on the transitioned aggregates, you can add disks.
a. Log in to the advanced privilege level:
set -privilege advanced
b. Select the spare disks from the 7-Mode disk shelves and add disks to increase the space in
the transitioned aggregates:
storage aggregate add-disks -aggregate aggr_name -disklist disk1
If 7-Mode spare disks are not available, you can use spare disks from the disk shelves in the
cluster nodes; however, doing so complicates the rollback process.
ONTAP 9 man page: storage aggregate add-disks
After you finish
You can start serving production data.
Important: You can serve data in the production environment for a brief duration to ensure that the
workloads are operating correctly in a production environment and a rollback to 7-Mode is not
required. You must not prolong this phase and must not delay committing the copy-free transition
project for the following reasons:
•
The probability of running out of space in the transitioned aggregates increases as new data is
written to the volumes.
•
Any new data written to the volumes during this stage will not be available during rollback.
Completing the transition | 87
Related concepts
Performing a transition rollback to 7-Mode on page 99
Committing the copy-free transition project
The final step in transition is to commit the copy-free transition project. After committing the
aggregates, you cannot perform a rollback to 7-Mode.
Before you begin
You must have manually verified the transitioned data and configurations and tested workloads and
applications.
About this task
All the aggregate-level Snapshot copies that were created in the export phase are deleted.
Steps
1. Click Commit.
2. In the warning message that is displayed, click Yes.
Result
All the preproduction testing phase restrictions are removed and the transitioned volumes can serve
production data, if not done in the preproduction testing phase.
88
Transitioning a SnapMirror relationship
You can transition the secondary HA pair first, set up a staggered SnapMirror relationship between
the 7-Mode primary volumes and clustered Data ONTAP secondary volumes, and then transition the
primary HA pair later. In some scenarios, you must transition the secondary and primary HA pairs of
a 7-Mode SnapMirror relationship in parallel.
About this task
If all the primary volumes belong to one HA pair and all the secondary volumes belong to the other
HA pair, you can transition by using the staggered method.
If either HA pair has a mix of primary and secondary volumes, you must transition by using the
parallel method.
After transitioning the primary and secondary HA pairs, you must manually set up the volume
SnapMirror relationship in clustered Data ONTAP after transition. For a successful
resynchronization, at least one common Snapshot copy, which is created in Data ONTAP 8.1 or later,
must exist between the primary and secondary volumes of the SnapMirror relationship.
Choices
• Transitioning HA pairs in a SnapMirror relationship in a staggered configuration on page 88
• Transitioning primary and secondary systems in a SnapMirror relationship in parallel on page 90
Related information
Data protection using SnapMirror and SnapVault technology
Cluster management using System Manager
Transitioning HA pairs in a SnapMirror relationship in a
staggered configuration
You can transition the secondary HA pair first, set up a staggered SnapMirror relationship between
the 7-Mode primary volumes and clustered Data ONTAP secondary volumes, and then transition the
primary HA pair later.
Before you begin
You must have prepared the source and destination clusters for transitioning the SnapMirror
relationships.
Preparing the cluster for transitioning volume SnapMirror relationships on page 56
Steps
1. From the 7-Mode Transition Tool, perform a copy-free transition of the HA pair that contain the
secondary volumes of the 7-Mode volume SnapMirror relationships.
Before transitioning the 7-Mode HA pair that contains the secondary volumes, no manual
intervention is required for the 7-Mode SnapMirror relationships. This ensures that the 7-Mode
secondary volumes are transitioned as read-only volumes to clustered Data ONTAP.
Transitioning 7-Mode aggregates using copy-free transition on page 58
2. During the precommit testing phase of the secondary HA pair, create a disaster recovery
relationship between the 7-Mode primary volume and clustered Data ONTAP secondary volume:
Transitioning a SnapMirror relationship | 89
a. From the secondary destination cluster, use the vserver peer transition create
command to create an SVM peer relationship between the 7-Mode primary volume and the
clustered Data ONTAP secondary volume.
ONTAP 9 man page: vserver peer transition create
b. Use the job schedule cron create command to create a job schedule that matches the
schedule configured for the 7-Mode SnapMirror relationship.
ONTAP 9 man page: job schedule cron create
c. Use the snapmirror create command to create a SnapMirror relationship of type TDP
between the 7-Mode primary volume and the clustered Data ONTAP secondary volume.
ONTAP 9 man page: snapmirror create
d. Use the snapmirror resync command to resynchronize the clustered Data ONTAP
secondary volume.
For successful resynchronization, a common 7-Mode Snapshot copy must exist between the 7Mode primary volume and the clustered Data ONTAP secondary volume.
ONTAP 9 man page: snapmirror resync
3. Perform the required testing of the transitioned aggregates and volumes.
4. From the 7-Mode Transition Tool, commit the transition of the project for the secondary HA pair.
Committing the copy-free transition project on page 87
5. Perform a copy-free transition of the HA pair that contains the primary volumes of the 7-Mode
volume SnapMirror relationships.
Transitioning 7-Mode aggregates using copy-free transition on page 58
6. During the precommit testing phase of the primary HA pair, create a SnapMirror relationship
between the transitioned secondary and primary volumes.
a. From the destination cluster, create an intercluster SVM peer relationship between the SVMs
that contain the transitioned primary and secondary volumes.
System administration
b. Use the snapmirror delete command to delete the TDP SnapMirror relationship between
the 7-Mode primary volume and the clustered Data ONTAP secondary volume that was
created in Step 2.c.
ONTAP 9 man page: snapmirror delete
c. Optional: Delete the cron job schedule that was created in Step 2.b.
ONTAP 9 man page: job schedule cron delete
d. Create a volume SnapMirror relationship between the transitioned primary and secondary
volumes.
Volume disaster recovery express preparation
e. On the destination volume, resynchronize the source volume and destination volume of the
SnapMirror relationship.
Important: At least one common Snapshot copy must exist between the source and
destination volumes.
Troubleshooting: SnapMirror resynchronization fails if the common Snapshot copy was
created in a Data ONTAP release earlier than 8.1. You can use the -fs-version parameter
with the volume snapshot show command in the advanced privilege level to view the
90 | Copy-Free Transition Guide
release in which the Snapshot copy is created. If this issue occurs, break the SnapMirror
relationship and then perform the resynchronization.
ONTAP 9 man page: snapmirror resync
f. Monitor the status of the SnapMirror data transfers.
Important: You must not perform any operation, such as volume move or SnapMirror
break, on the source and destination volumes until the resynchronization is completed
successfully. Ensure that the resynchronization does not get aborted and completes
successfully; otherwise, the volumes can go to an inconsistent state.
ONTAP 9 man page: snapmirror show
7. Commit the transition of the primary project.
Committing the copy-free transition project on page 87
Related information
7-Mode data transition using SnapMirror
Transitioning primary and secondary systems in a
SnapMirror relationship in parallel
You can transition the primary and secondary HA pairs that contain the volumes of a 7-Mode
SnapMirror relationship in parallel. You must then manually set up the volume SnapMirror
relationship in clustered Data ONTAP after transition. The SnapMirror relationship is retained after
transition without requiring a rebaseline.
Before you begin
You must have prepared the source and destination clusters for transitioning the SnapMirror
relationships.
Preparing the cluster for transitioning volume SnapMirror relationships on page 56
About this task
You must transition both the secondary and primary HA pairs in the same cutover window.
Steps
1. From the 7-Mode Transition Tool, perform a copy-free transition of the two HA pairs that contain
the primary and secondary volumes of the 7-Mode volume SnapMirror relationship.
Before transitioning the 7-Mode HA pair that contains the secondary volumes, no manual
intervention is required for the 7-Mode SnapMirror relationships. This ensures that the 7-Mode
secondary volumes are transitioned as read-only volumes to clustered Data ONTAP.
Transitioning 7-Mode aggregates using copy-free transition on page 58
2. Create an intercluster SVM peer relationship between the SVMs that contain the transitioned
primary and secondary volumes.
System administration
3. Create a volume SnapMirror relationship between the transitioned primary and secondary
volumes.
Volume disaster recovery express preparation
Transitioning a SnapMirror relationship | 91
4. On the destination volume, resynchronize the source volume and destination volume of the
SnapMirror relationship.
Important: At least one common Snapshot copy must exist between the source and destination
volumes.
ONTAP 9 man page: snapmirror resync
Troubleshooting: SnapMirror resynchronization fails if the common Snapshot copy was
created in a Data ONTAP release earlier than 8.1. You can use the -fs-version parameter
with the volume snapshot show command in the advanced privilege level to view the
release in which the Snapshot copy was created. If you encounter this issue, break the
SnapMirror relationship and then perform the resynchronization.
5. Monitor the status of the SnapMirror data transfers.
Important: You must not perform any operation, such as volume move or SnapMirror break,
on the source and destination volumes until the resynchronization is completed successfully.
Ensure that the resynchronization does not get aborted and completes successfully; otherwise,
the volumes can go to an inconsistent state.
ONTAP 9 man page: snapmirror show
6. Commit the transition of the secondary project, followed by the primary project.
Committing the copy-free transition project on page 87
Related information
Cluster management using System Manager
Data protection using SnapMirror and SnapVault technology
92
Troubleshooting transition issues
You should be aware of how to troubleshoot issues with the 7-Mode Transition Tool and where to
look for log files. When you use the 7-Mode Transition Tool, you might see error messages that
identify the issue and provide the solution.
Continuing with the transition if ignorable errors occur
During the transition, you might encounter some errors that block the transition. You can choose to
ignore some of these errors by acknowledging the issues through the 7-Mode Transition Tool CLI.
You should rerun the failed operation after ignoring the error to continue with the transition.
About this task
When you acknowledge an error, it means that you have understood the impact of these errors and
acknowledged them.
You must rerun the transition operation after ignoring the error. In some cases, after you acknowledge
the issue, Data ONTAP performs corrective actions on the affected aggregates and volumes when the
operation is run the next time.
Steps
1. If the transition operation results in any ignorable errors, run the following command from the 7Mode Transition Tool CLI:
transition cft ignorableerrors add -p project_name -c
ignorable_errorcategory
ignorable_errorcategory is the type of error that you can ignore.
Ignorable error categories on page 92
2. Rerun the transition operation.
The blocking error changes to a warning and the error is shown as acknowledged. You can
continue the transition with the warning.
Ignorable error categories
You might encounter some ignorable errors during the transition. These errors can occur during the
precheck, cabling, import, or commit operation of a copy-free transition project.
When you add any ignorable error category to the copy-free transition project by using the 7-Mode
Transition Tool CLI, it means that you have understood the impact of the error. You must rerun the
transition operation after ignoring the error. At this time, the blocking error changes to a warning
message and the error is shown as “acknowledged”. You can continue the transition with the warning.
Precheck operation: ignorable error categories
Category
When the error is displayed
ignore-source-not-multipath
7-Mode disk shelves are not in a multipath
configuration.
ignore-target-not-multipath
Disk shelves in the target cluster nodes are not in a
multipath configuration.
Troubleshooting transition issues | 93
Category
When the error is displayed
ignore-source-storage-fault
7-Mode disk shelves have some fault (as displayed in
the output of the storage show fault command).
ignore-target-storage-fault
Disk shelves in the target cluster nodes have some
fault (as displayed in the output of the system node
run -node node_name -command storage
show fault command).
ignore-target-port-requirement
Target cluster nodes do not have a sufficient number
of ports available to connect the 7-Mode disk shelves.
ignore-aggr-space-less-than-5percent
7-Mode aggregates are out of space because the free
space in the 7-Mode aggregates is less than 5% of
physical space.
ignore-aggr-logical-space-morethan-97-percent
7-Mode aggregates are out of space because the
logical space in the aggregate is more than 97% full.
ignore-aggr-snapshot-spillmore-than-4-percent
7-Mode aggregates are out of space because Snapshot
copies occupy more space than that allocated for the
Snapshot copy reserve.
ignore-aggr-physical-spacemore-than-89-percent-andsnapshot-spill
7-Mode aggregates are out of space because the total
used physical space is more than 89% and the
Snapshot copies occupy more space than that
allocated for the Snapshot copy reserve.
ignore-volumes-with-filegurantee
7-Mode volumes have space guarantee set to file,
which is not supported in clustered Data ONTAP.
ignore-volumes-with-disabledgurantees
Space guarantee of volumes is currently disabled due
to lack of space in the volumes.
nfs-qtrees-exported
Qtree export rules are present in the 7-Mode system.
Acknowledging this error means that you have
understood the differences in the qtree export rules
between Data ONTAP operating in 7-Mode and
clustered Data ONTAP. You might have to perform
some manual steps after the NFS exports rules are
applied by the 7-Mode Transition Tool.
NetApp KB Article 8010371:7MTT Precheck 10111 Transitioning 7-Mode volumes that have qtree-level
exports
ignore-configuration-limitscheck
Objects and configurations to be transitioned exceed a
certain limit.
The storage cutover can take a long time and you
must prepare for the downtime.
NetApp KB Article 3014882: Storage cutover time
considerations for Copy-Free Transition
94 | Copy-Free Transition Guide
Category
When the error is displayed
ignore-cifs-ad-domain-mismatch
The 7-Mode Transition Tool continues with the
transition of CIFS configuration even if the CIFS
Active Directory domain of the 7-Mode system is
different from the CIFS Active Directory domain of
the target SVM.
You must ensure that the CIFS Active Directory
domains of the 7-Mode system and the target SVM
are trusted domains. Otherwise, the transition of CIFS
configurations to the target SVM fails.
NetApp KB Article 3014999: 7MTT: Transition of
CIFS configurations from 7-Mode to clustered Data
ONTAP when CIFS Active Directory domains does
not match
Cabling verification operation: ignorable error categories
Category
When the error is displayed
ignore-missing-spare-disks
One or more 7-Mode spare disks are not detected by
the target cluster nodes.
ignore-missing-degraded-aggrdisks
Cannot detect up to two disks from any of the 7-Mode
RAID-DP RAID groups or one disk from any of the
7-Mode RAID-4 RAID groups on the target cluster
nodes.
Continuing with the transition makes such aggregates
degraded after the aggregates are transitioned.
Import operation: ignorable error categories
If you add an ignorable error category to the copy-free transition project during the import operation,
Data ONTAP performs some corrective action on the aggregates and volumes in addition to changing
the blocking error to a warning.
Category
When the error is displayed
Corrective action if the
error is acknowledged and
import operation is run
again
ignore-aggregateswith-32bit-snapshotfor-import
32-bit Snapshot copies are detected
in the 7-Mode aggregate.
32-bit Snapshot copies are
deleted from all the 7-Mode
aggregates that are part of this
project.
transition-dirtyaggregates-duringimport
One of the transitioning aggregates
was not cleanly (dirty) shut down
on the 7-Mode storage system.
All the 7-Mode aggregates
that were not cleanly shut
down are transitioned.
This might result in data loss
after transition.
ignore-aggregatesnot-being-onlinefor-import
The aggregate was not online when
the 7-Mode storage system was
halted.
All the offline aggregates are
brought online.
Troubleshooting transition issues | 95
Category
When the error is displayed
Corrective action if the
error is acknowledged and
import operation is run
again
ignore-volumeswith-32bit-snapshotfor-import
32-bit Snapshot copies are detected
in the 7-Mode volume.
32-bit Snapshot copies are
deleted from all the 7-Mode
volumes that are part of this
project.
ignore-volumes-withdirty-file-systemfor-import
One of the transitioning volumes
was not cleanly (dirty) shut down
on the 7-Mode storage system.
All the 7-Mode volumes that
were not cleanly shut down
are transitioned.
This might result in data loss
after transition.
transition-offlinevolumes-duringimport
The volume was not online when
the 7-Mode storage system was
halted.
All the offline volumes are
brought online.
transitionrestricted-volumesduring-import
The volume was in the restricted
state when the 7-Mode storage
system was halted.
All the restricted volumes are
brought online.
Commit operation: ignorable error categories
If you add an ignorable error category to the copy-free transition project during the commit
operation, Data ONTAP performs some corrective action on the aggregates and volumes in addition
to changing the blocking error to a warning.
Category
When the error is displayed
Corrective action if the
error is acknowledged and
commit operation is run
again
ignore-commitoffline-aggregates
Some of the transitioned aggregates
are offline.
All the offline aggregates are
brought online.
Downloading transition log files
The 7-Mode Transition Tool creates log files that provide processing details of the transition
assessment and migration operations run on your system.
Steps
1. Click Logs in the top menu.
2. Click Collect Project Logs to collect logs related to all of the projects.
3. To collect logs for a given projects, locate the projects from the project list, and then click
Download.
The logs are downloaded as a .zip file, and the folder name is the timestamp.
Related information
NetApp KB Article 1010090: How to upload a file to NetApp
96 | Copy-Free Transition Guide
Log files for the 7-Mode Transition Tool
The 7-Mode Transition Tool creates log files that provide processing details of the transition
operations that have occurred on your system. The log files are located in the logs directory of the
path where 7-Mode Transition Tool is installed.
You can also use the EMS messages related to SnapMirror logs from the 7-Mode system and the
cluster to troubleshoot issues.
The following table lists the log files that are related to a particular transition project:
Log file path
Contains information about...
project_name/
transition.log
Debug messages that are specific to a project
project_name/zapioutbound.log
Output of all the Data ONTAP APIs that are executed by 7-Mode
Transition Tool for a particular project
The following table lists the log files that are not related to any particular project:
Log file path
Contains information about...
transition-gui.log
Entries of all the actions performed by using the web interface
default/audit.log
•
All the parameters, such as HTTP or HTTPS port and log directory
path, that are used by the tool every time 7-Mode Transition Tool is
run
•
All the transition commands that are executed with the outputs
default/default/
transition.log
Debug messages that are not specific to any project
default/
STREAM_MANAGEMENT/
stream_management.l
og
Debug messages that are logged by the scheduler while managing the
schedules and which do not belong to any project
default/default/
zapi-outbound.log
Output of all the Data ONTAP APIs that are executed by 7-Mode
Transition Tool and which do not belong to any project
default/
STREAM_MANAGEMENT/
zapi-outbound.log
Output of all the Data ONTAP APIs that are executed by the 7-Mode
Transition Tool scheduler while managing the schedules and which do
not belong to any project
server-console.log
Log entries of all the packet exchanges done with the 7-Mode
Transition Tool server.
This file helps in troubleshooting issues related to a server crash.
Troubleshooting transition issues | 97
Recovering from a failed LUN transition
If the transition of volumes with LUNs fails, you can use the lun transition 7-mode show
command to check which LUNs were not transitioned to clustered Data ONTAP, and then determine
a corrective action.
Steps
1. From the advanced privilege level, run the lun transition 7-mode show command to check
which LUNs failed.
ONTAP 9 man page: lun transition 7-mode show
2. Review the EMS logs and determine the corrective action that you must take.
3. Perform the required steps shown in the EMS message to correct the failure.
4. If any supported LUNs failed to transition, run the lun transition start command to
complete the transition.
ONTAP 9 man page: lun transition start
5. Run the lun transition show command to view the transition status of the volumes.
The transition status can be one of following values:
•
active: The volume is in an active SnapMirror transition relationship and not yet
transitioned.
•
complete: All supported LUNs are transitioned for this volume.
•
failed: LUN transition failed for the volume.
•
none: The volume did not contain LUNs to transition from 7-Mode systems.
ONTAP 9 man page: lun transition show
Example
cluster1::*> lun transition show
Vserver
Volume
-------------------- -----------------vs1
vol0
vol1
vol2
vol3
Transition Status
----------------none
complete
failed
active
Related concepts
Space considerations when transitioning SAN volumes on page 55
98 | Copy-Free Transition Guide
Failed to boot the 7-Mode controller in maintenance mode
The export and halt operation fails with the error message: Failed to boot the 7-Mode
controller in maintenance mode. You must manually halt and boot the controller in the
maintenance mode and rerun the operation.
Workaround
1. Halt the 7-Mode storage system:
halt -f -t 0
2. At the LOADER prompt, record the values set for the bootarg.init.console_muted and
bootarg.init.console_level boot boot parameters:
printenv bootarg.init.console_muted
printenv bootarg.init.console_level
3. Disable the console messages by setting the following boot parameters:
setenv bootarg.init.console_muted "true"
setenv bootarg.init.console_level "-1"
4. From the 7-Mode Transition Tool, rerun the export and halt operation.
5. From the 7-Mode storage system, set the boot parameters to their original values, as recorded in
Step 2:
If the boot parameters are...
Enter the following commands...
Not set previously with any value (undefined)
unsetenv
bootarg.init.console_muted
unsetenv
bootarg.init.console_level
Set with a value previously
unsetenv
bootarg.init.console_muted
"original_value"
unsetenv
bootarg.init.console_level
"original_value"
99
Performing a transition rollback to 7-Mode
Rollback refers to discontinuing the transition to clustered Data ONTAP and reverting to 7-Mode.
Transition rollback is manual; however, the 7-Mode Transition Tool provides the list of manual tasks
you have to perform for a rollback.
You can roll back a transition project in the SVM provision, export, cabling, import, or preproduction
testing phase. You cannot roll back after the transition project is committed.
Any new data written or modified, such as LUNs or LUN clones, in the transitioned volumes will be
lost after a rollback. The volumes will be reverted to their original 7-Mode state.
When to roll back a transition and when to call technical
support
You can roll back without assistance when performing a rollback on test or lab clusters, but you must
call technical support if you encounter problems during or after transition, or if you want to roll back
a transition performed on a production cluster.
Important: You should not attempt to roll back a transition in a production environment without
assistance from technical support.
If you encounter any of the following circumstances, contact technical support immediately:
•
The transition process fails and cannot finish, and you are unsure of what to do next.
•
The transition process finishes, but the cluster is unusable in a production environment.
•
The transition process finishes and the cluster goes into production, but you are not satisfied with
its behavior.
•
The transition process finishes for some but not all of the data and configuration, and you decide
that you want to roll back the transition.
•
You have a problem with the transition process and cannot resolve the problem with the error
response messages in the 7-Mode Transition Tool, in the Data ONTAP EMS event messages, and
NetApp Knowledgebase.
NetApp Knowledgebase
Related tasks
Downloading transition log files on page 95
Rolling back a copy-free transition project
You can roll back a transition if you want to revert to 7-Mode at any stage of the copy-free transition
before the transitioned aggregates are committed. Rollback is a manual operation. You can use the 7Mode Transition Tool to generate the manual steps that you have to perform for a rollback.
Before you begin
•
You must ensure that no volume or aggregate transition operations are running on the cluster.
You can use the job show -jobtype transition command.
•
None of the 7-Mode aggregates must be committed.
100 | Copy-Free Transition Guide
Note: You cannot perform the rollback if even one 7-Mode aggregate is committed.
•
The target cluster nodes must not be in takeover mode.
Steps
1. Click Rollback Prechecks to verify that the project is eligible for a rollback.
If the precheck reports issues, you must fix them manually and rerun the precheck operation. For
example, if you have created any new volumes or LUNs during preproduction testing, you must
delete them manually.
2. Click Generate Rollback Steps to generate the list of manual steps that you have to perform for
a successful rollback.
3. Click Save As CSV to save the manual steps in a file.
You can copy the rollback commands from the file and run them.
4. Depending on the transition phase from which you decide to roll back, perform the required
manual steps:
•
Import or preproduction testing phase
a. Run the rollback commands on the cluster and click Confirm.
b. Connect the 7-Mode disk shelves to the 7-Mode controllers, verify the cabling manually,
and click Confirm.
c. Run the rollback commands on the 7-Mode controllers and click Confirm.
d. View the configurations that are applied on the SVMs from the Operations History tab.
e. Manually remove all configurations that were applied by the tool from the SVMs.
•
Cabling phase
a. Connect the 7-Mode disk shelves to the 7-Mode controllers, verify the cabling manually,
and click Confirm.
You must ensure that the 7-Mode cabling matches the way it was at the start of the project.
Note: You should use Config Advisor to verify the cabling.
b. Run the rollback commands on the 7-Mode controllers and click Confirm.
c. Manually remove all configurations that were applied by the tool from the SVMs.
You can view the configurations that are applied on the SVMs from the Operations History
tab.
•
Export phase
a. Run the rollback commands on the 7-Mode controllers and click Confirm.
b. Manually remove all configurations that were applied by the tool from the SVMs.
You can view the configurations that are applied on the SVMs from the Operations History
tab.
•
SVM provision phase
Manually remove all configurations that were applied by the tool from the SVMs.
You can view the configurations that are applied on the SVMs from the Operations History
tab.
Manual steps for rolling back the transition on page 101
Performing a transition rollback to 7-Mode | 101
5. After completing all the manual steps, click Verify 7-Mode from the 7-Mode Transition Tool to
verify that the 7-Mode controllers are ready to serve data.
Manually rolling back the transition
You must perform some manual steps on the cluster and 7-Mode systems if you decide to roll back
the transition. The list of manual rollback steps is generated by the 7-Mode Transition Tool.
About this task
The rollback steps vary depending on the stage at which you decide to roll back. You must perform
all steps in this task if you decide to roll back after a successful import operation. If you decide to roll
back at an earlier stage, you have to perform a subset of these steps.
Steps
1. Log in to the cluster.
2. If any transitioned volume is in a SnapMirror relationship, choose one of the following actions:
•
If a transitioned volume is the destination of a SnapMirror relationship, delete the SnapMirror
relationship:
snapmirror delete -destination-path destination-path -source-path
source-path
•
If a transitioned volume is the source of a SnapMirror relationship, release the SnapMirror
relationship:
snapmirror release -destination-path destination-path -source-path
source-path
3. From the cluster, verify that the following operations are not running on the transitioned volumes:
a. Volume move operation:
volume move show
b. LUN move operation:
lun move show
c. LUN copy operation:
lun copy show
4. Perform the rollback for all of the 7-Mode aggregates:
a. Log in to the diagnostic privilege level:
set -privilege diagnostic
b. Revert the aggregates to the 7-Mode state by using the storage transition revert
start command.
This command requires additional parameters, such as the transition project ID and aggregate
attributes. You should use the complete command with the parameters and its values, as
generated by the 7-Mode Transition Tool.
c. Verify that the rollback is successful for all of the transitioned aggregates:
storage transition revert show-status
The status-code field for an aggregate is displayed as revert_complete when the
rollback is successful.
5. Reassign the disk ownerships from the target cluster nodes to the 7-Mode controllers:
102 | Copy-Free Transition Guide
a. Assign disk ownership to the 7-Mode controllers:
disk assign –disk disk_id –s system_id -force true
b. Verify that the disk ownership is assigned to the 7-Mode controllers:
storage disk show -fields owner-id
6. Remove the 7-Mode LIFs from the SVMs:
network interface delete -vserver svm_name -lif lif_name
7. Remove the copy-free transition restrictions on the target cluster nodes from the diagnostic
privilege level:
storage transition pre-commit end -session-id transition_project_id
You can also perform this step after the rollback operation is completed and the 7-Mode
controllers are operational.
8. Delete the transition project information about the target cluster nodes by using the following
diagnostic privilege level command:
storage transition purge-info -session-id transition_project_id
You can also perform this step after the rollback operation is completed and the 7-Mode
controllers are operational.
9. Optional: If disk ownership autoassigment was disabled on the cluster nodes during the export
and halt operation, enable it:
storage disk assign -auto true
10. Manually remove all of the configurations that the tool has transitioned to the target SVMs.
You can view the results of the SVM provision and import operations for information about the
configurations transitioned by the tool.
11. Remove the disk shelves from the target cluster nodes, and then reconnect them to the 7-Mode
controllers.
Tip: You should use the Config Advisor tool to verify the cabling.
12. Optional: If any 7-Mode disk shelf IDs were changed to resolve the conflicts with the disk shelf
IDs of the target cluster nodes, manually change them to the old IDs and power-cycle the disk
shelves for the new IDs to take effect.
13. Boot the source 7-Mode controllers in to the normal mode.
Find a System Administration Guide for your version of Data ONTAP 8
14. From one of the source 7-Mode controllers, enable the takeover capability:
cf enable
15. If automatic deletion of aggregate Snapshot copies was disabled during the export and halt
operation, enable it:
options snap autodelete aggr_name on
103
Copyright information
Copyright © 1994–2016 NetApp, Inc. All rights reserved. Printed in the U.S.
No part of this document covered by copyright may be reproduced in any form or by any means—
graphic, electronic, or mechanical, including photocopying, recording, taping, or storage in an
electronic retrieval system—without prior written permission of the copyright owner.
Software derived from copyrighted NetApp material is subject to the following license and
disclaimer:
THIS SOFTWARE IS PROVIDED BY NETAPP "AS IS" AND WITHOUT ANY EXPRESS OR
IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE,
WHICH ARE HEREBY DISCLAIMED. IN NO EVENT SHALL NETAPP BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE
GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,
STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN
ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE
POSSIBILITY OF SUCH DAMAGE.
NetApp reserves the right to change any products described herein at any time, and without notice.
NetApp assumes no responsibility or liability arising from the use of products described herein,
except as expressly agreed to in writing by NetApp. The use or purchase of this product does not
convey a license under any patent rights, trademark rights, or any other intellectual property rights of
NetApp.
The product described in this manual may be protected by one or more U.S. patents, foreign patents,
or pending applications.
RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the government is subject to
restrictions as set forth in subparagraph (c)(1)(ii) of the Rights in Technical Data and Computer
Software clause at DFARS 252.277-7103 (October 1988) and FAR 52-227-19 (June 1987).
104
Trademark information
NetApp, the NetApp logo, Go Further, Faster, AltaVault, ASUP, AutoSupport, Campaign Express,
Cloud ONTAP, Clustered Data ONTAP, Customer Fitness, Data ONTAP, DataMotion, Fitness, Flash
Accel, Flash Cache, Flash Pool, FlashRay, FlexArray, FlexCache, FlexClone, FlexPod, FlexScale,
FlexShare, FlexVol, FPolicy, GetSuccessful, LockVault, Manage ONTAP, Mars, MetroCluster,
MultiStore, NetApp Insight, OnCommand, ONTAP, ONTAPI, RAID DP, RAID-TEC, SANtricity,
SecureShare, Simplicity, Simulate ONTAP, Snap Creator, SnapCenter, SnapCopy, SnapDrive,
SnapIntegrator, SnapLock, SnapManager, SnapMirror, SnapMover, SnapProtect, SnapRestore,
Snapshot, SnapValidator, SnapVault, StorageGRID, Tech OnTap, Unbound Cloud, and WAFL and
other names are trademarks or registered trademarks of NetApp, Inc., in the United States, and/or
other countries. All other brands or products are trademarks or registered trademarks of their
respective holders and should be treated as such. A current list of NetApp trademarks is available on
the web.
http://www.netapp.com/us/legal/netapptmlist.aspx
105
How to send comments about documentation and
receive update notifications
You can help us to improve the quality of our documentation by sending us your feedback. You can
receive automatic notification when production-level (GA/FCS) documentation is initially released or
important changes are made to existing production-level documents.
If you have suggestions for improving this document, send us your comments by email.
doccomments@netapp.com
To help us direct your comments to the correct division, include in the subject line the product name,
version, and operating system.
If you want to be notified automatically when production-level documentation is released or
important changes are made to existing production-level documents, follow Twitter account
@NetAppDoc.
You can also contact us in the following ways:
•
NetApp, Inc., 495 East Java Drive, Sunnyvale, CA 94089 U.S.
•
Telephone: +1 (408) 822-6000
•
Fax: +1 (408) 822-4501
•
Support telephone: +1 (888) 463-8277
106 | Copy-Free Transition Guide
Index
32-bit aggregates
expanding to the 64-bit format 36
32-bit data
preparing to transition 7-Mode systems 36
32-bit Snapshot copies
finding and removing, after expanding aggregates to
64-bit 37
32-bit volumes
finding and removing, after expanding aggregates to
64-bit 37
64-bit aggregates
expanding 32-bit aggregates to 36
finding and removing 32-bit volumes or Snapshot
copies after expanding to 37
preparing to expand 32-bit to 64-bit 36
7-Mode
preparing for assessment 10
preparing for transition 26
7-Mode systems
applying configurations to SVMs 73
copy-free transition workflow 58
disconnecting the disk shelves 76
exporting information before transition 75
gathering cabling information for transition 31
guidelines for mapping controllers for transition 60
halting before transition 75
importing data to ONTAP during transition 78
preparing volumes and aggregates for copy-free
transition 34
restrictions and corrective action for copy-free
transition 35
rolling back a transition project 99
setting up remote access through the SP or RLM for
transition 27
using copy-free transition to clustered Data ONTAP
6
verifying cutover readiness 74
7-Mode systems with 32-bit data
preparing to transition 36
7-Mode transition
considerations for IP addresses 30
customizing and consolidating 7-Mode NFS export
rules 66
7-Mode Transition Tool
generating assessment reports by adding systems to
12
log files 96
network port requirements 25
A
aggregates
committing the project, transition 87
expanding to the 64-bit format 36
finding and removing 32-bit volumes or Snapshot
copies after expanding to 64-bit 37
restrictions and corrective action for copy-free
transition 35
space considerations for transition 38
applications
preproduction testing for transition 86
supported versions for transition assessment 10
assessment
host and storage inventory information 9
preparing for transition 9
preparing the 7-Mode system 10
when to perform while transitioning 6
assessment executive summary
how to use for transition 17
assessment reports
generating by adding systems to the 7-Mode
Transition Tool 12
B
blocked operations
preproduction testing phase 80
C
cabling
for copy-free transition 76
gathering information for transition 31
ignorable error categories 92
worksheet for planning the transition 33
CIFS
considerations for transitioning local users and
groups 52
preparing for transition 48
prerequisites to transition 48
rehosting volumes after transition 82
supported and unsupported configurations for
transition 50
clustered Data ONTAP
copy-free transition workflow 58
using copy-free transition from 7-Mode 6
clusters
adding for copy-free transition 59
connecting disk shelves to nodes 76
copy-free transition workflow 58
gathering cabling information for transition 31
preparing for transition 30
preparing to transition volume SnapMirror
relationships 56
collection
host and storage inventory information 9
comments
how to send feedback about documentation 105
commit operation
ignorable error categories 92
committing
copy-free transition 87
completing
copy-free transition 80
configurations
CIFS, supported for transition 50
Index | 107
customizing for transition 66
supported for FC zone plan 16
verifying after transition 85
configuring
zones by using the FC zone planner 53
considerations
for transitioning DNS, NIS, and LDAP
configurations 41
for transitioning netgroups and UNIX users and
groups 42
for transitioning NFS exports 45
space requirements for transitioning LUNs 55
considerations during 7-Mode volume transition
in nondefault IPspace 30
IP addresses 30
consolidating examples
7-Mode export rules for transition 67
7-Mode Snapshot schedules 67
controllers
adding for copy-free transition 59
assessing transition readiness of 11
generating assessment reports before transition 12
copy-free transition
applying SVM configurations 73
cabling 76
cabling worksheet 33
checking cutover readiness 74
committing 87
completing 80
Config Advisor 25
connecting disk shelves to target cluster nodes 76
disconnecting 7-Mode disk shelves 76
documentation required 25
exporting 7-Mode system and hardware information
75
gathering cabling information 31
ignorable errors 92
ignoring errors and continuing transition 92
importing 7-Mode data 78
LIFs to be transitioned 60
overview 6
performing manual configuration tasks 85
phases 19
preparing 23
preparing 7-Mode aggregates and volumes 34
preparing for CIFS transition 48
preparing for NFS transition 42
preparing network 29
preparing SAN 52
preparing to transition data protection features 56
preparing to transition name services configuration
40
preproduction testing 86
project planning worksheets 60
requirements 23
restrictions and corrective action for aggregates and
volumes 35
restrictions in preproduction phase 80
roll back to 7-Mode 99
rollback to 7-Mode, performing 99
space considerations for aggregates and Flash Pool
aggregates 38
supported disk shelves 23
supported ONTAP versions 23
supported platforms 23
SVM and volume mapping information 60
tools required 25
transitioning SnapMirror relationships 88, 90
verifying configurations 85
volume mapping information 60
workflow 19, 58
copy-free transition projects
planning 59
customizing
configurations for transition 66
cutover
verifying 7-Mode systems are ready 74
D
dashboard
prechecks 71
Data ONTAP
7-Mode versions supported for transition assessment
10
data protection relationships
preparing for transition 56
rehosting DP volumes after transition 82
supported for transition 56
disaster recovery configurations
supported and unsupported for transition 56
disk shelf models
supported for copy-free transition 23
disk shelves
connectivity, planning for transition 31
copy-free transition overview 6
disconnecting 7-Mode and cabling to cluster nodes
76
DNS configurations
considerations for transition 41
documentation
how to receive automatic notification of changes to
105
how to send feedback about 105
downloading
the log files 95
E
errors
continuing the transition 92
errors, ignorable
during import and commit 92
executive summary
how you can use it for transition assessment 17
expanding
aggregates to the 64-bit format 36
export and halt fails
troubleshooting 98
export rules, 7-Mode
example of consolidating for transition 67
exporting
7-Mode system and hardware information 75
108 | Copy-Free Transition Guide
F
failed to boot the 7-Mode controller in maintenance
mode
troubleshooting 98
failures
recovering from LUN transition 97
FC
rehosting volumes after transition 82
FC switches
assessing transition readiness of 11
generating assessment reports before transition 12
FC zone plan
supported configurations 16
FC zone planner
configuring zones 53
FC zone plans
generating by using the Inventory Collect Tool 15
feedback
how to send comments about documentation 105
files
collecting the logs 95
firmware
disks, supported for copy-free transition 23
Flash Pool aggregates
space considerations for transition 38
FlexVol volumes
finding and removing 32-bit, after expanding
aggregates to 64-bit 37
flowcharts
collecting and assessing inventory information 9
copy-free transition workflow 19
performing copy-free transition 58
G
generating an FC zone plan
for grouping the initiator hosts and targets after the
migration 15
groups, local
considerations for CIFS transition 52
H
HA pairs
copy-free transition of SnapMirror relationships 88
transitioning SnapMirror relationships 90
halting
7-Mode systems before transition 75
hosts
assessing transition readiness of 11
generating assessment reports before transition 12
SAN, preparing for transition 54
hosts, supported
versions for transition assessment 10
I
import operation
ignorable error categories 92
importing
7-Mode data to ONTAP during transition 78
inventory report XML file for transition assessment
14
information
how to send feedback about improving
documentation 105
initiator hosts
generating an FC zone plan for configuring switches
15
interface groups
preparing the network for transition 29
inventory information
collecting and assessing 9
inventory reports
importing for transition assessment 14
IP addresses
considerations for transition 30
IPspaces
preparing the network for transition 29
iSCSI
rehosting volumes after transition 82
L
LDAP configurations
considerations for transition 41
LIFs
guidelines for mapping for transition 60
SAN, creating before transition 52
LIFS
selecting for copy-free transition 59
local users and groups
considerations during CIFS transition 52
log files
7-Mode Transition Tool 96
logs
downloading 7-Mode transition Tool logs 95
LUN.vol.proc.fail.no.space
cause and corrective action if transition fails 55
LUNs
recovering from transition failure 97
M
migration
downloading the log files 95
generating an FC zone plan for configuring switches
15
when to perform while transitioning 6
mirror relationships
transitioning SnapMirror relationships 88, 90
transitioning SnapMirror relationships, staggered 88
mixed-format volumes
finding and removing after expanding aggregates to
64-bit 37
ifgrps
See interface groups
ignorable errors
during import and commit 92
N
name services
Index | 109
preparing for transition 40
supported configurations for transition 40
netgroups
considerations for transitioning 42
network ports
requirements 25
network preparation
copy-free transition 29
NFS
preparing for transition 42
prerequisites to transition 43
rehosting volumes after transition 82
supported configurations for transition 43
unsupported configurations for transition 43
NFS export rules
consolidating for transition 66
NFS exports
transition considerations 45
NIS configurations
considerations for transition 41
nodes
connecting disk shelves 76
O
ONTAP versions
supported for copy-free transition 23
operational changes
when to perform while transitioning 6
overview
transition 6
P
phases of copy-free transition
cabling 19
committing 19
exporting and halting 19
importing 19
planning 19
preproduction testing 19
SVM provisioning 19
planning
adding controllers and clusters 59
configurations for transition 66
copy-free transition projects 59
mapping SVMs and volumes 59
selecting LIFs 59
selecting source systems 59
selecting target cluster 59
when to perform while transitioning 6
policies, export
resuse for transition 66
policies, Snapshot
reusefor transition 66
ports
requirements 25
post-transition tasks
completing 80
performing tasks listed in the precheck 85
volume rehosting 82
prechecks
error 72
ignorable error categories 92
information 72
notification 72
severity levels 72
warning 72
preparing
7-Mode HA pair for transition 26
7-Mode system for assessment 10
aggregates and volumes for copy-free transition 34
CIFS for copy-free transition 48
cluster for transition 30
for transition 23
name services for copy-free transition 40
SAN configurations for transition 52
SAN hosts for transition 54
setting up the SP or RLM for transition 27
transitioning volume SnapMirror relationships 56
preparing for transition
creating SAN LIFs 52
preproduction testing
operations that are blocked and are not
recommended 80
projects
assigning to project groups 59
planning copy-free transition 59
protocols
preparing the 7-Mode system for assessment 10
R
recovering
from a failed LUN transition 97
rehosting volumes
NAS 82
SAN 82
remote access
setting up the SP or RLM to access 7-Mode systems
for transition 27
reports
importing inventory reports for transition assessment
14
reports, assessment
generating by adding systems to the 7-Mode
Transition Tool 12
requirements
7-Mode system and hosts supported for transition
assessment 10
7-Mode Transition Tool 25
copy-free transition 23
for transitioning CIFS configurations 48
for transitioning NFS configurations 43
restrictions
in the transition preproduction testing phase 80
RLM
setting up to access 7-Mode systems for transition 27
rollback
performing a transition 99
to 7-Mode, transition 99
transition, manual steps 101
rolling back
transition, manual steps 101
110 | Copy-Free Transition Guide
S
SAN configurations
preparing for transition 52
supported for transition 54
SAN hosts
preparing for transition 54
SAN LIFs
creating, before transition 52
SAN transition
space considerations 55
SAN volumes
space requirements for transitioning LUNs 55
selecting
configurations for transition 66
SnapMirror relationships
performing copy-free transition 88, 90
performing copy-free transition, staggered 88
preparing for copy-free transition 56
supported and unsupported configurations for
transition 56
Snapshot copies
finding and removing 32-bit, after expanding
aggregates to 64-bit 37
Snapshot policies
reuse for transition 66
Snapshot schedules, 7-Mode
example of consolidating for transition 67
source systems
selecting for copy-free transition 59
SP
setting up to access 7-Mode systems for transition 27
space considerations
for aggregates before transition 38
when transitioning SAN volumes 55
storage transition
using copy-free transition, overview 6
suggestions
how to send feedback about documentation 105
support
when to call during transition rollback 99
supported configurations
data protection transition 56
for transition 50
name services transition 40
NFS transition 43
SAN transition 54
SVMs
applying configurations from 7-Mode 73
guidelines for mapping for transition 60
mapping volumes, copy-free transition 59
switches
FC, assessing transition readiness of 11
generating an FC zone plan for configuring 15
T
target clusters
selecting for copy-free transition 59
targets
generating an FC zone plan for configuring switches
15
technical support
when to call during transition rollback 99
testing
workloads and applications 86
transition
assessing controllers, hosts, and switches are ready
for 11
assessing hosts and controllers for 9
CIFS configuration prerequisites 48
CIFS configurations supported for transition 50
considerations for local users and groups 52
copy-free transition cabling worksheet 33
copy-free, applying SVM configurations 73
copy-free, committing 87
copy-free, overview 6
copy-free, preparing 7-Mode aggregates and
volumes 34
copy-free, restrictions and corrective action 35
copy-free, workflow 19, 58
creating SAN LIFs before 52
disk shelf connectivity, gathering information 31
downloading the log files 95
generating assessment reports by adding systems to
the 7-Mode Transition Tool 12
how to use the execute summary for assessment 17
importing inventory report XML file for readiness
check 14
manual steps for rolling back after import 101
NFS configuration prerequisites 43
NFS, preparing for 42
overview 6
preparing CIFS configurations for 48
preparing for 23
preparing name services for 40
preparing the 7-Mode HA pair 26
preparing the cluster for 30
preparing to transition data protection 56
rolling back a transition project 99
severity levels of precheck messages 72
supported and unsupported name services
configurations 40
supported and unsupported NFS configurations 43
supported and unsupported SAN configurations 54
troubleshooting issues 92
transition assessment
7-Mode system and hosts supported for 10
transition considerations
DNS, NIS, and LDAP 41
transition failures
recovering from a failed LUN 97
transition issues
continuing transition with errors 92
transition projects
prechecks,run 71
transition rollback
when to call technical support 99
transition terminology
7-Mode Transition Tool, to understand the transition
process 8
transition terminology related to the 7-Mode Transition
Tool
to understand the transition process 8
transitioning
Index | 111
netgroups and UNIX users and groups,
considerations for 42
preparing to transition 36
transitions
running prechecks 71
troubleshooting
export and halt fails 98
failure to boot the 7-Mode controller in maintenance
mode 98
transition issues 92
workaround to boot in maintenance mode 98
Twitter
how to receive automatic notification of
documentation changes 105
U
performing copy-free transition 88, 90
preparing for copy-free transition 56
supported and unsupported configurations for
transition 56
volumes
finding and removing 32-bit and mixed-format, after
expanding aggregates to 64-bit 37
finding and removing 32-bit, after expanding
aggregates to 64-bit 37
guidelines for mapping controllers for transition 60
mapping to SVMs, copy-free transition 59
rehosting, post-transition 82
restrictions and corrective action for copy-free
transition 35
space requirements for transitioning LUNs 55
transitioning a SnapMirror relationship 88, 90
UNIX users and groups
considerations for transitioning 42
unsupported configurations
data protection transition 56
for transition 50
name services transition 40
NFS transition 43
SAN transition 54
users, local
considerations for CIFS transition 52
W
V
Z
verifying
cutover readiness 74
vFiler units
applying configurations to SVMs 73
VLANs
preparing the network for transition 29
volume SnapMirror relationships
zones
configuring by using the FC zone planner 53
generating FC zone plan for migration 15
supported FC zone plans for migration 16
workflows
collecting and assessing inventory information 9
copy-free transition 19, 58
workloads
preproduction testing for transition 86
worksheets
cabling worksheet for transition 33
sample for planning a transition project 60