From Veeam's Solutions Architects!
Recently active
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
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 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 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 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 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 a Veeam Backup for Google Cloud deployment with 1000 workloads to protect. The protection scope includes Google Compute Engine(GCE) and CloudSQL. All backups will be targeted to an object storage repository in Google Cloud Storage(GCS) with Standard Storage Class and archived to GCS with Archive Storage Class.
Updated - V12.1The environment described in this architecture focuses on a single, 1 TB database instance. Most environments have multiple database instances, across multiple servers that may range from a few gigabytes (GB) in size to multiple terabytes (TB). This scenario can be used as a baseline to deploy for those multiple database environments.
The environment described in this architecture is a Microsoft 365 (M365) deployment with 10,000 users. Included within the protection scope is Mailboxes, Archive Mailboxes, and OneDrive for Business. Additionally, 1,000 SharePoint Online sites and 1,000 Teams. Total Space consumed in Microsoft 365 across the above applications is 100TB. All backups will be targeted to an object storage repository in Azure and copied to Azure Archive storage using a backup copy job. Veeam Backup for Microsoft 365 will be installed on Azure VMs.
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 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.
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.
The environment described in this architecture consists of a main datacenter with a single Kubernetes cluster running Red Hat OpenShift Container Platform with multiple application namespaces on Azure Cloud Computing services. All local snapshots will be exported to an immutable backup repository to protect against deletion or encryption attacks. Additionally, backups are imported onto a standby cluster for disaster recovery.
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. Copies of these backups will be stored on magnetic tape media. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method.
Updated - V12.1The environment described in this architecture is a 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 use the network transport (NBD) method.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
