10 Older Entries »
MEB 3.12.0 and above support cloud backup and restore using OpenStack-compatible object stores ("Swift"). This allows MySQL database users with Oracle Storage Cloud account to take backups and store them directly in the cloud and restore them from there.
The following steps illustrate how to set up and use MEB with Oracle Storage Cloud :
1) Create Oracle Storage Cloud account at https://cloud.oracle.com/storage . Once service gets activated, make a note of the following credentials that will be required in further steps :
Identity domain name
Service Instance Name : Customer-specified name of the service instance
The names of databases and tables within MySQL are known as identifiers. In the simplest case these identifiers are just strings of certain ASCII characters (the basic Latin letters, the digits 0-9, the dollar sign and the underscore). However, if an identifier is placed in quotes, it can contain any character of the full Unicode Basic Multilingual Plane (except U+0000). We say that a character is a special character if it is permitted in a quoted identifier but not in an unquoted identifier.
MySQL Enterprise Backup (MEB) 3.12.1 introduces support for proper handling of table and database names with special characters. In MEB versions prior to 3.12.1 database and table names were represented as ASCII strings and the same string was used on the command line, internally within MEB and in filenames. This caused MEB to fail some …[Read more]
MySQL Enterprise Backup 3.12.0 (MEB) introduces a new feature for restoring an InnoDB table from a backup. Now it is possible to rename the table during restore. This is useful when the user wants to restore a table from a backup without overwriting the existing version of the table in the database.
The following example illustrates how the renaming feature could be used. Suppose that the DBA has deleted three rows from a table T1 by mistake and he now wishes to get them back from a backup. He wants to leave the database online and to restore the 3 deleted rows from a TTS backup (a backup created with the --use-tts option) that contains the table T1. He can do this with this feature in three steps:
- He restores with MEB the table T1 from a TTS backup renaming
it to T2.
- He uses MySQL client to issue SQL statements to …
With the support for cloud backups in MEB, distributing innodb
tables across multiple MySQL instances has become easier.
1. Backup - take a cloud(Amazon S3) backup of the tables to be shared using the --use-tts=with-full-locking option.
--host=localhost --user=mysqluser --protocol=TCP --port=3306 \
--cloud-service=s3 --cloud-aws-region=us-east-1 \
--cloud-bucket=mebbackup –cloud-object-key=items.img \
--cloud-access-key-id=<access-key> --cloud-secret-access-key=<secret-key> \
--include-tables=^mycompany\.items.* --use-tts=with-full-locking \
--backup-dir=/tmp/bkups/backupdir --compress --backup-image=- …
With MySQL Enterprise Backup(MEB) 3.9.0 we had introduced
full instance backup feature for cloning the
MySQL server. Now with MEB 3.11.0 we have enhanced the feature by
copying all the master-slave setup files like MySQL server binary
logs(will be referred as 'binlogs'), binary log index files,
relay logs of slave, relay log index files, master info of slave,
slave info files. As part of full instance backup, copying of
binlog files is default behavior MEB-3.11.0 onwards. DBA should
be aware of the fact that current full instance backup is bigger
than the backups with old MEB's.
As every event on MySQL production database goes as a entry to binlog files in particular format, binlog files could be huge. Backing of huge binlog and/or relaylog files should not impact the performance of MySQL server. Hence, all the binlog files, …
Sometimes the best way to repair data issues and problems within a MySQL database is to restore only some of the tables from a backup. For example, suppose that some data was accidentally deleted from one table due to a software error, then the easiest way to recover the lost data might be to restore only one table from a backup. Previously this kind of partial restore was not supported by MySQL Enterprise Backup (MEB). However, MEB 3.11 introduces support for selective restore from backups created with the --use-tts option (or TTS backups).
TTS backups are backups that are created with the transportable tablespaces feature of InnoDB. These backups consist of InnoDB tables that …[Read more]
MySQL Enterprise Backup (MEB) is a highly efficient tool for
taking backups of your MySQL databases. In the 3.11.0 release we
are taking that one step further by introducing a new concept
called "optimistic" backup. Optimistic backup leverages the
patterns we saw frequently especially as related to very large
For backups the goals are:
1 - Quality and Consistency - the backup and more importantly the restore just "works"
2 - Size, time, and overhead - like in the game of golf - low score wins - for backups and for
3 - Flexibility – It’s not always one size fits all - whether how the backup is run, where it goes,
how it is recovered.
With optimistic backup - we look at mostly the read aspects of your database to enable us to create a backup that is smaller, faster to backup, faster to …[Read more]
I was recently asked about if MySQL Enterprise Backup would be
able to restore single databases.
My initial answer was that this was complicated, but might be doable with the Transportable Table Space (TTS) option.
But first let's go back to the basics. A common way of working with mysqldump is to get a list of databases and then loop through the databases and dump the data and schema to a SQL file. But both backups and restores will take a lot of time if the size of the database grows. And it's a luke-warm backup at best instead of a hot backup. So that's why we have MySQL Enterprise Backup.
MySQL Enterprise Backup allows you to make a hot backup of InnoDB tables by copying the datafiles while watching the InnoDB redo log files.
On disk the data from the InnoDB storage engine consists of a system tablespace (one of more ibdataX files), the redo log files (iblogfileX) and zero or more …
MySQL Enterprise Backup(MEB) has been widely used as the most efficient tool to take backups of huge databases. The storage of backups can be done on-premises – viz, local hard disk, external hard disk drives, network mounted disk. MEB can also stream backups to tape by supporting different Media Management Software like Symantec NetBackup, EMC2 and Oracle Secure Backup. Streaming of backups can also be done using 'ssh' to another machine.
As data keeps growing, instead of expanding the storage, database users are choosing to rely on the growing trend which is the Cloud Storage.
A few facts about Cloud Storage:
1. Offers off-premises storage with AAA(Anytime, Anywhere Access)
2. Sharing of data to make a collaborative effort.
3. Highly fault tolerant, durable and scalable and secure.
To the benefit of our MySQL database users, Mysql …
10 Older Entries »