MYSQL-ZRM-PARSE-BINLOGS(1)

📦 version 3.0, in epel 9, fedora 43, fedora 44

✨ mysql-zrm-parse-binlogs(1) ✨

okay so bestie, you know that moment when you're staring at a binlog like "where exactly did the bad thing happen"?? yeah. this is the tool for that. 🦋

🌸 NAME 🌸

mysql-zrm-parse-binlogs — the utility that parses MySQL binary logs for ZRM for MySQL. literally its whole job. 💅

🎀 SYNOPSIS 🎀

mysql-zrm-parse-binlogs
                [--source-directory dir_name]
                [--bin-logs "/fullpath/name1 /fullpath/name2 ..."]
                [--mysql-binpath MySQL_command_location]
                [--parse-binlogs-plugin plugin]
                [--parse-binlogs-plugin-options "opt1 opt2 ..."]
                [--row-event-details= never|always|auto]
                [--output-format= html|text]
                [--options-file filename]
                [--tmpdir temporary directory to be used]
                [--quiet|--no-quiet]
                [--verbose]
                [--help]

💖 DESCRIPTION 💖

So the whole point: this thing parses binary logs to find out the timestamp and/or the log position of specific database events. 🕵️♀️

It displays the parsed output of those binary logs for you, which is actually useful, because that's how you find the log positions and/or timestamp you need for restore operations. no cap.

Either the --source-directory option or the --bin-logs option should be specified. Here's the tea:

  • When the --source-directory option is specified, the parsed output of the binary logs from that backup gets displayed. 🫶
  • When the --bin-logs option is specified, the parsed output of the binary log file specified gets displayed.

Also, bestie, please go take a look at the ZRM for MySQL documentation at http://mysql-backup.zmanda.com/ for the procedures on how to configure and use ZRM for MySQL. it's giving required reading. 📚

👑 OPTIONS 👑

  • --backup-set name — specify the backup-set for the backup run. The default value is BackupSet1. 🎯
  • --source-directory directory name — choose the directory containing a backup. Both --source-directory and --bin-logs options should not be specified. If both are present, the utility will throw an error. 💀
  • --bin-logs "/fullpath/name1 /fullpath/name2 ..." — list binary log files, along with their full paths, to be used for restore. Both --source-directory and --bin-logs options should not be specified. The utility will throw an error if both are specified. 🚨
  • --parse-binlogs-plugin plugin — set the plugin, along with its full pathname, that filters the output of the parse-binlogs action. This plugin is optional. 🧚
  • --parse-binlogs-plugin-options "option1 option2 ..." — pass options to the parse-binlogs-plugin as one of the command line arguments. 🌈
  • --row-event-details= never|always|auto — this option describes how the row replication events in binary logs should be handled. okay here's the breakdown, pay attention:
    • If the mysqlbinlog command on the ZRM server supports decoding row based replication events and supports verbose mode (MySQL client versions > 5.1.28), set the value to always.
    • Set the value to never if the row based replication events decoding is not supported by the mysqlbinlog command.
    • Set the value to auto if ZRM should parse row based events if it is supported. Support of this feature is determined by ZRM when the value is auto.
  • --output-format= html|text — the output from the command can be in text format (value text) or in the form of an HTML table (value html). The default is the text format. 💅
  • --options-file filename — set the file, along with its full pathname, that contains MySQL command options. 📄
  • --mysql-binpath MySQL_command_location — set the full path where the MySQL binaries are installed. For example: /opt/lampp/bin 📍
  • --tmpdir temp_directory — full path of the directory for storing temporary files and directories on the backup host. The default is to use the system-specified temporary directory on the backup host, e.g. /tmp. 🗂️
  • --quiet|--no-quiet — choose quiet to suppress display of log messages on stdout. Choose no-quiet to display the log messages to stdout. The default is --no-quiet. 🤫
  • --verbose — provide more detailed output in the log. Verbose output is turned off by default. 🔍
  • --help — displays the help message and exits. This command-line-only parameter cannot be specified in the configuration file. 🙈

🌈 EXAMPLES 🌈

mysql-zrm --action parse-binlogs --bin-logs /var/lib/mysql-zrm/backupset1/20060818121532/mysql-bin.[0-9]* /var/lib/mysql-zrm/backupset1/20060819121532/mysql-bin.[0-9]*

The above command parses and displays the relevant contents of all specified binary log files. Use it to find out what position and or timestamp to specify for selective restores. 🎀

🍓 FILES 🍓

  • /var/lib/mysql-zrm — directory under which all backup data is stored.
  • /etc/mysql-zrm/backup set name/mysql-zrm.conf — configuration file read by ZRM for MySQL.

⭐ RETURN VALUES ⭐

On success, zero is returned. On error, a non-zero value is returned. simple as that. ✨

🦋 SEE ALSO 🦋

mysql-zrm(1), mysql-zrm-backup(1), mysql-zrm-manage-backup(1), mysql-zrm-restore(1), mysql-zrm-check(1), mysql-zrm-list(1), mysql-zrm-getconf(1), mysql-zrm-setconf(1), mysql-zrm-purge(1), mysql-zrm-extract-backup(1), mysql-zrm-verify-backup(1), mysql-zrm-abort-backup(1), mysql-zrm-scheduler(1), mysql-zrm-reporter(1), mysql-zrm.conf(5), mysqldump(1), mysqlbinlog(1), mysql(1), lvm(8), Zmanda Recovery Manager for MySQL (http://mysql-backup.zmanda.com/)

💜 AUTHOR 💜

Zmanda Inc. (http://www.zmanda.com)

and that's the whole page, bestie!! 🫶 this lil manual page came to you courtesy of Zmanda, Inc. — the ZRM for MySQL era, page mysql-zrm-parse-binlogs(1). mwah. go parse some binlogs. 💅✨

📦 where this page comes from