We use two card or one.  We have both TSM names in the DNS  tsm_primary
and tsm_backup.  We then use the name we want to use in the dsm.opt
file.  The backup is a private network we use just for backups.  We do
not route to or from this network.  Thus we can be sure that a server is
not going out the primary and then across a bridge or router to the
backup network.  If it wants to go out the primary looking for
tsm_backup then it will fail and we can look at the routing tables to
find out what to fix.  If the system only has a primary connection then
we use tsm_primary in its dsm.opt.  This has worked great for us.  When
we move tsm to a newer machine we get it working and then just change
the dns names and that night everybody goes to the new server.


--
Phillip
(901)320-4462
(901)320-4856 FAX



-----Original Message-----
From: Tyree, David [mailto:david.tyree AT SGMC DOT ORG] 
Sent: Thursday, April 06, 2006 2:51 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] DSM.OPT file


            I've got a question about the usage of the
"TCPSERVERADDRESS" line in the dsm.opt file on the clients.

            Currently I have the IP address of the TSM server listed in
the dsm.opt file on the clients. We will be implementing a new
addressing scheme for all of our servers in a couple of months and that
includes the TSM server itself.          

            In our case the DNS name of the server happens to match the
name of the TSM server instance. Since our TSM server only has one NIC
and thus only one IP address I went ahead and changed the line to show
the DNS name of the TSM server instead of the IP on a few of the
clients. The DNS name of the TSM server will not be changing, only the
IP address. I wasn't sure at the time if the TSM client would work with
the DNS name instead but I since found in the TSM docs it would. And
found that it actually did work just fine.

            The next issue is that we are thinking about adding another
NIC in the TSM at some point in the future to help split the load on the
network. At that point the TSM server will then have two IP's. Any
clients that I want to have come into the TSM server on the second NIC
would have to have the IP of the second NIC in its dsm.opt file. That
part makes complete sense.

            But what about any clients that I have with the DNS name of
the TSM server in the dsm.opt file instead of the IP address? Which NIC
would they connect to? If I absolutely wanted to ensure that the clients
came into the TSM server on the right NIC I would make sure I had the
right IP listed in that clients options file. But what would happen if I
left the DNS entry in the options file? 

            

 

David Tyree 
Enterprise Backup Administrator 
South Georgia Medical Center 
229.333.1155 

Confidential Notice:  This e-mail message, including any attachments, is
for the sole use of the intended recipient(s) and may contain
confidential and privileged information.  Any unauthorized review, use,
disclosure or distribution is prohibited.  If you are not the intended
recipient, please contact the sender by reply e-mail and destroy all
copies of the original message

*********************************************************************
This message and any attachments are solely for the intended recipient. If you 
are not the intended recipient, disclosure, copying, use or distribution of the 
information included in this message is prohibited -- Please immediately and 
permanently delete.