Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Decommission\s+Procedure\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Decommission\s+Procedure\s*$/: 10 ]

Total 10 documents matching your query.

1. [ADSM-L] Decommission Procedure (score: 1): Author: Shawn Drew <shawn.drew AT AMERICAS.BNPPARIBAS DOT COM>; Date: Mon, 22 Sep 2008 12:16:23 -0400; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00182.html (12,508 bytes)
2. Re: [ADSM-L] Decommission Procedure (score: 1): Author: "Bell, Charles (Chip)" <Chip.Bell AT BHSALA DOT COM>; Date: Mon, 22 Sep 2008 11:22:05 -0500; I rename them to 'OLD-nodename', and rename them back if necessary (i.e., for restore). I kill/disable any services that they had that once talked to the TSM server. That's probably too simple, but y; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00183.html (13,649 bytes)
3. Re: [ADSM-L] Decommission Procedure (score: 1): Author: Mark Stapleton <Mark.Stapleton AT CDW DOT COM>; Date: Mon, 22 Sep 2008 11:22:57 -0500; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00184.html (13,678 bytes)
4. Re: [ADSM-L] Decommission Procedure (score: 1): Author: "Allen S. Rout" <asr AT UFL DOT EDU>; Date: Mon, 22 Sep 2008 13:15:40 -0400; It'll do it itself. - Allen S. Rout; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00185.html (11,590 bytes)
5. Re: [ADSM-L] Decommission Procedure (score: 1): Author: Sergio Fuentes <sfuentes AT UMD DOT EDU>; Date: Mon, 22 Sep 2008 23:28:19 -0400; I create inactive/expired node schedules and associate decommissioned nodes to that schedule until they're ready for filespace removal and node removal. The schedule name should imply the node's stat; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00187.html (13,465 bytes)
6. Re: [ADSM-L] Decommission Procedure (score: 1): Author: Richard Rhodes <rrhodes AT FIRSTENERGYCORP DOT COM>; Date: Tue, 23 Sep 2008 07:13:07 -0400; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00189.html (14,188 bytes)
7. Re: [ADSM-L] Decommission Procedure (score: 1): Author: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>; Date: Tue, 23 Sep 2008 13:47:10 +0200; We...... - remove the association - rename the node from <node> to z<date_to_be_deleted_<node> Daily checks include checking for node names with expired date in the name. Regards, Karel We . . . . -; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00191.html (14,866 bytes)
8. Re: [ADSM-L] Decommission Procedure (score: 1): Author: goc <gooooc AT GMAIL DOT COM>; Date: Tue, 23 Sep 2008 13:47:59 +0200; ... and i make a phone call and regardless of the answer i delete everything :-) -- Murray Walker - "And now, excuse me while I interrupt myself."; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00192.html (15,431 bytes)
9. Re: [ADSM-L] Decommission Procedure (score: 1): Author: Timothy Hughes <Timothy.Hughes AT OIT.STATE.NJ DOT US>; Date: Tue, 23 Sep 2008 11:23:19 -0400; We - remove the association - in the Contacts we put the date it was retired, and the date it's backup is to be deleted tim ... and i make a phone call and regardless of the answer i delete everythin; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00199.html (14,995 bytes)
10. Re: [ADSM-L] Decommission Procedure (score: 1): Author: "Schneider, John" <John.Schneider AT MERCY DOT NET>; Date: Tue, 23 Sep 2008 11:33:13 -0500; Greetings, We do a couple things that no one else has mentioned: 1) We move the client to a special policy domain called DECOM. This policy domain is set to 90, 90, 90, 90, mode=absolute. The reason; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2008-09/msg00200.html (18,400 bytes)

Current List: 1 - 10
Page: [1]