Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Westi on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Formatting a Tape 3
- Thread starter dschmootz
- Start date
-
1
- #2
- Thread starter
- #3
- Thread starter
- #4
BeasterBob,
Actually, I tried "tape_unit" and it said the was no such device name. I tried "show device" and it listed many devices. There was an "mka100", but when I tried to use that, there was a "fatal drive" error. I tried to allocate a couple of the many other devices, but received the error "no file structure". Any thoughts....? Thanks.
Actually, I tried "tape_unit" and it said the was no such device name. I tried "show device" and it listed many devices. There was an "mka100", but when I tried to use that, there was a "fatal drive" error. I tried to allocate a couple of the many other devices, but received the error "no file structure". Any thoughts....? Thanks.
-
1
- #5
I'm confused. You're attached the TZ87 to your NT system?
MKA100: shoulds reasonable. I recall the at TZ30 is a type of tape not a drive so, I wonder if the TZ87 is a tape type...not a drive type?
Our tape drive is connected to MKB500: (not MKA500
. The A versus the B has to do with which SCSI chain you are using. I also believe the 500 has to do with the SCSI ID of the device (ID=5).
Assuming you're using VMS, you might want to check into some of the other parameters such as "foreign".
mike
MKA100: shoulds reasonable. I recall the at TZ30 is a type of tape not a drive so, I wonder if the TZ87 is a tape type...not a drive type?
Our tape drive is connected to MKB500: (not MKA500
. The A versus the B has to do with which SCSI chain you are using. I also believe the 500 has to do with the SCSI ID of the device (ID=5).Assuming you're using VMS, you might want to check into some of the other parameters such as "foreign".
mike
- Thread starter
- #6
Mike,
Thanks for your reply. The tape drive says that it's a Digital TZ87 and it's attached to the open VMS. How do I check "foreign" parameter? How do I figure out which device is the tape drive? Sorry, but I'm VERY new to this open VMS and I know very few things about it, but I have been studying.
Thanks for your reply. The tape drive says that it's a Digital TZ87 and it's attached to the open VMS. How do I check "foreign" parameter? How do I figure out which device is the tape drive? Sorry, but I'm VERY new to this open VMS and I know very few things about it, but I have been studying.
-
1
- #7
HughSamson
IS-IT--Management
- Feb 25, 2002
- 31
"TZ87" indicates the model of the tape unit, what sort of tapes the unit is compatible with, and the compression capability of the unit (eg TZ87 will compress to a greater density using the correct tapes(!) than a TZ85 unit... we're up to TZ89 last I heard - 40GB normal, 80GB compressed?). This should take up to a "DLT IV" type tape.
To init the tape, as per the first reply, enter
>> INIT/MEDIA=COMPAC MKA100: dummy
(where ">>" is your DCL prompt, and "dummy" is whatever you want to label the tape - remembering that you only have six chars for the label!) Lookup the "HELP INIT" command for more details...
The "IN USE" and "COMPRESSED" lights should be lit on the unit (I assume it is a desktop tape unit?) when the tape has been loaded and initialised withthe /media=compac qualifier...
The "/foreign" command is how the tape must be mounted to perform a backup or restore... in other words, it's not mounted files-11 (as are disks). This can also be used to read/write files that are not in native VMS file format - e.g. reading an IBM tape.
An example of performing a full image backup of your system disk to tape:
>> init/media=compac mka100: dummy
>> mount/foreign mka100:
>> backup/image/log/ignore=(interlock,nobackup,label) -
sys$sysdevice: -
mka100:bootdisk.bck/sav -
/rewind/media=compac
... backup copy messages are displayed...
>> DISMOUNT/nounload mka100:
The above would put the tape drive into it's higher possible compaction ratio (which saves tape space and can decreares the backup time)
Cheers,
Hugh.
![[shadeshappy]](/data/assets/smilies/shadeshappy.gif "[shadeshappy] [shadeshappy]")
To init the tape, as per the first reply, enter
>> INIT/MEDIA=COMPAC MKA100: dummy
(where ">>" is your DCL prompt, and "dummy" is whatever you want to label the tape - remembering that you only have six chars for the label!) Lookup the "HELP INIT" command for more details...
The "IN USE" and "COMPRESSED" lights should be lit on the unit (I assume it is a desktop tape unit?) when the tape has been loaded and initialised withthe /media=compac qualifier...
The "/foreign" command is how the tape must be mounted to perform a backup or restore... in other words, it's not mounted files-11 (as are disks). This can also be used to read/write files that are not in native VMS file format - e.g. reading an IBM tape.
An example of performing a full image backup of your system disk to tape:
>> init/media=compac mka100: dummy
>> mount/foreign mka100:
>> backup/image/log/ignore=(interlock,nobackup,label) -
sys$sysdevice: -
mka100:bootdisk.bck/sav -
/rewind/media=compac
... backup copy messages are displayed...
>> DISMOUNT/nounload mka100:
The above would put the tape drive into it's higher possible compaction ratio (which saves tape space and can decreares the backup time)
Cheers,
Hugh.
- Thread starter
- #8
Hugh,
Thanks VERY much. That worked perfectly with an old tape. When I used a brand new DLT III tape and did the following:
init/media=compac mka100: jimnew
it showed "fatal drive error". I went ahead and mounted it and followed the rest of your notes. It then said I used a "non-ANSI label" and it renamed it to "BOOTDI", then it started copying files. Will this be ok....and should I have done it differently with a new tape? Have a good weekend!
Thanks VERY much. That worked perfectly with an old tape. When I used a brand new DLT III tape and did the following:
init/media=compac mka100: jimnew
it showed "fatal drive error". I went ahead and mounted it and followed the rest of your notes. It then said I used a "non-ANSI label" and it renamed it to "BOOTDI", then it started copying files. Will this be ok....and should I have done it differently with a new tape? Have a good weekend!
HughSamson
IS-IT--Management
- Feb 25, 2002
- 31
The fatal drive error is probably indicating it can't use that particular type of tape (maybe I gave you a bum steer with the DLT IV - it may only use DLT III tapes...) sorry!
Anyways, if a tape is not labelled (or you put the /REWIND qualifier on as I did above), the backup program will initialise the tape to the first five chars of the saveset name you have specified, and append a "1" as the sixth character - this indicates it's the first tape in a set where more than one tape is used. If it had spanned to a second tape, it would have labelled it "BOOTD2"...
As long as you had no other errors, your backup should be OK.
If you want to be positive that the backup has written to tape OK, you can add the qualifier "/VERIFY" to the backup command above - the backup will write to tape, then rewind the tape, and re-read the disk, and compare the contents to what it has written to tape - be aware this will take twice as long to do!
B-)
Hugh
Anyways, if a tape is not labelled (or you put the /REWIND qualifier on as I did above), the backup program will initialise the tape to the first five chars of the saveset name you have specified, and append a "1" as the sixth character - this indicates it's the first tape in a set where more than one tape is used. If it had spanned to a second tape, it would have labelled it "BOOTD2"...
As long as you had no other errors, your backup should be OK.
If you want to be positive that the backup has written to tape OK, you can add the qualifier "/VERIFY" to the backup command above - the backup will write to tape, then rewind the tape, and re-read the disk, and compare the contents to what it has written to tape - be aware this will take twice as long to do!
B-)
Hugh
- Thread starter
- #10
- Status
Similar threads
- Question
- Locked
- Question
- Locked
- Question