Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 12/22/2018 in all areas

  1. 1 point
    Here's a thread I just found, entitled "Disk Media Sets Have Wrong Free, Capacity Columns", discussing the problem for Retrospect Mac 9. If you search the cumulative Release Notes for Retrospect Mac, there are several entries containing the word "capacity". However the only one with much relevance seems to be "Fixed: Media Set available capacity lists correct values (#5370)" for the Retrospect Mac 12.0 Console.
  2. 1 point
    Sorry, Lennart_T; I termed you a "now-two-Retrospect-variant-expert" only to describe what I thought was your work history. I thought that you had had a long-time job that included administrating a Retrospect Windows installation, and that you were then laid off and found a job that included administrating a Retrospect Mac installation. I didn't realize that you have Retrospect Mac at home. Whatever the historical reason, you certainly are an expert in both variants of Retrospect. I rely on you to deal with many of the difficult administrator problems posted on these Forums, since I have only used Retrospect Mac (versions 3 through 6, then versions 12 through 15) for my home installation. Thanks.
  3. 1 point
    We could not bring the hard drive back to life. Lennart_T suggested to "Repair" the media set in Retrospect which I ran yesterday. Today I am happy to report the repair was the correct fix and I have a backup for the entire lab. Thank you Lennart_T Once we have the hard drive for the failed computer replaced it will be added to the backup schedule.
  4. 1 point
    It's during the matching. The first thing to try is to repair the hard drive on Akumar's iMac, but I don't really think it would help. At least it can't hurt. https://support.apple.com/guide/disk-utility/repair-a-disk-dskutl1040/mac If that doesn't help, try to "Repair" the media set (in Retrospect). If that doesn't help, try "Rebuild" the media set (in Retrospect).
  5. 1 point
    No, don't do a Copy Backups, because it will only copy the most recent backup of each source unless you have specified a number of snapshots in your Grooming policy—per this 2016 post by a Retrospect Inc. employee. Unless your Copy Media Set run finished just before copying those backups, following up with a Copy Backups run will leave backups un-copied. Just delete the stalled-run data, Rebuild the destination Media Set, and run the whole 15-hour Copy Media Set again. Sorry to be the bearer of bad news.
  6. 1 point
    bradp015, I agree that it looks as if you have enough space on "4T HD" for another copy. The one thing that occurs to me is that you have two "Retrospect" folders on that drive. even though one of them is underneath the "NO USE SFA 3SAFE 4t 111116" folder. IME the parts of Retrospect that deal with creating Members on disk drives are programmed to either detect existing "Retrospect" folders or to create new ones. I'd hazard a guess that those parts get confused when there's more than one "Retrospect" folder on a drive. I'd suggest that you Finder-move the "SFA 3SAFE" folder that's two levels inside the "NO USE SFA 3SAFE 4t 111116" folder so that it—and its subsidiary "1-SFA 3SAFE" folder—are directly within the "NO USE SFA 3SAFE 4t 111116" folder, and then Finder-delete the "Retrospect" folder that the moved folder used to be underneath—along with the "Retrospect" folder's contained 0-byte "Backup Media" document. If you ever need to put the moved copy of the "SFA 3SAFE" folder back into action, you can first re-create a "Retrospect" folder and then Finder-move that "SFA 3SAFE" folder back inside it. Come to think of it, maybe the 0-byte "Backup Media" document is a marker to tell Retrospect that the "Retrospect" folder that contains it also contains a Media Set Member folder. If so, it would explain why Retrospect would get confused when it found more than one "Retrospect" folder containing a 0-byte "Backup Media" document on the same disk volume. Yes indeed, that's the sort of kludge I might have devised myself back when I was an applications programmer.
  7. 1 point
    We have released a patch that users of Retrospect 14 and earlier can use if backups incorrectly show a deferred status. https://www.retrospect.com/en/support/kb/deferred_date_on_mac You will install a new Retrospect console and continue to use your earlier Retrospect Engine. This fixes the issue without purchasing an upgrade.
  8. 1 point
    bradp015, You fail to understand the overall idea, which is that you will run a Copy Media Set script once and then run a Copy Backup script daily. I don't have time to write a post describing the procedure just for you, but here is a post I made in September 2016 describing a superset of that procedure—one for creating and maintaining a running copy in the cloud of backups to a local Media Set. In steps 1) through 6), ignore anything concerning Grooming or a cloud account—which means you can essentially convert steps 3) and 4) into whatever it takes to set up you new local duplicate-of-the-original Media Set. In both steps 5) and 6), don't check No Verification unless you like living dangerously (cloud providers are supposed to have such error prevention that lengthy-and-expensive verification isn't necessary). Ignore step 7).
×