Request doc changes
Edit this page
Learn how to contribute
Copy-based transition workflow
The copy-based transition workflow involves preparing for migration, migrating data and configurations, and performing post-transition configurations.
-
PDF of this doc site
-
Copy-based transition
-
Copy-free transition
-
Collection of separate PDF docs
Creating your file...
This may take a few minutes. Thanks for your patience.
Your file is ready
- 7-Mode Transition
- Release Notes
-
Command map for 7-Mode administrators
-
7-Mode Transition Tool installation and administration
-
Transition to clustered ONTAP by using the 7-Mode Transition Tool
-
Installing or uninstalling the 7-Mode Transition Tool on a Windows system
- System requirements for installing the 7-Mode Transition Tool on Windows systems
- Installing the 7-Mode Transition Tool on a Windows system
- Enabling login for users not part of the Administrator group
- Logging in to the 7-Mode Transition Tool
- Uninstalling the 7-Mode Transition Tool on a Windows system
-
Installing or uninstalling the 7-Mode Transition Tool on Linux (Copy-based transition only)
- Modifying the configuration options of the 7-Mode Transition Tool
-
Troubleshooting issues
-
-
Copy-based transition
-
Transition overview
-
Collecting and assessing the inventory information
- Copy-based transition workflow
-
Data and configuration migration process
-
Preparing for copy-based transition
- Requirements for copy-based transition
- Port requirements for communicating with the 7-Mode Transition Tool
- Restrictions for transition
- Preparing the 7-Mode system for transition
-
Preparing the network for transition
- Preparing the cluster for transition
-
Preparing 7-Mode aggregates and volumes for transition
-
Support for transitioning SnapLock volumes
- Considerations for transitioning of SnapLock Enterprise volumes
- Considerations for transitioning of SnapLock Compliance volumes
- Considerations for transitioning of SnapLock Audit volumes
- Considerations for transitioning of 7-Mode SnapLock options
- Considerations for using Chain of Custody verification for 7-Mode SnapLock volumes
-
Preparing to transition name services
-
Preparing for NFS transition
-
Preparing for SMB/CIFS transition
- Preparing for MetroCluster configuration transition
-
Preparing for SAN transition
-
Preparing data protection features for transition
- Guidelines for deciding when to perform cutover
- Impact of takeover and giveback on transition
-
Migrating data and configuration from 7-Mode volumes
- Transition preparation checklist
- Adding controllers and clusters
- Creating a transition project
- Customizing the transition of 7-Mode configurations
-
Running prechecks
- Starting baseline data copy
- Applying 7-Mode configurations
- Configuring zones by using the FC zone plan
- Performing on-demand SnapMirror updates
- Completing a transition project
- Completing the Chain of Custody verification
-
Transitioning volumes by using the 7-Mode Transition Tool CLI
- Scenarios for selecting volumes in a project
-
Transitioning volumes by using the 7-Mode Transition Tool CLI
- Commands for managing transition
-
Performing manual post-transition tasks
- Configuring zones by using the FC zone plan
- Recovering from a failed LUN transition
- Viewing transitioned SAN configurations
- Limitations with 7-Mode Snapshot copies of LUNs managed by SnapDrive and SnapManager after transition
- Configuring cron job schedules on the remote site after transitioning a MetroCluster configuration
- Deleting 7-Mode volume Snapshot copies from transitioned volumes
- Consolidating cron schedules from transitioned volumes
-
Managing a transition project
-
Troubleshooting issues
- Downloading transition log files
- Log files for the 7-Mode Transition Tool
-
Continuing with the transition if ignorable errors occur
- Transitioning a MetroCluster configuration that failed due to switchover or switchback
- Cannot select a secondary volume from the Volume selection pane
- Cannot select a volume for transition if the tool fails to retrieve the volume information
- Cannot proceed from the Volume mapping pane if the selected SVM has no aggregate
- Compression is not enabled after transition from Data ONTAP 7.3.x
-
-
Copy-free transition
-
Transition overview
-
Collecting and assessing the inventory information
-
Copy-free transition workflow
-
Preparing for copy-free transition
- Requirements for copy-free transition
- Tools and documentation required for copy-free transition
- Port requirements for communicating with the 7-Mode Transition Tool
- Preparing the 7-Mode HA pair for transition
- Setting up the SP or RLM on the 7-Mode systems for copy-free transition
-
Preparing the network for transition
- Preparing the cluster for transition
-
Gathering cabling information for transition
-
Preparing 7-Mode aggregates and volumes for transition
-
Preparing to transition name services
-
Preparing for NFS transition
-
Preparing for SMB/CIFS transition
-
Preparing for SAN transition
-
Preparing data protection features for transition
-
Transitioning 7-Mode aggregates using copy-free transition
-
Planning a copy-free transition project
- Applying SVM configurations
- Verifying that 7-Mode systems are ready for cutover
- Exporting storage configurations and halting 7-Mode systems
- Disconnecting disk shelves from the 7-Mode system and connecting to cluster nodes
- Importing 7-Mode data to ONTAP
-
-
Completing the transition
-
Transitioning a SnapMirror relationship
-
Troubleshooting transition issues
-
Performing a transition rollback to 7-Mode
-
-
Host and Storage Information Collection Guide
-
Collecting storage and host inventory information
- ONTAP target releases supported by the 7-Mode Transition Tool
- System requirements for running the Inventory Collect Tool
- Storage, host, and FC switches version requirements for inventory collection
- Preparing the 7-Mode systems and hosts for inventory collection
- Supported configurations for generating an FC zone plan
- Syntax and options
- Collecting inventory and generating inventory report
- Generating the FC zone plan
- Collection and assessment commands
- Where to find information about transition assessment
-
-
7-Mode data transition using SnapMirror
-
Transitioning 7-Mode volumes using SnapMirror
- Transitioning a disaster recovery relationship between vFiler units
-
Recovering from a disaster at the 7-Mode site during transition
-
Troubleshooting transition issues when using SnapMirror
-
-
SAN host transition and remediation
- ONTAP target releases supported by the 7-Mode Transition Tool
- 7-Mode Transition Tool transition phases
-
VMware ESXi host remediation
- ESXi versions and features supported for SAN transitions using 7MTT
-
Preparing for transition of ESXi hosts
- Testing transitioned LUNs and ESXi host applications before the cutover phase of copy-based transitions
- Downtime at apply configuration (precutover) phase of ESXi host transition
-
Post-transition remediation requirements for ESXi hosts
- Preparing for post-transition ESXi host remediation
- Reregistering VMs after transition on non-SAN boot ESXi hosts using vSphere Client
- Reconfiguration of VMware software iSCSI initiator after transition
- Setting up ESXi hosts configured for SAN boot after transition
-
Determining whether VMFS volumes need to be remounted after transition
-
Reattaching RDM LUNs to VMs
- Post-transition remediation for Linux and Windows guest operating systems
- Recommended settings for ESXi hosts after transition remediation
- Enabling CAW on a datastore using the ESXi CLI
-
RHEL host remediation
-
Gathering pretransition information from the Inventory Assessment Workbook
-
Transitioning RHEL DMMP devices without file systems
- Verifying that RHEL LUNs are ready for transition using the Inventory Assessment Workbook
- Verifying that RHEL 5 LUNs are ready for transition using the CLI
- Verifying that RHEL 6 DDMP devices are ready for transition using CLI
- Testing DMMP devices without file systems on RHEL hosts before the cutover phase of copy-based transitions
- Preparing for cutover when transitioning a Linux host DMMP device without a file system
- Replacing 7-Mode LUN WWIDs on Linux hosts after transition of LUNs
-
Transitioning LUNs with mount points using DMMP device names
- Preparing RHEL LUNs with mount points using DMMP device names for transition using the Inventory Assessment Workbook
- Preparing RHEL LUNs with mount points using DMMP alias names for transition using the CLI
- Testing DMMP devices with file systems on RHEL hosts before the cutover phase of copy-based transitions
- Preparing for the cutover phase when transitioning LUNs with mount points using DMMP device names on Linux hosts
- Remounting DMMP devices on Linux hosts after transition
-
Transitioning LUNs with mount points using DMMP alias names
- Preparing RHEL LUNs with mount points using DMMP alias names for transition using the CLI
- Testing LUNs with mount points using DMMP alias names on RHEL hosts before the cutover phase of copy-based transitions
- Preparing for the cutover phase when transitioning LUNs with mount points using DMMP device names on Linux hosts
- Remounting LUNs with mount points using DMMP alias names on Linux hosts after transition
-
Transitioning Linux host file systems on LVM devices
-
Transitioning of SAN boot LUNs
- Types of SAN boot LUNs supported for transition
- Preparing for transition of FC or FCoE SAN boot LUNs on RHEL hosts
- Preparing for transition of iSCSI SAN boot LUNs
- Testing SAN boot LUNs on RHEL hosts before the cutover phase of copy-based transitions
- Preparing for the cutover phase when transitioning SAN boot LUNs
- Discovering SAN boot LUNs after transition
-
-
Windows host remediation
-
HP-UX host remediation
-
Transitioning HP-UX host LUNs with file systems
-
Transitioning HP-UX host SAN boot LUNs with FC/FCoE configurations
- Preparing to transition SAN boot LUNs on HP-UX hosts with FC configurations
- Testing transitioned SAN boot LUNs on HP-UX hosts before the cutover phase of copy-based transitions
- Preparing for the cutover phase when transitioning SAN boot LUNs
- Making a SAN boot LUN the primary boot LUN for HP-UX Emulex HBAs after transition
- Making a SAN boot LUN the primary boot LUN for HP-UX QLogic HBAs after transition
-
-
AIX host remediation
-
Transition of SAN boot LUNs on AIX hosts with FC/FCoE configurations
- Preparing to transition SAN boot LUNs on AIX hosts with FC/FCoE configurations
- Testing transitioned SAN boot LUNs on AIX hosts before the cutover phase of copy-based transitions
- Preparing for the cutover phase when transitioning AIX hosts with FC/FCoE configurations.
- Booting from SAN boot LUN on AIX hosts with FC/FCoE configurations after transition
-
Transitioning AIX host data LUNs with file systems
-
-
Solaris host remediation
-
Transitioning Solaris host data LUNs with ZFS file systems
- Preparing to transition Solaris host data LUNs with ZFS file system
- Testing data LUNs on Solaris hosts with ZFS file system before the cutover phase of copy-based transitions
- Preparing for cutover phase when transitioning Solaris host data LUNs with ZFS file systems
- Mounting Solaris host LUNs with ZFS file systems after transition
-
Transitioning Solaris host data LUNs with Sun Volume Manager
- Preparing to transition Solaris host LUNs with Sun Volume Manager
- Testing data LUNs on Solaris hosts with Sun Volume Manager before the cutover phase of copy-based transitions
- Preparing for cutover phase when transitioning Solaris host Sun Volume Manager data LUNs
- Mounting Solaris host LUNs with Solaris Volume Manager after transition
-
-
Rolling back LUNs to 7-Mode after transition
- Legal notices