Server Decommissioning Checklist: 7 Steps, Physical & Cloud

Open Source & Linux · Cloud & Infrastructure · ~13 min read

Switching a server on takes an afternoon. Switching one off properly takes about three weeks, touches a dozen systems and is where most infrastructure documentation quietly goes wrong. We collected the questions readers send us most about retiring servers — physical and cloud — and put them to Puffin Notes editor Owen Calder.

Q&A WITH OWEN CALDER · NOVEMBER 2026 · CHECKLIST INCLUDED

$ cat summary.txt

7

Phases between “we don’t need this box” and a closed change record

2–3 wks

Typical end-to-end time to back up, remove and replace a server

14+

Systems that usually hold a reference to any given server

$118/mo

What a “deleted” AWS server can keep costing through leftovers (our calculation)

// part one · before you touch anything

The decision, the paperwork and the backup

Q01

Why does something as simple as switching off a server need a whole process?

OC

Because it isn’t one action, it’s a chain — and every link is somewhere a different team keeps records. The server is in your monitoring, your backups, your DNS, your firewall rules, your config management, probably three wikis and at least one spreadsheet someone made in 2019. Powering it down only changes one of those. Everything else now describes a machine that doesn’t exist.

The informal version — someone who knows the box shuts it down, a colleague helps carry it out, the docs get updated “later” — works right up until it doesn’t. Then you get a monitoring alert for a host nobody can find, a restore from a backup that turns out to be six months old, or a new server handed an IP address that an old cron job is still trying to reach.

IT provider Extech Cloud puts the realistic timeline at two to three weeks to back up, remove and replace a server. That matches my experience. Most of that time isn’t work; it’s waiting to be sure.

Q02

What’s the very first step?

OC

Paperwork, and I mean that seriously. Before anything is powered down, get written approval from the application owner — the one person who can say with authority that nothing important still runs there — and open a change record that says which server, why, when, and who approved it. Six months later, when an auditor asks where a device went, that record is your answer. Microsoft’s guidance on decommissioning source workloads after a migration makes the same point: stakeholder sign-off, reclaimed licences and archived data come before anything is switched off.

Then write down the server’s side jobs. The headline application is never the whole story. Old servers pick up roles over the years: a log forwarder, a backup client, a local DNS cache, a monitoring exporter, the cron job that rotates someone else’s certificates. Each one either moves or gets switched off deliberately — otherwise you find out when a dashboard goes dark.

~/decom/discover.sh — what is this box actually doing?
# who is talking to it right now?
$ ss -tunap | grep ESTAB

# scheduled work, for every user
$ for u in $(cut -d: -f1 /etc/passwd); do crontab -l -u "$u" 2>/dev/null; done
$ systemctl list-timers --all

# what is listening, and who logged in lately
$ ss -tlnp
$ last -n 50
Q03

How do I know my backup is good enough?

OC

You restore it. That’s the whole answer, and it’s the step almost everyone skips. A decommissioning backup that captured the app directory but not the database, or the data but not the encryption keys, is worse than useless — it gives you confidence you haven’t earned.

Three rules. Restore it on a different machine. Store it somewhere that survives the server — not a share on the box you’re about to wipe. And write the retention period and owner into the change record, so the data gets deleted deliberately when its time is up instead of lingering forever.

$ cat timeline.txt

What three weeks actually looks like

1 · approve & scope
days 1–3
2 · back up & restore
days 3–6
3 · deregister
days 6–8
4 · shut down & observe
days 8–15 · scream test
5 · erase media
15–16
6 · remove hardware
16–17
7 · reconcile & settle
days 17–24 · close record
day 1week 1week 2week 3day 24

Puffin Notes model for a single physical server with one main application. Active work is a few days; most of the calendar is observation, which is the point. A cloud instance skips phases 5 and 6 but not the rest.

// part two · cutting the strings

Deregister first. Shut down second.

Q04

Where do references to a server actually live?

OC

More places than anyone remembers. This is the list I work through. If you only take one table from this post, take this one.

Table 1 — Everything that knows your server exists
SystemWhat to remove or changeIf you forget
DNSA, AAAA, CNAME and PTR recordsNames resolve to an IP that may be reassigned
DHCP / IPAMReservations; release or re-reserve addressesAddress conflicts when the IP is reused
Monitoring & alertingHosts, checks, dashboardsAlerts for a ghost — and a team that learns to ignore alerts
Backup schedulesJobs and agentsNightly failures that hide real failures
Config managementInventory entries (Ansible, Puppet, Salt)Playbooks that fail or time out on every run
Firewall & security groupsRules referencing its IPsOpen paths to an address someone else may get
Load balancer poolsBackend membersHealth checks failing, traffic routed to nothing
Directory (AD / LDAP)Machine and service accountsLive credentials for a machine that’s gone
TLS certificatesRevoke and recordA valid credential that outlives the host
SSH trustKeys in other hosts’ authorized_keys, known_hostsOld keys that still open doors elsewhere
CI/CD deploy targetsInventories and pipeline variablesFailed deploys, or deploys to a recycled IP
LicencesRelease seats and keysPaying for software on a dead machine
CMDB / asset registerStatus to “retired” with disposal detailsAn inventory nobody trusts
Runbooks & wikisMark retired, point to the replacement3 a.m. instructions for a server that isn’t there

Puffin Notes list, building on the deregistration steps in Obelinf’s server decommissioning checklist.

Q05

What’s a scream test, and is it a real thing?

OC

Very real, slightly unprofessional name. You power the server off — but leave it racked, wired and intact — for a fixed observation window, and you wait to see who screams. Any unexpected alert, failed job or confused colleague in that window is a dependency you missed in step four. Finding it while you can still press the power button is cheap. Finding it after the drives have been wiped is not.

I use a week as a minimum, because it catches every daily job and most weekly ones. If the server ran anything monthly — billing exports, reports, certificate renewals — either extend the window past the next run or trigger that job manually while the server is off. Use the window for the cleanup that was too risky while the machine was live: disable its service accounts, remove the machine from the domain, revoke its certificates.

“A decommissioning that reaches the physical phase with every prior step verified is a process, and a process can be audited. One that reaches it on trust is a hope.”— André Ribeiro, The Complete Server Decommissioning Checklist, Obelinf

// part three · making the data actually go away

Wipe it before it leaves the building

Q06

Isn’t deleting the partitions enough?

OC

No. Deleting partitions or reformatting removes the map, not the data — anyone with free recovery tools can read most of it back. Once a drive leaves your premises for recycling, resale or a vendor return, you’ve lost control of what’s on it, so erasure happens while the server is still yours, and gets verified and written down.

The right method depends on the media. The widely used reference here is NIST’s media sanitisation guidance (SP 800-88), which sorts methods into three levels: clear, purge and destroy. The important nuance is that SSDs and spinning disks behave very differently.

Table 2 — Erasure by media type
MediaRecommended methodLinux toolingWatch out for
Spinning disk (HDD)Full overwrite, or ATA Secure Erase; shred if not reusedshred, hdparmSlow on large disks — budget hours, not minutes
SATA SSDFirmware secure erase or cryptographic erasehdparm –security-eraseOverwriting is unreliable on SSDs because of wear levelling
NVMe SSDFormat with secure erase, or sanitizenvme format, nvme sanitizeCheck the drive supports the mode you choose
Self-encrypting driveCryptographic erase (destroy the key)vendor or sedutil toolsOnly as good as the drive’s implementation
Drives behind a RAID controllerErase via the controller, or pass drives through firstcontroller CLIThe OS may not see the physical disks at all
Firmware & management controllerFactory-reset BMC/iLO/iDRAC, clear BIOS, remove USB/SD boot mediaipmitool, vendor UICached passwords and network config survive disk wipes

Summary based on NIST SP 800-88 categories. Commands erase data irreversibly — double-check the device name before you press enter.

~/decom/erase.sh — examples only, read before running
# confirm which device is which, twice
$ lsblk -o NAME,SIZE,MODEL,SERIAL

# NVMe: user-data erase (1) or cryptographic erase (2)
$ sudo nvme format /dev/nvme0n1 --ses=1

# HDD: one random pass, then zeros
$ sudo shred -v -n 1 -z /dev/sdb

# verify: this should print nothing but zeros
$ sudo head -c 1M /dev/sdb | hexdump -C | head

Then record the method, the date, the drive serial numbers and who did it in the asset register. That line is what makes your disposal defensible in an audit. If you use a certified disposal vendor, keep their certificate with the record.

// part four · the cloud version

You can’t unrack a VM. You can still get it wrong.

Q07

Isn’t decommissioning a cloud server just clicking “terminate”?

OC

That’s exactly the problem. Terminate removes the instance and leaves its surroundings behind: detached volumes, snapshots, the elastic IP, the load balancer that only existed for it, the NAT gateway in a subnet nothing uses any more. None of them make noise. All of them keep billing.

I priced a fairly typical leftover set on AWS at public list prices. The server itself is gone. The bill isn’t.

monthly cost of leftovers after an instance is terminated (AWS us-east-1, list prices)

500 GB gp3 volume
$40.00
NAT gateway (idle)
$32.85
500 GB snapshots
$25.00
Application load balancer
$16.43
Elastic IPv4 address
$3.65
Total, every month
$117.93

Our calculation at published us-east-1 list prices: gp3 $0.08/GB-month, snapshots $0.05/GB-month, NAT gateway $0.045/hour, ALB $0.0225/hour (before capacity units), public IPv4 $0.005/hour, 730 hours a month. That’s about $1,415 a year for a server that no longer exists — multiply by every half-finished cleanup in your account.

Q08

So what’s the cloud checklist?

OC

Everything in part one and two still applies — approval, backup, deregistration, scream test. Stopping an instance is the cloud’s version of leaving it racked but powered off. Then, before you call it done:

Table 3 — Physical vs cloud decommissioning
StepPhysical serverCloud instance
“Off but recoverable”Powered down, still rackedStopped (storage still billed)
Data erasureYour job, on premisesDelete volumes and snapshots; the provider handles media
Network identityRelease IPs in IPAM, clean switch portsRelease elastic IPs, delete unused ENIs
Surrounding infrastructureCables, PDUs, rack unitsLoad balancers, NAT gateways, security groups
The hidden costPower, cooling, rack spaceOrphaned resources billing silently
Proof it’s doneDisposal certificate, asset registerEmpty resource list for its tags; cost report showing zero

The single most useful habit: tag everything with the service it belongs to when you create it. Then “what’s left of this server?” becomes one filtered query instead of an afternoon of clicking.

~/decom/leftovers.sh — find what terminate left behind
# volumes not attached to anything
$ aws ec2 describe-volumes --filters Name=status,Values=available

# elastic IPs with no association
$ aws ec2 describe-addresses --query "Addresses[?AssociationId==null]"

# everything still carrying the old service tag
$ aws resourcegroupstaggingapi get-resources --tag-filters Key=service,Values=legacy-api

$ git commit -m

“A deliberate retirement leaves a trail of closed tickets. An accidental disappearance leaves a trail of confusion.”

— Owen Calder

// part five · after it’s gone

The step everyone skips

Q09

The hardware’s gone. Are we done?

OC

Almost, and this is where most teams stop one step short. Reconciling the documentation — IPAM, VLANs, topology diagrams, the CMDB, runbooks, disaster recovery plans — is the longest and least visible part of the job, which is exactly why it gets deferred forever. Make it a checklist item with a date, not an intention.

When you pull a server, also note what you found that the documentation didn’t mention: the extra network card, the second power supply, the label that doesn’t match the hostname. Those discrepancies are the best free audit you’ll ever get of how accurate the rest of your records are.

Finally, don’t close the change record the day the hardware leaves. Give it a settling week, check that nothing surfaced, then close it with a summary: what was done, where the backup lives and for how long, and where the hardware went.

Q10

What’s the one mistake you see most often?

OC

Releasing the IP address too early. Someone frees it in IPAM the day the server goes off, a new machine picks it up a week later, and suddenly an old firewall rule, a forgotten cron job or a monitoring check is pointed at a completely different server. Sometimes that’s merely confusing. Sometimes it’s a security hole. Hold the address until the record is closed.

$ cat decommission.md

The full checklist

decommission.md — copy into your change ticket
## 1 · approve
  • Written sign-off from app owner
  • Change record opened
  • Side jobs listed and reassigned
  • BMC credentials located
## 2 · back up
  • Data, DB, config and keys captured
  • Restore tested on another machine
  • Retention and owner recorded
## 3 · deregister
  • DNS, DHCP, monitoring, backups
  • Config mgmt, LB pools, CI targets
  • Firewall rules reviewed
## 4 · shut down
  • Off in a maintenance window
  • 7+ day scream test passed
  • Accounts disabled, certs revoked
## 5–6 · erase & remove
  • Drives erased and verified
  • BMC and BIOS reset
  • Cables, rack units, disposal recorded
## 7 · reconcile
  • IPAM, CMDB, diagrams, runbooks updated
  • IPs released only now
  • Settling week passed, record closed

$ man decommission

Quick answers

How long does decommissioning a server take?

Around two to three weeks end to end for a typical server, though the hands-on work is only a few days. Most of the time is the observation window and the final settling period.

What’s the difference between decommissioning and disposal?

Decommissioning removes a server from service and from your records. Disposal is what happens to the hardware afterwards — reuse, resale, recycling or destruction. Disposal should only start once the drives are verifiably erased.

How long should I keep the final backup?

As long as your legal, contractual or compliance obligations require for that data — and no longer. Write the date into the change record so the deletion is deliberate.

Is formatting a drive enough before recycling?

No. Use a secure erase or cryptographic erase for SSDs, a full overwrite or secure erase for spinning disks, and verify the result. Physical destruction is the fallback.

What is a scream test?

Switching a server off, but leaving it intact, for a fixed period to see whether anything breaks. It reveals dependencies you missed while the change is still easy to undo.

What do cloud servers leave behind?

Most often unattached volumes, snapshots, elastic IPs, load balancers and NAT gateways. Terminating the instance doesn’t delete them, and they keep billing.

Sources: André Ribeiro, “The Complete Server Decommissioning Checklist”, Obelinf, August 2026; Extech Cloud, “Everything you need to know about server decommissioning”; NIST SP 800-88 media sanitisation categories; AWS published list prices for the leftovers calculation, which is our own and illustrative. Commands are examples — test them somewhere safe first.

Contact Us

We'd love to hear from you