Commvault · Infrastructure · YoctoIT tech page

HyperScale X

Commvault's scale-out appliance: nodes adding capacity and power, erasure coding and immutability — backup infrastructure without a design project.

FOCUS · THE RIGHT IRON, READY-MADEFrom 3 nodes up: switch it on, add, grow — backup no longer needs a storage project
YoctoIT material for clients and partners · Commvault and the other products mentioned are trademarks of Commvault Systems, Inc.
01 · What it is

HyperScale X, made clear.

HyperScale X is the reference infrastructure for the Commvault data plane: an appliance (or reference architecture on certified iron) with distributed storage, erasure coding and native immutability. Three nodes to start, grow by adding bricks: no dedicated SAN, no media servers to design, fault resilience included.

3+
nodes to begin: pick the size later, while growing
EC
erasure coding: disk and node failures absorbed
Lock
pool immutability: ransomware stays out
HyperScale X
OFFICIAL BRANDING COMMVAULT
02 · How to use it well

The things that make the difference.

The appliance

Backups from the estateall the workloads in the plan
Node 1
Node 2
Node N
distributed storage · erasure coding · global dedup
HyperScale Xthe pool that grows brick by brick
Copies to cloud/air gapthe 3-2-1 completed
Backup infrastructure, solved

Zero design

No LUNs, no zoning, no re-sizing marathons: the pool is the product.

Rolling upgrades

Nodes update one at a time: backup doesn't stop for firmware.

Failures absorbed

Disks and nodes can drop: erasure coding rebuilds, service continues.

Linear growth

More data? More nodes. Capacity and bandwidth grow together, no steps.

03 · In depth

Scale-out with erasure coding: the architecture

Every node brings CPU, RAM, disks and network; the distributed filesystem writes with configurable erasure coding across nodes: efficiency stays high (no 3x replicas) and tolerance covers disks and whole nodes; global deduplication runs on the pool; immutability blocks deletions and rewrites for the set retention even against a compromised administrator; the same architecture is available as a reference on HPE, Dell and others.

  • Erasure coding — grown-up efficiency: protection without tripling storage
  • Immutable pool — retention lock on the filesystem: no deletes, not even by root
  • Dedup on the pool — global across nodes and workloads: the TBs you never buy
  • Identical nodes — the standard brick: easy spares, trivial upgrades
  • Reference architecture — the same solution on your preferred vendor's iron
  • Single management — the pool run from the platform's own console
04 · Numbers and lifecycle

The numbers that matter.

N+2
typical EC tolerance on larger pools
linear
growth: node added, bandwidth added
0
SAN or external storage required
1 h
typical time to add a node to the pool
Backup infrastructure shouldn't be the year's second storage project: here it's a row of identical bricks.
05 · Use cases

Where it really pays off.

New data plane

Backup rethought: single, scalable pool.

Media server refresh

Out with the fragile legacy: modern appliance.

Distributed sites

Small clusters at the edge, replication to the core.

Let's size the pool on YOUR change rate: real numbers, not price-list ones.