1 / 16

Veeam Backup & Replication: 7 Designs for Success

Veeam Backup & Replication: 7 Designs for Success. Rick Vanover, Veeam Software vExpert, VCP, MCITP @ Veeam @ RickVanover. Agenda. 7 scenarios on designing Veeam Backup & Replication Small, medium, large. No SAN, NFS, iSCSI, Fibre Channel

lou
Download Presentation

Veeam Backup & Replication: 7 Designs for Success

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Veeam Backup & Replication: 7 Designs for Success Rick Vanover, Veeam Software vExpert, VCP, MCITP @Veeam @RickVanover

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

  3. Backup storage is first decision Opportunity: Ultimate VM Backup Architecture Characteristics of first backup destination: http://vee.am/stp1002slides

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

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

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

  7. 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 plus2 GB RAM per each concurrent ingress CIFS, NFS, SAN, SMB, Local Disk, VMDK, RDM, etc. See Release Notes http://vee.am/stp1002slides

  8. Design #1: SMB, all virtual • NAS storage forVeeam backups • Configuration ofVeeam sent toNAS resource • Includes separation • Optional jobs for VMs by exception

  9. Design #2: NFS Storage • VA Hot-Addis best datamover • Proxies asVMs • Backups separated

  10. Design #2 - Alternative • Virtual repository • Multiple VMDKs • Or combine theProxy and theRepository

  11. Design #3 – iSCSI storage • Virtual repository • Multiple VMDKsor iqn targets for Veeam Backups • Leverage VADP andDirect SAN access • Hardware initiatoran option

  12. Design #4 – Fibre Channel • Leverage VADP andDirect SAN access • Highest performance • Cores for proxies

  13. #5 – Fibre or iSCSI with Hot Add • Leverage VADP forHot Add reads • Can use dedicatedstorage device as atarget repository • Can easily scalenumber of proxies

  14. Design #6 – Off-site backups • Veeam restore points written toremote repository • Uses new v7 feature • Backup Copy Jobwith Built-In WANAcceleration • Can provide GFS • Realistically only dedupe

  15. Design #7: Cloud option • Leverage publicstorage andcompute • Leverage cloudbased VPN • Restore optionsin cloud

  16. Questions and Wrap-Up Visit our stand at G213 v7 landing page Videos Blogs Press Releases Veeam Forums http://go.veeam.com/v7 http://vee.am/stp1002slides @Veeam @RickVanover

More Related