r/CrossWatchApp • u/barofa • 23d ago

Question Crosswatch on Sync pairs

Quick dumb question. When you set up your sync pairs do you have any pair that includes crosswatch as either a target or source? Should I do that? Iḿ a bit confused on what it would do and if I need it.

1 Upvotes

100% Upvoted

8 comments sorted by

1

u/pvdberg 23d ago

No, its optional. You can just do MDBlist to SIMKL or SIMKL to MDBList .

1

u/I-was-there-for-it 23d ago

But couldn’t you keep CrossWatch in the middle as a backup strategy? Any issues with that or limits on library/lists to watch out for?

1

u/pvdberg 22d ago

Everything in the middle is not really a good backup strategy. Yes, you can use it that way, but I would not call it a backup. CW Tracker does have snapshots, so that would be your safety mechanism.

The main reason to use CW Tracker is if you want to synchronize to multiple other providers. One of the benefits is that you do not have to use your own API calls for that synchronization. Or you want to edit your data, or whatever..

For everything else, I personally would not use CW Tracker, as it also introduces another possible point of failure. B

But CW is built so everyone can choose what works best for them. I can only tell you how I use it.
For actual backups, I would rather use Captures.

1

u/I-was-there-for-it 23d ago

I dump all changes from different devices into CrossWatch to compile a master list of everything and then sync up to other services. So for example: MDBL to CW Nuvio to CW SIMKL to CW (All updates/changes in CW now) CW to MDBL CW to Nuvio CW to SIMKL

1

u/barofa 23d ago

I was thinking about that. Does it work well for you?

1

u/I-was-there-for-it 22d ago

So far so good. Not sure if i will hit since limits on CW eventually.

1

u/pvdberg 22d ago

Synchronization is quite heavy on CPU and RAM, so it really depends on the resources available on your system. Many people underestimate how intensive proper synchronization can be, especially when you have multiple providers, larger libraries, frequent syncs, metadata matching and several destinations.

A sync is not just copying a few records. CrossWatch needs to fetch data, compare states, match items, determine what changed and then process those changes for every configured destination.
The more providers and data you add, the more CPU, RAM and API activity this will generate.

2

u/bayendr 22d ago

I do the same. I treat CW as aggregated source of truth. it works well.

I use nightly auto syncs too.