PikoSystem IT engineering services
فا Emergency Talk to an engineer
Emergency

Urgent server data recovery and backup restore

A RAID array failed, a database was dropped by mistake, or a virtual machine will not boot. In server data recovery, our first step is to stop anything writing to the affected disks, because every new write can destroy recoverable data. We focus on logical recovery, backup restores, databases and virtual machines, and if a disk is physically damaged we say so plainly so it can go to a hardware lab.

0900-000-0000 Send an urgent request
Tools & technology data-recovery
  • mdadm
  • ddrescue
  • TestDisk
  • LVM
  • VMware ESXi
  • Proxmox
  • Veeam Backup & Replication
  • mysqlbinlog
  • SQL Server
5work areas
4deliverables
4steps

What is Server Data Recovery?

Server data recovery is the logical recovery of files, databases and virtual machines after a RAID failure, accidental deletion or a broken backup. It is needed when a RAID 5 volume will not mount after a drive failure, a database was dropped by mistake, a virtual machine on ESXi will not power on, or a backup restore keeps failing. PikoSystem stops writes to the affected disks and images them with ddrescue, rebuilds mdadm or hardware arrays read-only from their metadata, restores databases from the last backup plus MySQL binary logs or SQL Server transaction logs, and examines damaged vmdk and qcow2 files. Physically damaged disks are referred to a hardware lab. You receive the recovered data in a location you choose, a list of what could and could not be recovered, and a report on the cause.

When you need Server Data Recovery

  • One drive failed and now the server's RAID 5 volume won't mount.
  • A colleague dropped our main database by mistake.
  • A virtual machine on ESXi throws a vmdk file error and won't power on.
  • We have backups, but the restore fails and we don't know why.

What Server Data Recovery includes

01

Stop the damage and image

We stop writes to the affected disks and image them with ddrescue. Every recovery attempt runs against the image, and the original disks stay untouched.

02

Logical RAID reconstruction

We work out disk order, stripe size and array parameters from the metadata and rebuild the array read-only. We handle mdadm software RAID and hardware arrays whose disks are physically healthy.

03

Database recovery

We bring a dropped database back from the last backup plus the MySQL binary log or SQL Server transaction log up to the moment before the mistake, provided those logs were enabled.

04

Virtual machine recovery

We examine damaged vmdk files and snapshots on VMware ESXi and qcow2 disks on Proxmox, then boot the machine or extract the data inside it where possible.

05

Backup restore troubleshooting

We find out why restores fail in Veeam, Proxmox Backup Server or control panel backups, and restore and test the backup in an isolated environment.

What you get from Server Data Recovery

  • Recovered data delivered to a location you choose
  • A list of recovered files or tables and anything that could not be recovered
  • A report on how the data was lost and the steps taken
  • Backup recommendations to prevent a repeat

Server Data Recovery: a practical guide

Deleted a file on the server? Where to look first

Files deleted from a network share never reach the Recycle Bin. Check Windows Shadow Copies first. If they are enabled on the volume, the Previous Versions tab can bring back earlier copies of a folder. On a Synology or QNAP NAS, look at the shared folder recycle bin and snapshots, and on Proxmox with ZFS, look at dataset snapshots.

SSDs behave differently. With TRIM enabled, the blocks of a deleted file are wiped quickly and software recovery rarely helps. Disks encrypted with BitLocker or LUKS cannot be recovered without the recovery key, so decide in advance where that key is kept.

SQL backup restore errors and how to fix them

A backup from a newer SQL Server version will not restore on an older one, and there is no workaround. If the MDF and LDF paths differ on the new server, restore WITH MOVE, and if the database is in use, set it to SINGLE_USER first.

Before restoring over a database that still opens, take a tail-log backup so transactions since the last backup survive. Order matters: full backup, then differential, then logs WITH NORECOVERY. After a move to another server, database users are no longer mapped to logins and need ALTER USER to reconnect them.

Restoring a cPanel backup without losing newer data

A full cPanel backup (a tar.gz file) can only be partly restored from inside the account. A complete account restore runs through WHM with root access. If the host uses JetBackup, files, databases and mailboxes come back as separate restore points.

Save the current state before restoring, since restoring over an existing account overwrites newer data. It is safer to restore a database into a new, empty database first and check it. For large SQL files, phpMyAdmin's upload limit gets in the way, and importing with the mysql command line is more reliable.

How to choose a server data recovery provider

Before handing over disks, ask whether they work from an image or on the original drives. Working on the originals removes the chance of a second attempt. Ask whether they have a clean room for physically damaged disks or send them elsewhere, and whether you get an assessment report before work begins.

Confidentiality should be in writing: a non-disclosure agreement, who can access the data, what media it is delivered on, and when copies left with the provider are deleted. Also agree up front how billing works if the recovery fails.

How Server Data Recovery works

  1. 01

    Call and stop using the system

    You describe what happened. We ask you not to run any recovery software or write anything to the disks until we have looked.

  2. 02

    Assessment

    We identify the type of failure and tell you whether logical recovery is possible or the disk needs a hardware lab.

  3. 03

    Image and recover

    We copy the disks or files and run the recovery against that copy.

  4. 04

    Handover and verification

    We hand over the data and check with you that files and databases are intact.

Server Data Recovery: frequently asked questions

Can you guarantee all the data will come back?

No. The result depends on the type of failure, what was done after the incident and whether backups or logs exist. After the initial assessment, we tell you plainly what is likely recoverable and what is not.

Is RAID 5 recovery possible after two drives fail?

RAID 5 survives the loss of one drive. If the second drive only dropped out of the array but is still readable, the array can be rebuilt from disk images. If it is physically damaged, it first has to be read in a hardware recovery lab.

What should we avoid until you get there?

Do not run rebuild or initialize on the RAID controller, do not run fsck or chkdsk, and do not install recovery software on the same disk. Keep the server off, or at least stop all writes to the disks.

The disk is making clicking noises. Can you recover it?

Clicking usually points to mechanical damage, and keeping the disk running makes it worse. Mechanical recovery needs a clean room and a hardware lab, which is outside the scope of this service. Power the disk off. Once a lab has imaged it, we can take over the RAID and database recovery.

Related searches

  • server recovery
  • RAID data recovery
  • RAID 5 recovery
  • recover deleted database
  • server backup restore
  • urgent data recovery
  • VMware virtual machine recovery

Related services

Urgent

Report an urgent problem

For a full outage, a phone call is the fastest route. If you can't call, fill in the form and we'll call you.

Call now 0900-000-0000
  1. 01We call you and get the details.
  2. 02Contain the damage and preserve logs before changing anything.
  3. 03Fix the issue, then report the cause and what was done.

Your details are only used to answer this request.