Tivoli Storage Manager
This is a guide to configuring a
Sparcstorage Library (Exabyte EXB-210) Firstly do a probe-scsi-all and check that these match the scsi id reported by the Sparcstorage library. ie /pci@1,f,0/pci@1/pci@3/SUNW, isptwo@4 target 3 unit 0 Removable tape Exabyte EXB850smbansh20793 target 4 unit 0 Removable tape Exabyte EXB850smbansh20793 target 5 unit 0 Removable device 8 Exabyte EXB-210 3.11 This says that there are two tape drives at scsi id 3 and 4 and the tape library itself has a scsi id of 5
to an ultra5 Mount the TSM cd and install the Tivoli software
pkgadd -d /cdrom/cdrom0Configure the tape devices.
Edit the file /usr/kernel/drv/mt.conf and add the two tape drives. In this case scsi id's 3 and 4. Your 2 lines will be name="mt" class="scsi" target=3 lun=0; name="mt" class="scsi" target=4 lun=0; Edit the file /usr/kernel/drv/lb.conf and add an entry for the tape library itself. Your line will be name="lb" class="scsi" target=5 lun=0; You will now need to create these devices by running add_drv. /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/lb /usr/sbin/add_drv -m '* 0666 bin bin' /usr/kernel/drv/mtRegister devices with TSM
Next you will have to register these devices twith TSM. You may need to set an environment variable DSMSERV=/opt/tivoli/tsm/server/bin start the DSM Server DSMSERV cd /opt/tivoli/tsm/server/bin ./dsmserv You should now be at the dsmserv prompt TMS: Server1> Firstly lets increase the size of the disk backup pool and the log file. The sizes here are in Mbytes and we are putting them on the /tivoli filesystem because it has space the filenames are arbitory but should be unique. The sizes to use for the database, log and backup pool should be calculated for your requirements. See the Calculating TSM sizes for an explanation of calculating the sizes. define dbvolume /tivoli/db2.dsm formatsize=500 define logvolume /tivoli/log2.dsm formatsize=50 define volume backuppool /tivoli/backup_pool.dsm formatsize=500 Next we need to expand the database and log by the size of the files we have just created. extend db 500 extend log 50 If you need a mirror database If your Tivoli Storage Manager database is not on a high availability disk ie (mirror, striping with spares) etc then you will need to create a backup mirror database. to do that do. define dbvolume /tivoli/db2.mir formatsize=500 define dbcopy /tivoli/db2.dsm /tivoli/db2.mir In the above we are creating a mirror database the size of the existing database and making a copy of it. Next license the software. We will license the Library and 10 clients. register license file=advdev.lic register license file=10client.lic Create and administrator for the syetsm We will create an administrator called neville with the password hobble register admin neville hobble grant authority neville classes=system Now register the library and tape drives Here we will call the tape library SPARCstorage and the two tape drives DRIVE01 and DRIVE02. The dev names from /dev/rmt have the extensions lb and mt respecivly. In the below examples /dev/rmt was blank if you have other devices or had previously ran a drvconfig or boot -r then the device numbers will he higher than those shown. define library SPARCstorage libtype=scsi device=/dev/rmt/0lb define drive SPARCstorage drive01 device=/dev/rmt/2mt element=82 define drive SPARCstorage drive02 device=/dev/rmt/1mt element=83 The elements 82 and 83 are physical addresses of the devices within the library. In our case element(position) 82 is the top drive and 83 the bottom drive. It is important to get the tapes drives correctly matched. ie the right element number to the right /dev device. If you get it wrong then the wrong drive will be used. If this happens use "delete drive SPARCstorage drive01" to remove the drives and then re-define them the correct way around. It is also very important to use the /dev/rmt/**mt devices as created by the add_drv commands and not any other /dev/rmt/** which might also access the drive ie by running drvconfig or a reboot -r. Any other /dev/rmt/** device will cause lots of ambiguous starnge problems to occur. Define device classes Next we need to group the devices by their function. In this case they are both 8mm Exabyte devices and the device class will be called exabyte. define devclass exabyte devtype=8mm format=8500 library=SPARCstorageSetup and label the tapes and tape pools
Set up storage pools We need to set up a storage pool and tell it what tape drive pools to use. In this case we will use the just defined devices pool exabyte and call the storage pool playpool. The maxscratch is the maximun number of tapes to use from the unlabled tapes in the library. The maxscratch variable is the maximum amount of tapes you will ever use. define stgpool playpool exabyte maxscratch=9999 Label the Tapes As we do not have a bar code reader we will label the tapes manually. Here we will label the first tape tape001 then tape002, tape 003, etc. Make sure to only have tapes in the library that you want to label. No cleaning tapes and no tapes that you do not want to label. label libvolume SPARCstorage search=yes checkin=scratch labelsource=prompt You will now be prompted to label the tapes one at a time to do this you need to use the command "reply nnn label=tapename". an example prompt is:- ANR9999 001: Please provide the label name for the volume in element 1 of library SPARCSTORAGE by issuing reply n label=xxx within 60 minutes, where n is the request ID and xxx the desired label name In this case issue the command "reply 001 label=tape001" The tape will then be loaded and labeled. You will be then prompted for the next label. in this case it will be "reply 002 label=tape002" etc, etc, etc. update the storage pool You need to inform tsm where next to move the data (ie from disk to tape) to do this use the update command. update stgpool backuppool nextstgpool=playpoolNow we need to register the nodes to backup
We will add the nodes boobo,wylie and bugs. They will have the passwords set to passwd_nodename respectfully. register node boobo passwd_boobo userid=none register node wylie passwd_wylie userid=none register node bugs passwd_bugs userid=none On the server you will have to set up the connection method from the clients. to do this you will need to edit the file dsmserv.opt /opt/tivoli/tsm/server/bin/dsmserv.opt contains:- commmethod tcpip tcpport 1500 tcpwindowsize 0 tcpnodelay yes On the client systems you will need to edit the dsm.sys file and add the server name. eg /opt/tivoli/tsm/client/ba/bin/dsm.sys contains:- SErvername backup COMMmethod TCPip TCPPort 1500 TCPServeraddress backup.test.arndike.co.uk You could also enter what needs to be backed up and the password accessing. The examples of this are domain all-local passwordaccess generate Next we need to setup the schedules Here we setup the schedule "standard" to do the appropriate actions in this case the incremental at 23:00 and associate this schedule with the nodes. set schedmodes any define schedule standard daily_incr action=incremental starttime=23:00 define association standard daily_incr boobo, wylie, bugs Thresholds for data movement Next we need to say when to migrate the data fron the disk pools to the tapes. As we are testing we will do this immediatly and therefore set the defaults zero from the normal values of high=90 and low=70. update stgpool backuppool highmig=0 lowmig=0Start your backups
You should now be able to run dsm (gui based) or dsmc (command line) to start doing your backups/restores/etc. An example to do am immediate backup is dsmc i The system will automaytically be backed up nightly at 23:00 as specified when the schedule was defined. The client system will need to have "dsmc sched" running to be able to be backed up. To have dsmc started automatically put the following entry in /etc/inittab. tsm::once:/usr/bin/dsmc sched >/dev/null 2>&1 To change when a schedule is ran use the "update schedule xx xxx" command.
For information regarding this page e-mail:neville_seed@yahoo.com