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
Failed to start transfer for Snapshot copy.... (CSM: Operation referred to a non-existent session.)
2019-10-28
11:29 AM
5,916 Views
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
All,
Had some sort of network issue recently and rendered a handful of snapmirrors "unhealthy" and not able to successfully replicate. Everything from a cluster peer standpoint looks ok, pings are successful between nodes, and no issue with authentication. I am seeing some destination volumes with busy snaps as a result. Was wondering if anyone has seen the snapmirror errors such as the below:
Failed to start transfer for Snapshot copy "snapmirror.e36...". (CSM: Operation referred to a non-existent session.)
cpeer.xcm.update.warn: Periodic update of peer network information failed. The following operations are incomplete: discovery failure.
cpeer.xcm.addr.disc.warn: Address discovery failed for peer cluster 0df39b.... Reason: Failed to discover remote addresses: RPC: Timed out [from mgwd on node "NODE" (VSID: -3) to Unknown Program:0 at Not available].
smc.snapmir.schd.trans.overrun: Scheduled transfer from source volume '_volume' to destination volume 'volume_dst' is taking longer than the schedule window. Relationship UUID '6b80exxxx'.
Solved! See The Solution
1 ACCEPTED SOLUTION
tduran12165 has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can disregard. The messages were as a result of a rogue Riverbed. 🙂
1 REPLY 1
tduran12165 has accepted the solution
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
You can disregard. The messages were as a result of a rogue Riverbed. 🙂
