NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
RN102 after FW update to 6.5.0 no backups
After updating 1 RN102 (my client) to FW 6.5.0 all backup jobs failed. No files copied. I deleted jobs, recreated them all and nothing. Remote is server IP/share (windows) to local share copy. After run show Running, but no file is copied. if i cancel the joRN102 after FW update to 6.5.0 no backupsb i get log with running time about 3 seconds. Even if job was "running fom minutes" Need a help.
-------- Backup Job Information -------- Backup Job Name: M Backup Job Type: Incremental Protocol: cifs Backup Source: [remote:cifs]///192.168.0.250/000 Backup Destination: [Dokumenty]/000 Backup Start Time: Wed May 18 2016 21:23:36 Backup Finish Time: Wed May 18 2016 21:23:39 Backup Status: Fail: cancelled by user.
Kardano wrote:
I think this is not "a lot slower". It is unusable. How can I to get backuo of directory with size in GB when 104kB (4 excel files) took 17 minutes??
Large backup jobs wouldn't be an actual problem. The slowdown is only during the protocol negotiation phase. 6.5.0 supports SMB3 and SMB2 for backup jobs now, but Windows XP does not respond to SMB2 or SMB3 protocol negotiation packets. So it takes the ReadyNAS a couple minutes to time out for each modern protocol negotiation attempted, since we don't get a failure response -- we get no response.
Once the backup job actually starts (after protocol negotiation) it runs at normal speeds.
We'll reduce the timeout during protocol negotiation in 6.5.1, so it will only take a minute or so on unsupported legacy clients. But your backup jobs will work fine in 6.5.0. They'll just take an extra 15 minutes or so more than normal each time they run. There isn't any additional overhead or anything, so there aren't any other side-effects during the negotiation period.
14 Replies
Replies have been turned off for this discussion
tI did factory default of the unit. changed NAS name. create new job remote (nas timestamp) to Local. Test for connection OK, backup start running, no files copied, backup running till i canceled it. No error was given. tried copry from NAS to remote server (Windows 2003 share) no files copied.
No problem Until unit was upgraded to FW 6.5.0
Tested on RN 104 exact the same IF:
Source or target is PC with Windows XP or Windows server 2003.
Test connection OK, backup jpb endless running, no files copied. Tested both ways.
Backup Job Name: testXP
Backup Job Type: Full
Protocol: cifs
Backup Source: [remote:cifs]///rodicia/0
Backup Destination: [test01]/
Backup Start Time: Thu May 19 2016 0:45:00
Backup Finish Time: Thu May 19 2016 0:45:02
Backup Status: Fail: cancelled by user.Job was running on RN104 for 3 minutes.
Backup Job Name: TestXP
Backup Job Type: Full
Protocol: cifs
Backup Source: [remote:cifs]///rodicia/0
Backup Destination: [test01]/
Backup Start Time: Thu May 19 2016 0:50:28
Backup Finish Time: Thu May 19 2016 0:50:30
Backup Status: Fail: cancelled by user.Job was running on RN204 for 3 minutes.
With FW 6.5.0 IS IMPOSSIBLE TO BACKUP TO or FROM PC/Server With Windows XP or Windows Server 2003 with Remote: Windows/NAS (Timestamp)
Is it possible to Fix this ERROR ASAP? or it is a new "function"? (I hope it's bug, not a function)
If it is function, then ReadyNAS is pointless or NOGO for many my clients. As we need to backup this way older servers or storages.
with Windows Server 2008 R2 is all OK. This is EXACTLY same job as above, source is Win 2008 R2.
All IS OK
Backup Job Name: TestW2008R2
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///WIN-4KJ5CT5RRMJ/000
Backup Destination: [test01]/
Backup Start Time: Thu May 19 2016 1:09:31
Backup Finish Time: Thu May 19 2016 1:11:18
Backup Status: SuccessSMB Plus settings has no effect. I tried with SMB1. no change, no backup.
Can you send in your logs (see the Sending Logs link in my sig)?
You shouldn't still be using Windows XP or Server 2003. Those are 13+ years old. These are EOL and are getting no more security updates from Microsoft.
Microsoft extended security updates beyond the usual 10 years to give extra time to migrate across to something newer.
Anyway to backup a server it's generally best to use software running on the server to do the backups not a backup job on the NAS.
This will be looked into, but I want to point out the supported OS versions from our manual:
Supported Operating Systems
The ReadyNAS supports the following operating systems:
• Microsoft Windows 10 (32 and 64 bit)
• Microsoft Windows 8.1 (32 and 64 bit)
• Microsoft Windows 8 (32 and 64 bit)
• Microsoft Windows 7 (32 and 64 bit)
• Microsoft Windows Server 2012 (64 bit)
• Microsoft Windows Server 2008 R2 (64 bit)
• Apple Mac OS X 10.7 or later
• Linux, Unix, Solaris
• Apple iOS
• Google AndroidThanks for your response and help (will be looked into).
I know that Windows Server 2003,XP, Vista etc. ARE obsolete, but some people (customers) change their HW and OS when.. you know....it die. And they think that when it was ok and it worked till today, it have to work also in future. (I have some customers in need to manage specific industry HW (without possibility of replacing by newer model), which has not any new version SW that work under common OS) And they think that wneh ti was ok a nd it worked till today it have to work in future.
Maybe it helps to write warning in some future release notes, (something like - from this release backup and some functions not working with old OS like XP etc.) And give to admin some switch that turns off that pop-up with suggesting FW update.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
