With my idea, you would export dude2, so you won't lose the inactive files.
Here's the order:

1.  Rename dude1 to dude2
2.  Register new dude1
3.  Export dude2

Nick Cassimatis
nickpc AT us.ibm DOT com

He who laughs last has a good backup.



                                                                       
             Alexander                                                 
             Lazarevich                                                
             <alazarev AT ITG DOT UIU                                          
To
             C.EDU>                    ADSM-L AT VM.MARIST DOT EDU            
             Sent by: "ADSM:                                            cc
             Dist Stor                                                 
             Manager"                                              Subject
             <[email protected]         Re: archive - inactive files?   
             .EDU>                                                     
                                                                       
                                                                       
             06/05/2004 11:30                                          
             AM                                                        
                                                                       
                                                                       
             Please respond to                                         
             "ADSM: Dist Stor                                          
                 Manager"                                              
                                                                       
                                                                       




I still can't get confirmation from the manual:

Does exporting a node preserve all the inactive (deleted) files?

Secondarily, if I rename dude1 to dude2, won't I lose all the deleted
files? I have to export dude1 to preserve the inactive files, assuming
export preserves those, right?

Thanks for the help,

Alex

On Fri, 4 Jun 2004, Nicholas Cassimatis wrote:

>
>
>
>
>
> Or rename node dude1 to dude2, and export dude2, register new dude1...
>
> Nick Cassimatis
> nickpc AT us.ibm DOT com
>
> He who laughs last has a good backup.
>
>
>
>
>              "Stapleton, Mark"
>              <mark.stapleton@B
>              ERBEE.COM>
To
>              Sent by: "ADSM:           ADSM-L AT VM.MARIST DOT EDU
>              Dist Stor
cc
>              Manager"
>              <[email protected]
Subject
>              .EDU>                     Re: archive - inactive files?
>
>
>              06/04/2004 07:49
>              PM
>
>
>              Please respond to
>              "ADSM: Dist Stor
>                  Manager"
>
>
>
>
>
>
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf 
> Of
> Nicholas Cassimatis
> >Unfortunately, that won't work to keep everything as it is now.  The
> >inactive files will expire per the rules established for them - after
> your
> >RetainExtra duration passes, you'll only have active files (except for
> the
> >Last Versions, retained per the  RetainLast setting).
> >
> >You can setup a new management class with all settings at 9999/no
> limit,
> >configure the client to use that for all files (new domain may work
> best)
> >run one last backup to rebind everything, then do the node rename.  I
> can't
> >think of an easier way to do what Alex is trying to accomplish.
>
> I can:
>
>         export node dude1 devc=<tape_device_class>
>
> The export will keep forever. dude1's data can be imported whenever it
> is needed.
>
> Oh, and name the new node dude2.
>
> --
> Mark Stapleton
>
>