Trigger sync to secondary destination?

Support
1

Is there a way to trigger the sync to a secondary backup destination without starting the backup job itself?

Background: I already have a full backup at the primary destination and only want it to sync to the (newly added) secondary destination without creating a new backup version.

And as a follow-up question: Would it be possible to run the actual backup job from e.g. my laptop but do the syncing to the secondary location from another machine (home server)? So I don’t have my laptop running during big sync jobs?

2

Ok, looks like i managed to find an answer to my questions. I wrote a powershell script utilizing the SyncTool. Easiest way is to create the job with both destinations in the UI and export the job config.

From there you can copy & paste backend_src and backend_dst (TargetURL in the *.json file)

3

As far as I know, the do-it-yourself approach is all there is, without backup.
One could set dry-run on backup. It’s a little lighter, but that’s slow and ugly.

4

One could set dry-run on backup

Oh, that’s a clever approach. But wouldn’t dry-run also apply to post backup sync?

5

Seemingly not. I tested it. Some might think it should.
If this changes, then your DIY approach will still work.

6

I agree --dry-run should apply to sync as well.

Generally the sync just kicks in after the backup, but if you want to not create a new version, your workaround with the sync tool seems to be the cleanest version.

You can use the SyncTool to do that, but it will not integrate directly, so you need to either kick it manually or have a script that somehow triggers the sync to run from a different machine.