Login

IT-wiki

TSM-server-configuration

it
RecentChanges
FindPage
HelpContents
TSM-server-configuration

TSM server configuration

It is assumed that the basic Tivoli Storage Manager setup has been performed as
described in TSM-server-initialization.
Contents

TSM server configuration

o TSM documentation
o TSM commands

TSM database configuration

o Create filesystems for large files
o Format Database, Log, and Data volumes on disk

o Define new Database, Log, and Data volumes

o Extend Database and Log

TSM storage pools

o Configure storage pools
o Define storage pool volumes

Backup management and policies

o Define management classes and policy set
o Define copygroups

Database backup
o Define device classes
o Define database backups

Scheduling backups
o Define backup schedules
o Define administrative schedules

Backup of TSM client nodes

o Register nodes
o Define client options
o Making a client backup

Server parameters and information

o TSM filespaces
o Client storage utilization
o Server log

TSM documentation
TSM documentation is available on-line from IBM's Tivoli Documentation site.

TSM commands
On the TSM server Linux machine, connect to the TSM server using the TSM
administrative command line tool dsmadmc:
/opt/tivoli/tsm/client/ba/bin/dsmadmc

using the username root and password as defined previously. It is

recommended not to use dsmadmc from network clients for reasons of security,
please use an SSH connection to log in to the TSM server.
Commands within dsmadmc can be abbreviated to the shortest unique string, for
example query can be abbreviated as q. The abbreviation is shown in
the HELP manual for each command, for example:
helpqueryvolume

where letters in Capitals are the shortest form of the command.

Full details of the query commands are in most cases displayed by
the format=detailed (abbreviated as f=d) option, for example:
qvolf=d

TSM database configuration

TSM uses an internal database for keeping track of stored files and configurations,
and preformatted disk files (or tape units) for storing actual client node backup data.
Create filesystems for large files
The disks which we use for the TSM server volumes will only contain very few, but
large, files. Firstly, the fdisk command is used to write a partition table to the TSM
disks. Probably you want to create only one partition spanning the entire disk device.
Secondly, the Linux ext3 filesystems used by TSM should be created with
appropriate parameters:
mke2fsjvm1Tlargefile4/dev/sdXX

See man mke2fs for explanation of the parameters. The actual disk device should
replace /dev/sdXX.
Format Database, Log, and Data volumes on disk
TSM works with preformatted Database, Log, and Data volumes on local disks.
These should be placed on separate physical devices for performance reasons, and

these volumes should be protected by mirroring or RAID-5 for reliability reasons. For
Database and Log volumes it is also possible to have 2 or 3 copies on separate
physical disks, but with mirrored disks we do not want to use this feature of TSM.
We have mounted the various separate filesystems used below.
In a Linux/UNIX shell prompt, use the /opt/tivoli/tsm/server/bin/dsmfmt formatting
tool. Define a 2 GB Log volume:
#dsmfmtglog/u3/log/log12

Define an 8 GB Database volume:

#dsmfmtgdb/u2/db/db18

Define a 32 GB Data volume:

#dsmfmtg/u1/data/data132

If necessary you may create additional volumes of each type, and with different sizes
as needed. The maximum size of a volume is dictated by the filesystem of the
server; on Redhat RHEL4 the file size limit is 64 GB, so you must use number less
than 64 GB with dsmfmt (63 GB is the proposed maximum size).
Define new Database, Log, and Data volumes
The newly formatted Database, Log, and Data volumes are added to the TSM server
within the dsmadmc TSM administration tool:
definelogvol/u3/log/log1
definedbvol/u2/db/db1
definevolumeBACKUPPOOL/u1/data/data1

Check the newly defined volumes by:

querylogvol
querydbvol
queryvolume

After you see both the newly added volumes as well as the predefined TSM
volumes, then you may remove the predefined default ones from the TSM package:
deletelogvol/opt/tivoli/tsm/server/bin/log.dsm
deletedbvol/opt/tivoli/tsm/server/bin/db.dsm
deletevolume/opt/tivoli/tsm/server/bin/backup.dsm

When these volumes have been successfully deleted from TSM, the corresponding
files can be removed from the filesystem as well.
Extend Database and Log
Once the new and larger Database and Log volumes have been configured as
above, the size of the database and log should be increased:
extenddb4000
extendlog1000

The units of extension are Megabytes, and you may want to extend the Database
and Log up to the maximum size of the defined volumes. Query the sizes by:
querydb
querylog

TSM storage pools

TSM uses the concept Storage Pool to describe disk or tape areas where backup
client data files are stored. The default TSM installation defines 3 storage
pools ARCHIVEPOOL,BACKUPPOOL, and SPACEMGPOOL.
Configure storage pools
We will only be concerned with using the BACKUPPOOL, which should have some
parameters modified:
updatestgpoolBACKUPPOOLdescription="Backupstoragepool"lowmig=50
maxsize=100m

We use a large, inexpensive RAID disk box as secondary storage pool

named RAIDPOOL:
definestgpoolRAIDPOOLDISKdescription="RAIDdiskstoragepool"
maxsize=100m

and make it a secondary storage pool to BACKUPPOOL:

updatestgpoolBACKUPPOOLnextstgpool=RAIDPOOL

We could also define storage pools for tape robots at this stage, but we do not
currently use any tape robots.
Define storage pool volumes

Some disk (or tape) volumes must be defined to the above storage pools. We use
only disk volumes on fast SCSI disks (BACKUPPOOL) and slower RAID devices
(RAIDPOOL):
definevolumeBACKUPPOOL/u1/data/data1
definevolumeRAIDPOOL/u/raid/raid01

Backup management and policies

TSM uses a hierarchy of management classes and policy set to define backups of
TSM client nodes.
Define management classes and policy set
Define domain, policy set, and management classes within the dsmadmc tool:
definedomainCAMP_DOMAINDESCription="CAMP'spolicydomain"
definepolicysetCAMP_DOMAINCAMP_POLICYdescription="CAMP'sdefault
policy"
definemgmtclassCAMP_DOMAINCAMP_POLICYMGTCLASS1description="Management
ClassNo.1"
definemgmtclassCAMP_DOMAINCAMP_POLICYEXTRA_COPIESdescription="Extra
copiesofimportantfiles"
definemgmtclassCAMP_DOMAINCAMP_POLICYSHORT_LIVEDdescription="Data
fileswithashortbackuplife"
assigndefmgmtclassCAMP_DOMAINCAMP_POLICYMGTCLASS1

In order to activate the backup policy defined by the policy set and management
classes, the policy set should be validated and activated:
validatepolicysetCAMP_DOMAINCAMP_POLICY
activatepolicysetCAMP_DOMAINCAMP_POLICY

Define copygroups
The destination storage pool for client node backups is defined by means of a Copy
Group for the various management classes:
definecopygroupCAMP_DOMAINCAMP_POLICYMGTCLASS1destination=BACKUPPOOL
verexists=1verdeleted=1
definecopygroupCAMP_DOMAINCAMP_POLICYSHORT_LIVEDdestination=BACKUPPOOL
verexists=1verdeleted=1retextra=2retonly=8
definecopygroupCAMP_DOMAINCAMP_POLICYEXTRA_COPIES
destination=BACKUPPOOLverexists=5verdeleted=1

Here we have specified how many versions of a given file may reside in the storage
pool, both if the files exists on the client or has been deleted. We may also specify
how many days to keep a file in the storage pool after it has been deleted on the
client.

Database backup
Backups of the internal TSM database must be made to an area of a remote server,
in case the TSM database should ever get lost or corrupted. We assume that a
remote NFS filesystem /home/backup/TSM is available to us with root priviledges for
writing.
Define device classes
For regular database backups define special device classes:
definedevclassDBBACKUPdevtype=filedirectory=/home/backup/TSM
maxcapacity=2G
definedevclassFILEdevtype=filedirectory=/home/backup/TSM
maxcapacity=500M

This can be used for manual full or incremental database backups:

backupdbdevclass=DBBACKUPtype=full
backupdbdevclass=DBBACKUPtype=incremental

However, these backup tasks should normally be performed by an automatic task

(see below).
Define database backups
The TSM internal database must be backed up before the database log becomes
full:
setlogmodeROLLFORWARD
defineDBBACKUPTRIGGERdevclass=DBBACKUPlogfullpct=50

Scheduling backups
Define backup schedules
Schedules for client node backups (every midnight, or at noon on weekdays) are
defined by:
definescheduleCAMP_DOMAINDAILY_BACKUPdescription="Backuprunevery
night"starttime=00:00:00duration=4period=1
definescheduleCAMP_DOMAINNOON_BACKUPdescription="Backupat12:00
(laptopsetc.)"starttime=12:00:00dayofweek=weekdayduration=4period=1

Check the schedules by:

queryscheduleformat=detailed

Define administrative schedules

Internal TSM administrative tasks are scheduled for backups of the internal TSM
database:
definescheduleADSM_DB_BACKUPtype=Administrativecmd="backupdb
devclass=dbbackuptype=full"active=yesstarttime=05:40:00
definescheduleADSM_DB_RESETtype=Administrativecmd="deletevolhistory
todate=todaytype=all"active=yesstarttime=05:30:00
queryscheduletype=Administrativeformat=detailed

Backup of TSM client nodes

TSM will only permit backups of clients which have been properly registered within
the TSM server.
Register nodes
Client nodes (say, <NODENAME>) for TSM backup are registered in the TSM server
by:
registernode<NODENAME><nodepassword>domain=CAMP_DOMAIN

A client node is associated with a TSM backup schedule:

defineassociationCAMP_DOMAINDAILY_BACKUP<NODENAME>

For laptops you would choose the schedule name NOON_BACKUP in stead
of DAILY_BACKUP.
List the set of registered nodes:
querynode

or individual nodes by:

querynode<NODENAME>format=detailed

Define client options

We want to restrict the file directories which the client nodes are permitted to back
up, because we do not want to backup the operating system files etc. of the clients,
but only user data.
For Microsoft Windows clients we must set this up inside the TSM server, because it
is very cumbersome and error prone to do this on the client nodes. For Linux and
UNIX clients it is more convenient to use the inclexcl.list file with the TSM client.

Define option sets in the TSM server for client backups:

definecloptsetWINDOWSOPTdescription="BackupoptionsforWindowsclients"

Define rules within this option set:

defineclientoptWINDOWSOPTdomainC:force=yes
defineclientoptWINDOWSOPTinclexcl"exclude*:\...\*.*"force=yes
seqnumber=2
defineclientoptWINDOWSOPTinclexcl"exclude*:\...\*"force=yes
seqnumber=3
defineclientoptWINDOWSOPTinclexcl"exclude*:\*.*"force=yesseqnumber=4
defineclientoptWINDOWSOPTinclexcl"exclude*:\*"force=yesseqnumber=5
defineclientoptWINDOWSOPTinclexcl"include*:\navi\...\*.*"force=yes
seqnumber=16
defineclientoptWINDOWSOPTinclexcl"include*:\navi\...\*"force=yes
seqnumber=17
defineclientoptWINDOWSOPTinclexcl"include*:\manus\...\*"force=yes
seqnumber=18
defineclientoptWINDOWSOPTinclexcl"include*:\manus\...\*.*"force=yes
seqnumber=19
defineclientoptWINDOWSOPTinclexcl"include'*:\...\MyDocuments\*'"
force=yesseqnumber=20
defineclientoptWINDOWSOPTinclexcl"include'*:\...\MyDocuments\*.*'"
force=yesseqnumber=21
defineclientoptWINDOWSOPTinclexcl"include'*:\...\MyDocuments\...\*'"
force=yesseqnumber=22
defineclientoptWINDOWSOPTinclexcl"include'*:\...\My
Documents\...\*.*'"force=yesseqnumber=23
defineclientoptWINDOWSOPTinclexcl"include*:\...\Dokumenter\*"
force=yesseqnumber=24
defineclientoptWINDOWSOPTinclexcl"include*:\...\Dokumenter\*.*"
force=yesseqnumber=25
defineclientoptWINDOWSOPTinclexcl"include*:\...\Dokumenter\...\*"
force=yesseqnumber=26
defineclientoptWINDOWSOPTinclexcl"include*:\...\Dokumenter\...\*.*"
force=yesseqnumber=27
defineclientoptWINDOWSOPTinclexcl"include*:\...\Mail\...\*.*"
force=yesseqnumber=28
defineclientoptWINDOWSOPTinclexcl"include*:\...\Mail\...\*"force=yes
seqnumber=29
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\...\cache"force=yes
seqnumber=102
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\Windows"force=yes
seqnumber=103
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\ProgramFiles"
force=yesseqnumber=104
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\Programmer"force=yes
seqnumber=105
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\Temp"force=yes
seqnumber=106
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\SWSetup"force=yes
seqnumber=107
defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\Drivers"force=yes
seqnumber=108

defineclientoptWINDOWSOPTinclexcl"exclude.dir*:\IBMtools"force=yes
seqnumber=109
defineclientoptWINDOWSOPTinclexcl"exclude.dir'*:\...\MyVideos'"
force=yesseqnumber=110
defineclientoptWINDOWSOPTinclexcl"exclude.dir'*:\...\MyPictures'"
force=yesseqnumber=111
defineclientoptWINDOWSOPTinclexcl"exclude.dir'*:\...\MyMusic'"
force=yesseqnumber=112

Notice the double-quotes (") surrounding strings with embedded blanks, and the
single-quotes (') for substrings with blanks.
Associate Windows client nodes with this option set:
updatenode<NODENAME>cloptset=WINDOWSOPT

Making a client backup

Now the TSM server is ready for backups of registered TSM client nodes. The TSM
client software is installed as shown in TivoliStorageManager.

Server parameters and information

A number of parameters may be set or inquired with the TSM server.
TSM filespaces
Each backed up filesystem becomes a separate Filespace within the TSM server:
queryfilespace

Client storage utilization

The TSM server keeps track of how much TSM backup storage is used by each TSM
client in each filespace and in each TSM server storage pool:
queryoccupancy

The nodes' total storage utilization can also be checked by the TSM license system.
Update the TSM license information first and then query the storage utilization:
auditlicenses
queryauditoccupancy

To have a weekly update of this information, set up regular license auditing

schedules:

setlicenseauditperiod7

Server log
Set the number of days that the activity log is kept:
setactlogretention2

Immutable Page
DeleteCache (cached 2015-02-10 15:34:44)
Or try one of these
actions: AttachFile, Despam, LikePages, Load, LocalSiteMap, PackagePages, RenderAsDocboo
k, Save, SlideShow, SpellCheck, SubscribeUser, SyncPages

Tape Library Manager/Client Configuration for TSM

Library manager configuration:

Library client configuration:

1) Define a shared library.

9) Define the server that is the

library manager. Make sure to use
the "crossdefine=yes" option of the
DEFINE SERVER command.

2) Define the library path.

3) Define the drive(s).
4) Define the path for the drive(s).
5) Define device class.

10) Define a shared library using the

same name as the library defined on
the library manager. Specify the
library manager server name for
theprimarylibmanager option.

6) Check in your volumes into the library.

7) Define a storage pool.
8) Ensure that "crossdefine "is set on using the
"query status" command.
11) Define a path between the library client
server to each drive using the server definitions
that were created as a result of executing step
one of the library client configuration.

On Library Manager TSM Server:

12) Define the device class, making

sure to specify the shared library
name from step 10.
13) Define the storage pool.

1) Define library
Define library <library_name> libtype=scsi shared=yes
2) Define library path
Define path <library_name> <server_name> srctype=library
desstype=server device=/dev/lib0 online=yes
3) Define all drives
Define drive <library_name>
<drive_name> serial=autodetect element=autodetect online=yes
4) Define device class
Define devclass <devclassname> library=<library_name> devtype=
LTO /DISk/FILE
Format =drive
5) Ensure that "crossdefine "is set on using the "query status" command
SET CROSSDEFINE ON
Configuration on Library Client:
1) Define library
Define library <library_name>
libtype=shared primarylibmanager=<tsm_server_name of library
manager>
2) Define the server that is the library manager. Make sure to use the
"crossdefine=yes" option of the DEFINE SERVER command

SET CROSSDEFINE ON

3) Define devclass
Define devclass <devclassname> library=<library_name> devtype=
LTO /DISk/FILE
Format =drive

On both the servers (library manager and library client) tape and library
should be zoned /mapped.
Before Configuring Library Need to check Tape and library on Physical
Servers from below commands:

To check the status of Tape and Library Robot

lsdev Cc tape
lsdev -Cc library
To check the serial no and model of library/tape
Lscfg vpl rmt*
Lscfg vpl smc*

All About Tivoli

Storage Manager
TSM Day to Day Operation Commands

In tsm we are using following command to be used which has been shown below:

step1: To check the how many volumes in the library we have following command to be used:

syntax : q lib or q libvol f=d here q stand for query whereus libvol means library volume and
f=d means format is equal to details.

step2: To check the status of volume we have following command to be used : syntax -> q vol
volumename ie: q vol vln745

step3: How to check the backup status we have following command to be used : syntax -> q event
* * here first start * deals with domain name whereus second * deals with schedule name

step4: suppose i want to see my status of yesterday backup we have following command to be used
-> q event * * begind=-1

step5:I want to check how many bytes is transfered we have following command to be used -> q
actlog begind=-1 serach=anrcodenos node=node name

step 6: I want to know what are things happening in tsm server we have following command to be
used -> q actlog begind=-1

step 7: I want know how many drive is mounted we have following command to be used -> q mount

step 8 : I want know the status of drive we have following command to be used -> q drive or q drive
f=d

step 9: I want know how session are running and along with how many bytes transfering even the
server status is started we have following command to be used -> q session

step 10: How to fire the db backup in balic environment we have following command to be used ->
backup db deviceclass=tsmdb wait=yes type=full

step 11: How to checkin the volume we have following command to be used -> checkin libvol
3583lib search=bulk status=scratch waitt=0 checklabel=barcode

step 12: How to checkin the new tape in the library we have following command to be used -> label
libvol 3583lib volume waitt=0 status=scratch

step 13:How to checkout the volume in library we have following command to be used -> checkout
libvol 3583lib volume name

step 14:How to check my volume is readwrite state or unavailable or readonly state -> q vol volume
f=d

step 15: How to update the volume from readonly mode to readwrite mode we have following
command to be used -> update volume volumename access=readwrite

step 16 : How take the incremental backup in command line mode in tsm we have following
command to be used -> incremental c:\abc\*.* -subdir=yes

step 17 : How to take the selective backup or full backup in tsm we have following command to be
used -> selective "d:\abc\*.*" -subdir=yes

step 18: If it is archieve backup we have following command to be used -> archieve "d:\abc\*.*"
-subdir=yes

step 19 : How to restore the file if ur take the backup in the particular which you assigned we have
following command to be used -> restore "d:\abc\*.*" -subdir=yes

step 20 : How to retrieve the file if ur take the archieve in the particular which you assigned we
have following command to be used -> retrieve "f:\abc\*.* -subdir=yes

step 21 : How to redirect the file from tsmserver to ordinary local drive to your system we have
following command to be used -> q event *.* begind=-1 f=d >> d:\200912.txt

Email ThisBlogThis!Share to TwitterShare to FacebookShare to Pinterest

Home
Subscribe to: Posts (Atom)

Contributors
Chetan Sharma
Chetan Sharma
Pages
About TSM
TSM New Version Features
TSM Client-server Compatability
TSM BA Client Installation
TSM Basic troubleshooting

Configure a Tivoli Storage Manager Backup with MS Cluster

Configuring a Tivoli Storage Manager client for DB2
Migrate current TSM DB Volume and Log Volumes to new storage
Troubleshooting for Recovery Log pinned issue
TSM 5.5 Backup Workload Calculation
TSM Day to Day Operation Commands
Tape Library Manager/Client Configuration on TSM
TSM Concepts

Blog Archive

2013 (6)
May (6)

Upgradation Tivoli Storage Manager from 5.5 to 6.3...

About TSM

Troubleshooting for Recovery Log pinned issue

TSM 5.5 Backup workload calculations

TSM 6.2 workload Calculation

Tape Library Manager/Client Configuration for TSM

powered by

Google+ Followers

Which is better
backup enterprise
software?
Share It
Search This Blog

The Daily Puppy

Google+ Badge
Apple GoogleMicrosoft
Apple Watch 'particle
cloud' pairing method
likely revealed in new
patent
Apple Insider
Lost amidst a sea of
flashy hardware
technologies introduced
withApple Watch was a
new image-based
pairing technique
distinguished by a
"particle cloud" effect.
On
Tuesday, Applereceived
a patent detailing what
appears to be the
bedrock of this ...
Related Articles
Apple and Microsoft's
visions for the future
are delightfully
different
The Verge
Microsoft's evolution
over the past few years
has brought it closer
toApple than ever
before. Just like its old
nemesis, the Windows
company now sells its
own phones and
tablets, gives away OS
updates for free, and
runs a large network of
retail stores.
Related Articles
Yeah, the AppleWatch
ScratchesAll Stainless

Steel Watches Do
Wired
Apple Watch shipments
may have been delayed
until July, but those
who have received their
shiny, stainless steel
versions have already
taken to Twitter,
Instagram,
andApple forums to
show off some
scratches and scuffs.
Should a luxury item
you paid ...
Related Articles
The Next Apple TV
Could Get A TouchFriendly Remote
Redesign
TechCrunch
Apple's next AppleTV is
rumored to be breaking
cover in just a few
short weeks at the
annual Worldwide
Developers Conference
it hosts in San
Francisco, and said
device could also come
bundled with a
redesigned remote
control. The remote
redesign will ...
Related Articles
powered
by

Cheeky Quotes

Windows Live Messenger + Facebook

Make Top Rank Blog
Michael Jackson
Bandwidth Speed Test
World Clock
Daily Horoscopes
Travel template. Powered by Blogger.