Latency that a vendor's own tool cannot explain
The array's own dashboard is green while the application it serves is visibly slow.
Enterprise infrastructure consulting
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.
On this page
Jump to the part that matches the problem or decision in front of you.
This service is usually bought in one of three situations.
The array's own dashboard is green while the application it serves is visibly slow.
You need the compatibility, cutover and rollback plan checked by someone who has done this before.
You need to know what happens — to performance and to recovery — when a path, host or array fails.

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.
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.
Design, change and day-to-day operation, including ActiveCluster active/active, where two sites serve the same data and either can carry the load.
Operation and support of NetApp ONTAP environments.
Operation of Dell EMC storage and VxRail hyperconverged infrastructure.
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.
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.
A written assessment your team, and your board, can act on.
Where requests wait, not just which counter is highest.
Compatibility, cutover order, validation checks and a defined way back.
Failure domains and recovery order stated plainly enough for a non-technical board to follow.
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.
Plan compatibility before data movement changes the operating path.
Sequence data movement with protection and recovery in view.
Agree cutover checks and validate the new environment.
Retain rollback, then hand over configuration, monitoring changes and remaining actions.
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.
Send the platforms involved and the problem you are trying to solve.
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.
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.
Kritical can help define a requirement and investigate sourcing routes, but product availability, authorisation, pricing and delivery terms are confirmed for each quotation.
Yes. The scope should include the affected workloads, timing, topology and available evidence across hosts, paths and storage platforms.
Yes. We establish compatibility, data movement, outage constraints, validation, rollback, protection and the teams or vendors required for delivery.
“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.
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.
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.
Tell us what you want to achieve, what you have today and when it matters.