FromDual Backup and Recovery Manager for MariaDB and MySQL 2.2.2 has been released

Wed, 2020-10-14 14:22 — Shinguz

FromDual has the pleasure to announce the release of the new version 2.2.2 of its popular Backup and Recovery Manager for MariaDB and MySQL (brman).

The new FromDual Backup and Recovery Manager can be downloaded from here. The FromDual Repositories were updated. 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 2.x to 2.2.2

shell> cd ${HOME}/product
shell> tar xf /download/brman-2.2.2.tar.gz
shell> rm -f brman
shell> ln -s brman-2.2.2 brman

Changes in FromDual Backup and Recovery Manager 2.2.2

This release is a new minor release. It contains only bug fixes. We have tried to maintain backward-compatibility with the 1.2, 2.0 and 2.1 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
shell> rman --version

General

Implode command made compatible to new PHP versions.
Function readMyCnf restructured to not write to STDOUT any more.
Max connection reached problem solved.
myEnv library and constants synced/updated.

FromDual Backup Manager

Missing return code added.
RELOAD privilege is checked in doSchemaBackup and BinlogBackup.
Reset return code to not spoil final return code in doSchemaBackup.
WARN reduced severity level to INFO to not spoil STDERR in doSchemaBackup.
Error caught in case when binary logs were deleted but not available in doCleanup.
doBinlogBackup separated into own file.
Do not print wrong recommendation in case of too many connections for target.
Bman error message improved.
Code clean-up in checkForGeneralTablespaces function.
Bman falsely warns on MySQL 8.0 for general tablespace (new InnoDB system tablespace). This warning is suppressed now.
Schema overview output was ugly with long schema names. Now extended to 24 characters.
Bug caught better for clean-up backups in case the backup was already deleted by somebody else.
Error handling improved for binlog backup on remote machine, code cleaned-up.
Separated schema backup into own file.
Fixed error messages and added remote binary log backup tags for future feature request.
Function checkForGeneralTablespaces cleaned-up.
Lock directory moved to /var/lock and alternative location for some Cloud set-ups.
Physical backup for MariaDB 10.5 fixed.