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:[EMAIL PROTECTED]]
Sent: Friday, 9 March 2001 13:11
To: [EMAIL PROTECTED]
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
[EMAIL PROTECTED]
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.
