How to migrate data from Ontap 7-mode to CDOT

Blog by Ephraim Iverson: How to mirgate data from Data Ontap 7-mode to CDOT using snapmirror http://ephraim-iverson-7mode-to-cdot.quora.com?share=1&srid=tklk

Snapmirror TDP to migrate to CDOT

Using Snapmirror TDP to move data from 7-mode to CDOT. *WIll not move luns * http://ephraim-iverson.blogspot.com/2014/03/using-snapmirror-tdp-to-move-data-from.html

How do I use Snapmirror to move data from 7-mode to CDOT. *WIll not move luns *

 Ephraim Iverson: Sourced from now.netapp.com

https://library.netapp.com/ecmdocs/ECMP1235582/html/GUID-DC377D15-5F08-4FEC-A5F8-22A2EAE44D39.html

In case you can not resolve the link. Here it is.......


Transitioning a secondary volume manually

Transitioning a secondary volume involves creating a transition peer relationship, creating a SnapMirror relationship, performing a baseline transfer, performing incremental updates, and setting up a SnapMirror relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume.
Before you begin
The secondary cluster and Vserver must already be set up.
Steps

    Use the vserver peer transition create command to create a transition peer relationship between the 7-Mode system and the Vserver.

    Example

    sec_cluster::> vserver peer transition create -local-vserver dst_vserver -src-filer-name dst_system
    Transition peering created

    Use the vol create command to create a clustered Data ONTAP secondary volume of type DP to which the 7-Mode data must be transitioned.

    The size of the clustered Data ONTAP volume must be equal to or greater than the size of the 7-Mode volume.

    Example

    sec_cluster::> volume create -volume dst_c_vol -aggregate aggr1 -size 20M -type DP
    [Job 24] Job succeeded: Successful

    Create an intercluster LIF for communication between the secondary Vserver and 7-Mode system by performing the following steps:
        Use the network interface create command to create an intercluster LIF on the same node that contains the volume.

        Example

        sec_cluster::> network interface create -vserver sec_cluster-01 -lif int_lif1 -role intercluster -home-node sec_cluster-01 -home-port e0c -address 192.0.2.140 -netmask 255.255.255.128

        Use the network routing-groups route create command to create a static route for the intercluster LIF.

        Example

        sec_cluster::> network routing-groups route create -vserver sec_cluster-01 -routing-group i192.0.2.140/18 -destination 0.0.0.0/0 -gateway 192.0.2.129

        Use the network ping command to verify that you can use the intercluster LIF to ping the 7-Mode system.

        Example

        sec_cluster::> network ping -lif int_lif1 -lif-owner sec_cluster-01 -destination dst_system
        dst_system is alive

    Copy data from the 7-Mode volume to the clustered Data ONTAP volume:
        Use the snapmirror create command with the relationship type as TDP to create a SnapMirror relationship between the 7-Mode system and the Vserver.

        Example

        sec_cluster::> snapmirror create -source-path sec_system:dst_7_vol -destination-path dst_vserver:dst_c_vol -type TDP
        Operation succeeded: snapmirror create the relationship with destination dst_vserver:dst_c_vol.

        Use the snapmirror initialize command to start the baseline transfer.

        Example

        sec_cluster::> snapmirror initialize -destination-path dst_vserver:dst_c_vol
        Operation is queued: snapmirror initialize of destination dst_vserver:dst_c_vol.

        Depending on whether you want to update the clustered Data ONTAP volume manually or by setting up a SnapMirror schedule, perform the appropriate action:

        If you want to perform...     Then...
        Update transfers manually    
            Use the snapmirror update command.

            sec_cluster::> snapmirror update -destination-path dst_vserver:dst_c_vol

            Use the snapmirror show command to monitor the data copy status.

            sec_cluster::> snapmirror show -destination-path dst_vserver:dst_c_vol

                            Source Path: sec_system:dst_7_vol
                       Destination Path: dst_vserver:dst_c_vol
                      Relationship Type: TDP
                    SnapMirror Schedule: -
                            Tries Limit: -
                      Throttle (KB/sec): unlimited
                           Mirror State: Snapmirrored
                    Relationship Status: Idle
                      Transfer Snapshot: -
                      Snapshot Progress: -
                         Total Progress: -
                    Snapshot Checkpoint: -
                        Newest Snapshot: dst_vserver(4053132614)_dst_c_vol.1
              Newest Snapshot Timestamp: 02/13 08:10:46
                      Exported Snapshot: dst_vserver(4053132614)_dst_c_vol.1
            Exported Snapshot Timestamp: 02/13 08:10:46
                                Healthy: true
                       Unhealthy Reason: -
               Constituent Relationship: false
                Destination Volume Node: cluster1-01
                        Relationship ID: e106827a-75b3-11e2-add9-123478563412
                          Transfer Type: -
                         Transfer Error: -
                       Current Throttle: -
              Current Transfer Priority: -
                     Last Transfer Type: update
                    Last Transfer Error: -
                     Last Transfer Size: 680KB
                 Last Transfer Duration: 0:0:12
                     Last Transfer From: system7mode:dataVol20
            Last Transfer End Timestamp: 02/13 08:13:40
                  Progress Last Updated: -
                Relationship Capability: 8.2 and above
                               Lag Time: 0:8:49
                      SnapMirror Policy: DPDefault

            Go to Step 6.
        Scheduled update transfers    
            Use the job schedule cron create command to create a schedule for update transfers.

            sec_cluster::> job schedule cron create -name 15_minute_sched -minute 15

            Use the snapmirror modify command to apply the schedule to the SnapMirror relationship.

            sec_cluster::> snapmirror modify -destination-path dst_vserver:dst_c_vol -schedule 15_minute_sched

            Use the snapmirror show command to monitor the data copy status.

            sec_cluster::> snapmirror show -destination-path dst_vserver:dst_c_vol
                            Source Path: sec_system:dst_7_vol
                       Destination Path: dst_vserver:dst_c_vol
                      Relationship Type: TDP
                    SnapMirror Schedule: 15_minute_sched
                            Tries Limit: -
                      Throttle (KB/sec): unlimited
                           Mirror State: Snapmirrored
                    Relationship Status: Idle
                      Transfer Snapshot: -
                      Snapshot Progress: -
                         Total Progress: -
                    Snapshot Checkpoint: -
                        Newest Snapshot: dst_vserver(4053132614)_dst_c_vol.1
              Newest Snapshot Timestamp: 02/13 08:10:46
                      Exported Snapshot: dst_vserver(4053132614)_dst_c_vol.1
            Exported Snapshot Timestamp: 02/13 08:10:46
                                Healthy: true
                       Unhealthy Reason: -
               Constituent Relationship: false
                Destination Volume Node: cluster1-01
                        Relationship ID: e106827a-75b3-11e2-add9-123478563412
                          Transfer Type: -
                         Transfer Error: -
                       Current Throttle: -
              Current Transfer Priority: -
                     Last Transfer Type: update
                    Last Transfer Error: -
                     Last Transfer Size: 680KB
                 Last Transfer Duration: 0:0:12
                     Last Transfer From: system7mode:dataVol20
            Last Transfer End Timestamp: 02/13 08:13:40
                  Progress Last Updated: -
                Relationship Capability: 8.2 and above
                               Lag Time: 0:8:49
                      SnapMirror Policy: DPDefault

    If you have a schedule for incremental transfers, perform the following steps when you are ready to perform cutover:
        Optional: Use the snapmirror quiesce command to disable all future update transfers.

        Example

        sec_cluster::> snapmirror quiesce -destination-path dst_vserver:dst_vol

        Use the snapmirror modify command to delete the SnapMirror schedule.

        Example

        sec_cluster::> snapmirror modify -destination-path dst_vserver:dst_vol -schedule ""

        Optional: If you quiesced the SnapMirror transfers earlier, use the snapmirror resume command to enable SnapMirror transfers.

        Example

        sec_cluster::> snapmirror resume -destination-path dst_vserver:dst_vol

    Wait for any ongoing transfers between the 7-Mode volumes and the clustered Data ONTAP volumes to complete, and then disconnect client access from the 7-Mode volumes to start cutover.
    Use the snapmirror update command to perform a final data update to the clustered Data ONTAP volume.

    Example

    sec_cluster::> snapmirror update -destination-path dst_vserver:dst_vol
    Operation is queued: snapmirror update of destination dst_vserver:dst_vol.

    Use the snapmirror show command to verify that the last transfer was successful.
    Use the snapmirror break command to break the SnapMirror relationship between the 7-Mode secondary volume and the clustered Data ONTAP secondary volume.

    Example

    sec_cluster::> snapmirror break -destination-path dst_vserver:dst_vol
    [Job 60] Job succeeded: SnapMirror Break Succeeded

    Use the snapmirror delete command to delete the SnapMirror relationship between the 7-Mode secondary volume and the clustered Data ONTAP secondary volume.

    Example

    sec_cluster::> snapmirror delete -destination-path dst_vserver:dst_vol

    Establish a disaster recovery relationship between the 7-Mode primary volume and clustered Data ONTAP secondary volume:
        Use the vserver peer transition create command to create a Vserver peer relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume.

        Example

        sec_cluster::> vserver peer transition create -local-vserver dst_vserver -src-filer-name src_system
        Transition peering created

        Use the job schedule cron create command to create a job schedule that matches the schedule configured for the 7-Mode SnapMirror relationship.

        Example

        sec_cluster::> job schedule cron create -name 15_minute_sched -minute 15

        Use the snapmirror create command to create a SnapMirror relationship between the 7-Mode primary volume and the clustered Data ONTAP secondary volume.

        Example

        sec_cluster::> snapmirror create -source-path src_system:src_7_vol -destination-path dst_vserver:dst_c_vol -type TDP -schedule 15_minute_sched
        Operation succeeded: snapmirror create the relationship with destination dst_vserver:dst_c_vol.

        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 7-Mode primary volume and the clustered Data ONTAP secondary volume.

        Example

        sec_cluster::> snapmirror  resync -destination-path dst_vserver:dst_c_vol

After you finish

    Delete the Vserver peer relationship between the secondary 7-Mode system and the secondary Vserver when all the required volumes in the 7-Mode system are transitioned to the Vserver.
    Delete the SnapMirror relationship between the 7-Mode primary and the 7-Mode secondary systems.

How to convert a Data ONTAP node from one operating Mode to the other?

Ephraim Iverson: How to convert a Data ONTAP node from one operating Mode to the other?

https://kb.netapp.com/support/index?page=content&id=1013517&cat=DATA_ONTAP_8_CLUSTER_MODE&actp=LIST

Here are the detail if you can not get into the link.  Taken from NetApp's Knowledge-base



Description

This article describes the procedure that should be followed to convert the operation of a storage controller from 7-Mode to Cluster-Mode or from Cluster-Mode to 7-Mode.

Note: Data ONTAP 7-Mode and Clustered Data ONTAP licenses are different. Please contact your sales team to obtain new licenses.

Warning: On-disk data is not preserved when using this procedure. All data will be lost.
Procedure

Prerequisites:

    The controller must have attached disk shelves.
    The disk shelves must be HA-cabled across the HA-pair (multipath HA cabling is recommended).
    This procedure will work for a single node as well, that is not part of an HA pair.
    Refer to the System Configuration Guides for the version and Mode of Data ONTAP that you will be using to ensure the hardware and slots used are supported.
    There must be a bootable image on the boot device.
    If converting from Cluster-Mode to 7-Mode, the node(s) of the Cluster-Mode must be unjoined from the cluster if the cluster remains active and only a node or HA-Pair will be converted to 7-Mode. See the article, 1013966: How to unjoin a node in Data ONTAP 8.1.x Cluster-Mode
    Data on the attached disk shelves is not critical and can be recovered from an alternate source, if needed
    Note: All Data will be lost when following this procedure to convert from one Mode to the other.
    If Data ONTAP 8.x is not on the boot device or new shelves are added as part of this process, see article 1010549: How to build a Data ONTAP 8.x system from the beginning.



Perform the following steps to convert from Data ONTAP 7-Mode to Data ONTAP 8.0X Cluster-Mode

    Disable 'Cluster Failover' and reboot the node to the LOADER prompt. Do not perform a takeover.
    Boot each node to the LOADER prompt and ensure that the following variables are set: 

    To convert from 7-Mode to Cluster-Mode: 
    LOADER> set-defaults
    LOADER> setenv bootarg.init.boot_clustered true
    LOADER>  setenv bootarg.bsdportname <node-mgmt_port_name>
    
    Boot the node with this command:
    boot_ontap
    When the nodes are booting, press CTRL+C to enter the Boot menu.
    At the Boot menu, select wipeconfig on each node.
    *******************************
    * Press Ctrl-C for Boot Menu. *
    *******************************
    How would you like to continue booting?
    (normal) Normally
    (install) Install new software first
    (password [user]) Change root/user password
    (setup) Run setup first
    (init) Initialize disks and create flexvol
    (maint) Boot into maintenance mode
    (syncflash) Update flash from backup config
    (reboot) Reboot node
    Please make a selection: wipeconfig
    After the wipeconfig completes, boot back to the Boot menu and select setup.
    *******************************
    * Press Ctrl-C for Boot Menu. *
    *******************************
    How would you like to continue booting?
    (normal) Normally
    (install) Install new software first
    (password [user]) Change root/user password
    (setup) Run setup first
    (init) Initialize disks and create flexvol
    (maint) Boot into maintenance mode
    (syncflash) Update flash from backup config
    (reboot) Reboot node
    Please make a selection: setup
    Enter the node configuration information for each node during the setup script.
    Hostname
    Location
    IP address for mgmt LIF on the mgmt port/Netmask/DefaultGwy
    DNS domain name/DNS nameserver IP(s)
    After the setup script completes, boot back to the Boot menu and select init.
    *******************************
    * Press Ctrl-C for Boot Menu. *
    *******************************
    How would you like to continue booting?
    (normal) Normally
    (install) Install new software first
    (password [user]) Change root/user password
    (setup) Run setup first
    (init) Initialize disks and create flexvol
    (maint) Boot into maintenance mode
    (syncflash) Update flash from backup config
    (reboot) Reboot node
    Please make a selection: init
    The init process can take a long time (hours depending on the number and size of the disks) as the disks are zeroed and initialized.
    Once the init process has completed, the node will boot Data ONTAP and the login prompt will be available.
    At this time, a new Cluster can be created or these nodes can be joined to an already existing cluster. The steps for creating or joining a cluster are available in the Data ONTAP Administration guides. See the article, 1010920: How to configure a pair of clean nodes and join them to an existing cluster

 Perform the following steps to convert from Data ONTAP 7-Mode to Data ONTAP 8.1 (and later versions) Cluster-Mode

    Disable 'Storage Failover' or 'Cluster Failover' and reboot the node to the LOADER prompt.  Do not perform a takeover.
    At the LOADER prompt, run the following commands:

    To convert from 7-Mode to Cluster-Mode:
    LOADER> set-defaults
    LOADER> setenv bootarg.init.boot_clustered true
    LOADER>  setenv bootarg.bsdportname <node-mgmt_port_name>
    LOADER> boot_ontap

    Stop the boot process at the special Boot menu and select option 4.
    The node automatically performs a wipeconfig, zeroes the disks and creates a 3-disk root aggregate with a FlexVol root volume.
    Perform the node setup.

Perform the following steps to convert from Data ONTAP Cluster-Mode to Data ONTAP 7-Mode

    Disable 'Storage Failover' and reboot the node to the LOADER prompt.  Do not perform a takeover.
    At the LOADER prompt, run the following commands:

To convert from Cluster-Mode to 7-Mode:
LOADER> set-defaults
LOADER> boot_ontap

    Stop the boot process at the special Boot menu and select option 4.
    The node automatically performs a wipeconfig, zeroes the disks and creates a 3-disk  root aggregate with a FlexVol root volume.
    Perform the node setup.

Ephraim Iverson: How do I create LUNs using NetApp C-Mode / CDOT?

How do I create lun in NetApp CDOT ?

1. Use the lun create command to create your LUNs.
If you want... Then use...
a space-reserved LUN space-reserve enabled
a thinly provisioned LUN space-reserve disabled
LUN setup | 33
Example
lun create -vserver vs3 -volume vol3 -lun ephraim_lun1 -size 50GB -ostype
windows -space-reserve disabled
2. Use the igroup create command to create your igroups.
Example
igroup create -vserver vs3 -igroup igroup1 -protocol iscsi -ostype
windows -initiator iqn.1991-05.com.microsoft:example
3. Use the lun map command to map your LUNs to igroups.
Example
lun map -vserver vs3 -volume vol3 -lun ephraim_lun1  -igroup igroup1
4. Use the lun show command to verify that you configured your LUNs correctly.
Example
lun show -vserver vs3
Vserver Path State Mapped Type Size
--------- --------------- ------- ------- --------- --------
vs3 /vol/vol3/ephraim_lun1  online mapped windows 50.01GB
vs3 /vol/vol3/ephraim_lun2  online mapped windows 50.01GB
vs3 /vol/vol3/ephraim_lun3  online mapped windows 50.01GB
3 entries were displayed.

Created by: Ephraim Iverson, Storage Architect

Storage-migrations

Ephraim Iverson : How to restrict snapmirror to allow access to a volume or qtree ONLY

On the source server in the snapmirror.allow file use the following syntax:

<hostname>:<volume_name>
<hostname>:<qtree_path>

Example:

destination_server:src_volume
destination_server:/vol/src_volume/src_qtree

By: Ephraim Iverson