Jump to content

Backup Scripts Lost


tracker

Recommended Posts

Restore the last working "config80.dat" file from your backup, stop the engine, replace the "wrong" version with the backed up version, then restart the engine.

 

If you never backed up the "config80.dat" file, then you will have to readd your scripts/clients, locate your media sets, etc...

Link to comment
Share on other sites

OK I found it. There is one marked Config80.dat.bad and is replaced by a new one. How do I restore so the scrips show up in the program?

If there is a file called Config80.bak and it's dated from prior to the time you began experiencing problems, you could try stopping the Retrospect Engine, removing the existing Config80.dat file, and restarting the engine. However, if, as is most likely, Config80.bak is more recent, and you don't have a recent good backup of Config80.dat, you are out of luck; you'll need to recreate everything from scratch.

 

We back up Config80.dat as part of our normal backups, and also periodically copy the file to another local hard drive volume so that a good copy is always readily available.

Link to comment
Share on other sites

If the system renamed the old file as bad then if I restore it, wouldn't I just be putting a bad file back in place. I do have a backup of it as I backup to an external drive. I have three backups to choose from.

Personally, I would first choose a backup from a few days ago. If this version is also bad, try any of the others; you've nothing to lose.

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.

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

Loading...
×
×
  • Create New...