Bare Metal Recovery (BMR): Techniques and Best Practices

Bare metal recovery rebuilds a server's OS, apps, settings and data onto blank hardware. Learn BMR techniques, steps and ransomware risks.

Content

    What is bare metal recovery?

    Bare metal recovery (BMR) is a restore technique that rebuilds a complete system, including the operating system, drivers, applications, configuration and data, onto a machine with no software installed. BMR uses an image-level backup instead of individual files, so the rebuilt server boots in the same state it was in when the backup was taken. Teams use it after hardware failure, disk corruption or a ransomware attack that leaves a server unusable.

    Key Takeaways

    • Whole system, one restore. BMR avoids reinstalling the OS and apps by hand before restoring data.
    • Hardware differences matter. Restoring to different hardware (dissimilar restore) needs driver injection or a hardware-independent image.
    • It can bring malware back. An image taken after an attacker got in restores the attacker's foothold too.
    • Virtual and cloud targets are faster. Many teams now restore to a VM or cloud instance instead of waiting for replacement hardware.

    How bare metal recovery works

    1. Capture an image backup. The backup includes boot volumes, system state, partitions and data.
    2. Boot recovery media. The blank machine starts from a recovery ISO, USB drive or network boot (PXE).
    3. Prepare disks. The recovery tool recreates partitions to match the original layout.
    4. Restore the image. The OS, applications and data are written back to disk.
    5. Adjust for hardware. Drivers for new storage and network controllers are added if the hardware changed.
    6. Reboot and validate. The system boots, rejoins the network and is checked against its expected state.

    Bare metal recovery techniques compared

    Technique

    When to use it

    Trade-off

    Same-hardware BMR

    Disk failure on a server that is otherwise fine

    Requires identical or repaired hardware

    Dissimilar hardware BMR

    Original server is gone or obsolete

    Driver and firmware issues can stall boot

    Physical-to-virtual (P2V)

    Fastest route back online when hardware is not available

    Needs a hypervisor with spare capacity

    Restore to cloud

    Site-wide outage or ransomware recovery

    Network, licensing and IP changes need planning

    Bare metal recovery best practices

    • Keep images off the network. Store BMR images in immutable, isolated storage so ransomware cannot encrypt them.
    • Update recovery media. Rebuild boot media after OS upgrades and driver changes.
    • Document hardware dependencies. Record RAID controllers, NIC models and firmware versions for each critical server.
    • Scan images before restore. After a cyberattack, check images for malware and pick a restore point from before the intrusion.
    • Time your drills. Measure how long a full BMR takes for each server class, and compare it to your recovery time objective.

    How Druva helps with server and system recovery

    Druva protects data center and hybrid workloads, including VMware, Hyper-V and Nutanix, in the air-gapped, immutable Druva Resilience Cloud.

    • Restore without waiting for hardware. Cloud disaster recovery brings protected workloads back in the cloud when on-premises infrastructure is down.
    • Avoid restoring the attacker. Accelerated Recovery & Response helps identify clean recovery points before a full system restore.

    Get servers back without rebuilding by hand. Book a Demo or read the Recovery Orange Book.

    FAQs

    Q. What is the difference between bare metal recovery and file-level restore? 

    A. File-level restore brings back individual files to a working system. Bare metal recovery rebuilds the whole system, including the OS and applications, onto blank hardware.

    Q. Can you do bare metal recovery to different hardware? 

    A. Yes, through dissimilar hardware restore. The recovery tool injects drivers for the new storage and network controllers so the restored OS can boot.

    Q. Is bare metal recovery safe after ransomware? 

    A. Only if the image predates the intrusion and has been scanned. Restoring an infected image puts the attacker's tools back on the network.

    Q. How long does bare metal recovery take? 

    A. It depends on image size, network or storage speed and hardware readiness. Test restores for each server class to get a real number for your environment.

    Further Reading