Sie sind auf Seite 1von 3

TSM LAN free backups

Why would you want to use LAN free? Generally speaking, backing up and restoring
over a SAN is much faster that over a LAN, but that really depends on how fast
those two items are in your site. Another benefit for traditional TSM is that LA
N free avoids clogging up backup disk pools with large backups, as this uses a f
ront end disk pool that is offloaded to tape each day. LAN free is also very sui
table for big databases. However many TSM installations do not use tape, or they
may use active copy storage pools. So LAN free is not an automatic choice, you
need to study the costs and the benefits to see if it will fit into your site. A
lso, tape drives are finite resource and too much LAN free will quickly use them
Assuming you decide to install LAN free, this is how you would do it on AIX.
Connecting the Tape Drives
First you need to organise cabling up your tape drives. If your backups are crit
ical you will need two fiber cards installed in each client for resilience. Then
you need them cabled up to your SAN switches and zoned in so your client can ac
ccess the tape drives. It is possible to rename your tape drives to something mo
re meaningful that the rmtnn names that UNIX provides by default, but to do that
you need to install an Atape driver, supplied free by IBM. Once you do this, yo
u rename the drives with smitty, or with the chdev command as below. It is best
to give your drives a name that contains the WWWN then they are unique. When you
rename them, several files will be created in the /dev directory. The device pa
rameter in your path name in TSM must match these names. The chdev command in fu
ll is:
chdev -l rmt0 -a new_name=T_AA02450
Defining the Storage Agent
Define at the TSM Server
Use a comand like the one below to define a storage agent to the TSM server. If
you want to look at existing storage agents to see how they are defined, you wil
l find them by using the 'q server' command or the 'other servers' tab in the GU
define server nnnnn serverpassword=password hla=x.xx.xx.xx lla=xxxx
nnnnn is the name of the storage agent. Each agent name needs to be unique, so c
ome up with a good naming standard. A simple standard that works is nodename_age
password is the password for the storage agent and must match the password suppl
ied in the client definition below
xx.xx.xx.xx is the ip address (or DNS entry) of the client machine
xxxx is the port you use in the dsm.sys for the storage agent. The example below
uses 1510.
define the tape paths
To define the tape paths to the TSM server, use commands like
define path SRCT=server destt=drive library=LIBNAME device
If you use alternate pathing, add a '0' onto the end of your tape name in the de
vice parameter above.
Define at the Client
The Storage Agent is usually found in the /opt/tivoli/tsm/StorageAgent/bin/ for
TSM 6.1 clients and above, and /usr/tivoli/tsm/StorageAgent/bin/ in TSM 5.5 clie
nts and below. A Storage Agent is basically just a cutdown version of a TSM serv
er with a reduced command set. It needs a dsmsta.opt options file just like a re
al server and typical values could be as follows.
Commmethod tcpip
Devconfig devconfig.sta
txngroupmax 512
enable3590library yes
commtimeout 7200
idletimeout 120
tcpport 1510
You need to work out what timeout parameters are best for your site. Commtimeout
is in seconds and idletimeout in minutes, so they are both set here to two hour
s. If you are backing up Oracle databases with incremental RMAN, then Oracle can
spend some time searching its catalog to workout what needs to be backed up. Wi
thout high timeout values the backup could fail, so the numbers above could be r
easonable. However this does mean that if you hit a problem you are locking out
tape drives for a long time, so smaller values could be more appropriate for sta
ndard backups.
Once you have an options file you create the storage agent with the command
dsmsta setstorageserver myname=nnnn mypasswordpppp myhladdress=nnn
servername=TSM1 serverpassword=pppp hla=nnn lla=mmmm
This will create a file called devcongif.sta that contains the above details, wi
th the passwords encrypted. The parameters in the command are
myname is the name you call your storage agent, the same one you used to define
the agent to the TSM server above.
mypassword is the password for the storage agent and must match the password use
d when you defined the agent to the server.
myhladdress is the TCPIP address of the client that is hosting this storage agen
servername is the name of the TSM server
serverpassword is the password for the TSM server
hla is the tcpip address that you use to get to the TSM server, the same one tha
t you use in the dsm.sys file
lla is the port name that you use to access the TSM server, the tcpport paramete
r in the dsm.sys file
Next you need to start your storage agent, which you can do by simply typing ech
o "dsmsta" from the command line. To stop the storage agent, you can log into it
using 'dsmadmc -se=storageagentname then typing halt from the command line. Alt
ernatively, just use the UNIX kill command.
Changes to dsm.sys
To use LAN free backups you need to make a few changes to the dsm.sys file. Firs
t you need to add a stanza for the storage agent like this, which is used to con
nect to the storage agent with the dsmadmc command. The node name must not be th
e one you use for normal backups.
servername nodename_agent
tcpport 1510
commmethod tcpip
The tcpserveraddress could be the address of your real server, but it is shown h
ere as the standard IP address of the localhost, as it is just used for internal
The tcpport number does not have to be 1510, but it must match the value you use
d in dsmsta.opt. I avoid 1500 as that is the server default and like to use 1501
upwards for the webports, so it seems reasonable to standardise all the storage
agents at 1510. You must make sure that you do not conflict with any address us
ed by other software on your machine so this standard might not be suitable for
Next you need to add some lines to your exisiting backup stanzas like this
servername TSM1
commmethod tcpip
webports 1501,0
other parms .
lanfreecommmethod tcpip
lanfreetcpport 1510
enablelanfree yes
The lanfreetcpport number must match the tcpport in dsmsta.opt and the tcpport i
n the storage agent stanza
Management Class
Finally you need to create a management class that writes direct to tape. Thebac
kup section discusses how to do this