locked
Restore points RRS feed

  • Question

  • My restore points disapear on reboot. Quad booting with Vista sp2, xp media edition sp3, xp prof sp3, W7 rc.

    Saturday, August 15, 2009 3:43 AM

Answers

All replies

  • Hello Mr. Seven

    This may not be your problem but what I have found with multi-boot systems is that System Restore must be set to only monitor its own operating system partition. If, say, SR was turned on for all drives in all OSs, and XP reached its maximum disk storage allocation, then some or all SR points are removed for other OSs.

    I can't explain the exact circumstances but I haven't lost any since I set each operating system to only monitor its own drive/partition.

    Saturday, August 15, 2009 7:32 AM
  • Workaround for your problem http://support.microsoft.com/default.aspx/kb/926185 




    My English is not very well.
    • Marked as answer by ONE ZERO Saturday, August 15, 2009 8:41 PM
    Saturday, August 15, 2009 7:36 AM
  • Bull. It should work without hacks. 

    I presently have SR set to monitor only the system partition. I have Vista on another partition configured the same way and it also reboots with no points. I have 40 GB alloted for restore points on each system.
    • Edited by ONE ZERO Saturday, August 15, 2009 9:41 AM
    Saturday, August 15, 2009 7:40 AM
  • Dual boot no excuse becouse it should work.

    "This problem occurs when you start the computer by using the earlier operating system, such as Microsoft Windows XP or Microsoft Windows Server 2003. In this situation, the earlier operating system deletes all the restore points that were created in Windows Vista. The earlier operating system also deletes all Complete PC Backup files except the most recent version of these backup files."


    However, in this case I am starting the computer with 7 and going back into 7.
    • Edited by ONE ZERO Saturday, August 15, 2009 9:39 AM
    Saturday, August 15, 2009 7:47 AM
  • Have you any antivirus installed on W7? Try to temporarily uninstall or disable it, also check for various non-system cleaners installed, etc... 




    My English is not very well.
    Saturday, August 15, 2009 8:07 AM
  • No AV present. Event viewer provides this record: 

    Log Name:      System
    Source:        volsnap
    Date:          8/15/2009 4:25:17 AM
    Event ID:      27
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      7RC
    Description:
    The shadow copies of volume J: were aborted during detection because a critical control file could not be opened.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="volsnap" />
        <EventID Qualifiers="49158">27</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-08-15T08:25:17.843750000Z" />
        <EventRecordID>30267</EventRecordID>
        <Channel>System</Channel>
        <Computer>7RC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>
        </Data>
        <Data>J:</Data>
        <Binary>0000000002003000000000001B0006C003000000340000C002000000000000000000000000000000</Binary>
      </EventData>
    </Event>

    Log Name:      System
    Source:        volsnap
    Date:          8/15/2009 4:24:38 AM
    Event ID:      25
    Task Category: None
    Level:         Error
    Keywords:      Classic
    User:          N/A
    Computer:      7RC
    Description:
    The shadow copies of volume J: were deleted because the shadow copy storage could not grow in time.  Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied.
    Event Xml:
    <Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
      <System>
        <Provider Name="volsnap" />
        <EventID Qualifiers="49158">25</EventID>
        <Level>2</Level>
        <Task>0</Task>
        <Keywords>0x80000000000000</Keywords>
        <TimeCreated SystemTime="2009-08-15T08:24:38.750000000Z" />
        <EventRecordID>30262</EventRecordID>
        <Channel>System</Channel>
        <Computer>7RC</Computer>
        <Security />
      </System>
      <EventData>
        <Data>\Device\HarddiskVolumeShadowCopy1</Data>
        <Data>J:</Data>
        <Binary>000000000200300000000000190006C0060000000000000000000000000000000000000000000000</Binary>
      </EventData>
    </Event>

    • Edited by ONE ZERO Saturday, August 15, 2009 8:29 AM
    Saturday, August 15, 2009 8:14 AM
  • Event view recommends this:

    "Consider reducing the IO load on the system or choose a shadow copy storage volume that is not being shadow copied."

    How would I go about either one of these?
    Saturday, August 15, 2009 8:59 AM

  • I always get confused by the difference between Restore Point and Shadow Copy  (which is not available in Vista HP: "Shadow copies of volumes and shared folders are configured from the server. You can set up shadow copies for all editions of this version of Windows except Starter Edition, Home Basic Edition, and Home Premium Edition.").

    You might try clicking the link Event Log Online Help that appears at the bottom of the Event Viewer page to get more information.

    Saturday, August 15, 2009 9:58 AM
    • Edited by ONE ZERO Saturday, August 15, 2009 11:03 AM
    • Proposed as answer by Drew1903 Saturday, August 15, 2009 8:20 PM
    Saturday, August 15, 2009 10:09 AM
  • Well, It seems that XP is the culprit. Read this! And it will not be fixed.

    I felt that using a separate drive would be ok, I went and checked my DATA drive, a shared volume for backups and storage, physically in the XP machine and found the Vista and Win 7 icons there with no files. So, I lost backups for a Vista machine networked to the shared DATA drive and the Win 7 RC backups on the dual booted machine.

    The registry change fix doesn't work for me as I access files on that drive when in XP. It would seem that removable storage is the solution. I have a removable drive eSata/USB enclosure and 500gb SATA drive as a backup for my laptop and is only connected to a Vista machine. Those backups are still there as it is only connected for back-up purposes for that computer and not network shared or in the same computer as the XP system.

    I think it's a bad deal that no one on the Vista or Win 7 teams alert anyone about this XP dual-boot back-up killer.

    Mr. Seven, thank you for the alert. This could have been a major problem later. I am trying to find another way to post this to alert others. Thanks again!

    The problem with troubleshooting is that trouble shoots back.
    Saturday, August 15, 2009 11:39 AM
  • The impact: When you boot into Windows XP and automount a disk, you will notice the following effects on the disk after booting back to Windows Vista:

    • All restore points are deleted from the disk. 
    • All previous versions of files are deleted from the disk.
    • All but the most recent CompletePC Backup are deleted from the disk. The remaining backup made by CompletePC Backup is full and complete and can be used to restore your entire computer.


    Should this affect me if I create a retstore point on windows 7 and reboot directly back into windows 7?
     

    Saturday, August 15, 2009 11:47 AM
  • My interpretation is that you will not be affected until you boot into XP. If you have no files on that drive that you need for XP, the registry change from kb926185 will protect it.
    I now have some data rearranging to do. I am going to protect the drive with the registry change as my XP system is only used for tech support purposes at this time and my Vista and Win 7 machines are primary.
    The problem with troubleshooting is that trouble shoots back.
    Saturday, August 15, 2009 11:53 AM
  • I read it the same way you did. It seems both 7RC and vista are losing restore points even if I avoid booting into XP.
    I'm still going to try the registry fix and what it does although I doubt it will make a difference becouse if I don't boot into xp xp's volsnap.sys won't change attributes to the points.
    I'll post the results. 

    Saturday, August 15, 2009 12:01 PM
  • I am going to try the registry change and create a backup and test now. I too will report back the result.
    The problem with troubleshooting is that trouble shoots back.
    Saturday, August 15, 2009 12:03 PM

  • Well, It seems that XP is the culprit. Read this!



    That article is at least from 2006, judging from the first comment.  I am not so sure where the hard line is drawn:  "Note that dual-booting Windows Vista with Windows Server 2003 or Windows XP Professional x64 Edition will also result in the shadow copies being deleted."

    I just do full image backups.  Heck with it.

    Saturday, August 15, 2009 12:05 PM
  • Actually image backups are more reliable I don't use system restore myself but I wonder why it's dead. I went to services and changed volume shadow copy from manual start to automatic. About to test it.
    Saturday, August 15, 2009 12:21 PM
  • No avail.
    Saturday, August 15, 2009 12:27 PM

  • I actually had a situation where I had to rollback a driver update.  But apparently the newer driver changed some config file the older one relied upon.  So, rolling-back ended up being worse than had I done nothing at all.  Now of course, someone is bound to come in here and defend MS by pointing the finger of blame at the faulty driver.  Finger-pointing does me no good.  I learned my lesson.  Regardless of what policies might have existed, I will always make full image backups.  It's the only way.

    Saturday, August 15, 2009 12:33 PM
  • I made the registry changes and confirmed that XP had no access to the Win7 partition and the Data drive. I then rebooted into Win 7 and performed a backup to the DATA drive.

    I then went to XP and changed the offline setting for the DATA drive to allow XP access. Booted to XP and confirmed access restored.

    Rebooted into Win7 and performed a file restore. XP didn't change anything on the DATA drive with no OS. Restore feature provided browse and restore functions. The files were intact.

    I am therefore concluding that XP affects only the OS partition or drive and the VSS features from a server if the client is dual boot. Make the registry changes and set the non-XP drives with Vista or Win7 as offline. A storage only volume is not affected.
    The problem with troubleshooting is that trouble shoots back.
    Saturday, August 15, 2009 4:30 PM
  • I also did the reg fix to the appropriate drives and also turned on the block level backup engine service to auto,
    the volume shadow copy service on to auto and have now have one saved restore point on the release candidate but no luck with vista. I also see there is a system created restore point but the ones I created are deleted.
    Is there a way to change where restore points are saved?
    Saturday, August 15, 2009 8:28 PM
  • Update:

    I changed the drive where RP's are saved. For some reason it saves points to drives other than system partition.
    • Marked as answer by ONE ZERO Monday, August 17, 2009 8:19 AM
    Monday, August 17, 2009 8:18 AM
  • Perhaps I should start a new thread but I had a big problem with Restore Points on a multi-boot system in which Vista was the OEM drive C: and Win7 was a new partition (drive letter E) on the same physical  hard drive.

    The Windows 7 System Restore run from the disaster recovery DVD cannot figure out the right drive to put the Restore Point information back on unless I manually run rstrui.exe /offline:e\windows from the e:\windows\system32 directory on a computer that can only be booted off the rescue disk.  The good news is that System Image Restore does know the right drive to put the restored images back on.

    If there is a better forum to post the above, please let me know.  Obviously the programmers in charge of writing System Restore are not talking much to the Microsoft programmers working on installs that allow mult-boot systems to be set up!

    Jim Lewis

    Thursday, October 22, 2009 4:17 AM