Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About klaveness

  • Rank
    Occasional Forum Poster
  1. It helps immensely. In a practice run after reading your post, I found that the user can indeed choose a place to save the catalog file when creating a backup set. I didn't notice that feature when I created the backup for the second internal drive several years ago. Unfortunately, there seems to be no way to change this aspect of a backup set once it has been created. So I'll start over with a new backup set. I'm most grateful to you.
  2. The user should not have to take that step, either manually or by setting up a separate Retrospect script to duplicate the catalog file -- especially since the software is "smart" enough to place the catalog file on the external G:\ drive. I have set up a duping script, by the way -- but I'm denied access to the folder that Retrospect places it in, even though I'm the administrator. (Please: Let's not divert this thread onto "access denied." That's a different can of worms.)
  3. Using Retrospect 7.7.620 on Win 7 Ultimate 64-bit. I run one Retrospect backup daily to a second internal drive (designated the D:\ drive) inside the computer, and an occasional backup to an external hard drive (the G:\ drive) that I store offsite. Retrospect puts the catalog file for the daily internal backup on the C:\ drive, which holds the operating system and my stuff. So when the C:\ drive crashes, the catalog file is lost. Although I can rebuild the catalog file from the backup on the D:\ drive, it takes two days. On the other hand, Retrospect puts the catalog file for the occasional/offsite backup onto the external G:\ drive itself. So that catalog file is accessible and usable in a restore. Could the program be tweaked so that the catalog file for the backup set always goes on the drive where the backup goes? Or so that the user can select where he wants the catalog file to go? Please see the post below, in the Professional forum, for elaboration. http://forums.retros...l-backup-drive/ Thanks.
  4. klaveness

    Why no Catalog File on internal backup drive?

    It's easy to find the catalog file for the backup on the second internal drive, except when the c:\ drive crashes. It dies along with the c:\ drive, because that's where Retrospect puts it. Here's the path: c:\Users\[my user name]\Documents\Retrospect Catalog files\[backup set name].rbc This is especially baffling, since the catalog file for the external backup is usefully placed on the external drive, not the c:\ drive.
  5. I use Retrospect 7.7.620 on a Windows 7 Ultimate 64-bit computer to make separate backups on two drives: 1. An internal hard drive, which is installed in addition to the c:\ drive and is not in a RAID array with the c:\ drive. The only thing that goes on this drive is my daily backups; the operating system and all my stuff are on the c:\ drive. 2. An external hard drive, which connects to the computer via USB. This is for weekly backups, and is normally stored offsite. It, too, is used for nothing but Retrospect backups. When backing up to the external drive, Retrospect seems to place a current Catalog File in the Retrospect folder, updating it each time a backup occurs. I haven't yet needed to use this Catalog File to restore my stuff, but assume that I could navigate to it and use it instead of rebuilding a Catalog File from the folder on the external drive. But when backing up to the internal drive, Retrospect does not create a Catalog File in the Retrospect folder. I recently did have to restore from the internal drive, and it took over two days for the Catalog File to rebuild. Two questions: Is there any way I can personally tweak Retrospect to do the same thing on the internal drive that it does on the external one: create a Catalog File and update it with each backup? If not, could our friends at Retrospect take steps to add this feature to a forthcoming update? This would allow a restore without a lengthy rebuild of the Catalog File. Thanks.