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.
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: Success
SMB 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.
Logs from RN102 sended. Older one are Befor Factory default. New one are after 2x factory default.
Thank you.
Iknow that windows server 2003 is obsolete. But there are still costomers who use it for connecting old disk arrays (which is not supported by windows 2012 etc)
Backup jobs are good addition to other backup SW (image SW), and they are very good for incremental backup of larges folders/shares from another storage (server/NAS). This can create 2nd backup which is OS Type independent and so we have another copy of specific data on our NAS.
I'm using backup jobs for create incremental daily backups from selected shares from servers to NAS with using snapshots as a aditional way to protect data. It is a backup copy that is OS and software independent with minimum backup time.
It is problematic that backup with backup job can not be automatically created (backed up) FROM or TO these old systems, but manual copy or copy files with web browser is OK. Test connection to server is reported OK.
We tested a backup with Windows 2003 and whilst it took a lot longer than we expected it still completed. So perhaps there is something a bit unusual at your end.
I am testing it in bakup job from windows XP with 4 excel documents with aprox 104kB in size.
Time til backup job ends:
on RN204 from PC with Windows 7 Pro x64:
Backup Job Name: TestWin7
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///cajo7n/0101
Backup Destination: [test01]/
Backup Start Time: Fri May 20 2016 14:29:10
Backup Finish Time: Fri May 20 2016 14:29:11
Backup Status: SuccessTime is about 1 second.
On RN104 From PC with Windows XP 7 (same 4 xls files):
Backup Job Name: testXP
Backup Job Type: Incremental
Protocol: cifs
Backup Source: [remote:cifs]///rodicia/0
Backup Destination: [test01]/
Backup Start Time: Fri May 20 2016 14:20:40
Backup Finish Time: Fri May 20 2016 14:37:56
Backup Status: SuccessNow it is 17 minutes of running backup job FOR 4 excel documents with aprox 104kB in size!!!
On another RN102 trying backup from Win2003 server (for 15 minutes no files copied at all)
RDP on clients server.
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??
I Thing, there is something is terribly wrong with this after upgrade fo FW 6.5.0. Nothing else changed. Nothing. There was 1 thing that changed only. Upgrading NAS units to FW 6.5.0. This is result. Thats all.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
