A site showing "error establishing a database connection", or a MySQL service that refuses to start after a power cut? We work on InnoDB and MyISAM files directly on disk: copy first, then extract the tables from ibdata, ibd and MYD files, rebuild the database and bring the site or the program back up on it.



Stop the service and do not repair tables before the data directory has been copied.
When the service refuses to start, the data is usually still there: the files sit in the data directory and the engine simply will not open them because of a fault in the tablespace or the redo log. So our first step is not another start attempt, it is a full copy of the data directory.
After that the InnoDB files are read at page level: the data dictionary is extracted and records are read back out of the per-table ibd files even when ibdata1 itself is damaged. MyISAM tables are handled from their MYD and MYI files once the indexes are rebuilt.
And because the target is the site or the program rather than the files, the database is reinstated on a healthy service and the system is started on it, with orders, customers and stock checked before handover.
Read the state of the data directory and the service logs and identify the damage.
What can be recovered, how long and at what cost, before any work.
A full copy of the data directory; work happens on the copy.
Pull tables out of the InnoDB and MyISAM files and rebuild the database.
Reinstate it on a healthy service, start the site or program and test it.
Copy the data directory as it is first; everything afterwards is built on that copy.
For data recovery, database recovery, accounting software recovery and business software recovery in Kuwait, contact A2Z MegaStore. Call or message on WhatsApp:
Location: Hawally, Kuwait.
Usually not. The files remain in the data directory and the fault is in the tablespace or the redo log. We copy the directory and extract the tables from the copy.
Yes. The work starts from the database files on disk. A backup shortens the job but is not a requirement.
Not necessarily. Where tables are stored in separate ibd files they can be extracted and the dictionary rebuilt, and we recover what we can even when the central file is damaged.
Stop writing to that disk immediately and do not create a new database in its place. Every new write can cover the deleted data and cost you the recovery.
Yes, including order, customer and product tables. We reinstate the database and confirm the orders are visible before handover.
One to two working days for the inspection, then the case decides. Logical damage is usually faster than damage to the storage media itself.
Call or message A2Z MegaStore on WhatsApp: +965 60991679 , +965 66963646 , +965 60380183. Location: Hawally, Kuwait.
A2Z MegaStore, Hawally, Ibn Khaldoun St, Al-Qairawan Complex, Mezzanine 21, Kuwait
For data recovery, database recovery, accounting software recovery and business software recovery in Kuwait, contact A2Z MegaStore. Call or message on WhatsApp:
Location: Hawally, Kuwait.
Please switch the device off, then submit the data recovery request form or contact us on WhatsApp. Work begins with an inspection and a written report before any procedure is carried out.