John Wray's Blog - 7-Mode

7-Mode snapmirror to CDoT cli

john@johnwray.com — Thu, 25 Sep 2014 00:17:00 -0500

NetApp has a 7-mode migration tool you can also use to do this. CLI manually seems easier to me. You don't have to install software anywhere. This assumes you have the intercluster lif ip addresses added to the 7-mode controller's snapmirror.allow file. You cannot snapmirror between the systems without an intercluster lif on the CDoT system. You will need an intercluster lif on each node in the cluster that can route to the 7-mode system.

1. Create a transition peer relationship

vserver peer transition create -local-vserver <cluster name> -src-filer-name <7-Mode Controller>

2. Create the volume to use for the mirror on the cluster side.

volume create -vserver <SVM on cluster> -volume <mirror name> -aggregate aggr1_01 -size 4t -space-guarantee none -percent-snapshot-space 0 -type DP

This creates a thin provisioned volume on the storage virtual machine that will eventually be using this volume. The aggregate, size, naming will be specific to your environment.

3. Create the snapmirror relationship, type, and schedule.

snapmirror create -source-path <7-mode controlle>:<source volume> -destination-path <svm>:<snapmirror volume> -type TDP -schedule hourly

4. Initialize the mirror

snapmirror initialize -destination-path <svm>:<snapmirror volume>
Once the initialization completes it will sync on the hour if you chose hourly.

You see the progress by using snapmirror show. Keep in mind CDoT does not constantly update the stats so you may not see change for 5 minutes or so. If you want more live stats, you can do a snapmirror status on the 7-mode controller.

Recreate 7-mode snapshot policies on CDoT

john@johnwray.com — Tue, 23 Sep 2014 03:08:00 -0500

I was replicating the old policies.

Here were the policies on the 7-mode NetApp

shares0 4 13 6@8,12,16,20

profiles: 2 2 6@8,12,16,20

So first thing I had to do was create a new cron job definition for the times they wanted.

job schedule cron create bmh -hour 8,12,16,20 -minute 0

Next I had to create the snapshot policies

vol snapshot policy create -vserver BMH-Share-01 -policy 4w13d6h -enabled true -schedule1 weekly -count1 4 -schedule2 daily -count2 13 -schedule3 bmh -count3 6

vol snapshot policy create -vserver BMH-Share-01 -policy 2w2d6h -enabled true -schedule1 weekly -count1 2 -schedule2 daily -count2 2 -schedule3 bmh -count3 6

Then I had to apply them to the volumes. You can’t apply them until you have done your cutover and they are no longer TDP mirrors.

vol modify -vserver BMH-Share-01 -volume shares0 -snapshot-policy 4w13d6h

vol modify -vserver BMH-Share-01 -volume profiles -snapshot-policy 2w2d6h

BMHNetApp::> snapshot policy show
Vserver: BMH-Share-01
                         Number of Is
Policy Name              Schedules Enabled Comment
------------------------ --------- ------- ----------------------------------
2w2d6h                           3 true    -
    Schedule               Count     Prefix                 SnapMirror Label
    ---------------------- -----     ---------------------- -------------------
    weekly                     2     weekly                 -
    daily                      2     daily                  -
    bmh                        6     bmh                    -

4w13d6h                          3 true    -
    Schedule               Count     Prefix                 SnapMirror Label
    ---------------------- -----     ---------------------- -------------------
    weekly                     4     weekly                 -
    daily                     13     daily                  -
    bmh                        6     bmh                    -

Convert 7-mode to CDoT on NetApp

john@johnwray.com — Mon, 22 Sep 2014 00:48:00 -0500

Clustered Ontap Change of Boot Loader

Stop the boot and go into the loader prompt.

LOADER-A>> setenv bootarg.init.boot_clustered true

LOADER-A> setenv bootarg.bsdportname e0M

LOADER-A> boot_ontap

Press CTRL-C to enter into the boot menu

Once in the boot menu select option 4 to Clean configuration and initialize all disks.

WARNING: This will erase your entire storage system, so unless you are doing this on a brand new system, a demo system, or an existing system that does not have any data on it, do not continue any further.