Jump to content

Retrospect configuration gets corrupted too easily

Recommended Posts

This is not a duplicate topic. I created a post here:


with a solution for other users. This post is just for the bug report.


The Config80.dat file is too fragile and does not survive forced power downs on the backup server. The current method of saving the configuration should be replaced with something that is more robust. The configuration file is also large - it's 80MB in my case - which suggests that maybe its design should be refactored or else the content split up into separate files so that the basic server configuration is less likely to get corrupted.

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