NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Michael_Oz
Jun 27, 2016Luminary
Error backup job 'name': destination cannot be accessed. USB Disc. RN316 OS 6.5.0
RN316 F/W OS 6.5.0 (yes I know .1 was just released...)
I have two, same, USB3 external HDDs.
tl;dr - one fails with 'destination cannot be accessed.' when I run a backup to it. It connects OK and I can browse it via 'shares' in Readynas web. It is NTFS, I disconnected it and chkdsk'd it OK. Any ideas? Logs I can check? It completed a backup in the past (full, current job is incremental).
longer vers.
Now that USB3 works properly, I setup my backups.
My plan was to have a father/son offsite backup, alernating each week.
So two backup jobs, which run on a Monday, one will fail as that HDD is not connected.
The backup jobs auto-eject.
So I unplug one when the email tells me it is done. Put it offsite, get the other, plug it in for the next week,when the other job will run.
The two are named Red & Black (case colours) and ReadyNAS calls them USB_HDD_4 & 5.
I started with Red(4), a full backup. OK
Then next week Black(5), again a full backup. OK.
{I also did a test incremental i.e 2nd run, to Black here, OK}
This weekend I plugged Red back in, connected OK, however when the job ran it got the error 'Fail: destination cannot be accessed.' (log below).
Note this would be Red 1st incremental backup, as 'schedule full backup' was set to 'first time'
I re-connected, re-ran, same.
I ejected, chkdsk'd it OK.
Reconnected, re-ran, same. I can browse it OK.
I got Black(5) and ran its backup (again incremental), works OK.
The two jobs are identical except name and destination.
Any ideas?
Note, on checking kernal.log, I note (was reminded) Red was formatted in Windows 7, I can't remember formatting Black, may have been out-of-box.
I cut-down and annotated the log here.
12 Replies
Replies have been turned off for this discussion
- Michael_OzLuminary
I formatted the Red HDD, now shows up as USB_HDD_6.
First full backup worked.
2nd incremental worked.
I then connected the Black and ran its job, error 'destination cannot be accessed.' (which was the Red error previouly).
Reran Red backup, OK.
I'm surmising that an incremental share backup is relying on something on the destination which the other backup job is overwriting.
Seeking confirmation via this
So any suggestions on how to do incrementals to two destinations?
- Michael_OzLuminary
I'm now testing a 'remote' Windows/NAS (timestamp) from the same local NAS as the host...
- Michael_OzLuminary
Well two alternating jobs as discribed in OP but using remote Windows/NAS (timestamp) also results in 'destination cannot be accessed.' on the alternate incremental job.
aaarrghhh
If it is using timestamps (presumably comparing source file to possibly existing file in destination) WHY should it not work?
- omicron_persei8LuminaryDon't take "full backup first time" literally. What it means is not a full back everytime, or not a full backup every week, in opposition with the other options.
For 6.5.1, I'm quite sure it won't make any difference. But "various bug fixes and enhancements" are always implicit.
I will test your job rotation config, and will post here my results.
But I don't think you need to have two separate jobs. If you create a single job with a usb port a destination, you should get your "incremental" jobs with rotation working. The job doesn't rely on any database or file on the destination, it just transfer the newer/missing files.
Btw, it might be something to consider to actially run a full backup job every two weeks (or four, can't remember the option), so you have one hdd with on incremental and one hdd doing full backups everytime. That way, you'd have to different kind of external backups, increasing the level of protection.- Michael_OzLuminary
omicron_persei8 wrote:
But I don't think you need to have two separate jobs. If you create a single job with a usb port a destination, you should get your "incremental" jobs with rotation working. The job doesn't rely on any database or file on the destination, it just transfer the newer/missing files.Thanks for the hint, I didn't see the 'USB Back...' options, I thought you had to use USB_HDD_n, which was a PITA as the n can change.
Testing now.
- Michael_OzLuminary
omicron_persei8 thanks for pointing out the port option, 'USB Back Left' works as I expected, with one job too.
Using ports v's USB_HDD_n also has benifit that you can edit job settings when HDD is not connected, which was a PITA (should be fixed, and allow destination to be changed when not connected IMO)
Note for posterity: Left/Right is as viewed from the rear, v's e.g. left being on the left side.
Related Content
NETGEAR Academy

Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!