q sess

To see currently working sessions

can sess ( sess no) To cancel a session q eve domainname schedulename To see schedule time,nodename, scgedule name and progress of the scheeduled backup. ( q eve * * to see all scheduled backups) q proc To see currently running background processes

cancel process (process no) q node

To cancel a process

To view assigned nodes in a Tivoli server

q filespace To check backup space utilized for each file system of a server, filesystem type... q actlog To view activity log

q act begind=mm/dd/yyyy begint=hh:mm:ss endd=mm/dd/yyyy endt=hh:mm:ss To view activity log for a specified period by begining date and end date

q act begind=today-1 begint=00:00

To view activity log from yesterday 12:00 am

q act search=transferred begint=00:00 from 12:00 am

To see all completed backup size of servers

q act search=nodename q drive f=d q library f=d q libvol q vol q req

To view activity log for a node

To get detailed report of drive, it's status ... To get detailed information about tape library

To see volumes in the tape library and it's status

To see volumes and it's storage pool name, capacity, status To see requests

reply (request no) To continue request q sched To show schedule name domain, action , start date & time

q sched f=d To show detailed report about schedules including schedule backup path UPDATE LIBVOLUME TS3200 L41117L4 STATUS=SCRATCH volume ( L41117L4 ) status to scratch from private To change a library

update node nodename "admin" domain=domainname forcepwreset=Yes change a tivoli login password of a node define vol storagepoolname L41116L4

To

Add new tape L41116L4 to a storagepool

delete volume L41116L4 discarddata=yes L41116L4

To delete data inside a tape media

To create a new schedule backup (incremental ) for a node UPDATE SCHEDULE domainname nodename desc="daily incremental backup for a server" action=Incremental options=-subdir=yes objects=""/fs1/*" "/fs2/*" "/home/user1/*"" priority=5startdate=mm/dd/yyyy starttime=hh:mm duration=1 duru=Houperiod=1 perunits=Day dayofweek=Any expiration=never

To start tivoli services in an AIX client #cd /usr/tivoli/tsm/client/ba/bin nohup dsmc sched & To start scheduled backup service

nohup dsmcad & To start BA client ( webmode backup i.e. http://ip.address.of.server>:1581) #cd /usr/tivoli/tsm/StorageAgent/bin nohup ./dsmsta & SAN to Tape library ) #ps -ef | grep dsm To start storage agent ( LANFREE BACKUP= backup directly from

To view currently running Tivoli services in server

To update drive status of a server to online update path sourceservername TAPE0 srct=server destt=drive libr=ts3200 online=yes To set serial number of a drive in tape library UPDATE DRIVE TS3200 TAPE0 ELEMENT=autodetect ONLINE=Yes WWN="2002000E11107B6C" SERIAL=autodetect

To detect label of a tape in tape library

label libvol t3200 checkin=scratch labelsource=barcode search=bulk waittime=0

To remove tape media from tape library checkout libvol ts3200 VOLLIST=A00015L3,A00019L3 CHECKLABEL=YES REMOVE=YES

To add and label new tapes into library LABEL libvol TS3200 search=yes labelsource=barcode overwrite=NO checkin=SCRATCH WAITTIME=0

To take full backup of Tivoli database manually to a file in local disk backup db dev=FILECLASS type=full

to assign a tape drive to a server ======================= UPDATE PATH servername TAPE0 SRCTYPE=SERVER DESTTYPE=DRIVE LIBRARY=TS3200 DEVICE=\\.\Tape0 ONLINE=YES AUTODETECT=no Important If you are not able to take backup through any of Tivoli backup methods ( BA client, dsmc , schedule ) then check any NFS mounted filesystems are there in the server and that server is available or not. If that server is not powered on, either unmount the NFS filesyatem or make that server available...

POLICY DOMAIN - This is a container for policy and scheduling info *BACKRETention* is a fallback value for any files which have been backed up under the specified policy domain, but for which there is now a lack of an active policy set. *ARCHRETention* is a fallback value for any files which have been archived under the specified policy domain, but for which there is now a lack of an active policy set. POLICY SET - This is a set of management classes within a POLICY DOMAIN.Only the active version has any effect. The active version is created by issuing ACTIVATE POLICYSET . After activating, you may edit the original set without affecting the active copy. MANAGEMENT CLASS - This is a classification for particular sets of objects. Minimal set to be bound is an entire archive for archiving (ARCHMC option) or a single file, directory, filespace or everything for a backup (INCLUDE option). There can be many management classes per policy set, but only ones in the active policy set may be referenced **The additional parameters for this structure are used only for HSM migration. BACKUP COPYGROUP - This is the structure which defines retention of backup data. These settings are the most confusing because their operation overlaps and may require some to be set to "NOLIMIT" to attain the desired effect. VERSIONS DATA EXISTS - This value specifies the maximum number of versions of a file which may be retained. If this is exceeded by additional backups or imports, then the next expiration run on the server will remove the oldest versions until there are only this many left. **This may be "NOLIMIT" or a whole number. RETAIN EXTRA VERSIONS - This value specifies the maximum number of days to retain an inactive copy when there is an active copy in the database. **This may be "NOLIMIT" or a whole number. RETAIN ONLY VERSION - This value specifies the maximum number of days to retain the only inactive version of a file once there are no active versions.

**This may be "NOLIMIT" or a while number.

**This does not affect active copies which are always retained. VERSIONS DATA DELETED - This is the maximum number of inactive versions of a file to retain once the file no longer has an active version. DESTINATION - This specifies the storage pool to which newly backed up data will go if it is bound to this management class during backup. **Rebound data will not move to a new pool automatically. **Data may be moved from this pool through migration or MOVE DATA commands. Archive Copygroup - This is the structure which defines retention of archive data. RETAIN VERSION - This is the only retention parameter for archives, and is the number of days that the entire archive will be kept. DESTINATION - This specifies the storage pool to which newly archived data will go if it is bound to this management class during archive operation.

**Rebound data will not move to a new pool automatically. **Data may be moved from this pool through migration or MOVE DATA commands. Schedule - This is a time/date/frequency setting for when commands may be automatically run by the tsm server either on the tsm server (administrative) or on the tsm client (client). Client Association - a separate entity that binds clients to schedules. Node - A separate entity which defines a client and allows access.

CAVEATS NOTE: Once an archive is made, it may not be rebound. In otherwords, you may not specify a different management class for it. It IS possible to change the copygroup retention period for this management class, and then re-activate the policyset. This will change it's retention; however, be cautious with this, as you will affect ANY data in the same management class. NOTE: Management classes with the same name but which are within a different policy domain will NOT conflict with eachother.

NOTE: Changes to a policy set will NOT have ANY effect unless that policy set is copied into the active policy set with ACTIVATE POLICYSET. Only the active policyset, and not it's source policyset or any other, will have an effect. NOTE: Active versions are converted to inactive only by the client, through clientside expiration. See the particular client code manual for details. This may happen during a backup with an exclude list, or during a backup with missing files, or through an API call to expire the object. NOTE: There are other parameters for all of these structures. Please see the ADSM/TSM Administrator's Reference Guide for details.

EXAMPLE Backup copygroup is set as follows: VDE = 3 VDD = 1 RETEX = 100 RETO = 1

Explaination: - Versions 1 through three are kept up to 100 days FROM WHEN THEY WERE BACKED UP. - Any versions past 3 will be expired immediately upon the next server-side EXPIRE INVENTORY process. - NOTE: NO MORE THAN THREE VERSIONS WILL BE KEPT AFTER EXPIRE INVENTORY, REGARDLESS OF THE NUMBER OF DAYS SPECIFIED IN RETAIN-EXTRA AND RETAIN-ONLY! - If the active version is made inactive (client side expiration), then only the most recent copy will be kept, and it will only be kept for one day FROM WHEN IT WAS BACKED UP.

EXAMPLE Backup copygroup is set as follows: VDE = NOLIMIT VDD = NOLIMIT RETEX = 14

RETO = 20

Explaination: - All versions will be kept for 14 days FROM WHEN THEY ARE BACKED UP. - When no active version remains (client-side expiration), the last inactive version will be kept for 20 days FROM WHEN BACKED UP. EXAMPLE Backup copygroup is set as follows: VDE = 5 VDD = 0 RETEX = NOLIMIT RETO = NOLIMIT

Explaination: - 5 versions will be kept while an active copy exists. - Files will not expire by age. - When the active version is made inactive, the next EXPIRE INVENTORY will remove ALL versions of the file.