Jump to content


  • Posts

  • Joined

  • Last visited

AmyJ's Achievements


Newbie (1/14)



  1. Check the Snapshot. Anything not copied in a given session will not show up in the Session tree.
  2. Mail sent through a POP account would be in the Sent Items in his local Outlook PST file. You won't find it in his Exchange mailbox.
  3. No problem. Thanks for the update - it may help another user in the future.
  4. It is not normal behavior to truncate the path, which indicates Retrospect may not be getting full path due to the corruption. Can you define the user folder as a subvolume and try another backup?
  5. NCO files are not Retrospect files. According to a Google search they belong to the NERO backup utility. You will need to use that program to access/restore your data...it was not backed up with Retrospect.
  6. Thanks Louis. I'm copying the relevant information below from Post 15 in case the link breaks. VSS errors plague many users. Please note that this issue is a Microsoft issue. EMC has not tested these fixes, and support is not provided for VSS errors. Proceed at your own risk when making Registry changes, and always backup your Registry prior to making any changes. --- This may not be applicable to your situation, however might be worth a look. I have had similar problems with VSS on XP machines that turned out to be caused by the MS Software Shadow Copy Provider Service (SwPrv). You should be able to manually start and stop both VSS and SwPrv (net start vss) (net start SwPrv). If VSS manually starts OK, but you get an error when trying to start SwPrV, then you could have a permissions problem with it (account used to start it? should be system account), or a registry error with the services command line. I have run across several situations with XP machines where the command line for the SwPrv service is incorrect. Possible Solution (these instructions are for XP) Open Control Panel, Administrative Tools, COMPONENT Services Inside the Console Root folder, goto COMPONENT Services -> Computers -> My Computer -> Com+ Applications. On the top toolbar, click on View, Status (or click the Status button on the toolbar). You will see all Com+ applications and their statuses including the Application ID and the PID (if currently running). Make a note of the Application ID for the MS Software Shadow Copy Provider entry. Next check the command line used for the SwPrv service. Navigate back to the top root folder. Inside the Console Root folder, goto Services (local). Note, you can also get here from Control Panel, Administrative Tools, Services. Find the MS Software Shadow Copy Provider Service and double click on it. Notice the Path to Executable field. It will have an entry similar to the following: C:\WINDOWS\System32\dllhost.exe /Processid:{xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx} Check to make sure that the GUID inside the curly brackets is the exact same as what you found in the Application ID in the first step. If it isn't, then this is what is preventing the service from starting. To correct, open regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\SwPrv Double click on the ImagePath value and make the necessary correction. It is obviously a good idea to export a backup reg file of the above key in case you make a mistake or need to restore the original settings.
  7. It's always helpful for users to post their steps and experiences. Thank you.
  8. What version of Retrospect? What version of Vista? x86 or x64? Check your Windows Event Logs for VSS (Volume Shadow Service) errors. Retrospect calls the Microsoft VSS for open file operations, and if it is not functioning correctly you'll see errors.
  9. Make the change in: Configure > Preferences > Execution > Startup The drop down menu is used when you want to change the behavior for the current session. Example: Preferences are set to Exit, but if you really want the machine to shut down after the current execution is complete you use the drop down menu to select "Shut Down". The machine would shut down and the next session would Exit.
  10. Hi Trip - 1. The file should be readable from a CD, and probably from a flash drive. Note that copying it back from a CD may set the file as "Read Only" - you'd definitely want to check that before rebooting. 2. A restore under these circumstances is being done over the top of a newly installed clean OS. You'll have full access to the Explorer. 3. If your prior system had the boot.ini problem that we are talking about you will not be able to use a DR CD for your existing problem. Going forward, your system would no longer have the hidden partition so a DR CD would be useful should you need to do a full system restore again. You can make your own XP SP 2 installer CD fairly easy with a free slipstream program such as AutoStreamer or nLite. It's a time saver over installing the OS and then patching it with the SP. Amy
  11. I'd have to agree about the backup device... I spent years backing up to CD and then DVD. Swapping out media became a pain. I back up to hard drives now and will never go back. The time saved between the faster speed and not having to babysit discs is considerable, and hard drives are very cheap these days.
  12. Retrospect can do a Live Restore over the top of the running system, assuming the system is patched to the same Service Pack that was running at the time of the backup. Marc's suggestion is valid and was the required method for full disk recovery before Live Restore was introduced in 7.0 and before the Disaster Recovery disc option. That you did a Live Restore and it failed may point towards the problem that Russ pointed out early on...that some systems (particularly Dell) have hidden system partitions on the hard disks when shipped. See: http://kb.dantz.com/article.asp?article=5445&p=2
  13. Try downloading Process Explorer: http://www.microsoft.com/technet/sysinternals/Processesandthreadsutilities.mspx?wt.svl=featured You can use it to search handles. Search for your drive letter to see if something is holding it open. I experienced this problem with Google Desktop indexing my drive.
  14. You may have to create new configuration files. Try renaming the Retrospect Docs and Settings folder (eg: Retrospect old), launching and entering your license code to see if you get your UI back. If so, you can try moving your old configuration files (retro75.bak and retro75.dat) into the new folder. If that does not work you'll need to start with new configuration files and recreate your scripts, etc. Some users have reported the permissions change fixes the issues, while other users have reported that their configuration files were corrupted by the upgrade.
  • Create New...