NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Replicate
12 TopicsCannot register RN104 to ReadyNAS Replicate
I had to rearrange disks and so I did a Factory Default on my RN104. OS version is 6.8.1 (same es before FD). Everything seems to work fine, but when I try to log the device into Replicate, I only get a message: "User name or password is invalid." ...which obviously is not the real problem, since credentials did not change. They do work on the Replicate web site. Also my RN312 runs on same network and is connected to the Replicate service. I know, DNS settings are important. I am on DHCP, IPv4 only. Any ideas, what is causing this? Are there any error log or setting fies I should check? Best regards, frantic1.7KViews0likes5CommentsReadynas Replicate
I have two devices, one at home and one at a remote location and the home NAS backups up to the remote NAS on a schedule. All works fine but I have a lot of history folders within each of the backup folders. I originaly made the mistake of setting them up as being kept for eternity, I have now limited the number of versions. My question is with the old folders be deleted over time or do I need to do it manually and also if I delete them now what impact will it have? I'm runnign out of space on the remote NAS hence the question although the required backup storage is well within the stored capacity it's just the versions that are padding it out.2KViews0likes3CommentsRN2120v2 - Can't (completely) replicate settings between two readynas using Configuration Backup
Hi all, i have to set up several ReadyNas 2120v2 with same settings, i have to do this in an isolated subnetwork (no internet) so i'm using "Configuration Backup" in System menu. I downloaded the "configuration archive" from the first ReadyNas, checking "Everything" button. So i uploaded the configuration file to a new ReadyNas previously upgraded with the same firmware of the first ReadyNas (6.6.0), using the "Restore" function. After the reboot, i noticed that the ReadyNas restored hasn't fully configured like the first ReadyNas. While Shares, accounts and active services are replicated, Host name and Network settings remain unchanged. Any suggestions would be appreciated. Thank you.3.5KViews0likes7CommentsReadyNAS Replicate Job Returning "Connect error code: -51"
Hi All, (Please do not tell me to contact support. They are thoroughly unhelpful.) I recently purchased a second ReadyNAS RN102. Both ReadyNAS RN 102's are running on OS 6.6.0 and are on the same network. I enabled ReadyNAS Replicate on both devices and registered them with the same ReadyNAS Replicate account. Both have static IP addresses, are a part of the same DNS server with 8.8.8.8 added as alternative DNS's, and IPv6 is disabled completely. Eventually, I want to be able to move one of these devices to another location, but still have them replicate to each other. When I create a job that is supposed to replicate some data (a small amount for test purposes) from one ReadyNAS to the other (and vice versa), I receive the below error in an email message stating, "Connect error code: -51". What is this error and how can I fix it? [2016-11-10 12:11:35] [Info] Replicate version: 1.3.0 build R2 [2016-11-10 12:11:35] [Info] Starting backup job "Data Backup [2016-11-10 11h 41m AM]" [2016-11-10 12:11:35] [Info] Locking target folder: /data/Replicate-Test/Data Backup [2016-11-10 11h 41m AM] [2016-11-10 12:11:36] [Info] Resume folder is "/data/Replicate-Test/Data Backup [2016-11-10 11h 41m AM]/2016-11-10 11-42 (failed)/data" [2016-11-10 12:11:36] [Warning] Incremental not possible [2016-11-10 12:11:36] [Info] p2p connect to nas-xx-xx-06 in xxxxxxxx network [2016-11-10 12:11:59] [Info] p2p connect to nas-xx-xx-06 in xxxxxxxx network [2016-11-10 12:12:12] [Error] Unable to connect to nas-xx-xx-06 [2016-11-10 12:12:12] [Error] Connect error code: -51 [2016-11-10 12:12:12] [Error] Please check source device is online and Replicate service is running [2016-11-10 12:12:12] [Info] Unlock target folder: /data/Replicate-Test/Data Backup [2016-11-10 11h 41m AM] [2016-11-10 12:12:12] [Info] Job finished5.3KViews0likes12CommentsCrashplan - My computer as a trusted device to a single share?
Hi All, We recently purchased a second ReadyNAS 102 with the hopes of using the two ReadyNAS 102s as backups for each other. We want to have our two ReadyNASes on two different networks backing up to each other (replicating with the ReadyCloud). At the same time, we want Crashplan to take the data from each ReadyNAS and back up to Crashplan's Cloud. I have another fruitless post explaining my issues with ReadyNAS Replicate returning a P2P error. You can find that here: https://community.netgear.com/t5/ReadyNAS-in-Business/ReadyNAS-Replicate-job-returning-quot-Unable-to-get-local-p2p/m-p/1160592#M5693 This isn't what my post is about but if you have any suggestions it would be most helpful. While trying to figure that out, I'm trying to use the Crashplan that is installed on my PC to backup from a mapped drive mapped to the ReadyNAS. I am able to get Crashplan to back up to a share I mapped, but I needed to open permissions to allow "Everyone" to read and write from that file. For security reasons, I want to allow access to only my computer without the need to log into the networked drive because Crashplan can't access a networked drive that requires another login to a mapped drive. Is there any way to add my computer as a trusted device to a single share?2.2KViews0likes1CommentReadyNAS Replicate job returning "Unable to get local p2p address" Error
Hi All, I recently purchased a second ReadyNAS RN102. Both ReadyNAS RN 102's are running on OS 6.6.0 and are on the same network. I enabled ReadyNAS Replicate on both devices and registered them with the same ReadyNAS Replicate account. Both have static IP addresses, are a part of the same DNS server with 8.8.8.8 and 4.4.2.2 added as alternative DNS's, and IPv6 is disabled completely. Eventually, I want to be able to move one of these devices to another location, but still have them replicate to each other. When I create a job that is supposed to replicate some data (a small amount for test purposes) from one ReadyNAS to the other (and vice versa), I receive the below error in an email message stating, "Unable to get local p2p address". [2016-10-25 10:57:37] [Info] Replicate version: 1.3.0 build R2 [2016-10-25 10:57:37] [Info] Starting backup job "Data Backup [2016-10-25 10h 37m AM]" [2016-10-25 10:57:37] [Info] Locking target folder: /data/Replicate-Test/Data Backup [2016-10-25 10h 37m AM] [2016-10-25 10:57:38] [Info] Resume folder is "/data/Replicate-Test/Data Backup [2016-10-25 10h 37m AM]/2016-10-25 10-39 (failed)/data" [2016-10-25 10:57:38] [Warning] Incremental not possible [2016-10-25 10:57:48] [Error] Unable to get local p2p address [2016-10-25 10:57:48] [Error] Unable to get p2p local ip address [2016-10-25 10:57:48] [Info] Unlock target folder: /data/Replicate-Test/Data Backup [2016-10-25 10h 37m AM] [2016-10-25 10:57:48] [Info] Job finished No actual data from one server is transfered to the other, HOWEVER, empty folders are created to prepare for the backups every time I run the job. Please see this picture: This implies that at least the cloud is able to communicate with the two ReadyNAS devices, but the two devices are not able to communicate with each other. This leads me to a few questions: After ReadyNAS Cloud connects to both devices, is there a point where the devices are attempting to communicate directly with each other. This would make sense. If there is a firewall issue, my firewall may be allowing the ReadyNAS Cloud to pass, but not the other ReadyNAS device. But both devices are on the same network. Idk. If it is a port issue, what port does ReadyCloud use to communicate? Any tips of the trade would be highly appreciated.4.9KViews0likes12CommentsFailover?
We have two of the ReadyNAS 516's on the same LAN. We are replacing an existing Windows 2008 server. We want to have the primary NAS for storage and the 2nd as a backup (really as a failover- and we know it will be manual). How can we quickly get the 2nd unit up as the primary in the case of a total failure of the primary? We have setup with ReadyNAS Replicate, but this looks like a backup and the restore process takes a while.Solved2.8KViews0likes2CommentsReplicate failes since firmware 6.4.0 (RN102)
Hi, since updating to firmware 6.4.0, Replicate over internet failes with exit code 10 (RN102). According to log files the detected connection before the update was relayed (method 5), afterwards LAN (mehod 2). The target NAS is not yet on firmware 6.4.0. Does someone have any suggestions? Thanks, KimSolved3.5KViews0likes3CommentsReadynas Replicate
Hi I have 2 x ReadyNas 312, both running OS 6.4. One is being used for storage of my companies files and every night this is backed up to the other using ReadyNas Replicate. This setup is working well and we have now have an off site backup. The issue that i have is with the reports from replicate. I get an email after each backup stating the files that were copied but it just has a few files, first it says '[Info] Skipped X lines'. Then i just have a few other lines of files that it has copied. Is there a way that i can get a more detailed report from replicate so that i can check all of the files that are being copied. Regard George3.4KViews0likes1Comment