Showing posts with label MySQL Recovery. Show all posts
Showing posts with label MySQL Recovery. Show all posts

Wednesday, February 29, 2012

3 Tweaks that Helped Me TO Recover MySQL Database In Few Hours


When I starts MySQL Server, I am not able to perform any action on it. Like other users, I am also stuck with MySQL Recovery process. But I am not able to understand “what is the reason behind it?” Recently, I made several changes to MySQL database that increased the speed of the database. 


Sometimes MySQL database can become inaccessible because of internal database corruption errors, hardware failure, software failure, power interruptions etc. Each possible database failure error requires a different recovery action. Protect your data against the possibility of data loss by having a well known recovery strategy in place. 


The tips I’m about to give you, it won’t cost you thousands of dollars—in fact, implementing these tips won’t cost you a cent. And they can easily be used by any user. My Guide will help you to recover your MySQL database in few hours. When you will apply any recovery strategy on your database then first check:


  • The database can be in recoverable stage?
  • Mark the time that will be spent to recover your database?
  • Mark the time that spent to performing backup operations?
  • How much storage space can be allocated for backup copies and another files.
  • Will Single table backup be sufficient, or will full MySQL database backups be necessary?


So these are some general terms you should know before performing MySQL Database Recovery 


3 useful tweaks:


Regular schedule for taking database backup:  The concept of a MySQL database is the same as any other database backup. Before taking the backup first shutting down the database to ensure that no further transactions occur, and then simply backing it up. Storing it on a different medium in case of failure or damage to the original. You can then rebuild the database if it becomes damaged or corrupted in some way. Take backup on regular basis to avoid the data loss.


Use Inbuilt Utilities to recover database: The inbuilt utility selection is depend on three terms:

1.Only want to repir MyISAM tables;
2.repair corruption of the other table types;
3.Restore from backup;
If you only want to repair MyISAM tables, use this command:

REPAIR TABLE tablename[,tablename1...] [options];
myisamchk [options] tablename.MYI;

You can use inbuilt MySQL database utilities to repair all corrupt MySQL database tables: 

mysqlcheck [options] dbname tablename [tablename2... ];

or in last you can use restore option to repair MySQL database from the backup. These are some inbuilt utilities examples which you can use to repair MySQL database. 


Commercial Solutions: Third-party recovery software is one another solution to repair corrupt MySQL database & repair all corrupt MySQL database files. The software is build with very advanced technology & work for all MySQL database tables. 


So these are three tweaks to recover MySQL database. If the article helps you to recover your MySQL database, please give your valuable comments..
»»  Read More...

Thursday, July 14, 2011

How to reslove error- “ERROR 29 (HY000): File 'tablename.MYD' not found (Errcode: 13)”

Have you encountered the following error message:

ERROR 29 (HY000): File 'tablename.MYD' not found (Errcode: 13)

Three conditions in which this error message occurs:
  1. When MYD-file permission denied.
  2. When the table is corrupt.
  3. When the .MYD file lost.

Choose Any Solution As Per Your Requirement:
  1. Check the permissions of the MYD-file and the directory. Putting files in the MySQL data directory or some other path where the server has read permissions.
  2. Execute the repair table command to repair corrupt table. REPAIR TABLE rebuilds the entire table and index.
  3. You can restore your database from your regular updated backup.

Note: It is best to take a backup of a table before applying a table repair operation.

Either the above command repairs corrupted MySQL database or there is a possibility of getting a new error message after this command:

error: File '../diaendomet/users.MYD' not found (Errcode: 2)

If you got this error message, it means MySQL database has been severely corrupted. In this case you can use Third party MySQL Recovery Software. These software repairs corrupt MySQL database in case of no backup. The Software repairs .myi, .myd, .frm (MyISAM database engine) files as well as .ibdata, .ibd, .frm (InnoDB database engine) files.

Note: Always remember that use these software on the copy of the corrupt database file. If anything went wrong, it will affect only duplicate copy of the database not the original one.

There are uncountable MySQL database errors that could be the reason of MySQL database corruption. There is no surety that every recovery software repairs corrupt MySQL database after all MySQL database error. So I will suggest you to first try demo version & take a fair idea about the software after that purchase it.
»»  Read More...