In this article
Justify each spare by the failure it addresses, its compatibility and the practical route back to a working host.
A GPU server spare parts reserve should list specific recovery needs: which component can interrupt operation, what confirms a replacement is compatible and how it will reach the machine. A percentage of the GPU purchase price can bound a discussion, but it does not explain what the team can restore.
For an owner considering external operation, the list also separates authorised maintenance from an unplanned upgrade to a different configuration.
Define the equipment boundary
Include the host, storage, power, cooling and network components relevant to the proposed task. A compatible power supply may matter more immediately than a spare accelerator if its failure stops the complete machine.
Record the exact component and supporting replacement guidance. NVIDIA’s DGX H100/H200 PSU procedure is specific to that system; it cannot be reused as a generic instruction for a workstation. Preserve compatibility evidence rather than relying only on a similar product name.
Build a decision table
| Item | What to confirm | Reason for considering a reserve | Decision before purchase |
|---|---|---|---|
| Power supply | Compatibility and connectors | Whole-host interruption | Approved replacement procedure |
| System SSD | Interface and recovery image | Loss of boot environment | Backup can be restored |
| Fan | Part and control compatibility | Cooling restriction | Suitable part is obtainable |
| Network card | Port, speed and driver | Remote access loss | Recovery access route |
These are illustrative categories, not a universal shopping list or failure-rate estimate. A spare on a shelf does not replace an authorised person and a safe service procedure.
Separate reserve from commitment
A budget line, ordered component, paid invoice and installed replacement have different states. Keep those states explicit so available funding is not confused with money already committed.
FinOps planning and estimating offers a useful approach: link future need to assumptions and evidence. For a physical host, record the price source, date checked and scenario for each item. The framework does not prescribe a mandatory reserve percentage.
Walk through one recovery scenario
Identify who detects the problem, gathers evidence, approves the replacement, reaches the site and checks readiness afterwards. Record whether neighbouring devices must stop. A supplier replacement process should not be treated as an instantly available local spare; approval and delivery are separate stages.
Continue with Compare Remote Hands Costs for Your GPU Server and A Change Register for GPU Drivers and Server Settings.