C
Cameron Dorrough
Hi all!! We recently started getting the following error on our nightly
Tape backups (separate server) and I have run out of things to check:
File \Projects\04000\04001\Acad\PDF\101312E3.pdf is corrupted.
This file cannot be verified.
Network disk drive has stopped responding. Backup set aborted.
Backup completed on 17/09/04 at 23:20:01.
Backed up 1945 files in 252 directories.
One corrupted file was backed up.
The Tape drive happily backs up all other machines on our network, so it
must be something to do with this server (W2kAS SP4). The problem happens
on all shared drives on this machine, so it doesn't seem to be a HDD
problem... but I've chkdsk'd and defragged all the drives anyway (no major
problems reported) and virus checked it as well (no problems reported).
The "corrupt" file is *not* corupt and can be opened fine. The file name
seems to change each time I do the backup... There are no errors in the
event logs on either machine, and the shared drive can be viewed fine in
Windows Explorer immediately following the failure.
Has anyone seen this before and know of a fix??
Thanks,
Cameron
Tape backups (separate server) and I have run out of things to check:
File \Projects\04000\04001\Acad\PDF\101312E3.pdf is corrupted.
This file cannot be verified.
Network disk drive has stopped responding. Backup set aborted.
Backup completed on 17/09/04 at 23:20:01.
Backed up 1945 files in 252 directories.
One corrupted file was backed up.
The Tape drive happily backs up all other machines on our network, so it
must be something to do with this server (W2kAS SP4). The problem happens
on all shared drives on this machine, so it doesn't seem to be a HDD
problem... but I've chkdsk'd and defragged all the drives anyway (no major
problems reported) and virus checked it as well (no problems reported).
The "corrupt" file is *not* corupt and can be opened fine. The file name
seems to change each time I do the backup... There are no errors in the
event logs on either machine, and the shared drive can be viewed fine in
Windows Explorer immediately following the failure.
Has anyone seen this before and know of a fix??
Thanks,
Cameron