Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi All,
I know this question has been in this discussion forum but it didnt help me out.
I have tried breaking and resyncing the relationship but still it gets stuck at 100 gb and even sometimes it shows restart at checkpoint.
Tried every possible way to fix this and even logs did not have much info.
Can it be a network issue?
Can anyone help here
Thanks
santosh
6 REPLIES 6
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Can you please post the output of the below command.
snapmirror status -l <dest vol>
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
PFB status
Snapmirror is on.
Source: LPLNHHDSGF01-SV:LPLOFS01
Destination: HORLWHDSGF01:LPLOFS01
Status: Transferring
Progress: 125383136 KB
State: Snapmirrored
Lag: 626:36:41
Mirror Timestamp: Tue Mar 7 23:10:06 GMT 2017
Base Snapshot: HORLWHDSGF01(0118057313)_LPLOFS01.1747
Current Transfer Type: Retry
Current Transfer Error: -
Contents: Replica
Last Transfer Type: Retry
Last Transfer Size: 26529344 KB
Last Transfer Duration: 00:40:55
Last Transfer From: LPLNHHDSGF01-SV:LPLOFS01
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
We had this happen on volumes in the past. Turned out to be an IDS device dropping packets that it didn't like.
The workaround was enabling compression on the snapmirror relationship in question. At least back then tricked the IDS into allowing it through.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
we had the same problem here, you need to exclude the storage IP adresses from IDS scanning.
Compression just changes the pattern of the data stream, excluding is the way to go.
Marcus
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Still unable to fix this.
can anyone help
