FAQs

What permissions do I need on the source or destination?

Simple read on the source and write on the destination should suffice.

For precise resume token creation on the source (highest consistency guarantee), write permission is necessary to inject a dummy record.

Can I write on the source while dsync is running?

Yes.

Can I stop dsync and resume later?

Yes, you can. Dsync will not repeat already completed tasks, and will automagically resume from the latest in-progress task.

How can I restart the process from scratch?

1. Delete the data on the destination

2. Clean up dsync metadata by running it with the --cleanup option.

How fast is dsync?

Dsync offers several different load levels that allow users to control the internal level of parallelism when reading data from the source and writing to the destination. Outside of that, the sync performance will depend on the following factors: 1) Provisioned capacity of source and destination databases 2) Network bandwidth 3) Record/row/document size 4) CPU allocated to dsync

What security or auth options are supported?

Dsync uses regular MongoDB Go Driver. All standard auth options are supported.

How do I start dsync in a highly-available configuration?

You can run it as a docker container with a sensible restart policy.

Docker?

https://github.com/adiom-data/dsync/blob/main/Dockerfile

For any other questions not included in this FAQ section, contact [e-mail]