Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


jweisbin last won the day on April 14 2014

jweisbin had the most liked content!

Community Reputation

2 Neutral

About jweisbin

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
    Not Telling

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. jweisbin

    media group bug

    I have been having issues with media groups - both cloud and disk based. Retrospect thinks the media is full long before it actually is. Repair does not help. Retro version 17.0.2 on Mac OS X 10.11.6.
  2. Retrospect 15.5, on Mac Pro running OS X 10.10. Cloud backups to Amazon S3 work great, but backups to Backblaze B2 fail with many "lost connection" errors. Is there a trick to getting Backblaze to work? It's much cheaper than S3, although quite a bit slower as well.
  3. Just updated from Retro 15.1 to 15.5, on Mac Pro running OS X 10.10. Retro won't backup to a new blank, erased tape - says it's part of a backup set. Tried erasing a few times, tried restart, etc. Still no go. How do I fix this?
  4. Retro 15.1 (upgraded from 15.0) on Mac 10.11.6 Server. After updating, the server spontaneously restarts itself every few minutes. Had to go back to version 15.0, which seems stable. In addition, when upgrading the server on every version since 9, the installer says that it failed, but it apparently succeeded. And this is on multiple different systems. Can't this be fixed? I can't believe i'm the only one seeing this.
  5. Retrospect Server 14.1, running on Mac OS X 10.9.5 Server. Retrospect client 14.0.1 running on Mac OS X 10.12.6. Suddenly the server sees no clients when trying to add clients (from default interface using multicast). Existing clients are still in list, but yesterday I uninstalled and reinstalled one client. When I I tried to refresh the client, Retrospect reported "wrong client". So I deleted the client and re-added it directly via it's IP address. Now Retrospect sees only that client's boot volume, no others, even after a refresh.
  6. jweisbin

    "backup client reserved" Mac v14.0

    Yes, I did post to the wrong forum, sorry about that. Can this thread be moved?
  7. I have one client out of many for which Retrospect 14.0 running on a Mac server (OS X 10.9.5 server) keeps giving "backup client reserved" message. the only fix is to uninstall the retrospect client and reinstall it, but I've done that repeatedly and the problem returns. There is another backup client running - ChronoAgent, but I have that running on other similar machines which don't have this issue. Is there a fix?
  8. For some reason I was under the impression that you could backup to multiple backup sets at same time. But I can't find anything in the documentation. I thought I would set up a disk backup set and a tape backup set that would be perfectly in sync. I set a script to backup to those two media sets, but when I run the script it asks me which media set to back up to. What am I missing? Do I first have to do a copy media set from the disk to the tape?
  9. Uninstall and reinstall worked. Apparently, the latest uninstaller deletes retroclient.state on its own.
  10. Recently updated from 13.0.1 to 13.5. I have one client for his mounted volumes used to show up but now appear with the missing "~" mark. I tried to refresh, no change. Then I deleted to source and set it up again, and now Retrospect only sees the boot volume. How to fix?
  11. jweisbin

    Retrospect 11 damaging tape drives?

    yea, tried all that, tapes won't come out. I'm just suspicious that not one but two drives failed within a week of each other and right after upgrading.
  12. I have one LTO-5 drive (HP Ultrium) and two LTO-4 tape drives (HP Ultrium 1760 SAS). Shortly after upgrading to Retrospect 11 both LTO-4's refuse to eject the last cartridge used. I have a suspicion that Retrospect 11 somehow caused this. Anyone else seen this happen?
  13. this is inside the office, client and server are both behind the firewall. Besides, it can back up from the client, so why wouldn't be able to write to the client? Also, this problem only surfaced in version 11.