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 ...
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.
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 Android
Thanks 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!
