Skip to content
Endpoint security renewing? Compare Falcon Complete
Menu

Enterprise infrastructure consulting

Make storage decisions around the workload.

Kritical helps organisations assess enterprise storage performance, architecture and change across hosts, fabrics, virtualisation, arrays, data protection and the applications that depend on them — so a migration or upgrade improves the thing that matters to the business.

Storage workload performance evidence

Start with the workload, not an isolated array metric.

Latency and throughput must be interpreted against the application operation, I/O shape, concurrency, cache behaviour and the complete host-to-storage path. We can assess where requests wait and whether the constraint is in the host, virtualisation layer, network or fabric, storage platform, replication path or workload design.

  • Performance investigation Correlate application timing with host, path and platform evidence.
  • Capacity and growth Separate usable capacity, performance headroom, protection overhead and forecast assumptions.
  • Architecture and resilience Review failure domains, multipathing, replication and recovery dependencies in context.
  • Migration and lifecycle Plan data movement, coexistence, validation, rollback and operational handover.

Platforms we work with, and what we have run.

We work across the main enterprise storage platforms, so the advice you get is about your environment and not one vendor's catalogue. It comes from people who have run these systems for critical operations, not only designed them.

Pure Storage, including ActiveCluster

Design, change and day-to-day operation, including ActiveCluster active/active, where two sites serve the same data and either can carry the load.

NetApp ONTAP

Operation and support of NetApp ONTAP environments.

Dell EMC and VxRail

Operation of Dell EMC storage and VxRail hyperconverged infrastructure.

Five-nines active/active, run for real

We have run five-nines active/active storage for critical operations: 13 years across active/active data centres. If you are weighing up a design like that, we can show you what it takes to keep it that way.

Connect architecture to failure and recovery behaviour.

Resilience depends on hosts, paths, services and operating procedures working together. We map failure domains, recovery order and the scenarios your organisation needs to handle, then show where backup, replication and high availability each fit — and where they overlap and quietly duplicate cost. A design that looks resilient on a diagram can still fail together if two paths share the same switch, the same power circuit or the same administrator's mistake, so we test the design against realistic failure combinations.

What you get from an engagement.

A written assessment your team, and your board, can act on.

A workload-aware performance finding

Where requests wait, not just which counter is highest.

A migration or change plan with rollback

Compatibility, cutover order, validation checks and a defined way back.

A resilience map

Failure domains and recovery order stated plainly enough for a non-technical board to follow.

Control migration without losing the operating picture.

Storage change can affect performance, data protection and recovery. We plan compatibility, data movement, cutover, validation and rollback, then leave your team with the configuration, monitoring changes and remaining actions needed to operate the new environment.

Enterprise storage array close-up

Compatibility

Plan compatibility before data movement changes the operating path.

Data movement

Sequence data movement with protection and recovery in view.

Cutover & validation

Agree cutover checks and validate the new environment.

Rollback & handover

Retain rollback, then hand over configuration, monitoring changes and remaining actions.

How the work is priced.

An assessment is scoped and fixed-price once we know the platforms, workloads and access involved. Migration and remediation work is quoted separately, once the assessment has established what needs to change.

What happens once we understand the workload.

The first call establishes the platforms, the workload and the question you need answered, and ends with a scoped, fixed-price plan before any assessment starts. Subject to the agreed scope and available evidence, an initial phase can move from evidence gathering to a workload-aware finding and, where needed, a migration or change plan with rollback.

Make the storage decision with performance and security in view.

Storage evidence must be read alongside workload ownership, access paths and recovery responsibilities. Set those boundaries first, then follow the specialist path that matches the measured risk.

Questions before you enquire

Do you sell storage hardware?

Kritical can help define a requirement and investigate sourcing routes, but product availability, authorisation, pricing and delivery terms are confirmed for each quotation.

Can you assess an existing storage performance problem?

Yes. The scope should include the affected workloads, timing, topology and available evidence across hosts, paths and storage platforms.

Can you plan a storage migration?

Yes. We establish compatibility, data movement, outage constraints, validation, rollback, protection and the teams or vendors required for delivery.

The array vendor says performance is within spec. Now what?

“Within spec” and “fast enough for this workload” are different claims. We test the second one, using the actual application transaction rather than a synthetic benchmark.

Can you review a design before we buy anything?

Yes. A pre-purchase design review is one of the more cost-effective ways to use this service — checking failure domains, sizing assumptions and recovery behaviour before money is committed, not after.

What evidence do you need from our current environment?

Topology, host and path configuration, representative I/O evidence and whoever owns the array, the fabric and the affected application. We will tell you exactly what is missing once we see what is available.

Let’s define the next step.

Tell us what you want to achieve, what you have today and when it matters.

Discuss your storage environment