Jump to content

DavidHertzberg

Members
  • Content count

    957
  • Joined

  • Last visited

  • Days Won

    34

Everything posted by DavidHertzberg

  1. 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?
  2. 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. Retrospect Inc. should "fix" his "bug" so he doesn't give out incorrect information to users.
  3. 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.
  4. I have 3 Macs at home: a 2011 MacBook Pro running OS X 10.10, a 2000(?) G4 Digital Audio tower that for now must run OS X 10.3, and a 2010 Mac Pro (that I inherited from a dead friend) running OS X 10.10 on the normal boot drive. The Mac Pro is my Retrospect 12 server; the other 2 Macs are clients on an Ethernet LAN. Every Saturday I run a Recycle MediaSet backup of all 6 hard drives (the G4 also has 2 OS 9.1 drives), which takes 7.5 hours. It would make life much simpler if I could get Retrospect to backup the 2 client machines first, which would free up the MacBook Pro after 3 hours and the G4 tower after another 1.5 hours. But Retrospect wouldn't do that; it backed up the MacBook Pro first, then both drives on the Mac Pro (for another 3 hours), and finally the G4 tower drives. I know I could get the desired result by separating the Saturday backup into 2 scripts: one--scheduled first--to backup only the client machines, and another--scheduled after that--to backup only the server machine. But that would be inelegant, so I phoned Retrospect Inc. tech support (I was still within my first 30 days) to ask how to change the order in which Sources back up within a script. The regular tech support guy (whom I will refer to here as A.) said that was "an algorithm that the developers know", but that he didn't know. I thought that was both ridiculous and intriguing, so I started thinking about this "secret unchangeable algorithm". I decided that, if I were programming Retrospect and didn't want to be bothered with making the order of Sources movable in the Console, I would use the alphanumeric sort sequence of each Source's Computer Name--as defined in its Sharing preferences. This explained the machine order I was getting on my Saturday backup script; I had given my machines the Computer Names "David's MacBook Pro", "David's Mac Pro", and "David's Old G4". So I changed the Computer Name on my G4 tower to "Mimi's Old G4" (Mimi being the nickname of my ex-wife, who gave me the tower after she decided to get a PowerBook), and the Computer Name on my Mac Pro to "Ronny's Mac Pro" (Ronny being the name of the dead friend from whom I inherited it). I then stopped and started their Retrospect Clients and Removed and re-Added both clients in the Retrospect Console. The names in the Machine column in the Source and Script Source reports in the Console changed accordingly, but the Saturday script still backed up my machines in the same undesirable order--as shown by running an incremental No Media Action copy of my Saturday script. I realized that the problem was with the two Mac Pro drives; their hidden Machine Names must not have changed because--as drives locally mounted on the server--Retrospect would not permit me to Remove and Add them. So I tried a bold experiment; I shut down the Mac Pro, physically pulled my friend's old "Macintosh HD" (which is not the current-boot-drive "Macintosh HD New"), and rebooted the Mac Pro. Retrospect then permitted me to Remove my friend's old "Macintosh HD" as a Source, because it was no longer locally mounted. Finally I shut down the Mac Pro again, put my friend's old "Macintosh HD" back into the machine, and rebooted it. My friend's old "Macintosh HD" showed up again in the Source report, and I clicked the Script Source checkbox to add it back to my Saturday script. That drive now backs up after "David's MacBook Pro" and "Mimi's Old G4", but "Macintosh HD New" still backs up between "David's MacBook Pro" and "Mimi's Old G4" because its hidden Machine Name is still "David's Mac Pro" instead of "Ronny's Mac Pro"--and I can't change that in Retrospect because I can't run it with the boot/Retrospect drive pulled. The moral of this story is that before installing Retrospect on the server(s) you should decide on what 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. Only after you have done this should you install Retrospect on the server(s). P.S.: It goes without saying that this "secret" should be documented in the User Manual ASAP. I'm also going to file a Product Suggestion that, in the Console Sources report, it at least be made possible to "pre-Remove" a locally-mounted-to-server drive so that it can then be truly Removed for the duration of that Console execution. The Removed local drive would of course show up in Sources again when Retrospect Console is next started--just the way my Removed old "Macintosh HD" showed up when I booted the Mac Pro after putting that drive back into the machine, but it would show up with the current Machine Name and be backed up--once it was re-checkmarked in the appropriate scripts--in the alphanumeric sequence of that current Machine Name. P.P.S.: In case it's not clear, the bug is that--because the locally-mounted-to-Server drive that contains the running executable for Retrospect 12 Server cannot be Removed as a Source--that drive can only be backed up in a within-script sequence dictated by the Server's original Computer Name at the time Retrospect 12 was installed on it. The consequence of the bug is that the locally-mounted-to-Server drive that contains the running executable for Retrospect 12 Server must be backed up in a separate script running before or after a script that also backs up other computers, unless you are happy with the within-script backup sequence that the Server's original Computer Name at the time Retrospect 12 Server was installed on it imposes. P.P.P.S: To improve readability, changed before-and-after-phrase underscores to making word/phrase italic.
  5. 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.
  6. 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.
  7. 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.
  8. 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.
  9. 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.
  10. 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.
  11. DavidHertzberg

    Console Backups panel bar graph bug for multi-drive backup

      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.
  12. DavidHertzberg

    Console Backups panel bar graph bug for multi-drive backup

    5 December: As scheduled every Saturday, today reran "Sat. Backup" (Recycle MediaSet) to a different MediaSet. The bar graph subdivisions for the six drives were correct. Nothing was different except the (rotated) Media Set onto which the backup took place. I pity the poor Retrospect Inc. programmer who has to debug this mess.
  13. 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. )
  14. DavidHertzberg

    Console Backups panel bar graph bug for multi-drive backup

    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).
  15. DavidHertzberg

    Restore script run later confuses App Store.app

    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.)
  16. 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.
  17. 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.
  18. 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.
  19. 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 Dashboard. Unless someone can provide a good reason for the discrepancy, I'm going to report 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. 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?
  20. 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.
  21. 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.
  22. I have 3 identical 512GB G-Tech G-Drive Slim drives: "G-Drive Red", "G-Drive White", and "G-Drive Blue" (I'm a patriotic American, even if the drives are made in China from a Japanese design ;-) ). On each drive I have a correspondingly-named Disk Media Set: "Media Set Red", "Media Set White", and "Media Set Blue". So far as I can recall, I created each of the Media Sets the same way, although not at the same time ("Media Set White" was a File Media Set for the first week I used it--I changed it when I recycled on the advice of A. of Retrospect TS, and I bought "G-Drive Red" at the same store two weeks later when I realized two media sets were insufficient for weekly rotation when the off-site site is a bank safe-deposit box). Retrospect 12 shows that "Media Set Red" and "Media Set White" have Capacities of 465GB, but "Media Set Blue" has a Capacity of 292GB. Neither a couple of rotational Recycle Media Set backups nor a Rebuild of "Media Set Blue" has changed that Capacity figure. Get Info shows the same size of 512GB for all 3 drives, which all have a GUID partition scheme. What could I have done that would make "Media Set Blue" different? How can I expand its official Capacity (just before I Recycle it in two weeks)? BTW, I also found a definite bug in the course of doing the Rebuild of "Media Set Blue". The Console showed no Active script after the Rebuild portion of the script was finished, but the log said a Verify had been canceled due to user intervention after one minute. I then did a separate Verify, which never showed up as an Active script even though the log said a Verify operation had completed successfully after 38 minutes.
  23. Thanks, Derek500. After reading your reply, I went to my "Sat. Backup Incremental" script Summary and dragged the locally-attached-to-server "Macintosh HD New" drive to the bottom of the drive order--where I had wanted it to be. I then ran the script, and it backed up all my drives in my preferred sequence. You're not misunderstanding my issue at all. I just didn't know that you have to drag drives in the Summary; back in July I had tried dragging them in the Sources tab--where you checkmark them, and they wouldn't drag. I had then phoned Alan at Retrospect Inc. TS, and he said you couldn't change the drive sequence--that "there is an algorithm which the developers know" that determines the sequence within a script. That's what I found ridiculous and intriguing, which led to my experimenting and starting this thread. Alan (whom I am naming because I am angry at him) claimed this afternoon that there must have been a miscommunication between us. I told him I was displeased with him, but not quite displeased enough to e-mail Robin about the incident. I also told him that dragging the drives in the script Summary to change the sequence should have been documented in the User Guide; I checked, and it definitely isn't. To me it's not a feature that is obvious, and it's significant that--of all the 150+ people who viewed my bug report over the past 3 weeks--nobody until you suggested it. I still think that the inability to Remove a locally-attached-to-server drive without physically pulling it first--which of course you can't do for the drive running Retrospect--is a monumental kludge, although maybe not technically a bug in itself. However, when combined with Retrospect's "secret" algorithm for pre-determining drive-backup sequence within all scripts (subject to override for an individual script by dragging in its Summary), I think it rises to the level of a bug. Does anybody have any suggestion as to why Retrospect has this inability programmed in? P.S.: This morning I duplicated the script "Sat. Backup NoMacHDNew" as "Sat. Backup", and checkmarked "Macintosh HD New" in the Sources tab. "Macintosh HD New" showed up as the last Source of the Details panel in the Summary tab--the sequence position I want, so I didn't even have to drag it. I should point out that I installed Retrospect 12.5 yesterday on Ronny's Mac Pro, so Retrospect Inc. may have fixed the underlying "hidden Machine Name for server drives is not updated in Retrospect when it is changed in server System Preferences->Sharing" bug--although such a bug fix is not mentioned in the Release Notes. Anyway, the proof of the pudding will come Saturday when "Sat. Backup" runs (I deleted the scripts "Sat. Backup NoMacHDNew" and "Sat. Backup OnlyMacHDNew"). P.P.S.: The new script "Sat. Backup" ran this morning. It backed up "Macintosh HD New" on Ronny's Mac Pro last, as I intended. BTW, I tried to do a Source Remove of the locally-mounted-to-server "Macintosh HD New" under Retrospect 12.5. The Remove button is still dimmed. so they didn't fix that kludge. P.P.P.S: To improve readability, changed before-and-after-phrase underscores to making word/phrase italic.
  24. Here's a couple of Console Backups panel bugs, that I noticed this afternoon, associated with the script "Sat. Backup NoMacHDNew" (Recycle MediaSet) as discussed in the quoted post. First, the Total GBs for last Saturday double-counts the 105.7GB backup of the last-backedup drive in that script, which is the locally-mounted old "Macintosh HD". (There is no double-counting for the single locally-mounted "Macintosh HD New" drive in the second-run script "Sat. Backup OnlyMacHDNew" (No Media Action).) Second, 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-backedup 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. P.S.: As scheduled every Saturday, today (12 September) 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 second bug--no subdivision for the first-backedup 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-backedup 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. The first bug, the double-counting of the 105.7GB backup of the last-backedup drive in "Sat. Backup NoMacHDNew", never appeared--even after a server shutdown and restart. P.P.S: To improve readability, changed before-and-after-phrase underscores to making word/phrase italic.
  25. Thank you, Lucky_Phil. I should have known that, but I hadn't bought external drives for many years. For those of the fellow-ignorant who don't have time to read his linked-to page (which actually doesn't take very long to read), the short version of his answer is: For reasons of mathematical convenience and tradition, to computer people 1K does not mean 10**3 = 1000 but 2**10 = 1024. However for reasons of sales hype, disk drive vendors consider themselves to be ordinary metric system users instead of computer people, so to them 1K means 10**3 = 1000. That goes for all the multipliers of 1K, so what G-Tech calls a 500GB capacity disk drive is what computer people would call a 465GB capacity disk drive. Retrospect is designed to be used by computer people. Not that I use tape drives any more, but I assume that tape drive vendors describe capacity using the same terms as disk drive vendors.
×