Jump to content

Nigel Smith

Members
  • Content count

    61
  • Joined

  • Last visited

  • Days Won

    5

Nigel Smith last won the day on June 7

Nigel Smith had the most liked content!

Community Reputation

6 Neutral

About Nigel Smith

  • Rank
    frequent Poster

Recent Profile Visitors

271 profile views
  1. 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...
  2. 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.
  3. 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?
  4. Nigel Smith

    Event Handlers

    Just a note -- that returns the username of the "current active GUI user" (for want of a better term). So if "backup" logs in it will give "backup", if "admin" then logs in using multiuser switching (i.e. "backup" is still logged in but "admin" is active) it returns "admin" -- and if "admin" logs out (but "backup" is still logged in) it returns "root" because you are at the login window. May not be an issue for you with your setup but it would confuse the hell out of me... I tend to hardcode these things -- apparently /var/log is a popular choice for log files πŸ™‚ I'm glad you did! I've never got Script Hooks to work and had assumed the system was borked. Now you've shown otherwise I'll attack it again. Slack integration, here we come!
  5. I've not seen it in the manual but, to be fair, dual active NICs on a client isn't common and they can't document *everything*. Searching the KB for "bind" gets me that linked page as second hit -- although you have to be techie enough to know the term "bind" in relation to NICs and IPs... You don't always have to remove and re-add the client -- depends on how it was added in the first place. But it won't hurt to do so unless you are trying to preserve an easily-followed backup history (and, usually, you do this kind of shenanigans because you can't get any backup to begin a history with!). Connection not showing might be a client-version thing -- certainly works for me in e.g. 15.6.0 As to speed -- unencrypted will be faster than encrypted, fewer large files will be faster than a lot of smaller ones, and so on. Try your own tests and see where the bottleneck is, watch the network usage, CPU %s, and disk I/O rates at both ends, etc. And when you say encryption are you talking encrypted communications, encrypted backup set, or both? (IIRC, Chronosync offers encrypted comms but not the backup itself, instead recommending you use an encrypted disk if you want that sort of thing. But it's been a while...)
  6. Nigel Smith

    Selector doesn't work for only 1 Backup Script

    As promised. The Test Client: "NIG-PC" -- Windows 10 VM, Retrospect 15.6.0, with C drive and external E drive. Both drives had "Test_Data" and "Test_Data2" directories, each with a couple of text files inside. Server: Windows Server 2016, Retrospect Multi Server Premium v15.6.1.104 Client was added by Direct IP with "Volumes" tab "Client Sources" set to "Client Desktop" -- both C and E drives were visible A new disk-based Backup Set called "Filter_Test" was created A new filter called "Filter_Test" was created, initially blank and then edited as per the following screenshots After the filter was edited, an Immediate Backup was created: Source -- "NIG-PC"; Destination -- "Filter_Test"; Selecting -- "Filter_Test". The Preview button was clicked and, once the results generated, the screenshot taken. The Immediate Backup was then cancelled to clear any cached Preview and to force a re-scan for the next test The Results "Windows folder path exactly matches \Test_Data\" -- no drive letter, so nothing is matched: "Windows folder path exactly matches E:\Test_Data" -- no trailing backslash, so nothing is matched: "Windows folder path exactly matches E:\Test_Data\" -- drive letter and trailing slash included, matches only with "Test_Data" on E and not E:\Test_Data2 or C:\Test_Data: So, what about "matches pattern"? We know from the filter dialog tip that "* matches any or no characters and ? matches any single character", but x509 had no special characters in his filter yet still got matches. Let's see what we can find out, starting with a filter similar to x509's... "Windows folder path matches pattern \Test_Data" -- matches Test_Data and Test_Data2 on both drives: "Windows folder path matches pattern \Test_Data\" -- matches Test_Data only on both drives: "Windows folder path matches pattern E:\Test" -- matches Test_Data and Test_Data2 only on the E drive: "Windows folder path matches pattern st_Data" -- matches Test_Data and Test_Data2 on both drives: Conclusion Exact folder matching requires a full path, including the drive letter, and a terminating backslash, i.e. "E:\Test_Data\". The "matches pattern" condition includes invisible "*"s, both prefix and postfix, i.e. if you enter "st_Data" it is actually "*st_Data*". That may be what you want, e.g. the same folder name at different levels of the directory structure across multiple drives on a client, but could also greatly widen the matches beyond what was expected. As always, the more explicit you are the closer the filter results will match your wishes. Vagueness on "includes" can massively increase backup resource requirements, vagueness on "excludes" can result in important data being missed. So test, test, test -- and be careful out there! Note Yes this was all done with "includes" whilst x509 was having trouble with "excludes" -- that's simply because I think it is much easier to see none, one or two ticked boxes amongst a column of unticked in a fuzzy screenshot than to spot the gaps in a line of selected items. But the conclusions above also apply to "excludes", and it's simple enough to verify for yourself if you doubt it. Hope that helps someone!
  7. Nigel Smith

    Selector doesn't work for only 1 Backup Script

    I'm mainly going by (possibly wrong) logic and (possibly incorrect) Retrospect instructions... Windows Explorer and Windows Open/Save dialogs have a "current working directory" and "default working drive" (the C drive) -- for example, in an Explorer window address bar you can use full paths to go to a directory ("C:\Logs") but you can also use relative paths ("..\" will take you up one level from the currently shown directory). If you have a directory called "Data" on both C and D drives, typing "\Data" from any location on your system will always take you to C:\Data and never to D:\Data because there's an implicit "C:" before any path starting with "\". Retrospect Client (assuming you aren't defining volumes/favourites) runs at the "machine" level -- it can "see" all drives so, to reference a particular one, you must state which. I can do no better than quote (again) the tip from Retrospect's "Windows Path" filter dialog: Paths for FAT/NTFS volumes start with a drive letter and use backslashes (\) as separators, as in "C:\Data\". That might, perhaps, be clearer if it was written as: Retrospect path filters for FAT/NTFS volumes... Drive letters aren't exposed on networked systems because the "server" doesn't present them. In a UNC path, e.g. \\MyServer\FirstShare\TheFolder, you could consider the share name to be analogous to the local drive letter. It's just differences in the way Windows abstracts and presents absolute paths to directories/files accessible via various services. It's perhaps more obvious on Mac OS X, where every mounted volume including the system disk can be reached via /Volumes/<volume_name>. I'm trying to find a PC client to test against, but I wouldn't be surprised if you got the results you did because "match" requires a prefixed drive letter, while "match pattern" has an implicit "?:" at the start and so will match C:<pattern>, D:<pattern>, etc.
  8. Nigel Smith

    Selector doesn't work for only 1 Backup Script

    I can only comment that, as a Mac user, the total lack of consistency in Windows itself -- never mind other software houses' Windows apps -- gives me the heebie-jeebies... πŸ˜‰ To be fair, I've just fired up Windows RS Server and checked, and the tip states: Paths for FAT/NTFS volumes start with a drive letter and use backslashes (\) as separators, as in "C:\Data\". ...so it doesn't say it requires a trailing backslash, but does include one in the example. However, you originally said: ...which didn't include the drive letter. That will be mandatory since, unlike your PC's Explorer Address Bar or an app's Open/Save dialog, the Retrospect filter has no concept of "current drive" or "current working directory", so a "match" or "starts with" must begin with drive-letter-colon-backslash. And there's no reason not to include the trading slash, just in case... Still doesn't explain why it suddenly works when you change to "matches pattern" though (I had confused that with "contains", my bad...). If I get time later I'll try a couple of tests.
  9. By default, Retrospect Client will bind to the first available active IP address. In a dual-NIC setup (e.g. network card and wireless in a laptop) that "first available" can vary. So you'll need to tell the client which IP to bind to -- see this page for details. Obviously, only works for static IPs. Luckily it sounds like that's what you are using. That might be enough to get you going. Otherwise, could you re-post the problem but refer to machines as "clients" for the ones you want to back up and "server" for the one doing the RS backup? Like David, I'm getting a bit confused as to what's what!
  10. Nigel Smith

    Selector doesn't work for only 1 Backup Script

    I'm sure they don't -- but they aren't Retrospect! The Retrospect tool tip tells you how to how to do "path matches" -- you must include the drive letter and the trailing slash if you are matching a directory. I'm not saying it *isn't* buggy, just that you shouldn't assume it is if you haven't done things the way the software tells you to...
  11. Even without, that should still give you options -- e.g. to boot via a wireless network. And you should get a password dialog if firmware security has been set. So we're back to the standard fix -- zap the PRAM (Command-Option-p-r at startup and let it chime thrice, for those playing along at home). But only worth worrying about if, like me, you have an uncontrollable urge to pick at such things πŸ˜‰ Never heard of that one! I know a Terminal-fix to force a HS-SSD-HFS+ install but it's pretty geeky, hence the "dug their own hole" comment. I haven't tried it recently but I see no reason why the instructions here won't still work. Perhaps the download included that in its launch instructions. To be fair to Retrospect -- Apple's repeated incremental tightening of security, while laudable, has made "fully functional restores" very much a moving target for all backup solution providers. Even Time Machine doesn't often get it right (we regularly have to re-register third-party software, download drivers, etc), so what chance do the others have? And, given the huge number of potential scenarios, they can't test for everything and so have to rely on us to report back. Kudos to you for bothering, and let's hope they resolve it soon. But I would think that, when bootable restores aren't possible, restore to external HD then Migration Assistant is still a viable alternative.
  12. That would also worry me, because it should work and doesn't. Internet Recovery is a function of firmware. You should be able to boot to the Internet Recovery screen irrespective of network connection etc (although you might have problems after that e.g. if using a non-Apple ethernet adapter). But it can be blocked if you are using firmware security -- have you set a firmware password? Quick way to test would be to boot with the Option key held down -- if you go straight to the boot-disk choice screen you haven't, if you have to enter a password to get the boot-disk choice screen then you have. (Behaviour can vary with firmware version, but the preceding is probably the easiest and most consistent test.)
  13. OS 10.11.6 protects exactly *one* file in /Library -- com.apple.Boot.plist -- which wasn't your problem (unless the problem was over-vaguely reported by Retrospect). OS 10.13 and 14 include a bunch more files/subdirectories in /Library (but not /Library itself), which is why I was asking what version you were restoring to. It sounds like your original restore attempt was to 10.12, since you had an HFS+ SSD. Again, if you'll confirm I'll set a machine up and give it a go. Time Machine doesn't back up a bunch of files which an unfiltered RS backup *will* copy. I believe that, again, this varies by OS version. You can see the list in /System/Library/CoreServices/backupd.bundle/Contents/Resources/StdExclusions.plist ...and it may be that RS is trying to restore a file/folder into a SIP-protected area that Time Machine wouldn't have backed up in the first place! I'm losing track here, and you still haven't said what the OS version of the backed-up laptop was, but it *sounds* like you (eventually) had an 10.12 backup to restore to a 10.13 machine. Retrospect's recommended route for "OS on the new Mac is newer than the backed-up OS" is simply a less comprehensive description of your solution. So it seems to be covered, though perhaps not as fully documented as it could be. The only use-case I can see that is left are those who had an SSD, upgraded to 10.13 without converting to APFS, backed up, and are now trying to restore a 10.13 backup to a 10.13-enforced APFS disk. And if they had the technical knowledge to do the that "non-converting" upgrade then they should be able to get themselves out of the hole they dug for themselves...
  14. Not needed. Command-Option-Shift-R will do an Internet Recovery to the "as shipped" OS version -- including access to Disk Utilities and Terminal so you can nuke the APSF-formatted drive back to an HFS+ one. I don't know what the "Apple database problem" is, but I do know that MacTracker agrees with you as to the original OS version. If you *really* want to check, download the 10.12 installer, make a bootable USB installer with it, boot from that installer and you'll either get the opportunity to install (Stop! Do not pass go!) or a dialog to the effect that "This hardware is not supported". If you want, but can't find, the Sierra installer then let me know -- be warned, it's a 4.8GB download... I'm thinking it's more likely that the "database problem" was simply that 10.12 won't install on an APSF-formatted drive -- if they had managed to get that back to HFS+ first it might have been a different story. Disabling SIP may not have helped you -- that's only one part of Apple's "modern" protection scheme and doesn't (AFAIK) protect /Library. /System and therefore /System/Library, yes -- but not /Library. Other sandboxing elements have been introduced over time, and it might be one of those. I'd still like to have a play, even if the results won't be directly applicable to your situation. So let me know the OS version as of "Saturday night 30 Marchο»Ώ" when this all kicked off and I'll see if I can replicate and check the validity of the "Live Restore" instructions. It's a bit quiet here after the Easter hols, so I'm looking for a project anyway!
  15. What OS was the MBPro on? Asking because that sounds more like Apple's new(-ish) security sandboxing kicking in, rather than an UNIX permissions error. If you fancy trying again, reboot with Command-Option-Shift-R held down -- that should install the OS version the Mac shipped with (unless that's the "Apple database" you mention). I'll confess, we long-ago decided to only back up user data while reinstalling the OS, apps, etc from scratch. Always seems like a good opportunity to clear out the cruft that accumulates over time. But for bare-metal restores in the past I've always connected the Mac-to-be-restored to another Mac (either client or the RS server) in Target Disk mode, though I guess lack of adapter prevented you from doing that initially. I've a spare laptop sitting on the bench right now. Let me know the client OS and I'll set up a test (though it'll be with Server v13) using the "Live Restore" instructions here.
×