Jump to content

karma

Members
  • Content count

    91
  • Joined

  • Last visited

Community Reputation

3 Neutral

About karma

  • Rank
    Occasional forum poster

Recent Profile Visitors

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

  1. Thank you for the information and the link to that lengthy previous discussion. One thing I am concerned about: as mentioned in Support End-of-Life Announcement for Mac OS X 10.3, 10.4, and 10.5, I have one machine running 10.4.11 that I still would like to be able to backup and access backups from; unfortunately I have some old apps and data in use that require running in Classic (!). I think you mentioned in an earlier post that you also had some ancient machines, so how do you deal with it? Is there some way to have both 15 and 16 installed, and just use 15 for the 10.4 Mac? Also, if I stay on Retrospect 15, and backup an AFPS volume, if I disable Instant Scan for that volume will it at least work well enough to use it? I didn't digest all of the details in that earlier post yet...
  2. I finally updated one of my Macs to Mojave with APFS. All my other Macs here are stil HFS+. I am currently still running Retrospect 15 on my server machine with Sierra. Can this setup backup APFS volumes? Have there been improvements or fixes in Retrospect 16 that relate to APFS? Thanks!
  3. I guess I didn't phrase that correctly. I realize it would be a "new volume", but my question was really "would Retrospect back up the whole thing again, or would it be smart enough to know that even though the Volume name had changed, the files had already been backed up, and it would only back up the changed files." So thanks, it appears that you are both saying that "it will not back up the files a second time."
  4. If you had an HD as a volume in a backup script (let's say it's got 500 GB of data on it), and you were to rename the HD, and then modify the script to include it, would Retrospect treat this as a new backup volume and backup the whole thing the first time (i.e. 500 GB), or would it somehow "know" that this is the same as a volume that has already been backed up and only perform an incremental backup?
  5. I recently upgraded from Retrospect Desktop 11.5 to 15.6.1. Everything seems to be working, but I see these strange errors in the LOG, after each backup script is performed: Usually just this: [*] UPreventSystemSleep: IOPMAssertionCreateWithName failed, err = -536,870,208 Sometimes this: [*] soccSend: send failed, err 32 [*] Captured signal SIGPIPE! [*] UPreventSystemSleep: IOPMAssertionCreateWithName failed, err = -536,870,208 Any idea what these mean? I do have it set to send me emails after each script is run, and I am getting them, so I don't know if it has to do with emailing.
  6. It was a data recovery tool named DiskDrill.
  7. I was able to figure out which program installed it by looking in var/logs/install.log. It wasn't Retrospect.
  8. Thanks, I can't ever recall seeing this before... I wonder how it got installed....
  9. So I finally bit the bullet and updated from 11.5 to 15.6.1 (because of the Deferred issue). I just updated a Mac Client by running the Client Installer. Now I see, in my System Preferences Panel, a Pane for something named FUSE. Is this installed by Retrospect, and do I really need it? Some discussions on the net indicate that this extension is problematic...
  10. I currently have Retrospect 11.5 Mac. Back when I had 6.1 for Mac, I backed up some data to some optical disk sets - in other words, spanning multiple DVDs. So I have the DVDs, and I have the catalog files stored on one of my hard drives. How can I add those catalog files into Retro 11.5 so I can access them and read the data from the DVDs? Thanks.
  11. I also have now been having this problem for several weeks, using Retrospect 11.5.3. Backups are working nightly, but cannot get to Dashboard. Doesn't anyone working for Retrospect have anything to say about this?
  12. Can Retrospect 11.5.3 (and Retrospect Client for Mac 11.5.2.104) be used to backup a Sierra 10.12.6 client?
  13. I had this same problem recently. Hanging on various .cdt files that cannot be found doing a search on the computer. After some research I discovered that a .cdt file is related to iCloud. In my case, I can directly tie this to the fact that I turned off iCloud on the computer in question, and started getting these hangs while backing up the computer immediately after. I fixed this by deleting the computer's ~/Library/Mobile Documents.xxxx folder (xxxx is a random number, and this is where the .cdt files live, even though they can't be located by a search), and the ~/Library/Application Support/Ubiquity folder (following some instructions in a related google thread), and restarting the computer.
  14. I generally make 2 sets of the archive onto DVDs - one for storing off site, and one for storing here. And then I free up the massive amount of space on my HDs that the files are taking up. Isn't that the point of an archive? I must admit that I have not really examined that idea before. I'm so used to making DVD archives for years. But having thought about it (thanks for bringing it up), USB sticks do sound like a decent alternative - even preferable. They are not very expensive anymore, you can store a whole project on a 32GB or 64GB stick for around $20 or $40 (vs about $16 or $35 for dual layer DVDs, so it's only slightly more expensive) and you could store them in one of those plastic binder pages with the 9 or 12 little pockets and have multiple sticks in a single binder. The data on a USB stick would be far easier to access than a Restrospect archive spanning multiple DVDs. Although I do worry about the dependenbility of the USB sticks, as well. I was searching online for some to buy, and there are many reports of failures. Hard to know which brand to buy...
  15. That's kind of a strange answer - sure, I'll need a working DVD player to read them back in the future. If I had been backing up to hard drives 10 years ago, and keeping those around, I'd still need working SCSI interface cards or whatever the hell obsolete connectors were being used back then. If it's "highly debated", that would imply that one camp thinks the longevity is fine. Besides, let's say I store a bunch of archives on a single HD. Many different 50GB archives of projects. If the drive goes bad, I lose my entire collection of projects. If a single DVD goes bad, I might lose one project. I trust DVDs for archival more than I do hard drives.
×