I'm having a problem that has gone from occasional to constant: my differential backups to my Buffalo NAS are aborting after a couple of hours with the following error in the log:
[1/4/2011 10:35:31 AM] Error: Backup aborted. Reason:
Cannot add file "C:\Users\Carl\Videos\X\projects\sample.wav" to "\\LINKSTATION\Backups\Carl and Xtras\11_C.zip".
Zip error: Cannot write file "\\LINKSTATION\Backups\Carl and Xtras\11_C.z11"
The handle is invalid (While writing compressed file in zip)
Backup aborted at 1/4/2011 10:35:31 AM with 1 error(s), 0 warning(s)
The error will show show up on different files, but each file always seems to be within the source "videos" folder (this time it aborted on a wav file, which is not particularly large).
I received a suggestion from the Help desk that I set my preferences to allow files to be split above 2GB, but this made no difference.
I'm also puzzled by the fact that documentation on this site indicates that, rather than an UNC path, it's possible to type in a drive mapping for your backup destination (e.g., X:\backups). This seems to be completely impossible...I can't even type a colon after the drive letter in the UNC field. I wanted to try using a network drive mapping because I read somewhere online that it works instead of UNC paths when experiencing file handle errors, but I can't get Backup4All to register that kind of path when the destination is designated as "network" for the backup job.
So at this point, I don't know if I have an application issue, or a NAS issue. Any ideas?