Home |  MySQL Buzz |  FAQ |  Feeds |  Submit your blog feed |  Feedback |  Archive |  Aggregate feed RSS 2.0 English Deutsch Español Français Italiano 日本語 Русский Português 中文
Showing entries 1 to 13

Displaying posts with tag: restore (reset)

A difficult XtraBackup restore
+1 Vote Up -0Vote Down
posted by Daniel van Eeden on Sun 09 Dec 2012 11:17 UTC
Tags:
(edit) mysql, SELinux, restore, Xtrabackup
There was one MySQL server with a Adaptec Raid controller and 4 disks. One of the disks was having media errors and caused the whole SCSI bus to become unavailable.

This resulted in a corrupted InnoDB table.

Luckily we did have backups. A full backup and incrementals.

So to restore the backups I installed XtraBackup and MySQL 5.5 on another server.

Then the first step was to 'prepare' the backup. This worked okay for the full backup (redo only).

The second step to add the incremantals failed for the first incremental. This was easily resolved by specifying the full paths instead of relative paths.

Then the backup was fully prepared using the redo logs and undo logs.

As XtraBackup doesn't backup your my.cnf we copied the my.cnf from another server and adjusted it for this server. The my.cnf in your













  [Read more...]
Surprises in store with ndb_restore
+1 Vote Up -1Vote Down
posted by SkySQL on Thu 16 Feb 2012 18:49 UTC
Tags:
(edit) Backup, cluster, ndb, restore, ndb_restore, gotcha

While doing some routine fiddling regarding some topic I've now forgotten, I discovered that ndb_restore was doing something quite surprising. It's been common wisdom for some time that one can use ndb_restore -m to restore metadata into a new cluster and automatically have your data re-partitioned across the data nodes in the destination cluster. In fact, this was the recommended procedure for adding nodes to a cluster before online add node came along. Since MySQL Cluster 7.0, though, ndb_restore hasn't behaved that way, though that change in behavior doesn't seem to be documented and most don't know that the change ever took place.

I'll go through some of the methods you can use to find information about the partitioning strategy for an NDB table, talk a bit about why ndb_restore stopped working the way most everyone expected

  [Read more...]
Viewing RMAN jobs status and output
+0 Vote Up -1Vote Down
posted by Ben Mildren on Fri 26 Aug 2011 05:10 UTC
Tags:
(edit) Oracle, Backup, Group Blog Posts, metadata, views, query, restore, Technical Blog, rman, gv$rman_output, output, v$, V$BACKUP_SET, V$BACKUP_SET_DETAILS, V$RMAN_BACKUP_JOB_DETAILS, v$rman_output

Yesterday I was discussing with a fellow DBA about ways to check the status of existing and/or past RMAN jobs. Good backup scripts usually write their output to some sort of log file so, checking the output is usually a straight-forward task. However, backup jobs can be scheduled in many different ways (crontab, Grid Control, Scheduled Tasks, etc) and finding the log file may be tricky if you don’t know the environment well.
Furthermore, log files may also have already been overwritten by the next backup or simply just deleted. An alternative way of accessing that information, thus, may come handy.

Fortunately, RMAN keeps the backup metadata around for some time and it can be accessed through the database’s V$ views. Obviously, if you need this information because your database just crashed and needs to be restored, the method described here is useless.


  [Read more...]
MySQL data backup: going beyond mysqldump
+1 Vote Up -0Vote Down
posted by Open Query on Tue 29 Mar 2011 00:25 UTC
Tags:
(edit) Replication, Backup, mmm, recovery, mysqldump, restore, mariadb, Xtrabackup, Good practice / Bad practice, Software and tools
A user on a linux user group mailing list asked about this, and I was one of the people replying. Re-posting here as I reckon it’s of wider interest. > [...] tens of gigs of data in MySQL databases. > Some in memory tables, some MyISAM, a fair bit InnoDB. According to my > understanding, when one doesn’t have several hours to take a DB > offline and do dbbackup, there was/is ibbackup from InnoBase.. but now > that MySQL and InnoBase have both been ‘Oracle Enterprised’, said > product is now restricted to MySQL Enterprise customers.. > > Some quick searching has suggested Percona XtraBackup as a potential > FOSS alternative. > What backup techniques do people employ around these parts for backups > of large mixed MySQL data sets where downtime *must* be minimised? > > Has your backup plan ever been put to the test? You  [Read more...]
On Hot Backups and Restore using XtraBackup
+3 Vote Up -0Vote Down
posted by Ovais Tariq on Sun 20 Mar 2011 10:48 UTC
Tags:
(edit) mysql, Backup, ubuntu, innodb, myisam, opensource, Backups, transactions, binlog, Percona, online backup, restore, incremental backup, Hot Backup, Xtrabackup, data consistency, cold backup, compressed backup, innobackupex, offline backup, point-in-time backup, prepare backup, read-lock, streaming backup, throttling, transaction log
Backups are an integral and very important part of any system. Backups allow you to recover your data and be up and running again, in the advent of problems such as system crashes, hardware failures or users deleting data by mistake. I had been evaluating backup solution for a while but to be honest I really wasn't satisfied with the solutions available until I came across XtraBackup and I am loving it since. In this post I intend on showing how to do backups and restores using XtraBackup.
Simple Backup Restore Trick
+2 Vote Up -1Vote Down
posted by Gerardo Narvaja on Mon 03 May 2010 19:27 UTC
Tags:
(edit) mysql, tips, Backup, mysqldump, restore
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







  [Read more...]
Applying binary logs without adding to the binary log
+3 Vote Up -4Vote Down
posted by Sheeri K. Cabral on Thu 25 Feb 2010 14:48 UTC
Tags:
(edit) mysql, Pythian, binary log, mysqlbinlog, restore, Technical Blog, disk space

Applying binary logs to a MySQL instance is not particularly difficult, using the mysqlbinlog command line utility:

$> mysqlbinlog mysql-bin.000003 > 03.sql
$> mysql < 03.sql

Turning off binary logging for a session is not difficult, from the MySQL commandline, if you authenticate as a user with the SUPER privilege:

mysql> SET SESSION sql_log_bin=0;

However, sometimes you want to apply binary logs to a MySQL instance, without having those changes applied to the binary logs themselves. One option is to restart the server binary logging disabled, and after the load is finished, restart the server with binary logging re-enabled. This is not always possible nor desirable, so there’s a better way, that works in at least versions 4.1 and up:

The mysqlbinlog utility

  [Read more...]
Tool of the Day: rsnapshot
+0 Vote Up -0Vote Down
posted by Open Query on Thu 17 Sep 2009 00:06 UTC
Tags:
(edit) mysql, Backup, innodb, recovery, open query, rsync, restore, Xtrabackup, Software and tools, rsnapshot

rsnapshot is a filesystem snapshot utility for making backups of local and remote systems, based on rsync. Rather than just doing a complete copy every time, it uses hardlinks to create incrementals (which are from a local perspective a full backup also). You can specify how long to keep old backups, and all the other usual jazz. You’d generally have it connect over ssh. You’ll want/need to run it on a filesystem that supports hardlinks, so that precludes NTFS.

In the context of MySQL, you can’t just do a filesystem copy of your MySQL data/logs, that would be inconsistent and broken. (amazingly, I still see people insisting/arguing on this – but heck it’s your business/data to gamble with, right?)

Anyway, if you do a local mysqldump also, or

  [Read more...]
When a backup is not, and when a restore is a failure
+0 Vote Up -0Vote Down
posted by Open Query on Fri 22 May 2009 19:23 UTC
Tags:
(edit) mysql, Uncategorized, Backup, restore

Since writing and speaking a bit more about the “relax! a failure is not an emergency” concept, more and more people approach me with interesting horror stories. I’m scribbling a few backup-related ones here for your enjoyment - and naturally there are important lessons.

Story 1: A place makes backups that get shipped off-site, interstate even. One day a couple of files are lost, and so someone files a request to retrieve said files from the archive. Well, apparently that’s something that should be done as it creates some very stressed responses and a quoted timeline of a few weeks. In the end the issue is resolved through other means and the request stopped - unfortunate, since it would have been very interesting if the requested files would actually ever arrive… clearly a retrieval was not part of the expected process. One also wonders how

  [Read more...]
Data Backup and Recovery for MySQL - a MySQL Time Machine is Born.
Employee +0 Vote Up -0Vote Down
posted by Charles Bell on Tue 14 Apr 2009 18:37 UTC
Tags:
(edit) mysql, Replication, Backup, database, conference, sun, data, recovery, users, restore, point-in-time

Sure, you've heard it before: [some company's logo] has a new MySQL backup tool that promises to solve all of your data recovery needs. The good news is most of these tools work pretty well. However, they tend to suffer from a similar set of limitations. Most require sophisticated infrastructures or complex setup and maintenance and can become a resource drain for some organizations. You're probably wondering, "Why can't someone build a fully automated MySQL backup solution that you can just turn on and forget?"

I am happy to say that the MySQL Developers at Sun are doing just that. In fact, a prototype will be demonstrated at the 2009 MySQL Users' Conference that will show the feasibility of a fully automated MySQL backup and recovery tool. It's being called the MySQL Time Machine and (with all due respect to all vendors with products of similar names) it allows you to

  [Read more...]
Data Backup and Recovery for MySQL - a MySQL Time Machine is Born.
Employee +0 Vote Up -0Vote Down
posted by Charles Bell on Tue 14 Apr 2009 11:37 UTC
Tags:
(edit) mysql, Replication, Backup, database, conference, sun, data, recovery, users, restore, point-in-time

Sure, you've heard it before: [some company's logo] has a new MySQL backup tool that promises to solve all of your data recovery needs. The good news is most of these tools work pretty well. However, they tend to suffer from a similar set of limitations. Most require sophisticated infrastructures or complex setup and maintenance and can become a resource drain for some organizations. You're probably wondering, "Why can't someone build a fully automated MySQL backup solution that you can just turn on and forget?"

I am happy to say that the MySQL Developers at Sun are doing just that. In fact, a prototype will be demonstrated at the 2009 MySQL Users' Conference that will show the feasibility of a fully automated MySQL backup and recovery tool. It's being called the MySQL Time Machine and (with all due respect to all vendors with products of similar names) it allows you to

  [Read more...]
Data Backup and Recovery for MySQL - a MySQL Time Machine is Born.
Employee +0 Vote Up -0Vote Down
posted by Charles Bell on Tue 14 Apr 2009 11:37 UTC
Tags:
(edit) mysql, Replication, Backup, database, conference, sun, data, recovery, users, restore, point-in-time

Sure, you've heard it before: [some company's logo] has a new MySQL backup tool that promises to solve all of your data recovery needs. The good news is most of these tools work pretty well. However, they tend to suffer from a similar set of limitations. Most require sophisticated infrastructures or complex setup and maintenance and can become a resource drain for some organizations. You're probably wondering, "Why can't someone build a fully automated MySQL backup solution that you can just turn on and forget?"

I am happy to say that the MySQL Developers at Sun are doing just that. In fact, a prototype will be demonstrated at the 2009 MySQL Users' Conference that will show the feasibility of a fully automated MySQL backup and recovery tool. It's being called the MySQL Time Machine and (with all due respect to all vendors with products of similar names) it allows you to

  [Read more...]
Maatkit Options for Restoring a Slave or Master
+0 Vote Up -0Vote Down
posted by Gerardo Narvaja on Wed 13 Aug 2008 06:32 UTC
Tags:
(edit) mysql, Maatkit, options, restore

The Maatkit toolkit is a real blessing for the MySQL DBA. And while its documentation is pretty good, in some cases it’s necessary to read carefully a second and third time to make sure you are not missing an important piece of information. In this article I will comment on mk-table-chksum and mk-table-sync. My comments are mostly aimed at those DBAs who are considering using these utilities with medium or larger-sized databases.

–replicate

This option allows you to store the checksum results on the master, in a table that will get replicated to the slaves. Although it might seem like overhead for a simple check, it really simplifies your life, especially when used

  [Read more...]
Showing entries 1 to 13

Planet MySQL © 1995, 2013, Oracle Corporation and/or its affiliates   Legal Policies | Your Privacy Rights | Terms of Use

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.