Nelson Simao

Systems Engineer

Veeam Backup and Replication

Architecture and Deployment

Agenda

Veeam Backup Server / Proxy Architecture

Veeam Backup Server / Backup Proxy

Backup Transport Modes

Physical or Virtual Machine?

Remote office Branch office deployments (ROBO)

Backup to cloud integration

Dual Site deployment

Demo

Q&A

Veeam Backup Server / Proxy Architecture

Veeam Backup Server

Windows based physical or virtual machine ● Coordinates backup, replication, recovery verification and restore tasks

● Controls job scheduling and resource allocation

● Is used to set up and manage backup infrastructure components as

well as specify global settings for the backup infrastructure

Requires a SQL database instance ● Simple: Installer includes SQL server express 2005 SP4 which can be

installed on the VBR server

● Advance: Leverage on an existing SQL database server

Protection of Veeam database instance ● Using native SQL tools for local instance (Physical Server)

● Use VBR server to backup itself (VM)

Veeam Backup Proxy

Backup Jobs ● Data mover for VM data from the production storage, compressing and

sending it to the backup repository

Replication Jobs ● Data mover for VM data from the production storage, compressing and

sending it to another backup proxy

Windows based physical or virtual machine

Always deploy backup proxies close to the source which you want to backup

Remote replication will require a source and target proxy

Deployment of additional proxies will be dependent on ● Backup window requirements

● High availability of proxies

Direct SAN Access mode

Veeam backup proxy has access to the SAN (Physical

server/FC or VM/iSCSI)

Metadata on the layout of the virtual disk are sent to the

Veeam backup proxy from the ESX host

Veeam backup proxy will read the data that needs to be

backed up directly from the SAN and send them to the

repository

Virtual Appliance mode

Veeam backup proxy is deployed as a VM

Using VADP hot add scsi capability, the virtual disks of a VM can be directly attached to the Veeam backup proxy VM

The Veeam backup proxy VM will read the attached disks and sent the backup data to a repository

Note that the datastore hosting VMs to be backup must be visible to the ESX host holding the Veeam backup proxy

Network Mode

Veeam backup proxy can be deployed as physical or

virtual

ESX hosts reads and sends data to backup proxy over

the LAN which is then sent to the repository

Slowest mode and loads on the network

Using physical host

Veeam Backup Server ● Minimal RTO to bring up backed up VMs using IVR when ESX

infrastructure goes down

Veeam Backup Proxy ● Physical SAN access mode for best backup performance can be

enabled

● Backup processing will not consume ESX host’s resources

● Tape backup software can be deployed on same server for tape out of

Veeam backup images

● Restores will be in network mode

● Higher deployment budget cost

Using VM

Veeam Backup Server Very simple and fast to deploy as there is no lead time required to

order and setup hardware

Increased RTO when ESX infrastructure goes down

Veeam Backup Proxy ● Very simple and fast to deploy as there is no lead time required to

order and setup hardware

● VADP which allows hotadd scsi capability for backups and also

restores

● Can use physical SAN access mode only with iSCSI

Physical or Virtual Machine?

Size of environment. ● Big -> Physical / Small -> VM

● Physical deployment for highly consolidated environments

Physical server will incur additional hardware costs

Performance versus costs

Any requirement for tape out of Veeam backup images

Remote office/Branch office

Scenario 1

Remote office/Branch office

Scenario 2

Backup to the cloud integration

Backup to the cloud? ● Cloud storage is utility based, pay as you grow

● Provides an alternative to setting up an offsite location for backup images

● Minimal setup costs and is hassle free

● Access backup images from “anywhere”

● Recovery will need additional steps which will increase RTO

● RTO very dependent on bandwidth to cloud provider

● Security issues, encryption, etc

Deployment usually involves integrating Veeam Backup and Replication with a cloud storage gateway

Cloud storage gateway is configured as target storage for the backup repository

When backup data is sent to the backup repository, the backup data is automatically synced to cloud storage

Backup to the cloud integration

Backup to the cloud integration

Backup to the cloud integration

Dual site deployment

Hot and cold site

Deploy a Veeam backup server at each site

Veeam backup server at hot site will schedule hot site

local backups

Veeam backup server at cold site will schedule

replication of hot site VMs to cold site

In the event of hot site failure, the cold site Veeam

backup server can be used to perform failover of VMs

Once hot site is recovered, failback of VMs can be

performed

Dual Site (Hot/Cold) Deployment

DEMO

Register for our other Webinars!

Topic: Veeam Backup and Replication v6.1

Topic: Veeam Replication for Disaster Recovery

Topic: Veeam vPower deep-dive demo

Topic: Veeam Backup and Replication for Hyper-V

http://www.veeam.com/product-demo

Thank you!

For more information, contact the presenter:

Email: nelson.simao@veeam.com

Twitter: @nelson_veeam

Veeam Blog www.veeam.com/blog

Veeam Forums: www.veeam.com/forums

Follow @Veeam on Twitter

Q&A