N
nick
Hi, I'm trying to restore files from a tape using Ntbackup on XP SP1.
Ntbackup terminates in the middle of the restore process saying "Bad data".
Using a SCSI spy tool, I found that the tape drive reports a bad block
(ScsiSence=MEDIUM ERROR 0x3, AdSense=READ ERROR 0xB, SenseQ=0x0). Ntbackup
immediately terminates without an attempt to read the rest of the data.
There are thousands small files on the tape before and after the bad block,
so selective restore is an an option.
Isn't there any fault-tolerance logic in Ntbackup?! A bad block is a quite
common think on tapes, and making a whole backup unavailable just because of
a single bad block is far from good. Is it possible to set some registry
value or pass a command line option to force Ntbackup to read past a bad
block ignoring bad files and restoring good ones?
Thanks.
Ntbackup terminates in the middle of the restore process saying "Bad data".
Using a SCSI spy tool, I found that the tape drive reports a bad block
(ScsiSence=MEDIUM ERROR 0x3, AdSense=READ ERROR 0xB, SenseQ=0x0). Ntbackup
immediately terminates without an attempt to read the rest of the data.
There are thousands small files on the tape before and after the bad block,
so selective restore is an an option.
Isn't there any fault-tolerance logic in Ntbackup?! A bad block is a quite
common think on tapes, and making a whole backup unavailable just because of
a single bad block is far from good. Is it possible to set some registry
value or pass a command line option to force Ntbackup to read past a bad
block ignoring bad files and restoring good ones?
Thanks.