Case study
Search Infrastructure Moved in Three Hours for a Canadian Energy Producer
How SquareShift moved a Canadian oil and gas producer's 465-index, 1.3-terabyte Elasticsearch cluster to Elastic Cloud, completing the live cutover in under three hours.
Book a session →
Client
One of Canada's largest oil and natural gas producers, running mission-critical, real-time ingestion pipelines that needed a more scalable Elasticsearch infrastructure.
Industry
Energy
Services
Stack
Elasticsearch · Elastic Cloud · Microsoft Azure · Index Lifecycle Management (ILM) · Snapshot Lifecycle Management (SLM)
How SquareShift delivered it.
The challenge
The client runs mission-critical, real-time ingestion pipelines that could not be interrupted. Its on-prem cluster carried 465 indices and 1.3 terabytes of data that had to move to Elastic Cloud without losing anything. The client's Azure footprint was also fragmented across multiple subscriptions.
What we delivered
Early attempts to back up the data failed security checks, so SquareShift tested and fixed the snapshot process on a separate, non-production cluster first. The team also merged the client's fragmented Azure billing into one subscription.
The outcome
The live move then finished in under three hours, carrying over all 465 indices, 1.3 terabytes of data, and every access rule and policy. Planning a similar move? See our Elastic migration services.
A failed snapshot on a production cluster is not a rehearsal you get to run twice — proving the backup process on a throwaway cluster first is what makes a three-hour cutover possible instead of a three-day incident.
Platform & Software Engineering Practice Lead, SquareShift
