1-800-691-1991 | 9am - 8pm ET
EN

Restoring GPT Disk to Incompatible Legacy BIOS System

KB ID: 2407
Product: Veeam Agent for Microsoft Windows
Version: Any
Published: 2017-11-20
Last Modified: 2021-10-04

Challenge

After selecting a restore point during the bare metal restore configuration, the following message pops up:
OS disk in backup uses GPT disk.  This may cause boot issues on BIOS systems.

User-added image


If this is ignored and the restore process completes, the following may happen when the restored machine boots up:
No boot disk found
or
An operating system wasn’t found

Cause

This warning occurs when the Veeam Bare Metal Recovery environment detects that the machine it is running on currently has a BIOS that is not in UEFI mode, and the backup file attempting to be restored contains GPT formatted disks.

A system with legacy BIOS mode only is not able to boot to an operating system using GPT.

Solution

Check BIOS Settings First

Check BIOS boot settings of the machine being restored to and determine if it can be configured to use UEFI instead of Legacy mode.

If the machine can be configured to use UEFI boot, the steps below do not need to be performed.

For VM's this setting may be enabled in the Virtual Machine settings:

If the machine does not have an option for UEFI boot in the BIOS, you must perform the following steps.

Part 1: Prepare System reserved Partition

To resolve the compatibility issue, it is necessary to manually create a System reserved as outlined in the following steps.

  1. Boot from the Veeam Recovery Media.
  2. Go to Tools and start command prompt utility.
  3. Run the following commands one at a time:
diskpart
list disk

Review the list of disks on the system, and identify which disk number you will be restoring the OS to.

Use that disk number in the following command.

select disk #
The following command (clean) will erase the entire disk that was selected.
clean
convert mbr
create partition primary size=100
select part 1
format fs=ntfs label=”System Reserved” quick
active
assign letter=S
exit
Close the Command Prompt and proceed to the next Part of this guide.

Part 2: Restore the OS

  1. Start the Bare Metal Recovery.
  2. Follow the steps of the restore wizard until you reach the Restore Mode.
  3. On the Restore Mode step of the restore wizard, select Manual restore (Advanced)
  4. Map the OS drive (e.g., C: ) to the empty space next to the System Reserved partition created in Part 1 of this guide.

    Note:
    • Do not restore the EFI partition.
    • Do not delete the System Reserved partition created in the previous steps.
       
  5. Complete the restore, Do not reboot.

Part 3: Make System Reserved partition bootable

  1. Identify which drive letter has been assigned to the restore Windows OS volume.
  2. Go back to Tools and open the Command Prompt.
  3. Run the following commands one at a time to list all volumes on the system.
diskpart
list vol
exit
  1. Copy boot files from the restored OS to the manually created System Reserved partition.

    Note:
    • This command assumes the OS is C: and the manually created System Reserved partition is set as S:
    • The /f switch is only available with recovery media created from Windows 8/Server 2012 and higher.
bcdboot C:\Windows /s S: /f ALL
  1. Reboot and start the restored OS.

More information

If the system does allow for both MBR and GPT partitions, check with your vendor whether this can be changed in the BIOS settings of the system.
Restoring MBR Disk to Incompatible UEFI System - KB3156.
KB ID: 2407
Product: Veeam Agent for Microsoft Windows
Version: Any
Published: 2017-11-20
Last Modified: 2021-10-04

Couldn't find what you were looking for?

Below you can submit an idea for a new knowledge base article.
Report a typo on this page:

Please select a spelling error or a typo on this page with your mouse and press CTRL + Enter to report this mistake to us. Thank you!

Spelling error in text

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Your report was sent to the responsible team. Our representative will contact you by email you provided.

Oops! Something went wrong.

Please try again later.

KB Feedback/Suggestion

By submitting, you are agreeing to have your personal information managed in accordance with the terms of Veeam's Privacy Policy.
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Thank you for your interest in Veeam products!
We've sent a verification code to:
  • Incorrect verification code. Please try again.
An email with a verification code was just sent to
Didn't receive the code? Click to resend in sec
Didn't receive the code? Click to resend

ty icon

Thank you!

We have received your request and our team will reach out to you shortly.

OK

error icon

Oops! Something went wrong.

Please try again later.