Skip to main content
NetApp Knowledge Base

CBT : How to provide all the required primary 7-Mode details for a given secondary project

Views:
348
Visibility:
Public
Votes:
0
Category:
7-mode-transition-tool
Specialty:
7dot
Last Updated:

Applies to

7-Mode Transition Tool

Answer

CBT : How to provide all the required primary 7-Mode details for a given secondary project

At a high level, the following steps describe the process involved in the transition of primary and secondary 7-Mode volumes and how to retain the SnapMirror relationships during the transition:

  1. Compose a secondary project with all the secondary 7-Mode volumes. 
  2. Compose a primary project with all the primary 7-Mode volumes.
  3. Add the primary 7-Mode details to the secondary project and add secondary cluster SVM details to the primary project.
  4. Start baseline and complete (cutover) the secondary project first. During the complete operation of the secondary project, 7-Mode Transition Tool creates SnapMirror relationships between 7-Mode primary volumes and secondary cluster SVM volumes.
  5. Start baseline and complete the primary project. Primary project complete (cutover) operation must happen only after the completion (cutover) of secondary project. During the complete operation of the primary project, 7-Mode Transition Tool deletes SnapMirror relationships between 7-Mode primary volumes and secondary cluster SVM volumes, and creates SnapMirror relationships between primary cluster SVM volumes and secondary cluster SVM volumes.

While transitioning secondary volumes (volumes that are destination of SnapMirror relationships) using 7-Mode Transition Tool CLI, you must provide the primary 7-Mode storage systems details to the project. These details are required to create volume SnapMirror relationships between 7-Mode primary volumes to clustered Data ONTAP secondary volumes during the Complete (cutover) operation of secondary projects.

Without the primary 7-Mode storage system details added to the secondary project, tool will not be able to create the required volume SnapMirror relationships between 7-Mode primary volumes and clustered Data ONTAP secondary volumes during the Complete (cutover) operation of secondary projects.

For 7MTT versions earlier to 3.0, tool will produce a warning if all the required primary 7-Mode storage system details are not added to the project.

From 3.0 or later versions of the 7MTT, tool will provide a ignorable blocking error during the precheck operation if all the required primary 7-Mode storage system details are not added to the project.

Procedure:

The 7MTT command that can be used to provide primary 7-Mode system details to the secondary project is as follows:

For 7MTT v3.0 or later releases: 
transition cbt add-primary-seven-mode-system -p <project-name> -h <primary-7-mode-host> -f <management-ipaddress> -d <data-copy-ipaddress> -m <multipathing-ipaddress>

For 7MTT releases earlier to v3.0:
transition add-primary-seven-mode-system -s <project-name> -h <primary-7-mode-host> -f <management-ipaddress> -d <data-copy-ipaddress> -m <multipathing-ipaddress> 

Valid options are as follows
-p/-s <project-name>             - Name of the project
-h <primary-7-mode-host>         - FQDN or IP address of the primary 7-Mode system of data-protection relationship
-f <management-ipaddress>       - Management IP address of the source host
-d <data-copy-ipaddress>         - IP address over which data is copied
-m <multipathing-ipaddress>  - Additional IP address that is used for data copy
    
The 'primary-7-mode-host' value must be the primary 7-Mode storage system name as seen by the secondary 7-Mode system.
For example, if the SnapMirror relationship entry is as seen below in the secondary 7-Mode system:

secondary::>snapmirror status secondary-volume
Source                         Destination                        
source-name:primary-volume     secondary-host:secondary-volume    

    
Here 'source-name' can either be FQDN or IP address of primary 7-Mode controller or it can be a connection name.
    
Primary 7-Mode FQDN or IP address:

If the 'source-name' represents FQDN or IP address of primary 7-Mode controller, this value must be provided for 'primary-7-mode-host' field.
    
Connection Name:

If the 'source-name' represents a connection name and if the connection is defined as below:

source-name = connection-mode(source-fqdn-or-ip1,dest-fqdn-or-ip1) (source-fqdn-or-ip2,dest-fqdn-or-ip2)

In this case, the 'primary-7-mode-host' value provided must be one of 'source-fqdn-or-ip1' or 'source-fqdn-or-ip2'.

For 3.0 or later versions of the 7-Mode Transition Tool:

If you want to ignore the blocking error produced by the 7-Mode Transition Tool and continue with the transition, run the following command on the host where 7-Mode Transition Tool is running and then re-run the operation. 

transition cbt ignorableerrors add -p <project-name>  -c ignore-secondary-snapmirror-source-check

Note: This command is available only from 3.0 version of the 7-Mode Transition Tool.

 

Additional Information

For more information, see the 7-Mode Transition Tool Copy-Based Transition Guide.

 

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.