You have to create mgmt classes. If their copy group points to another
(existing) stgpool the imported data will go to that pool. But the classes
must exist.

Zlatko Krastev
IT Consultant




Please respond to "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
Sent by:        "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
To:     ADSM-L AT VM.MARIST DOT EDU
cc:

Subject:        import node problems

I'm trying to import a node to 4.1.2.0 server on Solaris 2.6 -
It's an archive only export of a node on another system.

The import fails, and terminates the session of the admin trying to
import.

I have tracked this tidbit down:

One of the management classes in the domain where the node was exported
referenced a destination pool named "ARCHIVEPOOL".

That pool no longer exists on the source server, nor on the target server.

Provided that is the cause of the failure, is there any way to import the
node without haveing to create the pool and management classes, etc first?