Jump to content

All Activity

This stream auto-updates     

  1. Last week
  2. 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.
  3. 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.
  4. So, we now have these storage groups that function like a collection of mini-sets and mini-catalogs, with each client or source getting a mini-set/catalog. When I have to repair or rebuild a set on any of my consulting clients' Retrospect installations (WAY more often than I should if I had a truly reliable backup program IMHO), I see the individual "mini-sets" getting scanned and rebuilt. Is there a way to trigger a repair or rebuild for an individual source in a storage group? Right now I've got a client that isn't backing up due to a "chunk checksum (-641)" error. I'm so tired of rebuilding multi-terabyte backup sets that I really don't want to have to put everything on hold yet again while this 5TB disk is scanned and the catalog rebuilt. Since each source appears to have its own, self-contained catalog and folder of band files on the backup disk, couldn't Retrospect just rebuild the individual source whose catalog has failed? Thx, Fred
  5. 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.
  6. No, not in the "Summary" pane. Try the "Options" pane. Also try what I wrote in a previous reply.
  7. The Properties dialog for a backup set does not allow changes to the catalog file location:
  8. Possible dumb question. Have you tried to change the location of the backup set using the Properties of that backup set, of course, while that backup set is not in use.
  9. x509

    Curious (spurious?) verify error?

    David, (catching up a bit here). DNG is a photo format introduced by Adobe. It's different from other "RAW" photo file formats in that it is OK for an application to write metadata into the DNG. The best practice for other photo RAW formats, such as Canon's CR2 and Nikon's NEF, is to never write any metadata into these files, except date corrections. Otherwise, there is the real risk that some photo editors may not be able to read a CR2 or NEF file. So whatever happened with the OP's situation, metadata isn't the issue. Phil Burton
  10. I think (not sure) that you should double-click the catalog file (in Windows Explorer) while the backup is NOT running.
  11. OK, so I moved the catalog file to the desired location, then ran the backup script. It asked me "Where is the Catalog File for " the backup set. When I navigated to the new location and selected the catalog file it says "File Not Found" If I select the parent directory of the catalog file instead it says "The name is not valid" I see other messages in the forum about this problem in the context of attempting a disaster recovery restore... this does not inspire confidence that DR will actually work. Why does it not accept the new location of the catalog file?
  12. Retrospect 16.6.0.133 Given an existing backup set, is it possible to change the location where the catalog file is written? I have a Disaster Recovery backup for my C:\ drive that writes its catalog into a directory on D:\ and I'd like to change it to put the catalog on the same disk as the backup set itself. Can I alter the backup set? I don't see a way to do this from the "Properties" dialog.
  13. jhg

    Curious (spurious?) verify error?

    @DavidHertzberg no, I never alter the settings, this is from a standard archive script I run regularly. @x509 no, I don't run the archive while Lightroom is running... although it's conceivable I accidentally left Lightroom in the background during an archive run. Since the file on disk compares correctly with the restored copy, and chkdsk /r on the drive turns up no errors, I'm not going to worry about this one.
  14. 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.
  15. Earlier
  16. The same problem recurred today after several weeks using these scripts without a hitch. I submitted a support case. Addendum: I received a response from support. Hopefully this will fix it and I'm posting here in case anyone else has a similar problem.
  17. David, Many thanks for your help. It took a while to rebuild, but the next backup ran perfectly after. Good Health to you, -Andre
  18. Thanks, David, I will do that. The odd thing is, I sent out instructions (with sequentially numbered pubkey.dat files) to four of our developers, just to see. Two of their laptops backed up - once. Two other developer laptops have not been. My laptop started a second backup, but seems to have made very slow progress. (Started yesterday at 6:15 PM, still running, so it says, now on "building the snapshot.") For all five of these scripts, I did not check the "remote backup clients" tag on the Scripts/Sources tab, but I did check the one I created in the Sources/Tags tab. I may wait till Monday to submit the request, as our Proactive scripts are set to run M-F, so perhaps more will "be found" and run after early Monday morning.
  19. 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.
  20. 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.
  21. Shade Tek, If you actually submitted a Support Case for an enhancement, you got your wish with Restore Preflight in Retrospect Windows 17.0.
  22. barup, If you actually submitted a Support Case for an enhancement, you got your wish with Restore Preflight in Retrospect Mac 17.0.
  23. Background: I have 2 Synology NAS's, one that is strictly the storage for my media (photo) files, the other is the main backup destination for the media drive as well as other local drives in my system. For reasons unknown, no software changes of any kind made in over a year, the media NAS began to experience errors and crash when Retrospect (v 15.6.1 for Mac) ran its daily backup script. Synology support suggested changing the mounting of the media NAS from AFP to SMB. I did this and it seemed to fix whatever issue was at play with the media NAS crashing. I had to add the SMB media NAS share to my Retrospect backup script, which regarded it of course as a "new" drive and began to back it up in its entirety. During this process I discovered that due to operator error on my part the grooming options on the backup NAS hadn't been enabled and it began to run out of space. Retrospect prompted me mid-backup to add a new member to the Media Set that formerly consisted of the backup NAS only. I selected a local disk drive as a stopgap measure. After the backup was complete I enabled the grooming options on the backup NAS so that it should not run out of space in the future. The issue that I now find is that I need to remove the disk drive I added as a stopgap, and can't find any way to do so. I've looked through the manual, adding a member to a storage set is covered, removing a member is not. I've marked the stopgap drive as "lost" within Retrospect, but now the Activity pane shows each daily backup with a red 'x' for an execution error because of this. I have to look at each days' backup log to determine that the only error is the lost drive and nothing more, ideally I'd like to return to each backup pass being reported with the green check so that any real errors stand out and a quick glance at the Activity pane is all that's required. Is there a way to accomplish this without losing the groomed backups already present on the backup NAS? I don't have enough local storage to temporarily cache the backup NAS (~9.6TB) nor the media NAS (3.7TB) so need an in-place solution if possible. Thank you in advance, Andre (Retrospect 15.6.1 for Mac, MacOS 10.14.6 [Mojave])
  24. What with the coronavirus and all, many in my office are working from home these days. We have been using Retrospect (version 16.5, Mac) for some time now. I set up remote backup according to the directions at https://www.retrospect.com/en/support/kb/how_to_set_up_remote_backup. Rather than uninstalling and reinstalling with the server.txt and pubkey.dat files in the installer, I simply placed those files where they were supposed to go on my laptop, created a Remote Backup Clients tag on the server, and tagged one script (my own) with that tag. The script backed up my laptop remotely with no issues. Adding others, however, now has me concerned. I planned to send the server.txt and pubkey file (now renamed pubkey1.dat; it seems like they are supposed to be named sequentially, perhaps?) to another user and have him test it, but I added him and a couple of others to the Remote Backup Clients tag on the server prior to him placing the files on his client, to get a head start. One of the scripts I tagged as remote began to run, under my script. I stopped it immediately and removed all the remote backup client tags other than the one. I went back to the docs, and it doesn't make clear how you are supposed to do set up more than one. The image in the doc shows one script, labeled Remote Computers, with what looks like one source. Are my remote computers supposed to somehow be grouped into one script? That seems odd. Or can I label each individual proactive script as a member of the Remote Backup Clients tag, and if so, what do I need to do to make sure they are differentiated so that my script doesn't pick up someone else's source, as appeared to happen this morning? Is sequential numbering of the pubkey required? If so, do I need to somehow note which source got what number? Or do I just need to not check the remote backup client tag on the server till everything is in place on the individual client? Do I need to uninstall each client and reinstall with the key and server info inserted into the installer? Or is there something else I need to do? Thanks!
  25. 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.
  26. 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?
  27. Looking for any information on the Qualstar Q24 LTO-8 Tape Library. Considering a purchase of this system, but was wondering if anyone had real world experience with this tape library. I'm looking for Pros & Cons concerning the hardware reliability and ease of operation. Any info, good or bad will be much appreciated. Thanks.
  1. Load more activity
×