03-02-2006
You used the tape that you did a backup with Windows? It probably won't read it on UNIX. Take a new tape, put it in the drive, see if you can send a tar to it.
See
tape not found for more info on setting up a tape drive. Also see
Tapes and tape drives
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Howdy,
I'm trying to tar some directories to tape and then extract them from tape on another machine. I was hoping someone could help me with the syntax of the tar commands. Both machines are running Solaris 8.
Need to get all files and directories under the following:
... (6 Replies)
Discussion started by: pmetal
6 Replies
2. UNIX for Dummies Questions & Answers
Hi guys and gir.. emm
hey guys! (only kidding girls)
I have been asked to provide a tutorial on how to perform an automatic back up (to tape) for 23 sun sparc workstations networked using an ethernet setup under the UNIX operating system.
Sounds easy enough to you... I've never ever seen... (4 Replies)
Discussion started by: maross
4 Replies
3. UNIX for Dummies Questions & Answers
hello,
I don't know what exactly the cause and the solution!!
suddenly I receive this error message when I want to use the 8mm tape drive
"I/O write error"
I disconnect the tape drive and I hook it in another WS and I receive this error :- ... (5 Replies)
Discussion started by: geoquest
5 Replies
4. UNIX for Advanced & Expert Users
I have a hp d 350 running on 10.2,im having a problem with the dds2 tape drive whenever i tried backing up larger files...i have remove the tape driver and add it using sam again but still the tape drive is not working .....is there a solution to this problem?
# tar cvf /dev/rmt/0m priso.ds
a... (3 Replies)
Discussion started by: giriplug
3 Replies
5. Solaris
Hi,
I am a newbie to Solaris, I have a SunFire V120 box, i was trying to install a tape drive(HP SureStore DAT24), i did the install in this manner.
# rm -rf /etc/path_to_inst
# init 6
later at the "ok" prompt i gave "boot -ar" after doing that it asked me various options i accepted the... (2 Replies)
Discussion started by: rajendra.rait
2 Replies
6. Solaris
Well I have just added new tape drive to my server (lto)
However I am getting few errors in using it. I have checked status with
#iostat -En : giving me few hard errors, few soft errors and execution error.
Also tape status is not visible as "no sense" its coming as "no additional sense".
I... (5 Replies)
Discussion started by: saurabh84g
5 Replies
7. AIX
Hi All
I am trying to copy files present in a partition (server 2) which is mounted to a different server (server 1) as tape drive is connected to it. I ran the below command to copy files within a partition:
svr01:root:/sunfileserver> tar -cvf *
a <foldername>/<filename>/<filename>
a... (4 Replies)
Discussion started by: vathsan
4 Replies
8. HP-UX
HP rp5450 (L2000)
running HP-UX 11.11B
Using DLT 7000 and DLT 4000 tape drives for nightly full backups
Backup jobs created by SAM
DLT 7000 cron entry is as follows:
00 2 * * 1-6 /usr/sam/lbin/br_backup DLT FULL Y /dev/rmt/0m /var/sam/graphLCAa17036 root Y 1 N > /var/sam/SAM_br_msgs 2>&1... (1 Reply)
Discussion started by: dreh99
1 Replies
9. Red Hat
Hi Folks,
Looking for some assistance here on a Dell server connected to a Dell tape robot with Redhat 5.4 and Netbackup 6.5.
Netbackup thinks the tapes are all present and working, but they are not - we lost the internal encryption keys earlier but think that they are reinstated as the... (0 Replies)
Discussion started by: gull04
0 Replies
HT(4) Kernel Interfaces Manual HT(4)
NAME
ht - RH-11/TU-16 magtape interface
DESCRIPTION
The files mt0, mt1, ... refer to the DEC RH/TM/TU16 magtape. When opened for reading or writing, the tape is not rewound. When closed,
it is rewound (unless the 0200 bit is on, see below). If the tape was open for writing, a double end-of-file is written. If the tape is
not to be rewound the tape is backspaced to just between the two tapemarks.
A standard tape consists of a series of 512 byte records terminated by a double end-of-file. To the extent possible, the system makes it
possible, if inefficient, to treat the tape like any other file. Seeks have their usual meaning and it is possible to read or write a byte
at a time. Writing in very small units is inadvisable, however, because it tends to create monstrous record gaps.
The last octal digit of the minor device number selects the drive. The middle digit selects a controller. The initial digit is even to
select 800 BPI, odd to select 1600 BPI. If the 0200 bit is on (initial digit 2 or 3), the tape is not rewound on close. Note that the
minor device number has no necessary connection with the file name, and in fact tp(1) turns the short name x into `/dev/mtx'.
The mt files discussed above are useful when it is desired to access the tape in a way compatible with ordinary files. When foreign tapes
are to be dealt with, and especially when long records are to be read or written, the `raw' interface is appropriate. The associated files
may be named rmt0, ..., rmt7, but the same minor-device considerations as for the regular files still apply.
Each read or write call reads or writes the next record on the tape. In the write case the record has the same length as the buffer given.
During a read, the record size is passed back as the number of bytes read, provided it is no greater than the buffer size; if the record is
long, an error is indicated. In raw tape I/O, the buffer must begin on a word boundary and the count must be even. Seeks are ignored. A
zero count is returned when a tape mark is read; another read will fetch the first record of the next tape file.
FILES
/dev/mt?, /dev/rmt?
SEE ALSO
tp(1)
BUGS
The magtape system is supposed to be able to take 64 drives. Such addressing has never been tried.
Taking a drive off line, or running off the end of tape, while writing have been known to hang the system.
If any non-data error is encountered, it refuses to do anything more until closed. In raw I/O, there should be a way to perform forward
and backward record and file spacing and to write an EOF mark explicitly.
HT(4)