Join 1M+ other developers and:
- Get help and share knowledge in Q&A
- Subscribe to topics of interest
- Get courses & tools that help you grow as a developer or small business owner
Looking for backup strategy for write-intensive mysql database
Right now the setup consists of $10 droplet with an attached volume with MySQL datadir on the volume (following this guide). The reason for this is to be able to scale storage and cpu/ram separately with little downtime (using the flexible resizing for droplet). All tables are using InnoDB.
That said I’m looking for how to backup this properly. I have set up mysqldump and automysqlbackup (which uses mysqldump, if I remember correctly) before but (if I remember correctly) both of them lock the database while doing the backup which isn’t acceptable for write-intensive scenario (monitoring type of thing).
After some googling I found percona hot backup but I didn’t really understand how to automate it (looking to save backups to S3). Also I wasn’t sure if it’s what I’m looking for.
Googling “write-intensive mysql backups” unfortunately doesn’t really give anything. Looking for any ideas on how to do this so I can rely on it if/when something happens
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.×