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
brman
was made ready for MariaDB 10.3brman
was made ready for MySQL 8.0DEB
andRPM
packages are prepared.fromdual_brman
was renamed tobrman
(because ofDEB
).mariabackup
support was added.- Timestamp for physical backup and compression added to log file.
- Option
--no-purge
added 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_info
fixed. - 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
--quick
added for logical (mysqldump
) backup to speed up backup. - On schema backups
FLUSH BINARY LOGS
is executed only once when--per-schema
backup is used. - The database user
root
should not be used for backups any more. Userbrman
is suggested. - Option
--pass-through
is implemented to pass options like--ignore-table
through to the backend backup tool (mysqldump
,mariabackup
,xtrabackup
,mysqlbackup
). bman
can 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
brman
version. - If
RELOAD
privilege is missing--master-data
and/or--flush-logs
options are omitted. This makesbman
backups possible for some shared hosting and cloud environments. - Schema backup does not require
SHOW DATABASES
privilege any more. This makes it possible to usebman
for shared hosting and cloud environments. - Info messages made nicer with empty lines.
- Option
--archivedir
is replaced by--archivedestination
. - Remote copy of backup via
rsync
,scp
andsftp
is possible. - Connect string was shown wrong in the log file.
- Connect string of target and catalog made URI conform.
bman
supports nowmariabackup
,xtrabackup
andmysqlbackup
properly (recent releases).
FromDual Backup Manager Catalog
- Catalog write is done if physical backup hits an error in archiving.
- Renamed
catalog
tobrman_catalog
.
For subscriptions of commercial use of brman
please get in contact with us.
- Shinguz's blog
- Log in or register to post comments