- Client
- Confidential
- Sector
- Sector Not disclosed
- Outcome
- Critical data recovered, usable backups rebuilt, and several customer systems back in use
- What we do
- Analysis of the damaged databases and backups, data recovery, rebuilt backups, and integrity fixes after restoration
What was at stake
The data included audit trails and workflow records built up through years of everyday use. None of it could be recreated from scratch. Losing it would have meant losing the history the business and its customers relied on.
The problem also spread across several customer environments, not one database. Each one, and each backup, had to be looked at separately.
What we did
We worked with the client’s technical team to analyse the damaged database files and the backups that existed. Each database was assessed for what could be recovered, and a recovery plan was built around that.
Business-critical records were recovered, structures rebuilt where needed, and restored backups produced for testing before anything went live. Recovered data was checked for accuracy. Where the usual methods couldn’t get the data back, we used other techniques to recover more.
What the business kept
Large volumes of historical and audit data came back, alongside customer and operational information that would otherwise have been lost. Several customer systems returned to service, and the client carried on supporting its own customers.
Recovery was also far more practical than trying to rebuild the information by hand, where that would even have been possible.
Has a database stopped opening?
Don’t keep trying to open or repair it. Take a copy if you can, and ring. We’ll tell you what’s likely to be recoverable.
