Daniel,

        it makes a lot of sense!

And more, have you ever come across a HP High Availability software
MC/ServiceGuard? This software allows you to define packages that can be
assigned to specific nodes in a cluster. When, for any reason, you
move/transfer/migrate a package to a different node of the cluster, you
see all the VolumeGroups associated to that package move to the new nodes
and then see duplication of 'FileSpaces' without any relation with the
ones backed up on the other nodes! But they are the same file spaces! The
scenario become even more complicated because the migration may be
unattended when one of the nodes crashes (yep, it's High Availability).
The problem is that a package is NOT a virtual machine!

I'm still trying to find out the best solution with the tools ADSM gives
me, at the moment!

Ciao Mauro

> Hey Everyone,
>
> I don't know if this would ever be useful to anyone else, but, I
believe
> that it would be nice to be able to re-associate (bind or export)
filespaces
> to another adsm node.
>
> For example, for one reason or another, we use multiple nodes on one
> machine.  At times, changes are made, and we end up having to
completely
> backup the same filespaces that we already have on the previous node. I
also
> could've used such a tool in the past when I've migrated mount points
to new
> machines.
>
> Does this make any sense at all?
>
> Daniel Penrose
> J.D. Edwards & Company
> UNIX  Systems Administration
> One Technology Way
> Denver, CO. 80237
> (303)334-4747 DIRECT
> (303)334-1290 FAX
> daniel_penrose AT jdedwards DOT com