4 ms·
When I ran MySQL servers (which was many years ago), I ran a replication slave (or two) that didn't get query traffic; every so often, mysql would be shut down,
by toast0 4y ago
When I ran MySQL servers (which was many years ago), I ran a replication slave (or two) that didn't get query traffic; every so often, mysql would be shut down, the whole data directory would be tared and compressed, and then mysql would be started back up. IIRC, the interval was every 4 hours.
Normal production monitoring kept track that replication was working, but had to have an exception to allow more time between detection and alerting for the archiving.
These archives were used to start new production slaves, so the backups were tested from time to time. Older archives and careful use of binary logs could allow restoration to any particular point (although I never had to do that); at least within the retention of binary logs.
I did a rotation of backups to have the most recent X frequent backups, Y backups no more than 1 a day, Z weeklies, etc monthlys, etc, etc.