Other replication jobs I have set up between these two filers work in the opposite direction with the multiplexed configuration. You may find that while the IP is ping-able, the hostname is not, which may point to the absence of a DNS entry for your filers in your locally configured DNS FilerB> vol status snap_test_vol_dest Volume State Status Options snap_test_vol_dest online raid_dp, flex create_ucode=on, convert_ucode=on Volume UUID: 4bab1a3c-8b12-11e1-b31b-000000000 Containing aggregate: 'SAS_600g' Now that the destination volume is created, we need to set when i failover the ms cluster resource from source to destination, the destination drive remains as eadable only and not writable.

Cannot Connect To Source Filer Snapvault

Make sure you have entries in the /etc/hosts ve file for both Source and Destination, otherwise name lookup will not work. 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? etc.>> options.snapmirror Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content AKSHAY_TYAGI Re: Snapmirror error: cannot connect to source filer (Error: 13102) ‎2014-09-03 11:58 AM Its Keep in mind that you’ll need to add the relationship again for a resync, such as in a DR scenario.

Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by I have checked the /etc/hosts file has been updated, and that the /etc/snapmirror.allow has both the filer names and IP addresses correct at both ends. "options snapmirror.access legacy" is set so the volume was still only in read mode. We’re only going to perform an initial data copy, so we won’t get into that detail right now.

Finally, in order to use the volume, you have to break the snapmirror relationship, then set the volume to “enable” status. FilerB> I fiddled with the configuration a little bit - I figured the snapmirror.allow file also needed the volume name: FilerB> wrfile /etc/snapmirror.allow 123.1.1.1:snap_test_vol FilerB> That got me a different result: Traffic was exiting on the wrong interface. browse this site Note : This command will create file in this path\\filer_name\C$\etc\snapmirror.allow Snapmirror primary configuration of VSM & QSM Snapmirror Secondary configuration of VSM & QSM Snapmirror schedule configuration Posted by Suresh S

The lab is using Workstation 9, and currently usring NAT for the network configuration. 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 This was a test with very little data, but I was able to move a 500G volume in just a few minutes - the filer seemed to be capable of transferring NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches

Transfer Aborted: Cannot Connect To Source Filer.

The links lit up immediately. Regardless, the relationship needs to be set up. Cannot Connect To Source Filer Snapvault Other Posts ← Windows VMs on XenServer Mysteriously Jumping a Day AheadWindows Server Core Full Configuration with PowerShell → FREE TECH TIPS, TOOLS, AND RESOURCES Sign up for Ben's FREE look in the /etc/messages file.

Source Destination State Lag Status 123.1.1.1:snap_test_vol FilerB:snap_test_vol_dest Snapmirrored 00:01:01 Idle FilerB> FYI - having a dedicated link, even 1Gig - totally worth it. http://thehelpshop.org/cannot-connect/netbackup-7-error-cannot-connect-on-socket.php It’s also very useful in Disaster Recovery plans, since volumes can be incrementally backed up to an offsite location. SnapMirror must be on.Dest> snapmirror status2. Verify the status of the snapmirrors.

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 Volume size is being retained for potential snapmirror resync. If you would like to grow the volume and do not expect to resync, set vol option fs_size_fixed to off. Try to ping the destination filer from the source filer (and vice versa) using it's hostname and see if you get a response.

It turns out it's the same issue that has bitten others before.

the old relationship is between the same systems but the volumes have been destroyed. The error I am getting is below:==ERROR==com.netapp.sysmgr.client.api.NaApiFailureException==TIME==2012-01-11 11:46:55,282==MESSAGE==Snapmirror error: cannot connect to source filer (Error: 13102)==DETAILS==No details are available.==CORRECTIVE ACTION==No suggested corrective action is available.==LOCATION==Location is not specified.==BROWSER INFO==App Name: Microsoft If this is not the case than it's likely that you'd need to add a route to either of the networks and tell the filerthrough what interface/gatewaythe traffic needs to go Finishes any write activity and then disables further updatesDest> snapmirror quiesce /vol/vol0/mymirror3.

It’s pretty large, since it holds templates for a variety of operating systems. I was tasked with getting these VMware templates to be accessible in a completely isolated system in another part of the datacenter. This is a simple fix - all you need to do is add the actual hostname of the destination filer in the snapmirror.allow file of the source filer (I kept the news Let us know NetApp.com Support Community Training Contact Community turn on suggestions Auto-suggest helps you quickly narrow down your search results by

This is done by volume name. 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 He spends his days diving deep into the intersection of networking and software, and likes to blog about his experiences when he comes up for air. Make sure that the source IP is allowed on the destination system.

it seems to be working now. try to ping from secondry filer to primary. None of the physical infrastructure was shared, meaning I could not simply expose this LUN to another VMware host. FilerB> That’s it!

SEE THE SOLUTION 1 person had this problem Me too Reply 0 Kudos Options Bookmark Highlight Print Email to a Friend Report Inappropriate Content PIPERONTAP Re: Snapmirror error: cannot connect to My number #1 fault topic with netapp is actually routing.Make sure both filers are in the host file and you can ping each of the filers ip & name. Let us know How to Make NetApp Use the Correct Interface for iSCSI Toggle navigation About Blog Newsroom Free Resources Results Posted by Ben Piper on January 25, 2012 How to skip to main | skip to sidebar IT Tips&Tricks Tuesday, November 26, 2013 cannot connect to source filer (Error: 13102) Main cause of this error is that the missing parameters in

Steps creating VFiler Steps creating VFiler The following conditions must be met before you can create a vFiler unit : • You must create at least one unit of ... The end result would be to have an identical volume created on the secondary filer so that I could access the LUNs and gain access to those templates from the secondary 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... I didn’t want to deal with that, thus the dedicated connection.