Forum Discussion

Retired_Member

Feb 07, 2018

FTP Backup error

Firmware 6.9.2 Occasionally, FTP scheduled backup fails with the errors below. We scheduled the exact FTP backup activities with another client, and everything works: only the ReadyNAS fails. -----...

Backup

ReadyNAS Backup

Retired_Member

Mar 28, 2018

Unfortunately the problem persists even after the upgrade:

Error backup job xxx: Connection cannot be established. Check the connection and authentication, if required.



-------- Backup Job Information --------
Backup Job Name: xxx
Backup Job Type: Full
Protocol: ftp
Backup Source: [remote:ftp]/ftp://path_to_ftp/
Backup Destination: [Backup]/xxx
Backup Start Time: Wed Mar 28 2018 15:05:04
Backup Finish Time: Wed Mar 28 2018 15:07:44
Backup Status: Fail: Connection cannot be established. Check the connection and authentication, if required.

Amidala

NETGEAR Employee Retired

Apr 02, 2018

I've been trying to set every one hour, two hours, four hours until 24 hours, schedule full backup first time or every time, but I cannot reproduced this problem. Could you please provide more detailed information?For example, set every few hours, full or incremental backup job, the file size for backup files.Thank you.

StephenB
Guru - Experienced User
Apr 02, 2018
Perhaps it would also be useful to set up a local FTP server for testing, and see if you can replicate the problem on your LAN (removing the internet path from the equation).
Retired_Member
Apr 03, 2018
The bakcup is a daily backup (every 24 hours from 15.05 to 23.05).
Backup Job Type: Full

I could try a local ftp address, but I need the remote one to work.
This is the first time an application fails to connect or whatever other action with my ftp server, so I'm pretty sure it's a Netgear problem, but I'm not able to provide further details.
StephenB
Guru - Experienced User
Apr 03, 2018
FWIW, I tried this with an FTP server over the internet, and I also got a connection timeout on a data transfer. The web ui log showed "Connection cannot be established" - though it was in the middle of the backup job, so that particular error is misleading.

The backup job failed at that point.I then re-ran the backup job and it worked correctly. I don't see anything useful in the log zip file. This particular server is fairly slow, so I am wondering if a timeout changed. Is the backup job supposed to retry (e.g., download resume)?

FileZilla transfered the files successfully the first time.