Networker

Re: [Networker] Windows2003 R2 change tape order at boot

2007-09-06 11:28:16
Subject: Re: [Networker] Windows2003 R2 change tape order at boot
From: Gaddy <xy.0815 AT GMX DOT NET>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Date: Thu, 6 Sep 2007 11:22:17 -0400
AFAIK persistent binding on the FC-HBA affects only the physical addresses 
of the devices, scsidev AT bus.target DOT lun.
So you can easily put that addressing scheme into a fixed sequence.

Unfortunately NetWorker does not use physical addresses on Windows*,
but logical addresses like \\.\TapeX.

Logical to physical address resolution will be done on "1st come, 1st 
serve", which should be no problem, as long as all "persistent bound" 
devices are online. But, if for some reason (powered off, 
disconnected, ...) one physical address could not be resolved, the logical 
address is given to the next physical device.

This is the way MS works (from my POV).

MS knowledgebase article --> http://support.microsoft.com/kb/873337/en-us
( Thanks Michael ) could (I've never tested this, and in fact have not 
even known about before reading Michaels comment) changes this behaviour 
and adds probably some "logical persistent binding" to Windows2003.

I'd like to know, if someone has played a bit with that fix successfully.

Gaddy

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