@aab985030 This approach is fine for small databases, but it really doesn’t scale well.
Full backups, especially with mysqldump, become pretty inefficient as data grows. They put noticeable load on the system, take a long time to run, and restores can be painfully slow. In a production environment with larger datasets, that’s just not a great place to be.
A more modern setup usually relies on physical backups combined with incremental backups. That way you reduce resource usage and get much faster recovery times when something actually goes wrong.
Using something like Borgmatic can still make sense, but more as an additional layer for offsite or archival storage. It should not be treated as a standalone solution for consistent database backups.
So overall, the method shown is okay as a starting point, but it is not really suitable for larger or more demanding production setups.