Fulco Posted July 13, 2003 Report Share Posted July 13, 2003 System: Windows 2000 SP3; Retrospect 6.5.319; Single Server; Terminal Server installed After updating Retrospect 6.0 -> 6.5, the Preference file was damaged. See: http://forums.dantz.com/ubbthreads/favlinker.php?Cat=&Entry=2578&F_Board=multiserver&Thread=27887&partnumber=&postmarker= Is there a way to repair the Preference file? Is there another way to get the Backup Scripts, Clients, and Volumes back, without recreating them all? And what about all the Logs and other information stored in the Prefs? Fulco Link to comment Share on other sites More sharing options...
AmyJ Posted July 14, 2003 Report Share Posted July 14, 2003 If you have a backup copy of the Preference file, you can restore it. The file itself is not repairable. The logs are not contained in the config65.dat/config65.bak files. They are seperate .utx files. Link to comment Share on other sites More sharing options...
Fulco Posted July 15, 2003 Author Report Share Posted July 15, 2003 I used an older, version 6.0, of the Preference File with the same result. After converting the Preference File Retrospect still hangs on Quit (after Auto-start). In Retrospect 6.0 everything did function fine. What next? I don't want to spend hours on recreating everything. Fulco Link to comment Share on other sites More sharing options...
AmyJ Posted July 16, 2003 Report Share Posted July 16, 2003 The configuration file is not repairable. Unfortunately, you will need to recreate your scripts and preferences from scratch. Link to comment Share on other sites More sharing options...
Fulco Posted July 29, 2003 Author Report Share Posted July 29, 2003 I did create a new Preference file. The first few day the backups went OK. Retrospect did Quit after the backup. BUT: now the issue is back. The Preference File is damaged again. Retrospect hangs, when trying to Quit. Fulco Link to comment Share on other sites More sharing options...
AmyJ Posted July 30, 2003 Report Share Posted July 30, 2003 The next step is to determine what is corrupting the configuration files. How does this happen? Typically these errors can been seen if there is a crash or power failure while Retrospect is running. You can also see these errors if you have a configuration problem that is causing data corruption on your hard disk or network. Try running your backups from a different computer (we have seen obscure problems with data corruption being caused by specific hard disks). If the problem does not follow your backups to another computer, consider the original hard disk suspect. It may be that the drive is corrupting other data as well. Consult your drive vendor's documentation, or contact the vendor for assistance. If the problem follows your backups to another computer, we recommend hardware troubleshooting. These problems can be hard to troubleshoot; if things work well on another computer, we recommend switching the backups to that computer, and investigating what might be causing the corruptions on the original computer. Obviously this would be very complex to do. You may end up being satisfied with having your backups working again in their new configuration. It is up to you. Please see the Knowledgebase for troubleshooting applicable to the type of backup device you are using. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.