How you transition a stand-alone volume

Contributors ntap-bmegan netapp-ivanad Download PDF of this page

Transitioning a stand-alone volume includes different phases: preparation, data copy, apply configuration (precutover), and storage cutover. After completing transition, you must perform some post-transition steps before resuming client access. Understanding what occurs during each phase helps you manage your transition efficiently.

The following illustration describes different phases of transition
Phase Steps

Preparation

  1. Gathering information

  2. Performing the precheck

  3. Creating data copy schedules

Data copy

  1. Creating the ONTAP volumes as read-only

  2. Creating a transition peer relationship

  3. Establishing a SnapMirror relationship

  4. Performing a baseline transfer

  5. Performing scheduled incremental updates

Precutover

  1. Breaking the SnapMirror relationship

  2. Applying configurations to the SVM

  3. Configuring data LIFs on the SVM

  4. Testing data and configurations (manual and only for precutover RW)

  5. Resynchronizing ONTAP volumes with corresponding 7-Mode volumes

Storage cutover

  1. Disconnecting client access (manual)

  2. Performing a final SnapMirror update

  3. Breaking the SnapMirror relationship

  4. Removing 7-Mode IP addresses and setting the data LIFs to the up state on the SVM

  5. Taking the source volume offline

After cutover, performing post-transition steps and enabling client access (manual)

Chain of Custody verification for SnapLock volumes

  1. Enumerating all of the WORM files from 7-Mode volumes

  2. Calculating the fingerprint for each WORM file on the 7-Mode volumes (enumerated in the previous step) and calculating the fingerprint for the corresponding WORM file on the transitioned ONTAP volumes

  3. Generating a report with details about the number of files with matched and unmatched fingerprints, and the reason for the mismatch

Preparation phase

In this phase, information about the 7-Mode system and the cluster, volumes, and IP addresses is collected. The 7-Mode Transition Tool performs the following tasks in this phase:

  1. Collects and adds 7-Mode storage system and volume information.

  2. Runs the transition precheck.

  3. Collects and adds cluster, SVM, and aggregate information.

  4. Collects IP addresses that must be configured on the SVM:

    • Selects the IP addresses that exist on the 7-Mode system.

    • Specifies new IP addresses that must be configured on the SVM. NOTE: Transitioning of iSCSI and FC LIFs (SAN) is not supported by the tool. You must manually configure SAN LIFs on the SVM before transition.

  5. Creates data copy schedules for baseline copy and incremental updates.

  6. If the project contains SnapLock volumes, collects information about the read-write SnapLock volumes for which Chain of Custody verification is required and the details of the ONTAP volume that stores the fingerprint data that is generated during the Chain of Custody verification operation.

    The Chain of Custody verification operation is supported only for volumes with file names that have only ASCII characters.
  7. Plans configuration transition by selecting the 7-Mode configurations that must be transitioned to the target SVM and target volumes.

You should not modify the objects (volumes, IP addresses, system information, and so on) on the controller after fixing the errors and warnings that are reported during the precheck.

Data copy phase

In this phase, data from the 7-Mode volumes is copied to the ONTAP volumes. The 7-Mode Transition Tool performs the following tasks in this phase:

  1. Creates the ONTAP volumes with read-only access.

  2. Set up a transition peer relationship between the 7-Mode system and the SVM.

  3. Establishes a transition SnapMirror relationship (relationship of type TDP) between the 7-Mode volumes and ONTAP volumes.

  4. Completes the baseline data copy transfer based on schedule inputs.

  5. Performs scheduled incremental updates to the ONTAP volumes.

Apply configuration (precutover) phase

It is a best practice to run precutover operation a few days or weeks before the planned cutover window. This activity is to verify whether all the configurations are applied properly and whether any changes are required.

In this phase, configurations from the 7-Mode volumes are copied to ONTAP volumes.

There are two modes for the apply configuration (precutover) phase: precutover read-only and precutover read/write.

The precutover read/write mode is not supported when the project contains:

  • SAN volumes and the target cluster is running Data ONTAP 8.3.1 or earlier

    In this situation, the following configurations are not applied in the apply configuration (precutover) phase. Instead, they are applied during the cutover phase.

    • SAN configurations

    • Snapshot Schedule configurations

  • SnapLock Compliance volumes

    If the project contains SnapLock Compliance volumes, then the Snapshot Schedule configurations are not applied in the apply configuration (precutover) phase. Instead, these configurations are applied during the cutover phase.

If the target cluster is running Data ONTAP 8.3.1 or earlier, and you want to run the apply configuration (precutover) operation in read/write mode for NAS volumes, then you must create separate projects for the NAS volumes and SAN volumes. This action is required because the precutover read/write mode is not supported if you have SAN volumes in your project.

If the project contains SnapLock Compliance volumes, and you want to run the apply configuration (precutover) operation in read/write mode for non-SnapLock Compliance volumes, then you must create separate projects for SnapLock Compliance volumes and non-SnapLock Compliance volumes. This action is required because the precutover read/write mode is not supported if you have SnapLock Compliance volumes in your project.

The tool performs the following steps in the precutover read-only mode:

  1. Performs an incremental update from 7-Mode volumes to ONTAP volumes.

  2. Breaks the SnapMirror relationship between 7-Mode volumes and ONTAP volumes.

    For SnapLock Compliance volumes, the SnapMirror relationship between the 7-Mode volume and ONTAP volumes is not broken. The SnapMirror relationship is not broken because the SnapMirror resynchronization operation between 7-Mode and ONTAP volumes is not supported for SnapLock Compliance volumes.
  3. Collects configurations from 7-Mode volumes, and applies the configurations to the ONTAP volumes and the SVM.

  4. Configures the data LIFs on the SVM:

    • Existing 7-Mode IP addresses are created on the SVM in the administrative down state.

    • New IP addresses are created on the SVM in the administrative up state.

  5. Resynchronizes the SnapMirror relationship between 7-Mode volumes and ONTAP volumes

The tool performs the following steps in the precutover read/write mode:

  1. Performs an incremental update from 7-Mode volumes to ONTAP volumes.

  2. Breaks the SnapMirror relationship between 7-Mode volumes and ONTAP volumes.

  3. Collects configurations from 7-Mode volumes, and applying the configurations to the ONTAP volumes and the SVM.

  4. Configures the data LIFs on the SVM:

    • Existing 7-Mode IP addresses are created on the SVM in the administrative down state.

    • New IP addresses are created on the SVM in the administrative up state.

  5. Makes the ONTAP volumes available for read/write access.

    After you apply the configuration, the ONTAP volumes are available for read/write access so that read/write data access can be tested on these volumes during apply configuration (precutover) testing. You can manually verify the configurations and data access in ONTAP.

  6. Resynchronizes the ONTAP volumes when "finish testing" operation is triggered manually.

Storage cutover phase

The 7-Mode Transition Tool performs the following tasks in this phase:

  1. Optional: Performs an on-demand SnapMirror update to reduce the downtime after cutover.

  2. Manual: Disconnect client access from the 7-Mode system.

  3. Performs a final SnapMirror update from 7-Mode volumes to ONTAP volumes.

  4. Breaks and deletes the SnapMirror relationship between the 7-Mode volumes to ONTAP volumes, making the ONTAP volumes read/write.

    If the selected volume is a SnapLock Compliance volume and the volume is the destination of a SnapMirror relationship, then the SnapMirror relationship between the 7-Mode volume and the ONTAP volume is deleted without a SnapMirror break operation. This action is performed to ensure that secondary ONTAP SnapLock Compliance volumes remain in read-only mode. The secondary ONTAP SnapLock Compliance volumes must be in read-only mode for the resynchronization operation to be successful between the primary and secondary SnapLock Compliance volumes.

  5. Applies Snapshot schedules configuration if:

    • The target cluster is running clustered Data ONTAP 8.3.0 or 8.3.1 and project contains SAN volumes.

    • The project contains SnapLock compliance volumes.

  6. Applies SAN configurations, if the target cluster is running Data ONTAP 8.3.1 or earlier.

  7. Applies quota configurations, if any.

  8. Removes the existing 7-Mode IP addresses selected for transition from the 7-Mode system and brings the data LIFs on the SVM to the administrative up state.

    SAN LIFs are not transitioned by the 7-Mode Transition Tool.
  9. Optional: Takes the 7-Mode volumes offline.

Chain of Custody verification process for SnapLock volumes

You must perform the Chain of Custody verification operation. The tool performs the following operations when a Chain of Custody verification is initiated:

  1. Enumerates all of the WORM files from 7-Mode volumes.

  2. Calculates the fingerprint for each WORM file on the 7-Mode volumes (enumerated in the previous step) and calculates the fingerprint for the corresponding WORM file on the transitioned ONTAP volumes.

  3. Generates a report with details about the number of files with matched and unmatched fingerprints, and the reason for the mismatch.

  • The Chain of Custody verification operation is supported only for read-write SnapLock volumes that have file names with only ASCII characters.

  • This operation can take a significant amount of time based on the number of files on the 7-Mode SnapLock volumes.

Post-transition steps

After the storage cutover phase finishes successfully and the transition is completed, you must perform some post-transition manual tasks:

  1. Perform the required steps to configure features that were not transitioned or were partially transitioned, as listed in the precheck report.

    For example, IPv6 and FPolicy must be configured manually after transition.

  2. For SAN transition, reconfigure the hosts.

  3. Ensure that the SVM is ready to serve data to the clients by verifying the following:

    • The volumes on the SVM are online and read/write.

    • The IP addresses are up and reachable on the SVM.

  4. Redirect client access to the ONTAP volumes.

Related information