Jump to content

DavidHertzberg

Members
  • Content count

    1,038
  • Joined

  • Last visited

  • Days Won

    38

Posts posted by DavidHertzberg


  1. As of the day before yesterday, error -530 is back on my MacBook Pro.  Tried the workaround yesterday.  As of this morning, the workaround didn't work.  :(

     

    For my failing scheduled "Sun.-Fri. Backup" script, I just run it again from the Console.  My scheduled "Sat. Backup" script simply skips the MBP and goes on to backup the next client, so from the Console I submit a "Sun.-Fri. Backup" script to run after it—which backs up the MBP from scratch because  the "Sat. Backup" run has done a Recycle Media Set.  Therefore no big deal, just a minute per day of inelegance.   :rolleyes:


  2. Thank you for replying, Robin (but it took a phonecall to Retrospect Inc. Sales to get you to do so).  :)

     

    My error was in not looking far down enough in the list of Tutorials to see the Cloud Backup ones under Retrospect for Mac.   However the Tutorial you link to is not the correct one for fully answering my question.  I see now that the Retrospect Tutorial

    briefly explains how to "change the set's location in Retrospect to the cloud location" after "seeding".  There is another Tutorial
    that briefly recapitulates that explanation, but goes on to explain how to restore files from a Cloud Media Set that has been copied to a hard drive by the cloud media provider—and the drive then shipped to the user (similar to CP Home's "restore to door" service) to be installed as a local drive.  The key concept in both Tutorials is that the top dropdown in an apparently-new Member Type dialog invoked for a Cloud Media Set in the first Tutorial—now also invoked by Media Sets->mediaset->Members->edit-pencil in the second Tutorial—has been enhanced in Version 13 to allow switching between defining a true Cloud Media Set member and a local Media Set member for the same Cloud Media Set.  I think this is brilliant.  :wub:

     

    However, I have one rather large quibble.  In the words of Dr. Strangelove, "Why didn't you tell anyone?"!  Specifically, Retrospect Inc. could IMHO have added that Member Type dialog key concept to "Cloud Backup" in Chapter 1: "What's New" in the Version 13 Mac User's Guide in about three sentences.  If they didn't want to bother to do that, they could have added a sentence "Written words cannot explain the beauty of how we do this!", followed by a link to the relevant Tutorials. ;)

     

    It's bad enough when a competing cloud backup product (its initials are CP) does its documentation as a set of web pages with links only to the next step down the garden path, so that a potential user has to use Google etc. as the table of contents for the documentation.  It's even worse when Retrospect Inc. starts to do its documentation only in videos—without bothering to provide links from the User's Guide to the videos.  Some of us older potential users can read text faster than we can watch videos. :rolleyes:

     

     

    P.S.: Revised next-to-last sentence in second paragraph, to clarify the key concept.

     

    P.P.S.: Further revised next-to-last sentence in second paragraph, to clarify the key concept.


  3. One question I have relating to cloud backup in Ver. 13 concerns "seeding" followed by incremental backups.

     

    "Seeding for Cloud Storage" in Chapter 1 of the new Mac User's Guide states: "Seeding allows customers to back up their data to a local hard drive and then send that hard drive to the cloud storage provider. The cloud storage provider then imports that data into the customer's storage location. This process enables customers to send a large amount of data to the provider faster than it would take to upload it. After the data is imported, the customer can change the set's location in Retrospect to the cloud location and begin incremental backups."

     

    If the user backs up his/her data to a local hard drive, that would presumably be done after creating a Disk type Media Set for the Recycle Media Set backup—complete with catalog in the usual default location.  After the data is imported into the customer's storage location in the cloud, can the user now "change the set's location in Retrospect to the cloud location" by changing the type of that same Media Set from Disk to Cloud—and then plug in all the necessary cloud access information into the change dialog?

     

    If that is not possible, can the user create a new Cloud type Media Set, and then copy the catalog of the Disk type Media Set as the catalog of the Cloud type Media Set?  I am not familiar with many of the more esoteric capabilities of Retrospect; how would the user do this?  By following the "Adding a Media Set’s Catalog" procedure in Chapter 8 of the Mac User's Guide, but changing the Media Set name to that of the Cloud type Media Set?

     

    If that too is not possible, would the user have to Recatalog the Cloud type Media Set after it has been imported?  That sounds as if it would require the Retrospect server to effectively download some subset of the information for every file stored in the Cloud type Media Set.

     

    I now see that there is a Tutorial video entitled "Backup Set transfer to the Cloud for Windows".  However I have searched the Mac User's Guide, and there doesn't seem to be any such facility for Retrospect for Macintosh.  Version 13.5, perhaps?


  4. Around 15 February I started getting -530 errors for my MacBook Pro when my "Sun.-Fri. Backup" incremental script made its daily scheduled runs.  However, when I then ran the same script manually from the Console, it ran fine—as it had been doing via schedule for 7 months prior to 15 February.  My "Sat. Backup" Recycle Media Set script got the same -530 error for the MBP on its weekly scheduled run, but backed up all drives on my other two Macs.  When I then manually ran my "Sat. Backup  Incremental" script to compensate, the MBP backed up all files as if it were a Recycle Media Set run—which it was for the MBP on that particular Media Set.

     

    After nearly two weeks of this behavior, I realized on 25 February that the -530 errors had started just after just after I updated the Retrospect Client on my MBP from 12.0 to 12.5 before running the tests described in this post.  The morning of 26 February I realized that I might be able to fix the problem by reverting the MBP's Retrospect Client to the 12.0 version, and that I would probably have to do so by restoring it from a Media Set—but that I was scheduled to Recycle the only Media Set that still had the 12.0 Client the next morning when the "Sat. Backup" script ran.  Since I didn't know where on my MBP disk I could find the Retrospect Client files (the app is not in Applications to prevent a client user's deleting it), I phoned Retrospect Inc. Tech Support to ask.

     

    As soon as the words "-530 error" were out of my mouth, A. told me he could give me a workaround for it.  He told me to do the following: (1) Remove the MBP from Sources on the Retrospect Console.  (2) Export Client Installer from the Retrospect->Preferences->Console onto a flash drive, and then sneaker-net that flash drive over to the MBP.  (3) Run "Uninstall OS X Client.app" (no quotes) from the flash drive on the MBP.  (4) Make sure the file "root-drive-name/Library/Preferences/retroclient.state" (no quotes around file name, root-drive-name is usually "Macintosh HD" with no quotes) is no longer there; if it is still there, delete it.  (5) Run "Retrospect Client Installer.pkg" (no quotes) from the flash drive on the MBP, and alter the MBP's System Preferences->Retrospect Client preferences as required. (6) Add the MBP to Sources on the Retrospect Console, and then alter that client's Source Options as required.  (7) Re-checkmark the MBP as a Source in all Scripts where it should be used, and then (although A. didn't say this—either because he knows I know to do it or because he doesn't accept derek500's report in this post) drag the MBP client into the proper sequence position in the Summary of any of those Scripts that backup more than just the MBP.

     

    A. also said that Retrospect Inc. engineers are investigating the underlying cause of such -530 errors, but that they haven't found it yet.

     

    I did what A. said, and the workaround eliminated the -530 errors (so long as the MBP is awake when a script backing it up runs).  YMMV (for non-Americans, that's shorthand for "Your mileage may vary"—a caution given at the end of auto mileage claims in TV ads for many years in the U.S.).  Not only do I now have a working 12.5 Retrospect Client on my MBP, but Instant Scan has now started working on the MBP for the first time.  Step (2) deleted the file "Macintosh HD/Library/Preferences/retroclient.state", and step (4) re-created it.

     

    Here followeth a short tale of my stupidity as a likely explanation of why I started getting -530 errors on scheduled scripts starting around 15 February; feel free to skip it.  On 15 February, when I decided to update the Retrospect Client on my MBP from 12.0 to 12.5, I discovered that Retrospect->Preferences—>Console wouldn't Export Client Installer directly to my MBP over my LAN.  Rather than using a flash drive and sneaker-net, I downloaded Retrospect_Client_12_5_0_111.zip from download.retrospect.com.  IIRC—thinking I was doing an update—I then ran Mac_Client_Update_12_5_0_111.rcu from the downloaded Mac Client Updater folder, rather than "Uninstall OS X Client.app" followed by "Retrospect Client Installer.pkg" from the downloaded Mac Client Installer folder.  The result was that I didn't delete the file "Macintosh HD/Library/Preferences/retroclient.state", creating some kind of mismatch that seems to cause the -530 problem.

     

    Compounding this stupidity was my initially thinking that the -530 problem was being caused by some startup LAN connectivity problem between my Mac Pro "Retrospect server" and the MBP (I normally do not boot the Mac Pro until it is past time to run a script, with at least the MBP awake).  I therefore added Firefox to the Mac Pro's Startup Items as a connectivity check, and gradually replaced each non-coax piece of LAN cable between the Mac Pro and the MBP.  It was only when none of these measures resolved the problem that I started thinking about the MBP's Retrospect Client.

     

    In addition, before starting to think about the MBP's Retrospect Client, it occurred to me that maybe closing port 497 on my router had belatedly started to cause a problem.  So, despite my having posted this, I tried re-opening port 497 again.  That didn't solve the -530 problem, and I have—since implementing A.'s workaround—closed port 497 without getting any -530 error.  Note that, if you have an internal firewall—such as on a particular computer—or an internal router on your LAN, you do need to have port 497 open for TCP and UDP.

     

    P.S.: Very belatedly noticed that I had two step (3)s in the third paragraph; renumbered the steps.


  5. Motivated by a weird hang on a "Sat. Backup" Recycle Media Set script run that I eventually aborted early Saturday morning, yesterday I tried running my experimental "Sat. Backup Incremental" script with both my client machines set to Sleep in the Apple menu.  (I first updated the Retrospect Client on my MacBook Pro from the 12.0 version to the 12.5.0.111 version.   The Client on my G4 Digital Audio tower—my other client machine—is the legacy Mac PowerPC 6.3.029 version, because it's running under OS X 10.3—don't ask.)  The script run skipped backing up both client machines because of -535 errors, with no hangs.  In the Retrospect 12.5 Console, both Clients have the Wake-on-LAN option checkmarked.  In System Preferences->Energy Saver: the MBP has Wake for network access checkmarked; the G4 has the Wake for Ethernet administrator access option checkmarked.

     

    The last post in this thread in the Mac Retrospect 8 forum says "I can't confirm this myself but I have read in other threads that Retrospect doesn't support Wake on Lan despite it having a check-box indicating it is supported. One other user claimed this is a programming mistake and that this check box doesn't do anything and hasn't for many releases. Apparently many have asked for a true WOL feature to be implemented. "

     

    Page 43 of the Mac User's Guide says "Check the box next to Enable Wake-on-LAN if you want to make sure that Retrospect wakes up a sleeping client computer for Proactive Backup activities."  Page 346 of the Windows User's Guide says "Retrospect cannot wake a sleeping Mac OS client computer to back it up. Make sure that each Mac OS client’s sleep preference is set to never put the computer to sleep."

     

    Does the Client Wake-on-LAN option not work at all, or does it work only for Proactive Backup activities?  Either way, Retrospect Inc. should either (1) implement Wake-on-LAN for scripted activities, (2) modify the Client dialog in the Console to indicate that the option is only for Proactive Backup activities, or (3) eliminate the option.

     

    P.S.: Re-inserted inter-paragraph spaces that were in non-Bug-Reports version but got dropped in copy to Bug Reports.


  6. Sorry, I meant to post this in Bug Reports—and eventually did so.  Moderators please feel free to delete this post here.

     

    Motivated by a weird hang on a "Sat. Backup" Recycle Media Set script run that I eventually aborted early Saturday morning, yesterday I tried running my experimental "Sat. Backup Incremental" script with both my client machines set to Sleep in the Apple menu.  (I first updated the Retrospect Client on my MacBook Pro from the 12.0 version to the 12.5.0.111 version.   The Client on my G4 Digital Audio tower—my other client machine—is the legacy Mac PowerPC 6.3.029 version, because it's running under OS X 10.3—don't ask.)  The script run skipped backing up both client machines  because of -535 errors, with no hangs.  In the Retrospect 12.5 Console, both Clients have the Wake-on-LAN option checkmarked.  In System Preferences->Energy Saver: the MBP has Wake for network access checkmarked; the G4 has the Wake for Ethernet administrator access option checkmarked.

     

    The last post in this thread  in the Mac Retrospect 8 forum says "I can't confirm this myself but I have read in other threads that Retrospect doesn't support Wake on Lan despite it having a check-box indicating it is supported. One other user claimed this is a programming mistake and that this check box doesn't do anything and hasn't for many releases. Apparently many have asked for a true WOL feature to be implemented. "

     

    Page 43 of the Mac User's Guide says "Check the box next to Enable Wake-on-LAN if you want to make sure that Retrospect wakes up a sleeping client computer for Proactive Backup activities."  Page 346 of the Windows User's Guide says "Retrospect cannot wake a sleeping Mac OS client computer to back it up. Make sure that each Mac OS client’s sleep preference is set to never put the computer to sleep."

     

    Does the Client Wake-on-LAN option not work at all, or does it work only for Proactive Backup activities?  Either way, Retrospect Inc. should either (1) implement Wake-on-LAN for scripted activities, (2) modify the Client dialog in the Console to indicate that the option is only for Proactive Backup activities, or (3) eliminate the option.


  7. Monday morning I phoned A. of Retrospect tech support about another matter.  I then asked whether, using my $119 Desktop Edition of Retrospect, I could run a Retrospect Engine on multiple computers or run the Console app on a different computer than my Engine. I told him I was simply curious, and have no intention of actually trying to do either of those things. A. said—after he finally understood my question— that neither is allowed with the Desktop Edition, and that I would need a $659 Single Server 20 Workstation Clients Edition to do so. I therefore conclude that the Retrospect Mac 12.5 Desktop Edition has been crippled by licensing to externally look like Retrospect up through Mac 6—in which what later became the Console was merely the same-process UI for what later became the Engine. I'm sure Retrospect Inc. does so in order to be able to sell cheaply to little dogs like me without underpricing its products sold to the big dogs.

     

    Could I in fact do what A. says I can't?  B)


  8. Monday morning I phoned Retrospect Inc. tech support and spoke to A.. I told him I had run several backup scripts since closing port 497 on my router—including a 7.5-hour "Sat. Backup" Recycle Media Set backup on Saturday, and asked why he had told me last July that it was necessary to open port 497 on an Internet router connected to a LAN with no internal firewalls. It took A. nearly five minutes to concede that it is not necessary to open port 497 in this case, but he didn't explain why he continues to tell other users to open the port. 

    I consider A. a manual component of the Retrospect 12 system. :D   Retrospect Inc. should "fix" his "bug" so he doesn't give out incorrect information to users.

    • Like 1

  9. Terminology notes on posts I have made in this topic:

     

    Where I have written "server" I meant "Retrospect server" in Retrospect terms.  Note that "backup server" is not defined in the Glossary of the Mac User's Guide for Retrospect 12, although it is extensively used throughout that document—frequently abbreviated as "server"—presumably as a synonym for "Retrospect Server".  I do not run a Macintosh OS Server machine.

     

    Where I have written "local" I meant whatever "Local" means in the Retrospect console—specifically a drive that cannot be Removed in the Sources item.  Note that "local" is not defined in the Glossary of the Mac User's Guide for Retrospect 12, although it is extensively used throughout that document.  Since the "Overview of the Retrospect Console" section in that document says each set of items is for a particular "Retrospect server", I deduce that "Local" means a drive directly mounted on the particular "Retrospect server" to which the Sources item applies.  I run both the Console and and a single Retrospect server on the same Macintosh.


  10. Hi Tom,

     

    You made your second post in this thread, specifying your client Energy Saver preferences, after I had drafted—but not yet posted—the first version of my post above.  I then considered deleting my first paragraph in that post, but decided instead to add the sentence about wake on LAN—since what I said bears repeating even if it doesn't apply in your case.

     

    However I failed to spot the clue in Problem 1 in your OP.  IMHO your mistake was in changing the name of your machine in Retrospect->Sources->Rename, instead of changing it in System Preferences->Sharing->Computer Name.  Although I did not mention it in this thread, I had tried changing the machine name in Retrospect and found it to be ineffective.  Assuming the machine is a client, Remove the machine as a Source first, make the name change in System Preferences (if that doesn't change the Client Name in the Status tab of your machine's Retrospect Client, you may have to stop and start the client), then Add it back as a Source and re-checkmark it in your script.

     

    As currently programmed, Retrospect->Sources->Rename seems to be a snare and a delusion.  At best it is good for neatening the machine name for clarity purposes in the Retrospect Console.  It may have been more effective in Retrospect 5, which dealt with machines pre-OS X.

     

    P.S.: Added parenthesized note about stopping and starting client to last sentence of second paragraph.


  11. It sounds to me as if Lennart is right. The inability of Retrospect 8 and above (IIRC Retrospect 6 didn't have this limitation—maybe for OS 9 clients) to backup sleeping clients is well-known. It is also well-known that wake for network access is not effective for Retrospect backups. My own experiments on my little LAN have shown these facts to be true.

     

    However, also consider my posts here and here and here in a thread on a very similar topic.


  12. I have now noticed a possibly-somewhat-related problem. Last night I tried signing in to this forum from my Mac Pro, using Firefox 41.0.2 under OS X 10.10.5. and I keep getting "Username or password incorrect". I get the same error message when I try to sign in from the Mac Pro using Safari 9.0.2.

     

    Last night I even changed my password for the Retrospect forums from my MacBook Pro, just to make sure that it wasn't a question of the Mac Pro using an old password. I can still sign on from the MacBook Pro with the new password using either Firefox 42.0 or Safari 9.0.2—simultaneously. But the new password doesn't help when trying to sign in from the Mac Pro.

     

    Here's a wild shot: Is membership on the Retrospect forums tied to a particular MAC address? Both my MacBook Pro and my Mac Pro have hard-coded 192.168.1 local URLs tied to their MAC addresses.

     

    P.S.: Problem persists even after Firefox on Mac Pro updated to 43.0.3.

     

    P.P.S.: In case it's not obvious, the reason I tried last night to sign into the Retrospect forums from my Mac Pro was to test whether the "styling buttons" problem reported in the OP for this thread is peculiar to the copy of Firefox installed on this MacBook Pro. I normally use the Mac Pro only as a Retrospect backup server.


  13. Thinking about this further, in the light of the P.S. of my last post, I have realized that we can replace the concept of the Source's hidden Machine Name with the concept of the Source's Machine Name at the time the Source is checkmarked in a particular script. In other words, if you change a Source's Computer Name in its System Preferences->Sharing, the next time Retrospect is started it will not "notice" and automatically change—in all existing scripts—the sequence in which that Source is backed up—even though it will change the Machine name displayed in reports. However Retrospect will correctly sequence—according to its current Computer Name—a newly-checkmarked Source in a script. This explains why, when I checkmarked "Macintosh HD New" in the "Sat. Backup" script as described in my last post's P.S., it showed up as the last Source of the Details panel in the Summary tab without my having to drag it.

     

    This does not significantly change the "moral of this story" in my original post in this thread. Before writing any scripts you should decide on what default order you want your machines to be backed up by all scripts, and immediately change the Computer Name in the Sharing preferences for every machine--including the Retrospect server(s)--so that the Computer Names sort in the desired order of machine backup. However, since you will almost certainly start writing scripts as soon as you install Retrospect on a server(s), you would be well-advised to change Computer Names before installing Retrospect (so I'm not changing the thread title).

     

    Yes, as Derek500 has pointed out, you can manually change the sequence of Source backup in a particular script by dragging in the Details panel of its Summary tab. But it's going to be a nuisance to do this after you have already written a number of scripts, so if you have a default sequence you might as well establish it ASAP. Besides, we'll all be older and grayer before Retrospect Inc. gets around to documenting the Details-panel-of-the-Summary-tab-dragging trick. ;)


  14. About two weeks ago I created a new topic here about the use of word styling and “smilies” on the Retrospect Forums. By experimentation I had found out that I could get italic into posts here by using the before-and-after "tags" (not to be confused with Forums tags) that work in the forums on another website. However those forums have buttons beside and above the posting pane that put in the styling "tags" before and after a selected word or phrase, and that put in a specified "smilie" wherever the cursor is.

     

    On a whim (it was a Sunday evening) I drafted a post on the other forums by clicking all of its "smilie" buttons, copied and pasted that draft into a post on this forum, and deleted the draft on the other forum. On this forum a number of the "smilies" in the post generated the intended graphic. I then expanded the post with a sober plea for buttons to generate italic, bold, and links with URL hidden behind an underlined word/phrase. The next day I got an e-mail from Robin, saying that somebody had posted spam using my ID and that I should change my Forums password. Maybe he was motivated by the fact that my Topic Title was "Whee! ...". ;) Anyway, my "Whee! ..." topic disappeared from this forum. :(

     

    It turns out I have a web browser problem. I normally use Firefox (now version 42.0) on a Mac under OS X 10.10.5. When I post to the Retrospect Forums from it, clicking the More Reply Options button does not give me a toolbar with styling buttons above the text-entry pane.

     

    Three days ago I tried posting from Safari, and there clicking the More Reply Options button does give me a toolbar with styling buttons above the text-entry pane. One thing that may be significant is that I currently have Adobe Flash selectively blocked on Firefox.

     

    P.S.: When I Edit this post using Safari (it was originally composed on Firefox), I immediately get the toolbar with styling buttons etc. above the text-entry pane. When I click the Use Full Editor button—still in Safari, the toolbar goes away.


  15.  

    For those times when the graphic display is incorrect, have you tried quitting and relaunching the console to see if the display changes? I'm wondering whether the errors you see are a failure of the console to update properly with the latest data from the engine, which is a problem we frequently observe.

    I have frequently tried quitting and relaunching the entire Retrospect 12.5 application. In fact I normally use my Mac Pro only as a Retrospect server once a day, so I shut down the entire Mac Pro as soon as the daily backup is finished and reboot it the next day. I have not observed the display change in a good way from a new execution of Retrospect within the same week. However in my earlier post in the thread covering 22 November, I did observe the display to change in a further worse way.

     

    Within the same execution of Retrospect, I do not know how to quit and relaunch the console (I suppose I could look it up). I'm only a small-scale Retrospect user; I run the entire backup server complex on a single Mac Pro.

     

    I'll be glad to help in any way I can in debugging this. And may HaShem have mercy on our souls. ;)


  16. 22 November: As scheduled every Saturday, yesterday reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. As soon as "Sat. Backup" had completed, the bug described here (no subdivision for the first-backed-up drive, which is "Macintosh HD" on the client "David's MacBook Pro") appeared in the Console Backups panel bar graph. Today—Sunday—that bug was not fixed in the Saturday bar graph after "Sun.-Fri. Backup" (No Media Action) had completed. (In its place a further bug in the Saturday bar graph subdivision for the first-backed-up drive in "Sat. Backup" appeared after "Sun.-Fri. Backup" (No Media Action) had completed.) Retrospect 12.5.

     

    The Total GBs for Saturday, even rounding-down the individual drive backed-up amounts, is now about 7GB too low; it appears that the backed-up amount for the second-backed-up drive—"Macintosh HD OS X" on the client "Mimi's Old G4"—is no longer included in the Total GBs for "Sat. Backup"—even though it is a subdivision on the bar graph.

     

    This is not a bar graph bug, but a bug in the Total GBs for a particular day in the Console Backups panel. Although I reported it in the last paragraph of the linked-to post in the Console Backups panel bar graph bug topic, I wanted this bug to have its own topic for greater visibility. (I also wanted to test out the url editing tag, to see if it works the same way as it does on the Ars Technica forums; it does—maybe the Retrospect forums should display the same panoply of editing aids including smilies. :) )


  17. 22 November: As scheduled every Saturday, yesterday reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. As soon as "Sat. Backup" had completed, the bug—no subdivision for the first-backed-up drive—appeared on the Console Backups panel. Today the subdivision for the first-backed-up drive in "Sat. Backup", which is "Macintosh HD" on the client "David's MacBook Pro", did not re-appear in the Saturday bar graph after "Sun.-Fri. Backup" (No Media Action) had completed. In its place (the rightmost place—remember that subdivisions appear in the graph in the reverse sequence of their backup), the subdivision for the last-backed-up drive in "Sat. Backup", which is "Macintosh HD New" on the server "Ronny's Mac Pro", was duplicated in the bar graph for "Sat. Backup" after "Sun.-Fri. Backup" (No Media Action) had completed.

     

    The Total GBs for Saturday, even rounding-down the individual drive backed-up amounts, is now about 7GB too low; it appears that the backed-up amount for the second-backed-up drive—"Macintosh HD OS X" on the client "Mimi's Old G4"—is no longer included in the Total GBs—even though it is a subdivision on the bar graph. This is not a bar graph bug, but a bug elsewhere in the Console Backups panel (I can't change the topic title, or I would have).


  18. Here's a Console Backups panel bug that I've noticed again this afternoon, originally associated with the script "Sat. Backup NoMacHDNew" that has since been replaced by the script "Sat. Backup". Retrospect 12.5 all the way.

     

    10 September: The bar graph for last Saturday—which is subdivided by drive in the reverse sequence of their backup (I guess that's reasonable, and the mouse-over display is cool)—shows no subdivision for the first-backed-up drive in "Sat. Backup NoMacHDNew", which is "Macintosh HD" on the client "David's MacBook Pro". The GB for that drive is, however, included in the Total GBs.

     

    12 September: As scheduled every Saturday, today reran "Sat. Backup NoMacHDNew" (Recycle MediaSet) followed by "Sat. Backup OnlyMacHDNew" (No Media Action) to a different MediaSet. As soon as "Sat. Backup NoMacHDNew" had completed, the bug—no subdivision for the first-backed-up drive—appeared on the Console Backups panel—which only shows a bar graph entry for the latest day after at least one script has run on that day. However the subdivision for the first-backed-up drive in "Sat. Backup NoMacHDNew", which is "Macintosh HD" on the client "David's MacBook Pro", re-appeared in the bar graph after "Sat. Backup OnlyMacHDNew" had completed.

     

    15 November: As scheduled every Saturday, yesterday reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. As soon as "Sat. Backup" had completed, the bug—no subdivision for the first-backed-up drive—appeared on the Console Backups panel. Today the subdivision for the first-backed-up drive in "Sat. Backup", which is "Macintosh HD" on the client "David's MacBook Pro", did not re-appear in the bar graph after "Sun.-Fri. Backup" (No Media Action) had completed.

    • Like 1

  19. Thinking about this again, I now suspect that this is a "feature" of App Store.app that downloads a app Purchase originally made for another machine under the same Apple ID into the folder where it finds that app on this machine. I had originally Purchased both iMovie.app and iPhoto.app for my MBP, and ~/Documents/PhotosRestored/Media Set Red/Applications was a copy restored onto my Mac Pro of the Applications folder on my MBP. The dates for both iMovie.app and iPhoto.app in ~/Documents/PhotosRestored/Media Set Red/Applications are the dates I downloaded them onto the Mac Pro.

     

    So you're off the hook, Retrospect Inc.; this is not a Retrospect bug. The rest of you Retrospect users: if you restore a copy of an Applications folder from one machine onto another, it might be a good idea to delete that restored Applications folder after you've copied what you need from it.

     

    P.S.: Monday I deleted the ~/Documents/PhotosRestored/Media Set Red/Applications folder from my Mac Pro. Sure enough, App Store.app on the Mac Pro stopped showing the un-updatable Update for GarageBand 6.0.5. :) (You don't want to hear about my GarageBand Update problem; that's purely an App Store affair that doesn't involve Retrospect.)


  20. I had never had iPhoto in the Applications folder on my Mac Pro but had Purchased it for my MacBook Pro in December 2014. I simply had to click the button in App Store Purchases to download it onto the Mac Pro. :)

    However App Store downloaded iPhoto 9.6.1 not into the normal Applications folder, but into ~/Documents/PhotosRestored/Media Set Red/Applications. This is a folder I restored from the MBP with Retrospect 12.0 on 31 July, so that I could print a photo from DropBox on an inherited USB color printer cabled to the Mac Pro. When I found iPhoto.app 9.6.1 there, I also found the iMovie.app I had Updated from the App Store earlier last month that had mysteriously never appeared in the normal Applications folder. So there's either a bug in Retrospect that subsequently confuses App Store.app, or a bug in App Store.app that is confused by a prior Retrospect Restore script.

    • Like 1

  21. Yesterday I unintentionally left Retrospect 12.5 idle on my Mac Pro under OS X 10.10.5, after running my usual 8-hour "Sat. Backup" of 6 drives onto the Recycled Media Set White. This morning around 9:30 a.m. I noticed that the Mac Pro was on, and that the normal "Sun.-Fri. Backup" No Media Action scripted backup of my MacBook Pro—which should have run at 3 a.m. if the MBP was running—failed around 4:15 a.m. during the scan with error -559 (network connection timeout). (This possibly happened because I had been working on the MBP intermittently during the night, and put it to sleep at some point.) There were 8 warnings from OS X about G-Drive White having been removed, all of which disappeared when I clicked on the top one in the right-of-screen column of warnings.

     

    I then manually started the "Sun.-Fri. Backup" script, which incrementally backed up the MBP unevenfully in 10 minutes as usual.

     

    What occurs to me is that, since I have regular-to-micro cables attached to two different 6Gb/sec ports on my NewerTech USB3/eSata host adapter and usually alternate between them as I swap G-Drives on Friday afternoon, maybe the cable I used to attach G-Drive White wasn't solidly plugged in. But then why did the "Sat. Backup" script run in the normal amount of time without unusual Log errors?

     

    Oops, while I was writing this on my MBP, I got an unexpected but welcome long phone call. I had rebooted the Mac Pro just to check the Retrospect Log for this post, but then pushed the cable attached to G-Drive White and felt it move in a millimeter or two. When I just now went to shut down the Mac Pro, there was a removed-without-dismount warning for G-Drive White sitting at the top right corner of the monitor. Maybe there's a cable/port problem that's causing these warnings.

     

    P.S.: I later remembered that, when I first saw removed-without-dismount warnings back in July, I had just installed Retrospect 12 and attached the newly-purchased G-Drive White. I named it G-Drive White, and created Media Set White on it, because I had recently used the Storage Set Red to make backups onto DAT tape under Retrospect 6.1 on my G4 Digital Audio tower running OS X 10.3.9 (and I—as a patriotic American—give three cheers for the Red, White, and Blue in that sequence ;) ). I think the adapter port and cable were the same as on Saturday.


  22. Interesting.

     

     

    Ever since I installed Retrospect 12.0.2(116) in July on my Mac Pro, I've been getting intermittent messages from Mac OS X 10.10 warning me that I shouldn't dismount drives without doing it through the Finder. These messages come when I boot up the machine, and thus seem to refer to something I must have done previously. I just boot the machine once a day after having left on whatever client machines are going to be backed up that day, let Retrospect run the one scheduled backup script after it starts via System Preferences->Users & Groups->Login Items, then eyeball the Log and shutdown the Mac Pro. I don't bother to see if the USB drive-of-the-week is still really mounted.

     

     

    I'm still getting this occasionally, I think, under OS X 10.10.5 running Retrospect 12.5. My USB3 G-Tech G-Drive Slim drive-of-the-week is attached to a NewerTech USB/eSata host adapter with 6Gb/s ports. Tomorrow after the backup script runs, I'll quit Retrospect and attempt to do a GetInfo of the USB3 drive.


  23. A week later nobody has attempted to explain it, so I've re-posted it as a bug.

     

     

    As further evidence, I ran my Saturday Recycle Media Set backup again yesterday—this week onto Media Set Red. I got the same 18GB difference between the total to the left of the Sat. bar graph of the Dashboard's Backup section and the total to the left of the bar graph for Media Set Red in the Storage section. Media Set Red is also, FYI, a Disk Media Set.

     

     

    Here's my shot at an explanation of what is really a "conceptual" bug. It kind of makes sense to have the un-deduplicated "found" total for a drive be shown in _one_ place on the console, to reassure users that in fact all of the contents of a particular drive has been backed up _someplace_ on the Media Set. But that place should be the total to the left of the day's bar graph of the Dashboard's _Backup_ section, and also in the subdivision mouse-overs in the day's bar graph. The total to the left of the bar graph for the Media Set in the _Storage_ section of the Dashboard should be a sum of deduplicated "copied" totals, because that section is for users concerned about storage use.


  24. For several weeks I've noticed a discrepancy between storage use reported for multi-drive-backup days in the Backups section vs. the Storage section of my Retrospect 12.5 Dashboard. No one in "Retrospect 9 or higher for Macintosh" has provided any reason for the discrepancy, so I'm reporting it as a bug.


    As all you attentive readers must know by now, on Saturdays I do a Recycle Media Set backup of all 6 of my hard drives, rotating among 3 Media Sets. A week ago yesterday I backed up onto Media Set Blue. The total to the left of the Sat. bar graph of the Dashboard's Backup section reported I had backed up 181.2GB, which agreed with the sum of the subdivision mouse-overs in the bar graph, and these in turn agreed with the Log. However the total to the left of the bar graph for Media Set Blue in the Storage section of the Dashboard reported that I had Used 200GB. The difference, allowing for the fact that the Storage section totals round (upwards?) to an integer, is about 18.8 GB. That seems to be rather close to the 17.8GB Log difference between 48.2GB found and 30.4GB copied for "Macintosh HD New" on "Ronny's Mac Pro" server, which is no doubt due to deduplication because both that drive and "Macintosh HD" on "David's MacBook Pro"—which backs up first on Saturday—are running OS X 10.10.5 ("Macintosh HD" on "Ronny's Mac Pro" runs OS X 10.6.8 when it boots, "Macintosh HD OS X" on "Mimi's Old G4" runs OS X 10.3.9, and the other two drives on "Mimi's Old G4" run OS 9.1 when they boot).


    The Storage section totals may include Snapshots, which—per the Log—the Backup section totals do not; subtracting those would bring the Dashboard section discrepancy even closer to the Log found/copied difference for "Macintosh HD New". If you were thinking "Media Set drive catalog", think again; the Finder's GetInfo total for 1-Media Set Blue is 215GB. FYI, Media Set Blue is a Disk Media Set.

    Can anyone explain the discrepancy?

    A week later nobody has attempted to explain it in "Retrospect 9 or higher for Macintosh", so I'm re-posting it here as a bug.


    As further evidence, I ran my Saturday Recycle Media Set backup again yesterday—this week onto Media Set Red. I got the same 18GB difference between the total to the left of the Sat. bar graph of the Dashboard's Backup section and the total to the left of the bar graph for Media Set Red in the Storage section. Media Set Red is also, FYI, a Disk Media Set.


    Here's my shot at an explanation of what is really a "conceptual" bug. It kind of makes sense to have the un-deduplicated "found" total for a drive be shown in one place on the console, to reassure users that in fact all of the contents of a particular drive has been backed up someplace on the Media Set. But that place should be the total to the left of the day's bar graph of the Dashboard's Backup section, and also in the subdivision mouse-overs in the day's bar graph. The total to the left of the bar graph for the Media Set in the Storage section of the Dashboard should be a sum of deduplicated "copied" totals, because that section is for users concerned about storage use.

×