I have not written an article in a while, I partially blame it on
the World Cup and my day job. The time has come to share some of
my recent experiences with a neat project to provide several
teams internally with current MySQL backups.
When faced with these types of challenges is my first step is to
look into OSS packages and how can they be combined into an
actual solution. It helps me understand the underlying
technologies and challenges.
ZRM BackupI have reviewed Zmanda's
Recovery Manager for MySQL Community Edition in the Fall 2008
issue of MySQL magazine. It remains one of my favorite
backup tools for MySQL since it greatly simplifies the task and
configuration of MySQL backups taking care of most of the
details. Its flexible reporting capabilities came in handy for
this project as …
The primary responsibility of MySQL professionals is to establish and run proper backup and recovery plans. The most used method to backup a MySQL database is the mysqldump utility. This mysqldump utility creates a backup file for one or more MySQL databases that consists of DDL/DML statements needed to recreate the databases with their data. To [...]
Moving your data and tables around comes in many different
flavours. The use of mysqldump is common practice to dump your
data and schema out to a file. It is also possible to pipe your
mysqldump into a 2nd server. Try the code below (adapting the
users and passwords!) in a test environment;
$ mysqldump -u UserA -p p455w0rd --single-transaction
--all-databases --host=Server1 | mysql -u UserA -p p455w0rd
--host=Server2
As you can see from the command we are taking all the databases
in a single transaction into Server2 from Server1. If you're not
using transactional tables substitute the --single-transaction
for --lock-all-tables to ensure you get a consistent copy.
Remember; You must be able to see the 'other' server over the
network and there must be permissions set for remote access from
your feeding Server. For large databases this technique may not
be suitable because of the performance restrictions surrounding …
Moving, copying or renaming database is a very basic activity. I have just noted a few commands for reference to quickly follow the required operation. 1. Rename database on Linux…
The post Steps to Move Copy Rename MySQL Database first appeared on Change Is Inevitable.
I don't usually post these simple tricks, but it came to my
attention today and it's very simple and have seen issues when
trying to get around it. This one tries to solve the question:
How do I restore my production backup to a different
schema? It looks obvious, but I haven't seen many people
thinking about it.
Most of the time backups using mysqldump will include the
following line:
USE `schema`;
This is OK when you're trying to either (re)build a slave or
restore a production database. But what about restoring it to a
test server in a different schema?
The actual trick
Using vi (or similar) editors to edit the line will most
likely result in the editor trying to load the whole backup file
into memory, which might cause paging or even crash the server if
the backup is big enough (I've seen it happen). Using sed
(or similar) might take some time with a big …
Whether you’re working with MySQL, MySQL Cluster, or any other RDBMS, every database with a requirement for persistent data should always have a backup. As a Production DBA you’re the insurance policy to safeguard the data. Bad things do happen. Backups are your safety net to ensure you always have a way to recover should the worst happen and the database becomes irreparable.
There are many ways to produce a consistent backup of MySQL, I have listed a few of the options available below; Remember backups are your safety net, failing to retrieve a consistent backup when you need it most can be a very career limiting move, so no matter what backup method you choose always test your backups!
Logical Backups
The ever popular mysqldump is a backup and export utility
provided with the MySQL binaries …
EAVB_VFZUHIARHI To whom it may concern -
The mysqldump program can be used to make logical
database backups. Although the vast majority of people use it to
create SQL dumps, it is possible to dump both schema structure
and data in XML format. There are a few bugs (#52792, #52793) in this feature, but these are not the
topic of this post.XML output from mysqldumpDumping in XML format
is done with the --xml or -X option. In addition, you
should use the --hex-blob option otherwise the BLOB data will …
To whom it may concern,
in response to a query from André Simões (also known as ITXpander),
I slapped together a MySQL script that outputs mysqldump commands for backing up
individual partitions of the tables in the current schema.
The script is maintained as a
snippet at MySQL Forge. How it worksThe script works by
querying the information_schema.PARTITIONS system
view to …
Dave Edwards has offered me to write this week's Log
Buffer, and I couldn't help but jump at the opportunity. I'll
dive straight into it.
OracleI'll start with Oracle, the dust of the Sun acquisition has
settled, so maybe it's time to return our attention to the
regular issues.
Lets start with Hemant Chitale's Common Error series and his
Some Common Errors - 2 - NOLOGGING as a Hint
explaining what to expect from NOLOGGING. Kamran Agayev offers us
an insight into Hemant's personality with his Exclusive Interview with Hemant K Chitale. My
favorite quote is:
Do you refer to the documentation? And how often does …
The mysqldump filter was created with this need in
mind. It allows you to remove all DEFINER clauses and eventually
replacing them with a better one.
For example:
mysqldump --no-data sakila | dump_filter --delete > …[Read more]