Jump to content

Search the Community

Showing results for tags 'corrupted'.

The search index is currently processing. Current results may not be complete.
  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Announcements, News and Resources
    • Latest News
  • Windows Products-Retrospect
    • Professional
    • Server, SBS and Multi Server
    • Device and Hardware Compatibility-Windows
    • Exchange Server Add-On Support
    • SQL Server Agent
    • Linux, Unix and Netware Clients
    • Express for Windows
    • Product Suggestions-Windows
  • Mac OS X Products-Retrospect
    • Retrospect 9 or higher for Macintosh
    • Retrospect 8 For Macintosh
    • Retrospect 6: Desktop, Workgroup and Server for Mac OS X
    • Device and Hardware Compatibility-Mac OS X
    • Linux Clients
    • Product Suggestions-Mac OS X
  • Macintosh OS 9 and Earlier-Retrospect
    • Express, Desktop, Workgroup and Server for Pre-OS X
    • Device and Hardware Compatibility Pre OS X
  • General Discussion-Retrospect
    • Networking and Clients
    • Strategy, Scripts and General Use
    • Retrospect iPhone App
  • Retrospect 8.x for Mac
  • Retrospect 6.1 for Mac
  • Retrospect 7.7 for Windows
  • Retrospect 7.6 for Windows
  • Retrospect Express
  • General Discussion

Categories

There are no results to display.


Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 1 result

  1. 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.
×
×
  • Create New...