using https://mariadb.com/kb/en/mariadb/global-transaction-id/ in mariadb-10+ I'd be looking at recording the gtid as part of the backup. Then recovery is set global gtid_slave_pos=...; CHANGE MASTER TO master_use_gtid = slave_pos; start slave; regardless of server.

Timestamp is quite ambiguous when multiple transactions can happen in a millisecond.

I totally agree that log file/pos between servers is a pain, which I suspect was one of the great motivators for gtid implementation.

> Timestamp is quite ambiguous when multiple transactions can happen in a millisecond.

It should not matter when we use it for a cutoff: if (timestamp > stop_timestamp) stop;
(Also "STOP SLAVE AFTER <timestamp>" could be also usable).

I'm asking for no new features, just for a convenient way to do what is already possible.

The point of this feature is the ability to make dumps of two or more different servers for the given point in time.
We could stop masters at the same time, and then make dumps, but this is not an option Thus slaves
and stopping replication at the same time, but this time we should be taken from binlogs because of possible slave lags.

Point-In-Time Recovery needs time.

• restore full level backup
• apply binary logs to point-in-time

The idea is to setup a replication server to get prepared for requests from Development Teams.
Easy delivery of test data is possible when we break replication in a point-in-time and offer secondary server to development.

For example:
Every 4 weeks we have to prepare 20 test server with test data from different database server.
Data of each system has to be synchronized to one point in time.
We have 24 hours to copy data to test server with backup/recover-methods.
In my opinion it would be easier to setup 20 test server as replication clients in the period of 4 weeks and stop replication (point-in-time) when new test data is needed.

Label beginner-friendly would be appropriate as well?