Jump to content

Nigel Smith

Members
  • Posts

    365
  • Joined

  • Last visited

  • Days Won

    27

Nigel Smith last won the day on July 28

Nigel Smith had the most liked content!

Profile Information

  • Location
    UK

Recent Profile Visitors

1,215 profile views

Nigel Smith's Achievements

Rookie

Rookie (2/14)

  • Dedicated Rare
  • First Post Rare
  • Collaborator Rare
  • Week One Done Rare
  • One Month Later Rare

Recent Badges

31

Reputation

  1. It's probably me -- I'm a Mac rather than Windows user. But pp12 of the Windows RS v17 manual shows a "Preview" button, so I think the functionality is there if you dig around a bit.
  2. 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.
  3. Note that the error is actually "...stopped by operator", not user. IMO that means it is being stopped on the Retrospect "admin" side, not at the client. Have you set a limited schedule of execution, a media timeout, or similar? Is something going into power save/sleep just after midnight, effectively pausing the execution until the timeout is reached?
  4. In theory it could, but I've never tried. If you're worried about HD thrashing, think how bad it would be for a tape, constantly spooling/respooling to find those gaps to fill! If you want to do grooming and WORM (form ransomware protection etc), consider an HD for your "normal" backups and a regular copy from that set to a tape set for "permanent" storage -- disk-to-disk-to-tape. There's many ways of setting that up and you can adjust to suit your own schedule and retention policy. See the RS manual, particularly the "Staged Backup Strategy" examples.
  5. Retrospect shouldn't care, as long as the card works. Windows and your HP drive may have other ideas, so aim your compatibility checks in those directions. Where that theory breaks down is that RS can pump a lot of data through a card at speed, and that can reveal flaws in card design,ompatability. To an extent you get what you pay for... If your data is valuable enough that you're going to spend time backing it up, perhaps it's worth splashing out a little?
  6. For clarity -- which? I assume the "backing up the directly-mounted NTFS disk". but just want to be sure... I don't know if that's what's actually going on, but in general Retrospect (like all good backup software) makes the not-unreasonable assumption that "if there's any doubt, back it up again". In the vast majority of cases it much better to "waste" resources doing that than to find that the latest version of "My Very Important File.doc" can't be restored because, well, it kinda looked the same as the last one so RS didn't bother... Where it does bite is this kind of platform move. Having been there myself, I feel for you! What I do these days is start new sets on the new platform, run old and new in parallel until new is up to date, then archive the old in case it's ever needed.
  7. Have you tried changing the "Back up:" selection on the "Options" from "All Volumes" to "Selected Volumes" and ticking only the ones you want to back up (assuming that only show one entry per volume, of course!)? It's not something I've come across but, IIRC, there have been other mentions on the Forum of APFS volumes showing up multiple times. A good search might find something useful. And if Instant Scan is turned on on the client -- turn if off. Not only is it a CPU hog, it doesn't work with APFS anyway. It may or may not help, but Instant Scan gets blamed for all kinds of nonsense and I see no reason to stop now...
  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.
  9. Does this apply to any and all junction points, or just some? (Remembering the fun people have with OneDrive FOD and similar...) Are the point/target on the same or different volumes? Are you logging any messages about these failures?
  10. First thing to note is that you don't need to restart the client computer to free it up. Open the RS Client and Command-click the "Off" button to set the client to "Not running", then click the "On" button to turn it back on again. Next thing I'd do is try missing out the switch. Can you run a direct ethernet connection from server to client, if only for a test backup? If that works then it's a switch issue -- do you have other devices on the same switch that are being backed up successfully? If the direct connection has the same problem then it's a client issue. If it's client/server incompatibility then updating to 18.5.1 might help, otherwise (assuming you can't update the Lion machine) you'll probably have to rethink your backup strategy eg by using file shares mounted on the server instead.
  11. I think you generate an App Password as described on that page, then use that instead of your Google account password when setting up mail sending in Retrospect. This page should walk you through the process (assuming that the announced change doesn't break things!). The good news is that you've plenty of time to try to get it to work!
  12. By any chance has the volume been erased but left with the same name? Is it, perhaps, a different actual volume but with the same name? IIRC Retrospect uses the volume ID to "register" the volume, not the name, so it might be that something's changed... What OS is the client running? RS v16.5.1 isn't fully compatible with Big Sur or Monterey because of changes to how Full Disk Access works -- you may have fallen foul of that.
  13. Are you using "Locate" to try and add the catalog, and then RS is hanging? Is there anything in the log? As Lennart says, if all else fails you can rebuild the catalog from your tapes -- at least you'll then have access to the data.
  14. What account is Retrospect running in (Preferences->Execution->Security)? What account are you logging in to Windows with? I'm no Windows guru, but I think you only see the icon when logged in with the same account Retrospect is running under.
  15. You can guesstimate it if you've logged the used capacity of your source volume over the last few weeks -- that'll give you the amount of new data. Then the sum of all incremental backups over that time minus the amount of new will give an idea of your churn. But if you've got 40TB on the source, even only 0.5% churn a day plus some new stuff will fill your 80TB target -- especially since, as Lennart says, performance optimised grooming can leave a lot ungroomed. General recommendation for target volume capacity is 2-3 times the source capacity, assuming "regular" usage -- obviously you can get away with less if your data is mainly archival in nature and so doesn't change much. It might be a good idea to go through what was backed up each time (see Lennart's screenshots above) to see what's happening -- keep an eye out for things like database files (sounds like you have a lot of images, perhaps you are cataloguing them somehow?) where a small change will mean a multi-GB whole file backup.
×
×
  • Create New...