Hi. We are using Typesense Cloud at the moment and...
# community-help
j
Hi. We are using Typesense Cloud at the moment and now we have to move the cluster to our own infrastructure due to GDPR reasons. Since https://typesense.org/docs/guide/backups.html is not applicable for Typesense Cloud, does anybody have experience with this or know a best practice?
f
Typesense Cloud is GDPR compliant (SOC2 compliant). Here's our privacy notice: https://cloud.typesense.org/legal/privacy
1
j
While that is great the client's data privacy officer still insists on hosting it on own infrastructure.
j
You'd just have to update the hostnames in your application, and trigger a resync of the data from your primary DB into your self-hosted Typesense instance
The APIs are exactly the same between Typesense Cloud and self-hosted
j
Unluckily this is not an option since we cannot fully rebuild all the data in our cluster
j
Why though!?
Because Typesense is not meant to be used as a primary DB, so you definitely need to have a copy of your dataset in your primary DB at all times, and only sync a copy of it to Typesense
e
Can you use Typesense Dashboard to export collections on Cloud then import on Self? https://github.com/bfritscher/typesense-dashboard
The Collection area has an import export feature
j
Manual export/import is not an option since we have >1000 collections.
👍 1
Thanks everybody for the comments. Following Jason's statement I will work on the data sourcing logic.