VM Instant Access & EMC Avamar Plug-In for vsphere Web Client

Transcription

1 White Paper VM Instant Access & EMC Avamar Plug-In for vsphere Web Client Abstract With the ever increasing pace of virtual environments deployed in the enterprise cloud, the requirements for protecting these environments are quickly being identified as the bottleneck to deployment expansion. This white paper provides an overview of two major new features within EMC Avamar 7 that specifically target and greatly advance the capabilities, performance, and management of VMware data protection. June 2013

2 Copyright 2013 EMC Corporation. All Rights Reserved. EMC believes the information in this publication is accurate of its publication date. The information is subject to change without notice. The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. VMware is a registered trademark of VMware, Inc. All other trademarks used herein are the property of their respective owners. Part Number h

3 Table of Contents Executive summary... 4 Audience... 5 Introduction... 5 Image-level Backup & Restore... 6 VM Recovery Flexibility: Avamar VM Instant Access and Changed-Block Tracking for Restore... 9 VM Data Protection Management: EMC Avamar Plug-In for vsphere Web Client Conclusion References

4 Executive summary Today s virtual environments typically contain hundreds if not thousands of VMs. With the lower amount of VMs as we have seen in the past, the data protection scenario can be thought of as somewhat manageable, however given the more recent higher VM counts we have witnessed today, data protection of the environment is no trivial task. Balancing limits on VM growth due to data protection requirements and the expansion requirements requested from business units to cloud administrators is a daunting challenge. Oftentimes the environment continues to grow but portions are left unprotected or protected with less than ideal processes in place. EMC Avamar and it s integration with the VMware s vstorage APIs for Data Protection (VADP), addresses and removes these constraints for VMware environments. Avamar s data deduplication technology seamlessly integrates into virtual environments, providing rapid backup capabilities utilizing the Changed Block Tracking (CBT) feature within the API. As we all know, backup is performed for one reason and that is recovery. The ability to restore data from backup as fast as possible is paramount to your business. Introduced since the Avamar 6.0 release, the CBT process is now leveraged to speed the restore process as well assuring you recover your VMs to production in minutes. Couple this with our newly introduced VM Instant Access capability in Avamar 7.0 or later, for those customers leveraging the flexibility of EMC Data Domain System integration, the ability to boot and run a VM from the backup image in seconds is now also an option. Another important factor to consider in a virtualized backup solution is a robust, flexible, yet easy-to-use backup and recovery management interface. Avamar continues to provide robust integration of live vsphere client data within the main Avamar Administrator UI. In our latest release, to better reduce operational expenses and enhance cross-functional operations in typical data center, Avamar has introduced management functionality embedded within the native vsphere Client interface making backup and recovery management possible from the VMware administrator perspective while still retaining backup administrator control over schedule and retention policies. Couple this with the ability for providing individual VM owners with the ability to complete self service restores without making a restore request, you can accelerate your reduction in overall backup and recovery operational overhead. 4

5 Audience The white paper assumes the reader has a general understanding of the basic concepts and technologies behind EMC Avamar and VMware, and is intended for systems engineers, technical architects, implementation specialists, technical consultants, and individuals interested in leveraging the integration of currently shipping products and emerging technologies. Introduction This whitepaper provides a brief overview of the new features implemented in Avamar 7 for fast, efficient, and easily orchestrated backups and recoveries of VMware virtual machines. For VMware recovery, Avamar 7 offers flexibililty on the VM recovery workflow by offering two methods of orchestrating recoveries. VMware Image Recovery leveraging VMware Changed-Block Tracking (CBT) VM Instant Access While Image-level recovery leveraging CBT may provide the necessary RTO for some virtual cloud environments, there are use cases specifically where mission critical applications are involved, where waiting 3-5 mins for a VM recovery is still unacceptable. For these use cases as you will see in this paper, it is better to leverage the VM Instant Access feature allowing for the Application to be brought up in a much shorter time in production directly from the backup image. Also important in any VM Backup solution is the flexibility and efficiency that the solution brings from a Management perspective. Tightly integrating with the hypervisor management workflow provides efficiencies that in this day in age are required for effective cross-function communication. Today, there are many roles in a typical IT organization responsible in a cloud implementation. Making sure each role has access to backup and recovery management in their native UIs and workflows adds tremendous value and operational expense savings. With this in mind, we will also cover in this feature brief the newly introduced vsphere web client plug-in, which is available for Avamar 7 Backup and Recovery deployment. You will see how little training is required to have VM Administrators orchestrate their own backups and recoveries! 5

6 For the content in this paper, the reader should familiarize themselves with the following terms used throughout this document in the context of backup and recovery. A virtual machine (VM) houses the production data in its virtual environment. This solution was tested in an enterprise environment, so ESX Server was used as the VMware platform. Virtualization allows customers to reduce IT costs while improving efficiency, availability, flexibility, and manageability of their environment. Datastore is a VMware term for the storage that is added to house VMware File Systems (VMFS). The VMFS holds all of the files needed to leverage virtual machines. A VMDK file is a VMware image file that has the data that will be accessed by the application that runs in this VM. It is where the operating system and application are installed along with the data for the respective application. Changed Block Tracking (CBT) is a new VMkernel feature that keeps track of the storage blocks of virtual machines as they change over time. The VMkernel keeps track of block changes on virtual machines, which enhances the backup process for applications that have been developed to take advantage of VMware s new vstorage APIs. VMware vstorage APIs for Data Protection (VADP) enable backup software to perform centralized virtual machine backups without the disruption and overhead of running backup tasks from inside each virtual machine. EMC Avamar is a deduplication backup and recovery software and system solution. It embodies client deduplication that eliminates data from backup streams before it crosses the network. Savings are realized on bandwidth, storage, and backup windows. EMC Avamar Data Store is a bundled EMC solution that combines Avamar software and EMC hardware in a preconfigured, turnkey solution for simplified ordering, installation, and service. The Avamar Data Store scales from a single node to a multi-node solution in order to meet the needs of remote offices to data centers. Image-level Backup & Restore With the image based backup option EMC Avamar integrates with VMware s vstorage API for Data Protection, a feature set within the vsphere server to offload the backup processing overhead from the client to a backup proxy server running as a VM. This proxy server can communicate with the vcenter server to mount a snapshot of a 6

7 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 restore replacing a VM instance or creating a separate instance is also possible and supported. VMs protected via Image-level in Avamar 6.0 can reside on NFS, iscsi, or SAN storage. Given the scalability and sheer explosion in the size of some VM environments the workload burden placed on one proxy server can quickly build up. In this scenario, the recommendation is to provision multiple proxies to handle the combined workload and increase the amount of parallelism occurring when performing VADP processes. With the provisioning of two proxy servers, we can now perform the VADP process on two VMs simultaneously for backup by Avamar. Previously, VMs were assigned manually by the administrator to specific proxy servers to assure proper load balancing. With the latest enhancements introduced within Avamar, this load balancing occurs natively. Avamar will now utilize any idle proxy server to automatically load balance workload and maximize parallelism through the backup process. While offloading the backup-processing overhead from the client under backup to a proxy server provides a lot of benefit, the usage of a proxy alone does not introduce efficiencies and intelligence needed to reduce the amount of data blocks which are scanned and processed by that proxy server. To introduce further efficiency into the VMware image backup process, Avamar fully utilizes the power of VADPs Changed Block Tracking (CBT) feature. As depicted in Figure 3 below, leveraging CBT allows the VM Image Proxy to query the vsphere environment and obtain an intelligent list of which blocks have changed on a specific VM since the last backup. Therefore, Avamar will only scan and process blocks which are included in the changed-block list provided by the CBT mechanism within vsphere. This greatly reduces the backup time of a given VM image and is the cornerstone of Avamar s ability to process large numbers of VMs within a particular given backup window. Figure 1: Avamar VM Image Backup Utilizing Changed-Block Tracking (CBT) 7

8 Prior to Avamar 6.0, Restore operations were an all-or-nothing implementation as depicted in Figure 3. When restoring a particular VM image from a backup within Avamar, the entire VMDK would need to be sent over the network and restored. Recovery of only the individual changed blocks since the last backup within that VM image was not possible. With the introduction of Avamar 6.0, CBT is now leveraged by Avamar software to introduce more efficient and lightning-fast restores. Figure 2: Avamar VM Image Restore Classic Scenario (non-cbt) Some of the highlighted advantages to this VMware Image backup feature set: Provides full image backups of running virtual machines Utilizes efficient transport (SCSI hotadd), which avoids copying the entire vmdk image over the network Provides file-level restores from image-level backups for Windows Deduplicates within and across all.vmdk files protected by Avamar Uses changed block tracking for faster backups & restores. Minimizes network traffic by deduplicating and compressing data Eliminates the need to manage backup agents in each virtual machine for most scenarios Leverages proxy server load balancing to achieve parallelism for superior backup throughput 8

9 VM Recovery Flexibility: Avamar VM Instant Access and Changed- Block Tracking for Restore As mentioned briefly in the previous section of this document, Avamar provides for the fastest recovery possible for virtual machines in the industry. We will now take a look at how Avamar makes this possible in more detail. When a VM Recovery is executed on a particular vmdk, as depicted in Figure 4, Avamar will query the vcenter via VADP to determine which blocks have changed since the recovery point chosen, and then only recover or replace those blocks within the VM image file. This reduces data transfer traffic within the vsphere environment traversing the wire during a restore operation, and more importantly reducing the restore time objective (RTO) of a Virtual Machine Image. To further add to this intelligence, the Avamar software will automatically evaluate the workload between both restore methods (Full Image Restore, or a recovery leveraging CBT) and perform which method will result in the fastest restore times. This is particularly useful in the scenario where the change rate since the last backup on a VM being restored is very high and the overhead of a CBT analysis operation would be more costly than a direct full image recover. Avamar will intelligently decide which deployment method will result in the fastest VM Image recovery times for your particular scenario or enviornment. Figure 3: Avamar VM Image CBT for Restore Scenario There are some use cases however, where the typical SLA that a CBT based recovery provides is not sufficient enough. Certain VMs running mission critical applications need to be brought online immediately with no time to spare waiting for a full Avamar Recovery leveraging VMware CBT. Avamar s integration with vcenter database structure provides the backup administrator with the flexibility for different VM recovery options. A VM backup can be restored to the same VM instance from which the backup was taken or, we can perform a re-directed restore and create an entirely new VM instance within vcenter. All of the steps required to create the VM entry within vcenter have been done for you 9

10 through this integration with Avamar. Once the recovery is complete, the only remaining step is to power on the VM that was created from the recovery process. Figure 4: Ability to recover.vmdk files to different storage As shown in Figure 7, Avamar even gives you the flexibility to deploy a re-directed restore of a VM to a different VM data store entirely. In our latest release of Avamar, recovery flexibility is further extended through our integration with EMC Data Domain systems to allow the administrator to boot and run a VM in production directly from the Backup image. This allows for critical time access for the most important of mission critical applications. Let s now take a closer look at how this is implemented. 10

11 Figure 5: Running a VM from Backup W/ VM Instant Access We will use the illustration in Figure 5 as a reference for walking through a VM Instant Access recovery workflow. In this example, we have 3 VMs, all 3 run mission critical Java applications. Unfortunately, VM3 experienced some partial corruption and is currently unavailable. At this point, the backup administrator can exercise two options in the combined Avamar/Data Domain solution, leverage a full recovery back to the production VMFS datastore as described above, or orchestrate a VM Instant Access operation. For this illustration, we will go ahead and bring the VM back online to the end users immediately and boot it directly from last-night s backup image. As you can see, our VM backup image is currently protected on the Data Domain system enabling us to leverage this feature. From the Avamar Administrator UI as shown in Figure 7 below, an Instant Access operation is requested for last night s backup. The following steps will automatically be kicked into motion: 1. Avamar orchestrates the creation of an NFS Datastore via an NFS Export of the VM Backup Image stored on Data Domain 2. Avamar interfaces with the vcenter environment automatically to create a new VM entry in the appropriate VM database, along with all VM system state and configuration files associated with the VM being recovered. 3. VM is now ready for power-on and boot-up. Since Avamar automatically integrated with vcenter to create the virtual machine entry as described earlier in this section, the administrator simply just executes a power on of the newly added VM. End-users of the Java application running inside this VM can now resume operations as normal. 11

12 Figure 6: Avamar Administrator UI Instant Access Option While the VM is now running from the Backup, Avamar does not overwrite the original backup image. Any new I/O to the VM running from the backup goes into a separately tracked VM snapshot file. In order to complete the recovery of the VM to production storage, the administrator can leverage the normal vsphere interface to easily execute a Storage vmotion from the temporary NFS datastore export on Data Domain to the production VMFS datastore location. The key to this use case is that rather than waiting for a full restore to production storage that takes only minutes, the administrator can literally bring back a downed application from backup storage in a much shorter timeframe. Also, with the tight integration with VMware APIs this entire process is completed in seconds and is very easily managed and orchestrated, just takes a couple of clicks. 12

13 VM Data Protection Management: EMC Avamar Plug-In for vsphere Web Client The second major integration Avamar provides within VMware s vcenter ecosystem is the ability to install the Avamar Plug-In for vsphere Web Client. This is a plug-in that enables a VM Administrator with access to the vsphere Web UI, to take direct control of, and monitor Avamar backup and recovery for VMs within that specific vcenter environment. Figure 7: EMC Avamar Plug-In for vsphere Web Client Home Screen As shown here in Figure 9, the plug-in brings Avamar orchestration natively within the vsphere UI as an added sub-menu option. From this main interface, the administrator can go ahead and create backup policies, and orchestrate VM restores quickly. The biggest value add this Avamar plug-in for vsphere brings for IT staff is significant savings and efficiencies with no requirement to train VM administrators in new backup and recovery tools and interfaces. Avamar functionality is incorporated directly in the user interface style VM administrators are already familiar and comfortable with. More critical to an IT staff is the ability to empower application administrators to perform data and system recovery with minimal intervention and dependency on the backup team. In a VMware scenario, the ability to empower the VM Administrator to perform his or her own VM image recoveries is a foundation design point in bringing this management flexibility to Avamar customers. As shown below in Figure 10, it is 13

14 easy to leverage the plug-in to do just that, this plug-in provides all of Avamar s efficient recovery features at the VM Administrator s fingertips. Figure 8: EMC Avamar plug-in for vsphere Web Client Restore Tab While being able to orchestrate backups and recoveries efficiently is critically important to IT organizations, it is also equally important that all members of the IT team have a unified view of the operational status. Within the context of the same plug-in Avamar provides in the vsphere interface for executing VM backup and recovery operations, the same administrator can take the initiative independent of the backup administrator to gain insight into reporting metrics of the Avamar solution. As you can see in figure 11 below, from the Reports tab the VM administrator can also quickly look into system space utilization, along with the status of any scheduled or on-demand VM backup and restore jobs. All of this information is displayed within the management constructs and terminology of the vsphere workflow, so as all information is clear and concise in a language and style the VM Administrator understands right away. With this dashboard style display, an Administrator can quickly identify if any regular backups have failed or, if there are any, VMs which have not been backed up entirely. 14

15 Figure 9: EMC Avamar Plug-In for vsphere Web Client Reports Tab As you can see using either the Avamar Administrator UI or the vsphere Web UI, both administrators are able to view consistent data metrics and status across the entire VM backup and recovery policy set. Consistency across these various management interfaces which are tailored for different administration styles bring the added benefit of clear and concise information sharing between IT roles that otherwise would be time consuming to and involve human interaction to maintain. Clearly in today s globally distributed IT environments providing tools to enhance or eliminate the need for verbal or written communication for coordination clearly provides cost savings, reduced risk, and operational efficiencies. Conclusion With the ever-increasing demands placed on virtual cloud infrastructures via new ITas-a-service deployments, the need to protect the environments with some sort of data protection scheme still remains. Avamar has implemented the VMware features described in this paper and is already providing customers today with a more efficient VMware backup and recovery solution. Avamar 7 extends the improvement in backup process efficiency for VM backups, and continues to build upon its industry leading VM backup feature set with tighter integration and backup process management options for both the Backup and VM 15

16 administrator. With features detailed in this whitepaper, EMC Avamar continues to lead the industry in innovation making backup and restores for virtual environments more efficient and more importantly faster, allowing for worry-free and cost-effective expansion. References VMware product pages on VMware.com Avamar Product Page on EMC.com Powerlink, EMC s customer- and employee-only extranet (registration required) 16