[Borgbackup] delete and prune use consume gigs of data

[Jim Popovitch]

On Fri, 2023-05-19 at 18:17 +0200, Thomas Waldmann wrote:
> > > If that folder wasn't there before, borg had to do a re-sync of
> > > the chunks index. This is needed for prune/delete operations
> > > because it contains the refcounts for each chunk.
> > > 
> > > Once the resync is done (and while it stays in sync), it will
> > > work quicker and with much less traffic.
> > 
> > Thanks for the explanation, indeed that folder was not there
> > before. The backups are done from servers directly to remote
> > storage, and I was doing the pruning from my laptop.
> 
> > Now that the servers have produced more backups (to the remote
> > storage), should I expect to see ~/.cache/borg grow larger on my
> > laptop the next time I prune?
> 
> Yes, as soon as you do more backups from another machine to the
> repo, it will need to resync the chunks cache again and for doing
> that, it will fetch metadata of all new archives, build
> corresponding per-archive chunks indexes in the cache and compute a
> new overall chunks index from these cached per-archive chunks
> indexes.
> 

Got it, Thanks!!

-Jim P.