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?