All,
I'm running amverify on a full (about 10Gb compressed from three servers)
backup from this past weekend. as you can see its been running for about 24
hours. My concern is the tape errors I'm not exactly sure what they mean.
The device is DLT 4000
THIS IS THE REPORT FILE THUS FAR.
amverify FULL
Mon Jun 4 10:26:36 EDT 2001
Using device /dev/rmt/DLTlbn
Volume AM-FULL.05, Date 20010603
Checked sparc20._var.20010603.0
Checked sparc10._opt.20010603.0
Checked ultra._var.20010603.0
Checked sparc10._usr4.20010603.0
Checked ultra._.20010603.0
Checked sparc10._.20010603.0
Checked sparc20._.20010603.0
Checked sparc10._var.20010603.0
Checked ultra._usr.20010603.0
Checked sparc20._usr.20010603.0
Checked sparc10._usr.20010603.0
Checked ultra._usr2.20010603.0
Checked sparc20._usr8.20010603.0
Checked sparc20._usr7.20010603.0
Checked sparc10._usr3.20010603.0
** Error detected ()
amrestore: could not open tape /dev/rmt/DLTlbn: Device busy
** No header
0+0 records in
0+0 records out
** Error detected ()
amrestore: could not open tape /dev/rmt/DLTlbn: Device busy
** No header
0+0 records in
0+0 records out
** Error detected ()
amrestore: could not open tape /dev/rmt/DLTlbn: Device busy
** No header
0+0 records in
0+0 records out
Checked sparc20._usr6.20010603.0
Checked sparc10._usr2.20010603.0
Checked sparc20._usr9.20010603.0
TIA.
____________________________________________
Richard Sean Jaehne
ATT Technical Services Company
Unix Systems Administrator
NT Network Administrator
IRM/OPS/ITI/TWD/BOM
Tel.: 202-663-3375
Fax: 202-663-3481
All information contained in this email is Unclassified
