Security Blueprints

The environment described in this architecture consists of one main datacenter containing 10,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. All backups will be targeted to a local Veeam Hardened Repository Appliance and copied to a Veeam Data Cloud (VDC) customer Vault. Proxies are installed on physical servers and use the network transport (NBD) method.

The environment described in this architecture consists of one main datacenter containing virtual machines and physical servers protected with Veeam Data Platform. Multiple object storage backup repositories utilize Azure Blob storage. All backups are configured to go directly into these repositories, and encryption is enabled on all backups.This migration will move all backups from the current object storage repositories into new Veeam Data Cloud Vault repositories. Encryption is enforced, and immutability will be enabled by default for the new Vault repositories, and as a result, migrated backups will be automatically encrypted and immutable. This migration uses temporary Azure components to facilitate the move to avoid egress when the Vault is in the same region.  

The environment described in this architecture consists of one primary datacenter containing 5,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. All backups will be targeted to a local Veeam Hardened Repository Appliance and copied to a Veeam Data Cloud (VDC) customer Vault. The Proxy servers use the Network (NBD) backup method.#blueprint, #veeam, #reference architecture 

The environment described in this architecture consists of one main datacenter containing 1,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. All backups will be targeted to a local Veeam Hardened Repository Appliance and copied to a Veeam Data Cloud (VDC) customer Vault. Proxies are installed on VMs and use the virtual appliance (hot add) backup method. #veeam #Blueprint  #reference architecture #VDC Vault

The environment described in this architecture is one Microsoft 365 tenant with 50,000 active users.  The tenant contains Exchange Online mailboxes, archive mailboxes, OneDrive, SharePoint Online, and Teams data. The total amount of data being consumed by M365 is approximately 850TB. 

The 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 Veeam Data Cloud (VDC) Vault. Proxies are installed on physical servers and Virtual Appliance (hot add) backup method. Veeam Recovery Orchestrator (VRO) is installed in Azure and will be used to perform mass recoveries from VDC Vault to Azure. blueprint #veeam #reference architecture #VRO

The environment described in this architecture is a Veeam Backup for AWS deployment with less than 1,000 workloads to protect.  The protection scope includes EC2, RDS, EFS, and VPCs.  All EC2 backups will be targeted to an object storage repository in AWS S3 and tiered to S3 Glacier storage using a copy job. 

The environment described in this architecture is a Veeam Backup for AWS deployment with 1,000 – 5,000 workloads to protect.  The protection scope includes EC2, RDS, EFS, and VPCs.  All EC2 backups will be targeted to an object storage repository in AWS S3 and tiered to S3 Glacier storage.

The environment described in this architecture is a Veeam Backup for Azure deployment with 300 - 2000 workloads to protect. The protection scope includes Azure VMs, Azure SQL, and Azure Files. All Azure VM backups will be targeted to Azure Blob and tiered into the Archive tier for long-term retention.

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

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 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 Object Storage, which is set for Immutability and accessed via Gateway servers.

The 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 VMs and use the virtual appliance (hotadd) backup method. The primary Veeam Hardened repository will be on Dell PowerEdge R760xd2 server and the secondary repository will be on Data Domain 9300.

The 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 primary Veeam Hardened repository will be on Dell PowerEdge R760xd2 server and the secondary repository will be on Data Domain 6800.

The environment described in this architecture is one datacenter containing 1,000 VMs and 100 servers. Each VM and server has an average of 100 GB of used storage space. All backups will be targeted to a local primary backup repository and copied to a secondary offsite location. Flowmon provides full network layer visibility of potential attacks so customers can leverage early detection and warnings to trigger data protection workflows in Veeam® Backup & Replication™ using the Veeam Incident API. 

The environment described in this architecture is one main datacenter with 500 Nutanix AHV VMs with 100TB of source data. All local backups will be targeted to Hardened Repositories grouped in a Scale-out Backup Repository. Offsite backups will also target Veeam Hardened Repositories. VMs will require 2vCPUs, 4GB of RAM, and 200GB of disk space.

The 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 Veeam hardened repository will be on Dell PowerEdge R760xd2 servers.

The 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 VMs and use the virtual appliance (hotadd) backup method. The Veeam Hardened repository will be on Dell PowerEdge R760xd2 servers.

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

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

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

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.

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.

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.

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.

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.