Security Blueprints

V13 Software Appliance. 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. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeted to a local Veeam Hardened Repository and copied to a Veeam Data Cloud VAULT.  The Veeam Infrastructure Appliance hosting the proxies are installed on physical HPE DL380 servers (or similar) and will use the Network Block Device (NBD) backup method. The Veeam Hardened repository will be on HPE Alletra 4140 servers.

V13 Veeam Software ApplianceThe 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. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeted to a local Veeam Hardened Repository and copied to a Veeam Data Cloud VAULT. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method. The Veeam hardened repository will be on HPE Alletra 4120 servers.

V13 Software Appliance.The environment described in this architecture consists of three (3) 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 Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeted to a local Veeam Hardened Repository and copied to a secondary offsite location. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method.

V13 - Veeam Software Appliance. 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. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. 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 network transport (NBD) method.

V13 - Veeam Software Appliance. 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. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeted to a local Veeam Hardened Repository and copied to a Veeam Hardened Repository hosted offsite. The Veeam Infrastructure Appliance that hosts the proxies are installed in VMs and uses the virtual appliance (hot add) backup method.

V13 - Veeam Software Appliance. The environment described in this architecture consists of one main datacenter containing 5,000 VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of storage space. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeted to a local Veeam Hardened Repository Appliance and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that hosts the proxies are installed on physical servers and uses the network block device (NBD) backup method.

V13 - Veeam Software Appliance. 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. The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups will be targeted to a local Veeam Hardened Repository Appliance and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that hosts the proxies is installed in VMs and uses the virtual appliance (hot add) backup method.

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 ExaGrid repository and copied to a Veeam Data Cloud Vault repository.  All backups must be able to be recovered quickly to the customer's Azure tenant.

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

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 ExaGrid repository and copied to a Veeam Data Cloud Vault repository. Proxies are installed on physical servers and use the secure network transport (NBDSSL) method. The Veeam Data Mover is configured to run on the ExaGrid appliances in a SOBR configuration.

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.

The environment described in this architecture necessitates orchestrated recovery and comprises a production datacenter with 1,000 vSphere VMs and 100 physical servers. Each VM and physical server has an average of 200 GB of utilized storage space. All backups will be directed to a local primary backup repository and subsequently copied to a secondary backup target at a secondary datacenter. The tier one and two VMs will be replicated to the secondary datacenter using Veeam replication. Tier zero VMs will use Continuous Data Replication (CDP). Tier one and two VMs will use Image-Based Replication. Veeam will orchestrate mass recoveries to either the production site or the secondary location. The replica failover will be tested regularly.

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.