NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Sceduled Backup doesn't work anymore
Hi folks, I used to scedule a backup once a day from the readynas drive to a the external usb3 drive. This worked for years. Without any reason, the scedule doesn't start any more. Manual starting wo...
Hi Stephen,
thanks for helping. The update button says system is up to date. RAIDiator 5.3.13
Roland111 wrote:
RAIDiator 5.3.13
Ok. So it is a definitely a v2 NAS. That's not a model that I own.
Are the logs empty even after the manual job completes?
Have you checked the USB drive for added files?
Have you looked in the full downloaded log zip file for errors (not just the backup logs)?
Hi Stephen,
the logs show the hole backup entries when manual startet. Looks normal. But as the sceduled backup doesn't start, there is no entry for that. It's just like there weren't any backup jobs sceduled.
I checked the online log first. It shows that last year the disks had failures. I replaced them one after another and the restoring worked perfekt. After that I made a firmware update and after the update the jobs didn't start anymore. I then tried several settings in the backup scedule, while nothing worked. In the online backup aren't any entries that show, that the system tried to do the backup job.
Then I downloaded the logfiles and opened the error log. But I truely don't understand it. Actual entries are like this:
[Fri Sep 20 06:25:15 2019] [notice] caught SIGTERM, shutting down
[Fri Sep 20 06:25:20 2019] [warn] RSA server certificate CommonName (CN) `192.168.178.86' does NOT match server name!?
[Fri Sep 20 06:25:26 2019] [warn] RSA server certificate CommonName (CN) `192.168.178.86' does NOT match server name!?
[Fri Sep 20 06:25:26 2019] [notice] Apache/2.2.16 (Debian) mod_ssl/2.2.16 OpenSSL/0.9.8o DAV/2 Axis2C/1.6.0 mod_apreq2-20090110/2.7.1 mod_perl/2.0.4 Perl/v5.10.1 configured -- resuming normal operations
[Fri Sep 20 09:55:36 2019] [error] [client 192.168.178.41] File does not exist: /frontview/dashboard/images/scroller/style1-lr.png, referer: https://192.168.178.32/admin/dashboard.html
[Fri Sep 20 09:55:36 2019] [error] [client 192.168.178.41] File does not exist: /frontview/dashboard/images/scroller/style1-tb.png, referer: https://192.168.178.32/admin/dashboard.html
[Fri Sep 20 09:57:29 2019] [error] [client 192.168.178.41] File does not exist: /frontview/dashboard/images/scroller/style1-lr.png, referer: https://192.168.178.32/admin/index.html
[Fri Sep 20 09:57:29 2019] [error] [client 192.168.178.41] File does not exist: /frontview/dashboard/images/scroller/style1-tb.png, referer: https://192.168.178.32/admin/index.htmlDo you understand that?
In the backup logs there is only the last backup job. I have two external drives that should backup every second day each. Job 1 that I started manually yesterday, shows a normal full executet backup job and lists all directories that have been backed up.
Again, thanks for your help.
I deleted one job an recreated it new. As I recall, the external drives had to be also replaced in 2018. But even if that is the reason, there should have been some kind of error message.
Is the NAS also on a power schedule? Or is it always on?
Probably best to private-message (PM) one of the mods ( JohnCM_S or Marc_V ) a downloadable link to your logs and ask them to take a look. Don't post the logs publicly. Send a PM using the envelope icon in the upper right of the forum page.
Roland111 wrote:
[Fri Sep 20 06:25:20 2019] [warn] RSA server certificate CommonName (CN) `192.168.178.86' does NOT match server name!?
[Fri Sep 20 06:25:26 2019] [warn] RSA server certificate CommonName (CN) `192.168.178.86' does NOT match server name!?These are because that the NAS created it's self-sign cert when it was assigned a different IP address. It's safe to ignore them - you are already going to see some cert warnings (at least with current browsers) simply because the cert is self-signed.
Roland111 wrote:
referer: https://192.168.178.32/admin/dashboard.html
[Fri Sep 20 09:55:36 2019] [error] [client 192.168.178.41] File does not exist: /frontview/dashboard/images/scroller/style1-tb.png, referer: https://192.168.178.32/admin/dashboard.html
[Fri Sep 20 09:57:29 2019] [error] [client 192.168.178.41] File does not exist: /frontview/dashboard/images/scroller/style1-lr.png,The two files must be referenced in the web server html somewhere, but don't exist. They probably aren't actually be used (so would be harmless).
Neither set of errors is related to the backup.
The nas is always on. Only the disks power down after a long periode of non using. I tried several times to start sceduled backup with the new job, but the scedule doesn't start anything. I remember to set the hole system back to factory reset and try again last year. So it shouldn't be the update either. Maybe there is a onboard battery that is empty, like on a computer motherboard. But as it is always powered on, I don't think that is the problem.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
