emulator 1 Report post Posted February 20, 2009 (edited) When the retro75.dat file isn't happy, no one is. A more robust method of backup and recovery of this file would be VERY welcome. Currently, we run hourly backups that go to a groomed disk backup set, which is in turn copied to tape. This has saved our bacon a number of times, and have Retrospect automate this process out of the chute would make life easier. Edited February 20, 2009 by Guest Share this post Link to post Share on other sites
Mayoff 124 Report post Posted February 20, 2009 I don't know of a file named retro75.dat. Do you mean Config75.dat? If you backup the backup server, then that file is protected. If you duplicate this folder on a schedule, then you are protected. Share this post Link to post Share on other sites
emulator 1 Report post Posted February 20, 2009 Oops...you're right. It is the config75.dat. sorry about that. But, as I stated, the user has to create backups to protect this file. The new user just starting with Retrospect might not know about just how important this file is until it's too late. Having Retro protect this file with multi-generational backups out of the box would be very welcome. Share this post Link to post Share on other sites
Richy_Boy 18 Report post Posted March 11, 2009 As that file is key to the operation of Retrospect it shouldn't be as vunerable to corruption as it is. If there's nothing you can do about it getting corrupted, then Retrospect as an application needs to handle recovery - rather than the user through backup procedures. i.e. Imagine if Microsoft Windows lost all your registry settings occasionally and you had to set your desktop applications up again each time, taking days. ...and their solution was "backup your registry settings up regularly". Many people would suggest they fixed their buggy software! Rich Share this post Link to post Share on other sites
