I'll take a shot at this.
When you move a client from one domain to another:

1) No data moves.  Even if the backup copy groups in the new domain point to
different storage pools, the existing backup data stays right where it is
(and is still perfectly restore-able).  If you want to move the data, you
have to issue the appropriate MOVE DATA or MOVE NODEDATA commands to make
that happen.

2) If the new domain has management classes with the SAME NAMES as the old
domain, the data will be governed by verexist/verdeleted/retextra/retonly
values in the new domain.

3) If there are management classes in the old domain that DO NOT EXIST in
the new domain, the data is governed by the "backup retehtion grace period "
value for the DOMAIN.

Also in this case some ugly messes crop up.  When expiration runs, you will
see a LOT of funky error messages about backup copy groups not existing for
file xxxxxxxxxx, which essentially says that there is no management class.

Wanda Prather
"I/O, I/O, It's all about I/O"  -(me)


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Hammersley
Sent: Tuesday, September 14, 2004 10:14 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: effect of moving a client from one policy domain to another


I've been asked to revamp our policy domains/policy sets/management
classes/copy groups.  They want new ones of everything.  The goal is to
group clients in different ways and have different values for the
version and retention attributes.

After I move a client from the old policy domain to the new and change
its schedule association what will happen to the data that was backed up
?  Will TSM treat it as "deleted files" and use the "versions data
deleted" and "retail only verstion" attributes to expire the files ?  Or
not and keep the active files ?  Or something else ?

Thanks.

Richard Hammersley
Xavier University