How Refurbished Servers Can Play a Role in Disaster Recovery Plans

Disaster Recovery

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.

Quick answer: refurbished servers are a cost-effective choice for backup servers, standby virtualisation hosts and secondary recovery sites, because these machines often sit mostly idle until a disaster. Pair them with tested backups, replication and a written recovery plan.

Where refurbished servers fit in a recovery plan

RoleWhat it doesWhy refurbished works
Backup targetStores local backup copies for fast restoresLots of drive bays and capacity for the money
Standby hostRuns replicas of key virtual machines, ready to startSpends most of its life idle, so paying new prices is hard to justify
Secondary site serverRuns critical services at another locationLets you build a second site on a smaller budget
Test and restore labProves backups actually restoreCheap hardware you can rebuild freely
Spare parts sourceMatching spare server for quick part swapsSame model as production, at a lower cost
disaster recovery plan

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 hoursNightly backups to a local backup server, plus an off-site copy
RTO of hours, RPO of hoursFrequent backups and a standby host ready to restore onto
RTO of minutes, RPO of minutesVM replication to a standby server or second site, with failover tested regularly
Pro tip: follow the 3-2-1 backup rule: three copies of your data, on two different types of storage, with one copy off site. A refurbished backup server on site plus a cloud or second-site copy covers it.

Setting it up

  1. List critical systems and set an RTO and RPO for each.
  2. Choose backup or replication software that supports your hypervisor or servers.
  3. Size the standby or backup server for the workloads it must run during a disaster.
  4. Place the standby at a different location or in a different part of the building, on separate power.
  5. Write down the recovery steps so someone else can follow them.
  6. Test a full restore or failover at least once or twice a year.
Watch out: a backup you have never restored is a guess, not a plan. Test restores regularly, including restoring a complete server, not just single files.
Good to know: load shedding is a recovery scenario in itself. Put production and standby servers on UPS power, and configure them to shut down cleanly before the batteries run out.

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.

Server Site