Point-in-Time Recovery Using Binary Log backup was made. (The full backup can be made in several ways, such as those listed in Section 7.2, “Database Backup Methods” .) Point-in-time recovery then brings the server up to date incrementally from the time of the full backup to a more recent time. This section explains the general idea of using the binary log to perform a point-in-time-recovery. The next section, Section 7.5.2, “Point-in-Time Recovery Using Event Positions” , explains the operation in details with an example. Many of the examples in this and the next section use the  mysql  client to process binary log output produced by  mysqlbinlog . If your binary log contains  \0  (null) characters, that output cannot be parsed by  mysql  unless you invoke it with the  -- binary-mode  option. The source of information for point-in-time recovery is the set of binary log files generated subsequent to the full backup operation. Therefore, to allow a server to be restored to a point-in-time, binary logging must be enabled on it, which is the default setting for MySQL 8.0 (see Section 5.4.4, “The Binary Log” ). To restore data from the binary log, you must know the name and location of the current binary log files. By default, the server creates binary log files in the data directory, but a path name can be specified with the --log-bin  option to place the files in a different location. To see a listing of all binary log files, use this statement: mysql>  SHOW BINARY LOGS; To determine the name of the current binary log file, issue the following statement: mysql>  SHOW MASTER STATUS; The  mysqlbinlog  utility converts the events in the binary log files from binary format to text so that they can be viewed or applied.  mysqlbinlog  has options for selecting sections of the binary log based on event times or position of events within the log. See Section 4.6.9, “mysqlbinlog — Utility for Processing Binary Log Files” . Applying events from the binary log causes the data modifications they represent to be reexecuted. This enables recovery of data changes for a given span of time. To apply events from the binary log, process mysqlbinlog  output using the  mysql  client: shell>  mysqlbinlog  binlog_files  | mysql -u root -p If binary log files have been encrypted, which can be done from MySQL 8.0.14 onwards,  mysqlbinlog cannot read them directly as in the above example, but can read them from the server using the  --read- from-remote-server  ( -R ) option. For example: shell>  mysqlbinlog --read-from-remote-server --host= host_name  --port=3306 --user=root Here, the option  --ssl-mode=required  has been used to ensure that the data from the binary log files is protected in transit, because it is sent to  mysqlbinlog  in an unencrypted format. Viewing log contents can be useful when you need to determine event times or positions to select partial log contents prior to executing events. To view events from the log, send  mysqlbinlog  output into a paging program: shell>  mysqlbinlog  binlog_files  | more Alternatively, save the output in a file and view the file in a text editor: 1627 Note 7.5.1 Point-in-Time Recovery Using Binary Log