Hmmm, ARG b is specifying a blocksize of 1 KB, it looks to me as though you should specify 63. I presume that you know what you are doing with ARG s (File 33 of n on the tape). #ifdef PARANOID_MODE Also, unless you are planning to write on the tape, it should be write protected, just to protect against fumble fingers or other errors. #endif /*PARANOID_MODE*/ <scw>
I'm trying to do a restore from tapes where the netbackup images have expired. (I did a "phase1 import" which reads image headers, so I know which files I'd like off the tape; "phase 2 import" which reads files and rebuilds netbackup database info is failing -- this may be a separate issue.) The correct tape is loaded in the dlt. I'm seeing "RESTORE: Could not initialize media."
inbox1> mt -f nrst0a rewind inbox1> mt -f nrst0a status Tape drive: Digital DLT7000 Status: ready, write enabled Format: 85937 bpi 70 GB (w/comp) fileno = 0 blockno = 0 resid = 0 inbox1> mt -f nrst0a rewind inbox1> restore tvf nrst0a b 1 s 33 RESTORE: Tape Block size should be 1024, not 64512. RESTORE: Could not initialize media. inbox1> mt -f nrst0a rewind inbox1> restore tvf nrst0a s33 RESTORE: Tape Block size should be 1024, not 64512. RESTORE: Could not initialize media. inbox1> mt -f nrst0a status Tape drive: Digital DLT7000 Status: ready, write enabled Format: 85937 bpi 70 GB (w/comp) fileno = 0 blockno = 1 resid = 31744 inbox1>
Any ideas or suggestions?Dave Toal Thomson & Thomson
----- Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Finger for public key scw@cirrus.seas.ucla.edu,Internet mail:scw@SEAS.UCLA.EDU
Here's a brief explanation, incorporating all that I know about everything in the world.
1) inbox1> restore tvf nrst0a b 1 s 33 RESTORE: Tape Block size should be 1024, not 64512.
I think restore just wants you to format your line differently:
inbox1> restore tvfbs nrst0a 1 33
If your intention is to: Run a table-of-contents restore on the 33rd tape file on the physical tape, where the data was dumped with a 1KB tape record, this will work.
That being said, I don't think this is quite the right thing. As I understand it, though, NetBackup writes some tape file at the beginning of a dump (I can't remember how many) with the small tape record sizes, and then the dump proceeds with the 63KB tape record size.
So I can imagine what happened: 1) You ran: nbox1> restore tvf nrst0a s 33 because you know you want tape file 33.
Then restore told you: RESTORE: Tape Block size should be 1024, not 64512.
And we got to where you are today.
However, since the "s 33" option was in a place where restore didn't understand, the 1KB referred to the first file on the tape.
So, I'll bet you want to try: inbox1> restore tvfs nrst0a 33
And see what that gives you...
Stephen Manley File System Recovery Imagineer
I'm trying to do a restore from tapes where the netbackup images have expired. (I did a "phase1 import" which reads image headers, so I know which files I'd like off the tape; "phase 2 import" which reads files and rebuilds netbackup database info is failing -- this may be a separate issue.) The correct tape is loaded in the dlt. I'm seeing "RESTORE: Could not initialize media."
inbox1> mt -f nrst0a rewind inbox1> mt -f nrst0a status Tape drive: Digital DLT7000 Status: ready, write enabled Format: 85937 bpi 70 GB (w/comp) fileno = 0 blockno = 0 resid = 0 inbox1> mt -f nrst0a rewind inbox1> restore tvf nrst0a b 1 s 33 RESTORE: Tape Block size should be 1024, not 64512. RESTORE: Could not initialize media. inbox1> mt -f nrst0a rewind inbox1> restore tvf nrst0a s33 RESTORE: Tape Block size should be 1024, not 64512. RESTORE: Could not initialize media. inbox1> mt -f nrst0a status Tape drive: Digital DLT7000 Status: ready, write enabled Format: 85937 bpi 70 GB (w/comp) fileno = 0 blockno = 1 resid = 31744 inbox1>
Any ideas or suggestions?Dave Toal Thomson & Thomson
Stephen C. Woods; UCLA SEASnet; 2567 Boelter hall; LA CA 90095; (310)-825-8614 Finger for public key scw@cirrus.seas.ucla.edu,Internet mail:scw@SEAS.UCLA.EDU
-
Stephen C Woods -
stephen＠netapp.com