Problems with DLT7000 and SDLT


 
Thread Tools Search this Thread
Top Forums UNIX for Advanced & Expert Users Problems with DLT7000 and SDLT
# 1  
Old 02-20-2004
Problems with DLT7000 and SDLT

Hi,

I think this issue should be posted in a backup box, but there wasn't .


We have an issue that we made a backup on a DLT7000 tape using tar. Ones we check using : tar tvf /dev/rmt/0
It all works great on the same server.

Now ejecting the tape and putting it into server 2 with an SDLT unit we try to do the same but get an error. However mt stat -f /dev/rmt/0 shows :

Quantum Super DLT 320 tape drive:
sense key(0x6)= Unit Attention residual= 0 retries= 0
file no= 0 block no= 0


The DLT7000 would be read only compatible to the SDLT, right?

I know it's (by default) not the other way arround and you can't append, but is there something else we should look at ?


Best Regs David
Login or Register to Ask a Question

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

If/then problems

#! /bin/bash # ask what the user would like to do CMD=$CMD MBA=$MB RS=$RS CT=$CT echo echo -n "What would you like to do?? REMEMBER WHEN PROGRAMMING ICP's TO SELECT CORRECT COMMAND ACCORDING TO NECCESSARY TYPE CODE! Please enter a command ct = program ctek ... (5 Replies)
Discussion started by: tdalyman
5 Replies

2. Shell Programming and Scripting

while and do problems

Any ideas how to clear this error as it seems I dont understand if,do,while and els commands #!/bin/ksh set -x print "This script creates test messages" print "Please enter test case name" read testcasename echo $testcasename skipfield=Y while print "Do you want to skip this field... (4 Replies)
Discussion started by: andrew.p.mcderm
4 Replies

3. Shell Programming and Scripting

Problems with $?

Hello, I have the following piece of code that tries to retrieve the result of a .sh: . $HOME/prueba/Scripts/Recogida/recogida_sedra.sh resultado=$? echo "el resultado es : $resultado" if ; then echo "Se va a preprocesar los archivos" In the code of recogida.sh I have the... (8 Replies)
Discussion started by: danietepa
8 Replies

4. UNIX for Dummies Questions & Answers

Problems with using less

Hello, I am having problems with using less on Linux version 2.6.18-92.1.17.el5 (brewbuilder@hs20-bc1-7.build.redhat.com) (gcc version 4.1.2 20071124 (Red Hat 4.1.2-42)). I am using csh but have the same problems on bash. If I pipe something to less it works perfectly i.e. cat file | less... (9 Replies)
Discussion started by: z1dane
9 Replies

5. UNIX for Advanced & Expert Users

Get files from sdlt tapes

Hi everybody, I'm new using unix/linux and I have a sdlt tape wich has 2 segy files. I realise the tape isn't tar so when I use dd if=/dev/rmt/*bn of=filename bs=100000 to get the files after 10 Gb for file 1 an error message appear I/O error and I'm sure that I didn't get completly the first... (5 Replies)
Discussion started by: Titas
5 Replies

6. UNIX for Advanced & Expert Users

Problems with Last

Hi, I,ve a Unixware 7.1.3 working correctly for two years ago, since a several weeks I've a problem with the command last . The information that this command return is : For example : 1.- The user root , time login : 12:15 h, time logoff 12:15 h (the real time is 14:00). Connected time is... (3 Replies)
Discussion started by: By_Jam
3 Replies

7. HP-UX

SDLT Drivers

Greetings I looking for the drivers for an sdlt tape drive for hp-ux 11.0. I think the drivers i need are stape and tape2 does anyone know where i can get them Thanks Alan (2 Replies)
Discussion started by: Flipper_Al
2 Replies

8. Solaris

regd tanberg sdlt and sunfire v 880

Hii alll Thanks for the support, iam facing a problem regarding tanberg sdlt . iam trying to connect tanberg sdlt 160 to sun fire 880 r .As SUN FIRE DOSENT HAVE SCSI CONTROLLER IAM CONNECTING A ULTRA 2 SCSI CONTROLLER IN PCI SLOT AND FROM THERE IAM CONNECTING THE TANBERG SDLT 160. MY FIRST... (1 Reply)
Discussion started by: solaris8in
1 Replies

9. UNIX for Advanced & Expert Users

'make' problems (compliation problems?)

I'm trying to compile and install both most recent version of 'make' and the most recent version of 'openssh' on my Sparc20. I've run into the following problems... and I don't know what they mean. Can someone please help me resolve these issues? I'm using the 'make' version that was... (5 Replies)
Discussion started by: xyyz
5 Replies
Login or Register to Ask a Question
AMRESTORE(8)						      System Manager's Manual						      AMRESTORE(8)

NAME
amrestore - extract backup images from an Amanda tape SYNOPSIS
amrestore [ -r | -c | -C ] [ -b blocksize ] [ -p ] [ -h ] tapedevice | holdingfile [ hostname [ diskname [ datestamp [ hostname [ diskname [ datestamp ... ]]]]]] DESCRIPTION
Amrestore extracts backup images from the tape mounted on tapedevice or from the holding disk file holdingfile that match hostname, diskname and datestamp patterns given on the command line. The tape or holding file must be in a format written by the amdump or amflush program. If diskname is not specified, all backups on the tape for the previous hostname are candidates. If datestamp is not specified, all backups on the tape for the previous hostname and diskname are candidates. If no hostname, diskname or datestamp are specified, every backup on the tape is a candidate. Hostname and diskname are special expression descibe in the "HOST & DISK EXPRESSION" section of amanda(8). Datestamp are special expres- sion describe in the "DATESTAMP EXPRESSION" section of amanda(8). For example, if diskname is "rz[23]a", it would match disks rz2a and rz3a. Datestamp is useful if amflush writes multiple backup runs to a single tape. Unless -p is used, candidate backup images are extracted to files in the current directory named: hostname.diskname.datestamp.dumplevel OPTIONS
-b Set the blocksize used to read the tape or holding file. All holding files must be read with a blocksize of 32 KBytes. Amrestore should normally be able to determine the blocksize for tapes on its own and not need this parameter. The default is 32 KBytes. -p Pipe output. The first matching backup image is sent to standard output, which is normally a pipe to restore or tar, then amrestore quits. It may be run again to continue selecting backups to process. Make sure you specify the no-rewind tapedevice when doing this. Note: restore may report "short read" errors when reading from a pipe. Most versions of restore support a blocking factor option to let you set the read block size, and you should set it to 2. See the example below. -c Compress output using the fastest method the compression program provides. Amrestore normally writes output files in a format understood by restore or tar, even if the backups on the tape are compressed. With the -c or -C option, amrestore writes all files in compressed format, even if the backups on the tape are not compressed. Output file names will have a .Z or .gz extension depend- ing on whether compress or gzip is the preferred compression program. This option is useful when the current directory disk is small. -C Compress output using the best method the compression program provides (may be very CPU intensive). See the notes above about the -c option. -r Raw output. Backup images are output exactly as they are on the tape, including the amdump headers. Output file names will have a .RAW extension. This option is only useful for debugging and other strange circumstances. -h Header output. The tape header block is output at the beginning of each file. This is like -r except -c or -C may also be used to compress the result. Amrecover uses the header to determine the restore program to use. If a header is written (-r or -h), only 32 KBytes are output regardless of the tape blocksize. This makes the resulting image usable as a holding file. EXAMPLES
The following does an interactive restore of disk rz3g from host seine, to restore particular files. Note the use of the b option to restore, which causes it to read in units of two 512-byte blocks (1 Kbyte) at a time. This helps keep it from complaining about short reads. % amrestore -p /dev/nrmt9 seine rz3g | restore -ivbf 2 - The next example extracts all backup images for host seine. This is the usual way to extract all data for a host after a disk crash. % amrestore /dev/nrmt9 seine If the backup datestamp in the above example is 19910125 and seine has level 0 backups of disks rz1a and rz1g on the tape, these files will be created in the current directory: seine.rz1a.19910125.0 seine.rz1g.19910125.0 You may also use amrestore to extract a backup image from a holding disk file that has not yet been flushed to tape: % amrestore -p /amanda/20001119/seine.rz1a.2 | restore -ivbf 2 - Amrestore may be used to generate a listing of images on a tape: % mt -f /dev/nrmt9 rewind % amrestore -p /dev/nrmt9 no-such-host > /dev/null This asks amrestore to find images for host no-such-host. It will not find any entries that match, but along the way will report each image it skips. CAVEATS
GNU tar must be used to restore files from backup images created with the GNUTAR dumptype. Vendor tar programs sometimes fail to read GNU tar images. AUTHOR
James da Silva <jds@cs.umd.edu> University of Maryland, College Park SEE ALSO
amanda(8), amdump(8), amflush(8), tar(1) restore(8) AMRESTORE(8)