Freight carrier · Disaster Recovery

Environment corrupted, dispatch halted, operations back the same day

When a carrier's main environment was corrupted and froze all dispatch, PWS Cloud's disaster recovery was triggered and the operation was back the same day, from a clean recovery point.

A 24/7 operation with no real plan B

The Freight carrier ran routing, tracking, and dispatch from a single environment. There was no tested disaster recovery plan, so a serious failure there meant a halted operation and trucks stuck at the dock.

That's exactly what happened when the main environment was corrupted. Systems became inconsistent, dispatch froze, and the team had no reliable point to restore from on their own without dragging the corruption along.

With PWS Cloud's disaster recovery, the team triggered the switch to the replicated environment, from a clean recovery point. Routing and dispatch were back the same day, and the incident didn't turn into a prolonged outage.

Professional in a meeting about a technology project.

Results achieved with the project

1.

Operations back the same day

With DR triggered, operations returned the same day through the replicated environment, from a corruption-free point.

2.

Dispatch back to normal

Routing and tracking came back online and trucks rolled out, without a prolonged outage.

3.

Clean recovery point

The switch happened from a clean copy, without carrying over the corruption from the main environment.

4.

Data loss under 5 minutes

Frequent replication kept RPO below 5 minutes, with almost no information gap.

What made the results possible?

The environment got corrupted and dispatch just stopped. Before, that would've been days of downtime. This time we triggered DR and were back the same day, from a clean point. That was the best proof the investment paid off.

IT Manager

Talk to a specialist!

Get in touch