Jump to content


  • Posts

  • Joined

  • Last visited

  • Days Won


Lennart_T last won the day on October 18 2021

Lennart_T had the most liked content!

Profile Information

  • Gender
  • Location
    Helsingborg, Sweden

Recent Profile Visitors

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

Lennart_T's Achievements


Apprentice (3/14)

  • Very Popular Rare
  • First Post Rare
  • Collaborator Rare
  • Posting Machine Rare
  • Week One Done Rare

Recent Badges



  1. That clearly looks like a bug. You should contact support: https://www.retrospect.com/en/support/phone
  2. Not sure what you mean by "import" as that is not a Retrospect operation, as far as I remember. You should select "Media Sets" in the list to the left and then "Rebuild".
  3. Oh, and 38 past backups seems like a lot. Maybe you should try (temporarily?) to keep (say) the last 10 backups?
  4. Retrospect creates backup files that are around 650MB in size. With performance-optimized grooming, they are all kept intact until all its contents can be groomed out. This often means that hardly any data is groomed out and that can be the source of your problem. With storage-optimized grooming these files are shrunk as old backups are removed from them, one by one.
  5. I see. Getting a RAID (or two) into the equation makes it more complicated. I have never used Retrospect with so much data. How many backups do you have stored on the 85 TB disk? How much data on the 50 TB source gets changed daily (or weekly)? What kind of files are they? Database files that gets updated by the minute? Or video files that "never" changes? What groom settings did you use when you groomed?
  6. Let's see here. You mean 50 GB on your source drive (not TB), right? Otherwise you must have a small stack of external disks to store 50 TB. As for your backup drive: I asked the size of the drive and 85 TB is a slightly larger stack of disks. And if you mean 85 GB? Well, you can't buy disks with that size. So what size is the disk really? Repairing the backup disk means fixing any errors in the disk directory. Think of it as the index of a book. If the index gets corrupted it would be difficult to find the page you are looking for. How to repair: https://support.apple.com/en-us/HT210898
  7. How much data are there on your source drive? How large is the backup drive? Have you repaired the backup drive with Apple's Disk utility? What version of Retrospect? What version of Mac OS? To see what has been backed up: Click on "Past Backups" and then on "Browse" for the backup in question. Click on the checkbox at lower left and then on the disclosure triangle to see what was backed up.
  8. It's been some years since I used proactive scripts, so things may have changed how they work. And I also may not remember everything correctly. Back then (I think) the time between backups was measured from the end of the last backup to the start of next, so I had to set that to 23 hours (instead of daily) to get the next backup of that source to start a little earlier "tomorrow" than it ran "today". Otherwise it may miss the active window. The active windows was set to normal business hours plus one hour at each end to cater for those who came a bit early and those who had been on the road and arrived late. Perhaps you should set up the proactive script to run between (say) 6 AM and 8 PM. That should be ample time for the backup to finish. Except, perhaps, with the exception of the very first backup for each backup set. As for why your backup terminates at midnight, I have no idea. It shouldn't do that. Perhaps you could share a screenshot or two of your script settings?
  9. How old are they and how much have you used them? Old hard drives are failures waiting to happen. (On the other hand, it's many years ago I had a drive fail on me, even after years of use. ) No. Most files nowadays are already compressed and can't be compressed more. It's just a waste of (CPU) time and energy. Anyway: With that kind of data, you should be fine using the setup you have proposed with 2 sets of 3 backup drives. They should be large enough. I would not use block level incremental backup. That's useful only for very big files where you change only parts of the files, such as database files. I would use Disk backup sets, not storage groups. You should probably run a Groom script every once in a while, to groom out old backups. (You don't HAVE to, as Retrospect will do that for you when the disk becomes full. BUT that will happen in the middle of a backup and according to Murphy's law it will happen when you are in a hurry to get the backup finished.) Hope this helps.
  10. How much data is there on E: X: and Y: respectively? As a rule of a thumb, you should allocate storage about twice the size of the DATA you want to backup. Instead of two sets of three backup disks, you may want to have two larger disks. Seagate has disks with 16 TB capacity as well as 8 TB for about 40% of the price for the 16 TB disk. With larger disks as backup disks, you need only two backup sets. That way you can use "grooming", a process that "grooms" out the oldest backups. That way you don't have to erase all data to start copying x TB of data from scratch.
  11. I remember seeing something similar, but that was years ago. Please provide some facts, such as which version you (they?) are running and what the emails say.
  12. For my former employer, I managed Retrospect as a small part of my job. We had about 70 computers, divided into 4 disk backup sets. The clients were divided by platform (Mac/Windows) and then by department (development vs. others). Each group of clients had their own backup set. So we had four executions running at the same time. Then we had a tape backup set for off site storage. Every weekend we transferred from each of the four disk backup sets to the tape backup set. The disk backup sets were then groomed. Perhaps you could do something similar: Having four small backup sets, groomed to keep the last (say) three backups and one large disk backup set, transferring the last backup/snapshot for each client from the small sets to the large every night.
  13. Yes, Yes and No* *) I'm almost 100% sure that data deduplication was part of Retrospect 3, which was the first version I used. Yes, of course. A backup set doesn't "know" about any other backup set and its contents.
  14. Yes, that is the default (and has always been). However, Retrospect also looks at the file metadata, so a file that has identical content, but different modification date (for instance) will be backed up twice. That means that a lot of Windows' files will be backed up multiple times, even if seemingly identical, because their metadata is different. Windows updates, for instance, does not run on exactly the same time on identical computers, so updated files will be different.
  • Create New...