From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On 
Behalf Of Mike
>We have a few servers where the TSM GUI estimates nearly 3.5 
>days to restore all the files. We're talking now about getting 
>something like a JBOD as an additional copypool (is that the 
>right term?). The data flow would be node->storage pool->tape pool
>                                     ->JBOD copy pool.
>
>The JBOD copy pool would self-expire after 3 days (depending 
>on how much is actually stored to the JBOD.
>
>With the nightly backups copied to the JBOD, would this 
>help/speed up a catastrophic restore (catastrophic of the 
>node, not of TSM)?

Most likely not. When you perform a restore, the TSM server will look
for the desired client files in

        the disk pool (sometimes called the disk cache)
        the primary tape pool 

It will not restore files from the copy pool. (At least, I've never seen
it do so.) This list has talked about how to speed up restores. If
you're restoring from tape, your best bet is to use a collocated tape
pool, or run periodic MOVE NODEDATA commands on the primary tape pool.

I'm curious as to how you plan to "self-expire" the JBOD copy pool.
Remember that there will be as many files in the copy pool as there is
in the primary pool.

--
Mark Stapleton (stapleton AT berbee DOT com)
Berbee Information Networks
Office 262.521.5627