Jump to content

All Activity

This stream auto-updates     

  1. Today
  2. DavidHertzberg

    PSA: Wikipedia article on Retrospect going away in current form

    After 3 tries, DovidBenAvraham has created a sufficiently neutral-sounding Request for Comment section on the "Backup" article's Talk page that several other Wikipedia editors have commented. All of them so far, plus DBA, have reluctantly voted to split off the "Enterprise client-server backup" section into a separate article. DBA's justification is that only doing the split-off will allow him to file an Administrators' Noticeboard request to ban Pi314m from editing the new separate article. Pi314m promised in his own voting statement to act as if such a ban is in effect, but DBA pointed out that the promise is worded so as to likely expire within a day. Anybody who is already a Wikipedia editor can come over to the Request for Comment section on the "Backup" article's Talk page, in order to vote on and/or discuss DBA's request. Actually you don't already need to be a WP editor, but by the time you learn to use the idiosyncratic WP editing system DBA will have already filed his Administrators' Noticeboard request—so your input may not count for much.
  3. Last week
  4. DavidHertzberg

    multicast on wrong interface

    zz-pdb, Both possible versions of your problem have been discussed in a Mac 9+ Forums thread. Here's my post that distinguishes both versions; you can look forward or backward in that thread to find a possible solution for your particular version. However if it is indeed your "client" machine that has two network interfaces, this Knowledge Base article doesn't say how to specify the "ipsave" command for the Linux Client software. Page 554 of the Retrospect Windows 16 User's Guide says: If that doesn't help, here's why and how to submit a Support Request for a bug. P.S.: I had forgotten to suggest that you Add Source Directly, specifying its fixed IP address on your LAN. I see that this option in adding "client" machines, which solved a two-year-old problem I had with -530 errors, is called Direct Access Method on pages 294 and 296-297 of the Retrospect Windows UG. Since Subnet Broadcast—which also to some extent bypasses Multicast—may solve your problem if it is your "backup server" that has two network interfaces, you probably should read pages 294-299 in the UG. Either way you'll need to Remove and re-Add your "client" machine.
  5. I have a Linux (Ubuntu 18.04 LTS) system that has two network interfaces, and its doing its multicast advertising on the wrong one. Is there no config file or anything for the Linux client so that i can change the interface or even just have it not advertise?
  6. While it's a good idea to enable Full Disk Access in Mojave to allow Retrospect to back up all the files on a machine, it'll rarely have an impact on external volumes. Privacy mainly acts on parts of the user folders -- ~/Library/Mail, ~/Library/Cookies, etc -- and any Time Machine Backup folders. It generally won't be in play when backing up a mounted NAS volume unless that volume has been set as a TM backup target, *possibly* if you're redirecting User directories to the (non-startup) volume, or something similarly funky. In fact, "Error -1101" is almost certainly not a Full Disk Access issue, since that generates an error when scanning -- an error that includes the path to the folder, text to the effect that 'Retrospect has detected it is not listed under "Full Disk Access..."', and a link to the KB article explaining how to fix the problem. In both cases above it is most likely a name, permissions or volume integrity problem. But the various flavours of NAS and client implementations of SAMBA/AFP can make this difficult to troubleshoot...
  7. Thank you, CherylB. Would you believe that same article, titled "macOS Mojave – Application Data Privacy", has been in the Knowledge Base under "Top Articles" since 16 October 2018? Great article titling, Retrospect engineers! P.S.: CherylB, how about your creating a Support Case suggesting that Retrospect Inc. change the KB article's title to something like "macOS Mojave – Application Data Privacy and Error -1101"? Here's why and how to do that.
  8. In reference to Madison437 and the error code -1,101 (file/director not found) I found this helpful article on the Retrospect support site. The update to Mojave (10.14) has a new security feature. You need to open System Preferences > Security & Privacy > Privacy tab > Full Disk Access. Click the lock to authenticate. Now go to Finder menu and Go > Go to Folder. Enter: /Library/PreferencePanes and drag the Retrospect Client over to the Full Disk Access window then /Library/Application Support/Retrospect and drag the RetrospectInstantScan to the Full Disk Access window Attached is the document where I found this info. Retrospect: Full Disk Access Mojave .pdf
  9. PaulMikeC

    Event Handlers

    Hi Nigel, That '/dev/console' idiom seemed to come closest to what the tilde ('~') char in the original sample script was meant to do. As you pointed out though, it could end up varying too much, depending on login patterns. That's why, in the second parenthetical '{EDIT:- …}' in my post of 25th May, I too had suggested that it might be easier to simply hard-code the log pathname. {In fact, I myself later switched to doing just that, so my log file is always on the main user's Desktop. I'm now thinking about incorporating some kind of automatic log rotation (perhaps similar to what the OS does for system logs) with zipping, etc.} I do also hope that you got your Slack integration to work! 🙂 —Paul
  10. Earlier
  11. Ok, have it in writing.
  12. Nigel Smith

    repetitive SIGSEGV error

    Glad it's sorted -- the rogue attempted startup, anyways. That "...localsnapshots" volume is cruft left over from previous OS's Time Machine -- 10.14 doesn't use it any more. As to why it's being scanned -- you say you're only backing up a couple of directories from the User folder on the system drive. If they are defined as Favourites then nothing else should be scanned (assuming you've tagged them appropriately for your script etc). If you are doing it via Rules, eg. "back up files on this computer if their path matches /Users/..." then Retrospect has to scan every file and folder on the machine looking for matches. That will include other mounted volumes if your tags etc are set that way. Needless to say, for fast scan times when you are only backing up a subset of a computer's data, Favourites are your friend. Bonus tip 😉 Step away from the Console log! There's ridiculous amounts of guff in there these days, often with multiple updates a second. Step over to the Eclectic Light Company for a primer on using "log show" and how to isolate log items by time period, use predicates to filter by event or program, etc. I haven't tried their Consolation log viewer myself, but you might find it more friendly than using Terminal.
  13. I stopped the "sacrificial" script early 8 June morning after 19 minutes when it issued "!Error reading snapshot record ...", which it shouldn't have been doing because the script specified Recycle. I did a Rebuild of "Media Set White" from portable HDD "G-DRIVE White" , and the "real script started to run OK—until it failed with a -519 (network communication failed) error after 4 minutes when I absent-mindedly shut down my MacBook Pro "client" preparatory to going back to bed.
  14. After I downloaded Retrospect Mac 16.1.2.102, both the Recycle backup scripts—the "sacrificial" one and the "real" one—started to run OK early 1 June morning to "Media Set Red". However, after the "sacrificial" script ran OK, two things happened while the "real" script was running: The backup of my MacBook Pro "client" failed after 1.5 hours with -559 (network connection timeout). The script continued with my local drives. After the script backed up and compared my late friend's local "Macintosh HD" and backed up my local "Macintosh HD SSD", it failed with -116 (volume doesn't exist) when I gently (I thought) picked up "G-DRIVE Blue" to look at its bottom masking-tape label one minute into the compare.
  15. I originally posted this on 25 May (as shown in the right-most column of the thread listing), but it was deleted by Retrospect Inc.—evidently sometime after 6 June 2019 03:35 when I copied it as an Additional Note to Support Case #67777—because they considered a final paragraph I've now omitted to be overly critical of Retrospect Inc. engineers. This happens, as I warned you in the third paragraph here! Both the Recycle backup scripts—the "sacrificial" one and the "real" one—ran OK early 25 May morning to "Media Set Blue". Of the possibilities discussed here up-thread: I simply pushed the USB3 cable firmly into "G-DRIVE Blue" late 24 May morning; I didn't take special precautions. This wasn't the week for my cleaning lady, but last week—when the scripts also all ran successfully—was. The USB3 cable I used was the same one that was used when I had problems two Saturdays ago. I had upgraded my "backup server" to Retrospect Mac 16.1.0 before last Saturday's run, and I upgraded it to 16.1.1 on Thursday. So possibility 3 is the winner. The Retrospect Inc. engineers must have fixed the Recycle bug in 16.1.0, even though there's no mention of that in the cumulative Release Notes. I can't believe they released 16.0 without having tested Recycle for APFS-built Media Sets; I too would be ashamed!
  16. zz-pdb, I sincerely doubt that it wouldn't work on AMD processors, but I'm a Retrospect Mac administrator—and all Macs manufactured since 2006 have Intel processors (before that they had IBM PowerPC or Motorola processors).. Here's why and how to file a documentation request. P.S.: Here's the most recent post (from 2014) I could find where the OP says he is running Retrospect on an AMD CPU. Here's an 8-month-old post where the OP is having the same problem as jgaiche reported in 2014 but is running Retrospect Windows 15.6 on an Intel CPU. FYI, here's a post from farther down x509's 2018 thread where he recounts Retrospect Tech Support's response to that same problem, which AFAICT will only be resolved for Retrospect Windows administrators by the introduction of the glorious Web-based Management Console.
  17. Regarding Retrospect server: On the System Requirements page ( https://www.retrospect.com/en/support/kb/system_requirements_win16 ), it says " Intel processor (64-bit) with one or more multicore processors ". It sounds like it wouldn't work on AMD processors. Is that really that case? If AMD is ok maybe it should be changed to x86_64 or something.
  18. minidomo

    repetitive SIGSEGV error

    Thanks, Nigel! I used the sudo commands you listed and the SIGSEGV error immediately stopped showing up in the Mac's console log. Now that I have a meaningful system log again, I can go back to researching my non-Retrospect related issue.
  19. DavidHertzberg

    PSA: Wikipedia article on Retrospect going away in current form

    I've noticed a recent rapid uptick in the number of views of this thread. I'm guessing that's because a number of you have noticed drastic changes to the ""Backup"" article, including deletion or total-dumbing-down of two paragraphs in the "Performance" sub-section of its "Enterprise client-server backup" section (described here). DovidBenAvraham is now trying to remove the article from the clutches of what he and I would describe as a "neatnik near-nut-case". If any of you are Wikipedia editors, please don't interfere at this stage—which consists of getting a Third Opinion from a WP outside volunteer. To quote DBA [edited slightly]:
  20. Thanks Lennart. I was unaware of the power of a copy backup script and that I could select certain backups and move them from one media set to another. Looks like just what I want to do.
  21. DavidHertzberg

    repetitive SIGSEGV error

    Thank you, Nigel Smith, for suggesting a problem explanation—launchd—I didn't know anything about. minidomo, did you inherit and/or upgrade this Retrospect installation? minidomo, read all pages 198-204 in the Retrospect Mac 15 User's Guide. "launchctl on the Mac" on pages 203-204 discusses what Nigel has diagnosed, with a slightly different (but possibly out-of-date, because the chapters after "What's New" in the UG haven't been updated in years) solution.
  22. Nigel Smith

    repetitive SIGSEGV error

    launchd still thinks it should load InstantScan, even if you've turned it off. Try the following in Terminal to stop launchd from trying to load retroisa now, and turn if off for the future: sudo launchctl unload /Library/LaunchDaemons/com.retrospect.retroisa.plist sudo defaults write /Library/LaunchDaemons/com.retrospect.retroisa Disabled -bool true Then check to see if it's worked: sudo launchctl list | grep -i retro ...and, with any luck, you'll see just retroclient and updater listed and not retroisa. How are you choosing those folders -- are they "Favo(u)rites", or are you using rules?
  23. You could first use a "Copy Backup" script, to copy the backups you want. Page 137 in the User's Guide. http://download.retrospect.com/docs/mac/v16/user_guide/Retrospect_Mac_User_Guide-EN.pdf The you could remove the backups from the old Media set. Finally you can run a Groom Script to retrieve the space from the old Media Set.
  24. The title mostly says it all. I've got multiple destination media sets and run multiple proactive scripts so that multiple clients can be backed up at the same time (different activity threads) but I've done a poor job of balancing the space needed on the media sets (all are disk sets). I know that I could recycle a set and start over, but I'm loathe to do that. Is there a way to either move a selected client backup from a media set to another media set or less desirably to remove a selected client backup from a media set thus freeing up additional space?
  25. DavidHertzberg

    File properties changed - Did Retrospect

    x509, Look at pages 362-367 in the Retrospect Windows 16 User's Guide, and see if you can figure that out. You might have to check-mark the Set Archive Attributes option per page 364, Restore those photo files, and change the Windows date values for them again to cause the files to be backed up again. Then again, I might not know what I'm talking about. P.S.: Wait a second, aren't those file date values stored in the Snapshot entry for a file? If so, then Retrospect would have updated all of the entries on the next Backup run. I know that because, as a holdover from when I was having a problem with -530 errors, I schedule a "sacrificial" script run before each "real" Backup script run. The "sacrificial" scripts specify the No Files Selector (Rule for Retrospect Mac)—meaning no files are actually backed up, but they spend about 3 minutes "creating snapshot" and "copying snapshot"—evidently for each file on my MacBook Pro's SSD. And yes, "Windows Selector Conditions" on page 440 of the UG says: P.P.S: For Retrospect Mac administrators who may be reading this, Snapshots are the "crazy Mrs. Rochester in the attic we're not supposed to talk about". Back around 2000, first Unix-based OSes and then Windows developed this capability which the industry has termed a "snapshot". Thus when Retrospect Mac 8 was developed in 2008, EMC documentors decided to drop the use of the term "Snapshot" for a different capability that had been in Retrospect since the late 1980s; however the terminology in Retrospect Windows has never been changed due to "unfortunate events" in 2009-2010. DovidBenAvraham used to have this described in the Wikipedia article, but other meanie WP editors made him remove this as Original Research. So you'll have to sneak over and read about Retrospect Snapshots on page 31 of the Retrospect Windows 16 User's Guide. But don't talk about them, even though you can hear "Mrs. Rochester screaming" every day in messages issued by the Retrospect common underlying code. "Mrs. Rochester" doesn't "burn the house down" as in Jane Eyre; in fact Snapshots are a vital part of Retrospect Mac as well as Retrospect Windows operations. Pages 229-230 of the Retrospect Mac 16 UG say "Retrospect now uses the term backup to include both session and Snapshot data." BTW, APFS offers "snapshots" in the industry-standard sense, so the EMC documentors were prescient.
  26. I just changed the various Windows date values for a range of photo files, to correct for the camera clock being set for the wrong time zone. Retrospect did not back up the actual files again, since the contents (photo RAW files) were not changed. But did Retrospect back up the new Windows file date values? x509
  27. That's what I had to do. x509
  28. DavidHertzberg

    repetitive SIGSEGV error

    minidomo, Am I correct in thinking that the messages you refer to in your third paragraph immediately above are in the macOS Console log, not the Retrospect log? [assumes Indian accent] You should PM me your credit card information, so that our technical specialist can remove a very serious virus infection from your Mac! [ drops Indian accent] Seriously, maybe you should stop looking at your macOS Console log. I assume you've checked your Retrospect scripts to make sure that "Fridge" and/or its folders are not check-marked as Sources or used as Destinations in any of them. My guess is that you're getting those messages either because you're still running Time Machine, or at because at one time you specified a Time Machine Backup Disk. If it's the latter, you should go to System Preferences->Time Machine, click Select Backup Disk, click the "Fridge" disk that's shown there, and then click the Remove button to remove it. If it's the former, then you should know that Time Machine doesn't work with an APFS-formatted Backup Disk (which is what the messages are telling you)—so reformat "Fridge" with HFS+ (which you may not be able to do if it's an SSD). If you're not running macOS Server or Windows Server on any of your machines, then Desktop Edition is all you need. As I've delicately alluded to in this post and the following one in another thread, Retrospect Inc. is worried about reduced Edition license revenue because many installations have substituted Linux-based file servers for macOS Server—which doesn't provide much anymore beyond what you get for free with macOS 10.14. An upgrade to Retrospect Mac 16 Desktop Edition will cost you US$70-75.
  1. Load more activity
×