Copy pools, (created with the "backup stg") are just "incremental" backups
of the primary storage pool.
When the data expires in the primary pool, it expires from the copy pool.
If someone wanted data from 6 months ago, your management classes had better
allow for it and if they do, the data would be found in the primary pool
(unless the media in the primary pool was trashed then you would use data in
the copy pool to "restore volume" to fix the messed up volume/media in the
primary pool...
Also, if you keep your copy pool onsite (in the same atl / available) and
you do have media crap out in the primary pool...if a user issues a restore,
tsm will roll straight to the data on the media under the copy pool...

hope this helps...
later,
Dwight

> ----------
> From:         Jim Coen[SMTP:coen AT WASHBURN DOT EDU]
> Reply To:     ADSM: Dist Stor Manager
> Sent:         Monday, July 17, 2000 4:34 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Copy Pool Question
>
>     Simple question . . . Is my thinking correct on this?
>
>     I want to take our backup data offsite at the end of each month.
>     Do I create a new copypool for *each* month, copy to that pool and
>     then take offsite--repeating the process at the end of each
>     month?
>
>     Also, if I do this, and someone wants to restore a file from six
>     months ago, am I able to retrieve that file from my copy pool
>     from six months ago?
>
>     Thanks in advance.
>
>     Jim Coen
>
>     Washburn University
>     coen AT washburn DOT edu
>