mysqlbinlog — Utility for Processing Binary Log Files The transport protocol to use for connecting to the server. It is useful when the other connection parameters normally result in use of a protocol other than the one you want. For details on the permissible values, see Section 4.2.7, “Connection Transport Protocols” . By default,  mysqlbinlog  reads binary log files and writes events in text format. The  --raw  option tells  mysqlbinlog  to write them in their original binary format. Its use requires that  --read-from- remote-server  also be used because the files are requested from a server.  mysqlbinlog  writes one output file for each file read from the server. The  --raw  option can be used to make a backup of a server’s binary log. With the  --stop-never  option, the backup is “live”  because  mysqlbinlog  stays connected to the server. By default, output files are written in the current directory with the same names as the original log files. Output file names can be modified using the  --result-file  option. For more information, see Section 4.6.9.3, “Using mysqlbinlog to Back Up Binary Log Files” . Read binary logs from a MySQL server with the  COM_BINLOG_DUMP  or  COM_BINLOG_DUMP_GTID commands by setting the option value to either  BINLOG-DUMP-NON-GTIDS  or  BINLOG-DUMP- GTIDS , respectively. If  --read-from-remote-master=BINLOG-DUMP-GTIDS  is combined with  -- exclude-gtids , transactions can be filtered out on the source, avoiding unnecessary network traffic. The connection parameter options are used with this option or the  --read-from-remote-server option. These options are  --host ,  --password ,  --port ,  --protocol ,  --socket , and  --user . If neither of the remote options is specified, the connection parameter options are ignored. The  REPLICATION SLAVE  privilege is required to use this option. Read the binary log from a MySQL server rather than reading a local log file. This option requires that the remote server be running. It works only for binary log files on the remote server, not relay log files. The connection parameter options are used with this option or the  --read-from-remote-master option. These options are  --host ,  --password ,  --port ,  --protocol ,  --socket , and  --user . If neither of the remote options is specified, the connection parameter options are ignored. The  REPLICATION SLAVE  privilege is required to use this option. This option is like  --read-from-remote-master=BINLOG-DUMP-NON-GTIDS . Without the  --raw  option, this option indicates the file to which  mysqlbinlog  writes text output. With --raw ,  mysqlbinlog  writes one binary output file for each log file transferred from the server, writing them by default in the current directory using the same names as the original log file. In this case, the  -- result-file  option value is treated as a prefix that modifies output file names. Require row-based binary logging format for events. This option enforces row-based replication events for  mysqlbinlog  output. The stream of events produced with this option would be accepted by a replication channel that is secured using the  REQUIRE_ROW_FORMAT  option of the  CHANGE REPLICATION SOURCE TO  statement (from MySQL 8.0.23) or  CHANGE MASTER TO  statement (before MySQL 8.0.23).  binlog_format=ROW  must be set on the server where the binary log was 611 • --require-row-format • --result-file= name ,  -r  name • --read-from-remote-server ,  -R • --read-from-remote-master= type • --raw • --protocol={TCP|SOCKET|PIPE|MEMORY}