Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About waninae39

  • Rank
  1. waninae39

    Restore Failure

    aslo, the only message i get is this "No Removable Storage Manager to restore from this Snapshot" all restore attempts run for 4-5 minutes and then stop wit this message there is no documention explaning what it means, what it does or how to fix it only three google message are found
  2. waninae39

    Restore Failure

    hello i have the same issue did you get this working? i have opened up support case 19974
  3. also each type you reboot with the recovey cd, the PC node name changes , thus you must remove the old node name and add a new one unless you have a lot of unused client licnese. after rebooting i can confirm that the recovety first erases the partition. on the server it ;ollks like it is just going to leave some fioles, chnages other and add the remaing. instead it erase the vlouma nd then adds the files; until it stops in my case, i can no longer boot the PC as it has erased the root c drive and thus all the files needed are no longer there i am still waiting for support to get me a workoing soln for either: 1. recovering from a live PC using the retrspect server restore or 2. from a retropsect recovery CD that can boot a PC that does not need an active working root drive so far, neither work for me (;
  4. update i sent a note to support asking what the issue was . they stated: "The errors you are seeing in the log at the time of the restore are happening because the restore of the Windows System State is failing for a few of the system state components. Hopefully the restore performed while booted from the recovery disk will give better results. If not, you may have an issue with that specific snapshot and you may want to try doing a restore from a different backup date." i updated my server to 8.1 from 8.0 , no change noticed i was hopeing for more specific details for the failure as the document is weak on non working restores i created a bootable restore disk. for some reason, it built it with a 7.5 client and not a v8 clinet it boots , but you must have at least one free client licnese as you have to add this as a new client to the server i then did the restore and got the same results 13/2013 6:59:49 PM: Restoring from 2012-xp-64, Snapshot wb-x64, 4/26/2013 12:30:00 AM VssWEnumWriterMetadata: Excluding writer "System Writer" from the backup. VssWEnumWriterMetadata: Excluding writer "Shadow Copy Optimization Writer" from the backup. Reported missing by user: "1-2012-xp-64" Reported missing by user: "1-2012-xp-64" VssWEnumWriterMetadata: Excluding writer "System Writer" from the backup. VssWEnumWriterMetadata: Excluding writer "Shadow Copy Optimization Writer" from the backup. No Removable Storage Manager to restore from this Snapshot 5/13/2013 7:08:04 PM: 1 execution errors Duration: 00:08:15 (00:04:00 idle/loading/preparing) it now runs for 8 minutes before stopping with the same message "No Removable Storage Manager to restore from this Snapshot "
  5. Hello: I am running Pro 8.0.0(199) i had to restore an Xp pro 64 box that had a dead battery and a dead SSD. this unit has many snapshots i installed a base XP Pro 64 image, enabled volume shadow copy and the retrospect V8 client i need to totally recover the image back to before the system died, Ie a total image recovery The server can see the "new" PC. it can sync time also The restore starts fine . i see the traffic on the PC. the server seems to be copying files THEN the server stops after 4-6 mins with the following messag + Executing Restore from Backup at 5/13/2013 11:24 AM 5/13/2013 11:24:20 AM: Connected to wb-x64 To volume Main (C:) on wb-x64... - 5/13/2013 11:24:20 AM: Restoring from 2012-xp-64, Snapshot wb-x64, 4/26/2013 12:30:00 AM VssWEnumWriterMetadata: Excluding writer "System Writer" from the backup. VssWEnumWriterMetadata: Excluding writer "Shadow Copy Optimization Writer" from the backup. No Removable Storage Manager to restore from this Snapshot 5/13/2013 11:28:16 AM: 1 execution errors Duration: 00:03:56 (00:00:56 idle/loading/preparing i have searched this forum, someone had this issue in 2009 and noone responded to RJH213 http://forums.retrospect.com/index.php?/topic/24851-restore-failure/ I have google this , with no results can anyone shed light the V8 maniual does not shed light either i am stuck with this obscure message please advise walter
  6. waninae39

    how to migrate BU server for old pc to new PC

    i found this and will test it this week http://kb.retrospect.com/articles/en_US/Retrospect_Article/Moving-Retrospect-from-one-Windows-backup-computer-to-another-Windows-backup-computer/?q=kb9526&l=en_US&fs=Search&pn=1 the c:program data folder is hiden by default in win7, and that is where the old config files need to be placed
  7. hi found the soln here http://kb.retrospect.com/articles/en_US/Retrospect_Article/Moving-Retrospect-from-one-Windows-backup-computer-to-another-Windows-backup-computer/?q=kb9526&l=en_US&fs=Search&pn=1
  8. hello i have the same issue on my new win 7 machine, there was no such directory in the root of C: i created a new c:\program data\retrospect directory, copied all the files in there from the old xp machine, ie C:\Documents and settings\all user\application data\Retrospect when i start the sw it still asks for a license key i does the same when i double click an rbc file any ideas on how to fix this?
  9. i have to move for old pc to new ones, as well xp is going away my current retrospcet V8 Bu sw is running on a xp box i have a new home for it on a C220 server running vmware, very sweet device I plan to run in win7 as a VM i have copies of the .rbc and .rbf files saved. but i can't find any support files on how to migrate to a new pc for the backup v8 sw. how do i install the sw on the new win7 pc and get it to point to where the rbc and rbf files? I need that so that it can continue where the old BU sw stopped?
  10. waninae39

    Retrospect 8 - Windows 7 (64-bit) error -1101

    i have the same error. one device has a dead SSD. i started the BU restore and it died half way through. now i can't retore it at all as it complains it can't see the RDB file. the NAS is mounted and i can point it to the files. Then it complains that it does not have permission.(; i CANT re generate the catalog as i am trying to restore to end device. How can i get this fixed! please help
  11. as posted only one machine was affected. . that one machine was able to kill the server (; that should not be possible under any circimstance.! i was only able to get it working by deleteing the latter machines catalog and creating a new BU catalog for that machine. That took over 10 hours for that machine. the s/w needs to be more rebust to crashed and much beeter error messages that means something
  12. retrospect to have MUCH better error and help info
  13. Feedback from support, Thank you for contacting Retrospect support. A response from the agent can be found below. Your Problem Description: Retrospect Pro BU Application crashes 100% when backing up a single client. all details have been posted inthe forum. [url="http://forums.retrospect.com/index.php?/forum/18-professional/"]http://forums.retrospect.com/index.php?/forum/18-professional/[/url] please advise and also post in the forum so that others can see a soln Agent Response: Looking at the forum post... If the problem only happens when accessing a specific client, you will need to try the following: 1) Try a different backup set as your destination. If the catalog file for your backup set is corrupted, the matching can fail for data coming from a specific client. 2) If the problem happens with multiple backup sets, then try to forget the client from Configure>Clients and add the client again. 3) If you have done #2 and it still does not work, try to uninstall and reinstall the client software. 4) The crash could be caused by a problem reading data from a specific disk on the client. Try to backup a different disk connected to that computer. If the failure only happens when reading from the C: disk, try to isolate which directory Retrospect is copying or accessing on that drive at the time it crashes. You could have a corrupt file inside that directory that Retrospect can not read. Thank you for using Retrospect. The Retrospect Support Team
  14. do any support people read these posts? i sent them a note, but no reply
  15. Retrospect Pro BU Application is installed on a Server and it performs daily backups to client machines. The backup files are stored on a QNAP NAS Device. All client machines run either xp pro-64 or win 7 ultimate-x64 Until recently all backups have been running fine. two weeks ago, one client machine running win7 would not backup. When the BU schedule came around to that client machine, the BU would start, after about 30 secs, Retrospect would seem to hang and then Retrospect Pro would crash. the client does not hand or crash. Assertion failure at elem.cpp-1131 the assert_log.utx file show this I looked at the assert_log.utx file and it seems inconsistent in many ways OS: Windows XP version 5.2 (build 3790), Service Pack 2, (64 bit) Application: C:\Program Files\Retrospect\Retrospect 7.7\retrospect.exe, version 7.7.325 Driver Update and Hot Fix version (64-bit) Exception occurred on 01/05/2010 at 1:08:24 AM Error info: Assertion failure at "treefat.cpp-553" the version number listed does not match the version of Retrospect running. the date is wrong the "Assertion failure at" does not match the error message The time stamp on the utx file does correpsond with when retrospect last failed. I searched the KB and can't find this error number. this is a common issue with Retrospect error numbera, the KB is almost useless as they do not document all these cryptic error codes i have also attached the significant part of the operations log file when the win 7 machine last crashed The client is running 7.7.114 the server is running pro 7.7.620 We're getting an consistent endless crashes from just one client machine. No other client machine does this The client machine is other wise working fine. AV and roor kit scan see no issues with the machine. the Retrospect clients has been unistalled and reinstalled, no change is symptoms. Retrospect does see the client machine The machine has been removed from backups as the crash affects all other Retrospect clients. Retrospect has to be manually restarted even though it runs as a service (; The user wants his BU to commence has anyone else seen this issue? any fixes? i have not heard back from support and that is why i am posting this here assert_log.utx operations-log-for 1O-Oct2012-win7 crash.txt