Discrepancy in backups between storage locations

Support
#1

Seeking if anybody can guide me in the right direction for remediating some troubles that are plaguing me.

I am taking a backup to my local system, from there copying to 3 other off-site storage locations.

I had recovered my process back towards the beginning of the year due to some hardware failures and backups being in inconsistent states. I thought I’d resolved things and let it be for some time.

I’m finding now a pretty large discrepancy between my local (source) backup and the 3 other storage locations causing a ~2.5tb larger backup size on the off-site storage locations.

Is there a best way forward to treat my Local storage as the “source of truth” and get the other 3 locations to get re-aligned to that

As it stands, all 3 off-site storages match up from as far as
Backup IDs & Revisions
Chunks, including pruned revisions and chunks

My Local storage, which is the source these are all copied from differs by:
2 less Backup IDs (I believe this is a result of my recovery efforts back when)
646 less revisions against the Backup IDs
and around 600,000 less chunks

I’m looking for is there would a “most graceful” way to assess where this discrepancy is coming from and get the 3 off-sites aligned to the Local source. Hoping I can do something to address this without having to blow something away.

#2

I’m willing to bet you’ve run into the synchronisation trap. The good news is, you shouldn’t have to start over.

If you are suffering from unsynchronised storages like I describe in the above thread, here’s a clarification on the fix. Basically, don’t do any prunes until you’ve copied the storages every which way - making sure the revision numbers match on all storages.

So A → B, A → C … B → C, C → B … B → A, C → A - should probably cover all possibilities.

Then going forward: 1) use the same prune options for each storage, and 2) run them on the same day.