tsm basics(v5.5)
Tivoli Storage Manager Server – In
a traditional LAN configuration, the role of a Tivoli Storage Manager server is
to store the backup or archive data from the backup-archive clients that it
supports to storage media. It also has a database of information to keep track
of the data it manages, including policy management objects, users and
administrators, and client nodes.
Tivoli Storage Manager
Server refers to an instance, not a physical instance. You can have multiple
instances of the server on the same system.
Scheduler – Administrator-defined
schedules allow for the automation of Tivoli Storage Manager Server and
backup-archive client operations. A comprehensive and integrated set of
schedules can provide the basis for efficient data management with little need
for intervention during normal operations.
Scheduling Tivoli Storage
Manager backup-archive client operations consists of schedules on the Tivoli
Storage Manager server and a scheduler component that runs on the Tivoli
Storage Manager Client machine.
Backup-Archive Client – The TSM
backup-archive client is a service which sends data to, and retrieves data
from, a TSM server. The TSM backup-archive client must be installed on every
machine that needs to transfer data to server-managed storage called storage
pools. The TSM server uses a unique node name to identify each TSM
backup-archive client instance. A password can be used to authenticate
communications between the TSM backup-archive client and server. Data can be
recovered to the same client machine that initially transferred it or to
another client with a compatible file system format if that client has provided
permission.
Policy-Based Management – Business
policy is used to centrally manage backup-archive client data. Policies are
created by the administrator and stored in the database on the server.
Storage Rules, Based on the Business Requirements
Tape Library – A
tape library is essentially a box that holds drives and cartridges, and
provides automation for tape operation.
Important
Components of TSM Server
- TSM Database
- Recovery Log
- Administrative Scheduler
- Storage Pools
- Policy Management
- Tape Library
Important
Components of B/A Client
- B/A Client
- B/A Client Scheduler
Important
Files TSM Server
- dsmserv.dsk
- volhist.out
- devcnfg.out
- dsmserv.opt
- initserv.log
Important
Files baclient
- dsm.opt
- dsmsched.log
- dsmerror.log
- dsm.exe
- dsmc.exe
Important License Files:
- tsmbasic.lic
- tsmee.lic
- dataret.lic
- System
Privilege All TSM Server Task
- Storage
Privilege Database, Recovery Log,
Storage pool Management
- Operator
Privilege Server Availability, Resource
Usage, Physical Media Mgmt
- Policy
Privilege Policy Domain, Policy Set, Mgmt Class, Copy Group, Schedule
- Analyst
Privilege Review and Reset Server statistics
- Node
Privilege Client actions, Product Usage , Activity
Monitoring
Start the administrative
command line at the operating system prompt. The paths may vary, but the
default paths are as follows:
Windows: Program Files >> Tivoli >>
TSM >> Server
AIX: /usr/Tivoli/tsm/server/bin
Linux:
/opt/Tivoli/tsm/server/bin
To start the administrative command line,
type: dsmadmc
Backup/Archive Client Command Line:
Start the backup-archive
client command line at the operating system prompt. The paths may vary, but the
default paths are as follows:
Windows: Program
Files >> Tivoli >> TSM >> baclient
AIX: /usr/Tivoli/tsm/client/ba/bin
Linux: /opt/Tivoli/tsm/client/ba/bin
To start the backup-archive client command
line, type: dsmc
TSM Database
TSM Database contains the information about the files
which are backed up or archived from each and every client. That means it
contains the information about file name, file size, file path and location of
the file within the storage pools. TSM Database also contains information that is needed for server operations such as Authentication
for the TSM Administrators and Clients, Policy rules that applies to
client file system, Admin schedules and Client Schedules.
Estimating Space Requirements for TSM Database
- 1 KB of database space per copy
Or
- 3% to 5% of total amount of data to be backed up
i.e. 10 GB*53No’s=530 GB
20 GB*26No’s=530 GB
Commands for DB
ü Define
dbvol volume_name Formatsize=format_size
ü Ex: Define
dbvol D:\TSMDB\db2.dsm f=20
ü Extend DB size_in_mb
ü Ex: Extend
DB 20
ü Reduce DB size_in_mb
ü Ex: Reduce
DB 20
ü Query DB f=d
Command
for Defining Database Copy or Mirroring
Database
ü Define dbcopy primary_copy mirror_copy Formatsize=size_in_mb
Ex: def dbc D:\db1copy.dsm E:\db1coptmir.dsm
f=12
Backup
TSM Database
TSM
Database Backup Types
- Full Backup
- Incremental Backup
- Database Out-of-Band(Snapshot Backup) or DB Snapshot Backup
Full backup when the following occurs:
- Database has never been backed up.
- Maximum incremental backups reached. i.e. 32 Incremental Backups
- Database has been extended or reduced.
- Recovery log mode changed to Roll-Forward (default = normal).
ü Backup DB devclass=devclassname Type=Incremental|Full|DBSnapshot
Volumenames=volname(s) Scratch=Yes|No Wait=Yes|No
Ex:Backup
DB devclass=ltoclass Scratch=yes/no Type=Incr
ü Whenever
a TSM database backup will be happened all the transactions or entries present
in the Recovery Log will be committed or updated to the TSM Database hence it
will reduce the percentage utilized of Recovery Log.
ü To
decrease or reduce percentage utilized in TSM DB & Recovery Log backup
should be perform.
ü In
Real Time Recovery Log Percentage Utilized will be 0%.
ü If
Recovery Log Percentage utilized will reach to its maximum i.e.100% user cannot
logged into TSM Server.
ü To
Automate DB backups Triggers can be used
Triggers
Types
of Triggers
- Space Triggers Used if Log Mode is Normal and Roll-Forward Mode
- DBBackup Triggers Used if Log Mode in Roll-Forward Mode only
Space
Triggers
Space Triggers defines
settings for triggers that determine when and how Tivoli Storage Manager
prepares additional space when predetermined thresholds have been exceeded in
the database and recovery logs.
Command
for Defining Space Trigger
ü Define spacetrigger DB/LOG/STG fullpct=percent
spaceexpansion=percent
expansionprefix=path mirrorprefixes=“path1,path2“ max=size_in_mb
ü Ex:Define
spacetrigger db fullpct=80 spaceexpansion=20 expansionprefix=c:\tsmserver\
mirrorprefixes=“f:\mirvol1\,g:\mirvol2\“ max=10000
Command
for Defining DBBackupTrigger
ü Define
DBBackuptrigger devclass=device_class_name logfullpct=percent imcredevclass=device_class_name numincremental=number mininterval=minutes minlogfreepct=percent
ü Ex: Define DBBackuptrigger devclass=ltoclass
logfullpct=50 numincremental=6
mininterval=0 minlogfreepct=0
Restoring
TSM Database
Types
of Restoring TSM Database
- Point-in-time(Normal) Recovery
- Roll-forward to most recent state Recovery
- Single database volume Recovery
Point-in-Time (Normal) Recovery
Pros:
o
Smaller
size for recovery log.
o No auditing of the database is required after
the restore.
Cons:
o
Cannot
restore to most recent state.
o
Single
database volume cannot be restored.
o
Auditing
of storage pools is required after a database restore
Roll-Forward Recovery
Pros:
o
Database
can be restored to most recent state.
o No auditing of the database or storage pools
is required after the restore.
o
Single
database volume can be restored.
Cons:
o
Larger
recovery logs.
o
Mirrored
recovery log consumes additional disk space
Command
for restoring a database to its most current state:
ü
DSMSERV
RESTORE DB PREVIEW=No|Yes
Command for restoring a single database volume to its most current state:
ü DSMSERV RESTORE DB DBVolume=volname PREVIEW=No|Yes
Command for restoring a database to a specific point in time; history file available:
ü
DSMSERV
RESTORE DB TODate=date TOTime=time Source=DBBackup|DBSnapshot PREVIEW=No|Yes
Command
for restoring a database to a specific
point in time; history file unavailable:
ü
DSMSERV
RESTORE DB devclass=devclassname volumename=volname COMMIT=No|Yes
Ex:
dsmserv restore db devclass=ltoclass volume=A100L2 commit=No
ü
While restoring database first take latest version of Full DB volume with
Commit=No
ü
Commit the DB for the last or latest volume with
the option Commit=Yes
Real Time
1. What is the Command to Set Buffer Pool
Size?
A).
Cmd: Setopt
BUFPOOLSIZE 262144
Note: It should
be mentioned in KB. Recommended maximum value is 1 GB
2. What is the Size of DATABASE in your
environment?
A).
110 GB - 6.5 TB to 7.4 TB
Recovery Log
The
recovery log contains information about database updates that have not yet been
committed. Updates can include activities such as defining a management class,
backing up a client file, and registering a client node. Changes to the
database are recorded in the recovery log to maintain a consistent database
image
Commands for Recovery Log
ü Define
logvol volume_name Formatsize=format_size
ü Ex: Define
logvol D:\TSMLOG\log2.vol f=20
ü Extend LOG size_in_mb
ü Ex: Extend
LOG 20
ü Reduce LOG size_in_mb
ü Ex: Reduce
LOG 20
ü Query Log
Recovery
Log
- Default Size
8Mb
- Max Size 13GB
- Recommended Size
10GB
- Predominately write-oriented.
Estimating Space Requirements for
Recovery Log
- 1 KB of recovery log
space x daily number of transactions.
Or
- 5% to 10% of total
database size for normal mode
And
- 10% to 15% of total
database size for roll-forward mode.
ü Do not spread recovery log i.e. do not divide more volumes
or files max is 13
i.e. 1 GB*13No’s=13 GB
3
GB*4No’s=12 GB
Defining Recovery Log or Mirroring
Recovery Log
ü Define logcopy primary_copy mirror_copy Formatsize=size_in_mb
Ex: def logcopy D:\log1copy.dsm
E:\log1coptmir.dsm f=12
Types of
Log Modes
- Normal Mode
- Log
space in normal mode is managed as a circular array of blocks.
- Out
of log space causes in-flight transactions to abort.
- Log
space is freed when transactions commit or abort
- For
every Transaction tail will be moved along with Head
- Roll-Forward Mode
- For
every Transaction Head will be
moved and tail is fixed
To
Secure or Protect TSM Server
- Use automatic backup triggers.
- Use space triggers.
- Use recovery log mirroring.
- Store backup volumes off-site.
- Store backup of DEVCNFG.OUT, VOLHIST.OUT, DSMSERV.OPT and DSMSERV.DSK off-site.
- Complement with database mirroring for 24 x 7 environments (operate 24 hours a day, 7 days a week).
- Define volume history and device class backup files.
- Back up the database using administrator scheduling facility.
- Schedule database backup immediately following storage pool backup.
- Use Disaster Recovery Manager to automate the recovery of the TSM database.
For Storage pools:
- Create a copy storage pool.
- Do a backup of the primary storage pools to the copy storage pool.
Do the following daily:
- Do a backup of the primary storage pools to copy storage pools.
- Back up the database.
- Save the volume history file, the device configuration file, and the output of the QUERY SYSTEM command.
- Move storage pool volumes, database backup, volume history file, and the device configuration file off-site
Tivoli Storage Manager Maintenance
Plans
Processes
can be scripted to:
- Back up the primary
storage pools.
- Back up the server
database.
- Update a basic disaster
recovery plan.
- Migrate stored data
from primary storage pools to the next level storage pools.
- Remove expired data
from server storage.
- Reclaim fragmented
tapes by consolidating active data.
Daily Administration Cycle
Copy storage pool:
- Sequential only.
- Multiple primary pools
can use one copy pool.
- Back up each primary
storage pool hierarchy to same copy pool (Best Practice).
- Is independent of
client backups.
- Retains file level
granularity.
- Is an incremental
backup of files.
Initiate backup:
- Manually with command
or Administration Center.
- Automatically with
administrative command scheduling.
- Once per primary pool.
Client Configuration Files:
- Windows
•
dsm.opt
- AIX
•
dsm.opt
•
dsm,sys
Configure Client Access to the Server/
Options to set in the dsm.opt File
- NodeName
- TCPServeraddress
- COMMMethod
- TCPPORT
Client Options
- Options defined on the
server with server-enforced client options. The server overrides client
values with FORCE=YES.
- Options entered locally
on the command line.
- Options defined on the
server for a schedule using the options parameters.
- Options entered locally
in the options file.
- Options received from
the server with client options not enforced by the server. The server does
not override client values, when FORCE=NO is used.
- Default option values.
Type
of Backups
- Progressive or
Incremental Backup
- Complete
- Date Only
- Without Journal
- Selective Backup
- (Always Backup)
- Image Backup
- Logical Volume Backup
- Subfile Backup
- NAS Filesystem Backup
- Backup Sets
Policies enable data management based
on business requirements identifying the following:
- Data to back up
- Data to archive
- Where to store the data
- Retention period
- Number of versions to retain
Important Parameters in Copy Group
- DESTination=poolname –
Specifies the name of the primary storage pool where backup data is to be
stored.
- VERExists=verevalue –
Specifies the maximum number of backup versions to retain for current
files.
- RETExtra=retevalue –
Specifies how many days Tivoli Storage Manager retains a backup version
after that version becomes inactive.
- VERDeleted=verdvalue –
Specifies the maximum number of backup versions to retain for files that
are deleted from the client file system.
- RETOnly=retovalue –
Specifies the retention time, in days, for the last backup version of a
file that has been deleted or has expired from the client's file system.
Default
Server Policies
BACKRETention=30
ARCHRETention=365
TSM in the STANDARD Domain Default
Policy Settings
Backup Archive
Type
= Backup Type
= Archive
DESTination
= Backuppool DESTination
= Archivepool
FREQuency
= 0 FREQuency
= Cmd
MODE
= MODified MODE
= ABSolute
SERialization
= SHRSTatic SERialization
= SHRSTatic
VERExists
= 2
VERDeleted
= 1
RETExtra
= 30
RETOnly
= 60
Expire
Inventory
- Default Value 24Hrs (1 day)
- Max Value 336Hrs (14 days)
- To Remove Expire set value to 0
Storage pools are collections of like media
that provide storage for backed up, archived, and migrated files.
Command for Defining Device Class
ü Define devclass devclass_name devtype=type_of_device
ü Ex: Define devclass Diskclass
devtype=DISK
ü Ex: Def devc autodlt_class devt=dlt
format=drive library=autodltlib
ü Ex:
Define devclass ltotape devtype=lto
library=ltolib format=ultrium mountlimit=12 mountretention=5 prefix=adsm estcapacity=100G
Good one..
ReplyDelete