NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
FG
Jun 21, 2017Aspirant
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 ...
StephenB
Jun 23, 2017Guru - Experienced User
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.
FG
Jun 23, 2017Aspirant
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.
- StephenBJun 23, 2017Guru - Experienced User
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).
- SandsharkJun 24, 2017Sensei
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?
Related Content
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!