Why did the drive fill so quickly

[DeltaGolf]

I have a HB backup to an external USB drive. It all works well until suddenly - and I do mean suddenly - the drive has filled up. I can't work out what is suddenly being backed up to cause this. None of the files or folders listed in the task have increased by anything than the usual amount. I'll attach some screen shots to show.

My fingers are pointing at Active Backup for Business. Regular readers will know it's been causing me trouble. Is it possible that HB is somehow backing up my ABB backup? Or am I barking up the wrong application?

 

[Rusty]

Is it possible that HB is somehow backing up my ABB backup?

What is covered by this backup to begin with? Are ABB archives part of the backup task(s)?

 

[DeltaGolf]

What is covered by this backup to begin with? Are ABB archives part of the backup task(s)?

No, I haven't added ABB to the task. I only mentioned it as HB says "System configurations will be backed up automatically". Clutching at straws...

The only other suggestion I have is I added a large volume to my Synology Drive which I'm now able to access on my Mac desktop. All the files are (should be) set not to download. Unless they're somehow getting backed up, but I'm not seeing them.

Is it me or are the logs slightly less helpful here? Or maybe I needed to have them save mare detail then I'd have a clue as to what has suddenly been added to the task.

 

[DeltaGolf]

Looking around I note I have a large snapshots folder. 148 TB. That can't be right! Total volume is 17.5 odd TB. It really is 148 not 14.8. Actually 148.53 TB.

But according to the screen grabs I posted, all this data has suddenly appeared over the past few days, not an incremental increase.

Still puzzled!

 

[fredbert]

Looking around I note I have a large snapshots folder. 148 TB. That can't be right! Total volume is 17.5 odd TB. It really is 148 not 14.8. Actually 148.53 TB.

Snapshots include 0.img files per snapshot. These are reported by the file system as their fully inflated size (i.e. the physical bit/byte size of the drive they are imaging, not the used size of that drive nor of the image file itself on the host file system). Don't know why it is like this.