SEO

I have a Sun L9 autoloader with DLT-8000 drive in it, and have finally
got a real (not Sun I would add) HVD SCSI card. You may recall my
earlier problems when the card I bought was SE, not HVD as I was led
to belive.

The HVD SCSI card is now reconsised at the OBP, along with the tape
drive and the library on bus 6, devices 0 and 1. After a boot -r,
cdrecord -scanbus can see the devices on the SCSI bus, so I assume
that I'm at least 50% of the way to getting this working.

However, much to my surprise, there is no /dev/rmt/1* files. I
expected these, as my previous tape drive (DDS-4) produced the
/dev/rmt/0* files.

What is the quickest way to determine if the DLT-8000 is functional or
not? I'm not bothered about the autochanger faciltiies, barcodes etc
for now - I just want to verify the tape drive is working, preferably
without installing a lot of other software. I don't care about
performance issues for now.

This is a home machine, so I can't afford Veritas. I know there are
open-source solutions, but for now I just want to check the bare
minimum of functionality. I know this device has been connected to SE
SCSI cards on at least two occasions, so I'm not sure of its
condition. It is however seen on the SCSI bus, which must be a good
sign.

I got the autoloader for nothing, as it was unused in a company. I
don't know why it was unused - perhaps since it does not work. Hence
I'm looking for a quick and dirty solution to check its functionality
with ufsdump or tar.

Dr. David Kirkby

In article <c99d2c79.0405060030.1f5542c3@posting.google.com >,
see_my_signature_for_my_real_address@hotmail.com (Dr. David Kirkby)
wrote:

> I have a Sun L9 autoloader with DLT-8000 drive in it, and have finally
> got a real (not Sun I would add) HVD SCSI card. You may recall my
> earlier problems when the card I bought was SE, not HVD as I was led
> to belive.
>
> The HVD SCSI card is now reconsised at the OBP, along with the tape
> drive and the library on bus 6, devices 0 and 1. After a boot -r,
> cdrecord -scanbus can see the devices on the SCSI bus, so I assume
> that I'm at least 50% of the way to getting this working.
>
> However, much to my surprise, there is no /dev/rmt/1* files. I
> expected these, as my previous tape drive (DDS-4) produced the
> /dev/rmt/0* files.
>
> What is the quickest way to determine if the DLT-8000 is functional or
> not? I'm not bothered about the autochanger faciltiies, barcodes etc
> for now - I just want to verify the tape drive is working, preferably
> without installing a lot of other software. I don't care about
> performance issues for now.
>
> This is a home machine, so I can't afford Veritas. I know there are
> open-source solutions, but for now I just want to check the bare
> minimum of functionality. I know this device has been connected to SE
> SCSI cards on at least two occasions, so I'm not sure of its
> condition. It is however seen on the SCSI bus, which must be a good
> sign.
>
> I got the autoloader for nothing, as it was unused in a company. I
> don't know why it was unused - perhaps since it does not work. Hence
> I'm looking for a quick and dirty solution to check its functionality
> with ufsdump or tar.
>
> Dr. David Kirkby

You rebooted with

boot -r

right?

That will recreate the /dev and /devices files (there are other ways of
doing this, but this seems like it would be easiest for you).

Once the device files are setup, you should be able to put a DLT tape in
the drive and use ufsdump to the device file. Use the "u" device to get
the maximum compression:

ufsdump 0f /dev/rmt/0u

DO NOT use tar to backup your system. That's not it's job. It's a tape
ARCHIVER, not a filesystem dump utility. ufsdump/ufsrestore should do
you for now. Read the man pages on them. When you're ready, you can
use amanda (http://www.amanda.org) to automate your backups and run your
jukebox:

http://ptolemy.eecs.berkeley.edu/~cxh/sapub/juke.html

http://mtx.badtux.net/

http://www.epcc.ed.ac.uk/~spb/stctl/

B.U.R.T. (Backup and Recovery Tool),
http://www.cs.wisc.edu/~jmelski/burt/
Nice Tcl/tk front-end. Uses its own back-end engine.

Linux Backup (GTK-based),
http://www.linsupport.com/sw/linuxbackup.html

http://sunsite.dk/qweb/kdat/ Nice Qt/X11 front-end to tar.

Tob (Tape Oriented Backup). No longer maintained. Final version is
mirrored at http://linuxmafia.com/pub/linux/utilities-general/ Front-end
to tar or afio.

afbackup, Albert Flugel's Backup,
http://sourceforge.net/projects/afbackup/ Client/server backup
management system & engine. Can use mtx or stctl to control tape
changers.

hostdump.sh, http://www.backupcentral.com/hostdump.html Sophisticated
shell script. Will use dump, cpio, or tar, in that order of preference.

Kbackup, http://kbackup.sourceforge.net/ ncurses-driven (or
command-line) front-end to afio or tar.

Datbkr, http://www.psychosis.com/datbkr/ Fast, light script front-end
for tar.

star, ftp://ftp.fokus.gmd.de/pub/unix/star/ Highly optimised version of
tar. (Double-buffered FIFO streaming, does sophisticated diffs.)

Good informational site: http://www.backupcentral.com/

--
DeeDee, don't press that button! DeeDee! NO! Dee...

"Dr. David Kirkby" <see_my_signature_for_my_real_address@hotmail.co m>
schreef in bericht news:c99d2c79.0405060030.1f5542c3@posting.google.c om...
> I have a Sun L9 autoloader with DLT-8000 drive in it, and have finally
> got a real (not Sun I would add) HVD SCSI card. You may recall my
> earlier problems when the card I bought was SE, not HVD as I was led
> to belive.
>
> The HVD SCSI card is now reconsised at the OBP, along with the tape
> drive and the library on bus 6, devices 0 and 1. After a boot -r,
> cdrecord -scanbus can see the devices on the SCSI bus, so I assume
> that I'm at least 50% of the way to getting this working.
>
> However, much to my surprise, there is no /dev/rmt/1* files. I
> expected these, as my previous tape drive (DDS-4) produced the
> /dev/rmt/0* files.

We have a L9 with DLT8000 (HVD) at work, and its tape drive shows up just
fine as /dev/rmt/x after a 'devsfadm' or 'boot -r'. It is connected thusly:
If you look at the back, the connection to the server is at the rightmost
connector. One connection to the left is the passthrough cable, which
connects to the lower connector at the left. At the upper connector is a HVD
terminator. Hope this helps.


regards,

Derkjan

"Derkjan de Haan" <derkjan@haanjdj.demon.nl> wrote in message news:<409a259e$0$3865$4d4ebb8e@news.nl.uu.net>...
> "Dr. David Kirkby" <see_my_signature_for_my_real_address@hotmail.co m>
> schreef in bericht news:c99d2c79.0405060030.1f5542c3@posting.google.c om...
> > I have a Sun L9 autoloader with DLT-8000 drive in it, and have finally
> > got a real (not Sun I would add) HVD SCSI card. You may recall my
> > earlier problems when the card I bought was SE, not HVD as I was led
> > to belive.
> >
> > The HVD SCSI card is now reconsised at the OBP, along with the tape
> > drive and the library on bus 6, devices 0 and 1. After a boot -r,
> > cdrecord -scanbus can see the devices on the SCSI bus, so I assume
> > that I'm at least 50% of the way to getting this working.
> >
> > However, much to my surprise, there is no /dev/rmt/1* files. I
> > expected these, as my previous tape drive (DDS-4) produced the
> > /dev/rmt/0* files.
>
> We have a L9 with DLT8000 (HVD) at work, and its tape drive shows up just
> fine as /dev/rmt/x after a 'devsfadm' or 'boot -r'.

Em, that is worrying. I'll try a devfsadm, but I have already done a
boot -r.

> It is connected thusly:
> If you look at the back, the connection to the server is at the rightmost
> connector. One connection to the left is the passthrough cable, which
> connects to the lower connector at the left. At the upper connector is a HVD
> terminator. Hope this helps.
>
>
> regards,
>
> Derkjan

Thanks, I'll take another look at this.

The SCSI cable I have between the Sun Ultra 80 and the autoloader is
only 1.0 m long, so with the autoloader on the desk, there was not
sufficient room to connect the workstation to the tape server's upper
socket, so I used the lower one instead. This was not the way it was
originally connected, but I don't think that will make the slighest
difference.

In any case, both devices show up on the SCSI bus, and should be
terminated correctly.

The OBP sees this on the SCSI bus, but is it possible Solaris 9 needs
any drivers or patches loaded before it will reconise it as a tape
drive and so create the device files? That seems very unlikely,
especially given I have used a DDS-4 tape drive before. (The OBP
clearly says TAPE, but I expect that is just what the tape drive says,
not what Solaris uses).

It looks like I might have more of a problem than I thought, but I
only had about 15 minutes after connecting it up to test it out,
before needing to go out. I need to spend some more time with it.

Dr. David Kirkby