NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
alldidasmc
May 19, 2011Aspirant
All FTP backup jobs become Full = "Every Time" with upgrade
I just upgraded from 4.2.15 to 4.2.17. Now, all my FTP backup jobs have been changed to "Schedule Full Backup: Every Time." "Every Time" is the only option in the drop-down, so I can't fix them! This is ridiculous, now all my FTP backup jobs are just re-running the same data and never get to the new data before failing out!
I have an NVX. I have about five jobs that are ruined.
I cannot recreate them, either. If I create a new backup job, when the screen loads I see all the proper options for this drop-down:
First time
Every week
Every 2 weeks
Every 3 weeks
Every 4 weeks
Every time
As soon as I change EITHER the source OR destination to FTP Site, the drop-down gets limited to "Every time!"
-Robert
I have an NVX. I have about five jobs that are ruined.
I cannot recreate them, either. If I create a new backup job, when the screen loads I see all the proper options for this drop-down:
First time
Every week
Every 2 weeks
Every 3 weeks
Every 4 weeks
Every time
As soon as I change EITHER the source OR destination to FTP Site, the drop-down gets limited to "Every time!"
-Robert
34 Replies
Replies have been turned off for this discussion
- alldidasmcAspirantSo if we use this Toggle, the FTP backup jobs will still be setup as "Full Every Time" but will actually be incremental every time?
-Robert - ewokNETGEAR ExpertYes, they'll be listed as full every time, but will actually be incremental.
- csternAspirantHi,
Are there any updates to this?
Also, my remote server (i.e. the one in "the cloud", not the readynas) has a nasty habit of timing out, or rather pause, repeatedly. I see that when I use Beyond Compare 3.0 to manually ftp my changed files to the remote server. The pause can be as long as a couple of minutes at a time, but eventually the ftp server will respond and continue whatever process it was doing.
Using the standard frontview ftp backup, the backup is terminated when this happens and the backup is never completed. Is there a way to disable the time out, or to allow a much longer pause before the backup job is aborted? If needed I don't fear tinkering with config files on the readynas using SSH and vi.
Thanks for your assistance.
Claus - csternAspirantOne more thing: The timestamps of the FTP'ed files are not updated, rather they are set to the time of the FTP transfer.
I also use Beyond Compare 3.0 from Scooter Software to semi-manually transfer the files to my remote host. And BC3 is perfectly capable of resetting the timestamp to the original file date.
I hope that NG will do something about this missing features (incremental FTP backup and timestamp).
The thing about resume/file size of course should also be fixed, although it might not be trivial. On a Unix host smaller files appear to occupy different footprint depending on the server. I can see that e.g. on my NAS and remote storage space a file which on the readynas is listed as 14,958 bytes is listed as being 14,428 on the ftp server. Another example is 1,740 vs 1,631 bytes. Big files however for some reason match exactly - and it is not all small files that come out as being different sizes (a direct file compare shows no difference in contents). - CalgaryIT1AspirantI would just like to add my input that this feature ("proper incremental backup over FTP/SFTP") is absolutely crucial for us.
It's become a standard feature and is well-refined for competitors such as Qnap, but I was shocked to see it wasn't working for our new ReadyNAS Pro. We rely on this method of remote backup because we have about 1TB of data to backup which is far too expensive to backup using any method but FTP.
We're going to try this toggle addon for now, but if there isn't a proper working solution soon, we'll be forced to jump ship. - shadow11Aspirantis this add on still needed with radiator 4.2.22? I am having issues with FTP backup timing out and would like to know if this add-on would help fix the issue. The post is 1 year old, so would like to know if it is still relevant.
Thanks. - StephenBGuru - Experienced UserAre you attempting to do an incremental backup with FTP?
- shadow11Aspirantyes, that's the goal. Is there a better solution to getting a backup to an ftp server?
- StephenBGuru - Experienced UserIf you want to do incremental backup with FTP than you need the add-on. Note the warning:
Warning: the reason this was taken out is because this behavior is actually pseudo-incremental and can have nasty side effects. Incremental backup was a side effect of having upload resumes enabled. With upload resumes enabled, the backup manager will try to resume uploading a file if a file of the same name on the destination side was smaller than that of the file on the source side, regardless of whether the rest of the file matches or not.
So if you are backing up (for instance) updates to an existing document, this method will likely end up with a corrupt file on the backup site.
Rsync would be better if it is available on the remote side. - shadow11AspirantThanks for that info. I did see that warning in the thread, but it wasn't exactly clear what it meant. Now that I understand the warning better, I may reconsider. But the files I am backing up are mainly static (i.e. don't change much after creation). So I think my main risk would be for interrupted transfers that would resume at the next backup event. But this is for disaster recovery use in the event my local backups and nas machine stop functioning. I did see a couple of other threads that may suit my needs better (i.e. goodsync and crashplan). I'll check those options out aswell. Although, it looks like Goodsync would require another computer to run the backup; and there is no "addon" for crashplan (since i haven't been a linux user for years, i'm a bit weary to get crashplan set up).
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!