the best way to back up a prisma/mysql database?

https://www.prisma.io/dataguide/managing-databases/backup-considerations Prisma does a great job explaining all we should consider when setting up a backup strategy, however it looks like the prisma export command was deperecated and there's no off the shelf solution for backing up... from prisma. I guess i should look for solutions built for mysql? are there standard solutions? I dont like mysqldumb i mean dump
Prisma's Data Guide
Introduction to database backup considerations
Learn about the choices you will need to make when developing a database backup strategy.
8 Replies
royanger
royanger17mo ago
You will either want a service that hosts and backs up your DB, or you would need to use mysqldump and maintain your own backups (or whatever 3rd party backup solutions might exist). IE, while not MySQL, here are the backup options from CockroachDB. https://www.cockroachlabs.com/docs/stable/backup-and-restore-overview.html On the flip side, Railway which offers hosted DBs has no backups as part of their plan so you need your own if you hosted with them.
fotoflo
fotoflo17mo ago
hi @Ranger thanks.... i was thinking there should be some open source tools that reguarly back up and store on s3 or a google cloud bucket or something kind of something inbetween i wonder if i can can move easily to cockroachdb from mysql
royanger
royanger17mo ago
Pretty sure Planetscale has backups, but I didn't check.
fotoflo
fotoflo17mo ago
im using mysql on GCP for now (since i have $20k in GCP credits...) and ive been using mysql since forever
royanger
royanger17mo ago
GCP offers automated backups…
fotoflo
fotoflo17mo ago
so i just use theirs and i use workbench for imports and exports
royanger
royanger17mo ago
If you need to import/export.
fotoflo
fotoflo17mo ago
so right now im actually going through an important cycle i have a pre-prisma copy of the db working in production ive exported it from production and brought it down to local imported it to my workstation's mysql instance now i have 27 migrations i want to lay on top ... basically im testing this process before moving to production i should have done it earlier