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.
Is there a way we can find out why fracture is not working?
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.
Is there a way we can find out why StorageSynchronized is not working?
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,
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 ?