Overview

Role in the system

The core platform on which enterprise applications, databases, analytics workloads and private cloud run. Its power, cooling, network and recovery design set the availability ceiling for everything above it.

Our scope can cover greenfield facilities, capacity expansion, technology refresh, consolidation, migration and brownfield modernisation.

Leaf-spine data-centre fabric and rack elevationLeft: two spine switches fully meshed to four leaf switches, with compute, storage and backup hosts attached and a separate out-of-band management network. Right: a rack elevation showing patch panel, two leaf switches, a management switch, four servers, a storage array and reserved space, with dual power distribution units fed from separate UPS feeds, and cold-aisle air in and hot-aisle air out.Leaf-spine fabricSpine 1Spine 2Every leafreaches everyspineLeaf AComputehostLeaf BComputehostLeaf CStoragearrayLeaf DBackuptargetOut-of-band management networkseparate from production and storage trafficRedundant leaf pairs and dual-homed hosts keep a singleswitch failure or maintenance task from isolating a host.Rack elevation with dual power feedsPatch panelLeaf switch ALeaf switch BOOB management switchBlanking panelServerServerServerServerBlanking panelStorage arrayReserved for expansionPDU APDU BFeed A (UPS A)Feed B (UPS B)Cold aisle: air inHot aisle: air out
  • Data path
  • Power
  • Management path
  • Fault or alert
Fabric and rack design. A leaf-spine fabric with a separate out-of-band management network (left), and a rack elevation with dual power distribution and a defined cold-aisle and hot-aisle airflow (right).

Capability areas

Six infrastructure layers are designed together, because compute sizing, storage performance, network throughput and recovery objectives constrain one another.

Compute infrastructure

Server platforms are matched to the workload — database, application, virtualisation host or accelerated compute — rather than standardised on one form factor.

  • Rack and tower servers
  • Blade and modular compute
  • High-density compute
  • Virtualisation hosts
  • Database servers
  • Application servers
  • Graphics processing infrastructure
  • Edge-to-core compute integration
  • Clustered compute environments

Storage infrastructure

Storage tiers are chosen by access pattern, latency target and retention period, with replication and expansion paths defined up front.

  • Block storage
  • File storage
  • Object storage
  • High-performance storage
  • Archival storage
  • Software-defined storage
  • Storage-area networks
  • Storage replication
  • Tiered storage
  • Storage expansion

Virtualisation

Cluster design determines how much capacity must be held in reserve so that a host failure restarts workloads rather than exhausting the cluster.

  • Server virtualisation
  • Resource pools
  • High availability
  • Live migration
  • Virtual network design
  • Virtual storage integration
  • Resource reservations
  • Cluster design
  • Host failure recovery
  • Virtual machine lifecycle management

Backup and recovery

Backup is designed from recovery objectives backwards: what must be restored, in what order, how fast, and to which point in time.

  • Backup architecture
  • Backup scheduling
  • Retention design
  • Disk-based backup
  • Tape-based archival
  • Immutable backup
  • Off-site replication
  • Application-consistent backup
  • Database recovery
  • Disaster recovery integration
  • Recovery testing

Data-centre networking

Fabric, management and storage networks are separated so that a fault or maintenance activity on one does not take down the others.

  • Core and aggregation networks
  • Access-layer networks
  • Leaf-spine architecture
  • Management networks
  • Storage networking
  • Out-of-band management
  • Load balancing
  • Network segmentation
  • Redundant connectivity
  • Traffic engineering

Physical infrastructure integration

Rack layout, power distribution and cooling are planned alongside the equipment list, so that density and airflow are verified before delivery rather than discovered at installation.

  • Rack planning
  • Power distribution
  • Cooling coordination
  • Cabling
  • Patch management
  • Equipment layout
  • Rack elevation planning
  • Power-load assessment
  • Environmental monitoring
  • Access-control integration

Engineering considerations

Design inputs

These sixteen inputs are gathered before sizing begins; an unanswered input is recorded as an assumption and carried into the design review.

The data-centre design process should address:

  • Current and projected workloads
  • Processor and memory requirements
  • Storage capacity and growth
  • Input-output performance
  • Network throughput
  • Application dependencies
  • Recovery objectives
  • Availability requirements
  • Power density
  • Cooling capacity
  • Rack space
  • Cable pathways
  • Redundancy
  • Monitoring
  • Maintainability
  • Expansion

High availability

High availability should be engineered across multiple layers:

  • Power
  • Compute
  • Storage
  • Network
  • Virtualisation
  • Databases
  • Applications
  • Backup
  • Management systems

The architecture must identify single points of failure and determine whether each one should be removed, tolerated or operationally managed.

Capacity planning

Capacity planning should consider:

  • Average load
  • Peak load
  • Seasonal load
  • Growth rate
  • Failover load
  • Maintenance conditions
  • Recovery conditions
  • Storage retention
  • Log growth
  • Backup windows
  • Replication traffic

Sizing should not be based only on current consumption.

It should account for expected growth and degraded operating modes.

Brownfield modernisation

Existing data centres often contain:

  • Mixed hardware generations
  • Multiple management systems
  • Unsupported software
  • Underutilised capacity
  • Inconsistent configurations
  • Limited documentation
  • Unclear dependencies

A brownfield modernisation programme should begin with discovery and dependency mapping before migration or replacement decisions are made.

Discuss an ICT Requirement

Describe the requirement, the locations involved and where the project stands. We will respond with the technical questions that need answering first.

Discuss an ICT Requirement