Hi Christopher,

As far as I am aware there is no way to do what you are asking other than
keeping *all* versions of a file on disk.

The only tool that you have to hold data in a primary storagepool is the
migdelay parameter, and this is does not differentiate between active and
inactive data.  It would be nice if it did.

Regards

Steve.

Steve Harris
"Resting" in Brisbane, Australia


----- Original Message -----
From: "PEEK, CHRISTOPHER" <cpeek AT HCSO.TAMPA.FL DOT US>
To: <ADSM-L AT VM.MARIST DOT EDU>
Sent: Wednesday, May 11, 2005 1:38 AM
Subject: [ADSM-L] Keeping Disk Copies of Files - Storage Pool Cache or ????


I am trying to implement a backup process where a complete set of file
copies are kept on disk in addition to tape.  Our current process is a
very traditional basic setup with backups going to a single disk storage
pool that then migrates to tape during the day.  After the migration
completes, the process then makes multiple tape copies for offsite and
onsite vault storage.

I have the following questions:
1) What is the best process to keep a disk based version of the most
recent file copy?

2) Is it enabling the cache for the disk storage pool and increasing the
storage pool size to hold the copies; or is it better to go with a disk
to tape (d2t)/disk to disk to tape (dd2t) dedicated device?

3) Is anyone using the storage pool cache?  What is the size of the
storage pool and how has performance been impacted?





Just for reference, here are the details of our TSM environment.

Current TSM Server OS: AIX 5.1 ML 07
Current TSM Server Ver: 5.2.2.14
Disk Storage: DS4400 (FastT 700) SAN - Fibre Channel
Tape Storage: 3583-L72 with 3 LTO2 fibre drives