Tresy Posted November 14, 2005 Report Share Posted November 14, 2005 I have Retrospect Desktop 6.1 and 3 clients, 2 of them Windows clients using the latest 7.0 version. I have a dedicated backup for the Windows machines (one laptop and one desktop). My backups of the other Mac client are problem free. The problem is that I get the above error message every time I try to back up my Windows computers to a file on an external Mac Firewire drive. I have thrown out the existing catalogs several times now, but new catalogs produce the same error reliably. All my backups are to this same drive. Only the Windows backups fail. Any advice? Link to comment Share on other sites More sharing options...
natew Posted November 15, 2005 Report Share Posted November 15, 2005 Hi How far into the backup do you get before the error occurs? Have you uninstalled and reinstalled Retrospect and deleted the preference files? Corruption in the preference files can cause things like this. Thanks Nate Link to comment Share on other sites More sharing options...
Tresy Posted November 19, 2005 Author Report Share Posted November 19, 2005 Thanks for your reponse. The problem seems to occur during the verification stage. No, I have not uninstalled and reinstalled. My install is via multiple downloads and updates over time, so I'm not in a hurry to go back and repeat that history. Or can I just download a current version and skip the upgrade path? I will try deleting the prefs file however. Link to comment Share on other sites More sharing options...
CallMeDave Posted November 20, 2005 Report Share Posted November 20, 2005 Quote: Or can I just download a current version and skip the upgrade path? There really are no upgrade installers for Retrospect. Point revisions are the full application, that replaces the existing bundle. Your history and configurations are always stored in the configuration file, which is where Nate is suggesting the problem _might_ be happening. You can uninstall Retrospect and keep your preferences file (which you should be backing up anyway, as it's a valuable data file that deserves protection), or you can move/rename the active configuration file and restart, then test with the fresh preferences that the program will create. Since you see the problem every time, you should be able to test pretty conclusively. Dave Link to comment Share on other sites More sharing options...
Tresy Posted November 20, 2005 Author Report Share Posted November 20, 2005 I trashed everything in my Preferences folder and started over. It worked! Thanks. Link to comment Share on other sites More sharing options...
Tresy Posted December 8, 2005 Author Report Share Posted December 8, 2005 I take that back. I successfully backed up my Windows to a new catalog exactly once before the problem recurred. Does anyone have any other ideas? This is very frustrating. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.