workload and capacity assessment;
workload and capacity assessment;
VMWARE + ADD SOLUTION
VMware with architecture, licensing and operations managed as one platform.
Sustainable virtualisation requires more than hosts and VMs. Add Solution connects requirements, versions, capacity, storage, networking, protection, automation and evolution paths.
vSphere, VCF, vSAN, NSX and operations assessed against the environment and contracted entitlements.
VMWARE + ADD SOLUTION
Workloads before clusters
VM count alone does not define the architecture. CPU, memory, NUMA, latency, I/O, networking, peaks, application licences, affinity and dependencies guide cluster design and capacity. Reserves for maintenance and failure are explicitly addressed. Oversubscription is a controlled decision, monitored through telemetry and growth capacity. Version, hardware, firmware, driver and component compatibility is checked against current matrices. The cluster must remain operable precisely when some of its capacity is unavailable.
VMWARE + ADD SOLUTION
vSphere and vCenter — the management plane is critical too
ESXi runs workloads; vCenter centralises inventory, clusters, permissions and operations. Its availability, file-based backup, certificates, DNS, time settings and identity need their own runbook. vSphere HA can restart VMs on remaining hosts after a failure, subject to clustering, admission control, storage, networking and capacity. It does not automatically make the application resilient. DRS balances resources according to configuration; vMotion depends on appropriate compatibility and connectivity.
VMWARE + ADD SOLUTION
VMware Cloud Foundation — integration with prerequisites
VMware Cloud Foundation integrates compute, storage, networking and management components in an architecture with coordinated lifecycle management. Applicability depends on the contracted edition, bill of materials, supported hardware, topology and operational skills. The management domain and workload domains have distinct roles. SDDC Manager coordinates supported processes but does not eliminate the need for capacity planning, maintenance windows, backup or integration with external tools.
VMWARE + ADD SOLUTION
Storage — where VM policy meets physical capacity
VMware can run with supported external storage or vSAN. The decision considers latency, throughput, availability, operations, scalability, licences and recovery. In vSAN, storage policies define requirements for each VM. Failures to tolerate, RAID, fault domains, deduplication/compression where applicable, slack space and resynchronisation affect usable capacity and behaviour during a failure. Raw capacity must not be presented as usable capacity. The vSAN network, controllers, devices and firmware must comply with the architecture and compatibility requirements. Rebuilds and rebalancing are included in sizing.
VMWARE + ADD SOLUTION
Networking and NSX — segmentation depends on known traffic flows
vSphere Distributed Switches organise connectivity, uplinks and policies. VLANs, MTU, LACP, NIC teaming and traffic separation are aligned with the physical fabric. NSX can provide overlay segments, gateways, a distributed firewall and network services depending on the edition and architecture. Microsegmentation starts with inventory and traffic flows; rules without lifecycle management accumulate exceptions and risk. Underlay, overlay, edge nodes, routing, DNS and observability must be addressed together.
VMWARE + ADD SOLUTION
Availability and disaster recovery
HA, Fault Tolerance, replication, stretched clusters and DR orchestration address different events and have their own prerequisites. Not every workload supports the same mechanism. The design defines RPO, RTO, consistency, dependencies, destination capacity, addressing, DNS, licences and recovery order. Failover and failback have tests and decision criteria. Active replication alone does not demonstrate DR capability.
- FALHA
Definir eventos, dependências e impacto aceito.
- PROTEÇÃO
Combinar HA, backup, replicação e isolamento conforme o risco.
- RECUPERAÇÃO
Ordenar compute, storage, rede, identidade e aplicações.
- TESTE
Medir RPO, RTO, consistência, failover e retorno.
VMWARE + ADD SOLUTION
Backup — a snapshot is not a protection policy
VMware snapshots are temporary operational mechanisms and can affect storage and performance if retained improperly. They do not replace independent backups. Backup solutions must use supported integrations and APIs and address application consistency, change tracking, proxies, networking, repositories, retention, external copies and restore tests. vCenter, management appliances and network configurations also need a protection strategy.
VMWARE + ADD SOLUTION
Lifecycle — upgrading the stack requires the right sequence and compatibility
Upgrades consider vCenter, ESXi, firmware, drivers, add-ons, vSAN, NSX, backup, monitoring and integrations. Release notes, interoperability and hardware compatibility are checked before the change. The plan includes backup, health checks, capacity to evacuate hosts, sequencing, a maintenance window, acceptance criteria and rollback. Non-standard hosts and third-party extensions are inventoried before the upgrade.
VMWARE + ADD SOLUTION
Observability and operations
Operations monitor capacity, contention, latency, queues, physical errors, cluster status, alarms, certificates, jobs, snapshots, datastores and backups. Alerts have a responsible owner and a runbook. ESXi, vCenter, vSAN and NSX logs are retained according to operational needs. Privileged accounts, SSO, directory integration and support access are reviewed. Automated changes must be repeatable and auditable.
VMWARE + ADD SOLUTION
Migration and consolidation
Migrations between clusters, versions, storage systems or platforms begin with an inventory of VMs, networks, disks, snapshots, tools, operating systems, applications and licences. HCX or specialised tools can help in supported scenarios, but the method depends on the source, destination, connectivity and maintenance window. Pilots validate performance, consistency, rollback and operations. Incompatible workloads receive individual treatment; no tool guarantees universally seamless migration.
- INVENTARIAR
VMs, dependências, versões, hardware, storage, rede e licenças.
- CLASSIFICAR
Criticidade, compatibilidade, capacidade e estratégia por workload.
- PREPARAR
Destino, proteção, observabilidade, plano de mudança e rollback.
- PILOTAR
Onda representativa com métricas e critérios de aceite.
- MIGRAR
Ondas controladas, validação do owner e estabilização.
- ENCERRAR
Descomissionamento, documentação, capacidade e licenças revisados.
VMWARE + ADD SOLUTION
Licensing and support
The VMware portfolio and commercial metrics have changed. This page does not specify bundle names, entitlements or metrics without validating the customer’s current Broadcom/VMware proposal. Available features depend on the edition, version and contract. Add Solution support covers the scope agreed with the customer. Manufacturer support is separate and follows current entitlements and terms. Operations define when and how each support process is initiated.
PERGUNTAS FREQUENTES
FAQ
Answers to VMware platform, licensing, migration and operational decisions.
Does VMware HA make an application highly available?
Not automatically. HA restarts VMs where possible. The application must handle state, dependencies and recovery, and the cluster must have capacity, networking and storage available.
Does vMotion work between any hosts?
No. CPU compatibility, versions, networking, storage, configuration and the features used by the VM must be checked.
Does vSAN eliminate the need for storage design?
No. It makes distributed storage part of the cluster, increasing the importance of networking, devices, policies, usable capacity, failure domains and recovery.
Is NSX required for microsegmentation?
It depends on the architecture and the desired control. When used, policies must be based on traffic flows and ownership; the product does not create a correct policy on its own.
Snapshot substitui backup?
No. A snapshot depends on the same environment and is intended for temporary use. Backup requires retention, independence and tested restores.
Is upgrading ESXi first enough?
No. The sequence depends on the stack and interoperability matrices, including vCenter, drivers, firmware, vSAN, NSX, backup and integrations.
Can VMware coexist with another hypervisor?
Yes, but this creates separate operational domains, skills, backup, networking and automation requirements. The decision must be based on each workload and total operating cost.
VMWARE + ADD SOLUTION
Engenharia Add Solution
cluster and vCenter architecture;
cluster and vCenter architecture;
vSAN or external storage;
vSAN or external storage;
virtual networking, fabric and NSX;
virtual networking, fabric and NSX;
lifecycle management and upgrades;
lifecycle management and upgrades;
backup, DR and testing;
backup, DR and testing;
observability and hardening;
observability and hardening;
migration and consolidation;
migration and consolidation;
documentation, runbooks and ongoing operational support.
documentation, runbooks and ongoing operational support.
SOLUÇÕES RELACIONADAS
Tecnologia conectada à operação.
ADD SOLUTION + VMWARE
Evolve VMware through verifiable platform and operational decisions.
Assess architecture, licences, compatibility, capacity, continuity and alternatives before the next change.