Skip to main content
  • EN

Veeam Backup & Replication

Reference architecture documents related to common Veeam Backup & Replication scenarios encountered in the field

  • 33 Topics
  • 28 Comments
33 Topics
chas
chasComes here often
posted in Veeam Backup & Replication
Veeam Blueprints

Hi everyone.I run the Solution Architects organization for the Americas here at Veeam, and I am happy to introduce you to our Technical Blueprints. These are produced by our Solution Architects in collaboration with Veeam Product Management, R&D and our alliance partners - it truly takes a village.Our goal was to produce short, easy-to-digest reference documents that offer a prescribed architecture that mirrors situations we have seen in the field. As you can appreciate with a software-defined solution, there are countless variables that impact design and we consciously wanted to avoid "could do..." type documents so we worked to strike a balance between short and useful.The documents are firmly technical (again - prescribed architecture) but should be easily accessible to those with knowledge of Veeam. They are not designed to replace the product documentation (at helpcenter.veeam.com), be a full architecture and design (we have a different process for that, and partners add massi

10294
coolsport00
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Two production datacenters with remote offices, and plant sites with offsite backup copies - 26,000 VMs

The environment described in this architecture is two main datacenters containing 10,000 VMs and 100 physical servers at each location.  An additional 6,000 VMs and 50 physical servers are spread across 30 small office and plant sites across North America. Each VM and physical server has an average of 200 GB of used storage space.All backups will be targeted to a local primary backup repository and copied to a secondary off-site location. The small office and plant sites will send backup copies to Veeam Data Cloud Vault (VDC Vault). Proxies are installed on physical servers and use the network transport (NBD) method. #veeam #blueprints #reference architecture

1300
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Regional datacenter and remote site to VCCE in a central hub site – 10000 VMs

The environment described in this architecture consists of one Regional Datacenter with 10,000 VMs and 100 physical servers, and a ROBO site containing 100 VMs. All backups will be targeted to a local primary backup repository and copied to a secondary off-site location secured with Veeam Cloud Connect for the Enterprise (VCCE). #blueprint #veeam #reference architecture

671
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
CDP Replication for Average Write Rate of 100 MB/s

Updated - V12.1The environment described in this architecture are two datacenters and multiple VMs in a cluster with a total average write rate of 100 MB/s, consuming 30 TB of primary storage. The VMs will be replicated from the primary datacenter to the target cluster in the secondary datacenter through continuous data protection (CDP). The source and target cluster will be managed by a single vCenter. Each datacenter will contain a CDP proxy that is installed on a physical server. The networking speed between components in each datacenter is 10 Gbps. #blueprint #veeam #reference architecture

1051
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
CDP Replication for Average Write Rate of 500 MB/s

Updated - V12.1The environment described in this architecture are two datacenters and multiple VMs in a cluster with a total average write rate of 500 MB/s, consuming 150 TB of primary storage. The VMs will be replicated from the primary datacenter to the target cluster in the secondary datacenter through continuous data protection (CDP). The source and target cluster will be managed by a single vCenter. Each datacenter will contain a CDP proxy that is installed on a physical server. Networking speed between components in each datacenter is 10 Gbps. #veeam #blueprints #reference architecture

691
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
NAS Backup 500TB to a Veeam Hardened Repository

The environment described in this architecture is one main datacenter containing 500 TB of NAS data. The NAS environment contains 5 shares and 200 million files. All backups will be targeted to Hardened Repositories grouped in a Scale Out Backup Repository. The general-purpose proxies and cache repositories will be collocated on the same server hardware.

1521
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
NAS Backup 500TB to immutable Object Storage

The environment described in this architecture is one main datacenter containing 500 TB of NAS data. The NAS environment contains 5 shares and 200 million files. All backups will be targeted to Immutable Object Storage. The general-purpose proxies and gateways will be collocated on the same server hardware.

1272
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
NAS Backup 1PB to Hardened Repository

The environment described in this architecture is one main datacenter containing 1 PB of NAS data. The NAS environment contains 10 shares and 400 million files. All backups will be targeted to Hardened Repositories grouped in a Scale Out Backup Repository. The general-purpose proxies and cache repositories will be collocated on the same server hardware.

851
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
NAS Backup 1PB to Object Storage

The environment described in this architecture is one main datacenter containing 1 PB of NAS data. The NAS environment contains 10 shares and 400 million files. All backups will be targeted to Immutable Object Storage. The general-purpose proxies and gateways will be collocated on the same server hardware.

1121
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
NAS Backup 5PB to Hardened Repository

The environment described in this architecture is one main datacenter containing 5 PB of NAS data. The NAS environment contains 50 shares and 2 billion files. All backups will be targeted to Hardened Repositories grouped in a Scale Out Backup Repository. The general-purpose proxies and cache repositories will be collocated on the same server hardware.

771
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
CDP Replication for Average Write Rate of 1000 MB/s

Updated - V12.1The environment described in this architecture are two datacenters and multiple VMs in a cluster with a total average write rate of 1000 MB/s, consuming 300 TB of primary storage. The VMs will be replicated from the primary datacenter to the target cluster in the secondary datacenter through continuous data protection (CDP). A single vCenter will manage the source and target cluster. Each datacenter will contain a CDP proxy installed on a physical server. Networking speed between components in each datacenter is 10 Gbps.

1343
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Veeam Replication for 500 VMs

This environment consists of 500 VMs that require traditional Veeam replication and CDP replication to an offsite datacenter. The VMs average two disks each, and consume 75TB of source datastore space, averaging 150GB per VM. The VMs requiring CDP have a combined average write rate of 500MB/s.  For critical workloads, a short-term RPO of 15 seconds within a four-hour window and an RPO of eight hours for long-term retention within a 48-hour window. An RPO of 12 hours for residual workloads, which requires replication to occur twice a day, completing within an eight-hour window of starting.  The inter-site link is 10gb/s. This deployment will not share proxy resources with any existing backup tasks.

1501
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
NAS Backup 5PB to Object Storage

The environment described in this architecture is one main datacenter containing 5 PB of NAS data. The NAS environment contains 50 shares and 2 billion files. All backups will be targeted to Immutable Object Storage. The general-purpose proxies and gateways will be collocated on the same server hardware.

962
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Migrate an existing backup platform to Veeam Backup & Replication with new hardware

The environment described in this architecture consists of one primary data center containing a mixture of VMs and physical servers. A third-party backup solution currently protects the environment. Veeam Backup and Replication has been purchased and will replace the existing backup solution. In addition to Veeam Backup and Replication, block-based storage hardware has been purchased to hold the production backup archives and a replica of the backup archives at an off-site location.

1671
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Migrate an existing backup platform to Veeam Backup & Replication with temporary swing space

The environment described in this architecture consists of one primary data center containing a mixture of VMs and physical servers. A third-party backup solution currently protects the environment. Veeam Backup and Replication has been purchased and will replace the existing backup solution.Veeam Backup and Replication will ultimately use all the existing backup storage target. To help with this, a small storage array has been acquired as temporary swing space to host Veeam Backup and Replication backup archives until enough storage space becomes available (i.e., the legacy backups age out of retention) on the existing backup target to host all Veeam Backup archives.

2052
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Veeam Architecture Discovery

The first phase of the VeeamDesign Methodology is the Discovery phase. This phase is devoted to collecting relevant information for later phases. Stakeholders should be consulted to develop a detailed list of objectives and capture environmental data to form requirements.This document contains example technical discovery questions that should be answered before a Veeam Architecture is created.

2861
AndrePulia
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Regional datacenter and remote site to VCCE in a central hub site – 1000 VMs

The environment described in this architecture is one Regional Datacenter with 1000 VMs and 100 physical servers and a ROBO site containing 100 VMs and 10 physical servers. Each VM and physical server has an average of 200 GB of used storage space.  All backups will be targeted to a local primary backup repository and copied to a secondary offsite location secured with Veeam Cloud Connect for the Enterprise (VCCE).

570
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Regional datacenter and remote site to VCCE in a central hub site - 5000 VMs

The environment described in this architecture is one Regional Datacenter with 5000 VMs and 100 physical servers and a ROBO site containing 100 VMs and 10 physical servers. Each VM and physical server has an average of 200 GB of used storage space.  All backups will be targeted to a local primary backup repository and copied to a secondary offsite location secured with Veeam Cloud Connect for the Enterprise (VCCE).

400
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Single production datacenter offload to capacity tier 1,000 VMs

Updated - V12.1The environment described in this architecture builds of the 1000 VMs “Single production datacenter to offsite datacenter” scenario. The local repositories are defined as the Performance Tier of a Scale-out Backup Repository (SOBR). The Capacity Tier is a “public-cloud” Object Store. This reference architecture covers capacity tier copy + move operations. It accounts for the potential concurrency of primary backup and offload operations by detailing additional required resources. Each VM and physical server has an average of 200 GB of used storage space (1000 VMs and 100 servers).

1191
Scott
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Incident Response Plan

The processes described in this architecture utilize the Veeam Data Platform Premium, adding value to existing security countermeasures.An Incident Response Plan (IRP) has been developed to facilitate a quick and systematic response to a cyber-attack or a data security incident. The IRP is part of a broader Disaster Recovery Plan (DRP) and covers the following response steps: preparation, detection and analysis, containment eradication and recovery, and post-incident activity.What is described here is purposefully focused on Veeam and assumes other counter-measures and processes have been implemented, for example, clear lines of communication and assigned responsibilities in the event of a breach.

2971
vAdmin
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Veeam Service Provider Console (VSPC) licensing and reporting for VCSPs

The environment described is that of a Veeam Cloud Service Provider (VCSP) infrastructure providing data protection services for a tenant/customer workload. The VCSP utilizes the Veeam Service Provider Console (VSPC) solution to provide licensing, consumption monitoring, and reporting for the Veeam platform. The tenant is described as running 1 Veeam Backup & Replication server protecting up to 1,000 VMware/Hyper-V VMs and up to 9 Veeam Backup for Public Cloud Appliances protecting up to 270 VMs, for a total up to 1,270 VMs. The tenant also protects up to 10,000 M365 Users and less than 250 Veeam Backup Agents managed by VSPC.

1922
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Regional datacenter and ROBO with 100 VMs copy to main HUB site

Updated - V12.1The environment described in this architecture is three ROBO sites containing 100 VMs and ten physical servers. Each VM and physical server has an average of 200 GB of used storage space.  All backups will be targeted to a local primary backup repository and copied to a secondary offsite location. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method.

1300
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Single production datacenter to offsite datacenter 10,000 VMs – SAN repository

The environment described in this architecture consists of one main data center containing 10,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. The proxy service is installed on physical servers and uses the Network Block Device (NBDSSL) transport method. All backups will be targeted to a local primary backup SAN repository and copied to a secondary offsite location.

460
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
Single production datacenter to offsite datacenter 5,000 VMs – SAN repository

Updated - V12.1The environment described in this architecture consists of one main data center containing 5,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. The proxies are physical servers using the Network Block Device (NBDSSL) mode. All backups will be targeted to a local primary backup SAN repository and copied to a secondary offsite location.

350
vmJoe
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup & Replication
One Datacenter with a DR site 1000 VMs – SAN Repository

The environment described in this architecture is one main datacenter containing 1000 VMS and 100 physical servers.  Each VM and physical server has an average of 200 GB of used storage space.  All backups will be targeted to a local primary backup repository and copied to a secondary offsite location. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method. The backup target will be a server with an attached SAN array.

991
leduardoserrano

Badge winners

Show all badges
Terms & Conditions