Veeam Backup & Replication v6 Part 2: VMware and Hyper-V in one solution Doug Hazelman Vice President of Product Strategy Anton Gostev Director of Product Management Release contents subject to change prior to general availability (GA)
Agenda Introduction to Veeam Backup & Replication v6 Feature: Multi-hypervisor support Differences in VM processing Veeam Backup & Replication for Hyper-V 2-in-1: Backup and Replication Changed block tracking for Hyper-V Built-in compression and deduplication Unified data protection Demonstration Q&A
Poll Question Which Hypervisor does your organization (primarily) use?
Hyper-V support FAQ Q: Can you backup a Hyper-V VM and restore to a VMware host? A: No Q: Can you replicate a VMware VM to a Hyper-V host? A: No Q: How will it be licensed? A: Per socket, both platforms at the same price Q: Is vpower-based functionality available for Hyper-V. A: Not yet coming soon. This is the only difference so far. Q: What if I already own Veeam Backup & Replication for VMware and want to transfer licenses to Hyper-V? A: It s your lucky day
What s coming in v6 Enterprise scalability Advanced replication Multi-hypervisor support Numerous enhancements, including 1-Click File Restore
New distributed architecture New distributed architecture Better performance with lightweight proxies that act as data movers Simplified deployment and maintenance of remote/large scale installations Allows backup or replication over WAN Differences in platforms: VMware: pure proxy model; ESXi host cannot be the proxy (no accessible service console) Hyper-V: the host itself can be the proxy; option for off-host proxy to offload processing from Hyper-V
Hypervisor differences Specifically differences in backup: Snapshots Encapsulation Incremental backups
Snapshots Big differences between ESX(i) and Hyper-V ESX(i): Hypervisor snapshots: It s all about commit Storage snapshots: It s all about VMFS Hyper-V: Hypervisor snapshots: Limited Have to power-cycle VM to commit Storage snapshots: VSS and NTFS Software and storage assisted No performance hit w/hardware integration No commit
Snapshots with Hyper-V Use VSS, snap the volume Host as proxy Has access to the LUNS No additional setup Puts load on the host during backup operations Use off-host proxy Hyper-V Role needs to be enabled Server needs connection to LUNS (does not need to be part of CSV, iscsi initiator works fine) Need to configure according to hardware VSS provider
Encapsulation VMware: The entire VM sits in a directory structure, easily transportable Hyper-V: The VHD is the virtual disk data, but other important configuration information is stored on/in the host Recovering a Hyper-V VM to a different host requires export/import of this configuration information not easy!
Backups VMware gave us VMFS, CBT, VDDK, VAAI CBT is much better than the snap and scan method VDDK to read proprietary VMFS (for VM Snapshots) VAAI to offload some tasks to storage Actual snapshots cannot be offloaded to storage Microsoft gave us NTFS, VSS NTFS is easy to interact with directly Snapshots can be offloaded to storage No changed block tracking provided natively
Incremental backups Change block tracking for Hyper-V Veeam s File System Filter Driver is installed on each host in the cluster to keep track of changed blocks Microsoft CSV adds more challenges Differences in file clustering file system requires different approaches to incremental backups CSV requires coordination of changed block tracking data on all hosts connected to the CSV
2-in-1: backup and replication for Hyper-V Comprehensive data protection Unified approach
Changed block tracking for Hyper-V Fast incremental backup 20x faster Near-CDP backup and replication Supports VMs running on CSVs
Built-in compression and deduplication Manage large volume of data generated by imagebased backups Includes optional synthetic fulls and reversed increments to manage full backups data volume Included at no extra charge
Unified data protection across hypervisors Single license, install and console Same data protection infrastructure but still hypervisor-specific (e.g., volume- vs. VM-level snapshots) Single console for VMware and Hyper-V Same data protection infrastructure for VMware and Hyper-V
Unique offering Free license swaps Restore VM on any Hyper-V host Protect all VMs, including VMs on hosts running Windows Server Core installation
Poll Question Do you plan on switching hypervisors on the next 12-18 months?
So what are the differences? Shared processing engine Just a matter of different datasource to get data from, this is where the differences end! Single engine beyond datasource: backup format & modes, application-aware processing, retention, scheduling, statistics, notifications are all the same. All backup, replication and restore features are available for both platforms vpower is the only difference vpower-based features like Instant VM Recovery, SureBackup, Virtual Labs, Universal FLR are not yet available for Hyper-V (coming soon)
Demonstration
Register for the remainder of the series! Go to the Veeam v6 Landing page: http://vee.am/v6 Part 3: Advanced replication: 10x faster replication with streamlined failover and real failback Date: October 12 th Time: 11:00a.m.-12p.m. ET Part 4: Not a 1-click wonder : Learn more about the other enhancements available in v6 including 1-click file restore, 1- click VM restore and our new VM Migration for VMware Date: October 26 th Time: 11:a.m.-12p.m.
Poll Question Which 3 features are most important in a backup solution?
Thank you! For more information Contact the presenters: Email: vmdoug@veeam.com Twitter: @VMDoug Email: gostev@veeam.com Twitter: @Gostev Veeam Blog www.veeam.com/blog Veeam Forums: www.veeam.com/forums Follow @Veeam on Twitter