ADMS-L - DB2 backup

[Trimark, Jerry R]

Currently we are backing up daily, DB2 using TSM 6 DB2 API client LAN-Free to 
our TM 6 server/Virtual tape library.

Once a week I need to do a DB2 backup with a different retention. I am looking 
for options to this solution.

Here are some I have come up with, I am looking for other options.

* Copy dsm.sys file to dsm.sys.weekly. In the weekly file create a new 
node_name with the new retention. Weekly cp dsm.sys.weekly to dsm.sys. This way 
the database doesn't need to be stopped to read in a new dsm.opt file. Can you 
have 1 stg agent servicing 2 different TSM nodes on the same physical server? 
Or would you need to create 2 different stg agents?

* Weekly modify existing TSM stgpool (autocopy=client, 
copystgpool=weeklystgpool) perform the backup.  The copystgpool could be a VTL 
which could later be copied to physical tape or physical tape - writing 
directly would be an issue since we have fewer physical drives then virtual.  
Will the backupstgpool use multiple streams to copy data from the primary pool 
to the copystgpool if the DB2 backup is viewed by q occ in TSM as 1 filesystem 
(multiple streams are used to backup this environment to TSM)?

* Clone on storage array - requires offsite array for CLONE.

Thanks

ADSM-L - Sharepoint 2010 retention in TSM 6

[Trimark, Jerry R]

I looking for TSM 6 data retention configurations that people are using for 
their Sharepoint 2010 data.

We are performing Platform/Granular backups (Full) 1x week and incremental 
backups (every 6 hours) M-Sa.

I am trying to determine the retention setting in TSM 6 for the above backup 
schedule if I want to keep data 15 days and if the data is deleted it is kept 
for another 15 days.


Policy  Policy  MgmtCopyVersions   Versions Retain  
  Retain
Domain  Set NameClass   Group   Data   Data  Extra  
Only
NameNameName  ExistsDeleted   Versions  
 Version
-   -   -   -           
 ---
15DAY   15DAY   15DAY   STANDARD  15  0 15  
   0


Thanks