You are here
FromDual Backup and Recovery Manager for MariaDB and MySQL 2.0.0 has been released
FromDual has the pleasure to announce the release of the new version 2.0.0 of its popular Backup and Recovery Manager for MariaDB and MySQL (brman).
The new FromDual Backup and Recovery Manager can be downloaded from here. How to install and use the Backup and Recovery Manager is describe in FromDual Backup and Recovery Manager (brman) installation guide.
In the inconceivable case that you find a bug in the FromDual Backup and Recovery Manager please report it to the FromDual Bugtracker or just send us an email.
Any feedback, statements and testimonials are welcome as well! Please send them to feedback@fromdual.com.
Upgrade from 1.2.x to 2.0.0
brman 2.0.0 requires a new PHP package for ssh connections.
shell> sudo apt-get install php-ssh2
shell> cd ${HOME}/product
shell> tar xf /download/brman-2.0.0.tar.gz
shell> rm -f brman
shell> ln -s brman-2.0.0 brman
Changes in FromDual Backup and Recovery Manager 2.0.0
This release is a new major release series. It contains a lot of new features. We have tried to maintain backward-compatibility with the 1.2 release series. But you should test the new release seriously!
You can verify your current FromDual Backup Manager version with the following command:
shell> fromdual_bman --version shell> bman --version
FromDual Backup Manager
brmanwas made ready for MariaDB 10.3brmanwas made ready for MySQL 8.0DEBandRPMpackages are prepared.fromdual_brmanwas renamed tobrman(because ofDEB).mariabackupsupport was added.- Timestamp for physical backup and compression added to log file.
- Option
--no-purgeadded to not purge binary logs during binlog backup. - A failed archive command in physical full backup does not abort backup loop any more.
- Return code detection for different physical backup tools improved.
- Bug in fetching binlog file and position from
xtrabackup_binlog_infofixed. - Version made MyEnv compliant.
- Errors and warnings are written to
STDERR. - General Tablespace check implemented. Bug in
mysqldump. Only affects MySQL 5.7 and 8.0. MariaDB up to 10.3 has not implemented this feature yet. - Warning messages improved.
- Option
--quickadded for logical (mysqldump) backup to speed up backup. - On schema backups
FLUSH BINARY LOGSis executed only once when--per-schemabackup is used. - The database user
rootshould not be used for backups any more. Userbrmanis suggested. - Option
--pass-throughis implemented to pass options like--ignore-tablethrough to the backend backup tool (mysqldump,mariabackup,xtrabackup,mysqlbackup). bmancan report to fpmmm/Zabbix now.- Check for binary logging made less intrusive.
- All return codes (rc) are matching to new schema now. That means errors do not necessarily have same error codes with new
brmanversion. - If
RELOADprivilege is missing--master-dataand/or--flush-logsoptions are omitted. This makesbmanbackups possible for some shared hosting and cloud environments. - Schema backup does not require
SHOW DATABASESprivilege any more. This makes it possible to usebmanfor shared hosting and cloud environments. - Info messages made nicer with empty lines.
- Option
--archivediris replaced by--archivedestination. - Remote copy of backup via
rsync,scpandsftpis possible. - Connect string was shown wrong in the log file.
- Connect string of target and catalog made URI conform.
bmansupports nowmariabackup,xtrabackupandmysqlbackupproperly (recent releases).
FromDual Backup Manager Catalog
- Catalog write is done if physical backup hits an error in archiving.
- Renamed
catalogtobrman_catalog.
For subscriptions of commercial use of brman please get in contact with us.
- Shinguz's blog
- Log in or register to post comments