In general, it sounds good to me.

On the reclaiming of the offsite storage pool, as I understand it, what
happens
is really a function that occurs in the data base.  And once a tape or two
get
under the lower limit you have set for reclaimation in that pool, another
tape
gets made, with data copies from the on-site copy (from tape or disk cache,
it really doesn't matter, as long as they are the same files), and the new
offsite
tape is written.  The offsite tapes that are being reclaimed will be marked
as
empty, so they can be moved back on-site as you send the new offsite tape
out.

Does that help?


> -----Original Message-----
> From: Joni Moyer [SMTP:joni.moyer AT HIGHMARK DOT COM]
> Sent: Wednesday, March 20, 2002 1:19 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Procedures for TSM
>
> I've been studying the TSM manual and changing administrative schedules by
> trial and error, but I just wanted to know if I have the order of
> procedures down right.
> 1. Backup disk to offsite tape pool
> 2. Backup onsite tape pool to offsite tape pool
> 3. Migration of the disk pools
> 4. Expire Inventory
> 5. Reclamation
> 6. Client Backups (run at night)
>
> I was also a little confused about reclamation on offsite storage pools.
> How can reclamation run on an offsite tape when it cannot be mounted on a
> tape drive?  (On a daily basis I have a job that marks tapes full and
> offsite so that they are ejected from the silo and taken to our offsite
> vault)  When I looked in the book it stated that reclamation for an
> offsite
> volume obtains the active files from either an onsite pool or offsite pool
> and then writes the files to a volume on the original copy pool.  I'm
> trying to understand this process, but it's not making much sense to me.
> Any explanations?
>
> Thanks!!!
>
> Joni Moyer
> Associate Systems Programmer
> joni.moyer AT highmark DOT com
> (717)975-8338