Jump to content

Leaderboard


Popular Content

Showing content with the highest reputation since 09/20/2018 in all areas

  1. 1 point
    An update will show in Automatic Update and a manual check for updates from within Retrospect a few weeks after initial release. This presumably to allow the early adopters who go looking for the update to find any problems before the rollout to the masses via Automatic Update. As for safe to download and use, well I downloaded and installed it and so far the update has run without problems for me. (YMMV.)
  2. 1 point
    According to the Blog, 15.6 was announced on Tuesday. https://www.retrospect.com/en/blog/2018/10/16/retrospect_15_6 It's available for download now. https://www.retrospect.com/en/support/downloads However: My 15.5 Desktop/Pro does not see an update available Mayoff hasn't announced it here QUESTION: Is the new version safe to download and use?
  3. 1 point
    Actually Monafly isn't misreading what he/she is reading in the Grooming dialog. Retrospect Mac 12 added a Months to Keep entry box to the Grooming dialog, which is described on page 9 of the Retrospect Mac 12 User's Guide. A quick test on my "backup server" shows that (as I expected for compatibility) clicking the Groom to Retrospect Defined Policy button causes Months to Keep to default to 12. Unfortunately that page was part of the "What's New" chapter, and the august Documentation Committee has adopted for the last 4 versions of the UGs a policy of totally overwriting the last version's "What's New" UG chapter with whatever is new in the current version of Retrospect—without copying the last version's "What's New" content to another UG chapter. I have mentioned that policy in other posts; a frank appraisal of it would require me to use the words "heads" and "wedged" and "up" and the third-person plural possessive of the name of the human excretory orifice, which of course I'm too polite to do.
  4. 1 point
    This might help: https://www.retrospect.com/en/support/kb/scanning_incomplete_1103
  5. 1 point
    Thanks, you found what I was looking for, but didn't find. A bit further down in that article: "LTO uses an automatic verify-after-write technology to immediately check the data as it is being written,[42][43] but some backup systems explicitly perform a completely separate tape reading operation to verify the tape was written correctly. This separate verify operation doubles the number of end-to-end passes for each scheduled backup, and reduces the tape life by half."
  6. 1 point
    Lennart_T is, as usual, correct (second paragraph of the section).
  7. 1 point
    derek500, in this 2015 post, gave me the solution. See the remaining posts by me in that thread for further discussion. Although I'm still using Retrospect Mac 14, I routinely use that undocumented dragging-in-the-Details-panel-of-the-script-Summary trick whenever I Remove and re-Add a source. See further posts by me in that thread for an explanation. There's a limitation for local Sources because you can't easily Remove them, as discussed here and in posts that follow it. In any case, the first paragraph of this following post is my explanation of precisely what is the nature of the "alphabetical order" that Retrospect follows in backing up Sources within a script.
  8. 1 point
    Wha is an "august Documentation Committee"? Sounds like fake news, if you ask me.
  9. 1 point
    IMHO what ShadeTek wants is some version of what barup wanted in the OP of this thread. That would probably be because the tapes that are members of a particular Backup Set are not externally labeled as such in ShadeTek's installation. If so, then he/she cannot do "putting in all 8 tapes in one go". There is a facility in Retrospect Mac that allows one to see all the members of a particular Backup Set (called a Media Set in Retrospect Mac), but I don't know if it works for tapes—which I haven't used since 2010—much less what the equivalent facility would be in Retrospect Windows. If ShadeTek wants such an enhancement to Retrospect, here is why and how to submit a Support Case to request it.
×