Hi Charles,

Why don't you use "move data" command to move all data from old primary
pools to the new ones ? Off course if your pools are not collocated,
you'll be embarrasted for moving only the data from specific nodes, but
this could be bypassed by building an intermediary collocated pool where
you do a first move, and then only moving volumes corresponding to your
specific nodes to the new pool (or use move nodedata if you're under
version 5) ...
My 2 cents ...

Arnaud 

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
| Arnaud Brion, Panalpina Management Ltd., IT Group     |
| Viaduktstrasse 42, P.O. Box, 4002 Basel - Switzerland |
| Phone: +41 61 226 19 78 / Fax: +41 61 226 17 01       | 
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=



-----Original Message-----
From: Hart, Charles [mailto:charles.hart AT MEDTRONIC DOT COM] 
Sent: Wednesday, 05 February, 2003 20:46
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Binding Backup Data to new Mgmt Class


We have created a new domain, policy set, mngt classes and Stgpools for
existing Backup Clients to be a part of a domain that consists of backup
clients that are tested at an off-site DR Facility.  We did an upd node
to the existing nodes to the new dom and the backups are going to the
new stgpools.  There is still data in the stgpools that these systems
use to back up to.  

We are wondering how can we get all the preexisting data to the new
storage pools so that when a restore takes place it only looks at the
new stgpools that the clients have been backing up to.  We looked at
export node (TSM Serv 4.1.5) but do not remember the existing domain and
storage pools that the systems use to be on as this change was many
weeks ago. .  If we were to set the new copy groups to do an "Absolute"
backup would a restore go to the new stgpool or the old?  

Any ideas would be great!!!

Thanks!!!!