If you have a database which has entered "Suspect" status, will not attach, or produces error messages regarding corruption, then your business may come to a grinding halt. Restoring a previous day's back-up may be possible; however, only if there was sufficient integrity within said back-up. Typically, corrupted databases can be recovered directly from their underlying data files. We provide recovery services for all engines (including SQL Server, MySQL, Oracle, PostgreSQL) for businesses throughout Northern Ireland and Belfast, in-house.
While attempting to correct a database which has been damaged by corruption, the typical solutions may include one of two options: an emergency repair procedure which could result in data loss or restore a prior back-up over top of the active files. Neither solution would preserve recoverable rows. Create a copy of the underlying data files as they exist now (MDF, NDF & LDF, etc.) before implementing any correction procedures and allow us to proceed with correcting the issues identified within these copied files.
Database failures occur when either their data files, log files, back-ups or the physical storage media upon which they reside experience failure. It is with these types of failures that we typically find ourselves recovering data.
Any damaged or lost data from any database system/file-type can be restored, be it corrupt files or failed storage underneath.
The types of databases we can recover include Microsoft SQL Server & Access, MySQL & MariaDB, PostgreSQL, Oracle, Exchange, SQLite, MongoDB, Firebird, Sybase and IBM Db2, which include MDF/NDF/LDF sets, InnoDB & MyISAM (ibdata1 & .ibd), as well as EDB, DBF, ACCDB and BAK, regardless of where the database resides: on a single drive, as part of a RAID array, or on a NAS or SAN.
The process for database recovery starts at the bottom with the files. Once a backup copy of both the data and log files have been made, we can start repairing or extracting information from these backups to create a new, stable and functional version of the database, and if the underlying storage system (like a hard disk) has failed, we will first need to recover that. Originals are never fixed "in-place".
Once we know which type of database engine you are using, what group of files was corrupted and how bad the damage is; we will determine whether the underlying storage system (such as a single hard drive, RAID or SAN array) is healthy; after which time we provide you with a written quotation.
When one of the drives, RAIDs or arrays holding your database fails, we restore that from read-only images before we even touch your database files.
We only work off copies of your original data and log files (MDF, NDF, LDF etc.). This means that your original files remain untouched throughout our entire recovery process.
We repair your file structure, page and index issues, or when this is not an option, we simply pull out all of the individual tables, rows and other objects from the original data file.
We take all the pieces and rebuild a complete, usable database, restoring it based on the data file, if there's no log file available; and then restore the dropped tables and deleted rows from the database.
Then we check the recovered database to see if everything has been restored correctly and that it contains all of its tables and records; and then we can show you what was recovered prior to returning your original database.
Your database is provided as attachable files or exports. This can be provided on new media or via secure transfer. Whatever best fits your environment.
From a SQL Server database in suspect mode; to a corrupted MDF file; to a dropped table, or a database loss due to a RAID failure; we work with every type of engine (we work directly from copies of the data files; and rebuild the storage below where necessary).
Give us some information regarding what happened to cause this issue, and an engineer will contact you. Usually within a single business day.
We will get back to you soon. If it is urgent, call 028 9002 0144.
Assessment is no charge and you will receive a fixed written quotation prior to proceeding. A fix of a corrupted database whose files remain intact costs from £500 + VAT; if the underlying storage, i.e. drive or array, has also failed, then the price for recovering the data starts at £800 and will be provided separately. In most cases, you only pay if your data has been recovered and in all instances, there will be an advance payment required by us relating to replacement parts & labour charges when working on physical disks which will represent 50% of the total cost of such work. The remaining 50% will only become due upon successful completion of the data recovery.
Our work included numerous examples of recovering databases using a variety of engines and fault conditions; we have provided some sample cases and results (customer identifying information is removed).
Due to a write failure during a crash the system was unable to recover from this failure; however, our engineers made repairs on copies of the files, restored the structure of the database, and returned the entire database to an operational state without loss or damage.
As the ibdata and .ibd files were damaged we were able to extract the tables directly out of the tablespace and rebuild a fully functional database.
The main table for an application had been deleted. There was no longer a transactional log that could be used to restore the table. In this instance, we were able to recover the main table from the MDF alone as well as all of its records and rebuild one row at a time in order to provide full functionality to the client.
Multiple data blocks on the server were corrupted which made it difficult to read information out of those blocks. In addition to repairing the damaged block(s), we also pulled out schema and table information from the surrounding areas so that once the repairs were completed, the client would have access to the same types of reports they previously relied upon.
The client's Access Database (.ACCDB) would not open. They had attempted to repair but were unable. We were able to extract all of their tables, queries and forms from the .ACCDB file, create new versions of each item and then build a completely functional version of the database that provided all of the features they needed.
One of the servers hosting a SQL Server database had an array attached underneath which had become unavailable. We rebuilt the RAID 5 using disk images, recovered both the MDF (main data file) and LDF (transaction logs) files and got the client back online.
Send or drop off your item for a free diagnostic check with a description of the issue. One of our engineers will review the item, then provide you a written quote prior to doing any repairs.
Prior to sending or dropping off your device for a diagnostic test (free), obtain a quotation from us via telephone or using the provided form. Step one: get the device to our Belfast bench. Carefully wrap the device and include your contact information inside the parcel. Then send it over. There is no charge for this diagnostic service. Once we receive it, you will be given a firm written price to confirm whether you wish to go ahead, before any work is done.
Sending it? The use of a tracked, insured delivery method would be recommended. Alternatively, dropping it off can also be done Monday to Friday, 9am–5:30pm; no prior booking required but do ensure that all items are packed accordingly.
Still waiting to send something? Please complete the form describing the failure/fault in your own words and one of our engineers will get back to you with a quotation based upon your individual circumstances.
We will get back to you soon. If it is urgent, call 028 9002 0144.
These are the questions we get asked most often regarding database recovery.
Normally, yes. Most times when databases get into suspect mode it is because something has caused the database recovery process to stop (because of a log issue or some other file issue), but the actual data itself remains intact. We will work off copies of the MDF, NDF and LDF files and either repair the data file's structural integrity or pull the tables and/or rows out of the damaged data file and build a new database from them. Take a copy of these files before running any repair.
Yes, these are typically among the engines that we have the most experience in repairing. Regardless of whether the damage is to individual pages, indexes or the overall file structure, we can repair/extract data from the damaged data file(s) and build a consistent working database from them.
Very often, yes. The dropped table or deleted/updated rows generally stay in the data file until they are rewritten over. Once you realise what has happened, cease all access to the database immediately and make a copy of all files. There is a very good chance we will be able to retrieve your lost records.
Yes, this is another fairly common scenario. If the log file is missing/corrupt then it does not necessarily mean the data is missing/lost; we can recover the database solely based upon the MDF/data file and rebuild enough consistency to put the database back on line.
For a corrupt database where the underlying files are still accessible, our rates begin at £500 + VAT. Where both the underlying drive/array has failed also, prices for jobs begin at £800 and each job is priced on an individual basis after completion of the initial no charge assessment. In most cases you only pay us if we are successful in recovering your data. Any costs associated with physical repair of your disk(s) require a deposit for materials/parts and bench time. Payment for the remainder of the cost will only occur on successful completion.
In most cases, yes, you only pay us if we have recovered your lost data. If disks below the database are damaged and require physical repair, there will be a deposit to cover those parts and the labour cost associated with that repair; again, the remainder of the charge is based solely upon our ability to successfully recover your data. Prior to any work being done, we will clearly identify what type of payment applies.
All the big names (SQL Server, MySQL, MariaDB, Oracle, PostgreSQL, Microsoft Access, Exchange, MongoDB, SQLite, Db2, Firebird and Sybase), through all of their respective data, logs and backup files, regardless of the type of disk or storage they may be located on.
Yes. When the storage platform supporting a database fails, we first rebuild that (by taking images of the disk and rebuilding the RAID array), then proceed to recover your database files from the newly built platform and restore them. The work required is essentially identical; just at different layers.
Within honest limits, yes. We will attempt to recover your backed-up data, snapshots and/or other unencrypted copies of the database, and we will certainly search for these first, as an already-encrypted version of your database generally can't be decrypted without the key. However, we would never recommend paying a ransom to obtain the decryption keys for your database file(s) that were encrypted by ransomware.
In general terms, readable but corrupted versions of your database should take anywhere from 2 to 5 full business days to recover; whereas, when rebuilding the storage platform underneath the original database files must occur first (e.g., imaging/rebuilding failed disks), this entire process normally takes approximately 5 to 10 full business days. We can prioritise business critical databases, and we will usually complete our assessment within a couple of days.
When you can copy the files, a safe way of transferring the data, logs and any backups will usually be the fastest method; please contact us and we'll arrange this. If your database has become "stuck" due to a faulty drive or array, please deliver or post the relevant disks to our office in Belfast, fully insured. Our opening hours are Monday to Friday 9am to 5:30pm.
Free assessment; fixed written pricing starting at £500 + VAT; and in most cases, you only pay if we have successfully recovered your data. All database engines are recovered in-house in Belfast. Do not perform a lossy repair or restore over the original files. Copy the files and send them in.