NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Backup not working
I haven't run my regular backup jobs for a month. In that time I have: Replaced disk #1 after failure & resynced Replaced disk #2 after failure & resynced Upgraded to version 4 of FrontView N...
I recently started having problems with about 6 out of 8 backup jobs on my ReadyNAS 1000-S after updating to firmware version 4.01c1-p1.
I've had these backup jobs scheduled and working for over a year. Suddenly, after updating to 4.01, a bunch of them have been failing, all with a similar error message.
Job: 007
Protocol: cifs
Source: //server1/data/shared
Destination: [BU_Shared]/
cp: cannot stat `/job_007//shared/.': No such file or directory
Backup failed. Tue Mar 25 01:05:09 EDT 2008.
Reason for failure:
Error encountered copying data from remote source path //server1/data/shared ==> /BU_Shared/ due to unknown reason. Please see log.
All the jobs are set up as Windows Timestamp jobs, backing up from locations on my server to NAS shares. Odd thing is, a couple of them work, but most of them fail with the same reason: "no such file or directory". Of course, the directory is there, permissions are ok. When I test the connection to the backup source, it successfully connects using my username and password.
I tried several things (using the IP address to the source, instead of the named path, deleting and recreating the backup job) and couldn't get the jobs to work again.
I finally discovered that if I change the job type on the failing jobs to "Archive Bit" instead of "Timestamp", the job completes successfully.
Any idea why I can't use "Timestamp" on some jobs, but I can on others? I guess it doesn't really matter to me, but I didn't have a problem with certain timestamp jobs failing until I updated the firmware, unless it's all a coincidence. The only other thing I've done on my network is perform a server reboot.
I've had these backup jobs scheduled and working for over a year. Suddenly, after updating to 4.01, a bunch of them have been failing, all with a similar error message.
Job: 007
Protocol: cifs
Source: //server1/data/shared
Destination: [BU_Shared]/
cp: cannot stat `/job_007//shared/.': No such file or directory
Backup failed. Tue Mar 25 01:05:09 EDT 2008.
Reason for failure:
Error encountered copying data from remote source path //server1/data/shared ==> /BU_Shared/ due to unknown reason. Please see log.
All the jobs are set up as Windows Timestamp jobs, backing up from locations on my server to NAS shares. Odd thing is, a couple of them work, but most of them fail with the same reason: "no such file or directory". Of course, the directory is there, permissions are ok. When I test the connection to the backup source, it successfully connects using my username and password.
I tried several things (using the IP address to the source, instead of the named path, deleting and recreating the backup job) and couldn't get the jobs to work again.
I finally discovered that if I change the job type on the failing jobs to "Archive Bit" instead of "Timestamp", the job completes successfully.
Any idea why I can't use "Timestamp" on some jobs, but I can on others? I guess it doesn't really matter to me, but I didn't have a problem with certain timestamp jobs failing until I updated the firmware, unless it's all a coincidence. The only other thing I've done on my network is perform a server reboot.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
