David,

I've recently seen this on Windows with NetWorker 7.1.1 and 9940 tape
drives with persistent binding configured.  Sometimes the customer has
to reapply the driver after a reboot.  Often it's only a drive or two,
not all of them.

Mark

On 8/9/05, NETWORKER automatic digest system
<LISTSERV AT listserv.temple DOT edu> wrote:
> There are 14 messages totalling 946 lines in this issue.
> 
> Topics of the day:
> 
> Date:    Tue, 9 Aug 2005 18:01:14 -0400
> From:    Terry Lemons <lemons_terry AT EMC DOT COM>
> Subject: Re: SAN connections in Windows environments
> 
> I'm wondering if your Fiber Channel adapters have persistent binding
> enabled.  If not, Windows may become confused from boot to boot about seeing
> 'different' devices (along different paths through multiple HBAs through the
> SAN, for instance).
> 
> Just a thought.
> tl
> 
> -----Original Message-----
> From: Legato NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT 
> EDU] On
> Behalf Of Willeat, Todd
> Sent: Tuesday, August 09, 2005 5:47 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] SAN connections in Windows environments
> 
> I have seen that as well. A reboot or two fixes it for me, but I have no
> real solution yet...
> 
> -----Original Message-----
> From: Legato NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]On Behalf Of Browning, David
> Sent: Tuesday, August 09, 2005 4:42 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: [Networker] SAN connections in Windows environments
> 
> 
> We are having an intermittent problem with tape devices not getting
> "numbered".  For example, we were brining a new SAN device (Win2k3 server)
> on line, and it initially recognized all 8 of my LTO-2 drives.  We did a
> test backup over fiber, and it worked fine.  We rebooted the new client
> (Win2k3 Server), and now it doesn't assign tape numbers.  If you run the
> inquire command, you see all 8 devices, but it doesn't show a number (see
> text below).
> 
> 
> 
> I was just curious if anyone else has gone through this.  We are running
> 7.1.3 on both client and server.  We are using DDS and the client is running
> as a storage node.
> 
> 
> 
> Thanks in advance for any insight.
> 
> 
> 
> O:\>inquire
> 
> [email protected]:TEAC    CD-224E         K.9A|CD-ROM
> 
> [email protected]:IBM     ULTRIUM-TD2     4770|Tape,   *No Number, s/b \\.\Tape0
> 
>                                           S/N: 102100111A
> 
>                                           ATNN:IBM     ULTRIUM-TD2
> 10210011
> 
> 1A
> 
>                                           WWNN:202F0090A500111A
> 
> [email protected]:IBM     ULTRIUM-TD2     3AY4|Tape,
> 
>                                           S/N: 102200111A
> 
>                                           ATNN:IBM     ULTRIUM-TD2
> 10220011
> 
> 1A
> 
>                                           WWNN:202F0090A500111A
> 
> [email protected]:IBM     ULTRIUM-TD2     4770|Tape,
> 
>                                          S/N: 102300111A
> 
>                                           ATNN:IBM     ULTRIUM-TD2
> 10230011
> 
> 1A
> 
>                                           WWNN:202F0090A500111A
> 
> 
> 
> David M. Browning Jr.
> 
> LSUHSC Enterprise Network Operations/Help Desk
> 
> (504) 568-4364 - Direct
> 
> (504) 914-7550 - Cell
> 
> 
> --
> End of NETWORKER Digest - 8 Aug 2005 to 9 Aug 2005 (#2005-194)
> **************************************************************
>

--
Note: To sign off this list, send a "signoff networker" command via email
to listserv AT listserv.temple DOT edu or visit the list's Web site at
http://listserv.temple.edu/archives/networker.html where you can
also view and post messages to the list. Questions regarding this list
should be sent to stan AT temple DOT edu
=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=*=