Jump to content

DavidHertzberg

Members
  • Content count

    1,060
  • Joined

  • Last visited

  • Days Won

    38

Everything posted by DavidHertzberg

  1. oslomike, You're not going to get a response from the head of Retrospect Technical Support by posting here. He lost his phone-answering assistant over a year ago, and is ordinarily too busy to look at these Forums. His post above yours is one of several extraordinary ones, made because several administrators running older versions of Retrospect Mac are reporting this problem. His statement that "no backups should fail to run because of this issue" may only apply to Retrospect Mac 12.5 to 14.6, or it may be entirely wrong. However you could try deleting the schedules for all your scripts, and adding new ones. Please let us know how that works out. If that doesn't work, please read this post to find a suggestion by me.
  2. DavidHertzberg

    Limit Network Scan to IP range.

    PGalati, I'm not a networking expert, since I only have a couple of "client" machines connected by their Ethernet ports to my wired LAN—I don't use WiFi. However, based on a few minutes of reading Galen Gruman's Mac OS X Lion Bible, it looks as if you can separately specify a Mac "client"'s WiFi address from its wired Ethernet address. This would mean that you would have to designate, probably on your router, a separate range of IP addresses that your LAN WiFi would be limited to assigning. You would then, for each "client" Mac, go into its System Preferences->Network and designate a unique fixed IP address that would be used for the "client" machine when it is connected to the Ethernet adapter—an address which would not be in the permissible IP range for WiFi addresses. Once you've done this, you would have to Delete each Client Source from your backup server" Console and re-Add it with its specified Ethernet IP address—and then re-Add those "client" machines back to each of your scripts. If you have Windows "client" machines, yes—I've heard of that OS. In fact I had a Windows 95 desktop "client", forced on me by my employer, on my home LAN from 2001-2004—when I got laid off and returned the Windows machine (being careful to wash my hands afterwards ). While I had it on my home LAN, I backed up that Windows "client" with Retrospect Mac 6. Maybe the two-platform-expert Swedish administrator Lennart_T can tell you what the Windows equivalent of System Preferences->Network is.
  3. Retrospect Mac administrators, Based on the discovery by JamesOakley that "under 15.x for Windows, even Desktop edition gets multiple execution units," I was able to verify that the same is true for "activity threads" under Retrospect Mac 15.0—using the test version Retrospect Tech Support had given me for diagnostic logging of -530 bugs. (I still run production backups using the Retrospect Mac 14.6 "backup server" and the 14.1 Client, because later versions disable my -530 workarounds.) The new feature, of course, is simply a disabling of the Desktop Edition code that previously reset the number of units/threads to 1 every time the Engine was started—thus forcing Desktop Edition to mimic the non-multithreaded Retrospect Windows/Mac 6. However when the Retrospect Inc. engineers corrected Retrospect Windows 15.1 so that "Fixed: Desktop can now reduce its maximum execution units (#7317)", they didn't look at the Retrospect Mac 15 Console. Running Retrospect Mac 15.6.1, if I set General->Preferences Allow n Activity Threads to set n lower than 16, it snaps back to 16 whenever I reboot my "backup server"—thus restarting the Engine. However if I merely quit the Console and then restart it again, that preference stays where I set it. I'll file a Support Case. In the meantime, use this new capability carefully. Make sure that any script you run specifies Activity Thread 1, unless you known darned well that that script can safely run in parallel with any other script that can possibly be running at the same time. Retrospect will not allow you to do more than one Backup with the same Media Set as a destination simultaneously, nor will it allow you to do more than one Backup with the same drive as a source simultaneously—unless different Favorite Folders within the drive are being backed up. However I discovered two years ago that Retrospect will allow you to overlap a Backup script and a Copy of the Backup script's destination, causing a problem—described in the second substantive paragraph of this post—that will continue to exist until the Retrospect engineers add a modest enhancement I proposed in the remainder of that post—an enhancement they have not done yet.
  4. Retrospect Mac administrators, When the Retrospect Inc. engineers corrected Retrospect Windows 15.1 so that "Fixed: Desktop can now reduce its maximum execution units (#7317)", they didn't look at the Retrospect Mac 15 Console. Running Retrospect Mac 15.6.1, if I set General->Preferences Allow n Activity Threads to set n lower than 16, it snaps back to 16 whenever I reboot my "backup server"—thus restarting the Engine. However if I merely quit the Console and then restart it again, that preference stays where I set it. I'll file a Support Case.
  5. bradp015, You fail to understand the overall idea, which is that you will run a Copy Media Set script once and then run a Copy Backup script daily. I don't have time to write a post describing the procedure just for you, but here is a post I made in September 2016 describing a superset of that procedure—one for creating and maintaining a running copy in the cloud of backups to a local Media Set. In steps 1) through 6), ignore anything concerning Grooming or a cloud account—which means you can essentially convert steps 3) and 4) into whatever it takes to set up you new local duplicate-of-the-original Media Set. In both steps 5) and 6), don't check No Verification unless you like living dangerously (cloud providers are supposed to have such error prevention that lengthy-and-expensive verification isn't necessary). Ignore step 7).
  6. bradp015, As to the ""deferred" issue, see this post today by the head of Retrospect Tech Support. As I understand it—including the linked-to Knowledge Base article, the idea is that administrators running Retrospect Mac versions 12.5-14.6 should download the .DMG file linked-to in the KB article and install the 14.6.2 Console from it. It appears that it wouldn't work for the Retrospect Mac 9 Engine, which is what you say you are running. Maybe you can contact Retrospect Sales, and work out a deal to upgrade to Retrospect Mac 12.5 for a lower price than upgrading to 15.6.1.
  7. bradp015, To prevent the "matching" that is slowing down your Copy Media Set script, de-select the Match source files against the Media Set and Don’t add duplicate files to the Media Set options. These are described on pages 113-114 of the Retrospect Mac 10 UG, but are also shown in the dialog on page 155. The Roxio genius who wrote the Retrospect Mac 9 UG evidently didn't want to tire his/her fingers describing these options a second time, so he/she simply referred back to the descriptions for Backup scripts—where the options serve a fundamentally different function. You may want to to select those options for your Copy Backup script; although doing so will slow down your periodic executions of that script—which are likely to take considerably less time. Sorry I forgot to mention de-selecting those options ; it's been nearly 2 years since I experimented with a Copy Media Set script.
  8. DavidHertzberg

    data.appclicks.com DNS

    Retrospect Mac administrators, I was curious to see if this would apply to us, too. So I did a Forums search on "data.appclicks.com", and found this post in a 2013 thread on the subject. Since that thread is in the Mac 9+ Forum, I assumed it would also apply to current Retrospect Mac. So I went looking for the corresponding preference in Retrospect Mac 15.6.1, and found it under Preferences->Console. I've turned off that option, and it stuck through a reboot. If there ever was an appclicks.com website, it doesn't exist now. According to this post, David Lee is still listed on LinkedIn (which I don't subscribe to) as working for Retrospect Inc.; from the evidence he's still Director of Product Management, although he hasn't posted to the Forums since 2015.
  9. boegly, If you read the third paragraph in the OP in this thread, which was the latest one in this Forum before you posted yours, you'll find a link to an older post which may tell you how to solve your problem. I'm going to try that approach now, since I intend to try to revert to Retrospect Mac 14.6.0.
  10. DavidHertzberg

    data.appclicks.com DNS

    bstaud, The first thing I suggest is that you sign up for the Retrospect Management Console. It's currently no-cost, and nobody from the Retrospect Inc. Police is going to come around and force you to look at it. Installing the Management Console may give data.appclicks.com the IP it wants. The second thing I suggest is that you create a Support Request, to let the Retrospect Inc. engineers know that this is another bug they need to fix. Here's why and how to do it.
  11. bradp015, I'm sorry my latest suggestion didn't work. It looks as if the name of the Media Set may be coded into each .rdb file in the 1-SFA 3SAFE folder. I'll skip trying to debug or work around that problem, and go straight to an easy-to-use-on-a-continuing-basis version of your COPY alternative. The basic idea is that, once you do a single Copy Media Set run, which may take 15 hours for you, you can keep two Media Sets in sync by doing routine Copy Backup runs—which will take much less time. The idea is most succinctly described in the "Create synthetic full backups" paragraph in this Wikipedia article subsection (think Media Set whenever you see "archive file"; another editor forced DovidBenAvraham to use the latter term because it is application-independent). Based on what you have previously written in this thread about safety, I think you will want to use your single external OWC drive for the Media Set that is the destination for your Backup script runs—and then do Copy script runs with that Media Set as the source and a differently-named Media Set on your RAID drive as the destination. Copy Media Set is described (including an intro) on pages 153-155 of the Retrospect Mac 10 User's Guide. Copy Backup is described on pages 156-158 of that same UG (somebody at Roxio made a mistake and left the Copy Backup section out of the Table of Contents for that UG version). A word of caution: If you are running any Server version of Retrospect Mac, or if you upgrade to the Desktop or Solo Edition of Retrospect Mac 15, make sure your Backup and Copy scripts are running in the same "activity thread"; activity threads are discussed on pages 121 and 179 and 252 of that same UG. I found out nearly two years ago from the head of Retrospect Technical Support, after I ran an experiment overlapping a Copy Media Set script run with a Backup script run, that Copy scripts use the Catalog File—which is only updated at the end of a Backup script run. I then made a Product Suggestion—both in a thread and in a Support Request—that would allow overlapping without omitting copying of the latest files backed up, but Retrospect Inc. has not acted upon that suggestion.
  12. DavidHertzberg

    data.appclicks.com DNS

    bstaud, What also may help is, per the appropriate section of this Knowledge Base article, to make sure that you don't have Enable Management Console checked or anything else set in that Preferences -> Management dialog. IMHO what you really need is what I suggested in the last paragraph of this post.
  13. DavidHertzberg

    data.appclicks.com DNS

    bstaud, Lennart_T failed to notice that the 2013 post was in the Retrospect 9 or higher for Macintosh forum. Retrospect Mac has had a separate Console program since early 2009, but Retrospect Windows was unable to add that facility for reasons briefly explained in the last sentence of the first paragraph here. What may help is to look in the Secret Preferences dialog, opened as described for Retrospect Windows (not the Client) in this KB article section. That article was last updated in March 2015, so what you see may be different for Retrospect Windows 15.6.1.
  14. pwbimm, In Sources, select the "client" machine and click on the Options tab. Under Volumes on the dialog there's a dropdown labeled "Back Up:". Set that to Selected Sources, and check-mark the Macintosh HD you think you want to back up. Alternatively, set the dropdown to Startup Volume. Look in the Console at a Backup script while it's running to see if you're backing up the correct Macintosh HD. I encountered the same problem when I started to backup my MacBook Pro running macOS 10.12.6 Sierra using Retrospect Mac 14.6.0. Adding the MBP as a "client" defaulted to All Volumes in the dropdown, and one of the two volumes is a garbage-named volume which the Engine can't find. I submitted a Support Case about this, but Retrospect Tech Support replied that the garbage-named volume is Apple's fault.
  15. bradp015, I made a mistake in my preceding instructions, by not properly considering what would happen if you Added a Media Set named SFA 3SAFE—in which case Retrospect Mac would automatically prompt you to add a folder named 1-SFA 3SAFE in a way that would be difficult to bypass. However I made a bigger mistake by not realizing that, as shown by your casual disregard of the terminology in effect since Retrospect Mac 9 was released in 2011, your ability to improvise exceeds your ability to carefully read the Retrospect Mac 10 UG. First, make sure that there is nothing underneath the 4T HD -> SFA 3SAFE 4t 111116 -> Retrospect folder on your single external drive 4T HD. That assumes you have previously moved or copied the 1-SFA 3SAFE folder containing the files with names ending in .rdb to underneath the 4T HD -> SFA 3SAFE -> Retrospect -> SFA 3SAFE folder you created . Second, Add a new Media Set named SFA 3SAFE, with its catalog in the default location root -> Library -> Application Support -> Retrospect -> Catalogs. If there's already a Media Set with that name, use the Finder to delete it and repeat the Add. When Retrospect automatically prompts you to add the first member to a Disk Media Set, per the dialog on page 102 of the Retrospect Mac 10 UG, specify the location 4T HD -> SFA 3SAFE 4t 111116. Don't worry, it will take into account the fact that the Retrospect folder is already there. This should give you a 4T HD -> SFA 3SAFE 4t 111116 -> Retrospect -> SFA 3SAFE -> 1-SFA 3SAFE folder with nothing in it. Third, copy the the 1-SFA 3SAFE folder containing the files with names ending in .rdb from underneath the 4T HD -> SFA 3SAFE -> Retrospect -> SFA 3SAFE folder you created within the SFA 3SAFE folder into the 4T HD -> SFA 3SAFE 4t 111116 -> Retrospect -> SFA 3SAFE folder. The Finder will ask if you want to replace the existing folder (which has nothing in it); do so. Fourth, to be on the safe side , follow the instructions starting on page 213 of the Retrospect Mac 10 UG to Rebuild the Media Set named SFA 3SAFE. In step 4 on page 214, navigate to the 4T HD -> SFA 3SAFE 4t 111116 -> Retrospect -> SFA 3SAFE -> 1-SFA 3SAFE folder. Then do steps 5 and 6, and skip step 7. Finally click the Rebuild button, letting the catalog location default to root -> Library -> Application Support -> Retrospect -> Catalogs. After the Rebuild completes and is shown as successful, delete your new SFA 3 SAFE folder that is directly underneath 4T HD, which should delete the folders within it. That will include the SFA 3SSAFE catalog folder; it is contrary to the way Retrospect works to put a Media Set catalog on an external drive that also contains the Media Set's Members. P.S.: When Retrospect Windows 7.5 was released in 2006, it added the the Disk type of Backup Set—which allows the Catalog File to be on a different disk from any of the Members. Because transportable disk drives still had low capacity, the assumption was that the transportable disk backup drive would contain only one or more Members instead of an additional slew of other folders and files. That's why, as the dialog on page 102 of the Retrospect Mac 10 UG shows, the Retrospect procedure for adding a Member assumes that its location will be designated as a particular disk drive top-level folder—not a folder below the top level as you have done. Retrospect Mac 9 still works when you do that, but—as you have found out—the complications can be daunting to the administrator.
  16. bradp015, First, on your old single drive, you need to rename the folder inside your Retrospect folder to WhateverItIsSAFE. Then you need to rename the folder inside that to 1-WhateverItIsSAFE. Finally you need to create a new Media Set (only benighted users of Retrospect Windows have Backup Sets, sneer, sneer ) named WhateverItIsSAFE, and add as its first (and I presume only) Member 1-WhateverItIsSAFE on the old single drive. The procedure is described starting on page 99 of the Retrospect Mac 10 User's Guide (I can't cite the equivalent page in the Retrospect Mac 9 UG because that's only an Addendum to the Retrospect Mac 8 UG). If you have already defined a Media Set named WhateverItIsSAFE, you should instead Rebuild it—as described starting on page 213 of the Retrospect Mac 10 UG—and add 1-WhateverItIsSAFE on the old single drive as its first (and I presume only) Member.
  17. DavidHertzberg

    Assertion failure at elem.cpp-1096

    Add an Additional Note to your Support Case, containing links to this post and this post and this post. You could also start a new thread in the Product Suggestions—Windows forum. Fixing reported bugs is a different matter; the Retrospect Inc. engineers have historically been quite slow on that. I think they need a course in modern debugging techniques, since IME their approach is to ask the administrator who reported the bug to run a test version with increased logging.
  18. DavidHertzberg

    Assertion failure at elem.cpp-1096

    sowen222, According to the head of Retrospect Tech Support, "Fast Catalog Rebuild is turned on by default with all Disk Backup Sets. We don't have an option to turn it off/on because it is always enabled." Again according to the same person, "The .session files help Retrospect perform faster catalog rebuilds. We made the changes to help cloud backup users with catalog rebuilds. [new paragraph] Retrospect will read these files during a rebuild process. If you want to perform a through rebuild, you can delete all .session files before catalog rebuild and Retrospect will create new .session files from the original backup set data." I suggest that you file a Support Request, specifying a Feature Request that a Thorough Catalog Rebuild option be added to the "Recreating a Disk Catalog" dialog that is now shown and discussed on pages 453-456 of the Retrospect Windows 15 User's Guide. That option would delete all existing .session files and create new ones. The code for doing that used to be the default for the operation up until Retrospect Windows 11. 
  19. DavidHertzberg

    Assertion failure at elem.cpp-1096

    A search of the Forums doesn't show a report of an assertion with this particular number. Here's why and how to file a Support Request. If you just upgraded to Retrospect Windows 15 you may be entitled to personalized phone support, but I understand the European Retrospect Tech Support representative doesn't know very much.
  20. Cabling my "backup server" directly to the MoCA adapter in my bedroom, which I mentioned I had done at the end of the second paragraph here, resulted in a -530 Bug 2 scenario when I booted the Mac Pro "backup server" four hours after the scheduled time for the daily Backup of my MacBook Pro this morning. That means both the "sacrificial" NoOp script and the "real" Backup script failed with -530 errors. I was then able to do a two-second Locate of my MBP, and run the "real" script manually. I have accordingly just re-connected my bedroom MoCA adapter to my Mac Pro through the 5-port 1Gbps Ethernet switch in my bedroom.
  21. 1. It did, but Multicast also did that. 2. Yes, of course. 3. As per above, when run 2 hours past the scheduled time, the "sacrificial" NoOp script failed within a few seconds with a -530 error, and immediately after that—with no manual intervention—the "real" Backup script ran fine. This is the -530 Bug 1 scenario, as I have named it, which has occurred frequently since early February 2017. 4. I followed those steps nearly two years ago. The only exception is that "Make sure the client has the most recent version of the Retrospect client software" no longer applies, because—as I stated above—going more recent than the Retrospect Mac Client 14.1 makes the "real" Backup script also fail with a -530 error—an intermittent situation which I have named -530 Bug 2. 5. As stated in the preceding paragraphs of this post.
  22. henry-in-florida, Unfortunately it's not "very old news" when it affects what we can discuss in these Forums. I suggest you read the last two substantial paragraphs in that same post I linked to concerning the person who is the head of Retrospect Technical Support. I only have one router in my LAN, and that is my Verizon-provided Quantum FiOS "gateway". That router is directly connected to a full-up 8-port 1Gbps Ethernet switch in my study. That switch is in turn connected to a MoCA 2.0 adapter, which via a length of coax cable is connected to an identical MoCA adapter in my bedroom. Until a few minutes ago the adapter in the bedroom was connected to a 5-port 1Gbps Ethernet switch, but only one of the ports on that switch is in active use—connected to my Mac Pro "backup server". In order to eliminate a possible source of timing delay, I have just now cabled the "backup server" directly to the MoCA adapter in the bedroom. It works fine for a test NoOp backup; we'll see whether it makes any difference in eliminating the -530 error I got for the "sacrificial" NoOp script run two hours after its scheduled time early this morning (the "real" backup script scheduled directly after it ran fine). My LAN is totally wired. A few months ago I tried running a "real" Backup script via 802.11g (the fastest speed the wireless built into my old Mac Pro supports). It ran at around 20% of the normal speed, probably partly slowed down by the three layers of sheetrock and one concrete column between my router (a DSL one at the time) and the Mac Pro.
  23. henry-in-florida, First, the person you mentioned in the first sentence of your post immediately above has for years been the head of Retrospect Technical Support—not the head of Sales unless there has been an unannounced management upheaval. He's worked in T.S. since 1994 (and still will until at least Wednesday according to this announcement), and lived through the "near-death employment experience" I discussed in the first substantive paragraph of this post. As I discussed in the second substantive paragraph of that same post, he's IMHO a prime example of "Retrospect Inc. PTSD"—so for the last year or so I've had a policy of never mentioning his name on the Forums (because I'm convinced he does a daily search of the Forums looking for a mention of his name in a post by me). Nevertheless he's a good man doing a very difficult job, and I admire him even though I think 24 years in T.S. have made him just the least bit crabby. My intermittent -530 error problem has endured through two MacBook Pros and two pairs of Ethernet switches, so it's not a simple hardware problem. My best guess is that it's related to the fact that the switch in my study—where my two "clients" are located—and the switch in my bedroom—where my "backup server" is located—are connected via an installed-when-the-apartment-was-built stretch of coax cable with a MoCA adapter at each end. I'd love to replace that with a stretch of Cat5e Ethernet cable, but I couldn't do that without either tearing up an interior hallway floor or running a 100-foot-long Cat5e cable just underneath the ceiling of 3 sides of that hallway. At a cost of $120 I replaced the MoCA 1.1 adapters with MoCA 2.0 adapters about 6 months ago, but that doesn't make any difference. IMHO there's a bug in the Retrospect Multicast code that makes it vulnerable to timing delays, particularly when the "backup server" has just been booted and immediately needs to run a scheduled script. I even started a thread about that on the Ars Technica Networking forum, but nobody had an answer.
  24. henry-in-florida, First, sorry for misreading your second post in this thread. I saw "The only relevant IP's are clients at .70, .64 (TWO CLIENTS), .86 (the Server)", and thought you were saying you had two clients at .64. Second, thanks for probably solving a problem I have had for nearly two years with -530 errors on Backup script runs. I wasn't having any problems with Adding my two Mac clients, but I have been intermittently getting -530 errors for the first client (a MacBook Pro) when I run scheduled daily scripts that back it up. My closest approach to a remedy has been to schedule a "NoOp" script 5 minutes before the "real" script; the "NoOp" script is a duplicate of the "real" script that adds the No Files rule. Because the -530 errors are intermittent—indicating IMHO that the error is hardware-related, sometimes the "NoOp" script immediately gets an error but the "real" script runs OK, sometimes both scripts run OK—especially when both my "backup server" and my MBP client are booted before the scheduled time for the "NoOp" script, and sometimes the "NoOp" script sits there past 3 minutes trying to Find the MBP. My cure in the latter case is to Pause the "NoOp" script, do a Locate—which always works—of the MBP, and then do a Stop of the "NoOp" script; at that point the "real" script always starts and runs OK. I long ago submitted a Support Request for this problem, and twice Retrospect Tech Support has given me test versions with extra logging so that I can help the engineers find the bug. I am permanently stuck running the Retrospect Mac 14.6.0 Engine and Console and the 14.1 Client, because the test versions indicated that engineering had introduced a "fix" in 14.6.1 that actually made the problem worse. I'd like to be able to upgrade to Retrospect Mac 16 next spring so I can upgrade my Mac Pro "backup server" and MBP "client" to macOS 10.14 Mojave to get the benefits of APFS; maybe switching from Multicast to Subnet Broadcast—which I have just done—will enable me to do that. If Subnet Broadcast makes my intermittent -530 errors go away, that would be IMHO a sad day for Retrospect Inc. unless Retrospect 16.0 introduces an explicit fix for Multicast. If the fix isn't in Retrospect 16, Retrospect Inc. will have to distribute a very-prominent document (for Retrospect Windows, too, because some administrators have reported -530 errors with that variant) that says "Don't add your 'clients' with Multicast anymore, because it creates errors for some administrators. Instead use Subnet Broadcast; we know it's going to be tougher for you to learn how to do that but you're stuck with it." I don't think that will ease Tech Support's workload; quite the contrary, since they may have to process additional product returns from disgruntled customers.
  25. bradp015 got an answer by first making this post in the Server, SBS and Multi Server forum. His Retrospect Mac 9 success report, including methodology, is 2 posts below it.
×