NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
516 Backup Issues
Hi All,
I'm having problems with backup jobs on a 516 (6x2T) running 6.1.8. All of my jobs are backups from the same file server (running Win7x64). The first runs properly, always. The second, which is not only on the same machine but the same physical drive, repeatedly fails mid-backup and says "source cannot be mounted on the system." The third, which is on a different physical drive, fails either immediately or mid-backup, also with the error message "source cannot be mounted on the system." As with other people's experiences, clicking "test connection" gives a positive response for all 3 backup jobs.
These same exact jobs worked fine on my old NV+, and in fact seemed to work initially on the 516 but seem to have broken after one of the firmware updates.
I've been reading the forum posts for years, so I know that other people have had similar problems, and I've tried to take the collective advice given to others, but so far to no avail. I have tried switching from archive bit to timestamp, using the source IP address instead of network name, making the backup source folder its own share rather than just using the shared drive name\folder, resetting all permissions on the drive and share to R/W All, adding a username and PW for the readynas, and adding specific RW permissions for the username in addition to "everyone", and finally erasing the backup jobs and starting again, all with the same result. I can't tell from the logs what is working with any degree of specificity, as the backup job is long enough that the results are always truncated (I don't remember this ever happening with the NV).
As you might imagine it's been very frustrating to upgrade to a much more expensive ReadyNAS, only to get less functionality. I do agree with the repeated complaints on this board that the documentation for setting up backup jobs is incredibly sketchy, which may be why I'm doing it wrong. My hope was to get this working smoothly and then to buy a second one for a remote location backup, but that plan must stay on hold until I'm confident that I can get the backup jobs to work consistently.
Does anyone have any advice for further things I might try?
I'm having problems with backup jobs on a 516 (6x2T) running 6.1.8. All of my jobs are backups from the same file server (running Win7x64). The first runs properly, always. The second, which is not only on the same machine but the same physical drive, repeatedly fails mid-backup and says "source cannot be mounted on the system." The third, which is on a different physical drive, fails either immediately or mid-backup, also with the error message "source cannot be mounted on the system." As with other people's experiences, clicking "test connection" gives a positive response for all 3 backup jobs.
These same exact jobs worked fine on my old NV+, and in fact seemed to work initially on the 516 but seem to have broken after one of the firmware updates.
I've been reading the forum posts for years, so I know that other people have had similar problems, and I've tried to take the collective advice given to others, but so far to no avail. I have tried switching from archive bit to timestamp, using the source IP address instead of network name, making the backup source folder its own share rather than just using the shared drive name\folder, resetting all permissions on the drive and share to R/W All, adding a username and PW for the readynas, and adding specific RW permissions for the username in addition to "everyone", and finally erasing the backup jobs and starting again, all with the same result. I can't tell from the logs what is working with any degree of specificity, as the backup job is long enough that the results are always truncated (I don't remember this ever happening with the NV).
As you might imagine it's been very frustrating to upgrade to a much more expensive ReadyNAS, only to get less functionality. I do agree with the repeated complaints on this board that the documentation for setting up backup jobs is incredibly sketchy, which may be why I'm doing it wrong. My hope was to get this working smoothly and then to buy a second one for a remote location backup, but that plan must stay on hold until I'm confident that I can get the backup jobs to work consistently.
Does anyone have any advice for further things I might try?
4 Replies
- Have you contacted support about this issue?
Considering the first and second jobs: Is there any difference in the configuration of the folders that are the destination for the backup jobs (Snapshots on/off, a service on/off etc.)? - Hi mdgm, thanks for responding - and apologies that I have been on holiday for 2 weeks and thus delayed in answering your questions.
There is no difference in the configuration of the destination folders between the jobs which are completing and the jobs which are failing. In fact, all except for one (including both the working and non-working backups) have the same destination folder. It's difficult to understand why jobs with the same specifications, copying from the same drive share to the same destination folder, would operate differently. I note that even though the backup job fails and says "source can not be mounted on the system," at least *some* files are in fact being backed-up. So the NAS is indeed able to connect properly, but not to complete. Is there anything in the logs I should be looking for? Unfortunately, as in my previous post, the backup job is large enough that the file log is truncated, so I can't tell from logs what is being backed up and what is not, or if the job fails consistently at the same point or file.
I have not contacted support as my understanding is it is only valid for 90 days from purchase, and I'm outside that window. Instead they have directed me to the knowledgebase, and to this forum.
It sounds as though other people have had similar problems, and so I hope to find that one of their solutions works for me too. I'd really like to lick this issue! - You can still open an online support case at my.netgear.com after the 90 days are up. If you called support they should have told you about that option as well.
I would suggest you open an online support case and post the case number.
Also probably try 6.1.9 RC8. 6.1.9 RC8 won't truncate the backup job logs (I think) so may give better info as to what's going wrong if it still goes wrong on that. - OK, thanks - I shall try both of those ideas! Will report any conclusions here in case they are helpful to others in the same situation.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
