Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
"Incomplete" backup? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    I am unable to get a successful backup for one of my machines.  The console shows that backup for the first disk was successful but not for the the second one (from which I'm only backing up 2 folders).  The backup status windows says "100%" then displays an error message.

     

    Questions: 

    1. What, if anything, can be done with this partial backup?  Does it/could it serve any purpose at all? Could it be used to restore the primary disk or could I retreive individual files from it?
    2. What will happen the at the next automatic backup?  Will the connector start from scratch or will it do an incremental backup for the primary disk and try to get the two folders from the secondary disk? 

     

     

    Tuesday, April 3, 2007 3:50 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    I didn't have any AV running on either the server or the client.  After 2 more days, I finally managed to get a complete backup for the machine.

     

    Now I'd like to know why the console says the network is "healthy" but the systray icon says the network is at risk.  There's always something...

    Friday, April 6, 2007 2:52 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    1. Each drive is backed up as a separate operation, so if your system drive finished successfully, that backup should be good.
    2. I haven't experienced this problem, but I would expect that it will do an "incremental" of the system disk, then try to do a "full" backup of the folders on the second disk.
    Tuesday, April 3, 2007 3:55 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Is the second disk FAT32 or NTFS?  Was it formated NTFS or converted?


    Windows Home Server does sector backups fully then incrementally at a network wide level.

    Tuesday, April 3, 2007 9:09 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    The second drive is NTFS.  

     

    No matter what I do, this machine just can't be backed up.    It's set for automatic but I can't see that it even tried last night.

    Wednesday, April 4, 2007 2:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Athena,

    I had a similar problem with my system except the D: drive would complete but the C: drive would not.  Finally I logged into the WHS console, disabled the anti-virus program, and selected the "Back-up Now" option.  I made sure the PC did not go into hibernate by moving the mouse every ten minutes or so.

     

    The backup completed.  Since then, the automatic incremental back-ups have usually completed without a problem.

     

    HTH

    Stephen

    Wednesday, April 4, 2007 11:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    I didn't have any AV running on either the server or the client.  After 2 more days, I finally managed to get a complete backup for the machine.

     

    Now I'd like to know why the console says the network is "healthy" but the systray icon says the network is at risk.  There's always something...

    Friday, April 6, 2007 2:52 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    The systray icon notifications are notably buggy. Smile You can fix the tray (for now) by right clicking the icon and selecting Exit. Then find the Windows Home Server item in your programs menu and run it. The tray icon should sync up properly.
    Friday, April 6, 2007 3:12 AM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    In a related topic.  I am also getting an incomplete backup message.  I changed out the drive in my laptop, (the only drive in the system), and cloned the original system drive to this new one.  (I still havn't been able to get a successful restore on this machine, which is posted on connect).   As I am going to be switching drives back and forth for use with various beta programs, I renamed the new system drive.  Now I get an incomplete error message, stating that WHS couldn't back up drive C:\ (Original system drive).  Which would be true, because it's not there, but it did backup the new system drive.  I was able to exclude the original drive and get it to complete the backup successfully, but I could see this as a problem if WHS keeps trying to backup drives that are no longer available.  Yes they can be excluded, but do they drop off the excluded list if they havn't been backed up for a length of time, or are they going to be there years from now, when I forget what I was doing today?

    Is there a way to not remove the computer from the backup list, but to get the old drive to not show up in the list of drives that it wants to backup?


    Friday, April 6, 2007 2:14 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I believe that one identifier for PCs on WHS is the MAC address. Since you're swapping drives and (I assume) naming the PC the same on all of them, WHS is probably getting very confused. I mean, here it's got a connected PC, with a known MAC address and NetBIOS name, but the drive keeps changing.

    Now that we've got an SDK, we may be able to learn a little more about how all this works. I'm going to take a look at the documentation over the weekend...
    Friday, April 6, 2007 2:36 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    The PC name does stay the same, it's the volume name (HDD name) that I changed. 

    I guess what I'm getting at is, how is this going to work for people that do change out a drive, not using the restore option through WHS.  Is there always going to be an extra volume that WHS wants to backup even though it is no longer there?


    Friday, April 6, 2007 3:32 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I don't have an answer for that question. I don't think the current behavior is a bug, but I agree that for the people who need to be able to swap out drives, it would be convenient if there were a way to do so more seamlessly. You should check on Connect to see if there are any suggestions regarding this issue. If not, you should submit one.

    In the meantime, the workaround I would suggest is to first remove the computer entirely from WHS and uninstall the connector from both drives. (Doug Knox has a tool that makes that possible, though you will also have to do some additional work to complete the task). Then choose one configuration to connect to WHS and only install the connector there. I expect that you will lose the backup of the other drive. If you absolutely must retain both, then I would still remove the computer entirely, including all backups. Then I would change the computer name for one of the drives, install the connector on both, and back them up. I will warn you that A) I haven't tried this, so there may be problems (particularly if WHS doesn't actually use the NetBIOS name), and B) if it works, you will have a machine listed in WHS that is no longer being backed up, and so you will start to receive network health warnings. There's no way to avoid the warnings at this point.
    Friday, April 6, 2007 3:49 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote

    Resurrecting and old thread...

     

    I'm getting an "incomplete" backup when I run the backup on my main workstation PC. This machine has 2 HDDs installed and I only want the C: drive to back up (D is simply junk data/files etc I don't overly care about). I have set ONLY C: to backup and removed D from the backup backup plan. When looking at the backup results it shows "incomplete" for the entire job, but looking at the details C: is complete (green) and D: is simply greyed out with red incomplete.

     

    If I specifically have D not selected in the backup profile, why is it even mentioning it in the backup results? And why is it tagging it as incomplete when it (looks like) it backed up C entirely and completely?

     

     

    Thursday, April 26, 2007 6:25 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    This is a bug.  I've successfully been able to remove harddrives from being backed up without error.  Can you please run Talq on both the clients and the server and report the cab numbers?  Make sure to keep checking back on your bug!
    Monday, April 30, 2007 10:43 PM
    Moderator