emulator Posted May 10, 2009 Report Share Posted May 10, 2009 I would like to see Retrospect keep its data (config data, clients, backup scripts, backup sets, etc) in a built-in Microsoft SQL database. This would be much more robust than keeping all this config data in a single file as Retrospect does now, which offers a single point of failure. To accommodate backup of this internal database, every copy of Retrospect could include a limited Microsoft SQL Server add-on that could only back up the Retrospect database (users would still need to purchase the real MS SQL add-on to back up other SQL databases). 1 Quote Link to comment Share on other sites More sharing options...
blm14 Posted May 15, 2009 Report Share Posted May 15, 2009 I have retrospect itself back up its own Documents and Settings\All Users\Application Data\Retrospect folder nightly, so at worst case I only lose one day's worth of configuration changes. But I agree that that information should be easier to parse, read, re-create, copy, etc. I'm just not sure an MS SQL database is the best answer. Quote Link to comment Share on other sites More sharing options...
emulator Posted May 16, 2009 Author Report Share Posted May 16, 2009 I hear ya...we do hourly backups of our dat files. Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.