You are on page 1of 30

VCE Word Template

Table of Contents

www.vce.com

BEST PRACTICES FOR USING EMC AVAMAR OR AVAMAR WITH DATA DOMAIN DATA PROTECTION PRODUCTS WITH VCE VBLOCK INFRASTRUCTURE PLATFORMS
April 2012

2012 VCE Company, LLC. All Rights Reserved.

Contents
Executive summary ..................................................................................................................4 Benefits ...................................................................................................................................4 Objectives ................................................................................................................................5 Use cases: backup and recovery ............................................................................................5 Audience..................................................................................................................................5 Technology overview................................................................................................................6 Vblock Infrastructure Platforms.............................................................................................6 EMC Avamar ...........................................................................................................................7 EMC Avamar virtual machine image proxy ..............................................................................7 EMC Avamar file-level recovery proxy .....................................................................................7 VMware vCenter Server...........................................................................................................7 VMware ESXi ..........................................................................................................................7 EMC Data Domain ...................................................................................................................8 EMC Data Domain Boost .........................................................................................................8 Architecture overview...............................................................................................................9 Avamar architecture with Vblock platforms ............................................................................10 Avamar and Data Domain architecture with Vblock platforms ................................................11 Avamar architecture and best practices ...............................................................................12 Integration of EMC Avamar with Vblock platforms .................................................................12 Recovery ............................................................................................................................13 Replication..........................................................................................................................17 Avamar with Data Domain architecture and best practices .................................................18 Integration of Avamar and Data Domain with Vblock Platforms .............................................18 Recovery ............................................................................................................................19 Replication..........................................................................................................................19 Using Avamar/Data Domain centralized control and management .....................................20 Example One: Configure a Data Domain system within the Avamar Administrator interface ..............................................................................................................................................20 Example Two: Specify a dataset policy within the Avamar Administrator interface .............25 Conclusion ..............................................................................................................................28 Next Steps .............................................................................................................................28

2012 VCE Company, LLC. All Rights Reserved.

References ..............................................................................................................................29

2012 VCE Company, LLC. All Rights Reserved.

Executive summary
Most corporate Information Technology departments are tasked with protecting an ever-increasing volume of business applications and data. At the same time, budgets are not expanding to match this growth. The only way to meet these business requirements is to do more with less. In a drive for greater efficiency, the IT industry has moved rapidly toward server virtualization. Having now realized the benefits of virtualization, the industry has moved to the next step for even greater efficiency: converged infrastructures such as VCE Vblock Infrastructure Platforms. During the move to server virtualization, early adopters quickly discovered that the use of traditional backup, recovery, and archiving solutions for daily data protection creates bottlenecks in a virtualized infrastructure. Those bottlenecks not only extend the required backup window, but they also set a cap on the number of virtual servers that can exist on each physical server blade. The EMC Avamar data protection product on VCE Vblock platforms directly addresses and resolves the backup bottleneck problem in virtual environments. Avamar is extremely effective at delivering backups in less time, using fewer network resources and fewer virtual server resources than other options. In addition, it is tightly integrated with VMware. All of this translates into real capital savings and operational benefits. For these reasons, Avamar is an excellent choice to be used with Vblock platforms. When used along with EMC Data Domain on Vblock platforms, Avamar will, in many scenarios, expand backup scalability and further lower the cost per terabyte (TB) of data backup. This VCE-recommended backup solution includes two options, along with best practices for each: An Avamar-only solution on Vblock platforms A highly effective combination of Avamar and Data Domain on Vblock platforms

Using the Avamar interfaces and workflows, one can quickly and easily direct enterprise-wide backups to both of these EMC deduplication platforms, while simplifying the backup management infrastructure. This combination offers the benefits of Data Domains scale and performance and Avamars simplicity and efficiency, as well as Vblock platforms power and scalability. This paper highlights the specific features of these integrations, and explains how the integration of Data Domain systems into the Avamar management framework can enhance the management and optimization of backup operations without additional management overhead. Described are the solutions architectures hardware and software, and best practices for each solution. This paper also explains how to use the Avamar Administrator management tools to control data flow, and provides two examples with steps for using Avamar Administrator.

Benefits
The benefits of using the data protection solutions and best practices described in this paper include: The best of breed compute, networking, storage, and virtualization technologies
2012 VCE Company, LLC. All Rights Reserved.

A fully virtualized environment with the inherent efficiencies and flexibilities of VMware Elimination of bottlenecks that hamper scaling up Greater efficiency and cost effectiveness of the customers Vblock platform investment

Objectives
This white paper explains best practices and the Avamar Administrator tool use through scenarios and steps for two options: 1. Avamar-only on Vblock platforms 2. Avamar and Data Domain combined on Vblock platforms

Use cases: backup and recovery


Avamar is a backup-and-recovery software solution and a backup data target, whereas Data Domain is a backup data target that requires backup-and-recovery software to function. Together, Avamar and Data Domain support once-per-day backups and daily movement of a backup copy to an offsite archive without the risk inherent in transporting physical media. The products have tight integration with VMware deduplication capabilities, which reduces network I/O requirements, and have modules that support databases and Microsoft Exchange. For customers who need to store backups for very long times, Data Domain can deliver cost-effective archiving. Avamar and Data Domain targets have different advantages. The combination of the two addresses a broader set of data protection requirements for customer choice.

Audience
This white paper is intended primarily for backup systems administrators and IT administrators who are responsible for architecting and deploying data protection solutions across the virtualized enterprise. Knowledge of basic data deduplication concepts is assumed.

2012 VCE Company, LLC. All Rights Reserved.

Technology overview
This solution uses the following components and technologies: Vblock Infrastructure Platforms EMC Avamar v6.0 EMC Avamar virtual machine image proxy EMC Avamar file-level recovery proxy VMware vCenter Server VMware ESXi EMC Data Domain EMC Data Domain Boost

Vblock Infrastructure Platforms


Vblock platforms are enterprise- and service-provider-class IT infrastructure units that are preengineered, tested, and validated with pre-defined performance, capacity, and availability service levels. The standardized converged infrastructure of Vblock platforms is a foundation block for cloud computing that helps customers realize the benefits of applications running in a virtualized environment. Vblock platforms are characterized by: Repeatable units of construction based on matched performance, operational characteristics, and discrete requirements of power, space, and cooling Repeatable design patterns that facilitate rapid deployment, integration, and scalability An architecture that can be scaled for the highest efficiencies in virtualization and workload mobility An extensible management and orchestration model based on industry-standard tools, APIs, and methods A design that contains, manages, and mitigates failure scenarios in hardware and software environments Vblock platforms provide pre-engineered, production-ready (fully tested) virtualized infrastructure components, including industry-leading technology from Cisco, EMC, and VMware. Vblock platforms are designed and built to satisfy a broad range of customer implementation requirements. The two data protection options outlined in this paper work with any of the Vblock platform models.
Note: Refer to the VblockTM Infrastructure Platform Architecture Overview for detailed information on the Vblock platform architecture.

2012 VCE Company, LLC. All Rights Reserved.

EMC Avamar
EMC Avamar is a deduplication backup-and-recovery software and system solution. It performs deduplication on the client, which eliminates data from backup streams before it crosses the network. Client deduplication realizes savings on bandwidth, storage, and backup windows. VMwares vStorage API (in vSphere as deployed in Vblock platforms) also provides the ESXi hypervisor architecture.

EMC Avamar virtual machine image proxy


Avamar image proxy servers are a key element of image-level protection. They are delivered as vSphere-deployable Open Virtual Archive (OVA) templates. An OVA template contains a packaged image proxy virtual machine that includes both VMware and Avamar code for the purpose of imagelevel backups and recoveries. This machine is configured with a single CPU and consumes 1 GB of memory. Avamar image proxy machines use the vSphere APIs to mount the virtual machine files that require protection. The administrator has the flexibility to deploy multiple proxies based on ones operating system environment requirements. Multiple proxy deployments allow simultaneous backups and recoveries. During the initial deployment, the administrator assigns separate proxy servers to protect Windows and Linux virtual machines (VM)

EMC Avamar file-level recovery proxy


An Avamar file-level recovery proxy is a virtual machine that allows a single file to be recovered into a virtual machine from a full image backup. Avamar file-level recovery proxies require a virtual machine that is running Windows Server 2003 SP2. EMC recommends one CPU and 1 GB of memory for this VM. The virtual machine leverages the Avamar Virtual File System (AvFS) to create a browseable view within a virtual machines VMDK file for easy, selectable recovery.

VMware vCenter Server


VMware vCenter server provides a scalable and extensible platform that forms the foundation for virtualization management. It centrally manages VMware vSphere environments and allows IT administrators to dramatically improve control over the virtual environment. It manages the ESXi server, virtual machines, and user access, and helps provide Avamar with the information it requires. This information can encompass anything from a simple list of virtual machines within the environment to the information needed to configure virtual machines for backup and recovery.

VMware ESXi
VMware vSphere is the virtualization platform that provides the foundation for the private cloud. The core VMware vSphere components are the VMware ESXi Enterprise hypervisor and VMware vCenter Server for management. The VMware vSphere ESXi hypervisor runs in the Vblock platform.

2012 VCE Company, LLC. All Rights Reserved.

EMC Data Domain


EMC Data Domain is a deduplication storage system for backup and recovery. Scalable Data Domain systems feature high-speed, inline deduplication and network-efficient replication. A single system can reduce storage requirements 10 to 30 times and protect up to 28.5 petabytes of logical capacity. EMC Data Domain provides: Easy integration. Data Domain is qualified with all leading enterprise backup and archiving applications, and integrates easily into existing storage infrastructures. High-speed deduplication. With Data Domains throughput of up to 26.3 TB per hour, administrators can complete more backups faster while putting less pressure on limited backup windows. Network-efficient replication. Data Domain sends only deduplicated and compressed data across the network, requiring a fraction of the bandwidth, time, and cost of traditional replication methods. End-to-end data integrity. Data Domain provides safe and reliable continuous recovery verification, fault detection, and healing.

EMC Data Domain Boost


EMC Data Domain Boost (DD Boost) software extends the optimization capabilities of Data Domain solutions. DD Boost significantly increases performance by distributing parts of the deduplication process to the backup server or application clients, simplifies disaster recovery procedures, and serves as a solid foundation for additional integration between backup applications and Data Domain systems.

2012 VCE Company, LLC. All Rights Reserved.

Architecture overview
The VCE-recommended backup solution includes two options, along with best practices for each: Avamar on Vblock platforms Avamar with Data Domain on Vblock platforms This table defines the two products. Product
EMC Avamar

Definition
1 2 3 1 2 3 4 Avamar is backup and recovery software. Avamar is also a hardware platform where deduplicated backup data is stored. It is client side, also referred to as source-based, deduplication technology. Data Domain requires backup and recovery software. Avamar is the EMC preferred software. Data Domain is a hardware platform that deduplicates and stores backup data. It is a target-based deduplication technology. Certain Data Domain models are suitable for archival backup requirements.

EMC Data Domain

Backup: The Avamar and Data Domain products have different backup advantages. Which of them is best in a particular situation depends on the backup workload. Whereas certain low commonality workloads could bog down an Avamar-only solution, the addition of Data Domain as a target for storing the backups allows for a total solution that takes advantage of each products strengths. Deduplication: In Avamar, the source-based, client-side deduplication of the data is done right in the server whose data is being backed up. Avamar deduplication sends to the Avamar backup storage hardware only variable-length blocks of data that have not previously been backed up. This exponentially reduces the nightly backup load on shared network components within the virtual infrastructure. A server backup runs in minutes instead of hours. Therefore, more backups can be run in parallel and completed within a given backup window. Alternatively, Data Domain target-based deduplication requires 100 percent of the files that are being backed up - to flow through shared network components to the backup hardware, where it is deduplicated in flight. The advantage of Data Domain target-based deduplication is its consistent and predictable ingest rate, regardless of whether the data has high commonality, making it easy to deduplicate, or low commonality, which means there is less to deduplicate. Large databases are the most common backup workload with low-commonality characteristics. The architectures for the two solutions are shown in Figures 1 and 2.

2012 VCE Company, LLC. All Rights Reserved.

Avamar architecture with Vblock platforms


The following figure depicts the high-level architecture, configuration, and integration of Avamar on Vblock platforms.

Figure 1. Vblock Solution with Avamar

In Figure 1, Datacenter 1 has Avamar clients and proxies running on Vblock platforms. During nightly backups the Avamar agents copy the changed variable-length blocks from the Avamar grid and create a virtual full backup from just the changed variable-length blocks. To enable data recovery in the event of a site disaster, all data in the Avamar grid in Datacenter 1 is replicated to an offsite Avamar grid. Not only is transmission fast and efficient, but it is much more secure than shipping physical tapes to an offsite location. The Avamar software is used to schedule the backup jobs and to monitor and report on both backup and Avamar system status. Also shown in Figure 1 is a single-node Avamar solution backing up the remote location. To protect the data in the event of a total loss of the remote office, the single-node Avamar replicates its data to Datacenter 1.

2012 VCE Company, LLC. All Rights Reserved.

10

Avamar and Data Domain architecture with Vblock platforms


The following figure depicts the high-level architecture, configuration, and integration of the combined Avamar and Data Domain on Vblock platforms solution.

Figure 2. Vblock Solution with Avamar and Data Domain

In the combined Avamar with Data Domain solution, the backup jobs with low data commonality (large databases, video files, audio files, and so forth) are routed to the Data Domain device. The metadata for the backup is stored in the Avamar grid. Backups with high-commonality profiles are targeted to the Avamar grid. This combined Avamar and Data Domain solution allows the backup administrator the flexibility to use the best backup target for each backup workload. Certain Data Domain systems are also particularly well suited for multiyear data archives. Using Data Domain for archive is superior to using tape archive because it is more secure and is readily recalled.

2012 VCE Company, LLC. All Rights Reserved.

11

Avamar architecture and best practices


Avamar is backup-and-recovery software and it is also the hardware where the backup data is stored. Used with Vblock platforms, Avamar data deduplication technology seamlessly integrates and provides rapid backup and restoration capabilities. Avamar is integrated with VMware vSphere beginning with version 4.0. VMware has features that protect virtual machine images, called VMware API for Data Protection (VADP). VADP produces indepth details of sizing, deployment, and data flow, providing a total VMware data protection plan that can be used in conjunction with Avamar on Vblock platforms. The two most common recovery requests made to backup administrators are: File-level recovery: File-level recoveries account for the vast majority of user support requests. Common actions that require file-level recovery are individual users deleting files, application recoveries, and batch-process-related erasures. System recovery: Although complete system recovery requests are less frequent than filelevel requests, this capability is vital to the enterprise. Some common causes for full system recovery requests are viral infestation, registry corruption, or unidentifiable unrecoverable issues. The Avamar integration with VMware delivers capabilities for both backup and recovery for either filelevel recovery or system-level recovery. Integration with vStorage API, virtual proxy server pools, and change block tracking allow Avamar to deliver extremely efficient data protection for the Vblock platform.

Integration of EMC Avamar with Vblock platforms


Figure 1, in the Architecture overview section, depicts the high- level architecture of the Vblock solution with Avamar. See the References section to find information on configuration and setup. Avamar backup-and-recovery software provides integrated source/global data deduplication. An Avamar agent on the client system deduplicates the data and then backs it up to an Avamar server, such as an Avamar data store. Unlike traditional backup software, Avamar deduplicates backup data before it is transferred across the network and stored to disk. And, Avamar deduplicates data globally by storing a single instance of each subfile, variable length data string, or data segment that it identifies as unique across all of its protected sites and servers. Thus, Avamar enables rapid, daily full backups even across congested or slow WAN/LAN links and virtual infrastructures. Avamar is used in this solution to not only store the backup data, but also because its software provides integration with vCenter to manage, monitor, and configure the backup of the virtual infrastructure from a single administrative interface. Avamar image proxy machines use the vSphere API to mount the virtual machine files that require protection. The administrator has the flexibility to deploy multiple proxies based on the requirements of the operating system environment. Multiple proxy deployments allow simultaneous backups and recoveries. During the initial deployment, an administrator assigns a separate proxy server to protect either Windows or Linux machines.

2012 VCE Company, LLC. All Rights Reserved.

12

Recovery
Avamar file-level recovery proxy An Avamar file-level recovery proxy is a virtual machine that allows a file, or files, to be recovered into it from a full image backup. Avamar file-level recovery proxies require a virtual machine that is running Windows Server 2003 SP2, and EMC recommends one CPU and 1 GB of memory for this virtual machine. This virtual machine leverages the Avamar Virtual File System (AvFS) to create a browseable view within a virtual machines VMDK file for easy, selectable recovery. Recovery options with Avamar include guest-level recovery and image-level recovery. Guest-level recovery The process of guest-level recovery is the same in this solution for virtual machines as it is for traditional recovery from a backup application. The administrator has the ability to recover directories, files, and applications in the Avamar Administrator GUI. Image-level recovery There are three options for recovering data from an image-based backup: Recover to original Recover to existing Recover to new The administrator may often choose either Recover to original or Recover to existing machine. However, choosing Recover to new gives the administrator the ability to create a new virtual machine on the fly without having to create it with vCenter first. Recovery to a new virtual machine is unique to Avamar, as it incorporates a second process to also protect and store the .VMX files needed to create a new virtual machine container and register it with vSphere. When recovering a virtual machine to its original location, the Avamar Administrator window displays the source just as it appears currently within vCenter, and also shows how it will look after a recovery.

2012 VCE Company, LLC. All Rights Reserved.

13

To recover to a new virtual machine: 1. In the Avamar Administrator GUI select New Virtual Machine (Figure 3). 2. In the Virtual machine name field specify a name for the new machine. 3. From the Host/Cluster list select the folder location within vCenter for the new virtual machine. 4. Click Next.

Figure 3. Choosing a name and location for the new virtual machine

5. Select a Distributed Resource Scheduler (DRS) cluster location for the new virtual machine.

Figure 4. Choosing the DRS cluster for the new virtual machine to be added

2012 VCE Company, LLC. All Rights Reserved.

14

Once a host/cluster is selected in the GUI, Avamar will query vCenter and allow the administrator to select a different VMware data store. The administrator can choose a different destination and a different device for housing the virtual machines data. See Figure 5. This recovery option method permits the administrator to choose a different storage platform and/or drive type (to the current source) for the destination of the new virtual machine.

Figure 5. Selecting the VMware data store where each VMDK should reside

A systems boot drive and its data drive have different performance and storage requirements. This wizard addresses both in one GUI, and it permits a single-step recovery to multiple locations. The wizard also configures the creation of the container for a virtual machine. Avamars approach to protection protects the .VMX file of a virtual machine, the configuration container for a virtual machine. If Avamar did not create the containers as it does, and should a disaster occur, the administrator would have to log on to vCenter and create all the containers needed before conducting any recoveries. This Avamar capability is superior to the traditional approach that relied on detailed tracking via spreadsheet listings of the VM-to-container pairings.

2012 VCE Company, LLC. All Rights Reserved.

15

File-level recovery from an image backup The administrator can do file-level recoveries (FLR) for Windows virtual machines from the imagebased backup. To do this, Avamar leverages the VMware virtual machine tools along with an Avamar Windows FLR proxy. The proxy is a Windows 2003 server provided by the administrator, with code provided by Avamar. No agents are needed within the virtual machine for this recovery type. The key is that Avamar moves no data until there is a need to recover data, and that no other interface nor client-side software is needed for this recovery. The Avamar Administrator console is used to manage and monitor FLR jobs. When backups are selected for recovery, the FLR proxy server reads the VMDK data from the Avamar system and creates a browse tree, as shown in Figure 6 in the Avamar Administrator Backup and Restore window.

Figure 6. File-level recovery: selecting files and directories to restore.

2012 VCE Company, LLC. All Rights Reserved.

16

An administrator can recover the data in place, in order to move the data back to its original location. Or, the administrator can restore to a different location. As a prerequisite, the VMware Tools need to be installed on the virtual machine that the administrator would like to recover to. In the following scenario there is no Avamar agent on the guest level. Therefore, the administrator logs on to that virtual machine and uses the browse tree for recovery. See Figure 7. To recover the data to a different virtual machine: 1. Log on to the virtual machine and use the browse tree for recovery 2. Select the virtual machine you want to recover. 3. Navigate the Browse for Folders or Directories window and select a destination for the data.

Figure 7. File-level recovery - browse for out-of-place recovery

Restore requests pass from the Avamar system, through the Windows FLR proxy, to the machine that is being protected. Recovery speed depends on the FLR proxys ability to read in the data and send it to the machine that is the recovery destination. Consequently, large data recoveries by means of the FLR proxy recovery are unadvisable. An image-level out-of-place recovery is more efficient.

Replication
Replication for Avamar is also managed through the Avamar Administrator console.

2012 VCE Company, LLC. All Rights Reserved.

17

Avamar with Data Domain architecture and best practices


The combination of Avamar and Data Domain permits deduplication algorithms to operate at both the client and the storage system levels. From the Avamar Administrator management console, the administrator can direct a backup data set to target either the Avamar Server or the Data Domain system. Protection of Vblock platforms with the combination of Avamar and Data Domain involves an understanding of the differences and benefits of client-side deduplication and in-line deduplication. Client-side deduplication and in-line deduplication trade-offs A decision whether to deduplicate at the client or at the storage system relates to protecting a growing amount of data within a certain time objective: Deduplication at the client offers the benefits of network traffic reduction and back-end storage optimization. However, this implementation can be less effective for high-change-rate environments, which can negate some of its savings in backup time and network bandwidth. Deduplication at the storage system offers the benefit of massive scale and very rapid ingestion of data. However, this implementation is not optimized for network-bandwidth utilization because the full backup payload must be moved across the network to the storage system before it is deduplicated. Recent hybrid approaches to deduplication have allowed some of the deduplication processes normally run at the storage system to be distributed to a backup server. This can provide some of the network relief offered by client deduplication, while retaining the data ingest and scale attributes of deduplication at the storage system. Today, two challenges that face IT backup administrators are: Deploying two separate solutions to optimize for varying workloads Minimizing administrative costs for management of two solutions separately With the features and implementation details highlighted in the sections below, one can clearly see how the newly introduced integration of Avamar with Data Domain on Vblock platforms addresses these challenges.

Integration of Avamar and Data Domain with Vblock Platforms


Figure 2 in the architecture overview section depicts the high-level architecture of the combined Avamar and Data Domain solution on Vblock platforms. At a high level, starting in Avamar v6.0, the administrator can direct whether specific datasets in an Avamar backup policy will target an Avamar Server or an EMC Data Domain system.

2012 VCE Company, LLC. All Rights Reserved.

18

When an Avamar data store is the backup target, the Avamar client installed on each host works as a typical Avamar client performing client-side deduplication segment which processes and sends capacity-optimized blocks, and any required metadata, over the WAN/LAN to the Avamar server. This dataflow is not a change from the well-known implementation in previous versions of Avamar. When specifying a Data Domain system as the backup target of a particular dataset from within Avamar Administrator, the same Avamar client leverages Data Domain Boost (DD Boost) software to redirect this data directly to a Data Domain system. DD Boost extends the optimization capabilities of Data Domain solutions. It significantly increases performance, by distributing parts of the deduplication process to the backup server, and simplifies disaster recovery procedures. Rather than performing intensive deduplication processing only on the client, DD Boost transfers the source data in an efficient transfer method for processing by the Data Domain system. Besides transferring backup payload data optimally to the Data Domain system, the Avamar client simultaneously sends the relevant metadata it has generated to the Avamar server for storage. This metadata allows the Avamar management system to direct the client in performing restore operations directly from the Data Domain system without going through the Avamar server. This functionality, implemented within the Avamar client software, is the same DD Boost API and technology that are supported on many other Data Domain implementations today.

Recovery
The process of data recovery, whether from an Avamar data store or from a Data Domain system, is completely transparent to the backup administrator. The backup administrator uses the same recovery processes that are native to previous Avamar versions. The Avamar front end automatically retrieves datasets that are stored on Data Domain systems. No special retrieval mechanisms or processes are required.

Replication
As shown in Figure 2 in the architecture section, replication between primary and replica Data Domain systems is also integrated into the Avamar management feature set. This is controlled by the replication policy applied to each dataset in Avamar Administrator. All typical Avamar replication scenarios are supported for datasets targeted to Data Domain. These include: Many-to-one, one-to-many, cascading replication Extension of data retention times Root-to-root replication Like the recovery process, the replication process normally configured within the Data Domain platform is automated within the Avamar framework and is transparent to the backup administrator. This replication functionality requires that a remote Avamar server exists, along with the remote Data Domain system.

2012 VCE Company, LLC. All Rights Reserved.

19

Using Avamar/Data Domain centralized control and management


This section presents two examples that show how some of the processes highlighted in the previous sections are controlled from within the Avamar Administrator GUI: Example One: Configure a Data Domain system within the Avamar Administrator interface Example Two: Specify a Dataset Policy within Avamar

Example One: Configure a Data Domain system within the Avamar Administrator interface
This example shows the procedure for using the Avamar Administrator GUI to configure a DataDomain system for use with SQL database backups. 1. Log on to Avamar Administrator. 2. Access the Avamar Administrator main menu. Here, the administrator can provision either a new or currently deployed Data Domain system within the Avamar environment, in order to specify it as a backup target when backing up policy datasets. 3. Click the Server icon to access the Avamar backend system configuration settings, as shown in Figure 8.

Figure 8: Avamar Administrator Main Menu

2012 VCE Company, LLC. All Rights Reserved.

20

4. Select Server Management. 5. Click the icon in the toolbar (Figure 9) to display the Data Domain system configuration dialog box. Here, we can provision a Data Domain system for use by the Avamar client.
Note: To configure a Data Domain system within an Avamar environment there is no need to launch the Data Domain Enterprise Manager GUI or CLI interface.

Figure 9: Specify a target Data Domain system from within Avamar

2012 VCE Company, LLC. All Rights Reserved.

21

The Add Data Domain System dialog box appears (Figure 10).

Figure 10: Add Data Domain System dialog box System tab

6. Select System (Figure 10) and enter the system name (or IP address) for the Data Domain system to be targeted for backup. 7. Enter the DD Boost User Name. It is used for authentication. It specifies for the Avamar environment the credentials needed to access the Data Domain system and to authenticate the Avamar clients to write backups to the Data Domain backup target. The DD Boost account name is created in the Data Domain Enterprise Manager during the setup of the Data Domain system. For systems that are already implemented and have the DD Boost license installed, this authentication account is configured on the Data Domain. For newly implemented Data Domain systems with a DD Boost license, reference EMC Data Domain documentation for the procedure to configure this account. 8. Complete the Max Streams field. This setting indicates to the Data Domain system the total number of client backup streams launched simultaneously from Avamar clients managed by this Avamar server. This setting is especially important in deployments where the Data Domain system is being targeted by backup applications besides Avamar, such as EMC Networker. This setting assures that Avamar backup streams do not oversubscribe the Data Domain system if other backup jobs are being targeted to it within the same backup window.
2012 VCE Company, LLC. All Rights Reserved.

22

9. Click Okay. 10. Click SNMP (Figure 11). The Add Data Domain System dialog box appears. 11. In the Getter/Setter Port Number field, the default value is usually used. This number tells the Avamar server the port on the Data Domain system from which to receive and on which to set SNMP objects. 12. Next, complete the SNMP Community String field. This indicates to Avamar which community string will allow read/write access to the Data Domain system from an SNMP perspective. 13. Enter the Trap Port Number. This indicates the port on the Avamar server that Data Domain will use to send SNMP traps to the Avamar server. The default number usually does not need to be changed. Refer to the Avamar server SNMP configuration for the proper settings. 14. Click OK.

Figure 11: Add Data Domain System - SNMP Tab

2012 VCE Company, LLC. All Rights Reserved.

23

15. Click Events (Figure 12). This window shows all the events that will be passed to Avamar Administrator from the Data Domain system.

Figure 12: Add Data Domain System - Events Tab

16. To complete the provisioning of a Data Domain system for use by Avamar, verify the entries and click OK.

2012 VCE Company, LLC. All Rights Reserved.

24

Figure 13: Avamar Administrator - Server Management

The process of provisioning a Data Domain system for use with Avamar is easily and intuitively done. Repeat this process for multiple Data Domain systems that may be required for a particular Avamar/Data Domain joint solution. After adding a system, the administrator can return at any time to the Server window (Figure 13) from the main menu for a quick dashboard view of Data Domain system statistics such as capacity, DDOS version, and model number.

Example Two: Specify a dataset policy within the Avamar Administrator interface
This example illustrates the procedure for setting a dataset policy within Avamar. The dataset policy is needed in order to target backups. For this initial environment, a policy dataset for backup of a production SQL database has been created. It is the dataset called DDSQLDataset .
Note: Refer to EMC Avamar Administrator documentation for creating datasets from scratch.

The example re-directs the backups of this dataset from the Avamar Data Store to the Data Domain system provisioned in Example One.
2012 VCE Company, LLC. All Rights Reserved.

25

Use the Avamar Administrator policy configuration feature, as shown in Figure 14, to edit the dataset that is to be retargeted. Click Options on the Edit Dataset window to bring up the configuration settings in the New Dataset dialog box, as shown in Figure 15.

Figure 14: Avamar Administrator Edit Dataset window

2012 VCE Company, LLC. All Rights Reserved.

26

Figure 15: Avamar Administrator - New Dataset dialog box

1. Click the checkbox Use Data Domain system. From the dropdown box, select the Data Domain system target for this dataset. The dropdown list shows all the available Data Domain systems. We have pre-provisioned only one Data Domain system, so there is only one option in the box. If more Data Domain systems were provisioned then multiple selections would appear. 2. Click OK. The SQL databset will be processed by the Avamar Windows SQL plug-in to target its data to the Data Domain system. Upon the next backup policy execution (either manual or scheduled) the SQL dataset will be sent to the Data Domain system for deduplication and storage.

2012 VCE Company, LLC. All Rights Reserved.

27

Conclusion
The Vblock solution with Avamar, and the Vblock solution with Avamar and Data Domain, solve todays backup bottlenecks and other backup issues encountered when performing multiple kinds of enterprise-wide backups with deduplication. With the integration and control of EMC Data Domain systems within the EMC Avamar client on Vblock platforms, the backup administrator can now eliminate separate backup processes and manage enterprise-wide backup workloads associated with each dataset from a single management interface. Furthermore, backups of VMware, desktops and laptops, remote offices, NAS systems, and enterprise applications are all optimized for faster backups, maximum deduplication, and efficient recoveries. VCE offers on Vblock platforms both Avamar and Data Domain because these data targets have different advantages. The combination of the two addresses a broader set of data protection requirements and customer need for choice among them. Using Avamar and Data Domain as described in this white paper is a VCE recommended solution because it simplifies data protection AND it is a critical element for getting the maximum return-oninvestment out of a Vblock platform.

Next Steps
To learn more about this and other solutions, contact a VCE representative or visit www.vce.com.

2012 VCE Company, LLC. All Rights Reserved.

28

References
VCE Vblock Infrastructure Platforms 2010 Vblock Platforms Architecture Overview

EMC
Note: To access this documentation EMC requires that you have registered and have a user id and password. Contact EMC to set up your user id.

EMC Avamar 6.0 Administration Guide Data Domain OS 5.1 Administration Guide

2012 VCE Company, LLC. All Rights Reserved.

29

ABOUT VCE
VCE, the Virtual Computing Environment Company formed by Cisco and EMC with investments from VMware and Intel, accelerates the adoption of converged infrastructure and cloud-based computing models that dramatically reduce the cost of IT while improving time to market for our customers. VCE, through the Vblock platform, delivers the industry's first completely integrated IT offering with end-to-end vendor accountability. VCE's prepackaged solutions are available through an extensive partner network, and cover horizontal applications, vertical industry offerings, and application development environments, allowing customers to focus on business innovation instead of integrating, validating and managing IT infrastructure. For more information, go to www.vce.com.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED "AS IS." VCE MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OR MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.

Copyright 2011 VCE Company, LLC. All rights reserved. Vblock and the VCE logo are registered trademarks or trademarks of VCE Company, LLC, and/or its affiliates in the United States or other countries. All other trademarks used herein are the property of their respective owners.

2012 VCE Company, LLC. All Rights Reserved.