2x ReadyNAS Pro4 - One local, one offsite (which is a pain to get access to!) All 4 replicate jobs have been running perfect for months after moving the start times around to get around timeouts in the middle of the night from Time Warner. The guy who lives with the offsite NAS had to shut it down for a little bit, so he used the front panel to do a standard shut down. After rebooting, now all backups are failing. The stupid thing is that it says it can't find the NAS1 which is the local one. When I go to the Replicate website, I can SEE both units, NAS1 & NAS2 and browse their contents. But all backups are failing now.
I had previously tried rebooting NAS1 and replicate still failed. Today I tried updating Replcate versions on both units and restarted both, and now it works again. What gives? Why would a working system all of a sudden stop working after the remote NAS got rebooted? And the error clearly says the local NAS cannot be found.
This whole replicate system is very touchy, unreliable, and not user-friendly. It HAS to be better than this, this cannot be the state of offsite replication.
I had same problem & reloaded Replicate on both source and target NASs BUT now it tells me 'Copy Failed' every time. (Going from Duo V2 to an Ultra 4 Plus). Anyone else had this ?
So, it's been working somewhat, well, my main backup replication that I need anyway, but others are still failing on a regular basis. Sometimes I can tell it must have been a network issue because sometime one replicate won't quite finish when another one starts and they'll both fail at exactly the same time.
I think I'll just start posting my weekly failures here. My setup is one Pro4 at the office, the other at the owners house. No VPN tunnel, relying on P2P connectiong.
Summary: Copy start time: 2013-11-01 18:03 Total files processed: 24117 Total files transferred: 20661 Total files size: 20.83 GB Total files size transferred: 15.00 GB Average speed: 329.57 KB/s Exit code: 12 (Error in protocol data stream) Copy end time: 2013-11-02 07:18 Copy end time: 2013-11-02 07:18
Summary: Copy start time: 2013-11-02 06:02 Total files processed: 16 Total files transferred: 0 Total files size: 152.12 GB Total files size transferred: 42.94 GB Average speed: 1.07 MB/s Exit code: 30 (Data send/receive timeout) Copy end time: 2013-11-02 17:24 Copy end time: 2013-11-02 17:24
Summary: Copy start time: 2013-11-01 20:00 Total files processed: 22 Total files transferred: 8 Total files size: 28.27 GB Total files size transferred: 14.24 GB Average speed: 193.65 KB/s Exit code: 30 (Data send/receive timeout) Copy end time: 2013-11-02 17:24 Copy end time: 2013-11-02 17:24
Again!!!! Dammit!!! What the hell? The NAS1 and NAS2 show up in the Replicate network monitor just fine, so the cloud service sees them!! NAS1 is the local one inside the office.
I've been getting this again the last couple of weeks: Log: 2013-12-30 20:26:35 Replicate version: 1.2.0 build R1 2013-12-30 20:26:35 Starting backup job "FS_NS_BACKUP" 2013-12-30 20:26:35 Locking target folder: /c/backup/FS_NS_BACKUP/FS_NS_BACKUP 2013-12-30 20:26:36 Resume folder is "/c/backup/FS_NS_BACKUP/FS_NS_BACKUP/2013-12-27 22-45 (failed)/data" 2013-12-30 20:26:55 p2p connect to AndtechNAS1 in 939867 network 2013-12-30 20:26:55 Unable to connect to AndtechNAS1 2013-12-30 20:26:55 Connect error code: -501 2013-12-30 20:26:55 Please check network connection between devices 2013-12-30 20:26:55 Rotate backups (5) 2013-12-30 20:26:55 Rotation marker is "2013-12-23 22-45 (failed)" 2013-12-30 20:26:59 Unlock target folder: /c/backup/FS_NS_BACKUP/FS_NS_BACKUP 2013-12-30 20:26:59 Job finished
So, I figured out how to get around all these failures. I had to recreate each replicate job from scratch. My Jobs were created in 2012, so between firmware and Replicate updates, I guess they didn't survive compatibility. Another stupid thing. They should have some kind of verification of the job's compatibility. I mean, c'mon, it's sitting on your cloud server, and you know what firmware and software is being used.
I just wanted to update that since the latest updates and recreating my jobs in January, I've pretty much had successful replicates the whole time so far with only the occasional one that might have took too long and timed out. But even those big jobs will work the next time around.
Things started failing again all of a sudden. I don't know why yet. Here's how it started...
2014-08-15 22:07:59 p2p connect to AndtechNAS1 in 2551550 network 2014-08-15 22:21:30 Unable to connect to AndtechNAS1 2014-08-15 22:21:30 Connect error code: -601
Then, the next job says: 2014-08-18 22:00:37 Unable to get local p2p address 2014-08-18 22:00:37 Unable to get p2p local ip address
The retarded part of this, is that when I log into the online management, it can see NAS1, but not NAS2. Shouldn't I get something different like it can't find the destination (NAS2)?
And this is happened before where NAS2 can't be seen, and we just reboot it and it comes back. Not sure why either.
I have seen some cases where opening ports TCP 6819 to the local IP address of the destination (and source NAS) have fixed this issue. I suggest you try that. I encountered this once and that fixed it. 🙂
It happened again this week where NAS2 just disappeared. I can't get to it physically (its offsite), but when I asked someone to check it, it is powered on and looks normal on the display. Rebooting it got to show up in Replicate again. I added the port you suggested. We'll see what happens.
Sorry I know its bit of a late reply but I have been searching for information on this as I am having exactly the same issue. My NAS boxes are both running OS6 and work on the LAN but when one is taken offsite and reconnected to a network point (also showing online on the replication portal) it then fails with exit code 30.
