Jump to content

DavidHertzberg

Members
  • Content count

    1,199
  • Joined

  • Last visited

  • Days Won

    40

DavidHertzberg last won the day on May 14

DavidHertzberg had the most liked content!

Community Reputation

65 Excellent

About DavidHertzberg

  • Rank
    Occasional Forum Poster

Profile Information

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

Recent Profile Visitors

1,974 profile views
  1. DavidHertzberg

    cannot find Catalog File

    billbobdole, Here's a possible simple fix: Underneath the "Retrospect" folder on each of my 3 USB3 portable destination disks, there is a zero-byte Unix executable file named "Backup Media" that was created in August 2015 (when I first started using modern Retrospect Mac with Disk Media Sets) and hasn't been modified since. My hunch is that the lack of that file within your folder "Backup Sets" is what's preventing Retrospect Windows from locating the Catalog File; according to the first paragraph of this 2019 post, "The split catalog file will be named 'Backup Set Name.cat.'"" P.S.: Fortunately for him mbennett—whose Forums posting history only goes back to 2015—has no idea of the morass billbobdole is in. To understand it, mbennett can first read the short section "File Backup Sets" on page 45 of the Retrospect Windows 17 User's Guide—which implies why they are obsolete—and then this November 2019 post. Finally he should read this up-thread post by billbobdole, who is fundamentally the victim of one of the multiple f**kups in macOS 10.15 Catalina. (According to at least one knowledgeable poster on the Ars Technica Mac forum, these f**kups seem to be caused by very-centralized Apple management's concentrating on iOS—the mobile-oriented OS that provides the bulk of Apple's current revenue—and leaving "enhancements" of macOS to a basically-uncoordinated "second-string team".) Reasoning that the SMB share disconnection f**kup is unlikely to be fixed in Catalina (maybe it will be fixed in the forthcoming macOS 10.16), billbobdole is attempting to use his existing SMB share on a Retrospect Windows 17 "backup server"—running under an OS that continues to be developed by the company that invented SMB. He's being hit with the problem that Retrospect Windows 17 can't find his cross-graded Catalogs, which—because they are for many individual File Backup Sets—are on his SMB share. My suggestion in the first paragraph of this post attempts to deal with that problem. IMHO billbobdole really needs to talk to Retrospect Tech Support.
  2. DavidHertzberg

    cannot find Catalog File

    Oh my, billbobdole, it appears you're still using the same ancient trick with File Media Sets I described 6 months ago—except now you're trying to do it under Retrospect Windows (17?) with the File Media Sets supposed to be treated as File Backup Sets. 😢 At a minimum you need Retrospect Windows and Windows expertise, which as a Mac administrator I can't provide—but maybe Nigel Smith or Lennart_T can. What version of Windows are you running under? Did your 2012 Mac Mini die, or did the trick not work under Catalina? At a maximum you need the help of Retrospect Tech Support. If you upgraded to Retrospect Windows 17 within the last 30 days, you are entitled to free personalized Tech Support. And IMHO you need that kind of support; I don't even know if your trick works the same way under Retrospect Windows 17.
  3. DavidHertzberg

    Yet another -530 client not found error

    rfajman, You've left out a key word after "dedicated Gigabit Ethernet": "dedicated Gigabit Ethernet WHATSIS". Is the WHATSIS a piece of hardware—such as a router or "gateway", or is it a piece of software—such as something in Microsoft Windows 10. The WHATSIS apparently has an interface, and that interface is checkable and configurable via a command file. Some Googling seems to show that Gigabit Internet interface is a connection between a computer and a router. You may have a Windows 10 problem, but I'll let someone who knows Windows explore (no pun intended) that further—based on further information about your script that you must provide. P.S.: Rewrote 2nd sentence of 2nd paragraph; the interface isn't necessarily a particular Windows table.
  4. DavidHertzberg

    Scheduling a one-time backup

    rfajman, The facility you want is probably already in Retrospect Windows 16; it is called a "run document". See pages 236–238 of the Retrospect Windows 16 User's Guide.
  5. DavidHertzberg

    Yet another -530 client not found error

    MrPete, For the problem described inside parentheses in your first paragraph, have you defined your subnets per pages 228–229 of the Retrospect Windows 17 User's Guide—and have you added such clients using the Subnet Broadcast access method per the Access Tab alluded to (not described) on page 223? My impression is that Subnet Broadcast—which I've never used for its intended purpose—searches for the "client" machine using the Piton Name Service on each of the subnets defined on the "backup server". If that doesn't do what you need, here's why and how to create a feature request Support Case for enabling multiple Direct Access addresses for a particular "client".
  6. DavidHertzberg

    Windows 10 Feature Release 2004

    speedyme, You can find your answer in the cumulative Release Notes for Retrospect Windows. But I'll save you the effort of reading the most recent entries; the answer is no.
  7. DavidHertzberg

    Yet another -530 client not found error

    Nigel Smith, Your 10-step guess as to what might have been happening may be correct, although you got confused about the Location of my first test—it was "Automatic" (X.Y.Z.202) instead of "Retrospect Priority" (X.Y.Z.201). I reran that test yesterday, but—after changing the Location of my MacBook Pro "client" machine—scheduled the backup run 15 minutes in the future and then shut down and re-booted my "backup server". This time the No Files backup ran with no error. 😲 That raised the question of how the Retrospect Engine had been able to find the MBP Source, which I am sure I had defined with Add Source Directly as X.Y.Z.201. The answer seems to be the "magic" of Piton Name Service. When I did a Locate of that Source after the test, it found the MBP via Multicast as X.Y.Z.202. (I intentionally did not do a Locate after re-booting the "backup server" but before the test run was scheduled, because I found 3 years ago that a pre-Backup Locate would eliminate a -530 error that otherwise would occur.) So am I going to investigate this further in my installation, other than possibly making the effort (because of necessary script changes) to Remove and re-Add my MBP as a Source with Use Multicast? No I am not, because of an experience I had with Tech Support over two years ago. As the third paragraph of that post says, T. S. twice gave me test versions of Retrospect with extra logging. I uploaded the results to my Support Case, and got back a reply that said basically "Yes we see a problem, but we can't do anything about it unless we can reproduce it on our own machines—because it seems to be at least partially related to network hardware." I thereupon offered to snail-mail T. S. my two MoCA adapters (for which I had by then bought higher-speed replacements) and a 40-foot length of previously-bought-for-testing Radio Shack coax cable to run between them, but got back a reply that said basically "Thanks for the offer, but we cannot take responsibility for customer-owned hardware." I then suggested they find someone in the Retrospect Inc. organization who had gone far enough in law school to be able to write a deed of gift to Retrospect Inc. that I could sign, but they didn't reply. ☹️ So, as the last paragraph in this up-thread post states, we'll just have to wait until StorCentric discovers the -530 problem for the forthcoming Drobo variant of the "backup server"—and provides Retrospect "Inc." engineers the necessary resources to find and fix the problem. 😢
  8. DavidHertzberg

    Yet another -530 client not found error

    Nigel Smith, You are correct about my having defined the Piton protocol too narrowly; Instead of writing "multicast Piton Protocol", I should have used the term Piton Name Service—per page 227 of the Retrospect Windows 17 User's Guide. At last the -530 versus -519 difference is clarified. On page 221 the UG says: Page 228 says: Page 33 of the Appendices says: In fact, a closer examination of the log for my first test run illustrates the difference between the overall Piton protocol and Piton Name Service in a rather interesting way (it turns out I didn't need WireShark. 😁). The run actually "Finished scanning backup set data files to ... ", then issued the message "Can't access backup client ..., error -519 (network communications failed)". It seems my "backup server" managed to find my MacBook Pro "client" by name, when it couldn't do so by Direct Access because the IP address the "client" was using didn't match the one defined in Sources. Then, after successfully finishing scanning, the "backup server" said "Wait a minute, that's not the Source I'm supposed to back up" and issued the -519 error—not a -530 error. By contrast, the log for my second test run—where the IP address the "client" was using did match the one defined in Sources—says "Can't read state info, error -519 (network communications failed)" when I too-rapidly shut down the MBP after the "backup server" had successfully finished the backup stage. Thus it's the Piton Name Service that needs to be fixed. As I've predicted elsewhere, StorCentric will have to force this to be done for the forthcoming Drobo variant of the "backup server"—so hordes of new Retrospect users won't have to learn how to set up Direct access to avoid -530 errors.
  9. DavidHertzberg

    Yet another -530 client not found error

    I am in fact doing what Nigel Smith calls "belt-and-brace" ("braces" are British English for what the rest of us call "suspenders") ; I have entries both in my router's MAC table and my MacBook Pro's System Preferences->Network->Locations for both my Moshi USB-C-to-Ethernet adapter port (X.Y.Z.201) and my CalDigit TS3 Plus Ethernet port (X.Y.Z.202)—X and Y and Z are "seekrit" numbers you couldn't 🤣 possibly guess.. My "Automatic" Location has the CalDigit port enabled, and my "Retrospect Priority" Location has the Moshi port enabled. On my Retrospect Mac 16.6 "backup server", the Source for the MBP is defined with Add Source Directly as X.Y.Z.201—and my MBP usually uses the "Retrospect Priority" Location although the "Automatic" Location would give me slightly-faster Ethernet via Thunderbolt 3. Yesterday afternoon I did a couple of tests, using my handy-dandy NoOpSun-FriBackup script with the No Files Rule (Selector in Retrospect Windows). I first switched my MBP to the "Automatic" location and ran the script, which immediately issued a -519 error for the MBP. (That error number is an argument for my side in the 6-months-back dispute with Nigel Smith over whether the "backup server" uses the multicast Piton Protocol in finding a Source defined with a correct MAC address using Add Source Directly. My "backup server" would have found the MBP by name if it had used the Piton Protocol, or it would have issued a -530 error.) I then switched my MBP's Location to "Retrospect Priority" and reran the script. It started to run fine, until I too-rapidly shut down the MBP while the script was still making its 4-minute run—eliciting a "backup server" -519 error. (Point for Nigel Smith in the 6-months-back dispute; "the client was found, then disappeared".) Getting back to Nigel Smith's final warning, x509 should certainly find out what range for fixed IPs his router allows. I believe I checked the manual for my ancient Verizon Quantum G1100 "gateway", but I simply set up fixed IP addresses starting with X.Y.Z.200.
  10. DavidHertzberg

    Yet another -530 client not found error

    x509, I did a little Googling, and—just below the heading "How to assign static IP address using Settings" [my emphasis] on this Pureinfotech article on "How to set a static IP address on Windows 10"—is a section "Assigning static IP address for Wi-Fi adapter". So you wouldn't have to do scripting or get into your router's assignments table, but—from what you and mbennett have said up-thread—a Windows update might silently reset any such settings. Everyone, I went searching for this because I couldn't believe that modern Windows doesn't have the equivalent of the System Preferences->Network->Location dialog in macOS, for x509 to use with his Wi-Fi. This facility was developed in OS X to provide for Mac laptops that might be moved to different locations (hence the name) having different LANs, and is available as far back as my ex-wife's ancient Digital Audio G4 booting 2003's "Panther" OS X 10.3. Although my MacBook Pro never leaves my study desk, I discovered Location after I bought a CalDigit Thunderbolt Station 3 Plus dock to connect it via a KVM switch to a an external monitor. When my Apple 27-inch LED Cinema Display loses the video signal, it goes into a "deep sleep" mode—and needs to be "goosed" to wake up. If my KVM switch is still set to take input from the CalDigit dock, it has lost the DisplayPort video because I shut down the MacBook Pro the input was indirectly coming from—so rebooting the MBP results in the dock "goosing" the monitor. If OTOH my KVM switch was formerly set to take input from the G4 via converted DVI, it has lost the DisplayPort video because I switched it to an awake MBP—and only rebooting the dock results in the dock "goosing" the monitor. In that second case I originally found that detaching and re-attaching either end of the Thunderbolt 3 cable between the MBP and the dock was sufficient to reboot the dock—as was unplugging and re-inserting the dock's power cord, but a woman at Apple Tech Support suggested that a method which wouldn't violate any mechanical port-insertion limits would be to plug the dock into a surge protector whose sturdy switch I could use to reboot the dock—so I'm doing it. This created a problem with using Retrospect to simultaneously Recycle backup my MBP—using version 16 and an Ethernet connection wired via MoCA (inter-room Wi-Fi is slow in my apartment) to a "backup server" in another room—and my G4—using version 6.1 and a DAT tape drive SCSI-cabled directly to the G4. Using the KVM switch to switch the Cinema Display from the MBP to the G4 works fine, because the G4 automatically "gooses" the monitor out of "deep sleep". However using the KVM switch to switch the Cinema Display from the G4 to the MBP was killing the MBP's backup, because power-cycling the CalDigit dock was interrupting its Ethernet connection. My solution was to create a Location named "Retrospect Priority" in addition to the "Automatic" one. In "Retrospect Priority" the MBP's Ethernet connection is via a Moshi USB-C-to-Ethernet adapter (used with iffy StarTech USB32DPPRO before CalDigit), and the Ethernet connection through the dock is disabled—so power-cycling the CalDigit won't interrupt the MBP's Ethernet connection. I took the trouble to explain this because, now that external docks are becoming popular, other administrators with DisplayPort or Thunderbolt 3 monitors in their installations may have similar problems. The "deep sleep" feature is common to many such monitors—not just Apple's, and represents monitor manufacturers taking advantage of a DisplayPort (and Thunderbolt 3, which merges DisplayPort + PCIe + DC power) characteristic to lengthen monitor life—ignoring DP cable swappers and KVM switchers. HDMI monitors also have a "deep sleep" feature, but it can be disabled in some models.
  11. DavidHertzberg

    Retrospect 17 and low-end users

    Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. x509, The x.5 release of major version x is usually in late August or early September, and includes new Retrospect features. The fact that 17.0.2, consisting of bug fixes for big installations, was released in mid-May means IMHO there isn't going to be a release 17.1; I'd love to be proven wrong in this. My information is that engineers are hard at work on the variant of the "backup server" running on (beefed-up) Drobo hardware  (and possibly other Linux-based NASes), because it sounds as if that's the main reason StorCentric bought Retrospect Inc.. If OTOH you're looking for improvements in the Client programs that would overcome the -530 problem and difficulties with Windows 10, my feeling is that Retrospect "Inc." engineers won't be allowed to put in that effort until StorCentric management sees the Drobo variant of the "backup server" operating in 17.5 trying to backup Windows "clients"—and realizes that there are serious Client problems for some administrators. So my expectation is that we won't see the kind of upgrade you—and for that matter I personally—want until the release of Retrospect 18.0 in March 2021, or possibly a release 17.6 in December 2020. Sorry to be so pessimistic. 😒
  12. DavidHertzberg

    Applicability of v17 fixes to earlier releases

    rfajman, It's first worth noting that two Engine improvements in Retrospect 17.0.0 are for "10x Faster ProactiveAI" and "Restore Preflight". Years ago you were talking about using Proactive, and administrators have been screaming for Restore Preflight for years. Three out of the four Engine improvements in 17.0.1 are for Remote Backup—which was a new feature in 2018 but has suddenly received administrator attention because of COVID-19 Work From Home, and the other Engine improvement is for Restore Preflight. Second, let us consider the 17.0.1 bug fixes that doubtless apply to earlier major versions of Retrospect Windows—as per the cumulative Release Notes. These are easy to identify, because bug #8547 is a "milestone" that was identified by Tech Support the same day 17.0.0 was released (it's debugging code that was erroneously left in on 3 March). There are 14 bug fixes in 17.0.1 with numbers lower than 8547; these must fix bugs in 16.6 and earlier. Other than #8547 itself, that leaves 16 bug fixes in 17.0.1 that may be for bugs introduced in 17.0.0; OTOH they may instead be for later-discovered bugs in earlier major versions. Of these, 7 bug fixes are for Storage Groups, a feature designed to work with Proactive that was not changed in 17.0.0. Of the remaining 9 bug fixes, 1 was for NAS Shares (3 "fixes" in 17.0.0) and 2 were for ProactiveAI and 1 was for Restore Preflight. That leaves 5 remaining bug fixes for Backup and Install and Configuration and Rebuild, which could have been for bugs introduced in the course of un-noted 17.0.0 changes. So the short answer is that at least 21 bug fixes out of 31 in 17.0.1 also apply to earlier versions of Retrospect, not bugs introduced in 17.0.0.
  13. DavidHertzberg

    Retrospect 17 and low-end users

    rfajman, I looked at your posting history, which you can get to by first clicking the green circular icon containing 'R' (in your case) to the left of any of your posts and then clicking "See their activity". You asked this question for both Retrospect Windows 15 and Retrospect Windows 16. Your were also at one time talking about using ProactiveAI scripts, which were substantially speeded-up for finding the next-available source computer in Retrospect Windows 17.0.0. BTW, cloud backup is a feature added in Retrospect Windows 12; that's 4 major releases ago.. For some of us, March 2016 isn't "relatively recently". 🤣 P.S.: If you're not using Proactive (and you're almost certainly not using Remote Backup), the new feature that would be useful to you might be added in 17.5. As I said in this post in another thread, it looks as if Product Management decided "there's no possibility certain new major features are going to be ready in another week, so let's 'quick-ship' a 17.0 release containing bug fixes plus the three new features that are ready—and then follow up ASAP with a 17.1 or 17.5 release with the other new features." You may not appreciate one future major new feature, which IMHO will likely be a rewrite of the 1990s-designed and klunky built-in GUI for the Retrospect Windows "backup server". But lots of other administrators have complained about that GUI, so they'll probably feel a new one—which ditches Auto Launching and ditches a separate GUI for Immediate operations—is an improvement. It would end the need for two greatly-different User's Guides for the Windows and Mac variants of Retrospect. The real reason IMHO: similar-look GUIs will aid a variant of the "backup server" running on (beefed-up) Drobo hardware (and possibly other Linux-based NASes)—which StorCentric's top management has said it wants, controlled by a GUI Console running similarly on Windows or Mac machines on the same LAN and connected to the "backup server" via a NAS webserver.
  14. Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. denno, Storage Groups were previewed in the fall of 2018, and officially released in March 2019. I was given a feature justification shown in the third paragraph in this March 2019 post, but that justification left out a key element that is still IMHO inadequately documented in the Knowledge Base article—which has been recently copied into the User's Guides. That element, which was not documented in the Forums until this April post, is that "parallel backups" means a single Proactive script can be simultaneously backing up as many as 16 combinations of machine and drive to different Media Set components of its destination Storage Group. This is IMHO a clever riposte—using the multi-threading power of a modern "backup server" machine—to other more-complicated (and more-expensive) client-server backup applications, which require an installation needing equivalent multi-threaded random backup to interpose "appliances" backed up to on multiple "clients" own schedules—as if to an Airport Time Capsule (not necessarily using WiFi )—in between those "clients" and a "backup server" that backs up the "appliances" via periodically-run scripts . As shown especially in the Retrospect Windows cumulative Release Notes, the engineers have since been busy fixing Storage Groups bugs—most of them no doubt pointed out in administrators' Support Cases. The problem is that the engineers have not as yet provided any GUI for accessing the component Media Sets of an existing Storage Group, except for Restore in Retrospect Windows and for using custom Rules/Selectors in operations that can be scripted (i.e. not Rebuild). They may have planned to provide that GUI in the fall of 2019, but any such plans were upended by the StorCentric acquisition on 25 June 2019. Storcentric upper management has publicly announced it intends to build a Retrospect "backup server" that runs on at least a beefed-up Drobo version of a Linux-booting NAS, and my information is that Retrospect engineers are busily at work implementing that. Since NASes don't have their own monitors and keyboards and pointing devices, it seems obvious such a "backup server" would have to be accompanied by a Mac and Windows Console that connects to it over a LAN using (probably) a Web server on the NAS. And lo and behold, a Retrospect Console Preview was released on 3 December 2019—looking rather like a dumbed-down existing Mac LAN Console but also running on a Retrospect Windows "backup server" (where IMHO it'll be better when fully implemented than the 1990s-designed built-in GUI). It doesn't take great "tea leaf reading" skills to predict that it's unlikely further enhancements are going to be made this year to the existing Mac Console GUI. So—if you want to use Storage Groups—you'll for now have to live within the confines of the existing half-baked GUI. Until Retrospect 16 killed the Legacy Client, I was backing up 4 drives in two "client" machines plus two local drives and a Favorite Folder onto three rotated-weekly portable disk Media Sets. Now I'm instead backing up the 3 drives on my old G4 Digital Audio machine to 3 rotated-weekly DAT tape Backup Sets, using Retrospect Mac 6.1. I have a home installation, and I rotate a portable disk and a DAT tape off-site once a week; YMMV. Would describing your "problems with my existing media sets" get you better answers?
  15. denno, Why are you using a Storage Group? Are you backing up many machines, and want the backups to be on separate Media Sets but can't be bothered to set them up along with separate scripts? Or are you using a Proactive script, especially with Remote Backup, and want the backups of individual machines to run in parallel? Otherwise don't use a Storage Group! 😟 The feature was originated in 2018, and evidently was not much used by administrators until COVID-19 Work From Home. Its GUI, especially in Retrospect Mac, is half-baked (3rd linked paragraph)—probably because the engineers had other features to develop. As to your problem, I don't have time to run a test. However, based on my previous testing and knowledge of pages 34-45 of the Retrospect Mac 17 User's Guide—which are essentially a copy of a Knowledge Base article, backing up to a Storage Group creates a component Media Set—if it doesn't already exist in the Storage Group—for each combination of source machine and drive. I'd guess that it also creates a component Media Set for a Favorite Folder on a source drive that is used as a Backup source. I suspect you have or had such a Favorite Folder, and it is or was for the Users/jrubin folder on your Macintosh HD. It sounds as if that directory was deleted on the Macintosh HD disk—or its physical Catalog was deleted in the "Main Backup Media Set A" Catalog folder, without deleting its component Media Set within "Main Backup Media Set A"—which you can't do in the half-baked Storage Group GUI. OTOH it's possible Retrospect Mac 17.0.2 has a bug when it tries to compress a Storage Group containing a component Media Set created from a Favorite Folder. Here's why and how to file a Support Case for a bug, although it could also be formulated as a feature request for fully-baking the Storage Group GUI. BTW, if you don't like getting -1101 Backup errors for your Backblaze.bzpkg files, you can create a Custom Rule (pages 176–179 of the UG) that excludes them from your Backup scripts. This Ask Different thread recommends doing the equivalent exclusion from Time Machine backups. P.S.: I did eventually run a couple of tests, and it looks as if you manually deleted something. Both my tests were of backing up an old HDD locally installed on my "backup server", to a testing Storage Group whose members are in the spare space on my "backup server"'s boot SSD. I don't normally back up that HDD, but I do keep my Catalogs on it and back up the Favorite Folder containing them once a week. My first Recycle backup run check-marked both the HDD as a whole and the Favorite Folder as Sources. As I predicted in the third paragraph of this post, the first run created two component Media Sets—one for the entire HDD and one for the Favorite Folder. My second Recycle backup run check-marked as a Source only the HDD as a whole, not the Favorite Folder. Both script runs were successful; the second run Recycled only the component Media Set for the HDD as a whole.
×