VMware vSphere e Microsoft Hyper-V
VMware vSphere and Microsoft Hyper-V: image-based protection and recovery of VMs or supported items, accounting for APIs, snapshots, CBT/RCT, proxies and the window.
VEEAM + ADD SOLUTION
Backup is only complete when recovery is predictable.
Connect workloads, copies, isolation, retention, tests and owners in a Veeam architecture that can be operated during real incidents.
Protection, isolation, capacity and rehearsed recovery as a single system.
VEEAM + ADD SOLUTION
Strategy — design starts with the events recovery must address
Hardware failure, deletion, corruption, site unavailability and credential compromise are not the same incident. Each scenario requires its own recovery point, destination, restoration authority and procedure. Add Solution classifies workloads, dependencies and data; defines RPO, RTO, retention and recovery order; and then selects Veeam components. The 3-2-1-1-0 rule can guide the design—multiple copies, distinct media or domains, an off-site copy, an offline or immutable copy, and verification—but does not replace risk analysis or guarantee recovery by itself.
- REQUISITOS
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
- ARQUITETURA
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
- PROTEÇÃO
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
- VALIDAÇÃO
Testar consistência, restore, capacidade do destino e aceite do owner.
- OPERAÇÃO
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
VEEAM + ADD SOLUTION
Platform — different functions need explicit resources and limits
Veeam Backup & Replication coordinates protection and recovery of supported workloads. Backup servers maintain configuration and the operational catalog; proxies move and process data; repositories store backups; gateways mediate access to certain destinations. The exact separation varies by platform, scale and transport. Veeam Data Platform combines editions and components such as Backup & Replication, Veeam ONE and, in compatible offerings, Recovery Orchestrator. Composition, enabled features and licensing must be confirmed in the contracted edition. Monitoring or orchestration does not automatically make an environment recoverable: capacity, credentials, dependencies and testing remain necessary.
VEEAM + ADD SOLUTION
Workloads — broad coverage does not mean a single policy
The compatibility matrix, versions and limitations must be validated before sizing or migration.
Physical servers
Physical servers: agents for supported operating systems where hypervisor-based protection does not apply.
NAS and file shares
NAS and file shares: architecture driven by file volume, change rate, retention and destination; it must not inherit VM policy without assessment.
AWS, Azure and Google Cloud
AWS, Azure and Google Cloud: products and integrations vary by workload, region and deployment model; egress, accounts, snapshots and object storage affect cost and risk.
Applications and databases
Applications and databases: consistency and granular recovery depend on the application, application-aware processing and documented prerequisites.
VEEAM + ADD SOLUTION
Repositories — the destination is part of the security domain
Usable capacity depends on ingestion, retention, full and incremental backups, compression, synthetic operations, copies and operational headroom. Change rates and the backup window must be measured, not inferred solely from provisioned size. Veeam Hardened Repository uses Linux and can provide backup immutability in supported configurations. Protection depends on correct installation, credentials, filesystem, immutability period and procedures; it does not make the entire infrastructure invulnerable. Compatible object storage can use provider immutability mechanisms where supported and configured. Logical deletion, lifecycle, keys and the administrative account remain within the threat model.
VEEAM + ADD SOLUTION
Isolation — a copy is independent only when its controls are too
Repositories, the management plane, identities, keys and networking must be analyzed together. A copy on another device but under the same compromised credentials may not provide the expected isolation. The design separates administrative functions, restricts traffic, protects configuration backups, avoids everyday use of privileged credentials and documents emergency access. Offline, air-gapped and immutable copies are different terms and must only be used when the implementation actually meets the condition.
VEEAM + ADD SOLUTION
Consistency — a snapshot does not automatically equal a recoverable backup
Hypervisor or cloud snapshots can participate in the workflow but generally remain in the same failure domain and have their own lifecycle. Backups must be transferred and retained according to the defined policy. Application-aware processing can coordinate supported applications and enable restoration options, provided permissions, networking, writers and requirements are correct. For high-transaction-volume databases, log, truncation, retention and point-in-time restoration policies must be designed with the application owner.
VEEAM + ADD SOLUTION
Recovery — restoring data and restoring a service are different outcomes
Veeam provides workflows such as restoration of files, volumes, supported application items, VMs and Instant Recovery options. Actual time depends on size, backup chain, repository, networking, available compute, application validation and operations during the incident. Instant Recovery can reduce the time to make a supported workload available from backup but usually requires subsequent migration or finalization. The runbook defines who authorizes recovery, where to start, how to avoid network conflicts, how to validate the service and how to return to a permanent state.
- REQUISITOS
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
- ARQUITETURA
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
- PROTEÇÃO
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
- VALIDAÇÃO
Testar consistência, restore, capacidade do destino e aceite do owner.
- OPERAÇÃO
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
VEEAM + ADD SOLUTION
Microsoft 365 — shared responsibility requires a separate policy
Veeam Backup for Microsoft 365 is a specific product for supported Microsoft 365 data. It must not be assumed to be an automatic feature of a Veeam Backup & Replication deployment. The scope of organizations, users, services, retention, storage, authentication and Microsoft API limits must be validated. Native Microsoft 365 retention and external backup serve different objectives. The project defines loss events, restore authority, residency, costs and tests before choosing a self-managed architecture or a managed service.
VEEAM + ADD SOLUTION
Kubernetes — Kasten requires application-aligned design
Kasten K10 by Veeam protects supported Kubernetes applications through policies and integrations with snapshots and object storage. Portability depends on CSI drivers, storage classes, application resources, consistency and compatibility between clusters. Manifests, volumes, secrets, operators and external services must be included in the assessment. A namespace restore alone does not guarantee that every application dependency will return.
VEEAM + ADD SOLUTION
DR and orchestration — plans must be executable and rehearsed
Replication, backup copying and orchestration serve different objectives. A DR plan includes startup order, DNS, addresses, identity, dependencies, tests, communication, destination capacity and failback. Recovery Orchestrator can support plans, testing and documentation in licensed and supported scenarios. Automation must be validated against environmental changes. Exercises can use isolated networks where the platform and workload allow it; full tests remain necessary for external dependencies.
VEEAM + ADD SOLUTION
Operations — green jobs are not enough
Routine operations track duration, throughput, bottlenecks, retries, chain integrity, the age of the latest point, capacity, immutability, configuration backups and test results. Alerts need an owner, severity and action. Veeam ONE can provide monitoring and reports for supported environments and components according to edition and license. Telemetry does not replace policy review. Changes to hypervisors, storage, networking, credentials, APIs or versions enter change management and trigger renewed restore validation.
VEEAM + ADD SOLUTION
Implantação em ondas
- REQUISITOS
Definir eventos de perda, workloads, dependências, RPO, RTO e retenção.
- ARQUITETURA
Dimensionar plano de gestão, agentes ou proxies, rede, storage e isolamento.
- PROTEÇÃO
Aplicar políticas por criticidade, janela, destino e autoridade administrativa.
- VALIDAÇÃO
Testar consistência, restore, capacidade do destino e aceite do owner.
- OPERAÇÃO
Monitorar recovery points, falhas, capacidade, mudanças e evidências.
VEEAM + ADD SOLUTION
Limites, licenciamento e suporte
Editions, bundles, features and licensing metrics vary by product and contract. Veeam Universal License covers certain workloads and products, but units, portability and exceptions must be confirmed in the current guide and commercial proposal. Microsoft 365, Kasten, cloud appliances and managed services may have their own models. Compute, storage, object storage, API, transfer and cloud costs are not necessarily included in the Veeam licence. Compatibility depends on the versions listed by the manufacturer. Add Solution support and Veeam support have separate contractual scopes and SLAs; this page does not imply any partnership level or SLA.
PERGUNTAS FREQUENTES
FAQ
Answers to Veeam protection, recovery and operational decisions.
Does immutable backup eliminate ransomware?
No. It can make modification or deletion more difficult during the configured period, but identity, endpoints, the management plane, credentials, keys, the network and the recovery procedure also need protection.
Does the 3-2-1-1-0 rule guarantee recovery?
No. It is a design guideline. Compatibility, consistency, capacity, isolation and testing determine whether the service can be recovered.
Does a VM snapshot replace backup?
Generally not. Snapshots normally depend on the source environment and serve different purposes and retention requirements from an independent backup copy.
Does Instant Recovery deliver the advertised RTO?
Results depend on the repository, network, compute resources, size, application and validation. They must be measured using the actual workload and procedure.
Is Microsoft 365 already protected by the main deployment?
Not necessarily. Veeam Backup for Microsoft 365 is a separate offering with its own architecture, scope and licence.
Does Veeam protect every hypervisor or operating system version?
No. Supported versions, editions and features must be checked against the current compatibility matrix.
Does replication replace backup?
No. It can shorten recovery time, but it can also propagate corruption or deletion and normally serves different retention requirements. Both can be part of the strategy.
How often should restores be tested?
Frequency depends on criticality, changes and obligations. Critical workloads need a defined schedule, evidence, success criteria and a responsible owner.
VEEAM + ADD SOLUTION
Engenharia Add Solution
protection and recovery assessment;
protection and recovery assessment;
Veeam architecture and sizing;
Veeam architecture and sizing;
proxies, gateways and repositories;
proxies, gateways and repositories;
hardened repository and supported object storage;
hardened repository and supported object storage;
policies for virtual, physical, NAS and cloud environments;
policies for virtual, physical, NAS and cloud environments;
Microsoft 365 and Kubernetes within their own scopes;
Microsoft 365 and Kubernetes within their own scopes;
monitoring, capacity planning and upgrades;
monitoring, capacity planning and upgrades;
testing, runbooks, DR and ongoing operational support.
testing, runbooks, DR and ongoing operational support.
SOLUÇÕES RELACIONADAS
Backup e resiliência conectados à operação.
ADD SOLUTION + VEEAM
Build protection around the recovery the business needs to demonstrate.
Turn RPO, RTO, retention, isolation and testing into an operable Veeam architecture.