Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


OSProf last won the day on June 22 2016

OSProf had the most liked content!

Profile Information

  • Gender
    Not Telling

OSProf's Achievements


Newbie (1/14)



  1. Hello, I have been using Retrospect Desktop on Windows successfully for years, and I am currently using version I store the backup set itself on a Western Digital USB hard drive and the catalog on the main disk of my computer. This year, Retrospect got itself into a state where it could not find the Catalog file. If I try to "Configure a Backup Set" and select the set, it asks where is the catalog file. I can navigate to the file and try to open it, but it typically says that the file is not found, but occasionally it says that the "file is not a Catalog file or is heavily damaged." This happened a couple of months ago, so I completely rebuilt the catalog (taking more than 18 hours) and **thought** that all was working well. However, I now discover that it was not working as I thought. So here are several questions:-- 1. Is this the right forum for this topic? if not, what is? 2. Might it possibly have something to do with blanks in the backup set name? All of my backup set names have had blanks in them, and that was not a problem in the past. But something could have changed in more recent releases. 3. Is there a way to recover the backed up information? I know that it is possible to rebuild catalogs from the backup media, but that won't help if I cannot access the the catalog file. 4. Any other suggestions? Thanks, OSProf
  2. I use Retrospect to back up several computers on my home office network. I recently got a new 64-bit Windows 7 desktop system and transferred the Retrospect 7.7 license to it. My problem is how to configure power saving options and still have Retrospect run automatically in the middle of the night. Being energy conscious, I would like to let the computer enter sleep mode when I am not actually using it, but I would like it to wake up whenever Retrospect backups are scheduled to run, and I would like it to stay awake for the duration of the backup sessions, however long they might take. I tried to do this multiple times in the past with earlier versions of Retrospect and earlier versions of Windows, but was never successful. Any suggetions? Thanks, Hugh
  3. Thanks very much. This same issue came up under another topic, where you suggested backing up to 7.7.341. I did that, and it solved my problem.
  4. Retrospect is 7.7.533 and Retrospect Client is 7.7.114
  5. I recently upgraded from Windows XP to Windows 7 and from Retrospect 7.6 to Retrospect 7.7. I use it to back up two computers --- the main computer and a Windows Vista client every night. After the upgrade, client backups have not been successful. When I log in in the morning, Retrospect is simply hung. I have to kill it from the Task Manager. When I try to run the script manually, the main computer backs up okay, but the client gives errors like the following:-- T-36: main: transaction terminated by PDS exception T-44: MapError: unknown Windows error -2,147,217,405 T-44: W2dbWMIDbOp: pWMIRep->BackupREGDB failed, osErr -2147217405, error -1001 Can't back up WMI Repository, error 149126320 ( unknown) File "C:\Windows\winsxs\x86_microsoft-windows-ie-ratings.resources_31bf3856ad364e35_8.0.6001.18702_en-us_3ca84eef9f923007\": can't read security information, error -1017 ( insufficient permissions) File "C:\Windows\winsxs\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_6.0.6000.16386_none_c55b7c585fd029f3\": can't read security information, error -1017 ( insufficient permissions) File "C:\Windows\winsxs\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_6.0.6001.18000_none_c7923e545cbb3ac7\": can't read security information, error -1017 ( insufficient permissions) File "C:\Windows\winsxs\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_6.0.6002.18005_none_c97db76059dd0613\": can't read security information, error -1017 ( insufficient permissions) File "C:\Windows\winsxs\x86_microsoft-windows-ie-ratings_31bf3856ad364e35_8.0.6001.18702_none_aa7d60ae7286ab24\": can't read security information, error -1017 ( insufficient permissions) File "C:\Windows\winsxs\x86_microsoft-windows-ie-runoncessetup_31bf3856ad364e35_6.0.6000.16386_none_86b80675ce2ea891\": can't read security information, error -1017 ( insufficient permissions) They are not on the same files every time. Sometimes they are in a user directory, not a windows directory, and sometimes I get "file/directory not found" for files that are obviously there. Finally, there is a message in my log every time saying "Failed to load extension C:\Program Files\Retrospect\Retrospect 7.7\rdu64.rpx, error -630 ( bad program extension)" At first, I thought the problem might be due to forgetting to upgrade Retrospect Client to version 7.7, but they persisted after that upgrade and reboot. Does anyone have a clue as to what has been going on? Thanks
  6. I too had a hard drive failure. My RCB files were on an external USB drive which was unaffected by the failure. I now have replaced the hard drive, reinstalled the OS (Windows XP), and installed Retrospect Continuous Backup. However, I cannot get it to talk to the existing Data Vault on the external drive. I don't see how to rebuild a catalog, etc. Moreover, in the configuration of the Version Store, it says the the version store is on C:\{RetrospectCB} However, I cannot get it to change to another drive. It says "There are no other disks available that you can use for your Version Store." Can you help? Thanks, Hugh
  7. In my case, the anti-virus software seemed not to be the culprit. Disabling and even uninstalling it did not help. My problem appeared a lot like the "conflict" issues we used to have on the old Mac-OS. Some programs just didn't work with others. After days of experimenting, I could not figure out what the culprit was, so in the end, I re-installed Windows XP from the manufacturer's CD. Retrospect started working properly right away, but the process of reinstalling exposed some of the conflicts of other installed applications. Of all my applications, the ones that seemed most likely to be guilty were Adobe Acrobat 7.0, Quicken 2006, and HP Photosmart printing software. All of these are self-updating, so it is possible that one of their updates caused a conflict with Retrospect. To recover, I had to un-install and re-install each of them. (Originally, I also suspected Google Desktop, iTunes, and URGE, but none of these turned out to have any impact on the Retrospect and/or Windows reinstallation.) That leaves three questions about Retrospect. First, why did Retrospect's disk drivers for external USB drives deadlock so consistently and so hard, when the OS and all other applications could still read and write to the same disks? Second, once a deadlock in the writing occurred, why was Retrospect completely unable to abort the backup operation and exit cleanly? Third (and not mentioned previously in this thread), why did this leave the member of the backup set unusable after I put things back together? Basically, any attempt to append to a backup set that was part of the deadlock caused a 106 error, after an attempt to groom. Retrospect insisted that the drive was full (when it wasn't). My recovery was to Transfer the entire backup set to another drive, "forget" or recycle the original, and then transfer it back.
  8. Has anyone had any further thoughts on this problem? I am stuck without the ability to do a regular backup. The problem occurs when the backup data set is on a disk, but not when the backup data set is on a file ON THE SAME DISK. It happens to all USB drives I can lay my hands on, including a new one out of the box. It happens to drives formatted as FAT32 or NTFS. The problem does NOT occur when running in SAFE mode. I.e., I was able to do successful backups to the backup sets on the disks in question in SAFE mode, but not in NORMAL mode. The symptom is that Retrospect reads some number of files (usually about 8-15 MBytes) and then hangs. At the point where it hangs, a file has been created in the backup set member, but no data is written to it. Once it hangs, the only way out is to kill Retrospect in the Task Manager. I was just starting to set up Continuous Backup, and the problem appears to be happening there, also.
  9. The problem happens on two different drives, with two different USB cables and two different USB ports, and in various combinations of these. I blew away the backup contents of one of the drives, and created a new backup set. The problem still persists. I am not willing to blow away the backup set on the other drive, but I did check the drive on another computer (Vista). There were no problems reported by disk scan. Looking back into the Retrospect History file, the first sign of anomolous behavior came on Saturday morning, when I logged into my computer. Retrospect was waiting for an answer to a dialog box about downloading version 7.6; but the backup scheduled for 3:00 AM that morning was still waiting to run. After the download completed, it would not start by itself, so I had to stop the backup and restart it by hand, at which time it completed satisfactorily. Sunday I forgot to switch disks, so the backup was still waiting for the other drive. So I stopped it, shut down to switch disks, and restarted. At that point, it just hung before it wrote the first backup record on the file.
  10. Disk check succeeds. I can also open the disk in Windows Explorer and look inside. I can even run the defragmenter on the disk. Turning off XP System Restore made no difference. My test backup hangs at the same spot as it previously did. Moreover, Stop does not stop the backup execution. It acts as if it is hung up in the middle of a disk write with no error recovery or escape. Incidentally, I do run Norton Internet Security, and turning that off makes no difference, either.
  11. The other day, my Retrospect 7.5 stopped backing up to my external hard disks. It would say it was copying the first few files, but then it would hang forever. Clicking "stop" said it was stopping, but nothing happened. Trying to exit said it was exiting, but nothing happened. The only way out was to kill the Retrospect task with the Windows Task Manager. So I updated to Retrospect 7.6. Same problem. It does successfully back up to DVD, but not to the hard disk. Details: Windows XP, Retrospect 7.6, scripted backup at night to USB hard drive (alternating USB hard drives every week). Trying a new backup disk does not help. Trying immediate backup of a small number of files to disk does not help. Trying a different disk does not help. What is going on?
  12. I recently "upgraded" one of my home computers to Vista. I now find that Retrospect takes 2-8 hours each night to back it up over my home network, whereas it used to take 10-20 minutes. Upon investigation, I discovered that it is backing up multi-gigabyte files in the System Volume Information directory. These are hidden system files with bracketed names like {22eca3499-1234-...}. Each of these files compresses down to 3-4 kilobytes -- i.e., they are very sparse and don't consume much backup space. However, they consume lots of backup time. There is nothing like them in the two Windows XP machines that I also back up. What are they? can they be considered "cache" files that I should ignore during backup? or do I need them to restore a disk? I am using Retrospect Professional 7.5.13 over a 54 MBit/sec wireless home network. Thanks, OSProf
  • Create New...