Hi there,

Could someone share their experience & knowledge on what would be the
best way to implement this type of backup enviroment with TSM ?

Situation : 
1. unfortunately backups need to be weekly based (full on Sunday,
incremental till next Sunday). There is no way of changing that.
2. there are 2 types of physical storage : disk pool and tape pool LTO
library (LTO1 type tapes, 19(+1 cleaning) slots, single drive)
3. Each week the tapes will be taken offsite
4. data needs to be on both medias - disk and tape to ensure the
possibility of restore in case of library or disk storage failure (disk
media has enough space to store the backups of 2 weeks).

What would be the best way to do this ? I can simply create two storage
pools : diskpool and tapepool, set up tape as copy pool for disk pool. 
My idea would be:
1. create diskpool, create tapepool (as copy pool for diskpool).
2. create schedules : a.) Sunday - selective backup, b.) weekdays -
incremental, c.) saturday - incremental.

How should expiration be setup ? I only need data for current, and
previous week. However, backups are mostly files generated by databases.
Therefore to restore any backup, the full backup of the Sunday is still
needed. So depending on a weekday I need files from 8 to 14 days old
(current week, and previous week).

With tape rotation it's possible to store more data on tapepool (just in
case) than diskpool. Is it possible expire older data on diskpool but
still have it available via tapepool ? Can this be done without the
backup client doing a double job : a.) Backuping to disk b.) backuping
to tape

Or is it better to backup files to diskpool, and then backup diskpool to
tapepool ? How would this work if disk storage failed ? As I understand
- I cannot restore files directly from a stgpool backup, I have to
restore the stgpool or volumes, and only then can I restore the files ?
Is it like this or am I missing something.

Maybe such weekly/periodic backup scenarios/solutions for TSM have been
documented and explained ? Since this backup implementation does not
follow tivoli's recommendations I haven't found usefull info in their
documentation on this subject.

Thank you for your time.
mailto:viny AT parkas DOT lt