Jump to content

DavidHertzberg

Members
  • Content count

    1,136
  • Joined

  • Last visited

  • Days Won

    39

DavidHertzberg last won the day on January 9

DavidHertzberg had the most liked content!

Community Reputation

63 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,911 profile views
  1. DavidHertzberg

    Setting Up Remote Backup

    Alanna and other administrators of installations scared of SARS-CoV-2 (the virus that produces COVID-19 infections), This second of two posts deals with your OP-implied requirement to have a separate ProactiveAI script for each subset of office-mates working from home. If you want a separate script for each subset of Remote Backup "client" machines so that the subset of machines can be backed up in parallel with other subsets of Remote Backup "client" machines, I'm afraid you are Sh*t Out of Luck with Retrospect Mac 17.0—as evidenced by your OP. You'd want to have more than one ProactiveAI script using Remote Backup running in parallel if you can't back up all Remote Backup "clients" with the desired frequency and within the time-frame they are accessible to the "backup server". Let's assume that each such "client" takes 0.5 hours to back up, and you want to back up each such "client" daily. That assumption puts a limit of 48 "clients" that can be backed up with a single Remote Backup script, even if all such "clients" are connected to the Internet 24 hours per day. (That my assumption is not unreasonable is borne out by the fact that my 2016 MacBook Pro takes about 0.5 hours for a No Media Action backup, even though its connection to my Mac Pro "backup server" is over an in-the-apartment MoCA cable connection.) The remainder of this post is informed speculation as to why you can't have more than one ProactiveAI script using Retrospect Mac 17.0 Remote Backup, based on my reading of this sub-Appendix of the Retrospect Mac 17 User's Guide, which seems to be an updating—to incorporate Automatic Onboarding on Retrospect Management Console— of this 2018 Knowledge Base article. Other administrators should feel free to add posts to this thread correcting any part of my speculation that they believe is incorrect. The reason you're SOL is a kludge in the 2018 design of Remote Backup: Every "client" machine that is a candidate for Remote Backup must have the Tag "Remote Backup Clients", either assigned automatically by checking the "backup server" Preferences->Clients checkbox "Automatically add clients using public keys" or assigned manually in Sources—as you did. Any ProactiveAI script that does Remote Backup must have that exact Tag "Remote Backup Clients" as a source. So any ProactiveAI script that does Remote Backup is going to back up all such sources. Since a particular Retrospect script is not multi-threaded (because it is executed within a particular Activity Thread), all those "Remote Backup Clients" will be backed up one-by-one. IMHO the kludge was introduced with Remote Backup in 2018 because the original customer use case for Remote Backup was for—e.g.—a company with its main offices in Britain that has a few salespeople such as Sally in Shanghai and Albert in Adelaide, each of whom has files on his/her laptop that the company's backup administrator wants to be sure are backed up on a "backup server" running 24/7 in Britain. Since Sally and Albert are in different time-zones from each other, they're presumed not to have their laptops connected to the Internet at the same time, and since the company has only a few such remotely-located salespeople, it's OK to back them up via a single ProactiveAI script. As you can see, that kludge creates problems when a massive number of employees in the same time-zone start working from home because of COVID-19. IMHO what you should do, Alanna, is to submit a Support Case for a feature request that would treat a manually-defined Tag that has the prefix "Remote Backup Clients" as indicating it is eligible for Remote Backup with a script that specifies a Tag with that prefix. Thus an administrator could manually define the Tag "Remote Backup Clients A", and create a ProactiveAI script specifying "Remote Backup Clients A" as a Source that backs up only those "client" machines defined with that particular full Tag. Here's why and how to submit a Support Case for a feature request. BTW, I received an e-mail today inviting me to attend a 30-minute webinar on using Retrospect Backup to protect desktops and laptops for remote employees. The e-mail includes the following paragraph: I was surprised to find that a preceding sub-Appendix in the latest version of the Retrospect Mac 17 UG discusses VPN Backup, even though the cumulative Release Notes through 17.0 do not mention that feature. Either this has been a "seekrit" feature until now, or someone in Product Management "jumped the gun" in documentation for a soon-to-be-released 17.1. VPN Backup has the same kludge as Remote Backup, except that the literal Tag is "Automatically Added Clients" instead of "Remote Backup Clients". A problem with Retrospect backup over a VPN was mentioned most recently in this 2017 post by the highly-experienced Lennart_T; my Verizon-provided FiOS router (I don't run a firewall) does not allow Internet port forwarding to port 497. P.S.: The main difference of the UG sub-Appendix on Remote Backup from the KB article is that the "updating" describes the use of Automatic Onboarding, which requires the Management Console Add-On. That boosts Retrospect's price (minus ASM) by 30% to 20%, depending on Edition. Color me cynical.☹️ P.P.S.: At the webinar the head of North American Sales, who was giving an introduction for the head of Tech Support's presentation, said there will be a new release "within a couple of weeks". The release will be mainly bug fixes, but may include a few new features. I submitted slightly-shortened versions of the 2nd, 4th, 6th, and 8th paragraphs of this post as "questions". Of course they didn't get answered during the webinar—which lasted an hour and only skirted VPN Backup, but the head of North American Sales phoned me back afterwards—I urged him to get the kludge fixed as part of that release.
  2. fredturner, Not, as far as I can determine, directly in Retrospect Mac 16.6 (which I'm still using) or 17.0. Here's why and how to create a Support Case for a feature request. Make sure you mention that you're a "Partner", meaning a consultant; evidently Retrospect Product Management loves "Partners". You could indirectly fix a particular problem via a four-step process, somewhat per the fourth substantive paragraph in this post. First, do a Copy Media Set of the the Storage Group to a new Media Set—using a Rule that Includes only the particular Source Host and Volume whose backup had the -641 error. Second, do a Groom of the Storage Group—using a Rule that Excludes the particular Source Host and Volume whose backup had the -641 error. Third, do a Copy Media Set of the new Media Set back to the Storage Group—using a Rule that Excludes the date of the backup when the -641 error occurred. Fourth, do a No Media Action backup of the Source Host and Volume whose backup had the -641 error to the Storage Set—which IMHO should back up the files that were excluded in the third step. Note that I have not tested this process. Also note that the four-step-process may take longer than doing a Rebuild of the Storage Set; it certainly involves more manual effort.
  3. jhg, What you need to do is Recreate the catalog file on D:\ from its D:\ Member. The most recent time I did this was last Friday on my "backup server" 2010 Mac Pro (that can have up to 4 internal drives), which normally boots from an internal SSD but where I keep the catalog files on an old internal HDD (in case I have to revert to a previous version of Retrospect Mac). I was experimenting with creating a Storage Group—a container for multiple Backup Sets that is not relevant to this discussion—and I carelessly let Retrospect Mac 16 default to creating the catalog file for the misnamed "Media Set Groupie" (I thought I should have "Media Set" instead of "Storage Group" as the lead part of the name) on the SSD. I didn't discuss it in the second substantive paragraph of this post, but to fix my carelessness I did the Retrospect Mac 16 equivalent of what is described on pages 456-458 of the Retrospect Windows 16 User's Guide. That description was primarily written for a Backup Set with removable-disk Members, but it is also applicable to a Backup Set with HDD Members. Your Backup Set has only one HDD Member, to which you will almost certainly have to navigate inside the "Retrospect" folder on your D:\ drive in steps 5 and 6. I recommend you put the new catalog file someplace outside the D:\Retrospect folder, but you probably can get away with putting it inside D:\Retrospect. When the Recreate is finished and you have tested it with a script edited per page 458, save disk space by deleting the old catalog file on your C:\ drive.
  4. DavidHertzberg

    Setting Up Remote Backup

    Alanna and other administrators of installations scared of SARS-CoV-2 (the virus that produces COVID-19 infections), This first of two posts deals with your OP-expressed desire to have a separate ProactiveAI script for each subset of office-mates working from home. If you want a separate script for each subset of "client" machines so that the subset can be backed up to a different destination, there is an answer given over the phone to me by the North American head of Retrospect Sales on Thursday—a Storage Group destination. I upgraded my Retrospect Mac "backup server" from 16.1 to 16.6 Thursday evening and created a Storage Group, whose single member is on the spare space on on the portable HDD I was going to be recycling Saturday morning. The Storage Group is named "Media Set Groupie" (I thought I should have "Media Set" instead of "Storage Group" as lead part of the name), which caused a folder with that name to be created on the portable HDD. Inside that folder is a zero-byte marker file named "storagegroup". I then ran a Recycle Backup script (I don't do Proactive), whose source was the Macintosh HD on my "client" machine "David's MacBook Pro", and whose destination was that Storage Group. This created an empty inner folder named "1-Media Set Groupie", and another—when I ran the Backup—non-empty folder named "David's MacBook Pro-Macintosh HD". Inside the non-empty folder is another folder named "1-David's MacBook Pro-Macintosh HD", which contains the usual .rdb files and .session file. (The reason for the preceding paragraph is that the Retrospect "engineers" who wrote this Knowledge Base article illustrated it with screenshots of the GUI from their Retrospect Windows alpha-test runs; for 30 years they couldn't arrange adequate beta-testing. Those showed the names of their at-home machines and volumes, which for seeming security reasons they obscured with the digital equivalent of Magic Marker in the screenshots. So the KB article doesn't visibly make it clear that a Storage Group is merely a container for a Backup Set (Retrospect Windows' term for Media Set) for each client-volume backed up, and maybe there's a California law against publishing a screenshot of a folder 🤣 showing what's described in my above paragraph—which would be needed to show what the Retrospect Mac "backup server" does because its GUI has less detail than Retrospect Windows' GUI.) On Friday I ran a Copy Media Set script, copying "Media Set Groupie" (per the KB article, "For transfer in Retrospect for Mac, a Storage Group can be treated like a media set")—meaning "1-David's MacBook Pro-Macintosh HD"—to a Media Set in spare space on the portable HDD whose last daily backup was Friday morning—which I then put in my bank safe deposit box. So, using Copy Media Set with a Rule (p.169) that Includes only a particular Source Host, you can get beyond the Storage Group limitation that Member-n-for-every-component-Media-Set (i.e., where n=1, "1-clientname-drivename") must fit—even when Recycled—onto the same destination volume. You should upgrade to Retrospect 16.6, because that point release fixes most of the Storage Group bugs.
  5. DavidHertzberg

    Setting Up Remote Backup

    Alanna, With regard to the use of Tags in Remote Backup, you are first of all the victim of inadequate documentation. On pages 40-41 of the Retrospect Mac 16 User's Guide, there is an explanation of manually-created Tags. However at the bottom of the list in the Sources tab for a Script you will find disclosure triangles for Tags and Smart Tags. Tags disclose a line for each one you have manually defined per pages 40-41, and you click the checkbox on that line to include the volumes or Favorite Folders you have assigned that particular tag. Smart Tags—which are not defined anywhere in the UG—are automatically populated by the Retrospect "backup engine" (being what I might describe as "smart-as*ed") as you define Sources; in the past they have included All Clients and All Local and All Shares. Evidently Remote Backup Clients is a Smart Tag added as part of the new Remote Backup feature. "ProactiveAI Script" in the Knowledge Base article says But that paragraph assumes you want to backup all those volumes using a single Proactive script. (No doubt, when Product Management added the Remote Backup feature, their vision was that an administrator in London would keep a "backup server" running all the time so that Sally in Shanghai and Alfred in Adelaide would have their machines backed up Proactively whenever those machine connected to the Web.) But, as you say in the OP, that's not what you want to do. What you need is a way of defining a non-Smart Tag for a particular public-private keypair, so you can use that non-Smart Tag in a Proactive script instead of Remote Backup Clients. Unfortunately I don't know what that way is. Therefore what you need to do is to create a Support Case for a feature request. Here's why and how to do that.
  6. DavidHertzberg

    How to remove a Media Set member?

    ByTheC, I believe you need to Rebuild the Catalog for the Media Set, as described on pages 182-184 of the Retrospect Mac 15 User's Guide. In steps 4-6, Add Member only for the Member on the backup NAS. In step 7, if you specify the Catalog location to where it already exists, IIRC you will get an error message saying a Catalog file with the same name already exists there. If you get an error message, Finder-copy the existing Catalog file someplace else for safe-keeping, then Finder-delete the existing Catalog and repeat all steps of the Rebuild procedure.
  7. Shade Tek, If you actually submitted a Support Case for an enhancement, you got your wish with Restore Preflight in Retrospect Windows 17.0.
  8. barup, If you actually submitted a Support Case for an enhancement, you got your wish with Restore Preflight in Retrospect Mac 17.0.
  9. DavidHertzberg

    Qualstar Tape Library

    khudson, Here's the one post on the Forums that mentions a Qualstar LTO library, although an older one than the Q24. That post was about slowness of Retrospect Windows Server in backing up two drives simultaneously, but never mentioned any problem with the Qualstar RLS - 8350 LTO 6 library itself. rafi went on to immediately make other posts, which were related to using Retrospect Mac Clients with a Retrospect Windows "backup server". Unfortunately rafi was allergic to supplying further information by making any second post in the same thread.
  10. DavidHertzberg

    Qualstar Tape Library

    khudson, Almost all the Forums posts for Qualstar have to do with AIT drives, and are quite old. How about telling Qualstar "put your money where your mouth is", meaning guarantee in writing to refund what you paid for the Q24—and at least a couple of LTO-8 tapes—if it doesn't work with Retrospect for a 90-day trial period? BTW, you haven't stated either your version of Retrospect Windows or your version of Windows. You also haven't stated whether you want to connect your Q24 with SAS or FC. However thanks for copying your OP to this sub-Forum. Maybe you originally thought "Product Suggestions-Windows" was for suggestions about hardware products to be used with the Retrospect Windows software?
  11. DavidHertzberg

    QualStar Q24 Tape Library

    khudson, Almost all the Forums posts for Qualstar have to do with AIT drives, and are quite old. How about telling Qualstar "put your money where your mouth is", meaning guarantee in writing to refund what you paid for the Q24—and at least a couple of LTO-8 tapes—if it doesn't work with Retrospect for a 90-day trial period? BTW, you haven't stated either your version of Retrospect Windows or your version of Windows. You also haven't stated whether you want to connect your Q24 with SAS or FC. Also, although I hate to be a nitpicker, your OP doesn't state any Product Suggestions. You should have created the thread in the Device and Hardware Compatibility-Windows forum.
  12. DavidHertzberg

    Curious (spurious?) verify error?

    jhg, In regard to the question that Nigel Smith asked, is it possible you backed up that one file again on 8 November 2017 with the Generate MD5 Digests During Backup Operations (page 402 of the Retrospect Windows 17 User's Guide) preference disabled? That way the stored MD5 digest (in the Catalog File for the archive Backup Set) wouldn't match the one generated during the Verify run. If that didn't happen, let's consider the fact that the file in question is a .dng file. The Wikipedia article says DNG "mandates significant use of metadata". I don't know anything about digital photography, but it's possible there's some aspect of the metadata that Retrospect doesn't handle correctly. Is the other file that gives a Verify error also a .dng file? To make Retrospect back up that one file again, first create a Subvolume (pages 420-422 of the UG) for the directory containing that original file. Then create a Backup run from that Subvolume to your archive file, specifying the file name in the Include section of a custom Selector (pages 432-448 of the UG).
  13. DavidHertzberg

    Several Issues with mac Clients

    My suspicion in the second paragraph of this up-thread post turns out to have been misplaced. Per Retrospect Windows 17.0.0 cumulative Release Notes: "Mac Client: Fixed issue where non-English Windows ["backup server"] engine showed main Catalina volume as empty (#8415)". The bug resulted from a different limitation—failure to test non-English variants of "backup server" and Client software— than the one I suspected for Retrospect "Inc." beta testing.
  14. DavidHertzberg

    Retrospect 17: A Cautionary Tale

    amkassir, See the second paragraph in the P.S. in this Windows-Professional post, discussing my guess about the "quickie" nature of the 17.0 release. In the problem you report, I suspect the culprit is a bug in "Configuration Management: Fixed issue with importing certain subvolumes from configs.xml (#7848)". Here's why and how to submit a Support Case for a bug. I urge you to do so, because it must be done by someone who actually has experienced the bug.
  15. DavidHertzberg

    Retrospect 17 Client Connection Popup

    Hofstede, Are you actually using the Web-based Management Console with Retrospect Windows 17.0.0.180? In that case this popup window might be a too-obtrusive byproduct of "New: Dashboard displays status for backup engines". Or are you just using Proactive scripts with Retrospect Windows 17.0.0.180? In that case this popup window might be a too-obtrusive byproduct of "Improved: Client Discovery: Support for per-minute polling". P.S.: Here's a little Version 17.0 "tea leaf reading" by a non-insider, based on the Retrospect Windows 17 User's Guide posted on 5 March—supplementing the Retrospect Windows cumulative Release Notes: IMHO it's significant that the release occurred 3 March in the first week in March, although x.0 releases have usually occurred the second week in March. 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 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 containing the other new features." The 17.0 feature that IMHO will be of major significance to many Retrospect administrators is the "10x Faster Proactive AI" combined with "Client Discovery: Support for per-minute polling". Page 6 of the UG says "Customers with many endpoints offline at various times will see a 10x performance increase in how fast Retrospect Backup finds the next available computer."😃 Hofstede's complaint in the OP would thus be explainable as attempt-to-connect monitoring code someone failed to disable pre-release (forehead-smacking by harried engineers in Walnut Creek no doubt preceded the head of RTS's second post🤣). The 17.0 feature cluster that IMHO will not be of major significance to most Retrospect administrators is "Automatic Onboarding with Retrospect Management Console". This is obviously intended as an attempt to salvage the "go big or go home" strategy I have described elsewhere as an apparent Product Management failure. The only administrators who'd care about Onboarding are either multi-customer consultants or have really big installations (you, Hofstede?), but pages 5-6 of the UG include a link to a KB article that describes the feature—showing Product Management thinks it's saleable.🤨 The 17.0 feature that IMHO may help all Retrospect administrators fight ransomware is "Restore Preflight". UG Page 7: "Retrospect now allows customers to export a ... complete CSV for your [past] backup ... including each file, its metadata, and its backup location and filename or tape." Useful? 🤔
×