Jump to content


  • Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About etracer

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
    Not Telling
  1. I find that after every reboot I need to stop the Retrospect server process and restart it (through the System Preferences panel) before it will reliably see clients. Sometimes doing the "locate" would work, but the stop/start always works. My guess is that the RetroEngine process is starting up too early before networking is fully established during system boot. In my case I'm running a 2010 Mac Pro and I have the two NIC's bonded - so your issue might be slightly different (although the symptoms are the same). Edit - The Mac Pro is running 10.8.5 (not OS X server).
  2. etracer

    Mavericks support?

    I haven't tried it yet, but Retrospect is supposed to support 10.9. http://retrospect.com/en/blog/2013/09/19/fall_release
  3. Same problem here. 2010 Mac Pro w/10.8.5 running Retrospect 10.5.0 (145). Proactive client is a Mac Book Pro also running 10.8.5 with the 10.5 Retrospect client. The RetroEngine process stays stuck at 100% even with no activity. Trying to stop the server through the system preferences fails (simply does nothing). The only way to stop the RetroEngine is to do a force quit in Activity Monitor. After restarting the engine will behave normally for a while and even perform proactive backups. In less than a day the RetroEngine will get stuck at 100% again. Note that even when it's in this mode, normal (non-proactive) backups continue to run.
  4. As I mentioned in an earlier reply to this topic... I see the yellow triangles and the log message "Remaining: X files; Y KB" (the X and Y values vary, but it's usually only 1-2 files) frequently while running normal backup scripts with no verification.
  5. Still nice throery but not the answer. I get the "yellow triangles" all the time on backups that don't even have verification enabled.
  6. etracer

    OS X 10.9 support?

    Thanks, that's good news.
  7. As the release announcement of OS X 10.9 is imminent, any official response on Retrospect 10 support for the new version?
  8. I've also determined that stopping and restarting the Retrospect server process (from System Prefererences) usually resolves the problem. So now I always try to remember to do this after a reboot. It's almost like the Retrospect server process is starting up too soon during system initialization and networking is not fully ready.
  9. Multiple stop and restarts of the server - no difference.
  10. No luck on changing the path to the media set. I even removed the media set from Retrospect, moved the path (simply renamed the containing folder) and then "located" the media set back into Retrospect. The frustrating thing is that Retrospect "sees" the media member and knows about the backups contained. It just won't use it for any more backups.
  11. Background: I have some Retrospect 10 disk media sets on an external RAID array. I needed to upgrade the disk array with more disks to expand its capacity so I first copied the Retrospect media sets (entire folder structure) off to another drive and then upgraded the array. After the upgrade was complete I copied back the media sets to the same path (disk name remained the same). In the console I relocated the catalog files (since it seemed to think it couldn't locate them. Now the media sets look normal, list the contained members and backups. The problem is that any time I try to use the media set the operation waits with a "waiting for media" message. I tried clicking the "choose media..." and navigating to the path where the media resides (in the same path it already lists when looking at the media set), but I can't get past the "choose media..." prompt. I even tried removing and re-adding the media set (by locating it on disk) with no improvement. So how do I make Retrospect able to use these perfectly intact media sets?
  12. Yes, the server and the clients all have static IP addresses. The clients were originally added using the browser (multicast query), not by manually specifiying a host name or IP address.
  13. I realize you created a related topic under the Windows section, but not this is also a huge problem for backing up Linux clients. This problem has existed since version 8 and I have reported it many times (including in this topic http://forums.retros...post__p__249571). I have cases where I'm backing up Linux clients over a relatively slow network link (to a remote office) and the building snapshot phase can take literally hours even though only a few files representing only KB's of data were actually backed up. The scanning/matching/backup phase takes a couple of minutes at the most. Just wanted to make sure this was on the radar and Linux clients were not forgotten.
  14. I've found a repeatable pattern where client connections fail with error -530 ( backup client not found) messages if the backup server (2010 Mac Pro 12 core / 10.8.3 / Retrospect 10.1.0 (221)) has been rebooted. Attempting to refresh the source (clicking the "Refresh" button at the top of the Sources panel) results in the popup window "Source unavailable or is in use". I've found that by causing a multicast to the network by simply clicking the add button (+) on the Sources panel causes all of the clients to show up as automatically found on the network. After causing this multicast search and then canceling out of the add source panel, the clients will then respond to backups and/or the refresh request. So there's something about the process of searching for clients on the network that then allows the server to connect to the client even though the client was always available. Just to repeat, this only seems to happen after the server machine has been rebooted. Once the clients can be found they seem to be fine after that. Some networking info as it may be related: The server and the clients are on the same subnet ( The netmask for all machines is (subnet range 192.168.0 - 192.168.7) The server is a 2010 Mac Pro (10.8.3) with both gigabit NIC's in a LACP bond (link aggregated) to a managed HP switch (maybe the bonded connection is relevant?) The server has no networking problems connecting to any other service/connection after a reboot other than the issue with Retrospect clients. The server is running 10.1.0 (221) and the clients are also 10.1.0 (221). The screenshot of the network panel in the Retrospect preferences is attached.
  15. I was going to post a similar question so this is a "me too" response. I noticed that the yellow "warning" triangles seem to correspond to "remaining" files that were apparently not backed up. For example from a local disk backup: Remaining: 3 files, 12 KB Completed: 1273 files, 829.9 MB, with 61% compression How do we find out what files were not backed up and why? OS X 10.8.3, Retrospect 10.1.0 (221)