none
FAQ: Backup and Restore Trouble Shooting

    Allgemeine Diskussion

  • Backup and Restore Trouble Shooting FAQ (Part 1)

    General steps when backup and restore fails

                   Most of the backup and restore failures are caused by server missing updates, network connection issue or hard disk failure. If you get into any of the backup or restore issues, start with the following steps:

    1.      Make sure your Windows Home Server is up to date.

    a)       Open the console and click Settings->General.

    b)       Click the Update Now button in the Windows Update section to install the latest update.

    2.      Make sure your client connect to your server via wire connection.

    3.      Run chkdsk to address the hard disk issue on the client.

    a)       Run “chkdsk [driver-letter] /f /r” on all volumes on the client you want restore to.

    4.      Run chkdsk to address the hard disk issue on the server.

    a)       Remote to your server, open the command console, and run the following command lines.

    b)       net stop whsbackup

    c)        chkdsk D: /f /r 

    d)       chkdsk C: /f /r

    e)       for /d %1 in (C:\fs\*) do start chkdsk /f /r %1

    f)        net start whsbackup

     

    If the issue still occurs after the above steps, refer to following guidance.

     

    Restore or Open backup fails on 81%

    Symptoms: Normally you will hit this when you open a backup from your client, progressing to 81%, and finally fail to mount the volume.

    Cause: This usually happens when your backup database has some inconsistent data. The root cause could either be hard disk failure or memory corruption.

    Resolution: Please be aware that repairing the database in this case usually involves deleting damaged files; this may lead to losing some or all backup data. We suggest you backup your database as instructed and follow each steps carefully.

     

    1.      Follow the general steps above to fix the common issue.

    2.      Try following steps to ensure it is not client specific issues:

    1)       Try opening the same backup from other clients via Console. If you can successful open the backup, you could get the data from that client.

    2)       If you have older backups contain the same files you need, try opening that backup from your client and copy the files out.

     

    3. If you still have problem, start the repair steps below:

    1)      First, we suggest you backup your database by copying the entire folder D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4} to other volume. If you loss some backups during the troubleshooting steps, you can get your whole database back by copying the data back to the same folder.

    2)      Then, Optionally Delete Index.*.dat file under D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}

    (Note, Deleting Index.*.dat may cause the repair wizard to delete some or all back up data. Make sure to save your backup database before take this step)

    3)      Open the Console->Settings->Backup, click Repair button to check and fix the database.

    4)      Try restoring from your client, if you still have problem, you need delete all your backup data:

    Remote to your server, open the command window, run the following command lines to delete the backup database.

    ·        net stop whsbackup

    ·        del /f /q “D:\folders\{00008086-058D-4C89-AB57-A7F909A47AB4}”

    ·        net start whsbackup

    This will force a new database to be created, and future backup and restore will succeed under new database.

     


    This post is "AS IS" and confers no rights. Ni
    Dienstag, 15. März 2011 11:30
    Besitzer

Alle Antworten

  • Backup and Restore Trouble Shooting FAQ (Part 2)

    Backup fails on all clients

    Symptoms: Backup fails on all clients connect to the server.

    Cause: This usually happens when the network connection is broken, server has low disk space or server’s hard disk is failing.

    Resolution: Ensure your client could connect to your server. Clean up unused backup data and run chkdsk on the server disk. If this still happens, use the following steps to fix it.

    1.      Follow the general steps above to fix the common issue.

    2.      Open the Console and in each client’s backup list and change unused backup to “Delete at next Backup Cleanup”.

    3.      Open the Console->Settings->Backup and select “Cleanup Now”.

    4.      Make sure there is no “low disk space warning” on the Server, if so, you need consider adding more disks to the server storage.

     

    Backup fails on some clients

    Symptoms: Backup fails on some clients but succeeds on other clients.

    Cause: This usually happens when network connection is broken or you backup configuration has been changed.

    Resolution: Ensure your client could connect to your server and re-configure the backup configuration. If this happens, use the following steps to fix it.

    1.      Follow the general steps above to fix the common issue.

    2.      Run Configure Backup on the Console to make sure all you configured backup volumes still exist, for example, you would configure some external disks to do backup sometime, and then remove the external disk.

     

    Restore/Open backup fails on 6%

    Symptoms: Normally this message is shown when you open a backup from your client, progress to 6% and fail to mount the volume.

    Cause: This usually happens when the Windows Home Server’s mount volume driver is not properly installed or previous mount volume driver is not properly uninstalled.

    Resolution: Manually uninstall the Windows Home Server’s mount volume driver and clean up the installation information. If the error still happens, use the following steps to fix it.

    1.      Follow the general steps above to fix the common issue.

    2.      Close other mounted backup from the client.

    3.      Kill the MountBackup process via Task Manager if it has.

    4.      Open Device manager, turn on Show Hidden Devices.

    5.      Look for “Home Server Restore Driver 2” under “System Devices” and uninstall the driver.

    6.      Open the backup again to reinstall the mount backup driver.

     

    Can’t find the Windows Home Server when using client restore CD to do full system restore.

    Symptoms: When restore a backup via Restore CD to the client system; it fails to find the Windows Home Server at the detecting server phase. And on the “Detect Hardware” page, there will be “0 NIC driver” listed as installed.

    Cause: This usually happens if no proper network adapter driver is found or installed when booting from the client restore CD.

    Resolution: Manually find the suitable network adapter driver, copy to a USB Flash disk and install it in the client restore wizard. If this error still happens, use the following steps to fix it.

    1.      Download the latest Client Restore CD from Windows Download center.

    2.      Connect the server and client via wire connection.

    3.      [Option] If you are restoring a 64bit client, you need find the 64bit driver of your Network adapter on the Network adapter for Windows Vista on Network adapter vendor’s website.

    4.      There are some known Network adapter drivers may not been installed properly when booting from Client Restore CD. Those include Realtek and Marvell Yukon. You need find the latest driver of your Network adapter for Windows Vista on the Network adapter vendor’s website.

    5.      Copy the driver to a USB flash disk and plug into the client.

    6.      On the “Detect Hardware” page, Click “Show Details” and “Install Drivers…” after install the driver, you would see there is at least one NIC driver listed as installed.


    This post is "AS IS" and confers no rights. Ning Kuang[MSFT] Windows HSBS Program Manager
    Dienstag, 15. März 2011 11:32
    Besitzer