Jump to content

Nigel Smith

  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by Nigel Smith

  1. 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!
  2. 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...
  3. 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.
  4. 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.)
  5. 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...
  6. 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!
  7. 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.
  8. It's how it *does* work with Retrospect client (and has for the last umpteen years), and I've seen other IP-listener daemons do the same. Since you are on a static, just run retroclient.exe /ipsave <static-address> (from the page linked above) on the client and it will always behind to your external interface rather than the virtual one -- no messing with RS Server required.
  9. Nigel Smith

    R16 really slow backups

    Windows 10 updates have killed SMB1 updates before, so I think you've nailed it. It would be better to sort your Synology so it'll work with SMB2 or 3, both for speed and security. How you do that will depend on your DSM version, but you'll find instructions in "Option 1" here <https://www.synology.com/en-global/security/advisory/Precaution_for_a_PotentialSMBVulnerability>. Unless you have a particular requirement to use SMB1?
  10. In my experience, RS Client binds to the first interface it finds to be active -- I often see this when someone has wireless enabled but unused while they are actually using ethernet. Sounds like yours is (sometimes) seeing the virtual interface before the real one. Instead of deleting/re-adding the client, try the instructions here <https://www.retrospect.com/en/support/kb/client_ip_binding> -- whether you use the "temporary" or "permanent" solution will probably depend on whether that machine is DHCPd or on a static IP.
  11. Probably a StorageLoader, then. <https://www.overlandstorage.com/products/tape-libraries-and-autoloaders/neos-storageloader.aspx#Overview> Yes, that'll be manual cleaning. I understand you don't want to mess around too much before the Bank Holiday weekend but, when you're back, these are both easy jobs to do. The first is just spitting out the cleaning tape to the mail slot and removing it, cancelling the "cleaning slot" designation on the library slot, adding a new member to each tape set -- all done through the Retrospect GUI. The second would be setting up static-IP settings as per your network via the StorageLoader's front panel (pp48 of <https://www.overlandstorage.com/pdfs/support/NEO-S-Series-UG-ENG.pdf>, plugging in an ethernet cable, logging in with your web browser then resetting password etc. You can then use the Web GUI to do the important things like check/update the library firmware etc. One word of warning (coz this always catches me out) -- pressing front panel buttons often (always?) rips control from Retrospect but, when you finish, RS (or the Mac OS SCSI routines) can't always gracefully resume operations without a restart. So pick an idle time when, if necessary, you can restart the backup server 😉 Ooof! I excluded VHDs from our backups a l-o-n-g time ago, for that very reason. Not a practical solution for you though! And it may be worse than it first looks -- depending on how those VHDs are set up, every previous version of every edited file may still be on the VHD, hidden from a "file explorer" but still present in part or whole on the disk just as they are on a "real" hard drive. While you'll still get compression that might be countered by the large amounts of "unseen" cruft... Others (David? Lennart?) may be able to chip in how how best to manage this -- I've never used block level incremental backups <https://www.retrospect.com/uk/documentation/user_guide/mac/block_level_incremental_backup> or Retrospect Virtual <https://www.retrospect.com/uk/products/virtual>, which are the two quick fixes that leap to mind.
  12. Ah, but what is the library, how is it attached, and to what? I'll take a punt that it is a FlexStor II 1-U, fibre connected. On the face of it that is supported by Retrospect, but so is my fibre-connected Scalar 24 *except* the fibre connection is via a Thunderbolt to fibre adapter, which introduces its own problems -- I see similar SCSI errors to the ones you showed when my adapter has a "moment", and the tape finishes before it is "full" (note that on a sequential-tape system you can't go back and "fill up the gaps" later). You'll see RS's automated cleaning option if you click on "Options" when the drive (not the library) is selected as in your screenshot above. It is in "hours of use" and by default it is "0" (never) and I'd suggest you keep it at that. Cancel the cleaning slot and keep the cleaning tape in your desk for when needed and that'll give you an instant 33% bump in set capacity simply by adding a tape to each, which will buy you time to sort things out. Get the library on the network and use the management GUI to monitor the cleaning requirement instead. How often you'd need to manually load the tape and run a cleaning cycle will depend on your environment but, IMO, most people do it far too often given that LTO drives self-clean every time a cartridge is inserted. The drive/library should tell you when it is required: on the front panel there's probably a "Clean" indicator, and it'll show in (and should be set to email/Slack/SMS/whatever an alert from) the network management UI. And note on backing up the WP installs: Lots of small files will (almost) always take up more space on tape than the same amount of data in one single file -- assuming compression is the same, an unchanged WP install will use more tape capacity than the original installer. Also, many of the WP files across your client folders will be unchanged and thus the same and, under RS's default "don't copy the same thing twice" setting, don't actually get backed up a second/third/100th time and so don't contribute to the "compression percentage". So, across the whole set, the WP *code* contribution is minimal compared to media, assets, etc your clients have uploaded (which, I think, is the point Lennart was trying to get across). Hope some of that ramble helps...
  13. To my eyes, that looks more like a SCSI error causing a premature end to tape writing than an error with the tape itself. Retrospect would, in that case, still move on to the next tape so the effect is the same. Adam, you still haven't said what tapes you are using. I'm guessing from... IBM|ULTRIUM-HH6|E6R3 ...that Lennard's right and it's an LTO-6, and that Retrospect's reported nominal capacity is bogus. If we are right then, given that you are a media company and probably dealing with already-compressed video etc, I reckon the "space used" on tapes 1 and 2 is both correct and the best you can expect (they're full but mis-reporting spare capacity), i.e. 2.5-3TB per tape because there's minimal compression, while tape 3 "finished early" because of the comms error. So each 3-tape set is barely big enough for your current weekly usage, even without problems like this. But more info would help here -- what are the tapes, what's the drive and firmware version, what machine is the server on and how is it connected to the tape library, etc. Oh, and I wouldn't recommend using Retrospect's "automated cleaning" with LTO drives. The drive itself should flag a cleaning requirement for you, either on its display or via remote management, when it needs it rather than after a certain amount of time.
  14. Generally -- yes, you can use static IPs on (your own, controlled) Wi-fi connections. How you do that will depend on your router's interface (can you assign by MAC, do you "block out" a range from DHCP distribution and manually set from that range on the client, etc). Some low-end boxes may not offer the facility at all, of course...
  15. Unless you have reason not to, update your Mac to 10.11.6 -- that fixed a lot of small 10.11 problems for us, especially as other software was updated to cater for more recent OSs. And try mounting over SMB rather than AFP. While it shouldn't make a difference, it often does -- especially since your NAS is probably running Windows permissions that are being translated so they can be used over AFP, so plenty of scope for "strange behaviour"...
  16. As well as another "What David said...", whilst you can't use the finish of one script to trigger the next, you can set scripts to run sequentially after a single trigger-action by using Run Documents. See page 234 of the Windows guide but, basically, if you open several runs documents at once then the scripts contained will run in alphabetical order. So name them "A - First Script", "B - Second Script", "C..." etc, set them all to use the same execution unit just to be sure, and you should be good. Personally though, I'd just use scripts as others have suggested. Set them to trigger at 1-minute intervals in the order you want, set them all to the same execution unit, and they'll run consecutively.
  17. Nigel Smith

    Copy with Move not working

    These look to be Dropbox folders... First, test the script with a local source instead of the Dropbox folder and see if the problem still happens. I'm expecting it won't 🙂 but, if it does, follow David's suggestion of submitting a bug report. Otherwise you'll have to drill down through your Dropbox sharing settings, ownerships and permissions for those folder -- doing it through the Dropbox web interface will probably be easiest. While you're there, make sure those folders are actually empty! If everything looks OK then it is probably a Dropbox syncing problem -- try deleting those folders via the web interface instead of with Retrospect or through the Finder.
  18. Nigel Smith

    Selector doesn't work for only 1 Backup Script

    Isn't that to be expected? IIRC, the tip for Windows paths implies you have to include both the drive label and, for directories, the trailing slash. So it should be "path matches E:\2018\".
  19. Nigel Smith

    Automating cleaning tapes

    Cheryl, How this happens will depend on your tape drive. If you have a barcode-reading drive and a tape in the library with a "cleaning" barcode attached, Retrospect should automatically load that tape after your chosen number of hours (the default is 0, so make sure you set that in the drive's "Options" in the Storage Devices window. If you have a library that doesn't do barcodes you will have to set a slot to be your "Cleaning tape" slot -- control-click the slot you want in Storage Devices and "Enable as cleaning slot" -- put the cleaning tape into that slot and, again, RS should automatically use it when required. If you have a single drive without a library then the best you can do is get RS to remind you to clean the drive, then insert the tape yourself. As David says above, you can find this in the online User's Guide. The library options above are pages 54-56.
  20. Nigel Smith

    Cannot "move" disk media set

    The RAID itself shouldn't go to sleep. The disks will spin down, but the card itself should remain active and the volume should stay mounted on the Mac. Is it possible that the Mac itself went to sleep (if it happens again, check the OS logs for the sleep event)? I wouldn't set any backup server to auto-sleep, just to be sure (let the display sleep if one is attached, but not the computer) and would just do it manually if e.g. I had no backups to do over the weekend. I'm all for energy saving, but not when it turns an important system into a flakey one! 🙂 If it's not set to sleep then you are down to normal troubleshooting. AFAIK (David? Lennart?) Retrospect accesses an external volume via OS calls rather than directly as it does with tape drives. So you can test with Finder copies of similar size or larger as the first step.
  21. Nigel Smith

    Cannot "move" disk media set

    It all depends on what the problem is. If it was introduced at the file system level, e.g. a disconnect while writing data, then fine. The problem will be with the volume presented to Disk Utility and will (since this is a hardware RAID) be present on both drives. Fix the volume, fix the problem. If it's a disk problem then no, don't go there! One disk should be showing as "failed" -- simply pop, replace, rebuild RAID. Perhaps worth noting that RAID =/= backup -- it will protect (somewhat) against hardware failure, but not e.g. data corruption. And personally, I wouldn't trust *any* volume, RAID or not, that "unexpectedly" unmounted. Get that sorted before continuing!
  22. Late to the party, but... Retrospect is seeing (or Apple is presenting to Retrospect... Let the respective Support teams argue that one out!) Time Machine's local snapshots of the MacBook's APFS-formated drive as well as the actual, working, volume and the Recovery volume. As David says, set the client to only back up the startup volume (single volume machines) or a manually selected list of volumes (for e.g. partitioned or multiple drives).
  23. Nigel Smith

    can't link to

    I'm guessing this is Filemaker Server machine running under OS X... "Content" files uploaded to your database server and linked rather than embedded -- in this case a PDF -- are backed up once by Filemaker's internal scripts and then, subsequently, linked to so that you don't waste disk space. I *think* the latest backup has the real file and the previous backups contain links, but that should be easy enough for you to check. Check the timestamps in the paths above and you'll see that the older "instance" of the file can't be linked to the newer. So either you haven't duplicated that later "instance" or, for some reason, RS can't recreate the link in the older FMS backup directory. I'd worry about the first and honestly not care about the second since if I had to roll back to an earlier version of my database it wouldn't be that much extra work to manually copy "content" files into the right place. Which is it, and what are you duplicating to? Nige
  24. It's more likely that Retrospect doesn't get direct-enough access to the drive hardware for this to work. Worth a try to save some money, but I hope I didn't encourage you to waste too much time on it. Options: Get a compatible external drive Replace the internal drive in the Mini (sample iFixit teardown here) Do the restores on another Mac on which you can install or migrate Retrospect But I'm not sure any of that will help. If I'm getting the above right: Retrospect on the Mini works fine creating then restoring from a new DVD It doesn't work for 2001 (Sets 1 and 2) (CD-Rs) It does work for 2003 (Set 3) (CD-Rs) It doesn't work for anything more recent than 2003 (CD-Rs?) ...which implies it is a problem with the media rather than the drive -- I'm not sure that e.g. an alignment problem would cause failure on some but not all CDs. CD-Rs can degrade surprisingly quickly in the real world, unless you've used expensive "archival grade" media, and retrieving data from 10-15+ years-old disks will always be a dodgy proposition. I never used RS much with optical media, so hopefully the David and Lennart will chime in here: Could you use Disk Utility to image the CD-R, then burn that image off to another disk that could be read by RS? I guess there's a slim chance that the OS's disk access routines are more robust/forgiving than RS's, allowing you to recreate a CD that's readable by RS. Nige
  25. To add to the above -- is this test using lots of smaller files or fewer larger ones? I'd benchmark using something like: Current data set using disk-to-disk backup Current data set using disk-to-tape backup (which you've already done) 1TB tarball, disk-to-disk 1TB tarball, disk-to-tape ...and I wouldn't be surprised if you end up using some form of disk-to-disk-to-tape if you want to maximise tape-write speed -- at least until the API changes David mentioned come down the pipe. But -- do you want to, if it's at the expense of added complexity? While it's nice to go as fast as you can go, if you're completing during your backup window and not wasting too much tape (i.e. the drive's variable-speed operation copes well enough to reduce "shoe-shining" either completely or to an acceptable amount), then having another step to manage may not be worth the hassle. Nige