Every business needs a way to keep working when its main server fails, is stolen, or its building loses power for days. A disaster recovery plan answers that question, and refurbished servers make the hardware side of it affordable. Instead of leaving a costly new server idle as a standby, you can use refurbished hardware for backup targets, standby hosts and recovery sites.
Where refurbished servers fit in a recovery plan
| Role | What it does | Why refurbished works |
|---|---|---|
| Backup target | Stores local backup copies for fast restores | Lots of drive bays and capacity for the money |
| Standby host | Runs replicas of key virtual machines, ready to start | Spends most of its life idle, so paying new prices is hard to justify |
| Secondary site server | Runs critical services at another location | Lets you build a second site on a smaller budget |
| Test and restore lab | Proves backups actually restore | Cheap hardware you can rebuild freely |
| Spare parts source | Matching spare server for quick part swaps | Same model as production, at a lower cost |

Plan around RTO and RPO
Two numbers drive every recovery design. The recovery time objective (RTO) is how long you can be down. The recovery point objective (RPO) is how much data you can afford to lose, measured in time.
| If you need… | Typical approach |
|---|---|
| RTO of days, RPO of 24 hours | Nightly backups to a local backup server, plus an off-site copy |
| RTO of hours, RPO of hours | Frequent backups and a standby host ready to restore onto |
| RTO of minutes, RPO of minutes | VM replication to a standby server or second site, with failover tested regularly |
Setting it up
- List critical systems and set an RTO and RPO for each.
- Choose backup or replication software that supports your hypervisor or servers.
- Size the standby or backup server for the workloads it must run during a disaster.
- Place the standby at a different location or in a different part of the building, on separate power.
- Write down the recovery steps so someone else can follow them.
- Test a full restore or failover at least once or twice a year.
For the full planning process, read our disaster recovery planning guide. For keeping services online across several servers, see high availability architectures.
Frequently asked questions
Can I use a refurbished server as a backup server?
Yes. Backup servers need capacity and reliability more than the latest CPU, which makes refurbished servers with many drive bays a good fit.
What is the difference between RTO and RPO?
RTO is how long you can afford to be down. RPO is how much recent data you can afford to lose.
Does a standby server need to match production?
It should be compatible and powerful enough to run the critical workloads, though it does not have to be identical. Matching models do make spare parts and failover simpler.
How often should I test disaster recovery?
At least once or twice a year, and after any major change to your systems.
Building a standby or backup server? Browse our storage servers or talk to our team about your recovery plan.


