Veeam Backup & Replication: 7 Designs for Success

Veeam Backup & Replication: 7 Designs for Success

Rick Vanover, Veeam Software vExpert, VCP, MCITP @Veeam @RickVanover

© 2013 Veeam Software. All rights reserved. All trademarks are the property of their respective owners.

Agenda• 7 scenarios on designing Veeam Backup &

Replication• Small, medium, large. No SAN, NFS, iSCSI, Fibre

Channel• A starting point for your design• You can download these slides:

http://vee.am/stp1002slides


Backup storage is first decision• Opportunity: Ultimate VM Backup Architecture

Characteristics of first backup destination:Attribute Logic

High performance Meet the expectation of modern infrastructure systems

High cost Goes along with first point

Low retention (Relatively speaking) Keep most frequent restore points close, other points available.

Low capacity A consequence of all three of above



Ultimate VM backup architecture• http://vee.am/ultimate


Critical Veeam Components• Console – The UI where you install Veeam• Proxy – Data mover, interacts with VADP, reads CBT• Built-In WAN Acceleration – Part of Backup Copy Job

to write restore points in remote repositories.• Repository – Disk resource to hold Veeam backups

VBK Format Veeam disk based backup format

Linux host With SSH and Perl, we can install a target writer.

Windows path LUN (FC/iSCSI), removable disk, drive letter, mount point.

NAS Target SMB, UNC, CIFS network targets


Component Requirements• Console• Modern 64-bit Windows operating system (Vista+,2008 R2+)• 4 GB RAM + 500 MB per concurrent job

• Proxy• x86 and x64 OSes supported (XP+/2003+)• Connectivity: Network, Storage• 2 GB RAM + 200 MB per concurrent task

• Built-In WAN Acceleration• Modern 64-bit Windows operating system (Vista+,2008 R2+)• 8 GB RAM• Disk for cache


Component Requirements• Built-In WAN Acceleration• Modern 64-bit Windows operating system (Vista+,2008 R2+)• 8 GB RAM• Disk for cache

• Repository• Linux OS, x86 and x64 OSes supported (XP+/2003+)• 4 GB RAM plus 2 GB RAM per each concurrent ingress• CIFS, NFS, SAN, SMB, Local Disk, VMDK, RDM, etc.

• See Release Notes



Design #1: SMB, all virtual• NAS storage for

Veeam backups• Configuration of

Veeam sent toNAS resource

• Includes separation• Optional jobs for

VMs by exception


Design #2: NFS Storage• VA Hot-Add

is best datamover

• Proxies asVMs

• Backups separated


Design #2 - Alternative• Virtual repository• Multiple VMDKs• Or combine the

Proxy and theRepository


Design #3 – iSCSI storage• Virtual repository• Multiple VMDKs

or iqn targets for Veeam Backups

• Leverage VADP andDirect SAN access

• Hardware initiatoran option


Design #4 – Fibre Channel• Leverage VADP and

Direct SAN access• Highest performance• Cores for proxies


#5 – Fibre or iSCSI with Hot Add• Leverage VADP for

Hot Add reads• Can use dedicated

storage device as atarget repository

• Can easily scalenumber of proxies


Design #6 – Off-site backups• Veeam restore

points written toremote repository

• Uses new v7 feature• Backup Copy Job

with Built-In WANAcceleration

• Can provide GFS• Realistically only dedupe


Design #7: Cloud option• Leverage public

storage andcompute

• Leverage cloudbased VPN

• Restore optionsin cloud


Questions and Wrap-UpVisit our stand at G213

v7 landing page VideosBlogsPress ReleasesVeeam Forums

http://go.veeam.com/v7 @Veeam

@RickVanoverhttp://vee.am/stp1002slides

http://go.veeam.com/v7

http://go.veeam.com/v7

Veeam Backup & Replication: 7 Designs for Success

Documents

Transcript of Veeam Backup & Replication: 7 Designs for Success