Hi all,
This weekend, with my job on the line, I had some MAJOR difficulty
restoring from tape. The nightly routine does a full backup each
weeknight ( we are closed after 5 and current total Disk usage is only
30Gb's or so). the command used for example is.
vdump -0NUu /vol3 ( only have one tape drive )
This process is written out to a log file. Except for one instance of a
bad tape, I've never seen an error. Now I have had to restore single
files, and occasionally a small group of file but never an entire
directory. So of course, the first time I need to recover, I get error
messages. Here was the process:
# mt rewind
# mt fsf 3
# vrestore -x ./oradata/fsys ( I was restoring to a temporary location )
eventually the above erred out with a I/O [5], cannot read from device.
also tried the interactive method
# vrestore -i
vrestore: Date of the vdump save-set: Sat Jan 16 03:11:42 1999
(/) cd oradata
(/oradata/) add fsys
(/) restore
and this just sits there forever, no error, no response
Now I was in big trouble at this point and I was trying everything.
Here is where things got really weird. I was able to restore the files
within the directory fsys, but not the entire directory. Here was the
process.
vrestore -i
vrestore: Date of the vdump save-set: Sat Jan 16 03:11:42 1999
(/) cd oradata
(/oradata/) cd fsys
(/oradata/fsys/) add filename
Now while it was "not responding" I opened another session and did a
continuos ls -l of filename until it showed up at it's known size.
I then killed off the vrestore job and started over. Thankfully there
were only 47 files to restore as this took quite a while.
So my question is has anyone seen a problem like this? FYI I'm using DU
4.0D patch 2. Any thoughts you all might have before I have tech
support come in and test the device?
Received on Mon Jan 18 1999 - 14:34:38 NZDT