Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by DavidHertzberg

  1. I run a Recycle backup of my MacBook Pro "client" once a week, scheduled for 3 a.m. on Saturday. Lately I've discovered that if I stop working before 3 a.m. but leave the MBP up, Retrospect Mac 16.1 gets a -559 (network connection timeout) error for that "client" (it skips to backing up local drives) precisely 2 hours after I stopped using the MBP—apparently because a forced upgrade of my MBP to macOS 10.13 eliminates the slider for "Computer sleep" in System Preferences->Energy Saver's "Power Adapter" tab.   Re-running the Backup script with No Media Action completes the backup of the MBP, but notably that re-run takes less than 2 hours.

    My first hypothesis was that there was a failure after two hours in one of my Motorola MoCA bonded 2.0 adapters, which for nearly a year I've had attached to the two ends of a detached coax cable running in my apartment between my study (which is where the MBP is located) and my bedroom (which is where my Mac Pro "backup server" is located). I developed that hypothesis because, about 6 months ago, the adapter in my bedroom seemed to go dead until I reset it with an unrolled paper clip. However last week I switched back to my 4-year-old Actiontec MoCA 1.1 adapters, and this week I got the same -559 error.

    I upgraded my MBP to macOS 10.13 about 8 months ago. Before that I had the the slider for "Computer sleep" in Energy Saver's "Power Adapter" tab set to "Never", but that slider has been eliminated in macOS 10.13.

    I noticed that the Retrospect Mac cumulative Release Notes has, for, "Mac Client: Fixed issue where client did not prevent macOS from going to sleep during backup (#7273)". My current hypothesis is that #7273 is no longer operative in 16.1, and the lack of a fix is showing up for clients running under macOS 10.13.

    P.S.: The body of this post is copied from a Support Case I filed before posting in this Forum.

  2. trevorjharris,

    I run a Recycle backup of my MacBook Pro "client" once a week, scheduled for 3 a.m. on Saturday.  Occasionally I'm using the MBP then, and reflexively shut it down when I quit working even though the backup is running.  Lately I've discovered that if I stop working before 3 a.m. but leave the MBP up, Retrospect Mac  16.1 gets a -559 network error precisely 2 hours after I stopped using the MBP—because a change in macOS prevents me from inhibiting non-use shutdown..  In either case, rerunning the Backup script with No Media Action (Retrospect Mac term for Normal) completes the backup.

  3. erostratus,

    They'll be sending their their data through the Mac mini to S3.  (MinIO "is a cloud storage server compatible with Amazon S3, ... Apache License v2.")

    However I don't think you've thought through the consequences of having your "clients" back up directly to the S3 server.  Unless you scheduled the backup of each "client" at a different time, all your "clients" would be sending data over the network at once—possibly overloading the network and/or MinIO—because there would be no way of making each un-coordinated "client" "take its turn".  That's why enterprise client-server backup has thrived even though most backups are no longer directly to tape; it makes client machines "take their turn" as dictated by their place in a Backup or Proactive schedule.

    If after reading the preceding paragraph you still want multiple "clients" to back up directly to the S3 server, I'd suggest installing Arq on them instead of Retrospect—it'd be cheaper because Arq is per-user-licensed.  Let Stefan Reitshamer deal with your problems, instead of us or Retrospect Tech Support.

    P.S.: An important sub-question  in the "back up directly" case is how many "clients" you'll have backing up to S3.  In August 2017 I posted in an Ars Technica Mac thread whose OP had been trying to back up 25 Macs to one OS X Server instance.  He/she found that "when 25+ users are backing up over the network to our Time Machine backup server, there are a lot of backups not being completed. The Apple rep I spoke to actually confirmed that this number of users causes a Time Machine server a lot of issues."  Up to 15 "clients"  may work for you, even if MinIO's  efficiency equals OS X Server's.

  4. On 10/7/2019 at 10:27 AM, mbennett said:

    I experience this too, on a regular basis.  Yes, it used to work and stopped being reliable a couple of years ago.  Tried using a static IP address but that's inconvenient for a laptop that frequently travels to other locations and networks.  Nothing else works.  When it breaks I use ipconfig on the laptop and reset it to that address on the client setup in Retrospect.  It's annoying, but nothing else seems to work.


    When you wrote "Tried using a static IP address  ...", did that mean an IP address designated on your router via a "DHCP reservation" based on your laptop's MAC address?  Inquiring minds (with limited reading ability :rolleyes:) on the Ars Technica Networking forum want to know.

  5. Magnificent investigation, MrPete! :) 

    All machines on my LAN are Macs, and to my knowledge I don't have a network security system—not to mention VMware (for which the -530 problem was discussed starting in a 2017 thread).  I don't have a firewall on my LAN's FiOS "gateway", and the firewall is disabled on my MacBook Pro. 

    As a result of your investigation I'm now wondering if my "gateway", which is a Verizon G1100 which also functions as my router, uses pfSense (or its fork OPNsense) code.  Almost a year ago I ran a test which temporarily connected my MBP "client" to my Mac Pro "backup server" so that it was "upstream" from my "gateway".  However I didn't think of disconnecting the "gateway" until I had disassembled the test setup, and the connection probably wouldn't have worked without it.  However my original -530 problems, which started on 30 January 2017 when I still had DSL instead of FiOS, occurred only when I booted the "backup server" after the scheduled time for the backup script and the script ran immediately—so I thought the bug was caused by uncoordinated startup in the Retrospect Engine.

  6. amkassir,

    See "Version 16.5 Required" in this Knowledge Base article, and the macOS Mojave – Application Data Privacy KB article it links to.  However I don't think those will answer your all questions; you'd better phone Retrospect Tech Support, and please post what you've found out—including when the august Documentation Committee is going to update that first KB article.

  7. 12 hours ago, Xenomorph said:

    So why not add this as an additional post to your last thread, and save other people's time answering the same question?:rolleyes:  My answer, for instance, would be exactly the same.  A new post to an existing  topic makes that topic in the Forums list appear bolded, just like a new topic.

    The cumulative Release Notes for Retrospect Mac do say under Engine for 16.5 "Improved: Client scanning 2x faster".  However that doesn't appear in the cumulative Release Note for Retrospect Windows, and may apply only to the scanning phase—for which there had been an Apple-created problem with Instant Scan for APFS-formatted Mac volumes which the Retrospect engineers said was going to be solved by switching to a 64-bit API to speed up non-Instant scan .  So that probably doesn't improve the actual backing up phase speed for Retrospect Windows. :(

    Lennart_T suggested in a PM that the Engine should be made multi-threaded.  I responded that the Engine has been running each operation in a separate thread since Retrospect Windows 7.5 and Retrospect Mac 8, and I couldn't see how one would usefully multi-thread an individual backup operation.

  8. 15 hours ago, x509 said:


    In the interest of history.

    If I remember correctly, the "Multics" system at MIT when I was a grad student there was a Honeywell 635 system with virtual memory.



    Your attempted correction of MrPete is wrong as to manufacturer name.  Multics was developed for the GE 645, which was a GE 635 with "a configurable hardware protected memory system".  General Electric later sold its computer business to Honeywell, and the Wikipedia articles says a GE 645 follow-on was sold as the Honeywell 6180.   "The bulk of these computers running time-sharing on Multics were installed at the NSA and similar governmental sites. Their usage was limited by the extreme security measures and had limited impact on subsequent systems, other than the protection ring."

    IIRC, Fernando Corbató—lead developer of Multics—delivered the introductory IBM 7090 lecture in a 1963 post-summer week-long programming course at MIT somebody got me into.  I chose to study Fortran II (go-to-only logic  :o ) for the rest of the week; the course, followed by self-study, changed my life.

  9. On 10/7/2019 at 10:27 AM, mbennett said:

    I experience this too, on a regular basis.  Yes, it used to work and stopped being reliable a couple of years ago.  Tried using a static IP address but that's inconvenient for a laptop that frequently travels to other locations and networks.  Nothing else works.  When it breaks I use ipconfig on the laptop and reset it to that address on the client setup in Retrospect.  It's annoying, but nothing else seems to work.


    Alternatively, have you considered setting up a "BackupLand" or "HomeSweetHome" Location in the Windows equivalent of your laptop's System Preferences->Network?  You could copy your addresses from your Automatic location, and put your laptop's fixed IP address (not "static"; that term now refers to an Web-wide IP address permanently assigned to you by your ISP) specified on your home/office LAN's router into that Location.  You could then use the Windows equivalent of the Mac System Preferences->Network dropdown to switch to that Location whenever you bring your laptop back to your home/office where you back it up.That way you could continue to use the Direct Access Method for your laptop "client" in Retrospect.

    I have no personal experience with this, especially since I'm a Mac administrator, but from reading the Mac System Preferences Help I think this would be better than defaulting to the Automatic location—unless Subnet Broadcast instead of Direct works for you.  This Web page looks as if it might offer a clue to Windows 10 Settings for networking. I would welcome comments from Retrospect Windows administrators.

  10. mbennett,

    Have you tried using the Subnet Broadcast access method?  It is initially described under "Subnet Broadcast" on page 294 of the Retrospect Windows 16 User's Guide; how to use it is described under "Subnet Broadcast Access Method" on pages 295-296.

    Subnet Broadcast  was suggested by henry-in-florida in this December 2018 post.  IIRC I used it for my MacBook Pro "client" for about a month, then eventually (when a trial of Multicast didn't work) switched to Add Source Directly—the Retrospect Mac equivalent of Direct Access Method—after having upgraded to Retrospect Mac 15 (because of a Retrospect-Mac-only bug in preceding versions that activated at the start of 2019).  My MBP never travels off my LAN, so Add Source Directly using a fixed IP address works for me.


  11. Lennart_T,

    Point well taken, but the OP's Backup Set is named "Backup Set Drives C  D and V", so the message would have to be "Groomed 290.2 GB from 'Backup Set Drives C D and V'".  I myself use "Backup Set Red" and "Backup Set White" and "Backup Set Blue" when running Retrospect Mac 6.1 on my G4 Digital Audio, and "Media Set Red" etc. when backing up my other machines using Retrospect Mac 16.  The User's Guides and the Retrospect GUI(s) have long encouraged naming Backup/Media Sets that way.

  12. NoelC,

    According to all available documentation, Retrospect's grooming feature only works on Backup Sets—although page 234 of the Retrospect Windows 11 User's Guide under "Scripted Grooming" has the slightly scary sentence "When a Groom script runs, Retrospect deletes older files and folders from the source disk [my emphasis] Backup Set(s) based on its specified grooming policy" which I think is just sloppy tech writing.

    The reason I'm referring to the Retrospect Windows 11 UG is that, starting with Retrospect Windows 10 and Retrospect Mac 12, the august (adjective meant ironically) Documentation Committee decided that new features described in the "What's New" chapter for a particular major version would not have those descriptions moved to follow-on chapters of the next major version of the UG.  Instead those descriptions are simply over-written by the next major version's new features.  Therefore the only accessible written description of Performance-Optimized Grooming for Retrospect Windows is on page 8 of the version 11 UG (there is a description in the last section of GDPR – Deep Dive into Data Retention Policies with Grooming Selectors, but who would know to look there? :huh:).  There is also the Tutorial video Grooming Options Windows (plus a corresponding version for Retrospect Mac), but again who would know to look for a video?  :huh: The charitable explanation is that the august Documentation Committee (of which the head of Retrospect Tech Support—by his own admission—is not permitted to be a member :o) decided that nobody reads the User's Guides anymore; at 615 pages for the Retrospect Windows UG, exclusive of Release Notes, that IMHO is a supportable position.  However I prefer the uncharitable explanation, which is that nobody on the Committee could take time away from his (sexist pronoun intended) regular work in Engineering or Product Management for the one person-week of work (estimate detailed in a Support Case I wrote) to retroactively update the follow-on chapters of both variants of the UG—and pre-StorCentric Retrospect Inc. couldn't afford to hire and familiarize a tech writer (who could have been somebody's spouse).

    P.S.: FYI Retrospect does have an Archive operation, which is the same as a Backup operation except that has a Move Files option.  That option, described under "Archiving Execution Options" on page 376 of the Retrospect Windows 11 User's Guide, "deletes files from the source [my emphasis] volume after they have been copied.  If Thorough or Media verification is turned on and the files do not match exactly, the originals will not be deleted."  DovidBenAvraham reminds me that the competing application BE eliminated that option in 2018, probably because it violates the "3-2-1 rule" for backups.


  13. On 10/5/2019 at 10:40 PM, x509 said:

    There are so many, many frustrations in using Retrospect.  Why do I (or anyone else) stick with it?  This client not found issue seems like a self-inflicted wound.


    I understand your frustration, but IMHO calling the -530 error a "self-inflicted wound" is a bit unfair to the Retrospect engineers.  The Multicast access method used to work beautifully, at least for me using Retrospect Mac from 1995 to early 2017.  However if you read the first expert-quoting section in this post earlier in the same Forums thread I linked to in my preceding post, you'll see that Retrospect's version of Multicast seems to have recently stopped working reliably because of "improvements" in networking hardware (my situation) and/or software (your reported situation).  IMHO the Retrospect engineers should at most be faulted for not having done a really thorough investigation of my -530 problems as reported in Support Case #61302 (in which my March 29, 2019 00:38  Additional Note is a copy of the same post section I linked to in the third sentence of this paragraph), and then not having faced up to the need to revise Retrospect's method of Multicasting (e.g. to use mDNS as the Ars Technica expert suggested).

    Of course in 2018-2019 the Retrospect engineers had many enhancements on their agenda, which Product Management undoubtedly considered to be more urgent than an extensive effort to fix -530 bugs that only some administrators were experiencing.  Still, considering that AFAICT most Retrospect engineers are in their 50s, IMHO they would benefit from being forced to take a Software Engineering course in modern debugging methods—which they probably never had in college or grad school (I was a professional applications programmer from 1964 through 1988 after flunking out as a Political Science major, and then went back to get a quickie Bachelor's in CS followed by a night-school MSCS in early 1996—and I never had such a course).

    IMHO getting Multicast working reliably again will be an absolute must for the planned version (StorCentric management has announced this ) of the Retrospect "backup server" running on Drobo NAS appliances.  Given that reviewers agree the main market for Drobo is for home users and SMEs, how can Drobo expect those customers' backup administrators—having backgrounds as described in the last sentence  of that Wikipedia article's lead—to be expert enough in networking to assign fixed IP addresses to "clients" on their particular brand of routers and then enter those addresses via the Retrospect Drobo equivalent of the Direct Access Method?:rolleyes:  No, IMHO they'll need reliable Multicast.😎  I'd therefore suggest that you invoke superior force by communicating that requirement (as I already have in a snail-mail letter, but you can find an e-mail address on LinkedIn) to:


        Attn.: Mr. Rod Harrison, CTO

    1289 Anvilwood Ave.

    Sunnyvale, CA 94089


    Be sure to mention my name, which I used in the snail-mail letter (put a space between my "handle"'s second 'd' and the 'H'), and Support Case #61302.

    P.S.: A Forums search using "-530" (including the double-quotes) in the Sarch bubble shows some administrators have been getting this error since 2002.  A number of these have turned out to be networking problems, and a number because bugs had not yet been fixed for Retrospect Windows.

  14. x509,

    That is what finally worked for in Retrospect Mac 15 for my -530 problems that started on 30 January 2017, as detailed in this post and its thread predecessors—plus links to preceding threads.  Add Source Directly is the Retrospect Mac equivalent of the Direct Access Method, which is described on pages 296-297 of the Retrospect Windows 16 User's Guide.

    I had to both look up my old Forums post and find the Retrospect Windows UG equivalent of Add Source Directly, while working only during only the TV commercials interrupting the film "Dancing With Wolves".  Sorry for the delay.

  15. 1 hour ago, x509 said:

    I had assumed since all my systems are running Win 64 Pro on Intel CPUs, that one recovery disk would be suitable for all my systems.  Apparently not. 

    Welcome to the wonderful world of different Windows drivers, x509, which is why Retrospect "inc." markets the Dissimilar Hardware Restore Add-On.

    P.S.: As to x509's second-paragraph complaint directly below, IMHO he'd do well to read pages 328-337 of the Retrospect Windows 16 UG.

  16. x509,

    Here's why and how to submit a Support Case for a Retrospect enhancement, in this case to the Retrospect Windows User's Guide—which needs it.  IMHO the enhancement should go beyond the UG; Retrospect should detect any first-time use of a Windows "backup server" or "client" machine and throw up a "Now create a recovery disk" message per Nigel Smith's first sentence immediately above.

    You've been a Forums member since early 2010, and you didn't know you needed to create a Disaster Recovery Disk in advance?:rolleyes:  Even I knew that, and I administrate Retrospect Mac—which doesn't have a Disaster Recovery Disk.  (in the interests of truth, I backed up a work-provided Windows 95 machine at home from 2001-2004; however that was using Retrospect Mac 6—which didn't have a DRD feature AFAICT from reading its User's Guide—at the latest.)

  17. fredturner,

    AFAIK the "Client" sub-section of this Knowledge Base article is the authority on how to enable Full Disk Access for for a Retrospect Client under Mojave. I don't know about defaults commands, but my guess is that Apple wouldn't make automating the settings easy for fear everybody would use that to get around Privacy for "Application Data"—see the "Overview" of that KB article.

    Cheer up; it will be worse for macOS Catalina.:(

    P.S.: Here's an Apple Developer Forums thread discussing this problem for other applications.  Note that one of the thread's posters is S.Reitshamer, who as many of us know is the principal developer of Arq (which he mentions in his post).  However Arq is not a client-server backup application, so I feel I can get away with mentioning its name in this Forum (because it is not listed in the Competitive Analysis — Retrospect for Mac KB White Paper).  The KB article I linked to in the first paragraph of this post was written before the December posts in the Developer Forums thread, but I strongly suspect the Retrospect engineers were reading that thread.  In any case, AFAICT the developers in that thread didn't come up with an automation solution even for self-contained—much less client-server—applications.

  18. x509,

    As of 1 October 2019, the full-featured two-way Web-based Management Console I predicted in the second paragraph of this up-thread post is released in Retrospect Windows 16.5.  However, according to this brand-new Knowledge Base article, you'll have to pay for the Management Console Add-on to get it.  Yesterday I couldn't get anyone in Retrospect Sales to pick up the phone to tell me how much it will cost, and it's not yet in the Configurator.  Evidently Retrospect "Inc."  Product Management thinks this will only be of interest to larger organizations.

    P.S.: Just before noon I got Werner, head of North American Sales, to pick up the phone.  The Web-based Management Console Add-On is US$49 for The Desktop Edition,  US$149 for the Disk-to-Disk Edition (which is the same as the Single Server Edition except without tape destinations), and US$499 for the Single Server and Multi-Server Editions.  Werner tried it last night to access his own "backup server" over the Web; with the Add-On he can do anything Retrospect Mac non-Desktop Console users have been able to do over their LANs.  The one Web-vs-LAN tradeoff is that two-way updating between the "backup server" and the Console is done only once every 60 seconds; Werner says the engineers tried reducing the delay, but found that Web traffic made that inadvisable.  I hope the $49 you'll save by not buying it, x509, will ease the ongoing minor pain of your "simple and effective" substitute solution.;)

    P.P.S.: Thinking about what Werner said about Web traffic making faster-than-60-second response from the Management Console inadvisable, it occurred to me that the "traffic" Werner was talking about may be the Console's interaction with Salesforce Heroku's Amazon EC2 cloud-computing platform here's a discussion.  Competing client-server applications have a small Web server within their "backup server"—so they don't need to interact with a cloud service, and Retrospect Mac's non-Web-based Console of course relies strictly on interaction between computers on the same LAN/WAN.

    P.P.P.S.: On 16 October 2019 I attended a 45-minute webinar "Manage Backups from Anywhere with Retrospect Backup 16.5".  The demonstration of Granular Remote Management, conducted by the head of Retrospect Tech Support, showed a response time for the Web-based Management Console that seemed to be a lot faster than once-every-60-seconds. It's still not in the Configurator (I think Retrospect "Inc." Product Management is still thinking of it as a tool for Partners), but Sales told me it only costs an additional US$49 for the Desktop Edition.  If I were administrating Retrospect Windows, I'd pay that—for a Web-based Management Console that seems to be about as good as the non-Web-based Retrospect Mac Console I now use—instead of learning a Windows Task Scheduler without Retrospect facilities.

    P.P.P.P.S.: On 25 October 2019 I phoned the head of North American Retrospect Sales, who did part of the narration at the webinar.  He confirmed that Granular Remote Management really has a response time for the Web-based Management Console as fast as shown.

  19. I too have a bunch of these files on my MacBook Pro "client", and they're all dated Wednesday 3 July 2019 shortly after noon.  My Mac Pro "backup server" Activities log shows that about a half-hour before that I had done a Rebuild of my Media Set Blue, which I would start using the following Saturday—but whose portable HDD I had already brought home from my bank safe-deposit box (when I deposited the portable HDD for Media Set Red there after cabling the portable HDD for Media Set White) the preceding Friday.

    I can't remember the reason I did the Rebuild, but when I previously ran the initial Recycle backup to Media Set Blue on Saturday 8 June I had gotten a -559 (network connection timeout) error after about an hour of backing up my MBP.  Because before that I had gotten a series of -519 errors on "Sat. Backup" Recycle script runs on preceding Saturdays, I think I took advantage of the 4 July holiday the next day to swap in my replacement Ethernet switches.  Of course I had immediately run a No Media Action backup of my MBP on 8 June, and then run 6 daily No Media Action backups of my MBP to Media Set Blue, but I think I was still stupidly worried that there was something wrong with the Media Set Blue HDD or its cable that had caused the -559 error. 

    I think that's the reason I ran the Rebuild script in the late morning of 3 July.  And I probably started my MBP's Client after that just to check connectivity to the "backup server", which I guess in some way generated the log files.  The Client was Retrospect 16.1.0, running under macOS 10.12 High Sierra.

  20. On 9/26/2019 at 12:18 PM, Nigel Smith said:

    Oh, but he does!

    Being able to tell RS that "this new client is that old client, only reinstalled" would be useful. Not having to re-define Favourite Folders, re-do Tags, etc, would be great. But I get the feeling that there are practical, and probably security, reasons why this can't/shouldn't be done else we would have had the feature ages ago.

    But, in the meantime, Tags are a time-saving feature that anyone who isn't using should take a good look at.

    Nigel Smith,

    Pages 40-42 of the Retrospect Mac 16 User's Guide imply that you can assign a Tag to a Favorite Folder.  So on "this new client is that old client, only reinstalled" you would have to redefine any Favorite Folders and assign them the same Tags they had before, but if your scripts used Tags to designate Favorite Folders you wouldn't have to change the scripts.

    If you did this,  in most cases the NHS (I noticed how you spell "Favourite", even though your Profile doesn't specify Location) wouldn't have to treat you for extreme finger fatigue resulting from "client" reinstallation.;)

    P.S.: In Sources I added a Tag for my Favorite Folder on a drive local to my Mac Pro.  Then, for my my normally-unscheduled  "Sat. Backup Incremental" script, I un-checkmarked that Favorite Folder and checkmarked the Tag instead.  Finally I did a Run of the script to the Media Set I'm using this week; it did what it normally does, finishing with backing up that Favorite Folder via the Tag.  So the first paragraph of this post is correct.

    P.P.S.: In Sources I added Mimi'sOldG4, gave it a non-Smart new Tag, and also gave a non-Smart new Tag to David'sMacBookPro.   Then, for my my normally-unscheduled  "Sat. Backup Incremental" script, I un-checkmarked the Smart Tag for All Clients and checkmarked the non-Smart newTags instead—dragging them in the Summary pane into the desired backup sequence.  Finally I did a Run of the script to the Media Set I'm using this week; it did what it normally does, giving a -3203 error message for Mimi'sOldG4 (because Retrospect Mac 16 can no longer actually back up "client" machines booted under OS X 10.3 using the 32-bit Legacy Client—even though Sources can still Add such "clients").    So this up-thread post is correct; the procedure for creating and eliminating non-Smart Tags on pages 40-41 of the Retrospect Mac 16 User's Guide  is independent of their use for a specific Source—it's the checkbox in the Tags tab that designates whether a specific non-Smart Tag is used for a specific Source.

  21. On 9/24/2019 at 7:13 AM, Nigel Smith said:


    If you set your scripts to use tags to determine what to back up, you only have to set a new/replaced client's tags once and it will be picked up by all appropriate scripts.

    And as David said, you shouldn't get a full backup unless that's part of the script's definition -- "Match only files in same location/path" may be the culprit here.

    You da man, Nigel Smith, for suggesting Tags.:) 

    Yesterday evening I un-checkmarked David’sMacBook Pro from my normally-unscheduled  "Sat. Backup Incremental" script, and checkmarked All Clients under Smart Tags instead.  I then dragged All Clients to the top of the pane in the script's Summary panel, and did a Run of the script to the Media Set I'm using this week.  The execution did a No Media Action backup of David'sMacBook Pro, followed by a No Media Action backup of the two drives and a Favorite Folder local to my "backup server" that are also checkmarked.  (If Mimi'sOldG4 were still a "client", which it isn't because Retrospect Mac 16 can no longer backup machines booted under OS X 10.3 using the 32-bit Legacy Client, I'm pretty sure my "Sat. Backup Incremental" script run would have backed up Mimi'sOldG4 second—because its Sharing name sorts alphanumerically after David’s MacBook Pro.)

    So hrobinson doesn't need to submit a Support Case for a Retrospect enhancement that turns out to have been made in Retrospect Mac 8.  Administrator-defined Tags are covered on pages 40-42 of the Retrospect Mac 16 User's Guide.  Smart Tags—such as All Clients—really aren't covered at all in the UG,  because they're Tags that Retrospect automatically maintains for certain obvious software-determinable categories of administrator-defined Sources.