I have 2 servers.
both on arm, one on rasperry pi os and one on Manjaro arm.
Both use btrfs on backup storage.
I connected a few clients to them.
They have different paths to backup, ie, the Manjaro server does the same directories MINUS a few ones.
The client I have on my pc shows this behaviour if it has been turned off and powered on during a time where a backup should have been done.
It starts a FULL FILE (but calls it an incremental on the activity web page) on BOTH servers, starting to transfer 1TB when a full on Manjaro would be only 25GB (with the directories I have selected). And a full is NOT what should run, only an incremental with I would guess 100MB.
If I stop them both, and then starts an incremental one server at a time, it “resumes” the backup but with the correct amount, about 100MB on Manjaro and about 300MB on raspberry os.
I have a period of 1 minute before starting backups, I have changed that to 10min on the manjaro server hopefully not “colliding” the backups.
What can I do to remedy this?
If I don’t sit and actively watch the servers when I start up my computer 2TB (1TB to each server) would be transferred taking HOURS!
Yesterday, I actually let the full file continue on my raspberry os server, took a few hours but the registered data uploaded was STILL only 12,4GB (I’m guessing this is all btrfs metadata or something), because of shared_hashes but it still UPLOADED 1TB and it took a few hours.
How do I stop this behavior?
The clients that run 24/7 does not show this behavior.