The https://example MySQL service states that:
Render Disks make it effortless to deploy production-grade MySQL on Render backed by high performing SSD disks with automatic snapshots so your data is protected against database restarts and failures.
However, surely it’s not safe to simply snapshot the render disk (and therefore
/var/lib/mysql) on a running MySQL instance? This may well lead to data corruption.
The example MySQL repo example seems to hint at this as there’s a separate Dockerfile for backups which runs a
mysqldump command (one of the correct ways of backing up the data). This writes to
/var/lib/mysql/backups so I suppose would be snapshotted as part of the render disk. However, I don’t see how this links up to the service? Is this supposed to be set up as a cron? If so, how can it access the render disk associated with the MySQL example service?
I really feel like either I’m missing something or the docs are. Please advise!