Resources Case Studies

Five databases, from 11.19 TB to 4.22 TB

Storage was growing faster than it was budgeted for, and the answer on the table was buying more of it. Compression, index work and a renegotiated allocation meant none of it had to be bought.

Five critical databases

62%

Compressed from 11.19 TB to 4.22 TB, with backup and refresh times improving alongside.

Reclaimed by compression
6.97 TB
Reclaimed by index compression
2.5 TB
Added at no cost
3.7 TB

In short

What happened

A leading mortgage technology company processing millions of transactions a year was consuming storage faster than it had budgeted for, with five major databases past 11 TB between them and urgent space alerts on production. Under a managed service, Fortified Data compressed those five from 11.19 TB to 4.22 TB, a 62 percent reduction, applied index compression across four more servers for a further 2.5 TB, and negotiated a 3.7 TB storage increase at no cost by leveraging the existing disk allocation. Free space across the environment went from 5.98 TB to 12.95 TB, and daily backups now copy to Azure blob storage instead of restoring from VM disk.

62%

Reduction across five critical databases, from 11.19 TB to 4.22 TB, which also improved backup and refresh times.

Fortified Data case study, 2025

12.95 TB

Free space across the environment, up from 5.98 TB, without a capital purchase.

Fortified Data case study, 2025

3.7 TB

Of additional storage negotiated at zero cost, by leveraging disk allocation the client already had.

Fortified Data case study, 2025

When storage growth outruns the budget

This platform processes millions of transactions annually across an enterprise estate, and its data volumes were growing exponentially. Storage capacity was being consumed faster than it had been budgeted for, with five major databases exceeding 11 TB between them, and urgent space alerts were arriving on production systems and threatening business continuity. The obvious answer, buying more storage, was the one answer the budget did not allow.

Disaster recovery had a cost of its own. Restoring from VM disk is both time-consuming and expensive, and it sets a recovery time that has nothing to do with how quickly the business needs the data back.

Two more things were compounding it. Poorly optimized indexes were degrading the daily data refresh, and backups were being run manually, which turns every time-sensitive recovery into a bottleneck at the worst possible moment.

What the managed service did

Three workstreams, running alongside each other

None of these is a stage of the others. They ran under one managed service over the same period, which is why they are three cards and not five numbered steps.

Cloud-enabled disaster recovery

An automated process copies daily hot backup files to Azure blob storage, so recovery is rapid and the costly, time-consuming VM disk restore is gone. It delivered time and cost avoidance even before the automation was fully in place.

Strategic storage optimization

Five major databases compressed from 11.19 TB to 4.22 TB, free space across the environment raised from 5.98 TB to 12.95 TB, and index compression applied across four servers for a further 2.5 TB. Database refresh performance improved and the monthly operational workload came down with it.

Cost avoidance and rapid response

A 3.7 TB storage increase negotiated at zero cost by leveraging the existing disk allocation, and two 2.4 TB databases compressed and shrunk in under nine days after a low disk space alert on a 32 TB drive. Both avoided capital expenditure the budget did not have.

What changed

  • Five critical databases reduced by 62%From 11.19 TB to 4.22 TB, which dramatically improved backup and refresh times as well as freeing the space.
  • Free space more than doubledFrom 5.98 TB to 12.95 TB across the environment, deferring the infrastructure investment the growth curve had been pointing at.
  • 3.7 TB secured at no costThrough optimization of the allocation the client already held, rather than through a purchase order.
  • Disaster recovery off VM restoreDaily hot backups to Azure blob storage, which removes both the cost and the recovery time of the VM disk procedure it replaced.
  • A nine-day response to a production alertTwo 2.4 TB databases compressed and shrunk in under nine days after a low disk space alert on a 32 TB drive, through normal change management.

Three ways to work with us

On-Call DBA

A guaranteed 15-minute emergency response plus monthly on-demand hours that bank when unused.

Read more

Is the storage quote the only option on your table?

Compression, index work and a renegotiated allocation are cheaper than a purchase and they are the sort of thing a partner watching the estate every day finds before the alert fires. That is the argument for the arrangement rather than for the project.

Let us show you what's possible.

Two ways to start

Bring the growth curve and the next renewal.