Chavdar,

Thanks. There is something to win there, maybe. We could abandon the
current OS nodename and create a seperate for archives. I could then rename
the node in TSM to 'Archivenode' and the filespaces belonging to that node
as well. How about this: I have 'Node1' with archives and 'Node2' with
archives. I could rename 'Node1' as 'Archivenode', but not 'Node2' as well.
Is there still a way to move the archives on 'Node2' to 'Archivenode'
without export/import?

Cheers,

Rick

On Tue, Jul 17, 2012 at 2:22 PM, Chavdar Cholev <chavdar.cholev AT gmail DOT 
com>wrote:

> Hi
> You can use rename node & rename files space commands to do the job
>
> On Tue, Jul 17, 2012 at 1:55 PM, Rick Harderwijk
> <rick.harderwijk AT gmail DOT com> wrote:
> > Hi,
> >
> > In cleaning up old domains and nodes, we have 'found' some nodes that
> have
> > archives bound to it. We do wish to part with the old nodes, but not with
> > the archives. Is there any low impact method to rebind the archive data
> to
> > a new node? I've been reading up on export node / import node, but it
> > appears that would take quite some time and resources to accomplish this.
> > Is there any way to make this easier on the admins and the system?
> >
> > Many thanks for your input,
> >
> > Rick
>