I'm not really disagreeing with Tim's statement that the 
automatically-generated tape device file names are, er, unattractive.  But the 
names do have meaning; the WWID of your device is part of the name.  And, I 
don't think we ever need to fat-finger in the device name; both the NetWorker 
GUI and CLI should find these names automagically.

So, unless I'm missing something, who cares if they're ugly (at least as far as 
NetWorker is concerned)?

tl

-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On 
Behalf Of Tim Mooney
Sent: Monday, January 14, 2013 3:20 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] udev names / persistent bindings

In regard to: [Networker] udev names / persistent bindings, Teresa Biehler...:

> We're setting up a new Linux NetWorker server and are having problems
> getting setting up the devices.  Does anyone have a reference or
> suggestions on setting up the changer and tape devices with udev names
> for persistent binding?

You don't say what Linux distribution and version, so it's a little hard
to make recommendations.

At least with RHEL 6.x, it's already doing persistent bindings for both
the changer and the tape drives.  The problem for me is that the
persistent names it's using for the tape drives are horrible.  It's not
all that often that I have to specify a device when using nsrjb, but when
I do, I don't want it to be

        /dev/tape/by-id/scsi-350060b00002e179a-nst

Again assuming RHEL6, there should also be a link for your changer in the
/dev/tape/by-id directory, but assuming you only have one changer visible
to the host, you would be safe using the /dev/changer link.

You may also want to search Powerlink (or whatever it's called these days)
for document 300-008-352 .  It's a PDF with technical information on tape
devices, and there's a section in there for Linux and udev.

Finally, search the mailing list archives for posts from Frank Swasey 
in October 2012.  He provided some excellent guidance regarding udev and
making persistent device names that don't suck.

Tim
-- 
Tim Mooney                                             Tim.Mooney AT ndsu DOT 
edu
Enterprise Computing & Infrastructure                  701-231-1076 (Voice)
Room 242-J6, IACC Building                             701-231-8541 (Fax)
North Dakota State University, Fargo, ND 58105-5164