Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by DavidHertzberg

  1. DavidHertzberg

    Dashboard empty

    Lennart_T, Thanks for trying, sorry it didn't work for you. If you haven't already filed a Support Case, please do so; if you have filed one, please add an Additional Note about this attempt. The original e-mail from Retrospect Tech Support (which was actually about another bug, rather than the -530 bugs it ended up fixing for me) said to also move the config80.bak file—if I had one—to the desktop. I didn't have one and still don't, so I didn't mention the .bak file in this thread because I thought it must exist only for previous versions or for Retrospect Windows. I wonder if the fact that I don't have one indicates some difference in my installation. You can mention the fact that I don't have a config80.bak file in your Support Case; maybe that will provide a clue for the Retrospect Inc. engineers.
  2. DavidHertzberg

    Dashboard empty

    So how about updating the Gender in your Forums Profile, myhrik, from "Not saying" to "Male"—as I did years ago? In general I don't try to guess people's genders from their "handles", although I make an exception for those "handles" that are obviously male or female. OTOH I can't help but be aware that many backup administrators are women, and that a lot of those try to conceal that fact for fear that they won't be taken seriously on the Forums. Unfortunately myhrik's ancestors, when they invaded Britain, contributed a number of words to the English language—but not gender-neutral third-person pronouns. So I write "him/her" and "he/she" when the Forums Profile doesn't specify Gender and I can't guess. My other tactic is to address a poster with the second-person pronoun, which is gender-neutral in English (and has no difference between singular and plural, unless you're either from the American South—where they use "y'all" for the plural—or an old-time Quaker—who might use "thou" in talking to someone besides the Almighty). That's why so many of my posts begin with my naming the poster(s) I am responding to, myhrik.
  3. mbennett and anybody else, You currently can't run multiple scripts executing at the same time to the same destination Backup Set (Media Set in Retrospect Mac terminology). I submit pairs of such scripts to Retrospect Mac 15.6.1 (105) occasionally, and the second script submitted always goes into the "Waiting" queue. You will be able to do that some time this side of the indefinite future, once Storage Groups come out of beta. You can't run multiple scripts executing at the same time from the same-named Source. However since Retrospect Windows 12.6 (and Retrospect Mac 14.6) you can run multiple scripts executing at the same time from the same source volume if all of the scripts except one name different Subvolumes on the same source volume (ignore what it still says on page 421 of the Retrospect Windows 15 User's Guide; a "new" 7 November 2017 entry in the cumulative Release Notes overrides that). As I said in the second suggestion in my preceding post, there doesn't seem to be any prohibition on defining multiple Subvolumes (Favorite Folders in Retrospect Mac terminology) as the same real folder—including the root folder of a real volume. You can indeed schedule two scripts to run with the same source, one minute apart. I routinely run two such scripts scheduled 5 minutes apart every day, because until less than a month ago I needed to run a "sacrificial script" before the "real script" to try to eliminate -530 errors for the "real script". I schedule the "sacrificial script" 5 minutes before the "real script", because the "sacrificial script" uses No Files as the Selector (Rule in Retrospect Mac terminology)—and therefore normally completes in 4 minutes. However if the "sacrificial script" starts to run more than 1 minute after its scheduled time, the "real script"—which has the same source and destination—always waits to start. P.S.: As DovidBenAvraham clarified recently in Note 4 in the Wikipedia article, "a Subvolume must be specifically defined to the Retrospect application as a name for a filesystem folder" ; changed last 2 sentences in second substantive paragraph accordingly.
  4. jhg, I am a Retrospect Mac administrator, but I've got a couple of suggestions: First, if running 3 scripts as separate Immediate operations, explicitly designate the same Execution Unit for all 3 scripts. Look on page 93 of the Retrospect Windows 15 User's Guide (you don't specify your version of Retrospect) about switching into Advanced Mode to designate the Execution Unit, then proceed from there. I think that will put the operations into the "Waiting" queue; the equivalent does so on Retrospect Mac. OTOH Retrospect Windows may have special limitations for Immediate operations; Retrospect Mac eliminated Immediate operations in 2009, treating Toolbar-button submissions as scheduled-immediately script creations. Second, if trying to run 3 backup scripts as if they were one script, I assume that you would simply put all the Sources into a single script if they were disjoint volumes or Subvolumes. Since therefore they must overlap, consider defining the overlapping Sources as Subvolumes. Subvolumes are discussed beginning on page 420 of the UG, and —since they are only defined to Retrospect—I don't see any prohibition on defining them so that they name the same folder—provided that (at least on the same volume, and preferably globally) you use different names for each Subvolume. Page 175 of the UG says "Click and drag to rearrange the list order" of Backup Sources. Third, a script cannot execute other scripts. Administrators have occasionally asked for this facility, but Retrospect Inc. has evidently decided that its programming complications would outweigh its usefulness. P.S.: As DovidBenAvraham clarified recently in Note 4 in the Wikipedia article, "a Subvolume must be specifically defined to the Retrospect application as a name for a filesystem folder" ; changed 3rd sentence in second substantive paragraph accordingly.
  5. DavidHertzberg

    Config faulty - start from scratch

    johanvos, Based on my recent experience, you won't have to go through all the steps that you think you will. I think if you follow the steps I recommended for myhrik and Lennart_T in the second paragraph of this linked-to post by me, you will be able to get back a working version of Retrospect fairly easily. You'll be able to keep using your existing Scripts and Media Sets and local Sources; you'll only need to re-Add your "client" Sources and put them back into your Scripts as the paragraph says. For you the only additional requirement is that you first be sure you have upgraded to Retrospect Mac 15.6.1 (105), which I think you may still need to do because your 29 November post says you were using 15.6.0 (125). Just don't do anything to your configs.xml file; I originally did, and it caused me to spend several hours of extra effort for only 5 Scripts and 3 Media Sets. The "smart" Report folders in my Console Dashboard sidebar are just fine, with the exception of Active Scripts and Inactive Scripts. The sidebar says I have 4 active scripts, which is true, but the Active Scripts report folder shows 5 scripts—including one that is inactive. The sidebar says I have 1 inactive script, which is true, but the Inactive Scripts report folder is empty. After I looked inside the Inactive Scripts folder I couldn't select a script in either my Active Scripts folder or my Scripts sidebar category until I quit and restarted the Retrospect.app Console, so I suggest you don't look inside Inactive Scripts. The second paragraph of this earlier post by me explains what IMHO is going on with the engineers at Retrospect Inc.. Because I moved config80.dat to the Mac desktop and let my copy of regenerate it, I don't have a problem with an empty Dashboard. However, even though the pair of 15.6.1 releases fixed a number of "bad release" bugs that the engineers created in 15.5 and 15.6.0—especially for Retrospect Windows, it looks like there are several still-existing bugs for those users of Retrospect Mac 15.6.1 (105) who didn't regenerate their config80.dat files as I happened to. I'll file a formal Support Case for my problems with looking inside the Inactive Scripts and Active Scripts report folders; here's why and how you should file one for your missing Sidebar reports folders. Good luck! P.S.: A word of warning: If you worked through your problem with Retrospect's European Support, don't take that as the most authoritative word. From the comments of one administrator a year ago, it seems that the European Support person is a contractor who is not that familiar with Retrospect. The same administrator said that the contractor's first language seems not to be English (maybe it's German; lucky you! ).
  6. lhlo, I eventually tried to do a Forums search again, this time using "use at most"—including enclosing double-quotes—as the search term. I didn't find the post I had found before, but I found one that seems to be helpful because it deals with Retrospect 10.5. If you want to repeat the search, I suggest you ignore any posts found that are in a Macintosh forum or for Retrospect Express or are from 2007 or earlier. Here's the thread with the post that seems to be helpful. The post is the first one in the thread by Scillonian, who is generally quite knowledgeable about Retrospect Windows. However here's an earlier (and thus probably applicable, even though the OP doesn't state his Retrospect Windows version) Scillonian post in a different thread, which indicates that there may be a problem because it is the Use At Most percentage that is stored.
  7. Over three weeks after my immediately-preceding post in this thread, my -530 Bug 1 and -530 Bug 2 remain fixed. Thursday I upgraded the Client on my MacBook Pro from 14.1 to 15.6.1 (105); first I Removed the MBP "client" from my Sources on my 15.6.1 (105) "backup server", then I upgraded the MBP Client, and last I Added the MBP "client" back to the "backup server"—afterwards changing my Scripts so that the MBP is again backed up in the proper sequence. A "NoOp Sun-Fri. Backup" script and "Sun-Fri. Backup" script for my MBP both ran OK Friday morning, even though my "backup server" was booted well after their 3:00 a.m. and 3:05 a.m. scheduled start times. A "NoOp Sat. Backup" script for my MBP and "Sat. Backup" script for all my 6-drives-plus-Favorite-Folder both ran OK yesterday morning, even though my "backup server" was booted well after their 3:00 a.m. and 3:05 a.m. scheduled start times. I intend to run backup scripts with this configuration for another 2+ weeks, to make sure my -530 Bug 3 (eventual re-emergence of -530 Bugs 1 and/or 2 because of apparent corruption of a configuration file) doesn't emerge. If it doesn't, I'll repeat the Remove and re-Add of my MBP "client" on the "backup server", only this time I'll re-Add the MBP "client" with Use Multicast instead of Add Source Directly (using IP address). If that in turn works for 3 weeks we can declare my -530 Bugs fixed; if not, we can declare all of them fixed except when using Multicast to identify "clients". The fix was apparently made with the release of Retrospect Mac 15.1. The reason I thought it wasn't fixed is because, in the Retrospect.Tech Support e-mail sent with the offer of a test version of 15.0 per this 18 May 2018 post, nobody told me to move the config80.dat file to the desktop to allow it to be regenerated. Thus -530 bugs showed up when I ran that test version, and I reported to R.T.S. that the fix in the test version didn't work. If anyone else installs Retrospect Mac 15.6.1 (105) and wants to try the -530 bug fix that belatedly turned out to work for me, the "backup server" procedure is as follows: [1] In System Preferences->Retrospect , stop the Retrospect Engine. [2] Move the config80.dat file from Library -> Application Support -> Retrospect to the desktop. [3] re-Add any "client" machines to Sources, re-checkmark those "client" Sources in Scripts that use them, and (after hitting Save) drag them in the Summary of those Scripts into the sequence they should be backed up (and hit Save again). [4]  In System Preferences->Retrospect , start the Retrospect Engine again—or simply re-boot your "backup server". [5] To be on the safe side if you didn't re-boot your "backup server", Quit the Console and then re-launch it (Applications->Retrospect.app) again.
  8. lhlo (the Forums software says the first letter of your "handle" is a lower-case 'L'), I'd like to be helpful, but —especially being a Retrospect Mac administrator—I couldn't find much that would help. Two nights ago I used the Search facility of the Forums to find a really old (2009 IIRC) post that might shed some light on your problem, but I stupidly decided not to bookmark it and the next morning couldn't reconstruct the search terms I had used. The best I can suggest is that you Rebuild your Backup Set, per pages 533-535 of the Retrospect Windows 9.5 User's Guide. Click All Disks in the dialog shown on page 533, because you don't want to use the Fast Catalog Rebuild info that may be stored in your Backup Set's Catalog File. If you're lucky, that will eventually bring up a dialog that will allow you to change the "Use At Most" number of GB for your Member on the 4TB drive. If it doesn't allow you to do that, IMHO you'll just have to be satisfied with adding a second member on the same drive—as I suggested in the second paragraph of my preceding post in this thread. If any other "actually helpful" administrator has a better answer for Retrospect Windows 9.5, I urge him/her to post it. Retrospect Inc. eventually noticed this is a problem, and added a feature in Retrospect Windows 11 to solve it. Here is the entire description of this feature, taken from page 14 in the "What's New" chapter of the Retrospect Windows 11 User's Guide: Informative, isn't it? (You see, I can do sarcasm as well as condescension. ) And you won't find any further explanation in any UG up through version 15, because Retrospect Inc. adopted a new policy with Windows 11/Mac 13. Previously a new feature was announced in the "What's New" chapter of the UGs for the major version that introduced it, and then explained in more detail in the appropriate other chapter(s) in the UGs for later major versions. Starting with major version 11/13, that policy was changed so that the explanation of the new feature would be done in a separate Knowledge Base article—if a Retrospect Inc. engineer felt like writing one (which didn't happen for the "move the member folders" feature—and that's not the only feature for which no KB article was written). Meanwhile the "What's New" chapter of the preceding version's UGs would be completely overwritten with the announcement of newer features. Now you understand why my life outlook as a volunteer Forums contributor could stand some improvement.
  9. DavidHertzberg

    Dashboard empty

    Lennart_T and myhrik, Early this morning I thought of another possible reason why you have this problem and I don't. As recounted in this post (which you shouldn't read), on 9 January I stopped the Retrospect Engine on my "backup server" in System Preferences -> Retrospect and then moved the config80.dat file from Library -> Application Support > Retrospect to the desktop. When I rebooted my "backup server", thus restarting the newly-installed 15.6.1 (105) Retrospect Engine and starting the Retrospect.app Console, it regenerated the evidently-corrupted config80.dat file—which turned out to fix a set of -530 bugs I had had for 2 years. The reason you shouldn't read the post I linked to in the second sentence of the preceding paragraph is that it says I also moved another configuration file to the desktop. Having done so made me spend several hours recreating the "client" machines and scripts and Media Sets, but later repeating the operation on another "backup server" boot drive containing Retrospect Mac 14.6 showed me I wouldn't have had to do that if I had merely moved config80.dat to the desktop. Lennart_T—if he moves the config80.dat file from Library -> Application Support -> Retrospect to the desktop—will have to re-Add any "client" machines to Sources, re-checkmark those "client" Sources in Scripts that use them, and (after hitting Save) drag them in the Summary of those Scripts into the sequence they should be backed up (and hit Save again). myhrik, because he/she evidently doesn't have any "client" machines, shouldn't have to do anything further. To be on the safe side, Quit the Console and then re-launch it (Applications->Retrospect.app) again. If you're brave enough to try this, I hope it helps.
  10. DavidHertzberg

    Dashboard empty

    Sorry, Lennart_T, something you had written in a previous post made me think you actually have a Server Edition license for Retrospect Mac. But how about the "Enable Management Console" checkbox in the pane displayed by clicking the Management icon at the top of the Retrospect->Preferences panel? Is that checked? If it is, does un-checking it and quitting-restarting the Console bring back what should be the contents of your Console Dashboard? If the answer to both those questions is 'no", then I suggest you file a Support Case—which I'm sure you know why and how to do. I'm out of ideas that would explain why you and myhrik have this problem and I don't.
  11. DavidHertzberg

    Dashboard empty

    Lennart_T and myhrik, The more I thought about it today, the more the hypothesis in my preceding post made sense in terms of what I have deduced (from publicly-available information) about "Product Management Think" at Retrospect Inc.. J.G. Heithcock and his merry men evidently think Retrospect Inc. needs to "go big or go home"; to them that means [1] becoming appealing to consultants and [2] getting into the virtual-server backup sub-market. [2] has motivated the development of R.V. (the head of Retrospect Tech Support has forbidden me to mention the name of this Retrospect product on the Forums), and [1] has motivated the development of the Web-based Management Console—which Retrospect Inc. is advertising as enabling a consultant to monitor up to 100 "backup servers" at multiple locations—which will be those of the consultant's customers (I'm here avoiding the use of the term "clients" to avoid confusion with the Retrospect term). It would make marketing sense to limit the routine use of the Management Console to Server Edition licensees, since Desktop Edition and Solo Edition licensees would not normally hire consultants. So I wanted to ask myhrik if he/she has a Server Edition license, and fired up my Console to find out what to tell him/her to look for in Preferences under the Retrospect menu. I found—as I remembered—a Licenses icon on the top of the panel; the first license line in the pane displayed by clicking that icon says "Desktop" on my Console, and I'll bet the first license line of myhrik's pane (as well as Lennart_T's pane) says something else with the word "Server" in it. Then I noticed that immediately to the right of the Licenses icon is a Management icon, and the first item in the pane displayed by clicking that icon is an "Enable Management Console" checkbox. If that checkbox is checked, as it may be by default if you have a Server license, uncheck it and see if your non-Management Console Dashboard becomes populated—which may require your quitting and re-starting Retrospect.app (which is perfectly OK; I've done it myself on occasion). If this solves your problem, then it is still consistent with what years ago I perceived to be the other purpose of the Web-based Management Console. If you read between the lines of the History section of the Retrospect Wikipedia article, you'll see that Retrospect Windows has been seriously crippled for 10 years because Windows security restrictions made it impossible to separate a GUI Console from the Engine as was done for Retrospect Mac. The workaround, which all other enterprise client-server backup applications have implemented for their Windows "backup servers", is to make the Administrative Console a Web-served application and the Engine-equivalent a Web-served client. I've gotten unofficial confirmation that Retrospect Inc.'s intent is to give the Windows version of the Management Console two-way interactive communication with the Retrospect Windows Engine. Over a year ago, a Retrospect Mac administrator setting up a Retrospect Windows installation discovered he could almost perfectly control a Retrospect Windows "backup server" from a Retrospect Mac Console—because the Retrospect Inc. engineers have carefully preserved the inter-process communications capabilities of the Retrospect Windows Engine that were developed before 2009.
  12. DavidHertzberg

    Dashboard empty

    Lennart_T, I've never signed up for the Management Console and, as I've said two posts above, I'm seeing a fully-populated Dashboard on my Desktop Edition 15.6.1 (105) Console. The only explanation I can imagine is that there's some new feature (I'd call it a bug in Retrospect 15 and a kludge in Retrospect 16) ensuring that, since you (and possibly myhrik) are licensed for a Server Edition, you can't see a non-blank Dashboard even on your "backup server" unless you are signed up for the Management Console. Maybe that's what "We plan to launch it officially in Spring 2019 with a free tier [my emphasis] and a paid tier" on this About page means?
  13. DavidHertzberg

    Dashboard empty

    Sorry, myhrik, I don't agree with my President on almost everything, including his views on NATO. That was just my bad late-afternoon attempt at humor, inspired by Werner Walter's revelation that it is the U. S. Air Force that is insisting Retrospect Inc. keep the non-Web Console for Retrospect Mac. Seriously, I'm truly mystified by your blank-Dashboard problem—because I don't have it on what should be a very similar installation of Retrospect Mac. Here's a brief explanation of "backup server", so you don't have to read the Wikipedia article on Retrospect: Back in 2009, what was then the Iomega division of EMC (largely the same developers as now, AFAICT) split Retrospect Mac into two separate programs, the Engine and the Console. The Engine runs on a "backup server" Mac that has the backup drives (which can actually be in the cloud) attached, and does all the work involved with actually executing scripts. The Console runs the Graphic User Interface used by the backup administrator for communicating with the Engine. The reason EMC Iomega separated the programs is that, in many enterprises running Retrospect, the "backup server" machine sits in a locked and fire-resistant "server room" to which the backup administrator doesn't have a key. Therefore in any Server Edition of Retrospect Mac, the Console can be run on any Mac that is on the same Local Area Network as the "backup server" Mac. In a cheaper Desktop Edition (which I have licensed) or Solo Edition of Retrospect, the Console must run on the "backup server" Mac—but it is still a separate program (Retrospect.app) from the Engine that can be stopped and started while the Engine is running. After its split-off from EMC, Retrospect Inc. added the Dashboard as a high-level summary panel on the Console interface. As I said in the first sentence of the preceding paragraph, the Console on my Desktop Edition of Retrospect Mac 15.6.1 (105) has had a fully-functioning Dashboard up through early this morning—which is when I last looked. I ask you the same question I asked Lennart_T two posts above: If you click on the Past Backups category in the leftmost column of the Dashboard, do you see the usual information? In any case, I think you should file a Support Case about your problem. Here's why and how to do it. If you upgraded to Retrospect Mac 15 in the last 30 days, you are entitled to personalized help with your problem—which may have something to do with your setup of Retrospect—as opposed to mere processing of the bug report.
  14. DavidHertzberg

    Dashboard empty

    Then, Lennart_T, you have a different problem from Lindsay Robertson's. He/she reported back in May that the blank Dashboard only occurred on a non-"backup server" machine. However that same post also said "All the other sections perform exactly as on the backup server console." Is it true for you that, if you click on the Past Backups category in the leftmost column, you see the usual information? Another question for both you and myhrik is: are you running Retrospect Mac If you are running 15.5 or 15.6.0, you should be aware that those were "bad releases" in which Retrospect features that had worked before no longer worked—especially for Retrospect Windows. That is why Retrospect Inc. released for Retrospect Windows and for Retrospect Mac, and why they chose not to publicize those releases—because they fixed bugs that were newly-created by harried Retrospect Inc. engineers.
  15. lhlo (demerits for picking a cutesy-poo "handle" for which I can't figure out whether the first letter is upper-case 'I' or lower-case 'l'), First, read the boxed-in paragraph below the screenshot at the top of page 448 in the Retrospect Windows 9.5 User's Guide. If that paragraph describes what happens when your Member is full, un-check the checkbox and increase the "Use At Most" number of GB appropriately. Second, if that doesn't work, do what it says on pages 449-451 of the UG under "Adding a Disk to a Backup Set". Add the new Member on the same disk as existing Member, and give it the appropriate "Use At Most" number of GB. This post describes that as the workaround for an earlier version of Retrospect Windows. So this is your "poor second choice", but next time you'll remember to set the "Use At Most" percentage appropriately when adding all new Members.
  16. DavidHertzberg

    Dashboard empty

    myhrik and Lennart_T, I believe what you are experiencing is what Lindsay Robertson reported last May. I'm assuming your blank Dashboards are on Macs other than the "backup server". I've been (belatedly, for reasons not appropriate to this thread) running Retrospect Mac for nearly three weeks now, and the Dashboard on my Mac Pro "backup server" is filled with glorious information—some of which has old (the Backups bar graphs) or new (the circular Backup Report) bugs in it. I am only licensed for the lowly Desktop Edition, so I can't install the Retrospect Mac Console on my MacBook Pro "client" machine; my installation is at home, and I'm not so decrepit that I can't walk into my bedroom and use my Mac Pro's Console. My explanation for Lindsay Robertson's problem is in this post in that thread. My final post in that thread recounts my phone conversation in May with Werner Walter, the head of Retrospect Inc. Sales. The "related announcements" Werner referred to were the May release of the first beta version of the Web-based Management Console. My impression is that J.G. Heithcock and his merry Product Management men (I'm speaking of Retrospect Inc.; I think they've heard of women ) are hell-bent on delivering a fully-functional Management Console with Retrospect 16.0 in March 2019. As you can see, the Management Console is a Web-based version of the Dashboard, so the non-"backup server" Dashboard bug in the non-Management Console has not been fixed as of the cumulative Release Notes. I don't know whether the Retrospect Inc. engineers will have time to fix your bug before March. If you want to "go with the flow", here are instructions on how to install the Management Console—which will cost you nothing in Retrospect 15. Maybe the Scandinavian representative of Retrospect Inc. will want to record your impressions, and possibly attach sensors to your bodies , while you use it. Werner told me that, in any case, Retrospect Inc. cannot abandon the non-"backup server" Mac Console; the United States Air Force (helping to protect your NATO-member butt, myhrik, and Old Golden Boy would like Norway to pay more for that protection ) evidently uses Retrospect Mac, and won't allow Web-connected applications in security-sensitive locations.
  17. DavidHertzberg

    Dashboard Backup Report Errors

    (Copied—with clarifications—from the latest Additional Note to my Support Case) Interesting results running my "Sun.-Fri Backup" scripts early this morning, which is a Sunday: I initially looked at my Mac Pro "backup server" in the bedroom just after the "sacrificial script" (see last substantial paragraph of this post for the initial explanation of what that means) had started running. The Dashboard's "Most Recent" pane showed all 7 drives backed up—in a Recycle—as of yesterday. The "Backups" bar graph for yesterday did show a segment on the right end for my Macbook Pro's "Macintosh HD", and the circular "Backup Report" showed all 3 drives on the G4 as Unprotected. The "Backups" bar graph showed segments for the preceding Sunday-Friday "Sun.-Fri. Backup" daily No Media Action script runs, which backup only my MacBook Pro. I again looked at my Mac Pro "backup server" just after the "real script" had finished running. In the "Backups" bar graph for yesterday the backup for the Favorite Folder had changed, now being shown in two segments. The first segment is all the way on the right, in place of the backup for my MacBook Pro's "Macintosh HD"—which is the first drive backed up by the "Sat. Backup" script. The second segment is all the way on the left, which is where it should be because the Favorite Folder is backed up last by the script. I had not restarted the Console while all this was going on, so the change must have been from the Console picking up revised information from the Engine. The circular "Backup Report" still showed all 3 drives on the G4 as Unprotected. Since the circular Backup Report is new in version 15, my guess is that the engineer who programmed it said to himself/herself "I know that version 16 is not going to handle Legacy Client machines, so I won't bother to provide for them in the circular 'Backup Report'".
  18. bradp015 and Lennart_T, bradp015 can as of Retrospect Mac 14.6 do what he suggested in his OP, so long as he is simultaneously backing up a different Favorite Folder on the same drive in each script. He could divide his whole disk into Favorite Folders, which only apply to Retrospect, and have his two scripts back up the Favorite Folders in a different order. Alternatively bradp015 could do what Lennart_T suggests, with a Backup script and a Copy script. However he should be sure to assign the same Activity Thread, in the Summary tab for the Scripts, if he schedules the two scripts so that they could possibly overlap in execution. If he doesn't make sure to do that, the Copy script will ignore new or changed files that are being backed up—since it uses a Catalog File that is not updated for the Media Set until the end (barring any optional Comparing) of the Backup script run. P.S.: On 10 January 2017 I suggested in this Product Suggestions—Mac OS X thread that a modest enhancement to Retrospect would enable overlapping a Backup to a particular Media Set with a Copy Backup or Copy Media Set from that same Media Set as the source. That enhancement assumes that the Copy script would be scheduled at least a minute after the Backup script. On 2 April 2017 I converted that suggestion into Support Case ##54601 for a Feature Enhancement. That Support Case has been closed, with no evident action taken on it by Retrospect engineering since then. Considering that Retrospect 15 now enables multiple Activity Threads (Execution Units for Retrospect Windows) even for the Desktop Edition, IMHO Retrospect engineering should reconsider that enhancement for Retrospect 16.
  19. DavidHertzberg

    Defer on v10.5

    skypitt and Lennart_T, At the beginning of 2019 I was running Retrospect Mac 14.6.0 from a HDD on my Mac Pro. I was still doing that because my workaround procedures for -530 bugs—which had not been very effective for the preceding month or so—had not seemed to work at all when Retrospect Tech Support had me run a test version of 15.0 with a supposed -530 bug fix and enhanced logging last summer, which I had done from an SSD on my Mac Pro. I tried running 14.6.0 again on 7 January, but the "deferred" scripts would not back up "client" drives— only local drives. That was still true after I upgraded the Console to the newly-released 14.6.2 version. If you care, that's recounted in this post and the first paragraph of this post. Then, acting precipitously on an e-mailed suggestion from Retrospect Tech Support that was really for a Support Case for another bug, I installed on my Mac Pro's SSD and deleted a couple of configuration files. I had to recreate my scripts because of my over-zealous deletion of configuration files, but both the "deferred" bug and my -530 bugs disappeared—as recounted here and in the first 2 paragraphs below the quote here. Finally I switched back to my HDD and deleted only one configuration file, after which 14.6.0 with the 14.6.2 Console ran without either the "deferred" bug or a -530 bug I couldn't get around—as recounted in the last 2 paragraphs below the quote here. Therefore I've officially upgraded to as my production version of Retrospect Mac, although I'm currently using the 14.1 Client on my MacBook Pro to make sure I don't get -530 errors. However I've filed Support Case #65274, suggesting in the Problem Statement that Retrospect Inc. allow Mac administrators with a license for a version older than 12 to upgrade to version 12.5—so they can then install the 14.6.2 Console to fix the "deferred" bug—for less than the price of upgrading their Editions to version 15. It seems to me that getting some licensing income from these installations would be better than getting no licensing income, but maybe that type of business thinking is too sophisticated for the Silicon Valley area.
  20. DavidHertzberg

    No more instant scan on MacOS?

    1.5 weeks ago I switched to running Retrospect Mac in production on my Mac Pro "backup server". My Saturday Recycle backups of 6 drives plus a Favorite Folder are running about 0.5 hours faster then they used to. That is probably because Retrospect is running on an SSD, whereas Retrospect Mac 14.6.0 was running on an HDD (my Mac Pro has 2 HDDs, including the one belonging to my late friend, and 1 SSD). Instant Scan is still working for the SSD in my MacBook Pro "client" and the 2-drives-plus-a-Favorite-Folder in my Mac Pro. However both my MacBook Pro and my Mac Pro are still booting under MacOS 10.12, and all my drives use HFS+ instead of APFS. In addition my MacBook Pro is still using the Retrospect Mac 14.1 Client, because I have long suspected that a later version of the Client was contributing to my temporarily-vanished -530 errors. The half-hour speedup in my Saturday backup script may simply be due to the fact that the current Mac Pro boot drive, that I am backing up in its entirety, is an SSD rather than a HDD (I've kept my Catalog Files on the former HDD boot drive, so I'm backing them up as a Favorite Folder).
  21. DavidHertzberg

    Retrospect keeps backing up files that are linked to

    heavanw, To help other Retrospect Windows administrators who might have the same problem in the future, please be so kind as to post exactly which Windows Security backup options you checked and un-checked. Those would be, I think, on pages 379-382 of the Retrospect Windows 12 User's Guide. Thanks!
  22. DavidHertzberg

    Retrospect keeps backing up files that are linked to

    heavenw, Maybe there's a bug because you're doing block-level incremental on an external drive. I noticed in the cumulative Release Notes for the very first release of Retrospect Windows 10 "Fixed: Fix for backing up system file hard links as separate files (#4958)", but maybe it wasn't fixed for external drives. However, even though I'm a Retrospect Mac administrator, I realize these probably don't qualify as "system files". The following would probably be a pain in the butt, but have you considered defining everything on your external drive as a set of Retrospect Subvolumes—and then having your dedicated script not backup the Subvolume that contains these sub-directories?
  23. DavidHertzberg

    Retrospect keeps backing up files that are linked to

    heavanw, First, you fail to state either your version of Retrospect Windows or your version of Windows. You ought to know by now that doing so is in most cases a necessity for our giving you any kind of help on these Forums. However the cumulative Release Notes for Retrospect Windows do not show any recent fixes to Selectors. Second, your problem with excluding via a Selector not working sounds similar to the problem seanbreilly has reported starting with this post. Ignore the fact that he tacked his posts onto an existing thread on a Forum dealing with an obsolete version of Retrospect Mac; he reports using "Retrospect ( [whatever that is] in my post, but not my Windows, which is Windows 10". Note the suggestions in the P.S. of my 7 January 2019 post below his.
  24. seanbreilly, On these Forums there are no gripes about duplicating a question. You can always link to a previous post; that is done by [1] clicking or double-clicking wherever you want the link to be inserted, [2] clicking with the Right Mouse Button on the icon at the upper right of the previous post's window and selecting "copy link location", [3] clicking on the icon at the top of the editing window for your post that looks like a link in a chain, [4] pasting the URL you copied into your clipboard in step [2] into the URL field, and [5] typing the text you want to associate with the link into the Link Text field and clicking the Insert Into Post button. Discussion of your problem indeed belongs on a Retrospect Windows forum, because it both involves using a Retrospect-Windows-specific GUI feature and using that feature to specify a Windows path. I don't know why your screenshots didn't make it into your OP; I've never included a screenshot into a post on these Forums. I gather you need to click the Insert Other Media button at the lower right of the editing window and select the appropriate choice for your screenshot. If you've not already upgraded to Retrospect Windows, you should do so. 15.5 and 15.6.0 were "bad releases" with newly-introduced bugs in existing features—especially for Retrospect Windows, but they allegedly included fixes to problems with Windows 10.
  25. Wait a minute, bradp015. You had your RAID drive unmount? Is it a NAS server, and was it while running Retrospect Mac 9? The cumulative Retrospect Mac Release Notes say, for Retrospect Mac 12.0, "Fixed: Changing the media set 'Use at most' option when backing up to a NAS no longer results in a media request (#3861)".