Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

1 Neutral

About cjd

  • Rank
  1. In the menu bar: Retrospect -> Preferences In the Preferences window, click "General" at the top. In the second section of the General Preferences, look for "Allow: " x "Past Activities" Change the number in the drop-down menu to something reasonable, then close the preferences window. This is critical; the deletion doesn't occur until you actually close the window.
  2. It appears that the problem was caused by there being too many Past Activity logs stored. Clearing out the backlog also reduced the size of the Config80.dat file from 8.5 GB to 56 MB. If attempting to delete a large number of log entries at the same time, Retrospect does seem to hang for a long time, but it will recover. In order to quickly reduce the number of stored entries to a manageable level, changing the value in Preferences->General->Allow x Past Activities seems to do this automatically and much more quickly. NOTE: The program won't actually execute the deletion of logs until the Preferences window is closed, using the close box or cmd-W.
  3. Perhaps I should define my terminology. "The beachball", at least for me, refers to what the cursor turns into when an application stops responding to events. "The pinwheel", for me, is a loading icon that appears throughout OS X when "normal" loading is taking place, such as when the system is starting up or shutting down. It looks like this: Retrospect does not display the beachball cursor. It also doesn't become unresponsive while waiting to list sources or source contents; it's completely responsive and it's possible to back out of the operation instantly by clicking cancel or "x". What it does is display this gray rotating "waiting" thing, which I usually call "the pinwheel" to distinguish it from "the beachball". These are screen captures of the places where the delays occur. Both are under the Sources pane in the console application. After clicking "Add": (The Locate command has the same response as above) After clicking "Browse" or "Add Favorite" for a particular source: I tried a safe boot/normal boot sequence, but nothing has changed. I assume the reason to check Activity Monitor is because it would show if the Retrospect or RetroEngine processes were not responding to system events. Even when in the middle of this delay, the two processes are responsive, although the CPU usage for the Retrospect console application shoots up to 90% (which doesn't bog down the system, as it has 4 cores). Here is the output of the Sample Process command on the Retrospect console from Activity Monitor: Sample of Retrospect.txt
  4. Nothing else is sluggish. Nothing is suspicious in the console either.
  5. This has been consistent for several weeks, through three or four restarts of the computer, and numerous restarts of the Retrospect server process. The problem has persisted through a complete shutdown and restart of the entire network (all power removed and restored).
  6. All interactions with sources, local and remote, are very slow. For example, when the "Add Favorite" button is clicked, the sheet pops out, then displays a pinwheel and "Accessing Source" for between 10 minutes and an hour, before finally listing the source contents and allowing favorites to be added. Once the windows is accessible, adding a particular folder as a favorite is also slow, but not unreasonable (10 seconds at most). Similar delays are present when refreshing a particular source, or when trying to locate or add new sources. The network is not particularly slow, nor are any of the remote or local sources. When a backup is initiated, Retrospect connects to the sources within 30 seconds, and the backups occur with reasonable speed (the wiring limits communications to 100 Mb/s, so network backups usually max out at ~400 MB/min, according to Retrospect). The Retrospect version is 11.5.3. Both the console and the server are run on the same computer. The computer is a Mac Mini (Macmini6,1) with a 2.5 GHz Core i5, 16 GB of RAM, running OS X 10.10.2.