Finding a Home for Your VMware and Hyper-V Backups Veeam Backup & Replication Rick Vanover vexpert, VCP, MCITP Veeam Product Strategy Specialist @RickVanover @Veeam
About this webinar Technical in nature for using Veeam Backup & Replication This webinar is recorded and you will get a link to replay the webinar as well as download slides. Ask questions! Pay attention! At the end of the webinar, I ll ask one question and you can win a book!
Agenda Overview of Veeam Backup & Replication What is available: SAN, NAS, cloud and local disk options Where is the best place to implement deduplication When SSD should be part of the mix How to avoid vendor lock-in Demo of these points Q&A
What is the natural choice? It seems natural to do backups the same way as always Agent-based backups Same tools as physical systems Tired list of features, complicated to Get it all Cumbersome processes, slow restores Is this the right decision for Hyper-V or vsphere environments? Maybe, maybe not What are the protection requirements? Platform capabilities can t be beat
As our journey to virtualization goes. Storage has been one of the strongest learning opportunities Transition to virtualization (shared storage) Transition to disk-based backups (backup storage) Risky in terms of consolidation (finding the tipping point)
Differences come with disk-based backups Different purchase decision factors For virtual environments: Performance, then capacity, then price (ideally) For backup infrastructures: Price, then capacity, then performance (historically) Hard to forward provision VM storage requirements VM growth rate different than physical systems Data profile may change
What can we do with VM backups? Disk based backups mean a lot of different things to different environments for VMs Disk storage system decision is important Cost Performance Storage protocol Many types available, each with their own pros and cons SAN NAS Cloud Local disk Others
Options with Veeam Backup & Replication Windows Server Local disk iscsi LUN FC LUN Mount path SMB / CIFS NAS resources Linux Server NFS mount Local path SAN resource
What is the expectation of our VM backup? Just as we can provision quickly. Our restores may have the same expectation Example: Instant VM Recovery Veeam Backup Backup Production of Virtual Machine Virtual Production Machine Virtual Machine running from the backup running file from production storage VM Application (vpower) VM Application (production) vsphere Backup file for virtual machine
Deduplication and VM backups VM backups are an excellent candidate for deduplication System drives and source templates or libraries Many types of deduplication Storage system ingress Post process or background task Post process with partially hydrated zones Source/inline
Deduplication expectations Depends on a number of factors: VM change rate, Data profile Engine capabilities 256 KB (WAN), 512 KB (LAN) or 1 MB (Local Disk) VMs per job Objects (datastores, folders, etc.)
Veeam deduplication
Your mileage will vary Simple measure All VMs, all storage and all networks are not created equal. Same for backup windows, requirements and expectations
Storage decisions: SSD, connectivity, etc. SSD sources for VMs are becoming an option Especially hybrid solutions: Automatically tier SSD to rotational storage Tintri, for example Puts an incredible expectation on VM backup storage
Storage decisions - Continued SSD have seen price drops but still more expensive than rotational storage VMs that are running in flash can also be copied, backed up and cloned without user disruption Backup storage performance is now a critical factor
Avoiding vendor lock-in for VM backup Key is transportability Flat files (Veeam Backup files) are transportable Different for snapshot-based backups Disk system dependent Difficult to leverage multiple storage products Deliver the right storage system for the right VM backup Changing of minds: Multiple backup products Multiple storage solutions
Interactive Demo Quick demo of configuring these points with Veeam Backup & Replication
Q&A One question to win a book! All VMs are created equal. (Fill in the blank) Thank you! Rick.vanover@veeam.com Twitter @RickVanover and @Veeam