Restoring a Windows Server bare-metal

Anticipate failures, understand restoration, regain control

In a Cloud or on-premise environment, a Windows server is never fully safe: hardware failure, system corruption, human error, ransomware…

When this server hosts critical business applications, the impact can be immediate: production downtime, data loss, unavailability for users.

It is in these situations that a bare-metal restore truly makes sense: starting from an empty disk and fully rebuilding a working Windows system from backups.

1. Risks associated with losing an application server

A Windows server rarely hosts “just” an OS. It typically includes:

Business applications (ERP, internal tools, industrial services…)
Databases
Authentication or integration services
Specific configurations that are difficult to rebuild

The most common failure scenarios

Disk failure or file system corruption
Failed Windows update making the system unbootable
Human error (deletion, incorrect handling)
Ransomware attack encrypting the system
Complete loss of the VM in the Cloud (deletion, provider incident)

In these cases, restoring files alone is not enough: the system itself no longer boots.

2. What is a bare-metal restore?

A bare-metal restore consists of:

Restoring an entire operating system (OS, files, configuration) to a blank disk, with no preinstalled system.

What this includes

Disk and partition structure
Windows system files
Installed applications
Services and configurations (via the Windows registry)
The system’s ability to start (boot)

3. The general principle of a Windows bare-metal restore

Whatever the tool (Bareos, NetBackup…), the logic remains the same.

Step 1 – Prepare the disk

In a Cloud environment, you start with a completely empty disk.

You must:

Define the correct partitioning scheme (GPT for UEFI)
Create an EFI system partition
Create a main Windows partition

This step is crucial: Windows will not be able to boot without a correct disk structure.

Step 2 – Restore system files

Once the partitions are ready:

The backed-up files from the system disk (originally C:) are restored to the new Windows partition
The content is strictly identical to the backed-up state

With a tool like Bareos, you simply redirect the restore to the correct volume, without worrying about the original system.

For the restored system to be fully functional, the Windows registry must have been backed up correctly, which requires a backup performed via the VSS service.

Without VSS, restoring files alone does not guarantee system consistency.

Step 3 – Make the disk bootable (UEFI)

Restoring files is not enough.

You must also:

Recreate Windows boot files
Register the system in the UEFI firmware
Link the EFI partition to the restored system

This is the step that turns a restored disk into a truly bootable system.

Without it, Windows is present… but does not boot.

4. Restoring other data disks

A Windows system may include other data disks (D:\, E:\, etc…). These are restored in the same way to ensure system integrity and associated services.

If a database exists, the specific restore method is applied to it, unless an offline backup exists: topic for new IOKeep articles.

Data Perspective offers the IOKeep service to ensure monitoring and the recoverability of your systems. Please do not hesitate to contact us.