You are here

pitr

Oops! - That SQL Query was not intended... Flashback

It is Saturday night at 23:19. Time to go to bed after a hard migration day. Just a last clean-up query before finishing: Tap tap tap. Enter! - Oops!

SQL> UPDATE prospect_lists_prospects SET prospect_list_id = '73ae6cca-7b34-c4a3-5500-5d0e2674dbb6';
Query OK, 4686 rows affected (0.21 sec)
Rows matched: 5666  Changed: 4686  Warnings: 0

A verification query to make sure I am in the mess:

Cool new features in FromDual Backup and Recovery Manager 2.0.0

A while ago we released our FromDual Backup and Recovery Manager (brman) 2.0.0 for MariaDB and MySQL. So what are the new cool features of this new release?

First of all brman 2.0.0 is compatible with MariaDB 10.3 and MySQL 8.0:

FromDual Backup and Recovery Manager (brman) Installation Guide

Introduction

The FromDual Backup an Recovery Manager (brman) for MariaDB and MySQL is an easy to use application (CLI) for creating MariaDB and MySQL backups.
Its main purpose is to eas the many difficult ways of doing MariaDB and MySQL backups.

How to use FromDual brman you can find here: FromDual Backup and Recovery Manager (brman) User Guide.

Undefined

Download FromDual Backup and Recovery Manager

FromDual Backup and Recovery Manager (brman) for MariaDB and MySQL

The FromDual Backup and Recovery Manager (brman) for MariaDB and MySQL is an easy to use software to do Backup, Restore and Point-in-Time-Recovery for MySQL, Galera Cluster, MariaDB and Percona Server. It integrates the utilities mysqldump, mysql, mariabackup, xtrabackup and mysqlbackup (MySQL Enterprise Backup).

Undefined

FromDual Backup and Recovery Manager (brman) User Guide

About

The FromDual Backup and Recovery Manager for MariaDB and MySQL (brman) is an application to ease the use of the various MariaDB/MySQL backup tools. The Problem with MariaDB/MySQL backup tools is, that they have many options and thus are over-complicated and errors are easy made.

bman has the intention to make backups for MariaDB/MySQL easier and technically correct. This means it should per default not allow non-consistent backups or complain if some functions or parameters are used in the wrong way to guarantee proper backups.

Subscribe to RSS - pitr