Jump to content

DavidHertzberg

Members
  • Content count

    1,105
  • Joined

  • Last visited

  • Days Won

    39

Everything posted by DavidHertzberg

  1. DavidHertzberg

    File compare problem

    tbr00 (at least I can spell your "handle" correctlyđŸ€Ł), Here's an apparently-relevant Forums post I came across a few minutes ago in searching for a solution for someone else's backup problem described on an Ars Technica forum. Its thread—which I suggest you read in its entirety—concerns a Synology NAS instead of a Netgear NAS (can I name non-Drobo brands?). The thread is on the Mac 9+ Forum instead of the Windows Professional Forum, so YMMV—but the underlying Engine is the same even though the UI is different.
  2. DavidHertzberg

    Time machine data not supported?

    Nigel Smith, At this point SunbeamRapier has pretty well solved his/her problem, as described starting with this post in a Product Suggestions-Windows thread he/she hijacked. The solution was a full-fat version of your first suggestion: to first restore the entire TM backup to an external HDD, then to back up that HDD onto a Retrospect Media Set. That Media Set was intended to be a Tape one, but SunbeamRapier was confused by inexperience and created a Disk one instead. IMHO SunbeamRapier is eminently correct; the impossibility of backing up a TimeMachine volume directly with Retrospect should be officially documented.
  3. SunbeamRapier, If you used the Backup Assistant on pages 89-92 of the Retrospect Mac 16 User's Guide, you would have been prompted to create a Media Set destination and would have created one per pages 86-89—which includes specifying a Media Set Type. I'm not going to claim the UI is as simple as TimeMachine's, but I didn't have particular trouble learning it for backing up local disk sources in 2015—"client" machine sources were somewhat more complicated for a couple of installation-specific reasons. However from 1995-2010 I'd used the old UI, a non-multithreaded version of what Retrospect Windows' UI still is. I happen to do a Recycle backup on Saturday mornings that includes a source HDD that is installed inside my 2010 Mac Pro "backup server". The rate for its backup phase is around 2.3GB/minute for source data ("''B' is for bytes 'b' is for bits"), so for 1TB that would take about 7 hours. If you used the Backup Assistant it seems that'd automatically turn on the Thorough Verification option described on page 97; since it is a byte-by-byte comparison, that would add about another 7 hours. So IMHO 17 hours fits into the speed range for Retrospect, considering your source HDD is connected with USB. The product in column 2 of this Retrospect Knowledge Base article gives faster speed at a much higher price. See here for Retrospect backup of TimeMachine backups. Now you can proceed to create a tape Media Set, and then create a Copy Media Set script to copy the disk Media Set set you have already created to that tape Media Set. A Copy Media Set script is described on pages 135-137; it may take a few hours to run, but shouldn't put as much load on your CPU.😁
  4. SunbeamRapier, Where exactly is Retrospect creating your .rdb files? According to this post and the previous discussion in that thread , tapes do not have .rdb files—which are instead in the Catalog File on disk for the tape Media Set. For disk Media Sets, the destination disk files mostly consist of the .rdb files—which are the containers for the backed-up data. If your 2015 Mac Pro is "using everything" creating a Catalog File for upwards of 40 million files, that's probably because doing so eats up all available CPU cycles. If you want to create a Support Case for this feature request, here's why and how to do it. I suspect Tech Support will reply that, when you took your Mac Pro to Europe 3 years ago, you should have installed a copy of Retrospect Desktop on it for use with your portable 4 TB USB HDD, instead of making do with Time Machine. They may also reply that, having failed to do so, you should at least be running your Retrospect backup to tape from your restored TimeMachine disk as a series of script runs—each specifying a non-overlapping Date Modified Within as a Rule or non-overlapping Favorite Folder sources. BTW, I've used Retrospect Mac terminology in this post because your post is blatantly about that variant. It doesn't make any difference, because your complaint is about the underlying Engine—which is the same for both variants. However your complaint has nothing to do with the topic of the preceding posts in this thread; you should have started a new thread in the Product Suggestions-Mac OS X sub-forum—which has a large square green Start New Topic button. To create a link to a post in another thread: right-click the doohicky on the top right of that post that says "Share Link" when you mouse over it, then choose Copy Link Location form the resulting drop-down, then select the text in your own post that you want the link to be in, then click the Link tool in the editing toolbar and paste the copied Link Location into the URL box in the Link dialog.
  5. DavidHertzberg

    Time machine data not supported?

    SunbeamRapier, This was reported as early as this 2009 post. If your 4TB USB portable volume was local to your Mac and was running 12 hours per day for 3 years, that would have been about 13,000 backups. If an average of 3000 files incrementally changed between each of those hourly backups, that would come out close to 40 million TimeMachine files—only the weekly ones would be saved as hard links. If your 4TB USB portable volume was networked to your Mac—which it probably wasn't—you wouldn't be able to back it up with Retrospect, because in that case the TimeMachine backups would be sparse bundles. So buy another 4TB USB portable HDD for around US$100, or borrow one. And just be prepared to leave your Mac running until the restore is done.
  6. DavidHertzberg

    File compare problem

    tbr00, I also think it would aid us in suggesting s solution to your problem if you clarified your Retrospect-related installation configuration. My understanding from what you've said so far is that all your Retrospect "client" machines are Macs, but your "backup server" is a Windows 7 machine that also has a Netgear ReadyNAS. It is the files on the ReadyNAS that are giving "file compare errors"—about which you have so far revealed no further information—when you back them up. You are devoted to whatever data is already backed up to LTO4 tape, but (AFAICT) that generation is so old you can't buy a tape drive that will read it and can be attached to a more-modern machine. You are as devoted to your ReadyNAS server as to the "bunch of olï»żd hardware deviceï»żs", but that server also cannot be moved to a newer machine. Is my understanding essentially correct? P.S.: If you upgraded to Retrospect Windows 16 within the last 30-45 days, you are entitled to personalized assistance from Retrospect Tech Support. If—as I suspect—your "file compare errors" have something to do with your ReadyNAS characteristics, you're going to need that assistance. Here's why and how to file a bug-report Support Case; note that the Support Case will need to reveal to R.T.S. the information you won't reveal to us.
  7. DavidHertzberg

    File compare problem

    tbr00, So, you're going to do a "strip tease" by gradually revealing more information about your problem.đŸ€Ł How about "taking some more off" by actually reproducing the "file compare errors" you are getting—as shown in the logs? That would help us Forums volunteers to figure out what the problem is. It sounds to me as if you are having a problem described in this 2004 thread. See the last three posts in the thread. Is there a recent Windows-7-compatible driver update for your ReadyNAS RAID card? If you are satisfied that your manual compares show the data is being backed up correctly, how about switching to Media Verification—as described on page 354 of the Retrospect Windows 16 User's Guide? Page 459 says "In certain circumstances, Retrospect does not have access to MD5 digests generated during backup. This is true for all backups created using versions of Retrospect prior to Retrospect 16.0, as well as backups that took place when Retrospect’s “Generate MD5 digests during backup operations” preference was disabled." But at worse that means IMHO your data backed up with Retrospect Windows 12 will be backed up again—once.
  8. SunbeamRapier, Forgive me for possibly insulting your intelligence, but do you know that you can't upgrade from Retrospect Mac 12 to Retrospect Mac 16 without paying for a new license code? Here's the Licensing Wizard. If you're only backing up one Mac, and your backup destinations are disks rather than tapes or optical drives, you may only need to pay US$49 (or US$39—it looks like there's a discount in effect) for Retrospect Solo. Here's the Competitive Analysis Knowledge Base article for that edition. P.S.: Whenever I add later information—as opposed to a wording clarification—to a post I have already made, SunbeamRapier, I precede that later information with the centuries-old letter-writing abbreviation "P.S." or "P.P.S." etc.. That lets me add a Reason for Edit. Evidently your generation believes the abbreviation "OK" is equivalent. To which I can't resist replying "OK, boomer".đŸ€Ł Anyway, what you need to do is create a Support Case for the license-key bug; here is why and how to do so. The fifth paragraph of that post says the head of Retrospect Technical Support "has verbally assured me that you don't need to be signed up for ASM to report a bug—only to get personal assistance with coping with it." As far as Australian Retrospect Support being "no help at all", the only thing I dare do is to point you to this post—which describes what happened to me earlier this year when I posted about a similar situation. P.P.S.: In regard to Catalina, you need to read this Knowledge Base article and also this one. Note that the first KB article, in its last multi-sentence paragraph, erroneously links to the Mojave version of the second KB article rather than the Catalina version—which it should have (except that somebody on Retrospect "Inc."'s. august Documentation Committee didn't coordinate what he wrote in the first article with somebody else who was rewriting the second article for Catalina).
  9. DavidHertzberg

    File compare problem

    tbr00, See this post and the ones after it in that thread. Are you using OneDrive? Why are you still on Windows 7, since extended support ended on January 14, 2020?
  10. jhg and everyone else, Two days ago I received, probably like all other Retrospect administrators, a marketing e-mail from Retrospect "Inc.". It announces a new version in March, and says "Not sure if your backups are running? Simply set up an always-on ProactiveAI script, and schedule email notifications to send you a daily summary [my emphases]." IMHO that implies the new version will require having Retrospect.exe running when the summary is scheduled to be e-mailed. In the third paragraph of this post in another thread I reported the head of Retrospect Tech Support's voice-overs. Engineering's aimed at "eventually having Retrospect run as a service with an HTML-based interface". That IMHO implies targeting in 2020 a "browser based" more-recently-introduced client-server backup application analyzed in the second features column of this Retrospect Knowledge Base article. Itemized features include Windows/Linux support.
  11. prl and any other non-ancient Forums members, There appears to be some kind of bug in the Forums software regarding the display of Profiles. Members who did not disable the Recent Visitors "block" display, such as me and Don Lee and kolohe280 (who didn't put anything in his/her Profile but didn't disable its display) and Lindsay Robertson, have their Profile information displayed. Members who did disable the Recent Visitors "block" display, such as prl, don't have their Profile information displayed. Thus I can't see prl's Gender. I'll file a Support Case for the bug.
  12. prl, Your OP observation is that "the correct icon seems to be there initially, but then get overwritten", and the overlaying icon in your OP screenshot looks to my eyes like a distorted version of the correct icon. Therefore I'm speculating that code connected to the icon generates some reaction by Catalina, and that the reaction is what's distorting it. The fact that the changing-facet code isn't executing in System Preferences wouldn't necessarily deter Catalina's reaction, but my speculation implies that the same distortion would occur when the icon is displayed in the Menu Bar of a "client" machine running under Catalina. That's why I asked someone to check this; evidently that someone can't be either you or me. If your preferred personal pronoun is "he", set the Gender item in your Forums Profile to Male—as I did years ago. I know a lot of administrators haven't done that, which is why I always begin my posts with the "handle" of the administrator I'm responding to—whom I then can usually refer to as second-person "you" without my junior-high-school English teachers rolling over in their graves. If I have to use third-person, I check the administrator's Profile.
  13. I noticed a couple of days ago that all my script executions scheduled after 1 January were showing in Activities as "Deferred". I figured this was Retrospect Inc.'s New Year's gift to me, so I looked in the cumulative Retrospect Mac Release Notes. Lo and behold, Under Console for 15.6.0.125 there's "Activities: Fixed issue with scheduled activities showing up as "Deferred" (#7670)" . As we all should know by now, 15.6.0.125 was a "bad release"—so you'll want to download and install the 15.6.1.105 "backup server" instead. I've done this and tested it. It fixes the "Deferred" problem, but I've kept my Mac Client at 14.1. That's because last summer, when—at the request of Retrospect engineering—I ran an extra-logging version of the 15.0 Engine and Client to see if they'd fixed my -530 bugs, that combination of versions actually made my -530 problems worse. So I reverted to 14.6.0 for the Engine and 14.1 for the Client. I should also point out that, at the suggestion of henry-in-florida, I've recently switched the Console Sources definition of my MacBook Pro's Client to using Subnet broadcast instead of Multicast. That seems to have eliminated everything except -530 Bug 1, for which I developed a work-around nearly two years ago. For those who don't want to upgrade, here's an old post to the Mac 8 Forum that describes an alternate way to fix the problem.
  14. prl and anybody else, I'm going to hazard a guess that Catalina has some difficulty displaying the Retrospect icon, possibly because—as the icon is used in the Menu Bar of a Mac running the Retrospect Client—it has the capability of changing the way the facets are displayed at an interval of about one second to show the Retrospect Client is doing work. Maybe the Dantz-written facet-changing code is 32-bit, and therefore doesn't work under Catalina—but messes up the way the icon is displayed in the System Preferences main panel. My impression from looking backward at a few of prl's posts is that he/she is only backing up a single Mac, and therefore is running the Retrospect Engine (and probably Console) directly on it—without using the Retrospect Client. Would someone who uses the Retrospect Mac Client on a machine running under Catalina please check if it still has the capability of changing the way the facets are displayed at an interval of about one second to show the Retrospect Client is doing work? Please do so and post the answer back in this thread. (None of my Macs are running under Catalina.) Once we get that post—and maybe if we don't, prl, here is why and how to submit a Support Case for a bug.
  15. DavidHertzberg

    Several Issues with mac Clients

    Pesetus, Please, as soon as you know whether the 16.6.0.307 update given to you by R.T.S. works or not, notify Retrospect Tech Support. That will be important for other administrators, so the engineers can decide (assuming the update works) whether to release it for Retrospect 16 and/or Retrospect 17. I'm sorry I didn't think to tell you this yesterday. The deadline for a Retrospect 16 bug-fix release is probably 28 February. Please do your follow-up quickly.
  16. DavidHertzberg

    Several Issues with mac Clients

    Pesetus, Thank you for reporting back to us on the Forums. I'm assuming the 16.6.0.307 update given to you by R.T.S. is for the Retrospect Windows "backup server", rather than for the Retrospect Client program on your Mac Catalina "client" machines. That sounds to me as if the engineers had not sufficiently tested the Retrospect Windows 16.6.0.133 "backup server" software with Retrospect Mac 16.5.1.104 Client software on machines running running under Catalina. Running that combination of Retrospect software is a bit unusual—but many mostly-Windows installations also have Macs; obviously the engineers should have tested. The question for the rest of us administrators is whether the engineers will release the 16.6.0.307 update as a new distribution for Retrospect 16, or whether it is merely a test version of the Retrospect Windows 17.0 distribution—which according to past practices ought to come in the second week of March 2020.
  17. DavidHertzberg

    Several Issues with mac Clients

    Pesetus, To be fair to Retrospect Technical Support: Once an administrator customer's problem has been determined to be a bug, R.T.S. has to turn it over to the Retrospect "engineer" programmers to be fixed. Getting to that determination can take time, because R.T.S. has to first reproduce the problem—which may require asking the customer further questions beyond what is in the Support Case. R.T.S. must then decide if use of existing Retrospect features can solve the problem; if not, the problem is either a bug or a feature enhancement request. Right now the engineers seem to be very busy changing the Graphic User Interface of Retrospect, IMHO so that it will be suitable for running the "backup server" Engine on a Drobo NAS device as well as either a Windows or Macintosh computer. This is a task imposed on them by StorCentric—the new owners of Retrospect "Inc.". Remembering and "reading the tea leaves", in the 1.5 years before the June 2019 merger the engineers were busy adding a couple of major new features to Retrospect—IMHO ones conceived by Retrospect Product Management in order to attract the attention of IT consultants and large-scale enterprises. in their rush to to do that, the engineers seem to have been a bit careless in adding some less-exalted features to x.5 and x.6.0 releases—especially when it came to testing. On top of that, the engineers had to cope with Operating System "improvements"—both by Apple and by Microsoft. And that's why I'm still running Retrospect Mac 16.1, with my major "client" machine and my "backup server" machine under macOS releases two and three generations behind Catalina. Because I'm the not-very-ambitious sole user of a home installation, I can do that—but you evidently can't.
  18. DavidHertzberg

    Several Issues with mac Clients

    For those who were wondering what post Pesetus was responding to, it was one of mine that it turns out Big Brother has deleted. The horrifying content 🙄 of that post which B.B., otherwise known as the head of Retrospect Tech Support, evidently objected to was my merely having repeated what another administrator said about European Retrospect Tech Support in the first paragraph of this post in another thread nearly two years ago. IIRC I advised Pesetus to contact U.S. Tech Support, which evidently he/she has done. So Big Brother is indeed watching you on these Forums, or at least is watching me. I could suggest better uses of his time.
  19. jhg, Here's a SuperUser.com thread on how to kill a task at a scheduled time. Disclaimer: My only experience administrating Retrospect Windows was a Windows 95 Client on a Mac 6.1 Engine from 2001-2004. đŸ€Ł Here's another SuperUser.com thread on how to kill a task in general from a command script.. P.S.: As I said ending the second paragraph of this post in another thread, if my prediction is correct you'll be able to leave a GUI-less Retrospect.exe running constantly—mostly using virtual memory when not executing backup or restore tasks—so your daily e-mail report will be created at 7 a.m. with no effort. P.P.S.: BTW e-mailing of the daily backup report was added to Retrospect Windows 12.5 (so you're not still running 7.5 😀)and to Retrospect Mac 14.5, but with absolutely no documentation. Even this Knowledge Base article, updated in December 2019, uses screenshots from before the Preference was added.
  20. jhg, You probably know this, but here's how and why to submit a Support Case for a feature request. However IMHO Retrospect Launcher—which you refer to by its ancient name of retrorun—is going to disappear from Retrospect Windows 17 (you're surely not really still running Retrospect Windows 7.5 as your Profile says?), as it did from Retrospect Mac 8.0 in 2009, in March or August 2020. I've discussed that prediction starting with this post in another thread. If I'm correct, there's no way your feature request will be implemented by Retrospect engineering. Later on in that thread, Nigel Smith suggested using Windows Task Scheduler—for which a basic guide can be found in this Digital Citizen article. Disclaimer: I'm a Retrospect Mac administrator, and I haven't used Windows since I chose to retire from my last job—where I was using Windows 95 for all but the last 5 months—in mid-2004. So I don't know how you would schedule a kill of Retrospect.exe after it has sent the daily backup report, say at 7:05 a.m.. Maybe someone else on the Forums has a suggestion, or maybe you'll have to research that yourself.
  21. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    I briefly considered Windows Task Scheduler, but thought rbratton might not be knowledgeable enough about it—which was stupid of me since he/she is a software developer. In a prior thread NoelC wondered why the Retrospect developers hadn't included "ï»żeasyï»ż integration with Windows Task Scheduler just by setting the right options in the Retrospect UI"; my answer in a post in that thread—whose first paragraph links to an article describing how to use that modern Windows facility—was that doing so would have seemed a bit premature in 2013. Maybe rbratton should write a Support Case for such a product enhancement—per this boilerplate post, for Retrospect engineering to implement assuming Retrospect Launcher will disappear in Retrospect Windows 17. If rbratton chooses to setup a Windows Task Scheduler task that launches Retrospect early Sunday or Monday mornings, he/she should simply pre-write unscheduled Retrospect Backup scripts —so that he/she can Run them in my predicted Retrospect Windows 17 R.-Mac-like GUI after having worked on a Saturday or Sunday. That would ensure that there are no Retrospect tasks to cancel later on Mondays. He/she can test this currently with run documents. Here's a Knowledge Base article on writing Retrospect script hooks, in case rbratton chooses to follow the suggestion in Nigel Smith's second paragraph. AFAICT script hooks automatically apply to all Retrospect scripts—meaning running any script while Nigel-hooked would end with a machine shutdown.
  22. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    Nigel Smith, You're correct in the immediately-above post, but to "schedule Proactive to run only for certain hours of the day" requires that the "backup server" be already running to act on that schedule. For the next few months, that can be done via the Retrospect Launcher. But, as I said in the second paragraph of the same post you quote, "Retrospect 'Inc.' AFAICT intends getting rid of Retrospect Launcher in Retrospect Windows 17". That would mean that as of March or August of 2020 rbratton's "backup server" machine would have to either be constantly running the GUI-less Retrospect Engine whenever it is booted, or rbratton would have to remember to start the Engine each midnight—a reversion from what he is going to do. I think the second alternative might be more burdensome than the only-on-most-Mondays cancellation procedure I described in the second paragraph of this post, which is applicable to regular Backup scripts. The first alternative would, of course, also work with Backup scripts individually scheduled to run only at certain hours. We'll see in a few months—but see the next two posts.
  23. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton, Cheer up; even if my informed guess about Retrospect engineering plans to switch Retrospect Windows 17 to a Launcher-less Retrospect-Mac-like interface proves correct, you will have the following two options: The first option is the equivalent of your current solution. First, change your Sat.-Sun. backup scripts to both use the same execution unit (see page 272 of the Retrospect Windows 16 User's Guide), and change the scheduled time of those Sat.-Sun. scripts that backup your "backup server" machine to 5 minutes after those Sat.-Sun. scripts that backup your "client" machine. Then, on every Monday following a weekend on which you have not worked both Saturday and Sunday, boot your "backup server" machine first. Immediately, before you boot your "client" machine, start the Retrospect Engine and the Retrospect Console on your "backup server" and cancel every Backup activity awaiting execution. The Backup activity that has already started should be trying to back up your "client" machine; it will fail by itself because your "client" machine—not having yet been booted—is not yet visible on your LAN. After you have done the necessary cancellations, you can boot your "client" machine, By then no Sat.-Sun. Backup activities should be executing or awaiting execution, so you can leave the Retrospect Engine running on your "backup server" machine—where it will be using mostly virtual memory until the scheduled time for your midnight-Tuesday-morning Backups of your Monday work ( you can quit the Retrospect Console, restarting it to monitor those Tuesday-morning Backups). The second option is the equivalent of the one I said in a post above I personally would prefer. First, create scripts for Sat.-Sun. backups of your "backup server" and "client" machines, but do not schedule them. Then, on every Saturday or Sunday you work, when you have finished work simply start the Retrospect Console and Run those scripts using the appropriate Backup Set destination. When the Console shows those scripts have finished execution, you can shut down both machines. If you want, you can instead create a single two-Source script that does a Backup of both machines. I predict you'll like the new Retrospect Windows GUI after you get used to it. Based on the current Retrospect Mac 16 User's Guide, the Retrospect Windows 17.x User's Guide will be half—less than 300 pages—the length of the Retrospect Windows 16 User's Guide.
  24. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton, I had thought about what Nigel Smith says in the first paragraph of his post directly above. However I assume that you are bothered by the additional scanning time for regular backups that follow "catchup" backups, even if the backups are incremental. Moreover I'm not sure his second-paragraph suggestion of Proactive is applicable, because Proactive (which I don't use) assumes a dedicated "backup server" machine that is "always here" whenever the "client" machine is "sometimes here"—which (as Nigel Smith recognizes in his third paragraph) is not the situation described in your OP. Unfortunately your current solution will IMHO become impossible as of March or August 2020 (maybe with a month's delay if Retrospect engineering gets overwhelmed by other StorCentric-dictated enhancements). That is because, per this post in another thread (second sentence in P.P.S.), Retrospect "Inc." AFAICT intends getting rid of Retrospect Launcher in Retrospect Windows 17—as they did with retrorun (its old name) in Retrospect Mac 8.0 in early 2009. The Retrospect Mac 16 User's Guide describes no general Schedule Preferences equivalent to what is on pages 397-399 of the Retrospect Windows 16 User's Guide. Those Schedule Preferences are dependent on the Startup Preferences described on page 401, which affect the behavior of Retrospect Launcher—if the first checkbox in Startup Preferences is checked to enable Retrospect Launcher. This post is part of another thread that discusses the woes of using Retrospect Launcher in Retrospect Windows; and the post's P.S. says "And now that my [Retrospect Mac] backup script has finished running, the combination of Retrospect Engine and Retrospect Console has dropped to 250MB real memory. IMHO derek500's [Retrospect Windows] installation ought to be able to afford reserving that continuously." And in Retrospect Mac one can stop and start the GUI Console while the Engine continues to run.
  25. DavidHertzberg

    Stop "catchup" backups after starting Windows 10

    rbratton,Page 398 of the Retrospect Windows 16 User's Guide says "Schedule lets you define a window during which scripts are allowed to execute." So the result of your experiment is exactly what I would have predicted, if I had had time to post. If you prefer to remember on most Monday mornings to delete the "catchup" backups that have been scheduled but not yet executed, that's up to you. If I were you, I'd prefer to remember on a few Sunday or Monday mornings to execute a pre-prepared run document. Different strokes for different folks.
×