03-03-2006
It should be able to overwrite the tape - my concern was that you did a backup on windows, then brought the tape to UNIX and attempted to read it which may not work and make you think it's the tape drive versus format of the tape.
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 - TM-03/TE-16,TU-45,TU-77 MASSBUS magtape interface
SYNOPSIS
/sys/conf/SYSTEM:
NHT ht_drives # TE16, TU45, TU77
/etc/dtab:
#Name Unit# Addr Vector Br Handler(s) # Comments
ht ? 172440 224 5 htintr # tu 16 massbus tape
major device number(s):
raw: 6
block: 0
minor device encoding:
bits 0003 specify HT drive
bit 0004 specifies no-rewind operation
bit 0010 specifies 1600BPI recording density instead of 800BPI
DESCRIPTION
The tm-03/transport combination provides a standard tape drive interface as described in mtio(4). All drives provide both 800 and 1600
bpi; the TE-16 runs at 45 ips, the TU-45 at 75 ips, while the TU-77 runs at 125 ips and autoloads tapes.
FILES
/dev/MAKEDEV script to create special files
/dev/MAKEDEV.local script to localize special files
SEE ALSO
mt(1), tar(1), tp(1), mtio(4), tm(4), ts(4), dtab(5), autoconfig(8)
DIAGNOSTICS
tu%d: no write ring. An attempt was made to write on the tape drive when no write ring was present; this message is written on the termi-
nal of the user who tried to access the tape.
tu%d: not online. An attempt was made to access the tape while it was offline; this message is written on the terminal of the user who
tried to access the tape.
tu%d: can't change density in mid-tape. An attempt was made to write on a tape at a different density than is already recorded on the
tape. This message is written on the terminal of the user who tried to switch the density.
tu%d: hard error bn%d er=%b ds=%b. A tape error occurred at block bn; the ht error register and drive status register are printed in
octal with the bits symbolically decoded. Any error is fatal on non-raw tape; when possible the driver will have retried the operation
which failed several times before reporting the error.
BUGS
If any non-data error is encountered on non-raw tape, it refuses to do anything more until closed.
The system should remember which controlling terminal has the tape drive open and write error messages to that terminal rather than on the
console.
3rd Berkeley Distribution January 28, 1988 HT(4)