• EN

Veeam Backup and Replication

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

  • 33 Topics
  • 11 Comments

33 Topics

chas
chasComes here often
posted in Veeam Backup and 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

4
coolsport00
1 month ago
olivier.rossi
olivier.rossiVeeam MVP
posted in Veeam Backup and Replication

Single production data center to an offsite datacenter with ObjectFirst repositories 1,000 VMs

Updated 12.1The environment described in this architecture is one main datacenter containing 1,000 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 primary backup repository and copied to a secondary offsite location. Proxies are installed on a physical server and use the network transport (NBD) method. The backup target will be ObjectFirst Ootbi set for Immutability and accessed via Gateway servers.

2
leduardoserrano
26 days ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

0
vmJoe
30 days ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

0
vmJoe
30 days ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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. Networking speed between components in each datacenter is 10 Gbps.

0
vmJoe
30 days ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter 10,000 VMs Cisco UCS S3260 repository

Updated - V12.1The environment described in this architecture is one main datacenter containing 10,000 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 physical servers and will use the secure network (NBDSSL) backup mode. The repositories are on Cisco UCS 23260 Storage Servers.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter 5,000 VMs Cisco UCS S3260 repository

Updated - V12.1The environment described in this architecture is one main datacenter containing 5,000 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 physical servers and will use the secure network (NBDSSL) backup mode. The repositories are on Cisco UCS 23260 Storage Servers.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter 1,000 VMs Cisco UCS S3260 repository

Updated - V12.1The environment described in this architecture is one main datacenter containing 1,000 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 repositories are on Cisco UCS 23260 Storage Servers.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Regional datacenter and remote site to VCCE in a central hub site – 10000 VMs

The environment described in this architecture is one Regional Datacenter with 10000 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).

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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).

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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).

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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).

1
Scott
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter 5,000 VMs with an Exagrid repository

Updated - V12.1The environment described in this architecture is one main data center containing 5,000 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 physical servers and use the secure network transport (NBDSSL) method.  The backup repository is an ExaGrid appliance.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter 5,000 VMs – Pure FlashArray//C repository

The environment described in this architecture is one main data center containing 5,000 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 a physical server and use the network transport (NBDSSL) method. The backup target will be servers attached to a Pure FlashArray//C.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

1
vAdmin
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter with HPE Apollo 4510 10,000 VMs

The environment described in this architecture is one main data center containing 10,000 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 Veeam Hardened repository will be on HPE Apollo 4510 servers.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter with HPE Apollo 4510 5,000 VMs

Updated - V12.1The environment described in this architecture is one main data center containing 5,000 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 Veeam Hardened repository will be on HPE Apollo 4510 servers.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter with HPE Apollo 4510 1,000 VMs

Updated - V12.1The environment described in this architecture is one main data center containing 1,000 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 Veeam harden repository will be on HPE Apollo 4510 servers.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

2
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Regional datacenter and ROBO with 100 VMs copy to 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.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Single production datacenter to offsite datacenter with Hitachi Vantara VSP E590 5,000 VMS

The environment described in this architecture is one main data center containing 5,000 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 a physical server and use the network transport (NBD) method. The backup target will be servers with a Hitachi Vantara VSP SAN Attached array.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

0
vmJoe
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and 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.

1
leduardoserrano
1 month ago
vmJoe
vmJoeVeeam MVP
posted in Veeam Backup and Replication

Data spillage backup archive remediation

The processes described in this architecture utilize the Veeam Data Platform Premium and its backup scan capability using Yara rules to find classified data stored in an unclassified backup archive system. The ”Scan Backup” feature uses a customized Yara rule to find files in a backup archive and mark the affected archive as infected. These marked backup archives can then be sanitized. Remediation would align with the agency policy and may include sanitization, relocation of media, or reclassification.

0
vmJoe
1 month ago

Badge winners

Show all badges
Terms & Conditions