Jump to content

DavidHertzberg

Members
  • Content count

    1,374
  • Joined

  • Last visited

  • Days Won

    49

DavidHertzberg last won the day on March 25

DavidHertzberg had the most liked content!

Community Reputation

79 Excellent

About DavidHertzberg

  • Rank
    Occasional Forum Poster

Profile Information

  • Gender
    Male
  • Location
    New York, NY
  • Interests
    Retired applications programmer, with a few Macs at home.

Recent Profile Visitors

2,483 profile views
  1. SHAB, Yesterday I phoned the Worldwide Head of Retrospect Sales, and left a message asking whether the soon-forthcoming Retrospect 18.x would handle Docker containers. He phoned back (because they've got several people out sick and he was in meetings) while I was out to dinner , and left a message that is a bit muddy on my answering machine. When I listened to it again tonight, I understood him to be saying that Retrospect "Inc." has no plans to handle Docker in Retrospect 18.x. However his message indicates that he believes Docker is a Linux distribution, and I shudder to think about how he re-phrased my question when talking to the engineers. 🙄 I'm merely an ancient home user of Retrospect Mac (although one of my "clients" in 2002–2004 was a Windows 95 machine forced on me for Work From Home by my bosses' boss). The only time I've ever encountered a VM was briefly as a remote user in 1969 of what was later to become IBM's mainframe VM/370, but I do read enough Ars Technica posts to be somewhat aware of what Docker is and its current importance. I'll write him an e-mail tomorrow, containing links to that Wikipedia article as well as to this thread—and stressing that Bacula will handle Docker containers. Salespeople worry about competitor's capabilities, so that should perk up his ears. đŸ€Ł P.S.: E-mail sent 21:37 on 15 April 2021. In the first paragraph it also links to the Ars Technica front-page article saying Docker now runs natively on the Apple Silicon M1 chip, as requested by many developers. In the second paragraph it also links to a YouTube video on Bacula Enterprise Principles, a Web page showing Bacula's "backup server" only runs on Linux or FreeBSD or Solaris, and the Web page on Bacula and Docker you linked to below. I then said "Bacula—rather than just Synology’s Hyperbackup or OWC's maybe-back-from-the-dead BRU—looks like the competition StorCentric will run into for the Retrospect 18.x 'backup server' running on Linux [publicly predicted by StorCentric management]." How's that for motivating Product Management? 😎
  2. DavidHertzberg

    Download Retrospect for 10.6

    Clive Bruton, If you actually want help with your problem from volunteers such as me, IMHO you're not going to get it by picking fights about trivial points. My original guess that you're British was in the context of suggesting which location of Retrospect Technical Support you'd have talk to about getting a license code for Retrospect 16. Read that post again, and discuss its tone with your spiritual advisor. "Spelt" is the correct spelling in Britain; the Oxford dictionary is not considered an authority on American English spelling. In 1806 Noah Webster published his first dictionary; he was "very influential in popularizing certain spellings in the United States"—which resulted in Americans being spared Anglo-Saxon relics and Frenchifying. Retrospect "inc." is an American company, so its product terminology—including "catalog" without a "ue" on the end—follows American spelling standards. People on the Forums can cope with British spelling in a post, but IMHO we shouldn't be faulted for taking it as a clue to the poster's nationality when it's relevant to the problem—as it is for getting a license code. BTW the dialect's name is pronounced and popularly spelled "Strine"; I used to work for Australians. As the article at the right bottom of page 33 of this 25 September 1989 edition of InfoWorld says, "Apple will bundle Dantz Development Corp.'s Retrospect backup and archiving software with the Apple Tape Backup 40SC, Dantz officials announced recently." Apple is not in the habit of "buying a pig in a poke", so Retrospect must already have been in a demonstrable form around the 1988 timeframe when .tar was standardized. And use of the BSD version of Unix was legally restricted to universities until June 1989. I assume you already know that "Adoption of Linux in production environments, rather than being used only by hobbyists, started to take off first in the mid-1990s." Thus IMHO you'd be well-advised to quit griping about Retrospect not having adopted .tar format, and instead figure out how to skip your bad DVD file via copying. Discuss your feelings about the unfortunate necessity of that task with your spiritual advisor. Agreed, there's a rarely-encountered bug in Retrospect that should be fixed—but the only way you'll get that done is by submitting a Support Case.
  3. SHAB, Unfortunately this post in a January 2020 Forums thread says However that was for Retrospect Mac 16.6. You might consider upgrading your "backup server" to the latest 17.5.2 release, if you haven't already done so. For that release, the cumulative Release Notes for Retrospect Windows include
  4. DavidHertzberg

    Download Retrospect for 10.6

    (Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. The same is true of Retrospect's history, especially with references to here.) Clive Bruton, Good point about Retrospect's potentially being able to detect looping on a Rebuild when it continues to scan the same device past the data limit for that device.😁 That wouldn't be an example of the Halting Problem. In regard to this being a bug Retrospect Inc. should have fixed, note that the Forums post I linked to up-thread was in 2010 for Retrospect Mac 8.2. As this section of the old Wikipedia article indicates, Retrospect Mac 8.2 had a lot of more pressing bugs to fix. Here is why and how to submit a Support Case for a new feature. Retrospect has always had the option to run a compare phase after a backup, because writing to physically-flexible magnetic media—including DVDs—has always been error-prone; my backup scripts always include a compare even though their destinations have been HDDs for the past 6 years. Did you run a compare phase when you originally backed up to this problematic DVD? If you didn't, caveat emptor; if you did, it's bad luck your DVD decayed later. The format of Retrospect Media Set members isn't .tar, because the original version of Retrospect's "backup server" was developed before .tar was standardized for Unix. And, as that same section of the old Wikipedia article implies, that original "backup server" ran on Classic Mac OS—which had no connection to Unix. There is a fairly-reliable prediction by insiders that Retrospect 18.x will have a variant of the "backup server" that can run on Unix, but IMHO its format for Members of Media Sets won't be switched to .tar. If you want to switch to a non-client-server backup application that uses .tar format, consider A**. According to Wikipedia, "Spelt (Triticum spelta), also known as dinkel wheat[2] or hulled wheat,[2] is a species of wheat that has been cultivated since approximately 5000 BC." If you think "spelt" is the correct way of spelling "spelled", it's probably because you're British. Why try to hide your nationality?
  5. DavidHertzberg

    Download Retrospect for 10.6

    Clive Bruton, If this 2010 thread relating to Retrospect Mac 8.2 is applicable, then it looks as if your "constant looping on rebuilds/repairs" while "repairing a catalogue from a DVD" means a .rdb file in a Member of that Media Set on the DVD is bad. IMHO that would call for a Support Case to detect the looping, except that I believe your compatriot Alan Turing demonstrated doing it would require a solution—which he proved to be impossible—to the Halting Problem. A preceding post in that thread describes how the OP identified the problem file during the rebuild—and evidently got around his problem by removing the bad .rdb file from the Member; however his Member was on a Drobo (genuflects in the direction of San Jose CA)—not on a DVD. Maybe you can identify your bad file by the same method, then copy the Member to a HDD that you can edit to remove the bad file, and finally copy the edited Member to another DVD and rebuild your Catalog with the edited DVD as the substitute Member. You'll lose the backed-up data on the bad .rdb file, but that can't be helped. My jocular remark about the typical Britishness of your "handle" was intended to encourage you to edit your Forums Profile to allow us to see your Location. (However you've "outed" yourself as British by your spelling of the Retrospect term "catalog" as "catalogue", unless you're Canadian.) You could also be really brave and enter a Gender, so that other posters wouldn't have to guess whether to refer to you in the third person as "he" or "she". As my Profile says, my Location is "New York, NY", and it's always difficult to guess at the ancestry of Americans. My paternal grandfather told me "Hertzberg" was originally spelled "Herczberg", but a U.S. immigration official suggested he change it when he emigrated from Poland. (If it makes you feel any better, my mother's side of the family emigrated from Germany after 1848.) Nevertheless—from my childhood onward—people have been deciding my name must be spelled "Hirshberg" because I look like a Jew—which I am. I've lately been telling such people to imagine they're on a trip to Greenland, and want to rent an iceberg from a car rental company that's well-known in the States—hence a "Hertz berg" spelled as a single word.
  6. DavidHertzberg

    Download Retrospect for 10.6

    Clive Bruton, Do what Lennart_T said. This Knowledge Base article says the last version of Retrospect to run on macOS 10.6 is Retrospect 16.1. Lucky you; the Retrospect Mac Cumulative Release Notes have this Engine bug fix for 16.0: My instinct says that's your problem with Retrospect Mac 10.5. 😄 Of course you'll have to get a License Code for Retrospect 16. Since your "handle" is so typically British that it may in fact be a pseudonym, you'll have to consult Retrospect Tech Support for Europe (unless there's a separate Retrospect Tech Support for formerly-Europe đŸ€Ł ) . Be sure the appropriate credit card is close at hand when you make that phonecall; they may give you a discount because you want a license code for an older major version.
  7. DavidHertzberg

    Disaster Recovery doesn't support high DPI screens

    IMHO cgtyoder—because he's definitely got a license for Retrospect Windows 17—should create a Support Case at https://www.retrospect.com/en/rscustomers/sign_in?locale=en . If he isn't already signed-up he should click that link to do so. He should be aware that, if his problem statement runs much over 2000 characters (16 lines of a 9-inch-wide inner window), it will spill over into an Additional Note. He should also be aware that Retrospect "Inc"'s highly-advanced Support Case system doesn't allow linking or underlining; I use before-and-after underline characters, and I paste-in links with a space afterward to facilitate copying into a browser link window. Having done that, cgtyoder should put the Support Case number into new a post in this thread. x509 can then create another Support Case, with a Problem Statement mention of cgtyoder's Support Case number. That will get around the wonderful feature that limits access of a Support Case to the administrator who submitted it. Be aware that these problems may turn out to be a result of limitations in Microsoft's WinPE underpinnings for Disaster Recovery.
  8. backy, After some more belated thought and one little experiment, I'd like to revise my recommendation in the last paragraph of this up-thread post. If you want to use a Storage Group defined on a Retrospect Windows "backup server" as a Destination, you may be able to get away with it—but I'd advise against it. My belated thought was that you could define a Grooming policy for the Storage Group. My experiment showed I can do this even on a Retrospect Mac 16 "backup server". Presumably the Grooming policy is applied to each component Backup Set as it is automatically created—when a new machine-volume is added as a Source for a script whose destination is the Storage Group, but I can't confirm this because of the so-far-incomplete Storage Group GUI in Retrospect Mac. Also presumably in Retrospect Windows you could modify the Grooming policy and the initial Member size for a particular component Backup Set, but again I can't confirm this. Ability to do those modifications depends on the capability of using the Retrospect Windows GUI to directly access a component Backup Set; there's currently no such capability in Retrospect Mac's GUI. The combination of these two capabilities—if they exist in Retrospect Windows—would allow you to tailor the maximum initial Member size for a particular component Backup Set. This—done carefully—would enable you to ensure that the sum of all components' initial Member sizes would never actually exceed the size of the Storage Set's defined Destination disk. Therefore, if you ran Transfer scripts frequently enough, you could make sure that all files from components had been Transferred to tape before they were groomed out of existence. So you wouldn't have to run any Recycle scripts having as a Destination the Storage Group; you could rely on the components' Grooming policies. If you can add additional Members to a particular component Backup Set, that would provide an additional safety factor. I can't do this either, again because the so-far-incomplete Retrospect Mac Storage Group GUI won't let me directly access a Storage Group's component Media Sets. Of course your Transfer scripts wouldn't be copying files simultaneously backed up by your Proactive scripts (because you couldn't make them use one Execution Unit)—pending enhancement per my Support Case #54601 (case# in P.P.S.). And it'd take substantial effort for you to explain this strategy to another employee of your company. Undoubtedly my recommendation in that up-thread post that you not use a Storage Group is still the wise choice.
  9. What Lennart_T says may "always" be true nowadays—especially for LTO "tape stations", but it wasn't true in the past. IIRC my first DAT drive, from DAT Technologies, did not have hardware compression—which I could have used because I was at one point backing up 4 machines in my and my then-wife's home installation. I was creating at least 2 DAT tapes from my 7-hour Saturday Recycle runs, but I couldn't use software compression because my "backup server" machine was slow. I had hopes when I got the HP StorageWorks DAT72 drive, but it turned out Retrospect Mac 6.1 didn't support its hardware compression feature. backy, make sure for your Transfer scripts that you don't click the More Choices button shown in the dialog on page 213 of the Retrospect Windows 16 User's Guide. Those lead to the options shown on pages 360–361, but you want those options to default to Match source volumes to Catalog File and Don't add duplicates to Backup Set. That will make sure newly-backed-up-to-disk files are copied to tape once—and only once—so long as their contents don't change, allowing emergency retrieval despite later grooming of your disk Backup Sets.
  10. backy, Consider using the Data Compression (in software) option (page 357 of the Retrospect Windows 16 User's Guide) on your Transfer scripts. That'll save tape space. OTOH the option may slow down your Transfer scripts if you don't have a powerful "backup server" machine; the ancient HP DAT 72 tape drive that I use for backing up my (now-deceased) ex-wife's old Digital Audio G4 Mac has a hardware compression capability, but ancient Retrospect Mac 6.1 doesn't support it. I learned about Storage Groups to fully answer other administrators' questions, starting with this March 2019 post in a thread whose OP asked about running multiple Backup jobs to the same Backup Set. I was curious enough to run a couple of experiments on my own home installation, which is how I learned about how Storage Groups really work but also about the limitations of their current Retrospect Mac GUI. If you liked my "amazing" post that much, you could click the "Like" heart icon at its bottom right. The head of Retrospect Tech Support runs a contest every few days; I enjoy competing for "most liked content". Lennart_T's second post in this thread is also pretty helpful, so maybe you should "Like" that post too; competition is good.😁 P.S.: If you're going to give the Backup/Proactive script and the Transfer script for a particular Source the same Execution Unit, I wouldn't use the New Backup Set Backup Action. I haven't used it, but it sounds like a potential complication.
  11. backy, I was going to make the same suggestion as Lennart_T yesterday afternoon in an additional paragraph in this preceding post—but I had to leave for a dental cleaning appointment. The screenshot at the top of page 176 in the Retrospect Windows 16 User's Guide (I'm referring to that because the Retrospect 17 User's Guides have been subject to the attentions of the StorCentric Slasher—e.g. in the last paragraph of that linked-to-post) shows where to specify the Execution Unit for a Backup script. The screenshot on page 210 shows the same thing for a Transfer Backup Sets script. However you can't set the Execution Unit in a Proactive script that uses a Storage Group as a destination. That's because—as briefly explained in the first three sentences of the last paragraph of this post in another thread—a Storage Group is a magnificent hack (IMHO) for enabling interleaved backups of different machine-drive Sources using a single Proactive script, rather than forcing the administrator to create a separate Proactive script for each machine Source; the enabling is done by using the multi-threading capability (expressed as Execution Units) of the Retrospect "backup server" Engine. There are two tradeoffs, however. The first is that, when the Knowledge Base article uses the term "volume", it means volume on a particular Source machine. If your 12 Source machines have only one volume each, they would just fit within the limit of 15 Execution Units your "backup server" could—given around 20GB RAM—run simultaneously. But the Proactive script will create a separate Backup Set component of the Storage Group for each machine-volume combination; I've tested this on Retrospect Mac—doing so because the KB article seemed unclear. The second tradeoff is that all the initial Members of a Storage Group's component Backup Sets must fit on a single Destination drive. At least—using Retrospect Windows—the KB article says you can designate an individual one of those component Backup Sets as the Source for a Transfer script. (As the KB article article also says, you can't do that designation using Retrospect Mac—IMHO because the StorCentric acquisition in June 2019 prevented the engineers from fully completing the Retrospect Mac GUI for Storage Groups. But I've tested using a Rule—Retrospect Mac name for a Selector—for restricting Transfer to a component.) Unless you can add additional Members to an individual Backup Set component of a Storage Group (I couldn't test this, because I have to work within the inadequate limits of the Retrospect Mac GUI), you'll have to—after successfully running all your Transfer Backups script(s)—run a Backup script with the Recycle Media Action—specifying the No Files Selector—in order to re-initialize the component Backup Sets of your Storage Group before any initial Member of a component Backup Set exceeds its space on the Storage Group's designated initial Member drive. My personal suggestion is that you abandon the idea of using a Storage Group as a Proactive script Destination, and instead create individual scripts with individual Backup Sets as Destinations for at least each of your "Remote" Sources. It'll be more work to set up, but give you fewer long-run problems.
  12. Lennart_T, Unfortunately Retrospect won't wait for the Transfer to finish before running the Backup. And that has the unfortunate consequence discussed beginning with the second substantial paragraph of this OP in a January 2017 thread. Since that post is phrased in terms of the Retrospect Mac terminology, here's another post that backy can use for translation to Retrospect Windows terminology. My Support Case giving a product suggestion for overcoming the consequence was ignored. Therefore I'd suggest that backy use your "New Backup Set" suggestion, even though that would create a complication.
  13. DavidHertzberg

    Replacing External RAID

    francisbrand, I think on the Forums we're now supposed to say "Get a Drobo", since Retrospect Inc. was acquired in June 2019 by StorCentric—which is also the parent company of Drobo (genuflects in the direction of San Jose CA đŸ€Ł ). However at the moment you can't get a Drobo—because of some kind of supply chain hangup, which—I have it on excellent recent insider authority—is a reason the release of Retrospect 18.0 has been postponed until 2Q 2021. So here's the most recent thread in the Retrospect Forums discussing backing up to a Synology NAS—model number not specified. Its OP says backing up to it is working fine; the thread concerns a problem with getting a -2265 error in connection with Grooming. The last post in the thread, by the OP on 9 February, says "I guess at this point I need to upgrade to [Retrospect Mac] v17.5.x and hope that fixes this issue unless the group has any other suggestions." Note that the cumulative Retrospect Windows Release Notes say, for the 17.5.0 Engine, "Grooming: Fixed issue where grooming fails under certain scenarios (#8700)"—which probably also applies to Retrospect Mac since the Engine is the same under the GUI hood for both variants. Here's the Knowledge Base article for NAS backup, re-titled in 2020 to "How to Set Up Drobo for Retrospect Backup". However the article existed in much the current form—but discussing the NAS in brand-independent terms—before the acquisition; it's now merely had some Drobo-specific information added within it, and the YouTube video "Retrospect for Mac: Setting up a NAS as a Backup Destination" linked to within it has now merely had the audio edited to add the term "Drobo". (That illustrates the new "get a Drobo" mindset of Retrospect "Inc.".) If your "backup server" is booting Mojave or Catalina or Big Sur, pay attention to the "Full Disk Access on macOS Mojave and Catalina" section of the KB article. Since it probably was some years since you set up a NAS as a destination, you may want to review a 2020 thread about that starting with this post by me. The main take-away from that thread (you should, per my P.S.s, ignore anything I said about the uniqueness of the "marker" file) is that your backups need to be—directly or hierarchically—stored inside a folder named "Retrospect". In the third paragraph of this post further down that same thread, I quote another Forums expert as saying "The Retrospect folder can exist as a top level folder on any HDD connect [sic] directly to the Backup Server either internally or exterï»żnally. On an SMB share (e.g. Samba on a NAS) the Retrospect folder must reside in a share folder ....". That means you can't rely merely on the NAS share folder being named "Retrospect", as one administrator did. And use SMB 2 or 3; SMB 1 isn't supported anymore.
  14. A long-existing facility of Retrospect that I'd never used turned out to be key to implementing Phase 1 of my project of converting my late ex-wife's 1990–2005 literary and artistic files for future use by any of her friends or relatives. Phase 1 is the literary files; Phase 2—the artistic files—may require some programming. Retrospect solved the second of two Phase 1 problems, but IMHO other administrators should also know about the first problem. These files are on a HDD in a Digital Audio G4 that my ex-wife had given me in 2005 after I copied the HDD contents onto a PowerBook she'd bought. The literary files were written 1990–2005 using Mac MS Word 5.1a under OS 9.1, so they're in .doc format (no file extension on Classic Mac OS)—which I'm not sure will be readable by a future word processing app. When she complained in 2015 that she couldn't open the old files in Mac Word 2011, I dragged her G4 out of the back of my bedroom closet, took a thumb drive containing several hundred files over to her apartment, and demonstrated that she could with significant difficulty convert them to .docx format. However I was occupied with the ultimately-fatal illness of my longtime guitar teacher and friend , so I didn't then volunteer to do the several days of conversion work for her. She died 13 January, but her executor can't yet get me into her apartment to see if she later did the time-consuming conversion herself—which I doubt she did except for a few selected files. So four weeks ago I decided to do the conversion myself, using LibreOffice Writer on my 2016 MacBook Pro. I copied the files in her old "Microsoft Word" HDD folder onto a "Microsoft Word etc." folder on a thumb drive, copied the files from that folder onto a "Converted ..." folder on the same thumb drive, and then plugged the thumb drive into my MBP so I could convert them using LibreOffice Writer. I was able to convert 800 of the 900 files in either 20 seconds per file if LibreOffice recognized the file as .doc, or 30 seconds per file if it didn't. Note that the thumb drive, which I pulled out of its Best Buy 2015 wrapper, is formatted for Windows—which turned out to be significant as per two paragraphs down. The first problem was that, for another ~40 filenames, LibreOffice wouldn't do a name-preserving Save As. In 2015 I had encountered a filename for which Word 2004 replaced everything after "#2." as the the first three characters with "docx'". I then though this was a Microsoft stupidity, but 3 weeks ago I realized that the stupidity is a consequence of a Windows-friendly refinement in the way Apple handled the transition from Classic Mac OS to OS X. Classic Mac OS prohibited only the character ':' in filenames, but Windows NTFS prohibits basically all the characters listed in this Wikipedia article section (note '.' is specially treated). Apple's refinement—to avoid making users go through an editing process while upgrading—was to allow those characters in existing filenames, but to require that they be eliminated in every Save As to a Windows-formatted drive. In that case Apple's Save As code—used in both Microsoft Word 2004 onward and in LibreOffice—assumes the rightmost '.' in any filename is the beginning of a file extension, which wouldn't be true for a filename still in its Classic Mac OS format—which is still OK on OS-X-formatted drives. That meant I had to pre-replace filename characters banned by by Windows NTFS, of which '.' and '/' and '?' and straight-double-quote were the most common in my ex-wife's files. I did that by copying-and-pasting each file whose filename contained such characters from the G4 HDD to the G4 desktop, renaming the desktop copy with '_' or '-' or " quest" replacing its illegal characters, copying the desktop copy to its proper hierarchical place in the "Microsoft Word etc." folder on the thumb drive, and then deleting the desktop copy. LibreOffice on my MBP can convert a file with such a pre-replaced filename to .docx format with a name-preserving Save As. This is OK, because the friend/relative may use Windows. The second problem was that ~100 of the files converted in LibreOffice Writer as simply rows of hash symbols—rather than their contents when I opened them in Word 2004 on the HDD under OS X 10.3 Panther. I decided OS X 10.3 on the G4 had somehow messed up those files when I copied them from the HDD to the "Microsoft Word etc." folder on the thumb drive, and that this was probably because I'd used the Finder's ability to copy nested folders. At this point I remembered that Retrospect has long had a facility named Duplicate in the version 6.1 I had on an OS X 10.3 drive on the G4. Duplicate (still named that in Retrospect Windows, but renamed Copy in Retrospect Mac 8—distinct from Copy Backup or Copy Media Set) copies entire volumes or defined-to-Retrospect subvolumes (renamed Favorite Folders in Retrospect Mac 8 ) between a Source and a Destination. It goes beyond the Finder in having an option to compare the copied files and show the results in a log, and another option to delete successfully-copied files from the Source. What from fixed my hash row is that Duplicate's directory traversal is independent from that of the Finder. But Duplicate also logged two files it couldn't copy; I'd not spotted the character '/' in their filenames. LibreOffice on the MBP successfully converted most of the files I re-copied from the HDD to the thumb drive's "Converted ..." folder using Duplicate on the G4. Then I Finder-copied one by one the dozen files LibreOffice still couldn't convert. One file ultimately converted as a garbage line; it was garbage on the G4 HDD. IMHO the fact that Finder-copy didn't mess up a file when it was copied individually means that there's a bug in hierarchical Finder-copy, at least in OS X 10.3.
  15. 😧😧 I originally tried to test this out early this morning, but ran into a problem that may be peculiar to my installation—rather than Retrospect Mac 16.6. I first Removed and Added—afterward changing the Options—on the "backup server" Source definition of my MacBook Pro "client" to allow Wake-on-LAN, and did the same Options-changing on my two daily No Media Action Backup scripts (the "sacrificial" script and the "real" script—after re-checkmarking the MBP on all my scripts that use it. I then tried putting my MBP—booting macOS 10.13 High Sierra—to sleep via the Apple menu; but except for one time it wouldn't stay asleep for more than a few seconds. However tonight I experimented further, and I can get my MBP "client" to stay asleep—initiating that via the Sleep item on the Apple Menu—if in System Preferences->Energy Saver->Power Adapter I change the Turn display off after slider from Never to 3 hours. Then provided Wake for network access is check-marked on the pane below the slider, putting the MBP to sleep while running my "sacrificial" script (it uses the No Files Rule—note Rule is the Retrospect Mac term for Selector, but scans a while because I've now got a thumb drive plugged into my MBP) results in its waking up in a few seconds. I have no idea what the Windows "client" equivalent of the System Preferences->Energy Saver->Power Adapter settings would be. Nigel Smith will know. And yes, Nigel Smith, I knew about require password on wake; I wondered if some of your cleaning people might moonlight for Chinese Intelligence. 😧 P.S.: Forget what I said in the third paragraph of this post. I stayed awake long enough to try this on my scheduled 3:00 a.m. "sacrificial" and 3:05 a.m. "real" Backup scripts, and things didn't work out as I'd hoped. I woke up at 6:45 a.m., and remembered that since Spring 2015 I've been using an external keyboard and a mouse connected to a bus-powered KVM switch—so that I can switch both of them them back and forth between my MacBook Pro and an old Digital Audio G4. Bus-powered means the KVM switch shuts down unless either the MBP or the G4 is awake, so the spacebar on the external keyboard doesn't wake up the MBP. Pushing the spacebar on the MBP's built-in keyboard does wake it up, but that doesn't get an already-running Backup script out of a frozen state after I've slept the MBP while the script is running. In short: Wake-on-LAN still doesn't work for scheduled scripts.
×