Persistent binding is really the only way to accomplish this in earlier
releases. Of course, it isn't strictly necessary for the devID to match across
the storage nodes, it just makes housekeeping easier. In 7.4 and above the gui
presents a much easier mechanism to manage the devices it uses across storage
nodes.
Rudy
________________________________
From: Tom Birkenbach <tom.birkenbach AT WMICH DOT EDU>
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Sent: Fri, December 4, 2009 6:55:38 AM
Subject: [Networker] Persistent Binding
Anyone use "persistent binding" on Solaris in order to get the tape drives
to be consistently recognized across multiple/shared storage nodes? Are
there pros and cons to this?
I came across a small issue where, in setting up a server and two storage
nodes with shared drives (fiber SAN connected), the drives would show up
with different numeric values under /dev/rmt/#cbn. (please note that I'm
essentially a Solaris "noob", so please bear with me) In doing a bit of
research, I came across "persistent binding" and set that up on my storage
nodes (including server) and it seems to work in getting my tape drives to
be recognized consistently.
My question are:
1) Is there a reason to NOT use persistent binding?
2) Is there a better way in getting fiber connected tape drives to be
recognized in a consistent manner?
Any input and insight is greatly appreciated. Thanks!!
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
[email protected] 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
|