Don't forget to REMOVE ADMIN <nodename> before you DELETE NODE (if you
create admin IDs for your nodes).
 
--
Mark Stapleton (mark.stapleton AT cdw DOT com)
CDW Berbee
System engineer
7145 Boone Avenue North, Suite 140
Brooklyn Park MN 55428-1511
763-592-5963
www.berbee.com
 
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of Shawn Drew
> Sent: Monday, September 22, 2008 11:16 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [ADSM-L] Decommission Procedure
> 
> When a Node is decommissioned we typically
> - lock the node
> - remove it from the schedules
> - A script periodically checks for old file systems (Based on
> retention)
> and identifies file systems ready to be removed
> - We remove the expired filesystems (and the last active versions)
then
> remove the node
> 
> Mr Sims recently suggested changing the MAXNUMMP to 0 to allow
restores
> but not backups.
> 
> What are some other decommission procedures out there?   I'm trying to
> find the best way to do this so the decommissioned nodes will be
> obviously
> distinguishable from the active nodes.
> 
> Regards,
> Shawn
> ________________________________________________
> Shawn Drew
> 
> 
> This message and any attachments (the "message") is intended solely
for
> the addressees and is confidential. If you receive this message in
> error,
> please delete it and immediately notify the sender. Any use not in
> accord
> with its purpose, any dissemination or disclosure, either whole or
> partial,
> is prohibited except formal approval. The internet can not guarantee
> the
> integrity of this message. BNP PARIBAS (and its subsidiaries) shall
> (will)
> not therefore be liable for the message if modified. Please note that
> certain
> functions and services for BNP Paribas may be performed by BNP Paribas
> RCC, Inc.