Creating a transition project

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

You can create a transition project that identifies the 7-Mode objects to be transitioned and how they map to the ONTAP objects. While creating the project, the 7-Mode Transition Tool collects and saves the information about the transition objects. You can use this project information to perform the transition in stages.

You must have gathered the following information:

  • Project type: Possible values are stand-alone, primary, or secondary

  • FQDN or IP address of the 7-Mode storage system or the default vFiler unit, if MultiStore is licensed

  • Administrative user name and password of the 7-Mode storage system

  • List of 7-Mode volumes

  • FQDN of the cluster or IP address of the cluster-management LIF

  • SVM name

Steps
  1. From the Start menu, click All Programs > NetApp 7-Mode Transition Tool > NetApp 7-Mode Transition Tool (CLI) 3.0 to open the 7-Mode Transition Tool command prompt.

  2. Add the user name and password of the systems that are a part of the transition project:

    transition credentials add -h host_name -u user_name

    host_name is FQDN or IP address of the 7-Mode system or cluster.

    user_name is the administrative user name for the system.

    You must repeat this step for each storage system that you want to add to the transition projects.
    7-Mode Transition Tool>transition credentials add -h system1.example.com -u root
    Enter password for 'root@system1.example.com':
  3. Create a transition project:

    transition cbt create -p project_name -t project_type -n 7-Mode_system -c data-copy-ipaddress [-f vfiler_name] [-h cluster -v vserver_name

    project_name is the name of the transition project.

    project_type is the project type. Valid values are standalone, secondary, or primary.

    7-Mode_system is the FQDN or IP address of the 7-Mode system.

    cluster is the FQDN of the cluster or IP address of the cluster-management LIF.

    The host names of your 7-Mode system and cluster must be the same as those you had provided while creating the project.

    data-copy-ipaddress is the IP address over which data is copied.

    vfiler_name is the name of the nondefault vFiler unit.

    vserver_name is the name of the SVM.

    For a new SVM, you must provide the aggregate name of the root volume of the SVM with the -g option.
    7-Mode Transition Tool>transition cbt create -p sample_project -t standalone -n system1.example.com -n 10.238.55.33 -h cluster1.example.com -v vs2

    The transition project moves to the preparation state.

  4. Add the 7-Mode volume and ONTAP volume to the project:

    transition cbt volumepair add -p project_name -v 7-Mode_volume -c vserver_volume -g aggr_name -t

    7-Mode_volume is the 7-Mode volume name.

    vserver_volume is the ONTAP volume on the SVM.

    You can also add an ONTAP volume for which the baseline transfer has been completed. When you add such a volume in the preparation phase, only incremental transfers are performed during the data copy phase.

    aggr_name is the aggregate on which the ONTAP volume vserver_volume is created during the start operation.

    -t is used when a volume which is in SnapMirror relationships must be transitioned as standalone volume.

    When a volume is transitioned as standalone volume, SnapMirror relationships are not preserved during the transition.

    For SnapLock Compliance volumes that are in SnapMirror relationship, the transition of SnapMirror relationships for SnapLock Compliance volumes is not automated by the 7-Mode Transition Tool. All SnapLock Compliance volumes that are in SnapMirror relationship must be transitioned as standalone volumes (by specifying the flag -t) by including the volumes in standalone, primary, or secondary projects. You must then manually perform the SnapMirror resychronization operation between these volumes after the transition.

    7-Mode Transition Tool>transition cbt volumepair add -p sample_project -v vol1 -c vol1 -g aggr1
  5. Add the IP addresses to be transitioned to the project:

    transition cbt lif add -p project_name -i ip-address [-m netmask] [-g default-gateway] [-p home_port] [ -n home_node]

    To a transition project, you can also add existing IP addresses that are unconfigured or removed from the 7-Mode system during storage cutover, and new IP addresses that are not yet configured on either the 7-Mode or ONTAP.

    FC and iSCSI LIFs are not transitioned by the 7-Mode Transition Tool.
    7-Mode Transition Tool>transition cbt lif add -p sample_project -i 192.0.2.250 -m 255.255.255.128 -g 192.40.0.1 -p e0a -n cluster1-01

    The new IP addresses are configured on the ONTAP system in the up state during the apply configuration (precutover) operation.

  6. Follow these steps to add information to the primary and secondary project:

    If you want to add information about the…​ Enter…​

    Primary 7-Mode system to the secondary project

    transition cbt add-primary-seven-mode-system -p project_name -h source-host -f management-ipaddress -d data-copy-ipaddress [-m multipathing-ipaddress]

    Secondary cluster or SVM to the primary project

    transition cbt add-secondary-cluster-mode-system -p project_name -h c-mode-host-name -v vserver-name

    project_name is the name of the transition project.

    source-host is the primary 7-Mode storage system host name or IP address as seen in the snapmirror status command output of the secondary 7-Mode system.

    For considerations about providing the 7-Mode primary system details, see the man pages.

    management-ipaddress is the management IP address of the source host.

    data-copy-ipaddress is the IP address over which data is copied.

    multipathing-ipaddress is the additional IP address that is used for data copy.

    c-mode-host-name is the FQDN or IP address of the cluster to which the secondary volumes in the project have been transitioned.

    vserver-name is the name of the SVM hosting the secondary volumes.

  7. Create a data copy schedule:

    transition cbt schedule add -p project_name -n schedule_name -d days-range -b start-time -e duration -u update-frequency -t available-transfers-percentage -c max-cap-concurrent-transfers -x project-snapmirror-throttle

    The following command shows how to add a schedule that uses 100% of available concurrent SnapMirror transfers. However, it does not exceed the 25 concurrent SnapMirror transfers at any point of time.

    transition schedule add -p sample_project -n dr_active -d 1-5 -b 23:30 -e 03:00 -c 25 -x 200 -u 00:30

  8. View the detailed information about the transition project created:

    transition cbt show -p project-name