Processing and memory
Cores, frequency, memory, NUMA, accelerators and per-socket or per-core licences must be assessed together.
LENOVO TECHNOLOGY • ADD SOLUTION ENGINEERING
Lenovo for data centres where workloads, capacity and recovery must add up
Compute, storage, management and protection connected by verifiable assumptions.
The architecture considers performance, capacity, compatibility, licences, recovery and lifecycle without assuming particular products or services.
ENGENHARIA ADD SOLUTIONInfraestrutura orientada às cargas
COMPUTAÇÃOSTORAGEPROTEÇÃOGESTÃO
DIAGNÓSTICO · ARQUITETURA · VALIDAÇÃO · CICLO DE VIDALENOVO NO DATA CENTER
Lenovo for workload- and operations-driven data centres
Data centre infrastructure must support applications, data and recovery procedures without treating growth as an exception. ADD Solution builds Lenovo environments around actual workloads, dependencies, available capacity and the expected operating model. Compute, storage, virtualisation, protection, networking and management have different roles. The project records assumptions, limits and acceptance criteria before commercial configuration. The Lenovo identity is used in line with the manufacturer’s public naming conventions; this does not claim any ADD Solution partnership, certification, commercial status or support level.
ENGENHARIA ADD SOLUTION
Peaks, growth and the recovery window determine sizing—not last month’s average
Transactional environments, virtualisation platforms, file repositories and analytical workloads impose different CPU, memory, latency, throughput, capacity and recovery profiles. Discovery classifies criticality, dependencies, peaks, growth and the impact of downtime. Power, cooling, racks, cabling, uplinks, operating systems, hypervisors, agents, contracts and change windows also form part of the design. Sizing based only on average usage can hide period-end processing, batch jobs and seasonal events. Every assumption must be recorded to enable review and technical comparison.
CONFIGURATION AS A SYSTEM
Compute and storage require a complete configuration
ThinkSystem covers compute and storage infrastructure for different workload profiles. Selection should start not with a model, but with processing, memory, data access, expansion, availability and physical requirements. Raw capacity, usable capacity and estimates after efficiency gains must be shown separately. Latency, IOPS and throughput depend on the workload, protocol, concurrency and enabled services; published maximums do not mean all options can coexist.
Data and connectivity
Controllers, interfaces, redundant paths, protocols, queues and boot devices must be compatible with the operating system and hypervisor.
Power and environment
Power supplies, power requirements, cooling, physical footprint, airflow and maintenance determine which configurations are feasible.
ACCOUNTABLE OPERATIONS
Centralised management and hybrid environments need clear responsibilities
XClarity One is Lenovo’s currently published direction for infrastructure management, with options and requirements that vary by deployment, supported devices, connectivity and licences. A console’s existence does not justify indiscriminate updates: firmware, drivers, operating systems and integrations need a compatibility matrix, a window, validation and a planned rollback. Environments using earlier tools should treat the transition as a project, preserving inventory, alerts, credentials, history and operational capability. Publication of a migration roadmap does not guarantee feature parity in every scenario.
TruScale offers infrastructure as a service and flexible models for hybrid environments. Purchasing, subscriptions, consumption and managed services are not equivalent. The proposal must identify assets, metering, commitments, software, telemetry, support, data location and each party’s responsibilities.
VERIFIABLE CONTINUITY
High availability, replication and backup address different risks
The data strategy must distinguish platform availability, snapshots, replication, backup and disaster recovery. Independent copies, retention, isolation and immutability, where supported and configured, are different controls; no single feature proves recoverability. RPO and RTO guide architecture, capacity, connectivity and procedures. Feasibility must be demonstrated by restoring applications and dependencies, not merely by a successful copy job.
Reference architectures help organise components and assumptions, but do not automatically validate versions, licences, sizing or results in another environment. The actual combination must be checked against the selected bill of materials and software.
DELIVERY METHOD
Evidence-based deployment and lifecycle management
Changes to firmware, operating systems, hypervisors, drivers, agents or management tools can affect other layers. A package’s availability does not establish its suitability. Project closure records the deployed configuration, outstanding issues, tests, responsible owners and review cycle.
- Discover
Inventory workloads, dependencies, capacity, versions, contracts and physical constraints.
- Size
Turn measurements, peaks and growth into resources, redundancy and documented headroom.
- Validate
Check compatibility, licences, power, cooling, networking, support and recovery.
- Deploy
Run a pilot and phased changes with backup, observability and rollback criteria.
- Operate
Deliver documentation, alerts and procedures for updates, restores and capacity reviews.
PREMISSAS DA PROPOSTA
Technical and commercial limits must be visible
Licensing depends on the function
Management, virtualisation, protection and services may use different metrics and contracts; the current quotation takes precedence.
Compatibility applies to the combination
Hardware, firmware, drivers, operating system, hypervisor, adapters and applications must be validated together.
Effective capacity is an estimate
Data reduction, compression, encryption and workload profile affect the observed result.
Hybrid environments do not remove responsibilities
Operations, security, connectivity, data, support and recovery still need defined owners.
Regional availability must be confirmed
A global page does not establish stock, licensing, service, lead times or coverage in Brazil.
PERGUNTAS FREQUENTES
Decisions that change architecture, cost and risk
Does this page present available Lenovo products or SKUs?
No. It organises architecture criteria. Models, options, licences, services and regional availability depend on the validated technical and commercial configuration.
How should compute sizing begin?
Gather CPU and memory usage and peaks, applications, virtual machines, dependencies, growth, licensing, networking, storage and reserves for maintenance or failure.
Does more capacity solve every performance problem?
No. Queues can arise in CPU, memory, networking, storage, applications, databases or integrations. Diagnosis should locate the bottleneck before resources are expanded.
Does all Lenovo hardware support any hypervisor?
No. Support depends on the platform, version, components, firmware and drivers. The combination must be checked in the current interoperability guide.
Does XClarity One update any device automatically?
No. Supported devices, versions, licences, connectivity, credentials, catalogues and sequencing must be confirmed for the managed environment.
Does TruScale mean everything runs in the public cloud?
No. It is an infrastructure and services offering with options for hybrid environments. Location, metering, responsibilities and commitments depend on the contract.
Replicação substitui backup?
No. Replication can propagate unwanted changes; backup also provides retention and earlier versions. The design combines controls and tests restores.
Is Lenovo support equivalent to ADD Solution’s SLA?
No. Warranty, manufacturer support, ADD services and application recovery are distinct scopes. Coverage, hours, channels and commitments must be stated in the proposal.
SOLUÇÕES RELACIONADAS
Data center e infraestrutura conectados à operação.
ADD SOLUTION + LENOVO
Turn inventory and metrics into architecture criteria
Share priority workloads, current capacity, growth and constraints. The assessment organises dependencies and verifiable decisions.