Table of ContentsVirtualization Leading IT Transformation . 3Why the IT Transformation? . 4How can Backup & Recovery accelerate this journey? . 4Why Avamar? . 6Avamar Virtual Edition . 6Guest-Level Backup & Recovery . 7VMware guest backup capabilities . 7VMware guest backup limitations . 8Image-Level Backup & Recovery . 8VMware Image backup capabilities . 9VMware Image backup limitations . 9Why CBT? . 9Backup & Recovery with CBT . 10The requirements . 12VADP Snapshot Consideration . 12Avamar Integration with Data Domain . 12AVE with Data Domain . 12Licensing Guide . 14Appendix . 17Disclaimer: The views, processes, or methodologies published in this article are those of theauthor. They do not necessarily reflect EMC Corporation’s views, processes, ormethodologies.2014 EMC Proven Professional Knowledge Sharing2

Virtualization Leading IT TransformationThe IT Transformation Storymap graphically depicts the aspects of transformation to deliverIT as a service across infrastructure, application, and operating model, using an analogyfrom automobile manufacturing.Figure 1: IT Transformation StorymapGenerally, EMC believes there are there are three steps for the IT transformation.Step 1: Transform existing infrastructure to a cloud infrastructure. This is the move from rigidapplication-based silos to a truly dynamic infrastructure that can address the needs beingplaced on IT. In this step, virtualization is relied on to reach what we call the “softwaredefined data center”.Step 2: Transform the operating model to deliver IT as a service. IT must act and operatelike a Service Provider.Step 3: Build applications for the cloud. Leverage Big Data to build mobile and predictiveanalytic applications.2014 EMC Proven Professional Knowledge Sharing3

Figure 2: The 3 steps of IT TransformationWhile we still have work to do, improvements to make and kinks to work out. This will alwaysbe the case. Transformation is eternal. The need to adapt will be increasingly important asthe pace of business continues to accelerate and complexity manages to creep in as scaleincreases. Transformation is not a simple process. It is a journey that takes patience and acollective effort from all parts of the organization, but the results are worth the trip.Why the IT Transformation?These transformations are happening across infrastructure, applications, and operations.They increase revenue and lower operational costs for the business while providing amultitude of services are the key goals for many IT organizations. This requires services thatare both compelling and meaningful to the business and may be delivered by both internaland external providers to meet these goals.How can Backup & Recovery accelerate this journey?By enhancing backup and recovery, EMC and VMware together can help its customersunlock additional business value and accelerate their journey to broader, potentially 100percent, virtualization.Enhanced backup and recovery leads to extended business value that fuels the journey to100 percent virtualization.2014 EMC Proven Professional Knowledge Sharing4

Avamar’s enhanced backup and recovery enables you to: Increase consolidation ratios Perform 90 percent faster backups Experience 40- to 60-times data reduction and a 99 percent reduction inreplication bandwidth Have file, image, and site recoveryAvamar’s extended business value translates into: Lower backup infrastructure costs Simplified management Improved operations Investment protection Reduced riskFigure 3: Benefits of IT Transformation on Business Value & Backup and Recovery Systems2014 EMC Proven Professional Knowledge Sharing5

Why Avamar?EMC Avamar provides variable-length client-side deduplication to accelerate thevirtualization journey by providing extremely fast and efficient backup and recovery for theVMware environment. Avamar protects virtual machines (VMs) by deduplicating data at theclient level so that only new, unique, sub-file, variable-length data segments are sent duringdaily full backups. While traditional backup software moves upward of 200 percent of theprimary backup data on a weekly basis, Avamar moves as little as 2 percent over the sameseven-day period, removing backup bottlenecks and enabling even greater levels ofvirtualization.In many ways, Avamar was really built for VMware backup. Additionally, Avamar andVMware is a great match as it supports all major modes of VMware backup, either guest orimage. We will discuss them in depth in the next sections.Avamar Virtual EditionAvamar Virtual Edition (AVE) for VMware is Avamar server software deployed in a VMwarevirtual machine. AVE for VMware is an ideal product for small, medium, or remote officesthat have standardized on VMware infrastructure. AVE for VMware provides: Rapid, cost-effective deployment. Simplified management by virtualizing all aspects of the backup and recoveryoffering. Lower cost by leveraging shared server and storage infrastructure. Replication in virtual environments as well as between virtual and physicalenvironments for disaster recovery. Rapid return on investment. VMware vMotion support. Scalability with support for up to two Avamar Virtual Edition for VMware virtualappliances per ESX server. Capability to work on any server and iSCSI, SAN, or DAS storage that meetsthe combined Avamar and VMware specifications.2014 EMC Proven Professional Knowledge Sharing6

Starting with Avamar 7.0, each Avamar Virtual Edition for VMware virtual appliance supportsup to 4TB of licensed disk storage capacity provisioned to a virtual machine on a VMwareESX server. Other available capacities: 500GB, 1TB, and 2TB.Guest-Level Backup & RecoveryWith the guest backup option, the Avamar client software is installed on the individual virtualmachines. Backup configuration for this method is identical to that of a physical machine.Backup agents are installed on the virtual machines and send their backup data to thebackup application for storage.Figure 4: Guest-Level Backup & RecoveryVMware guest backup capabilities Highest level of data deduplication. Support for backup of applications inside the virtual machines. Application-consistent backups. Support for partial or file-level restores. Identical backup methodes for physical and virtual machines. No requirement for advanced scripting or VMware software knowledge. Unchanged day-to-day procedures for backing up.2014 EMC Proven Professional Knowledge Sharing7

VMware guest backup limitations Since each virtual machine has a separate backup client installed, ESX servers witha large number of virtual machines may experience a strain on resources, especiallymemory, if all machines are backed up at the same time. No Image-Level restore option. File-level restore is done in one step; however, full system restore is done in twosteps.Image-Level Backup & RecoveryAvamar is tightly integrated to vStorage APIs for Data Protection (VADP) for agentlessbackups. VADP enables backup products to perform centralized, efficient, off-host backupsof vSphere virtual machines. Introduced in vSphere 4.0, VADP replaces the VMwareConsolidated Backup Framework (VCB) for virtual machine backups. Since VADP integratesdirectly with Avamar, no additional software is required to be downloaded and installed.Incremental backups and restores are supported through the use of change block tracking(CBT) which will be explained in detail later in this article.Figure 5: Image-Level Backup & RecoveryVMware Image Backup uses a proxy server to handle backup processing. Using VADP,Avamar can back up VMware virtual machines without using backup agents inside eachvirtual machine. This proxy server can communicate with the vCenter server to mount a2014 EMC Proven Professional Knowledge Sharing8

snapshot of a particular VM's vmdk to perform image-level backup of that virtual machine.With this method, deduplication is provided on the file level as well as on the .vmdk level.Performing an image-level backup of a VMDK, the ability to execute a bare metal restorereplacing a VM instance or creating a separate instance is also possible and supported. Thisis accomplished by creating a snapshot of the virtual machine, then backing up thatsnapshot. No downtime for the virtual machine is required. Backup processing can beoffloaded from the ESX hosts, depending upon the method of deploying the proxy. File-levelbackups and restores are supported with image level backup.VMware Image backup capabilities Perform backup and restores without installing agents on individual virtual machines. Perform backups from a centralized location, thus offloading backup processing fromthe ESX hosts. Perform backups any time because backups are non-disruptive to the virtualmachines being backed up. The ability to perform backups at any time provides greater flexibility in schedulingbackups and increased backup window times.VMware Image backup limitations Requires at least ESX 4.0. Requires a moderate amount of VMware knowledge to set up and configure backupsand restores. Backups consume ESX server resources, including CPU, RAM, and disk. Backup requires a temporary virtual machine snapshot. Backup is crash-consistent snapshot of full VM image and may not support a fullsystem restore without data loss. File level restore from an image backup for Windows and for Linux, starting withAvamar 6.1.Why CBT?Starting with Avamar 6.0, support for vSphere Changed Block Tracking (CBT) enables fasterbackup and recovery by tracking incremental changes on virtual machines, introducingincremental protection instead of requiring full backups and full restores.2014 EMC Proven Professional Knowledge Sharing9

Another enhancement with Avamar 6.0 is proxy VM load balancing. With proxy VM loadbalancing, VM backups utilize a pool of backup server resources balanced for higherthroughput and backup speed. Provisioning of two proxy servers enables the VADP processto be performed on two VMs simultaneously for backup by Avamar. Previously, VMs wereassigned manually by the administrator to specific proxy servers to assure proper loadbalancing. However, as of Avamar 6.0, this load balancing occurs natively. Avamar will nowutilize any idle proxy server to automatically load balance workload and maximize parallelismthrough the backup process. Flexible image recovery options enable administrators torestore any backup image to a virtual machine, not just the most recent full backup of thatspecific VM. This vCenter integration feature enables Avamar to create a VM in a vSphereenvironment as part of the recovery process.Backup & Recovery with CBTThe Avamar agent is installed on a Proxy VM, off-loading the backup process from any ofthe VMs where the applications are running. Through vSphere, each VM is dynamicallymounted to the proxy without physically moving data across the network, enabling Avamar toback up numerous virtual machines in just minutes. With CBT, VMware presents onlychanged blocks to the Avamar agent, where each block is broken into variable lengthsegments and further evaluated for uniqueness. Only the unique segments are sent forbackup, achieving the fastest backup possible. Conversely, the restore process alsoleverages CBT for faster recovery. Avamar enables full VMDK or file-level restore to theoriginal VM, an existing VM, or a new VM directly from the Avamar user interface as shownin Figure 6-1, 6-2, and 6.3.LAN-freeLAN/WANCBT BackupVirtualVMCBTProxyUniqueServerBlocksFigure 6-1: CBT Backup2014 EMC Proven Professional Knowledge Sharing10

The VMware vStorage API for Data Protection determines the changed blocks. Then, theproxy reads only these changed blocks, deduplicates them, and sends the unique blocks toAvamar as depicted in Figure 6-1.LAN-freeVMWhole VMLAN/WANVirtVirtualualProxyWhole VMStandardRestoreVMProServerFigure 6-2: Standard RestorePrior to Avamar 6.0, Restore operations were an ''all-or-nothing'' implementation as depictedin Figure 6-2. When restoring a particular VM image from a backup within Avamar, the entireVMDK would need to be sent over the network and restored. Recovery of only the individualchanged blocks since the last backup within th