AFAIK, yes the domain, policy set has to be defined and active on the target
server otherwise it will default the node you are importing to "standard".

The storage pools don't have to be the same.  I am currently moving nodes
between servers and the target server has completely different storage pool
names.

You can always export the policy set(s) to the target server - just don't
forget to adjust the copygroups if the storagepool names are different and
you must activate them.

On Mon, Apr 25, 2011 at 12:02 PM, Ochs, Duane <Duane.Ochs AT qg DOT com> wrote:

> Good Day everyone,
> I have inherited an older AIX 5.2 server with TSM 5.3. It has been sitting
> for the last few years, due to litigation..
> The excess nodes and filespaces have been cleaned up and we are moving the
> data to an active 6.2 server.
>
> The old system has numerous domains defined and three mgmt classes per
> domain. I have redefined the mgmt classes on my establish 6.2 and each time
> I perform S2S export the data ends up using the default MGMT on my 6.2
> instance.
> I have performed numerous S2S exports in the past, but never with so many
> domains.
>
> Do I need to recreate each Domain to get this to work properly ?
>
> Thanks,
> Duane
>
>
> Duane Ochs
> Information Technologies - Unix,Storage and Retention
>
> Quad/Graphics
> Innovative People Redefining Printtec
> Sussex, Wisconsin
> 414-566-2375 phone
> 414-566-4010 pin# 2375 beeper
> Duane.Ochs AT qg DOT com
> www.QG.com<outbind://8/www.QG.com>
>
>
>
>
>
>
>
> Follow Quad/Graphics in social media<http://www.qg.com/socialmedia> <
> http://facebook.com/quadgraphics>  <
> http://www.youtube.com/user/QuadGraphicsVideos>  <
> http://linkedin.com/companies/8199>
>



--
Zoltan Forray
TSM Software & Hardware Administrator
Virginia Commonwealth University
UCC/Office of Technology Services
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details visit
http://infosecurity.vcu.edu/phishing.html