Sign in
Microsoft.com
 
Microsoft
 
 
 

locked
Backups fail after Google Desktop install RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote
    Had all 5 machines in my house backing up without a problem - until I installed Google Desktop on two of them.

    I have run chkdsk /f multiple times on the two machines that are currently having this issue. Prior to GDS install they worked fine, with multiple backups currently saved. Post-GDS install I cannot back them up manually or automatically.

    Anyone else having this issue? Any suggestions?

    /AM
    Saturday, April 25, 2009 5:52 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    @kariya: No, I have not tried uninstalling GDS. The machines in question had no issues backing up prior to the GDS installation (other than that first chkdsk /f to get the ball rolling). Their first backup post-install of GDS failed. Removing GDS isn't an option I want to pursue unless absolutely necessary, as reindexing takes forever. At this point GDS is more important than nightly backups, since I use GDS almost every hour while I work to search years of mail and chat archives, as well as vendor technical documentation.

    In a strange twist, it appears that the backups are now spontaneously functioning again. I didn't change anything, reboot, or otherwise modify my configuration - other than including my 70GB Time Machine backup in the scheduled backup for the personal folders on the WHS to a pair of external USB 2.0 drives. This should not be related to my original issue, but I wanted to note the change and its coincidental timing.

    Is there some possibility that indexing activity immediately following the GDS installation could impact the system's ability to back up to WHS, and that once initial indexing activity is complete the WHS backups were able to execute as normal? Has anyone else experienced a similar issue? I will monitor the next few weeks of backups to see if the failures reoccur.

    /AM
    Monday, April 27, 2009 12:01 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    When you attempt a backup on one of the affected computers, do you see any errors in that computer's event log? What does the attempted backup show on the Computers and Backups tab in the console?
    I'm not on the WHS team, I just post a lot. :)
    Saturday, April 25, 2009 6:43 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    Here is the error, from the Application log on one of the systems that failed to backup:

    System.IO.FileNotFoundException: The device is not ready. (Exception from HRESULT: 0x80070015)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.HomeServer.Common.Client.Win32.ThrowLastError()
       at Microsoft.HomeServer.Backup.NTFS.VolumeBuffer.BeginRead(Int64 cluster, Int32 count)
       at Microsoft.HomeServer.Backup.NTFS.ClusterRangeReader.MoreReadAhead(VolumeBuffer b)
       at Microsoft.HomeServer.Backup.NTFS.ClusterRangeReader..ctor(Volume volume, RangeReader getNextRange)
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass2()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()

    The error appears about 9 minutes after the backup started. The machine that this log comes from is powered on 24/7, so there shouldn't have been an issue with the machine being unavailable for backup or otherwise not ready. The machine is on the same Gigabit LAN switch as the WHS. Another machine on that same switch backed up without any issues.

    Both machines I mentioned above are running Windows XP, with all the latest service packs and security updates.

    /AM
    Sunday, April 26, 2009 4:04 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Here is the error, from the Application log on one of the systems that failed to backup:

    System.IO.FileNotFoundException: The device is not ready. (Exception from HRESULT: 0x80070015)
       at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
       at Microsoft.HomeServer.Common.Client.Win32.ThrowLastError()
       at Microsoft.HomeServer.Backup.NTFS.VolumeBuffer.BeginRead(Int64 cluster, Int32 count)
       at Microsoft.HomeServer.Backup.NTFS.ClusterRangeReader.MoreReadAhead(VolumeBuffer b)
       at Microsoft.HomeServer.Backup.NTFS.ClusterRangeReader..ctor(Volume volume, RangeReader getNextRange)
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.DoClusterPass2()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.RunWithoutCatch()
       at Microsoft.HomeServer.Backup.BackupOp.BackupOperation.Run()

    The error appears about 9 minutes after the backup started. The machine that this log comes from is powered on 24/7, so there shouldn't have been an issue with the machine being unavailable for backup or otherwise not ready. The machine is on the same Gigabit LAN switch as the WHS. Another machine on that same switch backed up without any issues.

    Both machines I mentioned above are running Windows XP, with all the latest service packs and security updates.

    /AM
    Did you try uninstalling Google Desktop to see if the backups work then?
    Sunday, April 26, 2009 6:29 PM
    Moderator
  • Question
    Sign in to vote
    0
    Sign in to vote
    @kariya: No, I have not tried uninstalling GDS. The machines in question had no issues backing up prior to the GDS installation (other than that first chkdsk /f to get the ball rolling). Their first backup post-install of GDS failed. Removing GDS isn't an option I want to pursue unless absolutely necessary, as reindexing takes forever. At this point GDS is more important than nightly backups, since I use GDS almost every hour while I work to search years of mail and chat archives, as well as vendor technical documentation.

    In a strange twist, it appears that the backups are now spontaneously functioning again. I didn't change anything, reboot, or otherwise modify my configuration - other than including my 70GB Time Machine backup in the scheduled backup for the personal folders on the WHS to a pair of external USB 2.0 drives. This should not be related to my original issue, but I wanted to note the change and its coincidental timing.

    Is there some possibility that indexing activity immediately following the GDS installation could impact the system's ability to back up to WHS, and that once initial indexing activity is complete the WHS backups were able to execute as normal? Has anyone else experienced a similar issue? I will monitor the next few weeks of backups to see if the failures reoccur.

    /AM
    Monday, April 27, 2009 12:01 PM