I attempted to add a second backup location to an existing job. After completing the next run I checked the file size of the newly created backup on the new location and it seems it only contains the incremental backup that was also uploaded to the primary backup location.
Can I force the job to upload a full backup to the scondary location even if the primary location only needs an incremental backup due to older versions already stored there?
Blog post: Built-in 3-2-1 backups through Remote Synchronization
just came out, providing further details about how this should work.
At the bottom, it says it came out in 2.3.0.1. That surprised me too.
I can say I had some trouble before. Maybe you can try updating it.
That should not be the case. After the backup, the full primary destination contents are synced to any secondary destinations.
Not really, as that should be the default behavior.
The change in 2.3.0.1 (and some canary before that) is that it is now integrated in the sense that it shows progress instead of just “hanging” while transfering to additional destinations.
Not sure what went wrong before, but I just updated from 2.3.0.0 to 2.3.0.1 and now get a “Synchronizing secondary destination” message and it seems to work.
Before it also created some files in the secondary destination but not the full backup replica.
Reading kenkendk’s answer it’s possible the process ran in the background before and I never gave it the time to fully complete the process since I couldn’t see any sign of progress.