dualathlonserver.com

Home > Could Not > Snapmirror Error 13102

Snapmirror Error 13102

Contents

I'll send you a private message 1287-272341-1489566 Back to top RACHEL ZHU Members #16 RACHEL ZHU 7 posts Posted 20 August 2010 - 06:39 PM SnapMirror seems to be using the SEE THE SOLUTION 1 person had this problem Me too Reply 0 Kudos Highlighted Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content PIPERONTAP Re: Snapmirror error: cannot connect SEE THE SOLUTION 1 person had this problem Me too Tags: 2240-2error13102fasfas2020fas2240-4 View All (8) Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content bsti Re: Break the snapmirror relationshipDest> snapmirror break Dest:/vol/vol0/mymirrorAfter using the snapmirror break command to temporarily break a SnapMirror relationship between a source and destination, you can use other SnapMirror commands to either click site

It turns out it's the same issue that has bitten others before. Unless SAN4's IP is 10.10.10.20, then you will get the error your describe. SnapMirror must be on.Dest> snapmirror status2. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content jeras Re: Snapmirror Error 13102 (The source volume is a dense volume which could not be snapmirrored

Cannot Accept Snapmirror Destination Requests: Access Denied For Snapmirror/snapvault Destination.

I confirmed with NetApp support that the Snapmirror configuration was correct for what I was trying to accomplish. so both systems need to allow each other Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-20 03:55 PM ok The lab is using Workstation 9, and currently usring NAT for the network configuration. Egemen TANIRER (Computer Engineer) View my complete profile PowerGui Feedjit Live Blog Stats Total Pageviews span.fullpost {display:inline;} Jump to content Citrix Citrix Discussions Log In Citrix.com Knowledge Center Product Documentation

  1. Is there a firewall between them?
  2. Assign the same network for both host of netapp simulator machine.2.
  3. If so, there should be details in the log.Or are you saying that StorageLink reports success and the array reports that the snapmirror errored out? 1287-272341-1489252 Back to top Derek Bezy

Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content GARCIA88JOSE Re: Snapmirror Error 13102 (The source volume is a dense volume which could not be snapmirrored Me too Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content mike_burris Re: snapmirror error 13102 ‎2012-06-20 09:07 AM How/what is the network setup between the Try this just to make sure:SAN1 snapmirror.allow:10.10.10.20 # Assuming this is for SAN210.10.10.44 # Assuming this is for SAN4 Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Netapp Snapvault Could Not Write To Socket Reply 0 Kudos « Message Listing « Previous Topic Next Topic » MORE IN COMMUNITY Learn How to Get Started Community Help Community Code of Conduct Provide Community Feedback Forums Blogs

If your snapmirror.conf is using names fo rthe relationship, then these entries need to be in there.Checking these options will not help, as they are related to the FilerView adminstration page.options Snapmirror.access Legacy Detailed error: Unexpected array element: snapmirror-connectionsWe are using snapmirror on these filers already to replicate other volumes, but this is our first StorageLink Site Recovery config. try to ping from secondry filer to primary. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-21 09:46 AM the source and destination volumes do not exist anymore.

but I am trying to setup a ms cluster across sites so I have snapmirror from source vol to destination vol. Could Not Read From Socket Snapvault Can you verify something in the middle isn't stopping SM traffic between the two? Make sure you have entries in the /etc/hosts ve file for both Source and Destination, otherwise name lookup will not work. Several functions may not work.

Snapmirror.access Legacy

If this is a SnapManager program, which should be utilizing SnapDrive, SnapDrive should be able to break the mirror from what I've glimpsed over documentation wise... navigate here As professionals know everything is not going in rules. Cannot Accept Snapmirror Destination Requests: Access Denied For Snapmirror/snapvault Destination. I'm always hesitant to label every quirk a "bug," but this is definitely not correct behavior. Netapp Snapmirror Could Not Read From Socket Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by

API name: snapmirror-list-connections. Finish writes to fas1_vol1Dest> snapmirror quiesce source_vol13. Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content soper_2010 Re: snapmirror error could not read from socket (error 13102) ‎2013-01-30 10:48 PM Thanks again!I solved The 1 specifies the cost metric for the route, which will always be 1 unless you need to add additional gateways. Netapp Snapmirror Could Not Write To Socket

Please re-enable javascript to access full functionality. Reply 0 Kudos « Message Listing « Previous Topic Next Topic » MORE IN COMMUNITY Learn How to Get Started Community Help Community Code of Conduct Provide Community Feedback Forums Blogs Found this article: https://kb.netapp.com/support/index?page=content&id=1011333 Something else to check, has snapmirror.access been setup on each system so they can talk to each other? http://dualathlonserver.com/could-not/snapmirror-error-could-not-read-from-socket.php This means that the destination volume needs to be able to re-hydrated data.

I havent seen this happen in our setup in house, except for cases where the DNS was not correctly configured. Netapp Snapmirror Cannot Connect To Source Filer Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by Make sure that the source IP is allowed on the destination system.

When trying to create a snap mirror for my test volume the volume gets created on the destination (NAFiler02) but I get the error message Snapmirror error: cannot connect to source

If so, are the required ports open? To make the change permanent, simply add the route statement to the /etc/rd file on the filer. Forums Blogs Tech OnTap Newsletter Register · Sign In · Help Products and Solutions FAS, ONTAP and OnCommand Backup and Restore E-Series, SANtricity and Related Plug-ins Virtualization and Cloud Network Storage Ossv Cannot Read From Socket I specified a multiplexed configuration in the snapmirror.conf to force replication to occur on a particular interface.

Verify the status of the snapmirrors. when i try to release or break themi get theserw-ntap2> snapmirror break -f rw-ntap2:mscluster_eq_vol_SnapMirror snapmirror break: mscluster_eq_vol_SnapMirror: destination is offline, is restricted, or does not existrw-ntap2> snapmirror break -f mscluster_eq_vol_SnapMirror snapmirror Some errors in syslog on the filer do not interfere with the actual snapmirror setup 1287-272341-1489235 Back to top Derek Bezy Members #3 Derek Bezy 17 posts Posted 19 August 2010 my review here I do have snap mirror access enabled but I think I might be missing something.

It will work fine in case of SRM failover but while doing failback it actually runs snapmirror resync, in this case our source becomes destination and destination becomes source so our The remedy was as simple as adding a route statement similar to this: route add inet 172.16.1.0/24 172.16.2.1 1 where 172.16.1.0/24 is the iSCSI network I want to traverse to reach Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content TDUBB1234 Re: snapmirror error 13102 ‎2012-06-20 11:16 AM bnot sure what happened. Forums Blogs Tech OnTap Newsletter Register · Sign In · Help Products and Solutions FAS, ONTAP and OnCommand Backup and Restore E-Series, SANtricity and Related Plug-ins Virtualization and Cloud Network Storage

but after the successful resync. I've found that you can get more details in the snapmirror log file than appears on the console when trying to troubleshoot SnapMirror.Ken Reply 0 Kudos Options Bookmark Highlight Print Email All Rights Reserved Privacy & Terms I fixed it by adding a route statement on the destination filer that specifically directs traffic to the source filer to use the desired interface (in this case, the iSCSI VIF).

Also, you may want to take a look at the SnapMirror log file on the destination system (found in the /etc/log directory. Unfortunately, in the case of some NetApp filers, this does not always happen. on filer lable just check that proper access is givine for both host on snapmiror.access list also check the /etc/hosts entry and /etc/hosts.equiv.Please let us know if still your problem is becouse i need both san2 and san4 to be able to sync the data with san1.

The designation destination volume does exist (I have tried this replicating both a volume and a qtree and both fail). Other replication jobs I have set up between these two filers work in the opposite direction with the multiplexed configuration. I had to do a manual mscs failover to the other site node and a failback before the volume shows as writable.why is that? But when you say undedupe thevolume, you mean ?myfilser> sis undo /vol/vol1If is the above command i did not.*Could it be the issue???*2) A: I am using Volume SnapMirror in DOT

Solved! Just the alerts pop up for the netapp error. 1287-272341-1489247 Back to top Parthasarathy Ramachandran Members #4 Parthasarathy Ramachandran 19 posts Posted 19 August 2010 - 05:14 PM As long as please recheck that.3. it seems to be working now.

Locate and delete the entry that specifies the SnapMirror relationship you want to end. I am only using 1 interface ips 192.168.72.151 and 152.

>