ADSM-L

Re: [ADSM-L] Decommission Procedure

2008-09-23 07:49:54
Subject: Re: [ADSM-L] Decommission Procedure
From: goc <gooooc AT GMAIL DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 23 Sep 2008 13:47:59 +0200
... and i make a phone call and regardless of the answer i delete everything :-)

On Tue, Sep 23, 2008 at 1:13 PM, Richard Rhodes
<rrhodes AT firstenergycorp DOT com> wrote:
> We . . . .
> - remove the association
> - rename the node from <node> to zzrt_<node>
> - in the Contacts we put the date it was retired, and the date it to be
> deleted
>
> Once a month we go through the retired nodes and delete those that are
> eligible.
>
> Rick
>
>
>
>
>
>             Shawn Drew
>             <shawn.drew@AMERI
>             CAS.BNPPARIBAS.CO                                          To
>             M>                        ADSM-L AT VM.MARIST DOT EDU
>             Sent by: "ADSM:                                            cc
>             Dist Stor
>             Manager"                                              Subject
>             <[email protected]         Decommission Procedure
>             .EDU>
>
>
>             09/22/2008 12:17
>             PM
>
>
>             Please respond to
>             "ADSM: Dist Stor
>                 Manager"
>             <[email protected]
>                   .EDU>
>
>
>
>
>
>
> 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.
>
>
>
> -----------------------------------------
> The information contained in this message is intended only for the
> personal and confidential use of the recipient(s) named above. If
> the reader of this message is not the intended recipient or an
> agent responsible for delivering it to the intended recipient, you
> are hereby notified that you have received this document in error
> and that any review, dissemination, distribution, or copying of
> this message is strictly prohibited. If you have received this
> communication in error, please notify us immediately, and delete
> the original message.
>



--

Murray Walker  - "And now, excuse me while I interrupt myself."