TSM Database space can be estimated by: 1) Number of Client files to be stored a) Number of versions for Backup, Archive

and Space - managed files 2) Method by which sever manages them a)Each cached file, copy storage pool file, active-data pool file b)Overhead space(Extra space - close to 50% space) TSM Recovery Log Space: It depends on the amount of client activity with the server. - Active Log Space: Min of 2GB and default of 2GB - Active Mirror Log Space: same as active log space(2GB) - Archive Log Space: If you perform a full backup of the database every day, the archive log must be large enough to hold the log files for client activity that occurs over two days . Typically 600 - 4000 bytes of log space are used when an object is stored in the server. Therefore you can estimate a starting size for the archive log using the following calculation: objects stored per day x 3000 bytes per object x 2 days It is important to maintain adequate space for the archive log directory. If the drive or file system where the archive log directory is located becomes full and there is no archive failover log directory, the data remains in the active log directory. This condition can cause the active log to fill up, which causes the server to stop. - Archive failover log space: The archive failover log is used by the server if the archive log directory ru ns out of space. Location/State Status Mountable FULL Not Mountable EMPTY Vault Vault Retreive Courier Retrieve Onsite checkin libvol 3494libj2 K00234 devtype=3592 status=pri checkl=no checkout libvol 3494libj2 K00234 rem=yes checkl=no recl stg Oracle_drcopy th=80 dur=600 move media <vol name> stg=* wherestatus=FULL remove=yes OVFLO=SHLEF (Moving Tape s from library to shelf) move media <vol name> stg=* wherestate=mountalen checkl=no upd vol <Vol name> access=reado