I've got a server that runs a full ntbackup once a week. Every week, it will log about a dozen files with the following messages:
WARNING: Portions of "\OBJECTS\SERVER\STORAGE\DOCS101\SomeFile.000" cannot be read. The backed up data is corrupt or incomplete.
This file will not restore correctly.
Warning: Unable to open "E:\OBJECTS\SERVER\STORAGE\DOCS101\SomeFile.001" - skipped.
Reason: The system cannot find the file specified.
Warning: Unable to open "E:\OBJECTS\SERVER\STORAGE\DOCS101\SomeFile.002" - skipped.
Reason: The system cannot find the file specified.
...
Warning: Unable to open "E:\OBJECTS\SERVER\STORAGE\DOCS101\SomeFile.012" - skipped.
Reason: The system cannot find the file specified.
Could not access portions of directory E:\OBJECTS\SERVER\STORAGE\DOCS101.
You may not have permission to open the file, or the directory may be missing or damaged.
Please contact the owner or administrator.
The thing is, it's never the same files. It's always a different, seemingly entirely random group of consecutive files. And it's not new files either. I've seen documents that are from as far back as 2006 show up on this list. I've checked, and all of the files are in the paths shown in the log file, and I am able to view them without problems. Any idea why this would be happening?
EDIT: This has been an ongoing problem for almost three years now, and I'm totally stumped.
Something else has those files locked. Do you have antivirus scan or is something indexing the file system (locally or over a share)? I assume chkdsk comes up clean?
The error is misleading, something has the files open. Try this right before the backup kicks off.
(handle.exe is a tool from sysinternals which you can download for here).
opensharedfiles.txt will show you is someone still has a file open remotely, handleList.txt will show you all handles on the machine, allowing you to locate which local process might have it open.
Shamelessly stolen from Fulgan@Arstechnica