Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation since 12/07/2021 in Posts

  1. I accidentally deleted 21 very detailed scripts. Retrospect Support saved my bacon by giving me the following advice: Locate and recover a backup copy of the file configs.xml that predates the date & time you deleted the script(s). On Mac, this file normally is in MacHD/Library/Application Support/Retrospect. Go to this link: https://www.retrospect.com/en/support/kb/server_configuration_management On that page, go to this link: Retrospect for Mac - How to Import Engine Configuration and follow the instructions for Importing. When you click on File/Import in Retrospect, you'll see the Retrospect Import Window. In that window, deselect all but the Scripts option. When you click OK in the Retrospect Import Window, a Finder window will open allowing you to select the recovered configs.xml file. After that, you should see all your missing scripts repopulate the Scripts window in Retrospect.
    1 point
  2. Thanks, Lennart_T. Creating a new script with the same source and media set seems to have worked. That saved me a lot of time!
    1 point
  3. Make a new script in Advanced mode with the same options, source(s), destination, and selectors as the script you are worried about and then "Preview" to see what's going to happen.
    1 point
  4. Thanks Lennart. I got it working by uninstalling Retrospect, downloading the archive copy again, and reinstalling. I suspect that the cause of the problem was that I had not downloaded the correct version; perhaps I had downloaded a non-USA version. In any case it is working now.
    1 point
  5. Support has just confirmed this is a bug. It apparently only affects MacOS Monterey.
    1 point
  6. One time move. So my plan now is to retain all the existing backup sets as read only for archival purposes because I know I can reliably restore from them on the Mac, and start all new for current backups and going forward.
    1 point
  7. Directions are at https://www.retrospect.com/en/support/kb/retroisa_advanced_options
    1 point
  8. Retrospect actually stopped *officially* supporting optical drives way back in version 8 or something! But, as far I know, the instructions for enabling optical device support are still valid. OS compatibility info for RS v15 is here. Yes, the file that needs editing is in the Library folder of the boot drive, which might explain why you are seeing the disclosure triangle in OS 10.11 but not 10.12 -- I'd have thought that CCC would have copied *everything*, but maybe not.
    1 point
  9. Ah that is great news, thanks. I have separate backup sets for all my clients, so this would then mean that I can have parallel backups of each, which is exactly what I had hoped for. Yes, I had seen that all subsequent updates were primarily about supporting the latest Windows versions and seasonal releases. I never ran into issues backing up, but like you state, the main question is also about restoring. I admit that I have not tried to restore anything yet with Windows 11 so maybe I was running a risk there that I wasn't even realizing. Which reminds me to soon do a couple test restores again. Anyway, guess I will be upgrading to 18.
    1 point
  10. Without storage groups you can backup one client to one destination at a time. Which means that with multiple destinations (backup sets), you can backup multiple clients simultaneously. That could make sense if you group your clients according to where they belong in the organisation. For instance, finance department computers use the finance backup set, production department computers use the production backup set and so on. Each department can then be backed up simultaneously as the departments. With storage groups you can have a large backup set for all computers and several clients can be backed up to that backup set simultaneously. Having a single, large, backup set may or may not be an advantage. Besides, version 12 is outdated by now. For instance, recent Windows 10 versions are not supported and not Windows 11. If you run older versions of Windows you may be fine with Retrospect 12, otherwise I would not trust it to restore without problems.
    1 point
  11. That could be a possibility. I'm still fairly new to the job, only been here for 6 months and Retrospect was handed off to me by my predecessor. I guess this could have happened before I got hired and our backup drive was just slowly filling up without anyone noticing (I personally didn't even know what to look out for at the time because I was so new and inexperienced). I basically had to learn Retrospect as I went while trying to solve this problem. Everything seems to be working fine now; our backup drive matches our master drive and all backups have been running smoothly for the past week.
    1 point
  12. I made sure the Retrospect Product Manager saw your document.
    1 point
  13. Thank you for the thoughtful and well details article. I am sure other users will find it helpful. side note: I see some access keys and secret keys in the article. I assume those are generic and do not expose anything private. And for the record, we fully support most models of NAS devices and that will never change. We want users to have the most flexible backup storage solutions available.
    1 point
  14. Case opened with support. They are saying it does look appear to be a bug. The first recommendation to complete the verification was to start a verify, insert the member following the defective one, then click Proceed. But I can't - the Proceed button is still greyed out in that situation.
    0 points
×
×
  • Create New...