Rebit Support Forum » Installation

Status shows Creating Recovery Point indefinitely

(8 posts)

  1. Dennis
    Member

    After installation, my Rebit shows "Creating Recovery Point this may take a few minutes" but stays that way for hours.

    How do I fix this?

    Posted 11 months ago #

  2. Admin
    Key Master

    This is likely due to a Windows system called Volume Shadow Copy Service failing to initialize.

    To configure the Volume Shadow Copy Service in Windows, follow these steps:

    1. Click here to download
      Part 1 of the VSS configuration
    2. Save the item to a convenient location such as the Desktop
    3. Launch, or double-click, the vss-config1.bat file
    4. Click here to download Part 2 of the VSS configuration
    5. Save the item to a convenient location such as the Desktop
    6. Launch, or double-click, the vss-config2.bat file
    7. Click "Ok" in any windows that appear, ignoring any errors
    8. Restart the computer
    9. Click here to download Part 3 of the VSS configuration
    10. Save the item to a convenient location such as the Desktop
    11. Launch, or double-click, the vss-config3.bat file

     
    At this point, Rebit status display should progress from "Rebit is connected" to "Rebit is creating Recovery Point" to "Rebit is copying data". If this does not occur, further steps are necessary. See http://support.rebit.com/forum/topic/configuring-volume-shadow-service for more information.
     

    Posted 11 months ago #

  3. c141heaven
    Member

    I followed all these steps ... (thru step 3, including selecting the option to turn off the Shadow copy server which was part of step 3 ) then let it run for 36 more hours ... still nothing working with this software .... just a continuous 'this mike take a few minutes' message. Only way to get control of my computer back is to disconnect the rebit drive and reboot .. while it is running the message keeps popping up and getting the 'focus' (even though there are no input fields on that msg box ) ... every time it does this , whatever screen I was on (windows apps/command prompt) loses the focus and any keystrokes entered are lost. There are some serious issues going on here that render this installation completely unusable.

    Posted 11 months ago #

  4. Admin
    Key Master

    This may be related to a problem that we have been unable to overcome.

    Open the "Disk Management" utility (press the 'Windows' + 'R' keys, type "diskmgmt.msc" and click "Ok"). If the list of "Volumes" has no drive letters (e.g. "C:") associated with any of the items, then Rebit software is unable to access the disk drive properly. We are working on a solution, but have no workarounds currently.

    Posted 9 months ago #

  5. avbentem
    Member

    Any news on this?

    My father's Dell machine on which I'm trying to use the latest Rebit SaveMe shows a 55 MB FAT partition, followed by a 3.5 GB FAT32 partition, followed by a 145 GB NTFS partition. The first two show no drive letter, the latter is C: for Windows XP. The machine does not freeze, but whenever Rebit finally shows that a recovery point has been created, it will go back to creating a new recovery point right away. Sometimes it actually claims it has completed processing drive C:, but then only reports a few thousands files have been processed, which is not enough for an initial beackup.

    My mother's PC is a Dell as well. That machine has one 47 MB FAT partition with no drive letter, and a 38 GB Windows XP partition, which is C:, and Rebit SaveMe runs fine on that machine.

    I already disabled Windows search indexing and ensured Avast! is not scanning the target disk.

    The described steps give me some errors, mainly because they were written for the orginal Rebit. Maybe I should not have run them for Rebit SaveMe? Before executing these steps, rbvss.exe C: as described at http://support.rebit.com/forum/topic/configuring-volume-shadow-service did not succeed, but now it does run fine.

    Still, running step 2 gives me "DllInstall in swprv.dll failed. The returned error code is 0x8000ffff". However, running net start swprv runs fine so I guess the DLL is installed and registered.

    Posted 5 months ago #

  6. Admin
    Key Master

    To correct this condition, it is necessary to modify a registry key.

    If you are familiar with editing the Registry, this is a pretty straightfoward procedure. Otherwise, please contact us and we can walk you through it via a remote web session.

    The registry value to edit is "UpperFilters", and it is located at this key:

    HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Class\{4D36E967-E325-11CE-BFC1-08002BE10318}

    If "UpperFilters" does not exist, add it as a MULTI string value.

    You need to APPEND "PartMgr" (do not use the quotes) to the current "UpperFilters" value. It should go on its own separate line.

    In order for this change to take effect, you need to REBOOT your system.

    At this point, the Rebit software should display "Creating Recovery Point" for no more than 2 minutes, followed by a countdown of files remaining to be copied.
     

    Posted 5 months ago #

  7. avbentem
    Member

    No changes after applying that registry change and rebooting. (I had Windows create a restore point prior to changing the registry --which only took seconds-- but forgot to write down the existing value, if any.)

    Meanwhile I not only removed the backup for that specific computer (to enforce a new initial backup; this showed a slow "percentage remaining" thingy, which seemed to indicate this would take hours but was completed all of a sudden), but also uninstalled Rebit SaveMe, and ran start.exe from the USB disk again. Now, when going to the USB disk, it still shows start.exe rather than the backups on that disk. It also did not prompt me for the license key. And I think earlier the file properties dialog would include a Rebit SaveMe tab sheet? Not now.

    I guess I need to ensure Rebit SaveMe is uninstalled in a better way, but I'm using TeamViewer for remote support which makes such operations a bit troublesome. To be continued.

    (I also noted that Adobe Photoshop Elements is monitoring the hard disk for new or moved files. Maybe that can interfere too?)

    Posted 5 months ago #

  8. KernelSoftware
    Member

    Same problem here. After Part 1 and Part 2, the problem stopped and Rebit showed the status as backed up. Then, I proceeded with Part 3 and the problem came back.

    About 20 minutes later, the status showed Backed Up. About 20 minutes after that, it's back to the original problem.

    I ran the rbvss tool and it completes successfully (no errors). I also try to review saved items, but My Rebit hangs when trying to open the computer.

    vssadmin list writers lists the following writers as stable:

    WMI Writer
    Microsoft Writer (Service State)
    Microsoft Writer (Bootable State)

    Thus, this issue does not appear to be caused by a VSS problem.

    Posted 2 months ago #

RSS feed for this topic

Reply

You must log in to post.