NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Can't add backup job after update to OS 6.2.0
I have a RN312 locally which nightly runs 5 backup jobs to a remote Readynas DUO at my daughters house. I am running Rsync jobs, and the remote destination is specified as Workxxx.homeip.net (Daughter has a DSL connection with dynamic IP address).
Now - problem is, yesterday I updated my RN312 to OS 6.2.0. The original 5 jobs successfully run, however when I attempt to add a 6th backup job the new version doesn't accept the remote host specification of Workxx.homeip.net. If I determine the currently assigned IP address of the remote Readynas and plug in its IP address ( 173.190.xx.xxx ) then the backup job works fine. But specifying a DNS name isn't accepted (The hostname tag shows up in red and I get a message indicating 'Value must be a valid host name'
What is the syntax for specifying a valid host name? (Looking at the other 5 jobs, the host name field has the workkxxx.homeip.net specification and they work fine. I haven't attempted to alter them for fear if I touch one of them it may reject the host name currently in them. Is there any MEANINGFUL documentation with examples anywhere? (The online examples are pretty worthless in my mind).
Now - problem is, yesterday I updated my RN312 to OS 6.2.0. The original 5 jobs successfully run, however when I attempt to add a 6th backup job the new version doesn't accept the remote host specification of Workxx.homeip.net. If I determine the currently assigned IP address of the remote Readynas and plug in its IP address ( 173.190.xx.xxx ) then the backup job works fine. But specifying a DNS name isn't accepted (The hostname tag shows up in red and I get a message indicating 'Value must be a valid host name'
What is the syntax for specifying a valid host name? (Looking at the other 5 jobs, the host name field has the workkxxx.homeip.net specification and they work fine. I haven't attempted to alter them for fear if I touch one of them it may reject the host name currently in them. Is there any MEANINGFUL documentation with examples anywhere? (The online examples are pretty worthless in my mind).
9 Replies
Replies have been turned off for this discussion
- Do your email alerts still work?
Have you verified the DNS settings are correct in the Dashboard? - Once you have setup the new job ( with the IP address), can you go into the job to edit it to the correct details? It seems the initial setup of a backup job is new in 6.2.0 but when you edit a task the old format with tabs is present. It may then accept the information you need to insert.
- DNS settings are: 192.168.1.1 (my router) and 8.8.8.8 (Google DNS), - Yes, my mail alerts work (Have 6 alerts this morning telling me my backup jobs have failed).
No - I cannot edit the job later to alter the host name - I get the message telling me the host name value must be a valid host name.
This morning ALL my backups have failed with a timeout attempting to connect to the remote NAS. Apparently the IP address of the remote NAS has changed.
Now that I have updated to 6.2.0 I cannot go back to a working version of 6.1.9. - I would suggest trying using a different DNS to 8.8.8.8
- Have you asked dyndns about this? (if I recall correctly, they own homeip.net)
If you enable SSH, you can use putty to connect to the NAS command line interface, and then try pinging the host names, and verify that the NAS is not resolving the names.
You could alternatively temporarily set up your PC to exclusively use 8.8.8.8 as the DNS server, and try the same experiment on the PC. Then try the experiment again using 192.168.1.1 as the exclusive DNS server. - Quick update.... Reason the original 5 jobs failed was because the DYNDNS updater on my daughters system hadn't run. I refreshed her IP address associated with WORKxxx.homeip.net and the 1st 5 jobs ran successfully. So my unit IS able to resolve host names - the problem is the new release will not allow me to create a NEW backup job that specifies a HOST NAME rather than a hard coded IP address. Is there some special syntax I am to use, or is it just broke?
- I think its just broke.
I can't create a new rsync job with a host name either. I tried my own DDNS hostname (which is noip, not dyndns), and also a hosted server using a two part name (xxxx.org).
FTP backup fails similarly.
Both balked when I tried to hit "next", and when I hovered over the host name said "value must be valid host name". - Thanks for reporting this.
- Hello,
I can report I also get the error backup for a FTP and have to use the IP Address instead of the host name.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
