Jump to content

Lennart_T

Members
  • Content count

    4,105
  • Joined

  • Last visited

  • Days Won

    71

Lennart_T last won the day on April 6

Lennart_T had the most liked content!

Community Reputation

151 Excellent

About Lennart_T

  • Rank
    Retrospect Veteran

Profile Information

  • Gender
    Male
  • Location
    Helsingborg, Sweden

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Lennart_T

    Disk-to-Disk-to-Cloud?

    I suggest you try a proactive script for laptops. That script will poll for the presence of any laptop on the network and start the backup as soon as it is available. https://www.retrospect.com/en/documentation/user_guide/mac/operations#proactiveai-backup
  2. Lennart_T

    Disk-to-Disk-to-Cloud?

    What will you be backing up? A laptop that might not be connected for la long time? Then a disk-to-disk-to-could backup would be good. A server idling anyway during the night? Then direct to cloud is easiest.
  3. Lennart_T

    Retrospect 17 and low-end users

    Don't try to fix what isn't broken. If Retrospect is doing everything you need it to do, there is no reason to upgrade.
  4. Interesting. I was indeed right.
  5. No, not in the "Summary" pane. Try the "Options" pane. Also try what I wrote in a previous reply.
  6. I think (not sure) that you should double-click the catalog file (in Windows Explorer) while the backup is NOT running.
  7. Lennart_T

    Curious (spurious?) verify error?

    My best guess is that you got a (temporary) read error from the disk during the verify. An error that is not repeatable. The MD5 digest is stored either in the catalog file or in the backup set itself. It is created/stored during the backup. What happens if you run the verify again? How is the disk connected to the computer? (USB isn't one of the most reliable types of connection.)
  8. Lennart_T

    Chipset Driver update broke Retrospect

    That will not be very informative 6 months (or more) from now.
  9. Lennart_T

    Files backed up again

    I found a solution, which work since this is just a data disk, not a system disk.
  10. Lennart_T

    Errors when laptop not connected

    Can you post that part of the log?
  11. Lennart_T

    Errors when laptop not connected

    You should get only one error and that is -530. What do you get?
  12. Lennart_T

    Files backed up again

    Hello and thanks for answering. A bit of digging revealed: "ext4" No, I did not. Yes (even within the same second) and yes. Only two files inside an application package (and they are quite small). I will try SSH later. I do have both the original disk I copied over to the NAS as well as backups. Do you think turning up logging in the "secret settings" will show anything useful? I will try a favo(u)rite folder with that. Regards, Lennart
  13. I run Retrospect 15.6.1 on Mac OS X 10.11.6. I had my media files (audio and video) on an external USB hard drive connected to my Airport Extreme. I did have some problems with unchanged files being backed up again and again, but I didn't really investigate since I was about to buy a NAS. Now I have a Synology DS218j as a NAS server. The audio and video files were copied over to the NAS, 2.1 TB in total. Then I ran a Retrospect backup with the Synology volume as the source to a media set that I had been using. 1.7 TB of files were backed up. Fair enough, since the metadata probably has changed. Then I immediately tried another backup from the Synololgy to the same media set. Retrospect wanted to backup a whopping 723 GB again. Why? What is going on? Is there a way to get Retrospect to tell me why it thinks it needs to backup all those files and what can I do about it? Bonus question: Is there a utility that can check and correct the file dates (for instance) so they are not somewhere in the future? I have TechTool Pro 11, but that does not seems to do the trick.
  14. Have you done any changes on the selector "All files"? If "yes", check those changes. If "No", I would check the source disk(s) with CHKDSK or something more powerful.
×