Sorry, I did not state that our primary pools reside on the VTLs.  New matching 
pools will be created on the new VTL and the new data directed to the new 
pools.  At that time the data in the old pools will be moved (various methods) 
to the new pools.  None of the pools will be consolidated and split.


Andy Huebner


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Richard Sims
Sent: Friday, July 09, 2010 11:34 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Copy Pool question

Andy -

Your scenario is vague as to exactly what you are doing, so difficult to 
answer.  Obviously, you don't do Backup Stgpool against a VTL: you do it with a 
primary storage pool.  We don't know whether the primary or copy is being 
migrated, or how, or if another incarnation is being created.

The guiding principles are that copy storage pools know nothing about each 
other's contents, and that the TSM database keeps track of whether a given 
primary object has such a copy in one or more copy storage pools.  Certainly, 
if you start with a fresh copy storage pool, a Backup Stgpool to it will be a 
"full" copy, without regard to any operations to pre-existing copy pools.

    Richard Sims

This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.

Thank you.