Or rename node dude1 to dude2, and export dude2, register new dude1...
Nick Cassimatis
[EMAIL PROTECTED]
He who laughs last has a good backup.
"Stapleton, Mark"
<[EMAIL PROTECTED]
ERBEE.COM> To
Sent by: "ADSM: [EMAIL PROTECTED]
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:[EMAIL PROTECTED] 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
<<inline: graycol.gif>>
<<inline: pic03491.gif>>
<<inline: ecblank.gif>>
