General overview of the server retirement process:

General overview of the server retirement process:
==> Database retirement if present
==> Middleware retirement if present
==> Any third party software or process retirement
==> Server retirement
==> Update Remedy of Server status (Assett record updated)
==> Backup of server retirement (stop backup of the server)
==> Security and monitoring tools retirement. [ E-health, eTrust (InfoSec), best1 )
==> Storage SAN of server recovery
==> Firewall rules of server retirement
==> Facility (datacenter:- Physical and Virtual servers) retirement/removal
==> DNS retirement/update of  server:  remove the hosts only from DNS Names, IP Addresses, and switchport assignments

========== Retirement process for Unix_Admin ==============

1. Before you shutting down the server, send email notification to all concern stakeholders.
Sub: CRQ00000000001 : Server retiring today 01/16/2014
Following servers listed below are retiring Today
Server1
server2
server3
Notify NOC, monitoging team that the server is no longer available and all

2. Change the status of the asset record that server is end of life (Possibly Remedy asset record)
You may want to open a ticket to asset management team to change the status.

3. Record following information
Change ticket #
hostname
Date
ip address
storage used on the system
Remove from Mornitoring tood
HW type
Add comment if any

4. On the retirement date, shut down the server into ok prompt/Single usermode or halt for linux servers.
Plan on keeping the server in this state for around 2 weeks for non-prod and 1 months for prod.