mydumper VS mysqld_exporter

You can create a MySQL backup for Railway.app using the MyDumper tool or by using a backup service like SimpleBackups. Both methods involve generating a dump file that can be used for restoration.

Maybe check mydumper which uses a multi-threaded multi-file approach so that backups are faster, but more important, restores are faster. Plus it makes it way easier to do a partial recovery (for instance, a specific table).

It looks like MyDumper added support to invoke PGP, etc. https://github.com/mydumper/mydumper/issues/101

Either xtrabackup, or mydumper.

Use mydumper. It has lightweight locking that can produce consistent backups without stopping replication. It also has multi-threaded sharding so it can backup much faster.

Agree with you, just let me suggest mydumper as a parallel and compressed version of mysqldump, much faster way to export and import tables- unless your tables are tiny.

Take a snapshot backup of the 5.1 server with mydumper.

Either way, use mydumper. It is much faster than basic mysqldump.

Check out mydumper it's multithreaded and way faster than mysqldump.

Better than basic mysqldump is mydumper. It has a bunch of nice features like multi-threaded parallel dumping. It can cut the dump/restore time by a huge amount.

To install it you can follow the instructions in the GitHub repository and you can run it in a Docker container as well.

Prometheus and the mysqld_exporter can provide lots of good, detailed, real-time metrics on your performance.

What I would do is to persist those between restarts. If you need metrics, something like the prometheus-mysql-exporter (or any other scrapping process) can periodically query mysql for metrics, including (although not by default) performance_schema. That is what I would suggest to solve your monitoring (and would get you a robust and maintained metric system), plus counters will automatically solve the "reset to 0" on restart.

As u/mtocker said, best practice today is to use a modern metrics-based monitoring platform like Prometheus and mysqld_exporter. This does much more than just "not offline".

​ To start monitoring MySQL with Prometheus, you’ll need to deploy the MySQL Exporter in your cluster. ​ To deploy the exporter, you can use the example files provided below. ​

I'm not MySQL user, but I'm writing a custom exporter for my NoSQL clusters, so studying the official mysql exporter (https://github.com/prometheus/mysqld_exporter) just for reference.

For example mysqld_exporter , you supply mysql connection details while mysqld_exporter itself running inside k8s as a just another container, then prometheus will scrape the mysqld-exporter. Deploying mysqld-exporter is just another Deployment.

When manually rejoining the cluster fails, syncing the server's replication logs manually is an especially harrowing experience. These occurrences were greatly reduced by upgrading our cluster to the 8.0.x series of releases, making use of the Auto Rejoin feature, and monitoring our clusters members using MySQL Exporter

"latest" as in 0.13.0-rc.0?