Jump to content

Keep Retrospect Configs in database

Recommended Posts

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).

  • Like 1
Link to comment
Share on other sites

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.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Create New...