Database Recovery Services

Not before a copy is taken and an assessment is done. That option can discard data that a file-level recovery could have retrieved.

Often, yes — these usually indicate datafile or control file corruption rather than actual data loss. We read the affected files directly at the block level, independent of the Oracle instance, to assess what's recoverable before any repair is attempted.

It varies by variant and file size. Some encrypt only the first portion of each file, leaving much of a large database intact; others encrypt fully. We assess before quoting.

Speed, mainly. Fully encrypting a 50GB+ datafile with strong encryption takes meaningful time per host, and most ransomware operators want to hit as many machines across a network as possible before defenders notice and start isolating systems. Encrypting just a file's header and a handful of blocks is usually enough to make the database engine refuse to open it — which is all the attacker needs for leverage — while leaving most of the actual data pages inside untouched. That's the gap file-level, page-by-page recovery works from.

Sometimes, from unallocated pages or transaction logs, provided the space hasn't been reused. Time matters.

Yes. Most database recovery is logical — worked from disk images and backup files rather than requiring anyone on-site — so we support clients across these and other Indian cities remotely, with secure courier for physical media and on-site visits arranged for enterprise engagements where needed.

Yes. We have recovered many damaged and ransomware-encrypted Tally, Busy and Marg data sets. Send us a copy of the company data folder; we tell you exactly which companies, years and vouchers are recoverable after a free assessment, and you pay only if we recover your data.

Usually, yes. The rows are still inside the .ibd tablespace; what is missing is the link between the file and the data dictionary. We read the tablespace directly and rebuild the table. Do not delete or overwrite the .ibd file in the meantime.

The assessment usually starts the same day. Many SQL Server, MySQL and accounting data recoveries are finished within one to three days; very large or heavily damaged databases take longer, and we tell you the expected time after the assessment.

Yes. Database recovery is the centre of our work: corrupted database recovery, encrypted database recovery after ransomware, and recovery of deleted or dropped data, for SQL Server, Oracle, MySQL, PostgreSQL and SAP HANA. Enterprise database recovery for ERP and line-of-business systems is handled the same way, table by table.

Repair tries to make the damaged file usable again in place. Recovery extracts the tables and rows from the damaged file into a new, clean database. For badly corrupted or partly encrypted databases, extraction is safer, because the original file is only read and never changed.