Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Posts posted by rsleegers

  1. Please note that when I start Retrospect, the system crawls. When I quit Retrospect, everything is back to normal.


    Starting Retrospect gives the splash for three minutes before the skeleton of the application window comes open. The window fills in around three minutes or so later, but all controls are grayed out.


    Look in your Event Logs for disk/drive errors. Scan the drive containing your configuration and catalogs. Preferably do the scan with a boot disk (SpinRite or Ultimate Boot Disk utility). I have seen Retrospect/Windows become non-responsive for minutes save for a brief second or two in between disk attempts.

  2. I don't have any specific advice, but I have had catalog errors and grooming errors as well from time to time. My current set up has the catalog file and backup on the same machine and it has been running well. Previously I had the catalog file on the local backup machine, and the backup set over the network. Where are your catalogs relative to the Retrospect machine? I had network failures from time to time so we had to rebuild periodically. This also meant having to re-link the backup set to the scripts, do you have to do this as well? (i.e. rebuilding deletes the backup set from scheduled script sources). If you have another network path (2nd NIC) you could try that, or another network cable. The backups I assume scan other machines in the network so the problem may only show up during catalog operations.

  3. Since the computer running Retrospect is only used for backups and file stores, I put Retrospect in my Startup folder to launch after logging in. The computer also automatically logs in (search internet for registry scripts to do this), but it's up to you whether your security set up allows this.


    If you see the activity screen come up and you just want to open the full Retrospect, check the status line for any running scripts. If none are running, click the green restart button and the full Retrospect will open.

  4. If you are just backing up data, create two or more remembered volumes in your Volumes Database (Configure|Volumes). Assign each volume to a different script.


    If you want to be able to recreate the system, I suggest leaving your existing client and script, but adding some folders to your Private files/folders screen in the client, and then creating a volume (as above) and and assigning it to a script. To do a complete restore, you would restore the client backup, then the volume(s) backup.

  5. Waht is the best solution to perfom this upgrade?

    Search for your Config75.dat or Config76.dat file. Save a copy of this file and note the location (often \Documents and Settings\All Users\Application Data\Retrospect or \ProgramData\Retrospect). Perform the uninstall and check if the file is still there. If it's not there, copy it back. Then install the new version and it will see/upgrade the old one. I have done this on a clean computer and it saw the old file and upgraded it fine. The new file should be Config77.dat. Your catalog and backup files should be untouched by the upgrade. If you leave them in the same locations the upgraded configuration will re-use them. If the catalog files are removed you can rebuild them.

  6. What's the correct procedure for moving a Retrospect installation to a new system? How can I fix this problem where Retropsect on the new server doesn't know where all the backup sets are located?

    Everything so far is correct. Now you must go into each backup set and set the location:

    Configure, Backup Sets

    Select backup set, click Properties



    change the Location for backup data folder (type it in or use Browse)

    Click Ok and close the backup set

    (repeat for each backup set)


    Remember to use the root folder (i.e. the folder above the \Retrospect\Dantz folder) - it should then be able to pick up from where it left off in the last backup.

  • Create New...