NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Error: cp: cannot create regular file
I have a FrontView backup job that I have been getting the following error for some time now and I have not been able to correct this:
There are many files that match the pattern of 'dailynoaareport*.htm' using the WIndows wildcard character of '*', but no files with the name of 'dailynoaareport*.htm' from a UNIX name standpoint. I have used Putty to look for any file name that has an asterix character in it and I cannot see one. Any clues as to how I can resolve this? Thanks for your help.
ReadyNAS Pro 4 with all the latest firmware/software.
Error encountered copying data from source path /Website/ ==> //192.168.0.95/Backup_S_3/Website due to unknown reason. Please see log.
cp: cannot create regular file '/job_010//Website/./wdisplay/dailynoaareport*.htm': No such file or directory
There are many files that match the pattern of 'dailynoaareport*.htm' using the WIndows wildcard character of '*', but no files with the name of 'dailynoaareport*.htm' from a UNIX name standpoint. I have used Putty to look for any file name that has an asterix character in it and I cannot see one. Any clues as to how I can resolve this? Thanks for your help.
ReadyNAS Pro 4 with all the latest firmware/software.
5 Replies
- Website is a share on the pro? Is there a wdisplay folder in it?
What backup protocol? - 'Website' is the share on the Pro 4 and 'wdisplay' is a folder in that share.
/c/Website/wdisplay/
The FrontView backup is using 'Share: Website' as the source and the destination is a 'Remote: Windows/NAS (Timestamp)'. The remote is pointing to another network location. The test connection does not show any errors to that location.
Please let me know what other information you would like, and thanks for your help. - I suggest creating a test backup job using a different share as the source but the same destination, and see if that fails the same way (with a different file).
- I created a new backup job with a different share on the same NAS as the source and the same destination as the job that has the error. It completed without any errors.
What next? (again, thanks for your help) - That test proves that the destination is accessible, so the problem has to be in the source share.
It is odd that the backup job is seeing that filename. I'd try changing your test backup job's source share to Website, and run it again - just to see if the error starts showing up there as well.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
