Data Recovery · Mumbai

Linux data recovery
when it actually matters.

ext4 wiped. RAID degraded. Server formatted by mistake. We've seen it. We charge only if we get your data back.

🔒

₹75,000 fixed. Only on success. No partial fees. No "assessment charges." If we don't recover your data, you pay nothing. GST applicable.

Scope — software recovery only

This is logical and software-level Linux data recovery — filesystems, RAID arrays, deleted data, corrupted volumes, database files. Physical platter-level recovery (clicking drives, seized spindles) requires a cleanroom and specialist hardware we don't have. We'll tell you immediately if your situation needs that — and we won't charge you for that assessment.

// what we recover

If it ran Linux, we can work on it.

Six scenarios that arrive in our inbox, week after week.

Formatted Linux server

mkfs ran on the wrong partition. The data's still there on the blocks. We stop all writes and work the superblock and inode tables before any more gets overwritten.

ext4 / XFS / Btrfs

RAID array failure

RAID 5 with two failed drives, or a RAID 0 stripe that lost one disk. Software RAID via mdadm or hardware RAID controller — we rebuild or extract directly from the member disks.

RAID 0/1/5/6/10

Accidental rm -rf

Someone ran it as root. Or a script went recursive in the wrong directory. If the filesystem hasn't been written over, inode recovery is feasible on most Linux filesystems.

ext4 · deleted inodes

LVM / partition table corruption

LVM metadata wiped, VG not accessible, or the partition table got zeroed out during a failed resize or a bad fdisk run. We scan, reconstruct, and mount.

LVM2 · GPT / MBR

Database files on Linux

MySQL/MariaDB or PostgreSQL datadir on an ext4 volume that got corrupted. We recover the raw InnoDB tablespace or pg_data directory before attempting a logical restore.

MySQL · PostgreSQL · SQLite

Ransomware / encrypted server

Post-ransomware Linux server where the encryption hit only part of the volume. We isolate, image the disk, and attempt recovery on unencrypted data blocks before any decryption negotiation.

Incident response

// how it works

From the call to recovered data.

No intermediaries. No cleanroom theatre. Linux commands on the actual disk.

Call or form — immediate response

You reach us by phone or the emergency form. We ask three questions: distro, filesystem type, what happened. That's enough to know if recovery is viable.

Response: within 2 hours, business hours · 24/7 for retainer clients

Stop all writes immediately

First instruction is always: unmount the volume. Do not write anything to that disk. Every new write overwrites blocks that might contain your data. We walk you through this remotely if needed.

This step happens before we even quote anything

Disk image — always

Before any recovery attempt, we create a sector-by-sector image using ddrescue or dd. All recovery work happens on the image. Your original disk stays untouched.

Non-destructive by default

Recovery attempt + viability assessment

We run the recovery on the image. testdisk, photorec, extundelete, manual inode scanning depending on what the situation calls for. We tell you what we found before you pay anything.

You see a file listing before we confirm success

Data returned + engagement letter signed

Recovered files are delivered to a medium you specify. You sign the Data Recovery Engagement Letter. You pay ₹75,000 + GST. If recovery fails, the letter isn't signed and you pay nothing.

Payment only after confirmed recovery

// supported

Filesystems and configurations.

ext2 / ext3 / ext4

Default on Ubuntu, Debian, most production Linux servers

XFS

RHEL, Rocky Linux, AlmaLinux default — large file systems

Btrfs

Snapshots, subvolumes, RAID modes — we work the subvolume tree

LVM2

Logical volume metadata reconstruction, VG rebuild

mdadm RAID

Software RAID 0/1/5/6/10 — member disk extraction and rebuild

ZFS

Pool import from failed/degraded vdevs — assessed case by case

tmpfs / NFS

Volatile filesystem data where underlying source is recoverable

Hardware RAID

LSI, Adaptec, HP SmartArray — member disk bypass when controller fails

LUKS encrypted

If you have the passphrase/keyslot — we decrypt, then recover

// pricing

One number. No surprises.

No diagnostic fees. No "partial recovery" billing. If the data comes back, you pay once.

₹ 75,000 + GST

// fixed · success-only · no upfront payment

Disk imaging before any recovery attempt
Full recovery attempt — all applicable tools
File listing shown to you before payment
Data delivery to medium of your choice
Data Recovery Engagement Letter (signed on success)
30-minute post-recovery consultation on what happened

GST (GSTIN: 27ACAPV2614B1Z0, SAC 998313) applicable on the ₹75,000 fee. If recovery is unsuccessful, no invoice is raised. You pay nothing.

Retainer clients Data recovery is covered under your monthly retainer for incidents that arise from server events we were managing. No separate fee. This is one of the reasons businesses put us on retainer.

// real recovery

A case from the field.

RAID 5 Recovery Data recovered Mumbai

Jewellery manufacturer — ERP database on a 3-disk RAID 5

A Mumbai jewellery firm running ERPNext on a 3-disk RAID 5 lost two drives within 48 hours — one during a power failure, the second during the rebuild. The array went offline. The IT team had no recent backup of the database volume.

Situation

RAID 5, 2 of 3 member disks failed. mdadm array in a failed/degraded state. Last verified backup was 11 days old. ERPNext database: 4 years of transaction history.

What we did

Imaged all 3 member disks. Reconstructed RAID stripe geometry manually. Mounted the reconstructed ext4 volume read-only. Extracted the MySQL InnoDB tablespace intact.

Result

100% of database tables recovered. Data loss: zero. Client restored ERPNext from the recovered datadir the same evening. Recovery time: 7 hours from first call.

What changed after

Client moved to an AV Services retainer. Automated daily backups to an off-server location now run under our management. RAID is now RAID 6.

// faq

Questions people actually ask.

Do I need to ship my server to you? ↓

Most recoveries happen remotely over SSH once you've unmounted the affected volume. For physically failed drives we either come onsite in Mumbai (2hr response) or you courier us the affected disks. We tell you which is needed after the initial call.

What counts as "successful recovery"? ↓

We show you a file listing or database table listing from the recovered image. You confirm the data is what you needed. That's the trigger for the engagement letter and payment. We don't define success — you do.

How quickly can you start? ↓

Same day for Mumbai, often within hours. The first step — stopping all writes to the disk — costs nothing and you can do it right now. Call us and we walk you through it immediately, before any formal engagement.

What if the disk has physically failed (clicking, not spinning)? ↓

Mechanical failure with physical platters is outside our scope — that requires a cleanroom. We'll tell you immediately if that's the case and point you to the right service. We don't charge for that assessment.

Can you recover from a server that's been ransomwared? ↓

Sometimes. If the encryption only hit part of the volume, or if shadow copies / older snapshots exist on the filesystem, there's recoverable data. We image first, then assess. We also handle the incident response side — isolating the server, identifying the attack vector.

We're not in Mumbai. Can you still help? ↓

Yes. Remote recovery works for most scenarios. For pan-India onsite, we can reach any major city within 24 hours. Travel actuals billed separately on top of the ₹75,000 recovery fee for onsite cases.

Linux data recoverywhen it actually matters.