thats what we used to do, but manually.
So you have a script that periodically checks
for nodes that havent backed up in 3 months,
then automatically removes the filespaces? then the node?

Or are you saying that you peridically check for
nodes ready to be deleted, then the script does the rest?

shawn


___________________________________________________________
Shawn Drew
Tivoli IT - ADSM/TSM Systems Administrator
shawndo AT tivoli DOT com


Joe Faracchio <brother AT socrates.Berkeley DOT EDU>@VM.MARIST.EDU> on 
03/08/2001
09:42:14 PM

Please respond to Joe Faracchio <joef AT socrates.Berkeley 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:  Re: Manually "inactivate" NT files



that's what we do: 3 months and then delete filespace
but we have it as a perl program that runs overnight
because it takes a lot of time and cycles.
Come to think of it that's the worse time!!!
I need to change it from 3 am to 8 pm !!!

.. joe.f.

Joseph A Faracchio,  Systems Programmer, UC Berkeley


On Fri, 9 Mar 2001, Stephen Mackereth wrote:

> Hi Shawn,
>
> Why don't you leave it alone for some period of time
> like 3 months (if you not short on space) and then
> delete the filespaces & the node permanently.
>
> This depends on
> 1. how the backup copygroup is defined.
> 2. how long after the client has gone, are you required to restore
anything.
>
> q filesp {node_name}
>
> del filesp {node_name} {filespace_name from above command}
>
> rem node {node_name}
>
>  Regards
>
>  Stephen Mackereth
>  Senior UNIX Consultant / Senior Storage Administrator (TSM)
>  ITS Unix Systems Support
>  Coles Myer Ltd.
>
> -----Original Message-----
> From: Shawn Drew [mailto:Shawn_Drew AT TIVOLI DOT COM]
> Sent: Friday, 9 March 2001 13:11
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Manually "inactivate" NT files
>
>
> I wanted to get an idea of what people do when
> clients are taken offline permanently.
>
> Ideally, we would run the backup client one last time excluding
everything
> (so the files will follow the Management Class setting for Inactive
files)
>
> However, we are commonly told a client is offline after the fact.  So we
> cannot
> run the client one last time.
> On unix, it seems (although I haven't done this yet) that is would just
be
> a matter
> of reconfiguring my workstation to "imitate" the removed node, and
running
> an incremental (with exlusion settings) and it will expire everything.
>
> On NT however, the filesspace name is named after the UNC name
> (i.e \\ntserver\c$)  So when I reconfigure my workstation, it creates a
new
> filespace
> with my workstations unc name.
>
> I see 2 ways to possibly solve this (both of which are a little
cumbersome
> and ugly
>
> - rename my workstation to the name of the removed node
> - rename the filespace on the server to fit my unc name
>
> Is there any server command or any other way to do this?
>
>
>
> shawn
>
>
> ___________________________________________________________
> Shawn Drew
> Tivoli IT - ADSM/TSM Systems Administrator
> shawndo AT tivoli DOT com
>
> This email and any attachments may contain privileged and
> confidential information and are intended for the named
> addressee only.  If you have received this e-mail in error,
> please notify the sender and delete this e-mail immediately.
> Any confidentiality, privilege or copyright is not waived or
> lost because this e-mail has been sent to you in error.  It
> is your responsibility to check this e-mail and any
> attachments for viruses.
>