Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Posts posted by DavidHertzberg

  1. amkassir (and others),

    The "promised 'detail document ...'" is no doubt referring to what Retrospect Tech Support replied to you on or before 11 October 2019.  Give the engineers time; this sounds like a tricky Apple-generated problem, and the last sentence of Tech Support's reply at least gives you a hint of what to do if you have to.  My guess—as an outsider—is that the time of at least some engineers is currently being occupied with figuring out how to convert the Retrospect Mac (because it's more Unix-related) Engine to run on a Drobo.

    P.S.: It's good to know, per your post directly above, that you can back up your Catalina installation with Retrospect 16.5.  amkassir, do you or did you have external drives cabled to your "backup server" machine—as sjmills does?  If so, why does he have problems that you don't?

    P.P.S.: It sounds—per your post directly below—as if the short-term solution, until the "detailed document" is released, is to restore using CCC and then overwrite files with previous versions—if needed—using Retrospect.


  2. All administrators upgrading to macOS 10.15 Catalina,

    This Knowledge Base article and this KB article were added on 5 November 2019.  The first of these appears to be a duplicate of this earlier KB article on macOS 10.14 Mojave, with a different URL and minor wording changes; in fact the second article links to that earlier article instead of the first article.

    As of 6 November 2019, there haven't been any updates to the Retrospect Mac downloads since 16 October 2019,  Therefore, if a fix to the Retrospect Mac Engine is required because of sjmills' problem, it is still in the future.

  3. 2 hours ago, sjmills said:

    The boot volume I'm backing up is on the same machine that Retrospect runs on, so it's not a client. But if I select that boot volume in the Sources, the Options tab is all disabled, then yes, All Volumes is selected.


    My "backup server" is booting macOS 10.12 Sierra, and it's running Retrospect Mac 16.1.  All other bootable  local drives would boot under macOS 10.12 or OS X 10.6.  When I click the Sources entry for one of my local drives, I can click the Options Tab, but everything on that dialog is grayed-out.  That makes sense for the checkboxes above "Volumes", since they have to do with options that apply to machines being backed up with a Retrospect Client application.  Greying-out also used to make sense for the "Volumes" section of the dialog, but with "improvements" in macOS it no longer does.  IMHO the dropdown should now default to Startup Volume if the local volume is bootable, with the boot volume automatically checkmarked.

    So  here's why and how to file a Support Case, in the event you don't already know.  Another example of great beta testing by Retrospect "Inc.".🙄


  4. sjmills,

    Assuming your problem is with a "client" machine, what is your "Volumes" dropdown setting on the Sources -> Options tab for that machine?  When re-Adding my MacBook Pro as a "client", I have the problem that that dropdown defaults to All Volumes—and for a couple of macOS releases that has included some garbage-named mirror volume.  I have to remember to change the dropdown to Startup Volume.  If I had an external  volume cabled to my MBP,  which I did during one re-Add, the default would include that also.

    OTOH this may be due to Retrospect not having been fixed to compensate for a change in macOS.  I submitted a Support Request for the problem described in the paragraph above, and Tech Support merely told me to change the dropdown.

  5. kidziti,

    Dashboard is a poorly-implemented feature of Retrospect Windows.  It was implemented in Retrospect Windows 8 because a Retrospect-Mac-like Console proved to be impossible (third paragraph of mbennett's post), but had glaring bugs that weren't supposedly fixed until 4 years later in Retrospect Windows 12.5.  See this 2017 Forums post by me, which quotes the applicable Release Notes but also quotes a reply from Retrospect Tech Support.  Also read the remainder of that thread.

    I suggest installing the _one-way_ Web-based Management Console, which is included for free in Retrospect Windows 16.5, as a substitute for the Dashboard if you're going to have Retrospect always running .  I also renew my suggestion of paying US$49 for the Add-On that enables the _two-way_ Web-based Management Console, especially if Sales tells you it has the capability of starting and stopping the Retrospect Engine on a particular "backup server".  Here's a Product Suggestions—Windows post with some more information and links.

    I have 7GB RAM (7 giga-bytes, not giga-bits; small 'b' = bits not a RAM measure) installed in my Retrospect Mac "backup server" machine.  That's sufficient to run the GUI-less Engine, which is ordinarily always running when the machine is booted, and also the non-Web-based GUI Console—which can be stopped and re-started separately. You may need more RAM than that, both because Windows 10 is Windows 10 (sneer, sneer 😀) and because the Web-based Management Console may use more RAM than the non-Web-based Retrospect Mac Console.  But extra RAM is comparatively cheap these days.

    P.S.: In the meantime, try this suggestion from mbennett.

  6. waves,

    I've got the same problem, both in Retrospect console > Sidebar Media Sets > Tab backups  and when I initiate a Restore -> "Restore selected files and folders" (which I cancel at that point, because it is just an experiment).

    Every Saturday morning I run a Recycle backup of one "client" machine plus two local disk drives and a Favorite Folder on a third local HDD.  Every other day of the week I run a No Media Action backup of the "client".  On one of my 3 weekly-rotated Media Sets (the "Media Set Red" I used last week) all backups are shown on the tab.  On the other 2 weekly-rotated Media Sets (the "Media Set White" I am using this week and the "Media Set Blue" I used two weeks ago), only the latest (Friday) No Media Action backup of the "client" is shown.  "Activities" shows all previous activities for all scripts.

    I'm running Retrospect Mac 16.1.  My "client" is running macOS 10.13.6 (High Sierra).  My "backup server" is running macOS 10.12.6 (Sierra).

    Here's why and how to submit a Support Case for a bug.  Note that for a couple of years now no Retrospect Inc. employee has regularly looked at this, or AFAIK any other, Forum.  So someone has to file a Support Case, and—waves—you're elected.  Basically all you have to do is copy the contents of your OP in this thread into the "Problem Description", plus put your appropriate information into the dialog boxes above that.  Thanks in advance for doing that.😃

    P.S.: What waves wrote two posts below this is what he said, not what I said.  It appears that waves was starting to quote me, and bollixed up the post.😒

  7. NoelC,

    If Retrospect "took a couple of months to begin to fail" on your home machine (you mention an "even bigger, more powerful office machine"), I assume that you don't have any legal constraints on data deletion on your home machine.  You haven't answered my question as to whether VSS-based backup can automatically comply with such constraints, but my added P. S.  implies it can't..  Assuming you don't have any legal constraints, and that after 2 months you developed the "data churn" that Nigel Smith mentioned in this post,  here's another simpler suggestion for the feature you could have requested:

    Add a checkbox under "Media" at the bottom of the Backup Set Options dialog, named something like "Override with Recycle to avoid Member overflow".  Again this type of "grooming" would have to be done at the end of the Matching phase of a Backup, since it would require pre-determining the amount of space that needs to be groomed out.  If—with the checkbox checked—that space is more than the remaining space on the mounted Backup Set disk Member, convert this Normal backup to a Recycle backup—which erases everything that is already stored on the mounted Backup Set disk Member and then replaces it with the full current contents of the Source.   That's rather extreme "grooming", but checking the checkbox means the administrator doesn't care—because not having to pay for an overflow Member overrides the constraints in the Grooming policy indicated above that checkbox in the dialog.

    I assumed that the paragraph immediately above—without the checkbox—was a description of what VSS-based backup does automatically, but the P.S. says otherwise.  Good luck, NoelC, and please don't come back complaining that you had to manually delete your previously-backed-up data from VSS.🤣

    P.S.: This Web page, which is really a commercial for AOMEI Backerupper, describes under "The Reasons" why VSS issues an "Insufficient storage available to create either the shadow copy storage file or other shadow copy data" message.  That's the after-two-months problem you've described for your home installation.  Under "The Solutions", the article describes manual steps to take to cope with this message; starting with the second sentence under item 1., it describes a manual process using the command:

    vssadmin delete shadows /for= [/oldest | /all | /shadow= ] [/quiet] 

    You want Retrospect to do the equivalent of automatically choosing the parameter for one or more executions of that command—excluding /shadow= because automating that'd be impossible.  I've described here an involved way it could iteratively choose  /oldest.    I've described in the second paragraph of this very post a way it could instead choose /all.  For either case, VSS obviously doesn't have any information about legal constraints.  Maybe the non-free Professional editions of AOMEI store such information and use it;  I'll let you explore that question starting with this Web page about upgrades.🤣

  8. kidziti,

    This Knowledge Base article used to have an explanation of what to do to get around Dashboard problems.  It was updated 16 May 2019, which may indicate an Engine update which got messed up in Retrospect Windows 16.5.  File a Support Case. Disclaimer: I'm a Retrospect Mac administrator.

    One suggestion would be to do what NoelC does, as quoted in this September 2019 post followed by my links to instructions on how to use Windows Task Scheduler, and bypass the Retrospect Windows Scheduler entirely.

    Another suggestion—not exclusive with the one in the preceding paragraph—would be to pay US$49 for the Management Console Add-On, for which you'll have to contact Retrospect Sales directly (it's not yet in the Configurator) and use Granular Remote Management so you can kiss the Dashboard goodbye.  I think there's already a way to open a particular Retrospect Engine from the Remote Console (I don't have major-league-pitcher-quality vision, so I can't read the screen images in the KB article); Werner Walter of Sales has used it; phone (888) 376-1078‬ X814.

  9. x509,

    I only once ran a program on an IBM 1130; it was IBM's Project Control System at an IBM service bureau in suburban Boston.  Your memory about the hardware is correct; the removable disk cartridge was an IBM 2315.   That cartridge mounted in an IBM 2310 disk drive, whose distinctive characteristic—to make it inexpensive—was that it used a slow voice-coil actuator instead of a faster rack-and-pinion one.  I remember standing around (there were several hundred activities in my client's project-scheduling data) and chuckling while the disk drive's access arm did buzzing seeks to the proper track.

    However you are incorrect in remembering Fortran II on the 1130; it had a Fortran IV compiler.  I never programmed for the 1130, but I wrote programs for a year using my service-bureau employer's IBM 7094 Fortran II (+) compiler.  A major problem was that Fortran II did not have logical operators and a logical IF statement—which were added in Fortran IVPerhaps the lack of these caused me to make a truly stupid coding error in enhancing my NASA PERT "C" summarization program (for which I independently re-invented depth-first search) used for RCA Burlington's Apollo LM electronics subsystems.  This led to the project manager for the Rendezvous Radar and Transponder losing faith in my program (although I found the error in 4 15-hour days), and doing his bi-weekly project network summarization for two years by hand.  He did that well; LM Eagle rendezvoused with Command Module Columbia on 21 July 1969.

    P.S.: It's been 54 years, and I never preserved a listing of my NASA PERT "C" summarization program because I couldn't follow it any more (see the last sentence in this paragraph).  However here follows what I now recall as a more-precise explanation of the coding error I made: Fortran II, even with the enhanced—denoted by "(+)" above—compiler my employer developed with the Smithsonian Astrophysical Observatory, which made the language barely suitable for character-comparison business applications (with an optional 'B' in card column 1 that converted the arithmetic IF on page 34 of this manual

       IF (a) x1,x2,x3 
       Where: a is any arithmetic expression except complex. 
    	      x1,x2,x3 are executable statement numbers.
         The arithmetic IF statement causes control to be transferred to the statement numbered x1,x2,or x3 
       when the value of the arithmetic expression (a) is less-than, equal to, or greater than zero, respectively. 

    into a kludgey logical IF—by making (a) into a Boolean expression with AND and EXCLUSIVE OR operators and making the values of (a) for the 3 statement numbers be zero for x2 and non-zero for x1 and x3—plus adding a DATA statement per page 69 of the manual), but had no capability for nested IFs—which weren't added until Fortran 77.   I had a pair of tests that were—I now recall—conceptually a nested IF, and I bollixed up the statement numbers.  I spent four 15-hour days searching for a compiler Boolean bug (because I'd found one soon after I started using the compiler), before realizing while brushing my teeth on Saturday night that the bug was in my code.  Like most programmers then and now, I was dismal at following control-transfer-via-branching logic.

  10. 21 hours ago, Nigel Smith said:

    ... may I offer another?

    Move *all* your systems onto the "pro-active" script!

    Schedule it to run during your overnight window. Set it to back up sources every 22 hours or so (roughly 24 hrs - time taken to back up all systems) so it only backs up each once. When it kicks off it will start polling the network for client availability, starting with the one least-recently backed up. Each system in turn will be backed up if present, or skipped for a while (I think the default is 30 minutes) then checked for again -- meanwhile the script continues with the other clients.

    ... or if you need to hit a certain time (eg quiescing databases first), but it's great to make sure that "irregular" clients get backed up if available and that those "most in need" get priority.

    AFAIK, with two backup sets listed *and available* the above would alternate between them nightly, but things may have changed in more recent RS versions.

    kidziti and Nigel Smith,

    I considered that alternative , but felt that having separate Proactive and Backup scripts would be simpler—even with having to coordinate the alternation of Backup Sets.

    However, regarding quiescing databases, note that Retrospect Windows 12 added Script Hooks.  These can be used in conjunction with: Lotus Domino, MongoDB, PostgresSQL, MS Exchange, and MS Outlook.  Also note that the Open File Backup Add-On for backing up Windows applications, which is free for the Desktop Edition, "is designed to back up line of business servers while they are up and running" and "is looking for a 'disk inactivity threshold'".

    AFAIK things have not changed in more recent Retrospect versions as far as alternation between Backup Sets is concerned.   However, according to this Knowledge Base article,  what Nigel Smith described as "polling the network for client availability, starting with the one least-recently backed up [my emphasis]" has been replaced in Retrospect Windows 12 with a much more sophisticated "AI" (misnomer; it's decision-tree+linear-regression) algorithm.

  11. NoelC,

    Here is why and how to submit a Support Case for a new feature.  In writing that Support Case for "make reliable backups in such a way as to give the longest possible backup horizon for any given available backup space" , here are some factors you should consider:

    • This type of grooming would have to be done at the end of the Matching phase of a Backup, since it would require pre-determining the amount of space that needs to be groomed out.  Presently Retrospect does grooming during during the Backing Up phase, whenever space has already run out on the Backup Set disk member being used.
    • This type of grooming would have to also comply with the other factors in the Grooming Policy for the Backup Set.  For many installations these are determined by legal requirements—non-existent 40 years ago, which is why Nigel Smith said above "you (and/or any Compliance Officer you may answer to!) can live with."  Does VSS "grooming" now comply with such legal requirements; does DEC (double-merged into HP) "grooming" do so?
    • The factor directly above would mean that the Catalog File would have to contain a list of each backed-up version of each file (which it may already do) plus the size of that version on disk (which it probably now doesn't).  The size would be needed to determine how much space would be saved by grooming out that version, while ensuring  that the Grooming Policy would not be violated by so doing.  An alternative would be to iteratively try a Groom-out of one version of each file, remaining in compliance with the Grooming Policy, while calculating if enough space had now been saved to accommodate the file versions that would be added to the member during the  Backing Up phase; no doubt you can see iteration would be kludgy!  With either approach, the Backing Up phase would have to be skipped entirely if Matching-phase grooming fails; would administrators prefer that?
    • Retrospect "Inc." would surely, because of the development cost considering the above factors, charge for an Add-On license for the feature.  For most installations that would be potential customers for this feature, the cost of the Add-On license would be more than the cost of an additional overflow disk—which for some reason you are dead set against purchasing.

  12. kidziti,

    What is this "16.x"?  In this post you said you had installed " (Windows Desktop version)".  Here's a thread whose OP had what sounds like a similar problem with that release, and was guided to a fix.  Someone else had a problem, and solved it by downgrading to 16.1—but I can't tell you where to download that.

    You seem to be having several problems within the last day or so.   Here's why and how to file a Support Request for a bug.  If you upgraded within 45 days (I think), you are entitled to free personalized help from Retrospect Tech Support.


  13. On 10/31/2019 at 10:44 AM, kidziti said:

    I think David hit the precise answer I was looking for (thank you, DavidHertzberg!) - if there is a way for the software to be "smarter" about the variable that some backup clients such as notebook PCs may or may not follow a schedule of being connected to the network. Time to hit the learning curve again because my two alternate-night-backup external drives are always "mounted" or connected to the computer. Surely there must be a way to add the notebook to the script without ensuring that one of them must be unmounted (if I understand your explanation correctly - which I suspect I do not.) My philosophy on backups is that if any user intervention is required, it will ultimately fail. I may even buy a third drive and remember occasionally to swap it out with one in a safety deposit box, but some day I will forget to do it or be on a trip or put it off for whatever unforeseen reason or lack of backup enthusiasm I may have in the future.


    The "Proactive Backup Script" column in the table at the bottom of page 240 in the Retrospect Windows 16 User's Guide says, in the "Destination Backup Sets" row, "Copies to the most ideal available Backup Set in the destinations list. Automatic media rotation among multiple available Backup Sets."  The only Forums mention of that sentence I can find is this post by me, and I didn't know any more in January 2017 about Proactive than I do now. 

    Since AFAICT from pages 250-252 of the UG you can't specify days of the week or alternate weeks for a Proactive script's schedule, this feature may result in more perfect alternation between destination Backup Sets than your schedule(s) of Backup scripts.  If so, you may have to compensate by disconnecting the Backup Set drive you don't want to use on the next Proactive run on Friday/Saturday nights or Monday mornings—IOW the last night or first morning  you are in the office during a particular workweek.  That's assuming you have multiple schedules for each Backup script, so that the Backup script backs up to Backup Set A on Mondays of some weeks and to Backup Set B on Mondays of other weeks.  In that case,  a better idea would be to put all your "clients"—including the ones that never leave the LAN—on the Proactive script and ditch the nightly Backup script.

    If you buy a third drive for offsite storage, you should use it as a destination for periodic Transfer Backup Sets or Transfer Snapshots scripts—where the source would be the most-recently-used destination Backup Set for your nightly scripts.  See pages 209-220 of the UG.

    P.S.: Backing up to both Backup Sets per your post directly below, you'd have to have two Proactive scripts, each one specifying one of your two Backup Sets.  Read that same column-row entry on page 240 of the UG; each Proactive script would back up a "client" based on that Backup Set's Catalog.  This 2006 thread confirms you can't alternate weeks, but—despite what I said in the second paragraph above—pages 251- 252 of the UG imply you may be able to effectively suppress execution of a Proactive script on a particular day of the week by Customizing with Stop time <= Start time on that particular day.  If you want to use Backup Set A on Monday of week N but use Backup Set B on Monday of Week N+1 (5 or 7 workdays per week instead of 6 workdays)—and the built-in rotation doesn't fit your requirements, you'd then need twin Proactive scripts with "invert-of-twin" Start-Stop for each workday in the week.

  14. The Retrospect article will have to remain in its current feature-less state, because I've been blocked indefinitely from Wikipedia editing.😖  I say "I" because—as I'm sure most of you have guessed—"DovidBenAvraham" is merely my Wikipedia "handle" . I pretended DBA was a separate person to have a fig-leaf of deniability in the face of the possible wrath of the head of Retrospect Technical Support (my 2016-2017 version of the article's "Documentation" section, deleted because comparing different versions of the Retrospect Mac User's Guide is considered Original Research—a Wikipedia no-no, was implicitly critical of Retrospect Inc.).

    Eliminating all first-party references, which I did in this 08:56, 27 October 2019 revision, was not enough for Guy—as I knew it would be.  I tried to get him to accept this 04:41, 29 October 2019 revision, which only mentioned the unique-to-Retrospect (it was patented by Dantz in 1996) Proactive feature, but he reverted that revision—resulting in what you see now, giving as his Edit Summary "Reverted good faith edits by DovidBenAvraham (talk): Promotional edits, primary sourceing [sic], usual problems".  I chose to go down fighting, created an Administrative Noticeboard Incident, and was "blocked indefinitely from editing for disruptive editing".

    Guy denounced in the ANI discussion "claims of novelty sourced to a patent (a canonical primary source)", but the real issue is "promotional edits".  A coterie of Wikipedia administrators is determined to clamp down on articles written to promote particular companies, and is going so far as to eliminate mentions of features of application software products unless these features are "unique"—without giving any indication of how to prove "uniqueness" with a reference.😲  Somehow articles written about really-expensive enterprise client-server backup applications, such as Backup Exec and NetBackup and EMC Networker and IBM Tivoli Storage Manager, are exempt under some kind of "grandfather clause".🤣  I think there's no hope of prevailing against this coterie, so I won't try to get the block lifted.


  15. kidziti,

    Disclaimer: I administrate a Macintosh home LAN, and the laptop "client" in it never leaves my desk.  My nightly incremental No Media Action (the Retrospect Windows term would be Normal backup action) script is scheduled for 3 a.m., but it actually runs at or after 3 a.m. whenever I boot the laptop "client" and then the "backup server" machine in that order.  My scripts are all Backup scripts; I've never used Proactive scripts.

    Nevertheless IMHO what you need is a Proactive script, as described on pages 239-254 of the Retrospect Windows 16 User's Guide (that information hasn't changed for years, but there's a more-recent Knowledge Base article that you probably don't need to read if you're only backing up one dis-connectable "client").  You can schedule it (pages 250-253) before or after your nightly Backup script, specifying all the Backup Set destinations your Backup script ever uses.  "Rotate Among Backup Sets" on page 242 says "Rotate through the sets by inserting different media in the backup device each day. ProactiveBackup uses whatever media you inserted"; so you'd just have to make sure the media for whatever Backup Sets your nightly Backup script isn't using that night aren't mounted on your "backup server".  (The alternative would be to manually change the Proactive script's specified single Backup Set whenever the schedule for your Backup script switches to a different Backup Set, but IMHO that would be a bigger nuisance than un-cabling/re-cabling drives—which I do every Friday preparing for Saturday's Recycle Backup). As it says on page 240, "Proactive Backup uses only the Normal backup action because New Member, Recycle, and New Backup Set backups are inappropriate for use with Proactive Backup scripts."

    If the Backup script is still running when the Proactive script starts, many of us administrators have learned—some the hard way— that Retrospect has a (undocumented, I think) feature that will delay running the second script until the first script using the same Backup Set destination has finished.  I'm not sure what will happen if the Proactive script is still running when the Backup script is scheduled, so I suggest you put a Stop time (page 252) on the Proactive script if you schedule it before the Backup script. 

    HTH; over to you, Lennart_T.


  16. Currently I've got "Prevent computer from sleeping automatically when the display is off" and "Enable Power Nap while plugged into a power adapter" checked. "Put hard disks to sleep when possible" and "Wake for Wi-Fi network access" are unchecked. Those aren't precisely the settings as of a week ago Sunday night (I was out of town Saturday); I since changed them per Nigel Smith's suggestion, and can't remember what they were before.

    Retrospect Tech Support suggested that I change network timeout from 300 seconds, which is what it has been every time I've gotten a -559 error, to 9000 seconds.  I did so,

    Saturday morning, since I was awake working on my MacBook Pro until past 3 a.m., I rebooted my  MBP before booting my Mac Pro "backup server", in order to see if the Recycle backup would run for precisely 2 hours before getting a -559 error. I then went back to bed. The MBP backup ran fine—including a Compare phase—for 3:45 hours; the "backup server" kept running the script to back up its local disks.

  17. Nigel Smith and trevorjharris,

    Nigel's point is well-taken in general, and Trevor would-be well-advised to back up his Catalogs and settings periodically to a local drive—as I do using a Favorite Folder (the Retrospect Mac name for a Subvolume). 

    However recovering an up-to-date Catalog that has been damaged during a long backup, which is what Trevor says in his OP he is worried about—will require a Rebuild.  Nigel is correct that doing so from a long backup to a cloud Backup Set would be very expensive, because of the provider charge for download reads.  The answer to that is to only do short backups to a cloud Backup Set, which can be repeated after restoring the saved previous Catalog from a local drive.  That IMHO is why Retrospect "Inc." recommends doing Transfer Backups from a local Backup Set to a cloud Backup Set.

    Trevor can ignore the preceding paragraph, since his OP says his long backups are to a USB3 disk drive.  So can I, since I rotate my USB3 drives to a bank safety deposit box instead of using cloud backup.

  18. Nigel Smith,

    The change in macOS is described in the first and third paragraphs of this OP in a Mac 9+ thread.  It's not just on my MacBook Pro; I took a look at macOS 10.14 Mojave running on a machine at my local Mac repair establishment, and the "Computer sleep" slider is missing on that Mac as well.

    You're correct about the OP's killing the "backup server" halfway through the process.  I missed the idea that the OP is running Retrospect Desktop as if it is Retrospect Solo, with only one Windows machine, whereas I was thinking of my own use of Retrospect Desktop—with a "client" machine that is separate from the "backup server" machine.

    trevorjharris and Nigel Smith,

    IME if the "backup server" does die halfway through the backup process, you'd be able to Rebuild the Catalog from what was written on the member(s) of the Backup Set.  Retrospect was designed to work that way, and many administrators—including me on Retrospect Mac—have Rebuilt damaged Catalogs.


  19. 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.

  20. 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.