Search the Community
Showing results for tags 'Config80.dat'.
We had a power outage nearby yesterday which took down all non-essential equipment in the building. Our backup server was powered down before I had time to reach it and gracefully shut it down (it is connected to a small UPS battery with 2-3 minutes power). On boot, the console tried to connect to the server but kept spinning. My guess is that the configuration file got corrupted. This was with Retrospect 10.1.0 (221) running on a Mac mini running Mac OS X Server v10.8.3. A similar situation happened earlier this year when the machine froze up and I was forced to cold boot. Again, the configuration file was broken and all information about our licenses was lost that time. That time we were running Retrospect 8.2.0 (399) on the same Mac mini with Mac OS X Server v10.6.8. The Config80.bak file was also corrupted in both instances. Thanks to twickland on the forums, I was able to resolve this both times using the following procedure. This relies on you having a back up your backup server and the license keys handy: Make sure all machines that Retrospect mounts through NFS are powered on and have the NFS service running (only applies if you use NFS). Stop the Retrospect engine. You will need to restore the configuration file from the backup of the backup server. First, make copies of /Library/Application Support/Retrospect/Config80.dat, /Library/Application Support/Retrospect/Config80.bak, and the catalog file for the backup of your backup server just in case. Delete the original Config80.dat and Config80.bak files. Retrospect now has no configuration. Start the Retrospect engine and open the console. The console will prompt you for the license key. If you use NFS mounts and your backup server media set has members on these mounts, you will need to re-add them. In Sources, click Add and in the Share tab of the dialog, enter: Share address: nfs://my.lovely.server/my/lovely/exported/directory Connect as: Registered User Name: [username for the user on the backup server] Password: [password for the user on the backup server] In Media Sets, click on Locate and open your catalog file for the backup server. Initiate a restore using the icon on the top-left of the Retrospect console. Restore /Library/Application Support/Retrospect/Config80.dat and /Library/Application Support/Retrospect/Config80.bak to some location. Close the Retrospect console and turn off the engine. Copy the restored configuration files back into /Library/Application Support/Retrospect. Turn on the engine, and open the console. Hopefully all is well. So that was a solution for me. The big question is why is the configuration file so fragile? Why does the server not write to a temporary file and then at safe points replace the main configuration file with the new configuration? And why is the server so bad at determining that the configuration file is broken? These seem like simple problems to fix and I personally have wasted hours on this problem the first time around.
This is not a duplicate topic. I created a post here: http://forums.retrospect.com/index.php?/topic/150552-retrospect-configuration-gets-corrupted-too-easily/ 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.
Retrospect 9.02 (107) /Library/Application Support/Retrospect/ I noticed my Config80.dat is a whopping 157 MB My Config80.bak is 930 kB They are both 'last modified' today. If I quit and replace the .dat with the .bak and launch Retrospect it seems that my settings and scripts and stuff are correct, but I am unsure what to look for. Should I replace it? What will I lose?