shawn,
as far as I understand your question, the only thing you want to do is to remove
data that you don`t use.
So, why don`t you remove the filespaces within the TSM Server ? After the
deleting is done by the server, you can remove the node .
Regards
HBit
Bitte antworten an "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
An: ADSM-L AT VM.MARIST DOT EDU
Kopie: (Blindkopie: Holger Bitterlich/BK/SK-Koeln)
Thema: 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
______________________________________________________________________
Da E-Mails leicht unter fremdem Namen erstellt oder manipuliert werden
koennen, muessen wir zu Ihrem und unserem Schutz die rechtliche
Verbindlichkeit der vorstehenden Erklaerungen ausschliessen. Die fuer die
Stadtsparkasse Koeln geltenden Regeln ueber die Verbindlichkeit von
rechtsgeschaeftlichen Erklaerungen mit verpflichtendem Inhalt bleiben
unberuehrt.
|