SnapMirror implementation using SMIS is not working using StorageSnchronized assosiation

[HrishikeshGokhale]

Background:

Currently we have implemented SnapMirror using Split operation, since we faced issue with Fracture operation.

As per CIM definition split will stop I/O to source elements and wait for in-transit copy operations between source and target elements to stop completely. In our opinion, if heavy I/O's are happening there will be a significant wait time in performing split operation, which might increase time to take a backup.

Query:

Is there a way we can find out why fracture is not working?

Background:

Currently we have implemented SnapMirror using GroupSynchronized association, since we faced issue with StorageSynchronized. As per definition it seems it will split/fracture association between two groups and not two storage volumes, of which we want to take a  backup.

Query:

Is there a way we can find out why StorageSynchronized is not working?

Background:

After performing split operation whenever we try to perform resync operation, snapshot copy created on destination volume is getting deleted. Following link mentions similar behavior,

https://library.netapp.com/ecmdocs/ECMP1610202/html/snapmirror/resync.html

Query:

Is there a way we can keep snapshot copy created on destination volume via CIM call so that during resync it doesn’t get deleted?

[naveens17]

Background:

After performing split operation whenever we try to perform resync operation, snapshot copy created on destination volume is getting deleted. Following link mentions similar behavior,

https://library.netapp.com/ecmdocs/ECMP1610202/html/snapmirror/resync.html

Query:

Is there a way we can keep snapshot copy created on destination volume via CIM call so that during resync it doesn’t get deleted?

That is a expected behaviour. IN this situation take the snapshot on source --> update the mirror.. you will see the snapshot on destination side

Now you can break and as long as source side if the snapshot exists then destionation side also it wil be exist.

[HrishikeshGokhale]

---

@naveens17 wrote:

Background:

After performing split operation whenever we try to perform resync operation, snapshot copy created on destination volume is getting deleted. Following link mentions similar behavior,

https://library.netapp.com/ecmdocs/ECMP1610202/html/snapmirror/resync.html

Query:

Is there a way we can keep snapshot copy created on destination volume via CIM call so that during resync it doesn’t get deleted?

That is a expected behaviour. IN this situation take the snapshot on source --> update the mirror.. you will see the snapshot on destination side

Now you can break and as long as source side if the snapshot exists then destionation side also it wil be exist.

---

Please confirm do i need to perform following operations

Take snapshot at source

Update mirror

break mirror relationship

take snapshot at target

resync relationship.

Also will this work for both sync & async mode?

[naveens17]

Take snapshot at source

Update mirror

break mirror relationship

you will see the source snapshot on the DR or target filer side and use it for any DR purpose or make a clone copy

resync relationship.

but instead of breaking the mirror you can do as well

Take snapshot at source

Update mirror

you will see the source snapshot on the DR or target filer side and use it for any DR purpose or make a clone copy

[HrishikeshGokhale]

Hi @naveens17,

Based on your input, what we did is that we took a  LUN snapshot at source side and resynced the snapmirror due to which it appeared in the backup side. After  presenting the  remote side snapshot it to a windows host we are able to see it in disk manager but on making it online it gives IO error message . But if we do the same thing by breaking the snapmirror link  the remote side Snapshot  becomes online without any issues . 

Any idea how we can use the snapshot in windows without breaking the link ?

Thanks in advance !

Regards,

Hrishikesh

[naveens17]

snapshot is a read-only ..

So with that snapshot make a flex-clone and present to the host. This will occur with out breaking the snapmirror

[HrishikeshGokhale]

---

@naveens17 wrote:

Take snapshot at source

Update mirror

break mirror relationship

you will see the source snapshot on the DR or target filer side and use it for any DR purpose or make a clone copy

resync relationship.

but instead of breaking the mirror you can do as well

Take snapshot at source

Update mirror

you will see the source snapshot on the DR or target filer side and use it for any DR purpose or make a clone copy

---

Thanks for your response @naveens17. Will surely try it.

Also any inputs on why StorageSynchronized is not working as mentioned above?

[HrishikeshGokhale]

Hi ,

Any inputs on  StorageSynchronized CIM will be appreciated .

Regards,

Hrishikesh

[HrishikeshGokhale]

Hi ,

Any inputs on  StorageSynchronized CIM will be appreciated .

Regards,

Hrishikesh