Not necessarily....
We had device names exactly \\.\Tape0 , \\.\Tape1 with the IBM drivers
before the change...
When We tried the Microsoft driver, it resulted in unique names with a
serial number like string \\.\tapexxxxxxxx (but it was not the drive
SN), which did not work (and are a pain to enter in jbconfig).
> -----Original Message-----
> From: Matthew Huff [mailto:mhuff AT ox DOT com]
> Sent: Wednesday, March 12, 2008 8:18 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU; Goslin, Paul
> Subject: RE: [Networker] Library/Drive Names getting shuffled
> by Windows.
>
> You will know when the "fix" is working since you won't have
> device names like \\.\tape0, \\.\tape1, etc... What hangs up
> most people is they try to set persistent binding via the
> fiberchannel drivers. That works on Unix, but the Windows
> plug & play driver overrides it and re-assigns device names,
> so under windows its useless. Once you get the hotfix or ibm
> tape driver working, it will be very obvious.
>
>
>
> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Goslin, Paul
> Sent: Wednesday, March 12, 2008 8:03 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Library/Drive Names getting shuffled
> by Windows.
>
> We've been working with Dell regarding this very issue. We
> have a 60 slot library and it had 3 IBM LTO2 drives until
> last December, when we added two more drives. Before adding
> the drives, I think we had persistent binding implemented via
> the IBM driver/registry lock down and never had any problems
> with drive mapping changing across reboots. In the process of
> adding the new drives, the Dell tech installed Dell drivers
> for all the drives, including the new ones. Ever since, we've
> had problems whenever the server was rebooted. We opened a
> case and we tried some registry hacks (including adding the
> persistence entry mentioned below), but nothing has worked so
> far. Now they recommend either using an emulex elxcfg.exe
> utility (we have an emulex fiber card) or installing SP2 for
> Win2003 server, which is supposed to include a fix for this...
>
> > -----Original Message-----
> > From: EMC NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Matthew Huff
> > Sent: Tuesday, March 11, 2008 8:44 PM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: Re: [Networker] Library/Drive Names getting shuffled by
> > Windows.
> >
> > True. Some libraries allow you to set the WWN/Serial # by
> the port on
> > the library so changing a tape drive doesn't change the id.
> However,
> > even if it changes, the results are predictable and easy to
> resolve.
> > Random ordering of tape drives especially in large
> libraries is much
> > more of a major issue.
> >
> > -----Original Message-----
> > From: EMC NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Frank Swasey
> > Sent: Tuesday, March 11, 2008 7:55 PM
> > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > Subject: Re: [Networker] Library/Drive Names getting shuffled by
> > Windows.
> >
> > All set that is until you have to replace a drive unless
> you can force
> > it to take the serial number of the failed drive.
> >
> > Today at 6:06pm, Matthew Huff wrote:
> >
> > > What's generally called "drive persistence" is a fiber
> > channel feature that under unix maps a Fiber Channel WWN to a fixed
> > unix device name. In windows, even with fiber channel drivers that
> > support "persistence", it merely maps the FC WWN to a lower level
> > device, however Windows "Plug & Player"
> > driver will re-number the device on top of that, so \\.\tape0 , etc
> > could be a different drive each time (although normally it
> won't be,
> > it's usually when something in the order changes, the drives get
> > renumbered differently.
> > >
> > > However, once you use either the IBM tape driver or
> > Microsoft new fix then the drivers will get created like
> > \\.\tapeSERIALNUMBER so that no matter what order they get
> created by
> > the Plug & Play driver, they will always have the same
> name. After the
> > reboot you will have to edit your jukebox with the new drive names,
> > but you should be set.
> > >
> > > -----Original Message-----
> > > From: EMC NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> > > On Behalf Of James E. Pratt
> > > Sent: Tuesday, March 11, 2008 5:43 PM
> > > To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > > Subject: Re: [Networker] Library/Drive Names getting
> > shuffled by Windows.
> > >
> > > Ok. So I am also afflicted with this "dev shuffle" issue. After
> > > looking at this "hotfix", and comparing to our NW 7.4
> > windows 2003 r2
> > > (patched via windows update last week), I see I have a
> > version number
> > > that is much higher on tape.sys, so needless to say,
> after running
> > > regedit, I see I also have the
> > >
> >
> \\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Tape\Persistence
> > > value there, but alas it was set to 0 ... :(
> > >
> > > So I changed it to a 1. I'm not in a position to reboot right now
> > > (backups are running), but I will indeed reboot it tomorrow
> > to see if
> > > the tape0-3 device names in winblows get shuffled again.
> > >
> > > Anyhow, I'm certainly not installing some hotfix that is
> from last
> > > july, and are obviously outdated, given the versions on our
> > server and
> > > the ones in these kb's.. So, I'll let you know... I'm
> > actually kind of
> > > baffled this problem still exists at all to be honest. I
> > had to fight
> > > it for years with a physical (pos) hp msl series library with 6
> > > drives. :\
> > >
> > > Lastly, what persistence are you talking about when you
> say it only
> > > applies to *nix?
> > >
> > > Regards,
> > > Jamie
> > >
> > >
> > >
> > >
> > >
> > >> -----Original Message-----
> > >> From: EMC NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> > >> On Behalf Of Matthew Huff
> > >> Sent: Tuesday, March 11, 2008 4:02 PM
> > >> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > >> Subject: Re: [Networker] Library/Drive Names getting shuffled by
> > >> Windows.
> > >>
> > >> There really shouldn't be a need to do this. If you apply
> > the windows
> > >> hotfix, the device names change to ones that use the
> > serial# of the
> > >> drive, so they won't change even if the order changes.
> > >>
> > >> -----Original Message-----
> > >> From: EMC NetWorker discussion
> > [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> > >> On Behalf Of MIchael Leone
> > >> Sent: Tuesday, March 11, 2008 3:53 PM
> > >> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> > >> Subject: Re: [Networker] Library/Drive Names getting shuffled by
> > >> Windows.
> > >>
> > >> "Hutchison, Jay A" <Jay.Hutchison AT va DOT gov> wrote on 03/11/2008
> > >> 03:13:00
> > >> PM:
> > >>
> > >>> We have a procedure that does not require you to delete
> > and recreate
> > >> the
> > >>> library if anyones interested. It`s just a rescan and
> reconfigure.
> > >>
> > >> I'd be interested, especially if it's automated ...
> > >>
> > >> To sign off this list, send email to
> > listserv AT listserv.temple DOT edu and
> > >> type "signoff networker" in the body of the email.
> Please write to
> > >> networker-request AT listserv.temple DOT edu if you have any
> > problems with
> > >> this list. You can access the archives at
> > >> http://listserv.temple.edu/archives/networker.html or via RSS at
> > >> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >>
> > >> To sign off this list, send email to
> > listserv AT listserv.temple DOT edu and
> > >> type "signoff networker" in the body of the email.
> Please write to
> > >> networker-request AT listserv.temple DOT edu if you have any
> > problems with
> > >> this list. You can access the archives at
> > >> http://listserv.temple.edu/archives/networker.html or via RSS at
> > >> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> > > To sign off this list, send email to
> > listserv AT listserv.temple DOT edu and
> > > type "signoff networker" in the body of the email. Please
> write to
> > > networker-request AT listserv.temple DOT edu if you have any
> problems with
> > > this list. You can access the archives at
> > > http://listserv.temple.edu/archives/networker.html or via RSS at
> > > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> > > To sign off this list, send email to
> > listserv AT listserv.temple DOT edu and
> > > type "signoff networker" in the body of the email. Please
> write to
> > > networker-request AT listserv.temple DOT edu if you have any
> problems with
> > > this list. You can access the archives at
> > > http://listserv.temple.edu/archives/networker.html or via RSS at
> > > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> > >
> >
> > --
> > Frank Swasey | http://www.uvm.edu/~fcs
> > Sr Systems Administrator | Always remember: You are UNIQUE,
> > University of Vermont | just like everyone else.
> > "I am not young enough to know everything." - Oscar Wilde
> > (1854-1900)
> >
> > To sign off this list, send email to
> > listserv AT listserv.temple DOT edu and type "signoff networker"
> in the body
> > of the email. Please write to
> networker-request AT listserv.temple DOT edu if
> > you have any problems with this list. You can access the
> archives at
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
> > To sign off this list, send email to
> > listserv AT listserv.temple DOT edu and type "signoff networker"
> in the body
> > of the email. Please write to
> networker-request AT listserv.temple DOT edu if
> > you have any problems with this list. You can access the
> archives at
> > http://listserv.temple.edu/archives/networker.html or via RSS at
> > http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> >
>
> To sign off this list, send email to
> listserv AT listserv.temple DOT edu and type "signoff networker" in
> the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any
> problems with this list. You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS
> at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
