none
System image restore failed with error: 0x807800B8 RRS feed

  • Question

  • Hello All ,

    I have CISCO Blade physical server. I have taken baremetal and data drive backup of the server.

    While restoring it from the network I am getting this error.
    "System image restore failed with error: 0x807800B8"

    When I try to do restore from another disk within the same Server, it work fine.

    Any help much appreciated.

    Thanks

    Wednesday, September 25, 2019 4:01 PM

Answers

  • This problem got resolved by running the restore through the command line.

    Below are the steps followed

    • Use the "drvload " command to load the NIC driver.
    • use command "wpeinit" to initialize the NIC
    • Use the command to assign the static IP to the NIC 
    • netsh interface ipv4 set address "<Name of interface>" static  <IP address> <subnet mask> <Gateway>
    • Run below command to get available backup version.

    X:\Sources>wbadmin get versions –backuptarget:<location of backup> -machine:<Server name (from where you are running the command)>

    • Note down the version of backup 
    • Run the below command to initiate the restoration.

    X:\Sources>wbadmin start sysrecovery -version:<Version> -backupTarget:<backup loacation> -recreatedisks -machine:<Server name>

    • Supply username and password again to access on network backup drive.
    • Type Y and enter to start recovery.
    • Type Y and enter to format and recover volume
    • It will start immediately showing the progress percentage of backup restoration.
    • Once it will completed successfully , exit command Prompt and restart the computer.

    Bare-metal recovery of the physical Server is completed. Hope this will be helpful.


    Regards Baneesh Pal Singh

    • Marked as answer by Baneesh Singh Friday, December 13, 2019 2:44 PM
    Friday, December 13, 2019 2:42 PM

All replies

  • Hi,

    Thanks for posting in our forum!

    1. Make sure that the current account has access to remote shared files.

    2. Please check if the network connection has error.

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Thursday, September 26, 2019 2:56 AM
    Moderator
  • Hi,
    Just want to confirm the current situations.
    Please feel free to let us know if you need further assistance.
    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    Wednesday, October 2, 2019 2:03 AM
    Moderator
  • Hello Daniel ,

    Thank you for the reply. Really appreciate it.

    Those 2 points are already verified. But my problem got resolved by running the restore with command line.


    Regards Baneesh Pal Singh

    Friday, December 13, 2019 2:30 PM
  • This problem got resolved by running the restore through the command line.

    Below are the steps followed

    • Use the "drvload " command to load the NIC driver.
    • use command "wpeinit" to initialize the NIC
    • Use the command to assign the static IP to the NIC 
    • netsh interface ipv4 set address "<Name of interface>" static  <IP address> <subnet mask> <Gateway>
    • Run below command to get available backup version.

    X:\Sources>wbadmin get versions –backuptarget:<location of backup> -machine:<Server name (from where you are running the command)>

    • Note down the version of backup 
    • Run the below command to initiate the restoration.

    X:\Sources>wbadmin start sysrecovery -version:<Version> -backupTarget:<backup loacation> -recreatedisks -machine:<Server name>

    • Supply username and password again to access on network backup drive.
    • Type Y and enter to start recovery.
    • Type Y and enter to format and recover volume
    • It will start immediately showing the progress percentage of backup restoration.
    • Once it will completed successfully , exit command Prompt and restart the computer.

    Bare-metal recovery of the physical Server is completed. Hope this will be helpful.


    Regards Baneesh Pal Singh

    • Marked as answer by Baneesh Singh Friday, December 13, 2019 2:44 PM
    Friday, December 13, 2019 2:42 PM