topic Re: run "snapmirror initialize", but the result is still showing uninitialized in ONTAP Discussions

run "snapmirror initialize", but the result is still showing uninitialized

netappmagic — Tue, 27 Jan 2015 23:27:14 GMT

I have gone throug all steps to set up SM LS on the same cluster. However, in the end, when after I run snapmirror initialize-ls-set -source-path n://vs1/vs1_root,

the job got queued, [Job 116] Job is queued: snapmirror initialize-ls-set for source n://vs1/vs1_root.

and then "snapmirrow show", the result is still uninitialized.

What could go wrong? is this something to do with snapshot or snap reserver configurations? Please shed some light for me.

also when I run "job show", that particular job is not listed there.

Re: run "snapmirror initialize", but the result is still showing uninitialized

Uddhav — Tue, 27 Jan 2015 23:39:23 GMT

The create relationship must exist before

cluster1::> snapmirror create -source-path //vs1/vs1 -destination-path //vs1/vs1_ls_b -type LS [Job 172] Job is queued: snapmirror create the relationship with destination //vs1_ls_b [Job 172] Job succeeded: SnapMirror: done

you have to do this for each load sharing volume

after this

cluster1::> snapmirror initialize-ls-set //vs1/vs1 [Job 175] Job is queued: snapmirror load-share initialize for source //vs1/vs1.

here you specify only source path, rest is taken by from above create relationship

try it

Re: run "snapmirror initialize", but the result is still showing uninitialized

netappmagic — Wed, 28 Jan 2015 00:52:48 GMT

"snapmirror create..." command that you suggested has already been run on both ls1 and ls2 volumes, and it got approved, because if I run it again,
I got a message saying the relationship with the destination already existed.

Re: run "snapmirror initialize", but the result is still showing uninitialized

netappmagic — Thu, 29 Jan 2015 02:12:16 GMT

anybody please?

Re: run "snapmirror initialize", but the result is still showing uninitialized

netappmagic — Thu, 29 Jan 2015 14:57:37 GMT

The following is the list of detailed run-book, step by step commands I used and their outputs. I removed some unrelated display messages. Hope somebody can help me our why SM-LS can not be initialized.

==========================

vs1::> vol create -vserver vs1 -volume vs1_root_ls3 -aggr vs1_n01_aggr1 -type dp
(volume create)
[Job 5538] Job succeeded: Successful

vs1::> snapmirror create -source-cluster vs1 -source-vserver vs1 -source-volume vs1_root -destination-cluster vs1 -destination-vserver vs1 -destination-volume vs1_root_ls3 -type ls
[Job 5541] Job is queued: snapmirror create for the relationship with destination "vs1://vs1/vs1_root
[Job 5541] Job succeeded: SnapMirror: done
vs1::> vol create -vserver vs1 -vol vs1_root_ls4 -aggr vs1_n02_aggr1 -type dp
(volume create)
[Job 5542] Job succeeded: Successful

vs1::> snapmirror create -source-path vs1://vs1/vs1_root -destination-path vs1://vs1/vs1_root_ls4 -type ls
[Job 5546] Job is queued: snapmirror create for the relationship with destination "vs1://vs1/vs1_root
[Job 5546] Job succeeded: SnapMirror: done
vs1::>
vs1::>
vs1::> snapmirror show
                                                                       Progress
Source            Destination Mirror Relationship Total             Last
Path        Type Path         State   Status        Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
.................

                                                                       Progress
Source            Destination Mirror Relationship Total             Last
Path        Type Path         State   Status        Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
....................................

                 vs1://vs1/vs1_root_ls3
                              Uninitialized
                                      Idle           -         -       -
                 vs1://vs1/vs1_root_ls4
                              Uninitialized
                                      Idle           -         -       -
....................
16 entries were displayed.

vs1::> snapmirror show -instance
..............................

                Source Path: vs1://vs1/vs1_root
           Destination Path: vs1://vs1/vs1_root_ls3
          Relationship Type: LS
        SnapMirror Schedule: 5min
                Tries Limit: 8
          Throttle (KB/sec): unlimited
               Mirror State: Uninitialized
        Relationship Status: Idle
          Transfer Snapshot: -
          Snapshot Progress: -
             Total Progress: -
        Snapshot Checkpoint: -
            Newest Snapshot: -
Newest Snapshot Timestamp: -
          Exported Snapshot: -
Exported Snapshot Timestamp: -
                    Healthy: -
           Unhealthy Reason: -
   Constituent Relationship: false
    Destination Volume Node: -
            Relationship ID: -
              Transfer Type: -
             Transfer Error: -
           Current Throttle: -
Current Transfer Priority: -
         Last Transfer Type: -
        Last Transfer Error: -
         Last Transfer Size: -
     Last Transfer Duration: -
         Last Transfer From: -
Last Transfer End Timestamp: -
      Progress Last Updated: -
    Relationship Capability: Pre 8.2
                   Lag Time: -
          SnapMirror Policy: -

                Source Path: vs1://vs1/vs1_root
           Destination Path: vs1://vs1/vs1_root_ls4
          Relationship Type: LS
        SnapMirror Schedule: 5min
                Tries Limit: 8
          Throttle (KB/sec): unlimited
               Mirror State: Uninitialized
        Relationship Status: Idle
          Transfer Snapshot: -
          Snapshot Progress: -
             Total Progress: -
        Snapshot Checkpoint: -
            Newest Snapshot: -
Newest Snapshot Timestamp: -
          Exported Snapshot: -
Exported Snapshot Timestamp: -
                    Healthy: -
           Unhealthy Reason: -
   Constituent Relationship: false
    Destination Volume Node: -
            Relationship ID: -
              Transfer Type: -
             Transfer Error: -
           Current Throttle: -
Current Transfer Priority: -
         Last Transfer Type: -
        Last Transfer Error: -
         Last Transfer Size: -
     Last Transfer Duration: -
         Last Transfer From: -
Last Transfer End Timestamp: -
      Progress Last Updated: -
    Relationship Capability: Pre 8.2
                   Lag Time: -
          SnapMirror Policy: -
.....................
16 entries were displayed.

vs1::> snapmirror initialize-ls-set -source-path vs1://vs1/vs1_root
[Job 5547] Job is queued: snapmirror initialize-ls-set for source "vs1://vs1/vs1_root".

vs1::> snapmirror show
                                                                       Progress
Source            Destination Mirror Relationship Total             Last
Path        Type Path         State   Status        Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
.......................................
                                                                       Progress
Source            Destination Mirror Relationship Total             Last
Path        Type Path         State   Status        Progress Healthy Updated
----------- ---- ------------ ------- -------------- --------- ------- --------
...........................
                 vs1://vs1/vs1_root_ls3
                              Uninitialized
                                      Idle           -         -       -
                 vs1://vs1/vs1_root_ls4
                              Uninitialized
                                      Idle           -         -       -
........................................
16 entries were displayed.

Re: run "snapmirror initialize", but the result is still showing uninitialized

Uddhav — Thu, 29 Jan 2015 14:26:34 GMT

Do this as exact

snapmirror create -source-path //vs1/vs1 -destination-path //vs1/vs1_ls_b -type LS

and to initialize

snapmirror initialize-ls-set //vs1/vs1

Re: run "snapmirror initialize", but the result is still showing uninitialized

netappmagic — Thu, 29 Jan 2015 14:55:06 GMT

Hi,

I am sorry, but your suggested command is not working. Please let me know what else can I try

> snapmirror create -source-path //vs1/vs1 -destination-path //vs1/vs1_ls_b -type LS
Error: command failed: Volume "vs1:vs1_ls_b" not found. (entry doesn't exist)

the volume "vs1_ls_b" should be "vs1_root_ls3" here, right?

I think, you really meant is the following and I have already tried last time:

> snapmirror create -source-path //vs1/vs1_root -destination-path //vs1/vs1_root_ls3 -type LS

Error: command failed: Relationship with destination vs1://vs1/vs1_root_ls3 already exists.

Re: run "snapmirror initialize", but the result is still showing uninitialized

radhakrishnan — Mon, 18 Apr 2016 05:02:34 GMT

Not Sure if this late reply helps But had a similar issue and this Document helped to resolve the issue.

To add a new mirror to LS set you need to run individual initialize and then it becomes part of ls-set

https://library.netapp.com/ecmdocs/ECMP1368017/html/GUID-FB6C2A65-7744-4AB8-A361-688D11CFDD08.html

Hope it helps some one who is struck :)..