How should N+1 be defined in liquid cooling?

Support / Technical answers

How should N+1 be defined in liquid cooling?

Direct, data-backed answers to the questions that matter before and during deployment.

Redundancy and fault domains define availability: N+1 pumps keep the rack running through a single failure (flow/pressure recovery ≤30 s per industry practice), and branch-level isolation lets one node be serviced without stopping the rack. Design makes explicit what fails, what is affected and how recovery works.

01

How much redundancy

N+1 pumps for critical loops (auto-switchover), N+N for high availability; power likewise N+1. Switchover recovery targets ≤30 s for flow/pressure.

02

How to draw fault domains

By loop: a CDU failure affects the racks it serves; branch quick connects isolate single nodes. The principle is smallest impact, shortest recovery.

03

What to watch

Redundancy is not maintenance-free: run switchover drills, alarm verification and recovery tests; write the power-recovery sequence into the service manual.