Veeam Backup & Replication

V13 - 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. 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 group in a Scale-out Repository (SOBR) and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed on physical servers. The genera

V13 - The environment described in this architecture is one main datacenter containing 1 PB of NAS data. The NAS environment contains 10 shares and 200 million files. 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 group in a Scale-out Repository (SOBR) and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed on physical servers. The general-purpose proxies and cache repositories will be collocated on the same server hardware.

V13 - 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. 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 group in a Scale-out Repository (SOBR) and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed on physical servers. The general-purpose proxies and cache repositories will be collocated on the sa

V13 - 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 Veeam Hardened Repository. The Veeam components will be installed on the Veeam Software Appliance and Veeam Infrastructure Appliance. The tape server is installed on a Linux server. Copies of the backup archives will be stored on magnetic tape media. Proxies are installed on VMs and use the virtual appliance (hotadd) backup method.

V13 - The environment described in this architecture is one main datacenter with 100 VMs  with 200 GB of used storage  hosted on the Proxmox VE Hypervisor . The Veeam components are hosted on the Veeam Software Appliance and Veeam Infrastructure Appliance. All backups target a local Veeam Hardened Repository Appliance and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method.

V13 - 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 target a local Veeam Hardened Repository  and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method.

V13 - The environment described in this architecture are two datacenter and multiple VMs in a cluster with a total average write rate of 1000 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. The Veeam components are host on the Veeam Software Appliance and the

V13 - The environment described in this architecture are two datacenter and multiple VMs in a cluster with a total average write rate of 500 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. The Veeam components are host on the Veeam Software Appliance and the Veeam Infrastructure Appliance

V13 - The environment described in this architecture are two datacenter 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. The Veeam components are host on the Veeam Software Appliance and the Veeam Infrastructure Appliance. The Veeam Infrastructure Appliance that host th

V13 - The environment described in this architecture consists of 500 VMs that require traditional Veeam replication to an offsite datacenter. Each VM has an average of 200 GB of storage space. RPO is 12 hours, requiring replication to occur twice a day, completing within an 8-hour window. The inter-site link is 1gb/s.  This deployment will not share proxy resources with any existing backup tasks. The Veeam components are host on the Veeam Software Appliance and the Veeam Infrastructure Appliance. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup/replication method.

V13 - The environment described in this architecture consists of 100 VMs that require traditional Veeam replication to an offsite datacenter. Each VM has an average of 200 GB of storage space. RPO is 12 hours, requiring replication to occur twice a day, completing within an 8-hour window. The inter-site link is 1gb/s.  This deployment will not share proxy resources with any existing backup tasks. The Veeam components are host on the Veeam Software Appliance and the Veeam Infrastructure Appliance. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup/replication

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

V13 - 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 target a local Veeam Hardened Repository  and copied to the Veeam Data Cloud (VDC) Vault. The Veeam Infrastructure Appliance that host the  proxies are installed in VMs and use the virtual appliance (hot add) backup method.

V13 - 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. 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 and Veeam Hardened Repository are installed on physical servers and uses the secure network block device (NBDSSL) backup method.

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.

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 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 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