The TSM server must use the settings of the archive copygroup associated 
with the management class with same name in new policy domain.
You should investigate why it shows "<unknown>". Output from your queries 
may sched some light what is going on.

Zlatko Krastev
IT Consultant






Markus Engelhard <Markus.Engelhard AT BUNDESBANK DOT DE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
13.10.2003 17:21
Please respond to "ADSM: Dist Stor Manager"

 
        To:     ADSM-L AT VM.MARIST DOT EDU
        cc: 
        Subject:        Moving archives between policy domains


Hi *sm ers,

I´m presently trying to consolidate 20 odd distributed TSM-Servers that
were indiviually managed and have very different logical setups. My aim is
to have identical policies across the country, so I thought having
standardized policy domains would be a good idea.
It´s quite straightforward for backups, so I´m not so worried about those.
But what !!!!!really!!!!! happens when a node with archived data is moved
to a new policy domain isn´t quite clear to me.
I used a TSM 5.1.5 Server on W2K and a 5.1 Client: an archived file will
show <unknown> for the Management-class after an "update node" moving it
from one policy-domain to another, althougt the management class with the
matching archive copy group was defined in both domains. The default
management class doesn´t apply either. So it would only be the grace 
period
that stops data expiring with the next "expire inventory", but even that
does´nt seem to apply: I changed grace period to one day and did an 
expire,
but the archive is still there.
Does anyone have a comprehensive description what happens when moving
archives this way or has even gone through this himself? I´m not quite 
sure
I understand the implications decribed in the QuickFacts and IBM support
didn´t manage to give a convincing explanation yet.
I can´t afford to loose archive data (a real no-go!) and I hate not 
knowing
what is up, so any help will be welcome.

Thanks,

Markus