2015-08-12 09:54 AM
Our environment has a history of a few volumes consistently having laggy snapmirror relationships between one site and another. We’re running CDOT 8.2.3 on two filers linked by a fairly slow pipe, and the source filer is about 1500 miles away from the destination.
One relationship in particular is as follows:
Am I misunderstanding something about how snapshots and snapmirror work? The snapshot that should be snapmirrored is about 71MB, and yet the progress of the snapshot that's in flight is 77GB so far, and growing. What am I missing?
Another possibly interesting fact about this snapmirror job:
Shouldn't the Total Transfer Time in Seconds number increment as time progresses?
Thanks for the help, everyone!
2015-08-12 01:29 PM
2015-08-12 02:47 PM
I'm not sure if I know a command to measure the delta between two snapmirror*** snapshots (or any other snapshots for that matter). Is it simply a matter of looking at the size of any two snapshots and doing some arithmetic?
2015-08-12 03:49 PM
Hmm ... you are right, seems that cDOT does not have direct analog. Command map suggests "snap delta" from node shell. As long as volumes are still visible fom node shell this should be possible.
2015-08-18 07:33 PM
To get more infomration use NetApp API to get all of the data.
You can get how much has bee transmitted and when it started so you can caclulate how much kb per second.
Did you look at all of you peer relantionships? Do you have one LIF for each node on both cDOT systems (source and destination)?
I would to do a ping from the lif you think that data is being transmitted on, then do a traceroute.