- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
Backup-----push data from NAS to another source
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Backup-----push data from NAS to another source
firmware 6.7.4
readynas 2120
In the GUI, under the backup tab, I have a task the pushes some of data on the NAS to a drive on our server( win server 2008).
Task settings
Remote:windows/NAS (timestamp)
I don't have a schedule for this, it backs up only when I click start
options tab
- schedule full backup: everytime
- remove the contents of the backup destination before the full backup
Often times I get a message like below when task is finished. But the same task worked fine the day prior. As soon as I go to the destination and delete or rename target folder then everything is fine again for a bit.
How do you post a screenshot or attachment to this forum, am I just overlooking it?
Backup Status: Fail: destination is read-only or files/folders could not be created. Check if these files or folders meet the destination file system limitation.
Cannot create file '/job_020/Backup_From_NAS/test123/__foo__.10845' (error: No such file or directory)!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Ok, thanks.
Any thoughts to my backup error?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Are you using the hostname or the IP address in the remote destination configuration? Often IP address works more reliably.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
I am using the host name for the remote destination
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Try switching to IP address for a bit, and see if that is more reliable.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
No luck.
I switched to IP address instead of host name and I get the following message.
Backup Status: Fail: destination is read-only or files/folders could not be created. Check if these files or folders meet the destination file system limitation.
Cannot create file '/job_020/Backup_From_NAS/test123/__foo__.5014' (error: No such file or directory)!
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Under the task options for a backup, I don't think "schedule full back---everytime" and having the remove the contents of the backup destination before full back box checked is a good combination.
Though those are the exact same settings I use when I backup to USB drive and that never gives me errors.
?????
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Are there any errors reported on the Windows Server?
Possibly the NAS is using SMB1?
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
No errors on server.
Where would I see SMB1?
On the NAS, under the share settings, under network access, I see SMB, NFS, AFP, FTP..........., but I am only using SMB
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
It's possible that the windows server was patched to remove SMB1 (since there was a recent CVE), and perhaps that's causing a problem. But that's just a theory, and I'd expect something in the server logs if that were the case.
The normal web ui doesn't give you visibility into the SMB modes. There is an SMB Plus app from Netgear that does.
You might also try re-entering the PC credentials in the backup job settings.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
When I go to destination tab, enter creds and click test connection I get window......successfully connected to ..........
How could it be a Windows server problem, if by changing the settings NAS
from------Under the task options for a backup, "schedule full back---everytime" and having the remove the contents of the backup destination before full back box checked
To------first time and remove conents NOT checked
then it appears the problem goes away....maybe
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
@FG wrote:
...then it appears the problem goes away....maybe
I can't read your mind and this is the first time you've mentioned it.
Though I'm not convinced it has gone away. The error happens when the NAS tries to write to the destination folder. If you just make the settings change and run the job again, there might not be any writes to do. With the remove option checked, of course it begins by deleting files.
Another thought is that the Windows server isn't giving the NAS write permission. If you are entering credentials for the server in the backup job, perhaps double check them in the PC. If you aren't entering credentials, perhaps create an account on the server for the NAS, and use those credentials in the backup job.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Hi,
It's a bit odd why it would go read only. It is a difficult thing to troubleshoot with several possibilities;
- Does the mount point go R/O on the NAS side?
- Does the win server make the destination R/O for some reason?
- Does it happen because the file permissions changes on stuff inside the windows folder, denying the NAS to write to it?
- Could it be some windows sync program causing the folder to go read only (locking it) ?
Is not that easy to answer straight away. However, what the NAS does is really simple. It mounts an smb share and edits/copies data into it. That is really straight forward. I think the reason StephenB asks about the widows side is because more things can go wrong there. Best approach would be to start eliminating things.
When the job fails, check:
- File permissions on the Windows folder (Properties --> Security). Are files and folders still R/W for the user that the NAS is authenticating with? Try resetting the permissions on the windows folder and all content inside.
- Is there a pattern? If you run the job at a different time, does it work?
- Turn off programs like AV and sync agents, then try again.
- Login to the NAS over SSH and monitor the Windows mount point when the job runs: watch "mount"
Does the mount point stay R/W on the NAS side?
- When it fails, don't rename the folder in windows. Delete all files inside the folder manually instead and run the job again. Does that help?
- When it fails, don't do anything on the windows side. Delete the backup job on the NAS and re-create it. Does that do anything?
You have to try and determine where the issues is first. NAS side or windows side. When did the problem start? Any recent program installs around that time or other changes, etc.
We might be able to help better if we know on which side the fault lies 🙂
Cheers
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
@Hopchen wrote:
It's a bit odd why it would go read only.
My understanding from the first post is that the NAS is unable to write to the share on the PC. It'd be helpful to get clarification on this point though.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
The NAS can write to the PC. It completes most of the backup task, writing nearly all of the data then at some point fires off the error message.
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
@FG wrote:
The NAS can write to the PC. It completes most of the backup task, writing nearly all of the data then at some point fires off the error message.
So taking this one as an example:
Backup Status: Fail: destination is read-only or files/folders could not be created. Check if these files or folders meet the destination file system limitation. Cannot create file '/job_020/Backup_From_NAS/test123/__foo__.10845' (error: No such file or directory)!
It might be useful to know
- the folder permissions/owner for subfolder test123
- whether __foo__.10845 already existed in that folder, and if so what permissions it had (And who owned it).
It would also be useful to know if you could access the NAS share from the PC and copy __foo__.10845 into that folder (or not).
- Mark as New
- Bookmark
- Subscribe
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Re: Backup-----push data from NAS to another source
Looking at this at face value:
Backup Status: Fail: destination is read-only or files/folders could not be created. Check if these files or folders meet the destination file system limitation. Cannot create file '/job_020/Backup_From_NAS/test123/__foo__.10845' (error: No such file or directory)!
Does /job_020/Backup_From_NAS/test123/__foo__.10845 actually exist on the NAS? Maybe the real file name has an illegal character in it for a Windows file name? Or could it have been deleted while the backup job was ongoing? Are you backing up into a Windows folder that is too deep and the resulting full path name is more than 260 characters?