Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


Everything posted by DavidHertzberg

  1. 😧😧 I originally tried to test this out early this morning, but ran into a problem that may be peculiar to my installation—rather than Retrospect Mac 16.6. I first Removed and Added—afterward changing the Options—on the "backup server" Source definition of my MacBook Pro "client" to allow Wake-on-LAN, and did the same Options-changing on my two daily No Media Action Backup scripts (the "sacrificial" script and the "real" script—after re-checkmarking the MBP on all my scripts that use it. I then tried putting my MBP—booting macOS 10.13 High Sierra—to sleep via the Apple menu; but except for one time it wouldn't stay asleep for more than a few seconds. However tonight I experimented further, and I can get my MBP "client" to stay asleep—initiating that via the Sleep item on the Apple Menu—if in System Preferences->Energy Saver->Power Adapter I change the Turn display off after slider from Never to 3 hours. Then provided Wake for network access is check-marked on the pane below the slider, putting the MBP to sleep while running my "sacrificial" script (it uses the No Files Rule—note Rule is the Retrospect Mac term for Selector, but scans a while because I've now got a thumb drive plugged into my MBP) results in its waking up in a few seconds. I have no idea what the Windows "client" equivalent of the System Preferences->Energy Saver->Power Adapter settings would be. Nigel Smith will know. And yes, Nigel Smith, I knew about require password on wake; I wondered if some of your cleaning people might moonlight for Chinese Intelligence. 😧 P.S.: Forget what I said in the third paragraph of this post. I stayed awake long enough to try this on my scheduled 3:00 a.m. "sacrificial" and 3:05 a.m. "real" Backup scripts, and things didn't work out as I'd hoped. I woke up at 6:45 a.m., and remembered that since Spring 2015 I've been using an external keyboard and a mouse connected to a bus-powered KVM switch—so that I can switch both of them them back and forth between my MacBook Pro and an old Digital Audio G4. Bus-powered means the KVM switch shuts down unless either the MBP or the G4 is awake, so the spacebar on the external keyboard doesn't wake up the MBP. Pushing the spacebar on the MBP's built-in keyboard does wake it up, but that doesn't get an already-running Backup script out of a frozen state after I've slept the MBP while the script is running. In short: Wake-on-LAN still doesn't work for scheduled scripts.
  2. Gintzler, On page 40 of the Retrospect Mac 16 User's Guide, an Enable Wake-on-LAN checkbox is described for Sources->Options. I don't know whether checking this box for a "client" will wake it up if the user sleeps his/her machine during a backup; at the bottom of this post I've asked Nigel Smith if he knows. In fact, per this 2016 post, I don't know if Wake-on-LAN is now working—it wasn't in 2016—at all for Scheduled (rather than Proactive) scripts. FYI, the screenshot at the top of page 40 is way out of date; the two checkboxes in the top pane have been joined by three more for features added in the last 10 years, and a middle pane has been added for the Allow client to permissions—also added in the last 10 years—that Nigel Smith mentions in his post directly above. Unfortunately the august Documentation Committee stopped updating UG chapters other than "What's New" in 2015. Nigel Smith, If a user puts a "client" to sleep while a Scheduled script is backing it up, do you know if Wake-on-LAN will reawaken it if enabled for that "client" Source? Also, given the recent substitution of SSDs for HDDs, does sleeping a machine—other than for "mere" đŸ€Ł security—actually still prolong its lifetime?
  3. Gintzler, If you're getting a -535 error, it may be because you've got some process doing a forced update of your "client" machine. In June 2016 I was getting that, and this post shows it was because of Adobe Flash Player—which is now repeatedly advertising it's going away— or MS/Firefox doing updates. Also, here's a post that details the differences in terminology between Retrospect Mac 6 and Retrospect Mac ≄ 8.
  4. Gintzler, I think you must be looking at the page number in the top left corner of your browser's view of the Retrospect Mac 16 User's Guide, rather the actual manual page number printed at the bottom right or bottom left of the page. Starting some versions after Retrospect Mac 6, User's Guides begin with a un-numbered title page followed with a copyright-license-warning page that has the number "ii" at the bottom left. So if you type "36" into your browser's view, you'll actually be looking at page 34 of the manual. That's the first mention of Media Actions, saying that Incremental is the default. Now do a browser search for "Media Action". Once you get past page 36, the next mention of the term is on page 96 of the UG. Paragraph 9 on that page says: Also starting some versions after Retrospect Mac 6, the Retrospect Inc. august Documentation Committee stopped actually printing Chapter numbers except—sometimes—on the top left and bottom left of the first page of a chapter. If you go back to page 85, you'll see page 96 is part of Chapter 6. While I was writing this post, Lennart_T's posts—with your reply in between—arrived. Why the heck had you planned to use an Archive script? 😕
  5. Gintzler, My references are to the Retrospect Mac 16 User's Guide. (Unlike Lennart_T, I don't trust the Mac 17 UG because it's been edited by the StorCentric Slasher.) First, you're not as wrong as you think. There's a Copy script Move Files option on page 121 that "deletes files from the source volume after they have been copied." However "By default, this option is off." Second, I don't see why per your OP you "Don't want to have 3 separate scripts." Unfortunately the UG has never explained for any type of activity the Use pop-up shown in the Summary screenshot for Copy below item 11 on page 121. As defined on page 225, an activity thread—a capability added to Retrospect Mac 8 and not extended to the Desktop Edition until Retrospect Mac 15—allows multiple activities to run concurrently if they have unique sources and destinations. "By assigning activities to the same activity thread, it ensures that they will run one after the other." Thus you can have 3 Copy scripts for each corresponding source and destination Favorite Folder—but specifying the same Activity Thread, and either schedule them one minute apart or give them script names in the alphanumeric sequence in which you want them to run. Third, your OP says "Don't want to do a Backup script because I do not want incremental." If you read media action on page 228, it says "“Recycle Media Set” tells Retrospect to delete the contents of the selected Media Set’s Catalog, then erase and reuse the first member of that Media Set, literally recycling the media and using it over again." So, per page 35, you could have one Backup script specifying all 3 Favorite Folders as sources and its own separate Media Set as a destination. That would eliminate incremental backup, but the latest backed-up version of the 3 Favorite Folders wouldn't be available to the users until you ran a Restore activity for that separate Media Set—and that activity could use a Rule specifying a Windows Path per page 168 to limit the Restore to one or two of the 3 Favorite Folders. In short, for what purpose do you intend to use files contained in these Favorite Folders?
  6. A week and a half ago, as part of an effort to convert files on her old Digital Audio G4 left in my care in 2005 by my ex-wife—who died on 13 January 2021—to a format readable by modern computers, I moved a thumb drive created on the G4 to my 2016 MacBook Pro. While I was painstakingly using LibreOffice on the MBP to convert each of 800 MS Word 5.1a files to the .docx format, I checkmarked the thumb drive in drives backed up for my MBP Source in Retrospect. I immediately started getting -530 errors unless I did a Locate for the Source before or while the "sacrificial" script was running. I then Removed and re-Added my MBP as a Source, using Add Source Directly with both the HDD and the thumb drive check-marked in the Options tab Volumes pane pop-up Selected Volumes. The -530 errors went away. Obviously I also re-checkmarked the MBP in the Sources tab of any scripts intended to back it up. In 2019 I'd Added the MBP with Add Source Directly, but it seems just altering the Options tab Volumes pane pop-up Selected Volumes made Retrospect Mac 16.6 re-Add it sneakily with Use Multicast. I'll file a new Support Case, or add this as an Additional Note for my long-running Support Case #61302.
  7. Nigel Smith, I'm surprised at you! 🙄 Don't you realize that the whole idea of modern (since low-cost large-capacity HDDs were introduced in the 2000s; previously it was that tape drives were expensive) client-server backup is based on the principle of not trusting ordinary users to be responsible for backing up their own machines? That's why Retrospect Mac 9 introduced "Locking client features and preferences"—page 8 of the Retrospect Mac 9 User's Guide Addendum, with the first preference listed being "Turn off the Retrospect Client software". A long-time close acquaintance (we've never been in each other's apartments) is quite knowledgeable in her specialized field—which isn't related to computers or engineering, and is a part-time teacher of university courses that require her to grade student exams and papers etc.. I happened to ask her in January 2018 how she was backing up her Mac, and she said she had bought some kind of wireless external HDD to use with Time Machine. I no longer recall the details, but the HDD was USB-powered and had a battery that was good for 10 hours. It turned out she wasn't routinely plugging in the USB cable to her Mac—her only USB electrical power source, apparently because she was afraid of tripping over a USB cable in her small apartment. So Time Machine was not in fact backing up her Mac; thank goodness she hadn't had a disk crash. How do you know some of jethro's bosses aren't as lazy (she never checked if TM had been successfully backing up) as she was? Wouldn't jethro have to be monitoring his bosses under your proposal? Prepare to be picked up by the fearsome Retrospect Support Police and be taken to a backup administrator re-education camp.đŸ€Ł
  8. jethro, On -Demand Backup/Restore was a capability added to Retrospect Mac 9, per pages 4–5 of the Retrospect Mac 9 User's Guide Addendum. So I guess the same "standing-by" for a "reaching-out" Remote "client" must have been added to that capability—as it was for Proactive scripts—to the "backup server" in Retrospect Mac 15.6. I can't find a post on the Forums from anyone who has used it, so I guess we'll have to see if Nigel Smith can run a test. P.S.: Assuming On-Demand Backup does work for a Remote "client", then the Client for that Remote "client" would have to be non-operational for that "client"—either because the machine wasn't booted or because the Client had been turned off—whenever a Proactive script specifying the tag "Remote Backup Clients" as a Source was running. Otherwise the "client" would be backed up by that Proactive script.
  9. Does the Back Up Now choice on the Retrospect Mac Client menu-bar icon actually work for Remote Backup "clients? I have no way of testing that, so maybe you could. Page 74 of the Retrospect Mac 16 User's Guide says My understanding is that Remote Backup "clients" are not logged into the "backup server" unless and until they "reach out" to that server, which would happen when the "client" machine boots with its Client running or turns on its Client. By thus "reaching out", a Remote Backup "client" has automatically put itself into the volumes queue of any Proactive script specifying Remote Backup sources that is currently "proactive" per page 107—so clicking the Back Up Now choice wouldn't AFAICT accomplish anything additional. Besides, page 74 goes on to say That paragraph is speaking of a popup list on the Clients panel of the "backup server"'s Retrospect->Preferences, and it would therefore have to specify a Storage Group to allow for simultaneity. Because of the current limitations of a Storage Group, the administrator would IMHO periodically have to Copy Backups from that designated Storage Group to another Media Set.
  10. DavidHertzberg

    Restore RDB files to scratch re-install

    BillClark22, It sounds as if you didn't bother to RTFM—which is the Retrospect Windows 9 User's Guide, or else you wouldn't have "tried copying the folder with all the files to the PC". First, assuming your client's external drive is still OK, IMHO you should do the following: (1) Windows-delete the sub-folder of RDB files you copied from the PC you copied it to. (2) Retrospect-Forget—per page 433 of the UG— the Retrospect Backup Set you recreated on the PC. (3) Windows-delete the Retrospect Catalog File you recreated on the PC. Next, follow the "Recreating a Disk Catalog" procedure on pages 533–535 of the UG to recreate the Catalog for the Backup Set. Important: You must use precisely the same name for the Backup Set you used before the crash; if you have any doubt any doubt about the name, use Windows File Explorer (whatever it's called now—I haven't used Windows since early 2004) to look at the folder name of the sub-folder on the external drive—the portion of the name following numbers and a dash will be the name of the Backup Set (i.e. if the folder name is "1-Backup Set Whatever", then the name of the Backup Set is "Backup Set Whatever"). If you don't get this right, Retrospect will refuse to use the RDB files to recreate the Catalog File for the Backup Set. After that, follow the "Restoring In Wizard Mode" procedure on pages 123–131 of the UG. Finally, follow the "Creating a Retrospect Emergency Recovery Disc" on pages 369—372 of the UG and "Using the Retrospect Emergency Recovery Disc" procedure through "Planning Ahead" on pages 372–373. Note that, under "There are two methods for restoring a computer that won’t boot:" on page 369, some Retrospect Inc. lame-brain forgot to revise the second bulleted item from the way it was in the Retrospect Windows 6 UG so that it instead referred to the "Restoring In Wizard Mode" procedure on pages 123–131—that item was deleted for Windows 10 in the Retrospect Windows 16 UG.🙄
  11. (Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. The same is true of Retrospect's history, especially with references to here.) jethro, Your post immediately above says I don't think you realized the implication of what I was saying about the Retrospect Windows Scheduled Backups enhancement in section 3) of my last up-thread post. That enhancement isn't in Retrospect Mac 17, which means the only way you can currently do Remote Backups using a Mac "backup server" is with Proactive scripts. To understand why, you also need to consider portions of the first 3 paragraphs in this post in another thread; they reveal that for Remote Backup the Retrospect engineers needed the capability of having a "backup server" script stand ready to act whenever a "client" machine "reaches out" to it. That capability has been in Proactive scripts for many years, so to get Remote Backup all the engineers needed to do was add a specialized extension of Retrospect's public-key cryptography facility to Proactive script processing. The "Remote Backup: Support for Scheduled Backups in addition to ProactiveAI Backups" Release Note for Retrospect Windows 17.0.1 implies they eventually figured out how to add the same crypto extension to Scheduled script processing, but not yet for Mac "backup servers". That means the only way you can currently get Remote Backup of your computer late at night is to run a Proactive script with thï»że exact Tag "Remote Bacï»żkup Clï»żieï»żntï»żs" in its Sources. You could schedule that Proactive script to run during a late-at-night period on certain days , but only "manually initiate" the booting of your computer during the time that script runs if you want it to be backed up. ï»żï»żï»żBut then you'd run into the "kludge" problem if you later decided to back up your bosses' laptops at home using a Remote Backup Proactive script instead of TM/CCC. You'd have to schedule the Remote Backup Proactive script during one time-of-day period to give their computers backup priority, but make sure you didn't boot your computer during that same time-of-day period to avoid its grabbing Remote Backup priority. Of course the Remote Backup priority-grabbing problem would disappear if your Proactive script had a Storage Group destination, which would enable up to 16 simultaneous backups—with simultaneity working fine on a fast "backup server" Mac because of slow "client"-to-"backup server" data transmission speeds. But then you'd run into the incomplete-GUI problem for Storage Groups on Retrospect Mac. And I don't expect that to be fixed in Retrospect Mac 18.0—according to past practices due to be released in early March 2021, because AFAICT StorCentric management has demanded the Retrospect "Inc." GUI engineer give priority to supporting the Windows/Mac Console needs of a "backup server" release running on a Drobo/Linux NAS.
  12. (Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. The same is true of Retrospect's history, especially with references to here.) AlexB, WRT "embedded" Rules, it appears this 2014 post by jotrago is the best analysis in the Forums. Note—however—that the post appeared in the "Server, SBS and Multiserver" Forum, and that it uses the Retrospect Windows term Selectors instead of the Retrospect Mac term Rules. IMHO that doesn't make any difference to the question you raised, because—although the GUIs differ—I doubt that the Retrospect engineers went to the trouble of developing two different sets of underlying implementation code. If you question my doubt about their going to that trouble, look at pages 366–376 of the Retrospect Windows 17 User's Guide.
  13. (Disclaimer: Anything I may say about the intentions of Retrospect "Inc." in this or any other post is merely the result of "reading the tea leaves", the "tea leaves" being documentation and public announcements supplemented by an occasional morsel from Retrospect Sales. I have never been paid a cent by Retrospect "Inc." or its predecessors, and I pay for my upgrades. Any judgements expressed are—obviously—mine alone. The same is true of Retrospect's history, especially with references to here.) jethro, My Retrospect installation uses a LAN between rooms in my apartment, so I don't have a VPN. 1) However my understanding of VPNs, which is basically contained in the lead of this Wikipedia article, is that no special special procedures are required if the client machines' addresses can be uniquely defined via subnets per pages 24 and 74 of the Retrospect Mac 17 User's Guide and ports 497 and 22024 can be opened throughout the VPN for both TCP and UDP per page 227. But consider Nigel Smith's item 1. in the post directly below. 2a) The last paragraph before the P.S. in the post linked-to in my next paragraph mentions a separate VPN Backup feature. However that paragraph talked about a preceding sub-Appendix that was later removed from the published Mac 17 UG. Besides, the feature was AFAICT merely a different Tag for Remote Backup—so maybe it was removed because of Nigel Smith's item 1. in his post immediately below. 2b) Remote Backup is required for VPN backup when 1)'s "if" can't be satisfied; i.e., the "backup server" doesn't have a unique address for a "client". This is typically the case for Work From Home, but AFAICT Remote Backup was designed in 2018 for another atypical case described in the fifth paragraph of this post in another thread. The rest of that post describes the consequences of the 2018 kludge in the design of Remote Backup. I've submitted a feature request Support Case—per my suggestion to Alanna in that post, requesting that the kludge be remedied by treating a manually-defined Tag that has the prefix "Remote Backup Clients" as indicating it is eligible for Remote Backup with a script that specifies a Tag with that prefix. IMHO the Retrospect "Inc." engineers would respond that the multi-threading capabilities of a Storage Group—about which I updated the post when I became aware of them—would eliminate the kludge without implementing my request. However the preceding post in that same thread hints at the GUI deficiencies of Storage Groups in Retrospect Mac (per this post in a later thread)—deficiencies that don't exist in Retrospect Windows. I have repeatedly recommended that Retrospect Mac users stay away from Storage Groups until the GUI deficiencies are fixed, which apparently won't happen soon—because my information is that Retrospect "Inc."'s recently-hired GUI expert has been diverted to developing Mac and Windows Consoles that can communicate with the forthcoming "backup server" implementation on Drobo and other Linux-based NASes. 3) Definitely upgrade to Retrospect Mac 17 if you're going to use the Remote Backup and/or Storage Group features; the cumulative Release Notes show there have been a lot of bug fixes. Three Retrospect Windows enhancements to 17.0.1—not yet for Mac—are (I've shifted Scheduled to the front): However those haven't yet been documented, because the Rothschild family would surely use a space-based laser to burn đŸ€Ł (that's a Marjorie Taylor Greene joke) the Walnut Creek CA headquarters of Retrospect "Inc." if they published an updated version of the Retrospect Windows 17 UG or KB article.
  14. oslomike, I don't understand how your different product for daily disk backup could achieve the result you said you were looking for in this up-thread post. Nigel Smith's post further down the thread basically said you would have significant difficulties achieving that automatically with date-based rules, which why I suggested in the next post that you achieve it with minimum manual effort using project-based rules. I don't believe there is any other backup application that has the equivalent of date-based rules that are more flexible than Retrospect's. I also don't believe that any backup application could have the equivalent of project-based rules that are more flexible than Retrospect's. I might be wrong in my second belief, because the advent of the GDPR's "right of erasure" has probably unleashed a storm of creativity among the developers of backup applications. However, given the wide variety of ways in which various commerce applications could store customer-identifying data—which is what the "right of erasure" is all about, I suspect that the GDPR solution for any backup application would have to have the same kind of flexibility that Retrospect's use of Rules in Grooming provides. And that kind of flexibility would require the same kind of minimal manual effort as an adaption for project-based Grooming. Please Private Message me with the name of the different product you plan to use for daily backup. I'd ask that you not post it on these Forums, because past experience has shown that the long-time head of Retrospect Technical Support "gets his knickers in a twist" when a Forums post mentions the name of a competing backup product. However I think he'd make an exception for backup products mentioned in this Knowledge Base article, which consist of one competitor that is much more expensive than Retrospect plus the free-but-limited Apple Time Machine. I just checked the manual for the much-more-expensive backup product, and it doesn't seem to have any capability that Retrospect Mac Rules don't have. As for Time Machine, we know its date-based filtering is more limited than Retrospect and its project-based filtering is essentially equivalent to Retrospect's.
  15. AlexB, Guided by Nigel Smith's mention of "is like" in his post immediately above, I did a Forums search and struck gold in this 2010 post by kswisher. So "is like" provides a wildcard capability, but there apparently is no regular expression capability. Page 432 of the Retrospect Windows 16 User's Guide says—for Find (in code borrowed for Rules?)—that the character '*' can be used to match multiple characters, and the character '?' to match a single character. Observe that, in the 2010 post, ", works" after a condition is a note meaning it worked for kswisher's test and ", not work" after a condition is a note meaning it didn't work for kswisher's test. It probably would also be worthwhile to read preceding posts in that thread. "is like" is mentioned on page 168 of the Retrospect Mac 16 User's Guide, which I prefer to use because it had not yet been subject to the tender ministrations of the StorCentric Slasher (see the P.S. of this October 2020 post).
  16. AlexB, First, this 2012 post for Retrospect Mac 9+ by the very-knowledgeable Don Lee says "There is no 'wildcard' or regular expression capability in the rules ...". Pages 440–441 of the Retrospect Windows 16 User's Guide says Retrospect Windows has a "wildcard" capability for Selectors. Second, both the first screenshot on page 167 of the Retrospect Mac 16 User's Guide and the last screenshot in this Knowledge Base article show a trailing slash at the end of a "contains" path specification. A Mac Path should end with a forward slash; a Windows Path should end with a backslash.
  17. DavidHertzberg

    Error -2,265 during grooming

    ByTheC, Let's consult the cumulative Retrospect Mac Release Notes. First, notice that the Knowledge Base article you cite was last updated 1.5 years before your version 15.6.1 of Retrospect Mac was released. It's by no means inconceivable that in that time period error -2265 was expanded to cover another error. Second, WRT what Lennart_T posted, notice that in release 17.0.0 "Grooming: Fixed issue where groom failure could cause catalog errors after a rebuild (#8457)". Is it possible you did another grooming run before you recreated the Catalog File on 1/26/2021? P.S.: Nigel Smith, in the first sentence of his post directly below, shows that his recall is excellent.😀 See the last sentence of the Note near the bottom of page 186 of the Retrospect Mac 16 User's Guide.
  18. DavidHertzberg

    OWC LTO tape drive compatible?

    mackeymouse, This qualified device list doesn't show any entries—from any manufacturer—for Thunderbolt (even Thunderbolt1) LTO drives. But don't take that as up-to-date; my SCSI HP DAT72 drive was qualified by Retrospect Inc. on a date 6 years after I (temporarily) stopped using it. However, when I searched that list again, it showed an entry for the mLogic mTape LTO-8 as Qualified but not tested in-house on 6 December 2019.
  19. oslomike, I can see now that I didn't read this up-thread post by you and its immediate successor carefully enough.😔 What you are calling your "archive" is an LTO Tape Media Set containing—ideally—every version of every file your installation has ever created. But that "archive" is too clumsy for "returning customer" restores, so you also want a "For Fast Restores" Disk Media Set containing only what you consider to be "active projects". The problem's that you want Retrospect to automatically delete from "For Fast Restores" all backed-up files—and only those files—that no longer belong to "active projects". As Nigel Smith has made very clear, you're just not going to be able to get that result automatically using Retrospect's set-it-and forget-it Grooming based on any kind of dates associated with a file. IMHO the best you'll be able to do is to get that result with a minimum amount of manual effort, based on using the "seekrit" v15 Grooming-with-Rules capability described in the second paragraph of my last up-thread post. And you'll only be able to get that result if you keep each project's files in one or more separate folders, which I suspect you do—or you wouldn't have stayed in business long.🧐 Here's a minimum-manual-effort approach using Apple's macOS 10.13 High Sierra Notes.app, which I've never used but is described in this iMore.com "Mastering High Sierra" article: Start Notes and create a new Note, then add a table to which you add a column (maybe you won't have to do this; the article's sections are inconsistent on the default number of columns) so that it will contain a 3-column row for each "active project". The first column in each row will be your name for the project, likely including client name and "album" name. The second column in each row will be the year-month-day last-activated date for the project. The third column in each row will be the path fragment to the project's folder on your SAN. If there can be multiple folders for a single project, in separate paths, I suggest adding additional columns rather than trying to cram multiple path fragments into the third column. Add a row for any project after the first one, for which 2 empty rows will have automatically been created—I suggest putting column titles into the first of those 2 rows. Then, each time a project is re-activated, change the last-activated date in the second column for its row and drag that row to the bottom of the table. The result will be a table whose rows are sorted least-recent-to-most-recent on last-activated date. (Incidentally, if you can do this with a spreadsheet application instead of Notes.app, feel free to do so—using automatic year-month-day date-sorting on the second column.) Then, every few days look at the Note—noticing any rows whose second column is now more than 24 months old. For each such "inactive" project, create per the last sentence of the second paragraph of my last up-thread post a Rule with the contents of the third column of the row replacing the KB article's path fragment /Users/Bob/ (don't forget to include a trailing forward-slash) in the last Mac screenshot in the Knowledge Base article. If you have more than 3 non-empty columns in the row, click the '+' button and add extra lines to the rule with all fields the same as the first line except using the path fragments from the additional columns, and make sure Any is in the top-left popup. Give the new Rule the name "Remove" followed by the project name from the first column in the Note row, and click the Add button. Then click the radio-button at left of the Rule you have just created in the Rules tab of a Groom script created per page 140 of the Retrospect Mac 16 User's Guide—after check-marking the "For Fast Restores" Media Set in the Media Sets tab, and click the Run button to run that Groom script immediately—unless you want to use the Schedule tab to run that Groom script later. After the Groom script has run successfully, you'll want to remove the row for its now-Groomed-out project from the Note. This section of the iMore.com article at least tells how to delete the contents of all the row's cells. The "Manage rows and columns" section of this support.apple.com article—which appears to be more comprehensive than the iMore article—tells you how to delete the row. You may also want to delete the project-specific Rule—if you don't want to save it for later duplication and modification into another Rule; see the P.S. below. This approach eliminates the use of the Copy Media Set script discussed in the third paragraph of my last up-thread post. You won't need that—or its Include Rules corresponding to the Exclude Rules, because you're already running a backup to your "archive" Tape Media Set every night. P.S.: In case you've not understood "Working with Rules" on pages 164–165 in the Retrospect Mac 16 User's Guide, the GUI for Retrospect Mac 8 was designed assuming that a Rule could be used in multiple scripts—so it's defined by clicking the Rules tab in Preferences. A Rule is specified to be used in a particular script by clicking the Rules tab for that script—which shows all the Rules that have been defined, and clicking the radio button to the left of any Rule you want to use. This GUI was not modified when the use of Rules in Groom scripts was added to Retrospect 15.1, but it's not too clunky for the purpose described in the fourth paragraph of this post—provided you use the Preferences facilities for "Duplicating Existing Rules" and "Deleting Rules" described on page 170 of the UG.
  20. oslomike, On second thought, I agree with Nigel Smith that the relevant definition of small-'a' "archive he describes in this up-thread post, rather than the big-'A' "Archive" definition described in this earlier up-thread post, is the one relevant to your needs. In that respect I think you should consider using a "seekrit" capability of Grooming scripts that was introduced in Retrospect 15.1. This "Grooming Selectors" capability—although the Retrospect engineers evidently "busted a gut" creating it in time to meet the deadline for the GDPR's "right of erasure"—is documented only in this Knowledge Base article, because it was created too late to be described in the "What's New" chapter of the User's Guides based on 15.0. (The "What's New" chapter of the next edition of the User's Guides based on 16.0 is primarily about the glories of the Management Console—created as a key part of Product Management's ultimately-unsuccessful "go big or go home" strategy. The policy of the august Documentation Committee described in the last sentence of the first paragraph of this even-earlier up-thread post meant that the capability could not be documented in any other chapter of the UGs for versions later than 15.) The "seekrit" is that you can create one or more conditions that can specify any directory or filename or other criterion that would identify a particular project, to be used in the Exclude section of a Rule (the post-Retrospect-Mac-6 term for Selector) in a storage-optimized Groom script's Rules—per "Adding or Editing Rules" on pages 166–170 of the Retrospect Mac 16 User's Guide. You can then adapt these same conditions as a companion Include-section Rule for use in a Copy Media Set script's Rules tab. The two scripts, when the Copy Media Set script is run—with results checked—before the Groom script, "archive the project" onto the destination of the Copy Media Set script while removing it from the source of the Copy Media Set script. The article implies the Options tab for the Media Set being Groomed need only specify "Performance-optimized grooming" in the popup; if that's wrong, also specify "Groom to Retrospect-defined policy" with 999 in the "Months to keep" box. Of course you'd have to upgrade to at least Retrospect Mac 15.1 to use this capability, though I recommend Retrospect Mac 16.6. I suggest you phone European Retrospect Support and speak to a salesperson; you probably can negotiate a reduced price for an upgrade to a not-the-latest major version.
  21. Gintzler, When you said "a disk media set", I assume you meant a Removable Disk Backup Set—which in Retrospect Mac 8 was converted into the Disk Media Set while being eliminated in its existing form (except in Retrospect Windows)—because the "superfloppies" it was intended for had stopped being manufactured. So you got that working for USB -connected disks? Anyway, page 154 of the Retrospect Mac 6 User's Guide mentions—in discussing the Media Action button in the Options Tab for a Backup Set—discusses the Skip action. I think that's what you needed in 2019. From Retrospect Mac 8 onward, Skip to New Member—page 96 in the Retrospect Mac 16 User's Guide—is a Schedule Tab option for an individual run of a script instead of a Media Set option. Have you considered upgrading to Retrospect Mac 16? That will still run under OS X 10.6.8, and I'm myself running that version under macOS 10.12 Sierra. By reading from here to here in my Ars Technica thread about Retrospect, you could learn what isn't in the UG and switch over in about 5.5 hours of work. Since you're backing up from a Windows file share, maybe you don't need Mac OS Server anymore—which would mean you could run the Desktop Edition instead of the Single Server Edition of Retrospect Mac 16. In any case, you could see if this discounted upgrading offer is still in effect.
  22. Gintzler, The second paragraph of this Knowledge Base article on error -43 says Also, since you are backing up from a mounted Windows file share, look at the "Illegal Characters in File Names" section on page 111 of the Retrospect Mac 6 User's Guide.
  23. DavidHertzberg

    Wish to Change Destination Media

    Ultrachanel, In the traditional IT phrase, "RTFM". Since you've an allergy to stating what version of Retrospect Windows you are using, I'll refer to the Retrospect Windows 16 User's Guide. Read as much of pages 373–387, which is easily findable as "Managing Backup Sets" in the Table of Contents, as you need. After creating your new Backup Set(s), change your scripts—for which starting on page 390 would be good mental exercise. Here's where to find User's Guides from previous releases.
  24. oslomike and Nigel Smith, Let's get our terminology in sync with Retrospect's terminology, which is mostly 30 years old and wasn't adopted by the rest of the IT industry. I'll refer to the Retrospect Mac 13 User's Guide, which is—fortunately for this thread—the first Mac version where the august Documentation Committee stopped copying the contents of the previous "What's New" chapter into other chapters of the UG (later converting the "What's New" chapter into marketing fluff): Page 144 says about "archive" That concurs with your use of "archive", except that Retrospect has a particular type of script named Archive—described from the rest of page 144 to the top of page 146. An Archive script does what the quoted paragraphs say, but as a version of a Backup script with some enhancements and some limitations. One of the enhancements is an option to delete from the Source (Nigel Smith "move") the data that has been backed up to the Destination. Page 15 shows the latest version of the "Grooming" dialog for Retrospect Mac. Pages 221-223 describe Grooming of a Disk Media Set, but they have not been updated to include the Months to keep specification shown (above v13's "Performance/Storage optimized" popup) for Groom to Retrospect defined policy in the dialog on page 15 —an enhancement that was added in Retrospect Mac 12. Pages 163–164 tell how to create a Groom script. What Nigel Smith calls a "filter" is called a "custom Rule" in Retrospect Mac; it used to be called a "custom Selector" before Retrospect Mac 8, and is still called one in Retrospect Windows—despite its having the capability of excluding files (which is why Retrospect Mac 8 renamed it a Rule). Creating one is described under "Adding or Editing Rules" on pages 195–199; using them—as well as "built-in Rules"—is described on pages 193–195.
  25. oslomike, Based on announcements made at the time of its 2019 acquisition by StorCentric, Retrospect Inc. had about 20 employees—with most working from home. It has never in its 30-year history had any hardware-related capability. In fact before Dantz Development Corp. was acquired by EMC in 2004, Dantz used to get driver source code from the manufacturers of various kinds of tape drives—and hire contractors to rewrite that code so it would interface with Retrospect Mac and Windows. That's how Retrospect at the time of its acquisition by EMC had cornered 90% of the market for Mac backup software, and more Windows users than Mac users. (EMC end-of-lifed Retrospect Mac after disk-destination Time Machine was released.) Sometimes the manufacturer's driver code would have bugs, and sometimes the contractors would introduce bugs—which is probably why Retrospect Mac 6.1 can't use the hardware compression capability of my HP DAT72 tape drive. A lot of Retrospect's terrible reputation among IT old-timers, which they've expressed to me in my 4-year-old Retrospect thread on the Ars Technica Mac forum, results from the defects of its tape drivers—note that the linked-to post says another Windows 2000 app's AIT driver worked better. It sounds as if there might be a bug in the Retrospect Mac 10.5 AIT driver code, although it might use an AIT driver provided by Apple in later versions of Mac OS X. Your idea of copying your AIT Tape Backup Set to an LTO tape using Retrospect Mac 6.1 is excellent, because LTO is an industry-standard tape format with less flexibility for drive manufacturers.