Jump to content

DavidHertzberg

Members
  • Content count

    1,044
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by DavidHertzberg

  1. Gee, Indi-Tech, and yet you only joined these Forums on 2 May 2019. Maybe your big boss belonged under a different Forums "handle"? Anyway, good of you to condescend to ask for help from us home professionals. I'll deal with your Favorite Folder problem later, to the extent I can, after I've had dinner and watched a movie.
  2. I spoke by phone with the head of North America Retrospect Sales earlier this afternoon. He said there are no immediate plans for instituting a charge for the Linux client. I told you so (last quote). He also said that further enhancements to Shared Scripts in the Web-based Management Console are now scheduled for September 2019.
  3. Indi-Tech, Retrospect Inc. could have, in fact, put a sentence or two about "ipsave" in the User's Guide. However a search of the cumulative Release Notes shows this feature was added in September 2014 to Retrospect Mac, and in March 2015 to Retrospect Windows. It therefore ran afoul of the User's Guide policy described in this post in another thread (which is not the only place I have complained about it). But Google shows you're a consultant (or someone has stolen your "handle" and logo), so you'll have to develop an encyclopedic mastery of the Knowledge Base articles to justify your charging the big bucks—which is why I think Retrospect Product Management intentionally adopted this "disappearing documentation" policy as part of its "go big or go home" strategy. lwhitten complained about the connection not showing in this post I linked to above. He/she was using "a trial of [Mac] v14", and you're using Mac version 16, so Nigel Smith must be somehow hitting the sweet spot in Retrospect versions—or there's another explanation. As for the speed of backup over a LAN, dittberner@dbr3.de complained about that for nearly 2 years before switching to another client-server backup application. I came up with a hypothesis here, but my hope—expressed a couple of posts down in that thread—that things would improve with version 16 has not been realized. My average speed in Recycle backups over my home LAN is around 600MB/min; my hypothesis might explain why ChronoSync—which you're probably using in Synchronize mode—is faster.
  4. As you can see from the color-named progression ("three cheers for the Red, White, and Blue") of my Media Sets in the OP, this morning I was scheduled to do my Saturday Recycle backup to "Media Set White"—whose "1-Media Set White" Member is on portable HDD "G-DRIVE White". Since the Retrospect Agent Reply in the post directly above this evinces a certain skepticism about whether my portable HDDs have been properly cabled to my Mac Pro "backup server" when I switched them, after I had yesterday un-cabled "G-DRIVE Red" (to take it to my bank safe deposit box) and cabled "G-DRIVE White" I ran a "sacrificial" script with No Media Action backing up my MacBook Pro's SSD to "1-Media Set White". This ran OK in 4 minutes. I then scheduled a repeat of the same "sacrificial" script to run 5 minutes before the "sacrificial" script with Recycle backing up to "1-Media Set White" early this morning. All three scripts ran OK in succession early this morning backing up to "1-Media Set White" : the No Media Action "sacrificial" script backing up my MBP , followed by the Recycle "sacrificial" script backing up my MBP, followed by the Recycle "real" script backing up my 4 drives—starting with my MBP's SSD—and a Favorite Folder. I have to admit I was disappointed with missing the opportunity to demonstrate my bug-proving prowess to Retrospect Tech Support. I can think of only 3 possibilities for why the Saturday scripts ran OK this morning: My "G-DRIVE"'s cables had previously been jiggled loose by me or my cleaning lady on previous Fridays, but not yesterday. This seems unlikely, because I'm pretty careful and because my cleaning lady only comes on alternate Fridays. One of my two "backup server" USB3 cables, which are swapped into use every Friday morning, is defective. This seems unlikely, both because the OP shows failures on four successive Saturdays and because the same two cables worked fine connecting "G-DRIVE"' portable HDDs on Sundays through Fridays. On Friday morning I upgraded to Retrospect Mac 16.1 from 16.0. Whoever wrote the Retrospect Agent Reply in the post directly above this made that upgrade suggestion; maybe he/she knew knew something about an undocumented bug fix involving Recycle and APFS. I'll test again next Saturday morning.
  5. Retrospect 16.1 for Mac and Windows has "New Retrospect Management Console: Pause/Unpause/Stop support", per this post in another Forum. Is that a truly new capability for a Web-connected Retrospect monitoring application (as opposed to the LAN-only Retrospect Mac Console), or is it already in Retrospect for iOS? If the capability is already in Retrospect for iOS, please post on what precisely the capability is. P.S.: I just found this blog site, with posts claiming to have developed Retrospect for iOS up through version 2. So Brian Dunagan, if you're not too busy being COO of Retrospect Inc., maybe you could obtain from one of your subordinates an answer to the above question.
  6. Despite the lack of non-Partner-applicable progress (other than "Pause/Unpause/Stop support", which I think may be already in Retrospect for iOS) described in the last paragraph of this post in another Forum, DovidBenAvraham will try to keep the mentions of Shared Scripts here and here in the Wikipedia article. If the promised deployment enhancements aren't in Retrospect 16.5—expected in early September 2019—however, DBA's afraid those mentions are going to have to be removed.
  7. To which I replied [start-end underscored words changed to underlined words, which the Forums allow but the Support Case software doesn't]: "G-DRIVE Red", which is a USB2 portable HDD, was—and still is—cabled to my Mac Pro "backup server". Note that, as soon as the "sacrificial" script terminated on 11 May with the -1102 error. the "real" script began to run. It proceeded several minutes after logging "Finished scanning backup set data files" before I stopped it, which I did because the Summary was showing that the run was methodically examining the existing files in "Media Set Red"—despite all 3 schedules for the script specifying Recycle. Then, after I did a Rebuild of "Media Set Red"—which I stopped after the log said "Adding to 29.9 GB of backup set data, starting at file index 51", I'm pretty sure I Finder-deleted file "1-Media Set Red" on "G-DRIVE Red" and Removed/reAdded "Media Set Red"—which doesn't show in the log. After that a Repeat Never schedule of the same "real" script to "Media Set Red" ran OK. Note that the same sequence of script runs the previous Saturday 4 May to "Media Set Blue", with its member on "G-DRIVE Blue", got pretty much the same results. The only differences are that I manually-scheduled a run of the "real" script I created after stopping the automatically-scheduled run, and stopped that run after it logged "!Cannot find parent directory for file Scalloped-Frame-V-2.png in backup 4/13/19 4:06:29 AM"—which certainly implies that it wasn't doing a Recycle, and that I let the subsequent Rebuild for the existing "1-Media Set Blue" run over an hour to completion. I alternate portable HDDs weekly between 2 USB-A-to-USB-Mini cables attached to different built-in ports on the back of my Mac Pro "backup server". Note also that these 3 portable HDDs always work fine for the rest of the week's No Media Action scheduled runs. So, despite my not having attended Hogwarts, I think there's a bug in Retrospect Mac 16.0 for Recycle. I will now proceed to upgrade to Retrospect Mac 16.1 for both Engine-Console and Client.
  8. It being the evening of 14 May—close to my expected date for the release of Retrospect 16.1, ""I dipped into the future" again. The Knowledge Base articles haven't been updated yet—with the exception of "How to Set Up the Management Console", but the 16.1 downloads are on the website. As for updated "What's New" chapters in User's Guides, I don't want to laugh so soon after dinner. The question applicable to this thread is "What improvements have they made in the Web-based Management Console?" As shown by the 16.1 version of the cumulative Retrospect Windows Release Notes, the answer appears to be "not too many, but promising". For the Engine they are: New Retrospect Management Console: Pause/Unpause/Stop support New Retrospect Management Console: Versions, Editions, Platforms listed Improved Retrospect Management Console: Disable deployment for an existing shared script Improved Email Notifications: stopped scripts now generate email with title "Execution stopped by operator - Retrospect" For both Engine and Windows Client there is also—and this will make a lot of administrators happy : New Windows 10 May 2019 Update certification The first and third Engine improvements actually IMHO sound like a real step forward in 2-way capability. However as of this evening it's evidently not enough to persuade Retrospect Product Management to actually insert the Management Console Add-On into the Product Configurator, so that ordinary non-Partner administrators can add 2-way Console capability (for US$49 or more) to their installation of Retrospect without saying "pretty please with cherries on top" to a salesperson on the other end of a phone line. How the dickens do they expect the Management Console's 2-way capability to be adequately beta-tested without the help of ordinary administrators? (And testing, for the few of you who don't already know, has been Retrospect's product weak spot for the past 30 years. ) OTOH there appears to be no progress towards the "Management Console - How to Use Shared Scripts" KB article promise that "Support for local sources, local destinations including disk, scheduled scripts, and more extensive scheduling options will be available soon". I have a jaundiced vision of running battles in the halls of Walnut Creek between developers shouting "Make the GUI look like Retrospect Windows!" and other developers shouting "Make the GUI look like Retrospect Mac!" I hope there isn't blood spilled. However a more developer-realistic vision is that the engineers just didn't have time to make releasable progress on that front, because they were fixing 9 bugs—of which 4 for Retrospect Mac (only 2 of which affected Retrospect Windows) involved Storage Groups. P.S.: There is progress as of late October 2019 on "Support for local sources, local destinations including disk, scheduled scripts, and more extensive scheduling options". See this post in a more-recent thread, and the Granular Remote Management webinar it links to in the third paragraph.
  9. This suggestion is an offshoot of this thread in "Windows Products—Retrospect->Professional", which I shall henceforth refer to as the "New Windows user" thread. It is motivated by iCompute's astounding revelation in post #21 (posts beginning with #21 are on page 2 of the "New Windows user" thread) : "I have a Mac laptop, with a copy of the Mac Retro 'console' on it. Just 'cuz, I fired up the console, and lo and behold, it *works* on the WINDOWS Retro server. As far as I can tell, I get the full function of the Mac engine/console via the Mac console when operating/controlling the Windows Retro server." In the fourth paragraph of post #22 in the "New Windows user" thread, I belatedly realized that we shouldn't consider iCompute's revelation quite so astounding, because what is now known as the Retrospect for iOS app has been working—connected to a Retrospect Windows "backup server" as well as a Retrospect Mac "backup server"—since 2010. This means that the "engine side" of Retrospect.exe retains the capability of exchanging messages with another app—even if that app is not the Retrospect Launcher. In post #23, after doing some inferences based on an 18 January 2007 article in The Register by Ashlee Vance, I concluded "My guess is that the Retrospect engineers simply left the code for interprocess communication in Retrospect Windows 7.5 and following, where it has remained ever since—ready for iCompute to activate its inter-machine capability with a Retrospect Mac Console." So creating a separate Windows user-space GUI app similar to the Console app in Retrospect Mac seems feasible, so long as the GUI app is run on a different Windows machine from the "backup server" Engine—as is allowed for Server editions of Retrospect Mac. What makes this suggested app desirable is the discussion on page 1 of the "New Windows user" thread. iCompute, an experienced Retrospect Mac administrator faced with his first Retrospect Windows installation, was especially flummoxed by the fact that the Retrospect.exe app stops any running scripts cold if he logs off—unlike the Retrospect Mac Engine app if you quit the Console app. Guided by ProFromGrover, he discovered that the Retrospect Dashboard.exe app is a way to work around this problem, which I had explained in post #2 is a consequence—along with the need for the Retrospect Launcher Windows service—of security features added to Windows Vista and beyond. What makes this suggested app seem practicable with a reasonable amount of Retrospect Inc. engineering effort is a further inference from the Ashlee Vance article, stemming from the fourth paragraph of post #23 in the "New Windows user" thread. It is that by December 2006 the EMC Insignia engineers had made significant progress in developing a Windows, as well as a Mac, version of the separate Console app. If this inference is correct, and the source code for that Windows Console was saved, it should be possible to update that source code with the fixes that were made to the Retrospect Mac Console in later point releases of Retrospect Mac 8 and later versions of Retrospect Mac. There is a caveat: the resulting Retrospect Windows Console app would, barring extensive modifications, use the Retrospect Mac Console GUI—although it would be fairly easy to change the terminology within the GUI back to the terminology of Retrospect Windows. What makes this suggested app seem more desirable is that, based on what other administrators have posted on page 1 of the "New Windows user" thread, the combination of the old Retrospect GUI and the limitations imposed with Windows Vista makes using Retrospect Windows a kludge-filled mess compared to using Retrospect Mac. That's clearly why iCompute wrote at the end of post #21 "Way back when I posted this thread, I had no idea this would work. Turns out that it does. I hope it's supported. ;->" I think that, after reading 1.3 screen pages in the third bulleted item in this section of the old Wikipedia article, administrators running a Server edition of Retrospect Windows will use the proposed Retrospect Windows Console app—and bless Retrospect Inc. engineers for developing it.
  10. Thank you, Nigel Smith, for that suggestion. I'd forgotten about this prior thread of Nigel's, to which I made a few ignorant contributions. However it looks as if this post in an earlier thread is closer to solving Indi-Tech's problem. Nigel's problem dealt with "clients" that can be on either of two different subnets when they connect to his LAN, with his "backup server" machine only sitting on one of the two subnets. lwhitten's problem, in the earlier thread, was that—for speed in backup—he/she wanted his "client"'s Client to access his "backup server" over a dedicated cat6 cable port rather than via a router with dynamic DHCP IP addresses. Using ipsave—described in the "Binding Retrospect Client to a specific IP address" Knowledge Base article Nigel linked to above, lwhitten found it worked OK for scheduled backups and "kind of OK" for Proactive backups. Indi-Tech's "LAN data server" that is also a Retrospect "client" is, I confidently assume, not being backed up with a Proactive script—since it is undoubtedly always connected to the LAN. In case it's not obvious why I'm making this post, it's so other administrators will in the future be able to find a solution for similar problems by doing a Forums search. An enabling Client "ipsave switch" was fixed in Retrospect Mac 11.5 and in Retrospect Widows 10.0, but Retrospect Inc. never described its function in either variant of the User's Guide—only in the KB article.
  11. Indi-Tech, I have no idea, except that it sounds as if the "client having (2) NICs" is actually a LAN data server, which implies that it is shared on the LAN by the "Retrospect backup server" machine as well as other machines. If so, is there any reason that you can't back up the "client having (2) NICs" as if at least its "server_RAID" drive is a network share to the "Retrospect backup server" machine rather than as a "client"? See pages 71-72 of the Retrospect Mac 16 User's Guide. Please be aware that I'm a home user with a simple LAN, composed of "client" machines and a single "backup server" machine, all of which have only one NIC apiece, and I don't have a LAN data server. You'd have to set up an afp: or smb: address that would somehow specify using the "LAN data server"'s secondary IP; this makes it seem as if you can do it with AFP. P.S.: Changed first paragraph to suggest that "server_RAID" be treated by the "Retrospect backup server" as a network share, and split off second paragraph with caution on how to do it.
  12. Indi-Tech, My little brain is thoroughly confused by "the client (primary server)" in the third paragraph of your immediately-preceding post, and by "hosts a share that is used by backup server because the backup server also hosts a share that requires backup" in the final paragraph. Please rewrite that post using the terms "LAN data server" and "Retrospect backup server" to distinguish the separate functions of these machines/drives on your LAN. You'll need that rewrite, if for no purpose other than to communicate clearly with Retrospect Technical Support, which I suggest you do—ASAP to get your free personalized T.S. if possible.
  13. DavidHertzberg

    Duplicate-Copy has stopped working in 15.6

    Fredspon, As this post in a 2012 thread shows (click the blue-underlined link to be taken to it, then click the Back arrow in your web browser to be taken back here), "it's not a bug, it's a feature!" There's a zero-byte file named "Backup Media" in the "Retrospect" folder on the "backup disks" Member(s) of your Backup Set that's designed to activate the feature. The reason Dantz Development Corp. (the predecessor of Retrospect Inc.) put in this feature years ago is to prevent administrators from "holding it wrong" (that's a Macintosh joke, referring to a Steve Jobs on-stage remark about a previous version of the iPhone), as this post (responding to the one linked to in the preceding paragraph of this post) says. If you've scheduled a Transfer operation (not "program"; you'd better be more precise about terminology if you want us to help you ) after each Backup operation, then use Transfer Snapshots—here's the Tutorial that you should watch after the one linked-to in the next sentence. If not, use Transfer Backup Sets—here's the Tutorial that you should watch before the one linked-to in the preceding sentence. For the scripted operations, see pages 206-217 of the Retrospect Windows 15 User's Guide; for the Immediate operations, see pages 141-152.
  14. Indi-Tech, Apologies for not realizing until now what your problem probably is. First, for background, you should watch this Retrospect Mac Tutorial video again—even if you have watched it already. Note that, at minute 1:47, the last thing the head of RTS does is add "client" computers—and he does it by first specifying the pre-defined name for the NIC and then specifying the method of scanning for "client" computers. I strongly urge you to specify Use Subnet Broadcast, and I hope that "is added manually with the 'service' subnet" means that's what you did. But the key requirement IME is that the Client on each "client" not yet have a "backup server" address stored in a "secret field" within it at that point—which is the situation assumed in the Tutorial, meaning it hasn't yet been imprinted with the address of the "backup server" with which it is supposed to communicate. That imprinting is done by the "backup server" when you first Add a "client"; therefore (as told to me 4 years ago by Andy —now departed from RTS) you must Uninstall and then Install the Retrospect Client on each "client" computer. I have done this in the past by downloading the latest Retrospect Client .zip from the website, rather than messing with trying to accomplish this from the Console. But before running the Retrospect Client Installer.pkg for the "client" you must have first Removed that "client" computer from Sources via the Console. Only after running the Retrospect Client Installer.pkg on the "client" computer can you then re-Add the "client" into Sources from the Console—via Use Subnet Broadcast—and thus imprint the "secret field". Up through Retrospect Mac 15, the "secret field" where the Client stores forever (I'm not sure whether Refresh can change it) the identity of its imprinted "backup server" used to be displayed—uneditable—in the Advanced tab of the Client; version 16.0.2.101 displays 0.0.0.0 instead for what is now called the Private Backup Server field—which may merely be a byproduct of Engineering hijacking the associated dialog control for use in editing the newly-added Public Backup Server field when needed for Remote Backup. The unchangeable-after-imprinting function of the "secret field" is informed speculation, BTW, since I don't have access to the Retrospect source code. After you've done this for each "client" computer (the sequence I recommend is: [1] do all "client" Removes from the Console, [2] do the Client Uninstall and Install on each "client" computer, and [3] do all "client" Adds from the Console), you'll have to re-add the "clients" to each Backup/Archive/Proactive script that uses them. After doing all "client" adds for a script by selecting the script in Scripts and then check-marking the boxes for all desired "clients"' in the panel shown by clicking the script's Sources tab, you should Save the script and then click its Summary tab. If the "clients" don't appear in the backing-up sequence you want, you can—with some GUI kludginess—drag their names in the Summary list pane into the desired sequence (thanks derek500 ); if you've dragged, do another Save of the script. If you don't believe me, read this final post in the Forums thread I linked to up-thread. Nigel Smith says what I suggested didn't quite work for the problem he was having, but that it was because his problem was dealing with a Fortigate setup—with "client" computers connecting at random to only one NIC at a time—rather than the multiple NICs you evidently have on your version of the Mac Pro (3,1). P.S.: Changed 2nd substantive paragraph to get rid of male-chauvinist-like language, and clarify that paragraph—I hope.
  15. Indi-Tech, Since you're using Retrospect Mac version 16, look in that User's Guide at page 64 for "Network Interfaces" and pages 78-81 for "Advanced Networking". I have no knowledge of VLANs; I just now took a look at the appropriate Wikipedia article. However you might find an answer in this relatively-recent Forums post and its successors by an administrator who is much more knowledgeable than I am about such matters. I have also noticed that the version 16 Mac Client's Advanced tab has a new Public Backup Server entry capability. As is unfortunately par for the course in recent versions of Retrospect, the "What's New" chapter of the UG is pure marketing drivel, and doesn't discuss that capability. However you might try clicking the lock icon and entering your "Client"'s password to make changes, then clicking the Edit button and entering the address of the "backup server". I must caution you that Your Mileage May Vary, and see the P.P.S. below. Finally, how did you generate the screenshot in your most-recent preceding post—the one you posted as if it were a copy of another post? Was it with the Retrospect "backup server", or with another application? P.S.: I suggest you phone Retrospect Technical Support at (888) 376-1078 or (925) 476-1030‬; they're on extension 3. If you bought Retrospect Mac 16 within the past 30 days, I believe they'll give you personalized help for free. P.P.S.: The new Public Backup Server entry capability is described in this section of a Knowledge Base article, and is intended for use in Remote Backup (introduced in version 15, so nothing remains in the UG). But IMHO that doesn't mean you couldn't pervert it to do what you want. You could speed the perversion by simply installing a server.txt file on each "client" machine, as described in "Installation Process" in the KB article. However using this capability would for now require converting your scripts to Proactive, so you'd do better to phone RTS instead.
  16. DavidHertzberg

    Can I safely downgrade from V15.61 to V12?

    x509, Isn't it rather ironic how the decision of some Brussels bureaucrats (with which I, as a computer user, generally agree) caused Retrospect Inc. to add a valuable new feature? Of course there was a temporary price for Retrospect Windows administrators, as mentioned in the fourth paragraph of this post in another thread.
  17. Indi-Tech, You don't say which version of Retrospect Mac you are using, so I'll refer you to the Retrospect Mac 15 User's Guide. "Network Interfaces" on page 60 sounds applicable to your problem. For further information, see "Advanced Networking" on pages 74-77. I suggest that —at a minimum—you add your "client" machines with Subnet Broadcast on your "service subnet". If you feel more energetic, you can Add Source Directly—for which you will have to assign each "client" machine a fixed address on your router using its MAC address. That's what I do on my home LAN (with "backup server" and "client" now running Retrospect Mac 16), for which Multicast stopped working a couple of years ago for mysterious hardware-related reasons. But I have only one subnet, so Add Source Directly may not solve your problem —whereas Subnet Broadcast probably will.
  18. Assuming, x509, that "I want to confirm that that approach works" means "I want someone else to confirm that that approach works" rather than "I want to confirm that that approach has worked for me", I've done the following—using Retrospect Mac 16.0.2.101: Every morning except Saturdays at 3:05 a.m. I schedule a No Media Action (Retrospect-Mac-speak for Normal) backup of my MacBook Pro "client"'s only drive, but 5 minutes before that "real" script is scheduled I still schedule—out of habit although it's no longer necessary— a "sacrificial" script that does the same backup for that same "client" with the No Files Rule (Selector). x509 doesn't pay me enough money to stay up until 3 a.m., so last night before I went to bed I re-scheduled this morning's "sacrificial" script for 3:04 a.m.. My BPH awakened me around 3:40 a.m., upon which I booted my MBP followed by my Mac Pro "backup server". The "sacrificial" script" immediately started running, while the Activities panel (the Retrospect Mac equivalent of merged panels from all the Activity Monitor tabs except History) on my Console showed a yellow warning icon—which when clicked said "Waiting for Media Set White" (which I would have named Backup Set White if I had been running Retrospect Windows)—scheduled before the "real" script. As soon as the "sacrificial" script had finished running in about 4 minutes, the warning icon disappeared and the "real" script—with the All Files Except Cache Files Rule (Selector)—began to run. This is the behavior I've had since I started scheduling "sacrificial" scripts with Retrospect Mac 12 in February 2017. So, barring any unlikely scheduling difference between application variants, I predict "that that approach works" for Retrospect Windows too.
  19. DavidHertzberg

    Can I safely downgrade from V15.61 to V12?

    But Transfer Snapshots and Transfer Backup Sets have been in Retrospect Windows since 7.7, although there were some bug fixes as late as Retrospect Windows 11.5. Am I missing something about your wish for Retrospect Windows 15, x509?
  20. DavidHertzberg

    Selector doesn't work for only 1 Backup Script

    Surely, x509, I don't need to tell you why and how to file a Support Case for a bug.
  21. DavidHertzberg

    Can I safely downgrade from V15.61 to V12?

    x509, Sorry "life has been happening" for you, but welcome back to the Forums. By "the transfer datasets features of V15", do you mean or something else in a previous release? Since the beginning of April 2019 I've been using Retrospect Mac 16.0.2.101. One minor problem I've had that may affect everybody upgrading to version 16 concerns scanning Media/Backup Sets with a Recycle script. I do this twice each Saturday as I Recycle the Set whose sole Member is on one of my three portable HDD drives (I'm very 20th century; I swap one of the drives every Friday in my bank safe deposit box, because until last October I didn't have the upload speed for Cloud backup—whatever that is ). Early Saturday morning I run a Recycle backup of all my 6 drives, but 5 minutes before that is scheduled I still run—out of habit although it's no longer necessary— a "sacrificial" script that does the same backup for my first "client" with the No Files Rule/Selector. The last 3 Saturdays I've found the scanning phase on the "sacrificial" script running very slowly, because of errors such as Once I notice this is happening I pause all scheduled runs and stop the "sacrificial" script, then do a Rebuild of the Media Set being Recycled, and have no further problem for the remainder of the week with that Media Set—even when doing the same Recycle with the afterward-un-paused "real" Saturday backup. I didn't have the same problem when I upgraded to Retrospect Mac 15.6.1.105 in January 2019, and the problem may be peculiar to Retrospect Mac 16. But be warned that, if any of you downgrade from Retrospect 16.0 to Retrospect 15, you may have to do a Rebuild of your Media/Backup Sets from the existing Members. BTW, x509, I noticed that in your post directly above this one you made the same mistake I made in this post in the thread where lhlo accused me of "condescension". You initially thought the first letter of "lhlo" was an upper-case 'I' (the letter whose name sounds like "eye") instead of a lower-case 'L'. Maybe it would have been more polite if, instead of saying lhlo had picked a cutesy-poo "handle", I had merely suggested he/she either take a course in Human Factors or repeat the (Canadian equivalent of?) third grade.
  22. Saturday night 30 March I hastily decided that I needed to do a full-SSD restore of my Late 2016 MacBook Pro. Because I didn't have a USB-C to-Firewire adapter, I started to do the restore from Saturday morning's Recycle backup over my LAN. This was stupid, because the restore would have wiped out my Retrospect 15.6.1.105 Client, but it didn't get that far. After "Finished deleting 2,385 unnecessary files and 198 unnecessary folders on destination", it bombed with "!Trouble writing folder "Macintosh HD/Library/", error -1,017 (insufficient permissions)". How does one avoid that with Retrospect, since I'm told Time Machine avoids it? Meanwhile I was left with a MBP SSD with no usable macOS on it. I next attempted to download and install Sierra on the SSD, expecting to then be able to solve the permissions problem and rerun the backup application's Restore of my complete High Sierra disk. However I couldn't find how to do that download of the installer, and it was by then after Apple Support's 11 p.m. EDT closing time. I should explain here that, for reasons explained in this KB article and this Forums post, I'd prefer for now to keep all 6 drives on my 3 Macs using HFS+ rather than APFS. So I phoned Apple Support around noon Sunday. I spent a couple of hours talking to the senior Support technician Jenna. I first downloaded a High Sierra installer, which left me with a single APFS partition. Disk Utility wouldn't let me erase that partition, or delete it because it was the first one created. I worked on the problem for another hour while Jenna took a four-hour break; I ended up with an SSD which sat forever with 7 minutes to go when I booted into the Recovery Partition, and stopped booting after a couple of minutes—showing a big white circle crossed by a right-slanting diagonal line—when I did a conventional boot without Command-R—etc.. Here's what happened after I took my MacBook Pro in to Mike's Tech Shop on Monday 1 April: Despite my (open-box 15-inch Late 2016) MBP having come with macOS 10.12 Sierra installed, Apple has some database that says it can't run under anything earlier than macOS 10.13 High Sierra. So that's what Mike's had to install on Tuesday, and it formatted the MBP's 500GB SSD as a single APFS partition—which High Sierra and above inescapably do with any SSD. Tuesday morning I connected an external Firewire HDD to my 2010 Mac Pro backup server running Retrospect Mac 15.6.1.105 under macOS 10.12.6 Sierra, changed the permissions on all existing top-level folders to Read-Write for all users, and ran the same restore to the HDD. It ran, but got over 90 cases of "[*] MapError: unknown Mac error 22" and ended with "!Trouble writing folder "/Volumes/Macintosh HD OS X+/.HFS+ Private Directory Data", error -1,101 (file/directory not found) 3/31/19 2:11:03 AM: Execution incomplete". The HDD remains formatted with HFS+. Tuesday afternoon I took my MBP home, booted it, and—using the pair of adapters I had bought to go USB-C-to-Firewire—ran Migration Assistant to copy my backed-up files from the external HDD onto the MBP's SSD. I chose the iCloud option, because I want to be able to access those files from my MacPro in case my MBP gets messed up again. It wouldn't install SUIDGuardNG.kext, but that turns out to be incompatible with High Sierra. My MBP then would boot under High Sierra, but only using the MBP's built-in display. I normally use an inherited Apple 27-inch LED Cinema Display, connected to my MBP via a KVM switch and a StarTech USB32DPPro adapter. That adapter requires software from DisplayLink.com; at first it wouldn't install. I eventually found this and this Web page, and got the Cinema Display working Tuesday night. So what do you suggest as a substitute for this complicated process? I should note that, having also bought from Mike's a pair of adapters to go USB-C to-Firewire, I have since tried to boot my MBP from my external Firewire HDD.—it doesn't work.
  23. DovidBenAvraham has been faced with a new problem by this revised Knowledge Base article, which now says: The second issue sounds as if it is a permanent result of design differences between Apple's old HFS+ filesystem and its new APFS filesystem (with one result that Retrospect Mac administrators have already discussed in this Macintosh 9+ thread). The first issue, however, sounds as if it's something for which the Retrospect Inc. engineers may eventually develop a workaround. Therefore DBA has chosen to put mentions of the second issue into the Wikipedia articles here and here, but to treat the first issue as a "temporary bug" that need not be mentioned in the articles.
  24. What the head of Retrospect Tech told me in this Agent Response turns out to have been officially announced the day before in courageous fashion—which I guessed is what might happen. This revised section of an existing Knowledge Base article now says: Enjoy the weekend.
  25. Nigel Smith, I didn't want to say before, because I thought it would be distracting. My Late 2016 MacBook Pro came with macOS 10.12 Sierra in December 2017; I bought it open-box precisely because I thought High Sierra was too new. A couple of months ago I upgraded it to High Sierra under the direction of an Apple Support person (he suggested it to fix a problem with several mini-apps in Dashboard); the upgrade file he told me to download did not re-format the SSD as APFS (presumably he had the "technical knowledge"). The backup I was originally trying to Restore, made on Saturday 30 March, was of the MBP's Macintosh HD formatted with HFS+. My original attempted Restore (stupidly) over the LAN—which stopped because of "insufficient permissions"—was made to the HFS+-formatted MBP running High Sierra. My external HDD, onto which I later Restored using Retrospect 15.6.1.105 running under Sierra on my Mac Pro "backup server", had probably previously contained a Restore of my old MBP—which IIRC was running OS X 10.10 Yosemite when its logic board died in December 2017. Here's something that may blow your mind. If I boot my MBP with the Option key held down, it goes directly to my ordinary High Sierra desktop. That may be because there is no other drive cabled to the MBP. I'll haul the external HDD from the bedroom into the study, cable it to my MBP with the USB-C-to-Firewire adapter string, and try that again; but not now, because I was up past 3 a.m. writing the posts above and copying the last reply as an Additional Note to my Support Case—so I'm going back to bed. Late this afternoon I'll wander over to Mike's Tech Shop and try to find out if they did anything tricky to my MBP's firmware on Tuesday 2 April; the Ethernet adapter they sold me in December 2017 is a Moshi one sold under Apple auspices.
×