EMC AVAMAR INTEGRATION GUIDE AND DATA DOMAIN 6.0 P/N REV A02

Transcription

1 EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE P/N REV A02 EMC CORPORATION CORPORATE HEADQUARTERS: HOPKINTON, MA

2 Copyright and Trademark Notices Copyright EMC Corporation. All rights reserved. Published September, 2011 EMC believes the information in this publication is accurate as 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 regulatory document for your product line, go to the Technical Documentation and Advisories section on EMC Powerlink. For the most up-to-date listing of EMC product names, see EMC Corporation Trademarks on EMC.com. All other trademarks used herein are the property of their respective owners. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 2

3 TABLE OF CONTENTS Revision History Preface Scope and intended audience Related documentation Avamar documentation Data Domain documentation Product information Avamar Support Your comments Typographic conventions Safety admonitions and notices Introduction How Avamar and Data Domain work together Architecture Backup Restore System maintenance Replication Monitoring and reporting Capabilities and limitations Terms used in this guide Installation System requirements Supported Data Domain environment Supported Avamar clients Replication Licensing Port usage and firewall requirements Internationalization support Installation best practices Capacity considerations Security Data migration EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 3

4 TABLE OF CONTENTS Configuring Backups with Avamar and Data Domain How backups work with Avamar and Data Domain Where backup data is stored How Avamar manages backup data Supported backup types Canceling and deleting backups Managing Data Domain systems Preparing the Data Domain system Adding a Data Domain system Editing a Data Domain system Deleting a Data Domain system Selecting a Data Domain target for backups Selecting a Data Domain target for an on-demand backup Selecting a Data Domain target for a scheduled backup Replication How replication works with Avamar and Data Domain Configuring replication Setting the default Data Domain destination Mapping a domain to a Data Domain system Deleting a domain mapping Monitoring and Reporting Monitoring Data Domain with SNMP Backup and restore monitoring Server monitoring Event monitoring Data Domain capacity monitoring Monitoring capacity in Avamar Administrator Monitoring capacity in Avamar Enterprise Manager Replication monitoring Reports Filtering existing reports Filtering a custom report Troubleshooting Viewing detailed status information for troubleshooting Data Domain status and resolutions Monitoring status details Re-creating the SSH public/private key pair Index EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 4

5 REVISION HISTORY The following table presents the revision history of this document. REV DATE DESCRIPTION A02 September 2011 Added information on support for Data Domain Archiver to the following topics: Capabilities and limitations (page 16) Terms used in this guide (page 18) Supported Data Domain environment (page 21) How replication works with Avamar and Data Domain (page 38) Added port information in the new topic, Port usage and firewall requirements (page 23). Fixed a syntax error in the step to copy the private key in Re-creating the SSH public/private key pair (page 72). A01 April 2011 Initial release of EMC Avamar 6.0. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 5

6 PREFACE Scope and intended audience Scope. This guides describes how to install, configure, administer, and use a Data Domain system as a backup target for Avamar. Intended audience. The information in this publication is primarily intended for system administrators who are responsible for maintaining servers and clients on a network, as well as operators who monitor daily backups and storage devices. Related documentation The following documents provide additional details on how to use Avamar with Data Domain. Avamar documentation Related Avamar documentation includes: EMC Avamar Release Notes EMC Avamar Server Software Installation Guide EMC Avamar Administration Guide EMC Avamar Operational Best Practices EMC Avamar Product Security Guide EMC Avamar for Exchange VSS Guide EMC Avamar for SharePoint VSS Guide EMC Avamar for SQL Server Guide EMC Avamar for Oracle Guide EMC Avamar for VMware Guide EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 6

7 Avamar Support PREFACE Data Domain documentation Related Data Domain documentation includes: DD OS Release Notes DD OS Initial Configuration Guide DD OS Administration Guide DD OS Command Reference DD OS Command Reference Guide Data Domain Hardware Guide The Data Domain installation and setup guides for each of the supported platforms (for example, DD610, DD690, and DD880) Product information For current documentation, release notes, software updates, information about EMC products, licensing, and service, go to the EMC Powerlink website at Avamar Support Before contacting EMC Technical Support, please go to the Avamar Support landing page at and: Refer to the Product Documentation Check the listed Support Topics for: How-to's Troubleshooting Search the Avamar Knowledge Base (KB) for applicable solutions using the convenient search engine: Enter the KB solution number (for example, esgxxxxxx) Enter keywords If none of the previous resources resolve your issue, many issues can be successfully resolved through live interactive chat. You can engage EMC Technical Support using live interactive chat by selecting Additional Resources > Live Chat on the Avamar Support landing page. If more in-depth help is required, or if you have an existing open Service Request (SR), you can submit or review a service request through Powerlink: To review an existing SR, go to and select Support > Request Support > View Service Requests To open a new SR, go to: and select Support > Request Support > Create Service Request EMC recommends that all Avamar systems have ConnectEMC and Home enabled to facilitate the best possible support. Systems with ConnectEMC configured and enabled will be able to automatically generate SRs when appropriate and as noted in this guide. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 7

8 Safety admonitions and notices PREFACE Your comments Your suggestions will help us continue to improve the accuracy, organization, and overall quality of our documentation. You may comments to: Please include the following information: Product name and version Document name, part number, and revision (for example, A01) Page numbers Other details that will help us address the documentation issue Typographic conventions The following table provides examples of standard typographic styles used in this guide to convey various kinds of information. EXAMPLE Click OK. or Select File > Close. Type: cd /tmp --logfile=file Installation Complete. DESCRIPTION Bold text denotes actual buttons, commands, menus, and options that initiate action. Sequential commands are separated by a greaterthan (>) character. For example, the second example instructs you to select the Close command from the File menu. Bold fixed-width text denotes shell commands that must be entered exactly as they appear. All caps text often denotes a placeholder (token) for an actual value that must be supplied by the user. In this example, FILE would be an actual filename. Regular (not bold) fixed-width text denotes command shell messages, code, and file contents. Safety admonitions and notices The following safety admonitions and notices appear in this guide: Danger safety admonitions indicate a hazardous situation which, if not avoided, will result in death or serious injury. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 8

9 PREFACE Warning safety admonitions indicate a hazardous situation which, if not avoided, could result in death or serious injury. Caution safety admonitions indicate a hazardous situation which, if not avoided, could result in minor or moderate injury. IMPORTANT: Important notices contain information essential to software or hardware operation. NOTE: Notes contain information intended to clarify a topic or procedure. Notes never contain information that will cause a failure if ignored. TIP: Tips present optional information intended to improve your productivity or otherwise enhance your experience with the product. Tips never contain information that will cause a failure if ignored. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 9

10 INTRODUCTION You can store EMC Avamar backups on one or more Data Domain systems, and then seamlessly restore data from the backups when necessary. The following sections provide an introduction to using the Avamar product with Data Domain: How Avamar and Data Domain work together (page 10) Terms used in this guide (page 18) How Avamar and Data Domain work together Avamar clients that support backup and restore to and from Data Domain include: Microsoft Exchange VSS Microsoft SQL Server Microsoft SharePoint VSS Oracle VMware image backup and restore The storage and retrieval of backups on a Data Domain system may be faster than on an Avamar server in an environment with these products, especially if there is a large, active database in the environment. A Data Domain system can manage large datasets and high change rates of data within a large dataset more effectively than an Avamar server. A dataset of greater than 5 TB is considered a large dataset, and a daily change rate of more than 5 percent is considered a high change rate. Architecture Avamar clients use the DD Boost API to access a Data Domain system. The DD Boost API is installed automatically on the client computer when you install the Avamar client. The ddrmaint utility on the utility node of a multi-node server (or the single node of a single-node server) implements all required operations on the Data Domain system on behalf of the Avamar server. It is not installed on the data nodes of the Avamar server. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 10

11 How Avamar and Data Domain work together INTRODUCTION The ddrmaint utility also uses the DD Boost API to connect to a Data Domain system. The DD Boost API is installed with the ddrmaint utility automatically when you install Avamar. Basic architecture. The following figure illustrates a basic Avamar environment with a Microsoft Exchange server that sends backup data to a Data Domain system. NOTE: The connection between the Avamar client and the Data Domain system is not encrypted. The DD Boost library does not support data encryption between the client and the Data Domain system. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 11

12 How Avamar and Data Domain work together INTRODUCTION Mixed client environment. It is likely, however, that there are other Avamar clients in the environment, some of which are sending backups to the Data Domain system, and some of which are sending backups to the Avamar server. In the following figure, Avamar client 1 sends backups to the Avamar server, and Avamar client 2 sends backups to the Data Domain system. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 12

13 How Avamar and Data Domain work together INTRODUCTION Multiple Data Domain systems. To segregate data, you also can use multiple Data Domain systems with a single Avamar server. In the following figure, Avamar client 1 sends backups to Data Domain system 1, and Avamar client 2 sends backups to Data Domain system 2. Shared Data Domain system. Avamar can share a Data Domain system with other backup solutions, as shown in the following figure. The other backup solution can be any other backup product that uses a Data Domain system, or it can be another Avamar server. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 13

14 How Avamar and Data Domain work together INTRODUCTION The architecture of an Avamar environment with Data Domain is flexible and can combine several different strategies. For example, there can be multiple Avamar clients that send backups to a single Data Domain system that is shared with another backup server, while other Avamar clients send backups to the Avamar server. Backup During a backup, the Avamar server sends a backup request to the Avamar client. If the backup request includes the option to use a Data Domain system as the target, then the Avamar client sends the backup data (for files that are larger than 10 MB) directly to the Data Domain system. In other words, the backup data is not staged on the Avamar server before it is sent to the Data Domain system. Metadata for the backup is sent from the Avamar client to the Avamar server. This enables Avamar to manage the backup even though the data is stored on a Data Domain system. You can perform both full backups and incremental backups (for those clients that support incremental backups) when a Data Domain system is the backup target. If you delete a backup in Avamar, it is deleted from the Data Domain system. If you cancel a backup while it is in progress, then Avamar deletes the backup data that was written to the Data Domain system during the next cycle of the Avamar Garbage Collection (GC) process. Restore Restore of an Avamar backup from a Data Domain system is seamless. When a restore is initiated from Avamar, the restore data is streamed directly from the Data Domain system back to the Avamar client. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 14

15 How Avamar and Data Domain work together INTRODUCTION When you select a backup to restore, you can identify whether a backup is located on the Avamar server or on a Data Domain system by viewing the Server column on the Select for Restore tab of the Backup and Restore window, as shown in the following example. If replication is enabled, you can restore seamlessly from a replicated Data Domain system, the same way that you would if the backup data were on a replicated Avamar server. System maintenance Avamar system maintenance operations include backup data that is stored on configured Data Domain systems. Avamar performs the system maintenance operations for backup data on the Data Domain system. Data Domain maintenance operations may also run on the Data Domain system. However, these operations do not replace Avamar maintenance operations. HFS check. When HFS check runs on the Avamar server, it also verifies backup data on the Data Domain system. However, the integrity check on the Data Domain system is limited to file existence, file size, and file modification time. Checkpoints. When you perform a checkpoint on the Avamar server, then the checkpoint includes Avamar data on the Data Domain system. If a checkpoint succeeds on the Avamar server but fails for Avamar data on a configured Data Domain system, then the checkpoint is considered a failed checkpoint. All checkpoint names on a Data Domain system match the checkpoint names on the Avamar server. Rollbacks. When you perform a rollback on the Avamar server, then a rollback is performed on Avamar data on the Data Domain system. If a rollback succeeds on the Avamar server but fails for Avamar data on a configured Data Domain system, then the rollback is considered a failed rollback. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 15

16 Capabilities and limitations INTRODUCTION Garbage Collection. When Garbage Collection runs on the Avamar server, it also deletes expired Avamar backup data on the Data Domain system. Garbage Collection may perform other cleanup operations on the Data Domain system as required, such as removing deleted checkpoints and backups, and removing incomplete, aborted, and failed backups. Space from data deleted through Avamar Garbage Collection is reclaimed on the Data Domain system when the Data Domain file system cleaning operation. Secure deletion. Manual secure deletion is possible on both the Avamar and Data Domain servers, but data shredding is not currently supported with this solution, even though Data Domain has a data shredding feature. The EMC Avamar Product Security Guide provides details on how to securely delete backups from the Avamar server. Replication The Avamar replication feature transfers data from a source Avamar server to a destination Avamar server. If you use a Data Domain system as a backup target for Avamar, then the replication process also transfers Avamar data from the source Data Domain system to a destination Data Domain system. Replication (page 38) provides details, including supported architectures and configuration instructions. Monitoring and reporting Avamar can collect and display data for health monitoring, system alerts, and capacity reporting on a configured Data Domain system using SNMP. This enables you to monitor Data Domain activities, events, capacity, and system status in the same way that you monitor activities, events, capacity, and system status for the Avamar server. You also can run reports to analyze the system. Monitoring and Reporting (page 46) provides details. Capabilities and limitations Consider the following capabilities and limitations when you use a Data Domain system to store Avamar backups. Mixed backups are not supported. The full backup for a client and all subsequent incremental and differential backups must be stored on either the Avamar server or a single Data Domain system. Avamar does not support the following scenarios: Full backup on a Data Domain system and incremental or differential backups on the Avamar server Full backup on the Avamar server and incremental or differential backups on a Data Domain system Full backup on one Data Domain system and incremental or differential backups on another Data Domain system EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 16

17 Capabilities and limitations INTRODUCTION As a result, if you change the device on which backups for a client are stored, then you must perform a full backup to the new device before any further incremental or differential backups. There are two exceptions to the requirement for storing all backup types on a single server: If you use the Avamar for SQL Server Client and you perform a tail-log backup during a restore, then the tail-log backup is always stored on the Avamar server. If you use the Avamar Exchange VSS Client, then the Microsoft Exchange log files are always backed up to the Avamar server. In addition, files in Exchange VSS backups that are less than 10 MB are always stored on the Avamar server, regardless of the selected backup target. Rollbacks to restore a configured Data Domain system require manual addition of the SSH key and trap host. If you roll back to a checkpoint that contains a configured Data Domain system that you deleted from the configuration after the checkpoint, then the Data Domain system is restored to the configuration. If you do not want the Data Domain system, then delete it from the configuration after the rollback completes. However, if you want to restore the Data Domain system to the configuration, then you must re-add the SSH key and trap host to the Data Domain system, as these values were deleted when you deleted the Data Domain system but cannot be restored on the Data Domain system during a rollback of the Avamar server. To restore these values, open the Edit Data Domain System dialog box in Avamar Administrator and click the Re-add SSH Key and Re-add Trap Host buttons. Tail-log backup is not supported when restoring SQL Server data from the target archive or sealed archive tiers on a Data Domain Archiver. If you are restoring SQL Server data from either the target archive or sealed archive tiers on a Data Domain Archiver, then you must clear the Log Tail backup checkbox to disable tail-log backups. Otherwise, the restore fails. Tail-log backups are supported only when restoring data from the active tier of a Data Domain system. Level 1 Oracle backups to a Data Domain Archiver may time out. When performing a Level 1 backup from an Oracle client to a Data Domain Archiver, the backup may time out and fail in the process of creating a snapview. To work around this issue, increase the timeout limit by adding the following flag to the avoracle.cmd file: --[avoracle]subprocesstimeoutsecs=n where N is the number of seconds before timeout occurs. The default value is 150. A value of 200 or greater is recommended. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 17

18 Terms used in this guide INTRODUCTION Terms used in this guide The following terms related to Avamar and Data Domain are used in this guide. Avamar Administrator Avamar client Avamar server backup checkpoint client Data Domain Archiver Data Domain system dataset Avamar Administrator is a graphical management console software application that is used to remotely administer an Avamar system from a supported Windows client computer. A computer or workstation running Avamar software and accessing the Avamar server over a network connection. Avamar client software consists of a client agent and one or more plug-ins. The server component of the Avamar client/server system. Avamar server is a fault-tolerant, high-availability system that efficiently stores the backups from all protected clients. It also provides essential processes and services required for data restores, client access, and remote system administration. Avamar server runs as a distributed application across multiple networked storage nodes. A point-in-time copy of client data that can be restored as individual files, selected directories, or as entire filesystems. Although more efficient than a conventional incremental backup, a backup is always a full, stand-alone copy of client data that can be restored immediately from an Avamar server. A system-wide backup taken for the express purpose of assisting with disaster recovery of the Avamar server. A computer or workstation that runs Avamar software and accesses the Avamar server over a network connection. Avamar client software consists of a client agent and one or more plug-ins. A specialized Data Domain system with an internal tiering approach designed to enable cost-effective long-term retention of data on deduplicated disk. Data is initially stored in the active tier, which operates similarly to a standard Data Domain system for backup and recovery. Based on user-defined policies, the aged data is then moved to an archive storage tier that is optimized for longterm data retention. Disk-based deduplication appliances and gateways that provide data protection and disaster recovery (DR) in the enterprise environment. A policy that defines a set of files, directories, and filesystems for each supported platform that are included or excluded in backups across a group of clients. A dataset is a persistent and reusable Avamar policy that can be named and attached to multiple groups. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 18

19 Terms used in this guide INTRODUCTION DD Boost DDOS ddrmaint utility Garbage Collection (GC) HFS HFS check Management Console Server (MCS) plug-in policy replication restore DD Boost is the API that Avamar clients use to access a Data Domain system. The DD Boost API is installed automatically on the client computer when you install the Avamar client. It is also installed automatically on the Avamar server when you install Avamar. Data Domain Operating System (DDOS) is the internal operating system on the Data Domain system. The DDOS provides both a command line interface (CLI) for performing all system operations and the Enterprise Manager (a graphical user interface, or GUI) for some configuration operations, management, and monitoring. Installed on the utility node of a multi-node server (or the single node of a single-node server), this utility implements all required operations on the Data Domain system on behalf of the Avamar server. It is not installed on the data nodes of the Avamar server. The ddrmaint utility also uses the DD Boost to connect to a Data Domain system. The DD Boost is installed with the ddrmaint utility automatically when you install Avamar. A daily Avamar maintenance process that recovers storage space from deleted or expired backups. Hash Filesystem. The content addressed storage area inside the Avamar server used to store client backups. An Avamar Hash Filesystem check (HFS check) is an internal operation that validates the integrity of a specific checkpoint. Once a checkpoint has passed an HFS check, it can be considered reliable enough to be used for a server rollback. The MCS provides centralized administration (scheduling, monitoring, and management) for the Avamar server. The MCS also runs the server-side processes used by the Avamar Administrator graphical management console. An Avamar plug-in is a software process that recognizes a particular kind of data resident on that client. A set of defined rules for client backups that can be named and applied to multiple groups. Groups have dataset, schedule and retention policies. Replication is an optional feature that allows one Avamar server to store a read-only copy of its data on another Avamar server in order to support future disaster recovery of that server. File or object restore. An operation that retrieves one or more filesystems, directories, files, or data objects from an existing backup and writes it to a designated location. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 19

20 Terms used in this guide INTRODUCTION retention rollback SNMP The ability to control the length of time backups will be kept in an Avamar server before automated deletion. Retention can be set to permanent for backups that should not be deleted from an Avamar server. Retention is a persistent and reusable Avamar policy that can be named and attached to multiple groups. The process of restoring the Avamar server to a known good state using data stored in a validated checkpoint. Simple Network Management Protocol (SNMP) is a UDPbased network protocol. It is used mostly in network management systems to monitor network-attached devices for conditions that warrant administrative attention. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 20

21 INSTALLATION The following sections describe the system requirements and installation best practices for a Data Domain system with Avamar: System requirements (page 21) Installation best practices (page 25) System requirements Consider the system requirements in the following sections for an environment that will include one or more Data Domain systems as backup targets for Avamar. Supported Data Domain environment The requirements for the Data Domain environment are listed in the following table. DATA DOMAIN FEATURE OR SPECIFICATION Data Domain Operating System (DDOS) Data Domain device type REQUIREMENT FOR USE WITH AVAMAR Version 4.9.x, with a minimum version of Version x, with a minimum version of Any Data Domain system (except for a Data Domain Global Deduplication Array) that supports the execution of the required DDOS version. This includes the Data Domain Archiver. Avamar sends backup data to the active tier on a Data Domain Archiver, and can restore files from either the active tier or an archive tier. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 21

22 System requirements INSTALLATION DD Boost DATA DOMAIN FEATURE OR SPECIFICATION Data Domain File System (DDFS) REQUIREMENT FOR USE WITH AVAMAR You must enable DD Boost using the Data Domain CLI or the web-based Data Domain Enterprise Manager. You also must create DD Boost account and password using the Data Domain CLI. The account must have admin privileges. If you have already created an account and password, then ensure that you have the account name and password available when you add the Data Domain system to the Avamar configuration. Preparing the Data Domain system (page 29) provides instructions on enabling DD Boost and creating a DD Boost account. Enable DDFS using either the Data Domain Enterprise Manager or CLI. Supported Avamar clients The following Avamar clients support the use of a Data Domain system as a backup target: Microsoft Exchange VSS Microsoft SQL Server Microsoft SharePoint VSS Oracle VMware image backup and restore Details on supported operating systems for each client are available in the EMC Avamar Compatibility and Interoperability Matrix on the EMC Powerlink website. Replication If you use Avamar replication and the source Avamar server uses a Data Domain system as a backup target, then there must be a separate Data Domain system configured with the destination Avamar server. Avamar automatically replicates the data on the source Data Domain system to the destination Data Domain system. If there is no destination Data Domain system configured with the destination Avamar server, then replication fails for backups that are stored on the source Data Domain system. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 22

23 System requirements INSTALLATION Licensing Ensure that the environment meets the following licensing requirements. PRODUCT Avamar Data Domain LICENSING REQUIREMENT Standard Avamar licensing requirements apply, as discussed in the following documents: EMC Avamar Server Software Installation Guide EMC Avamar Data Store System Installation Guide Avamar Virtual Edition System Installation Guide The DD Boost license must be installed on the Data Domain system. For replication from one Data Domain system to another, a replication license must be installed. Port usage and firewall requirements To enable communication between the Avamar and the Data Domain systems, the following ports need to be opened if firewalls are installed. PORT/ PROTOCOL PURPOSE SOURCE DESTINATION REMARKS 7/ECHO Java-related for Data Domain system communication Only required if Data Domain is used to store Avamar client backups. 22/TCP SSH Utility node and trusted administrator hosts All nodes Required EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 23

24 System requirements INSTALLATION PORT/ PROTOCOL PURPOSE SOURCE DESTINATION REMARKS 80/TCP HTTP User-defined web client hosts or reverse proxy web server Utility node Required. Permits access from all Avamar clients or only from reverse proxy web server (recommended). Avamar Downloader Service / web server / AvInstaller HTTP communication User-defined Microsoft Windows host that runs the Avamar Downloader Service Utility node or single-node server Required. Permits access to and from specific hosts. Web browser / web server / AvInstaller HTTP communication User-defined host with a web browser Utility node or single-node server Required. Permits access to and from specific hosts. Avamar client web browser UI User-defined client with a web browser Utility node or single-node server Required. Permits access to and from Avamar client web UI. 111/TCP RPC protocol Avamar client or server 131 Related to the network environment Data Domain system or Data Domain Archiver Only required if Data Domain is used to store Avamar client backups. Only required if Data Domain is used to store Avamar client backups. 2049/TCP Collection of Data Domain system information Data Domain system Utility node Only required if Data Domain is used to store Avamar client backups. The port is used by Avamar to collect Data Domain system information by using the SNMP protocol. NFS, incoming port to the Data Domain system or Data Domain Archiver Avamar client or server Data Domain system or Data Domain Archiver Only required if Data Domain is used to store Avamar client backups. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 24

25 Installation best practices INSTALLATION PORT/ PROTOCOL PURPOSE SOURCE DESTINATION REMARKS 2052/TCP Incoming port to Data Domain Archiver Avamar client or server Data Domain Archiver Only required if Data Domain Archiver is used to store Avamar client backups. 3008/TCP Incoming port to Data Domain Archiver Avamar client or server Data Domain Archiver Only required if Data Domain Archiver is used to store Avamar client backups. Internationalization support The same filename lengths and character sets are supported when you use either a Data Domain system or an Avamar server to store Avamar backups. The EMC Avamar Release Notes provide details on international language support in Avamar. Installation best practices Review the following best practices for installing and configuring a Data Domain system with Avamar. Capacity considerations Carefully assess your backup storage needs when evaluating how much data to store on the Data Domain system and the Avamar server. Include estimates from data that is sent to the Data Domain system from other servers, if any, and review the capacity management information in the EMC Avamar Administration Guide. If the Data Domain system reaches its maximum storage capacity, then no further backups to the Data Domain system occur until additional capacity is added or old backups are deleted. Data Domain capacity monitoring (page 53) provides details on how to monitor capacity. Security The following topics provide details on security in an Avamar environment with Data Domain. Encryption The connection between the Avamar client and the Data Domain system is not encrypted. The DD Boost library does not support data encryption between the client and the Data Domain system. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 25

26 Client authentication Installation best practices INSTALLATION The Avamar client uses the credentials for the Data Domain system that you specify on the Avamar server when you add the Data Domain system to the configuration in Avamar Administrator, as discussed in Adding a Data Domain system (page 30). The credentials are encrypted and stored on the Avamar server. User access Use caution when granting users access to the Data Domain system. A user should not be able to directly access the Data Domain system and manually delete data. In addition, use caution when granting users access to the Avamar server. The ddrmaint utility is not intended to be invoked from the command line by users. Data migration If you store backup data on the Avamar server and you add a Data Domain system to the environment, you cannot migrate backup data directly from the Avamar server to the Data Domain system. To start using the Data Domain system as the backup target for the Avamar client instead, edit the dataset to use the Data Domain system, and start performing backups to the Data Domain system. A full backup is required when you change the backup target to the Data Domain system. After you successfully perform a backup to the Data Domain system, you can delete the earlier backups from the Avamar server. The EMC Avamar Administration Guide provides details on how to delete backups. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 26

27 CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN The following sections describe how to configure Avamar to use a Data Domain system as a backup target: How backups work with Avamar and Data Domain (page 27) Managing Data Domain systems (page 29) Selecting a Data Domain target for backups (page 35) How backups work with Avamar and Data Domain During a backup, the Avamar server sends a backup request to the Avamar client. If the backup request includes the option to use a Data Domain system as the target, then the Avamar client sends the backup data directly to the Data Domain system. In other words, the backup data is not staged on the Avamar server before it is sent to the Data Domain system. The following topics provide additional details on how backups work with Avamar and Data Domain. Where backup data is stored All data for a backup is stored under a single dedicated Logical Storage Unit (LSU) on a single Data Domain system. The LSU for an Avamar server is named avamar- DPNID, where DPNID is a unique identifier for the Avamar server. NOTE: IN DDOS 5.0.x and later, LSU is referred to as MTree. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 27

28 How Avamar manages backup data How backups work with Avamar and Data Domain CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN During a backup, metadata for the backup is sent from the Avamar client to the Avamar server. This enables Avamar to manage the backup even though the data is stored on a Data Domain system. The original path and filename for a file is not stored on the Data Domain system. Instead, a unique filename is used on the Data Domain system. Supported backup types You can perform full backups, incremental backups, differential backups, and VMware backups with change-block tracking enabled (for those clients that support those types of backups) when a Data Domain system is the backup target. However, the full backup for a client and all subsequent incremental and differential backups must be stored on either the Avamar server or a single Data Domain system. Avamar does not support the following scenarios: Full backup on a Data Domain system and incremental or differential backups on the Avamar server Full backup on the Avamar server and incremental or differential backups on a Data Domain system Full backup on one Data Domain system and incremental or differential backups on another Data Domain system As a result, if you change the device on which backups for a client are stored, then you must perform a full backup before any further incremental or differential backups. There are two exceptions to the requirement for storing all backup types on a single server: If you use the Avamar for SQL Server Client and you perform a tail-log backup during a restore, then the tail-log backup is always stored on the Avamar server. If you use the Avamar Exchange VSS Client, then the Microsoft Exchange log files are always backed up to the Avamar server. In addition, files in Exchange VSS backups that are less than 10 MB are always stored on the Avamar server, regardless of the selected backup target. Canceling and deleting backups If you cancel a backup while it is in progress, then Avamar deletes the backup data that was written to the Data Domain system during the next cycle of the Avamar GC process. If you delete a backup in Avamar, it is deleted from the Data Domain system during the next cycle of the Avamar GC process. The EMC Avamar Administration Guide provides instructions on how to cancel or delete a backup. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 28

29 Managing Data Domain systems Managing Data Domain systems CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN The following sections provide details on how to manage Data Domain systems in the Avamar configuration: Preparing the Data Domain system (page 29) Adding a Data Domain system (page 30) Editing a Data Domain system (page 33) Deleting a Data Domain system (page 34) Preparing the Data Domain system Before you can add a Data Domain system to the Avamar configuration, you must prepare the Data Domain system by enabling DD Boost and creating a DD Boost user account for Avamar to use to access the Data Domain system for backups, restores, and replication, if applicable. To prepare the Data Domain system: 1. Enable DD Boost on the Data Domain system by logging in to the Data Domain CLI as an administrative user and typing the following command: DDOS VERSION 4.9.x x COMMAND ost enable ddboost enable 2. Create a DD Boost account and password: (a) Log in to the Data Domain CLI as an administrative user. (b) Create the user account with admin privileges by typing the following command: user add USER priv admin where USER is the username for the new account. (c) Set the new account as the DD Boost user by typing the following command: DDOS VERSION 4.9.x x COMMAND ost set user-name USER ddboost set user-name USER where USER is the username for the account. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 29

30 Managing Data Domain systems CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN (d) Disable and then reenable DD Boost to allow the changes to take effect by typing the following commands: DDOS VERSION 4.9.x x COMMANDS ost disable ost enable ddboost disable ddboost enable Adding a Data Domain system When you add a Data Domain system, the process creates a Logical Storage Unit (LSU) on the Data Domain system for an Avamar server. The LSU refers to the directory created within the DD Boost path. To add a Data Domain system to the Avamar configuration: 1. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 2. Click the Server Management tab. 3. Select Actions > Add Data Domain System. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 30

31 The Add Data Domain System dialog box appears. Managing Data Domain systems CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN 4. On the System tab, complete the settings as described in the following table. SETTING Data Domain System Name DDBoost User Name Password Verify Password DESCRIPTION Fully qualified domain name of the Data Domain system to add. NOTE: Do not use an IP address or a secondary hostname that associates with alternative or local IP interfaces. It may limit the ability of Avamar to route optimized deduplication traffic. Username of the DD Boost account that Avamar should use to access the Data Domain system for backups, restores, and replication, if applicable. Password for the account that Avamar should use to access the Data Domain system for backups, restores, and replication, if applicable. Verification of the password. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 31

32 Managing Data Domain systems CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN SETTING Max Streams Use system as default replication storage DESCRIPTION Maximum number of Data Domain system streams that Avamar can use at any one time to perform backups and restores. Consider both the maximum number of streams that the Data Domain system supports, as well as whether other applications are using streams to send data to and receive data from the Data Domain system. NOTE: If the maximum number of streams is reached, then any additional backup or restore requests are queued until one or more streams become available. NOTE: Avamar uses multiple streams for backups to and restores from Data Domain for Oracle. Multiple streams to and from a Data Domain system are not supported for Microsoft Exchange VSS, Microsoft SharePoint VSS, Microsoft SQL Server, and VMware image backups. If replication is used, whether the Data Domain system is the default destination to which Avamar replicates data when a destination Data Domain system is not identified. Replication (page 38) provides details on configuring replication. 5. Click the SNMP tab. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 32

33 6. On the SNMP tab, verify the SNMP configuration: Managing Data Domain systems CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN The Getter/Setter Port Number text box lists the port on the Data Domain system from which to receive and on which to set SNMP objects. You should not need to change the default value of 161. The SNMP Community String text box lists the community string for Avamar to have read/write access to the Data Domain system. If necessary, you can edit the community string. The Trap Port Number text box lists the port on the Avamar server to which traps are sent. The default value is 163. SNMP configuration enables Avamar to collect and display data for health monitoring, system alerts, and capacity reporting. 7. Click OK. Editing a Data Domain system To edit the configuration for a Data Domain system that you are using as a target for Avamar backups: 1. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 2. Click the Server Management tab. 3. Select the Data Domain system to edit. 4. Select Actions > Edit Data Domain System. The Edit Data Domain System dialog box appears. 5. Edit the settings for the Data Domain system as necessary. Adding a Data Domain system (page 30) provides details on each setting in the dialog box. NOTE: If the Re-add SSH Key and Re-add Trap Host buttons are enabled, then click the buttons to restore the SSH key and trap host values on the Data Domain system. When these buttons are enabled, then the configuration on the Avamar server is not synchronized with the configuration on the Data Domain system. Clicking the buttons restores the values to the Data Domain system to ensure synchronization. 6. Click OK. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 33

34 Deleting a Data Domain system Managing Data Domain systems CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN You can delete a Data Domain system from the Avamar configuration if the Data Domain system is online and if there are multiple Data Domain systems configured on the Avamar server. If you are deleting the only Data Domain system configured on the Avamar server, or if the Data Domain system is offline, then advanced service is required. Contact your EMC sales representative to purchase this service. To delete a Data Domain system from the Avamar configuration: 1. Ensure that no backups are present on the Data Domain system: Delete each backup for all clients that use the Data Domain system as a backup target. Ensure that all backups on the Data Domain system are expired and deleted through the Avamar GC process. Ensure that there are no checkpoints for the Avamar server with backups on the Data Domain system. There are two ways to do this: Wait for all checkpoints that contain backups for the Data Domain system to expire. Perform and validate a new checkpoint after all backups to the Data Domain system are deleted, and then delete all other checkpoints. 2. Ensure that the Data Domain system is not designated as the default replication storage system. Setting the default Data Domain destination (page 43) provides details on designating a default replication storage system. 3. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 4. Click the Server Management tab. 5. Select the Data Domain system to delete. 6. Select Actions > Delete Data Domain System. A confirmation message appears. 7. Click OK. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 34

35 Selecting a Data Domain target for backups Selecting a Data Domain target for backups CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN The following topics provide details on how to select a Data Domain system as an Avamar backup target: Selecting a Data Domain target for an on-demand backup (page 35) Selecting a Data Domain target for a scheduled backup (page 37) Selecting a Data Domain target for an on-demand backup To select a Data Domain system as the target for an on-demand backup: 1. In Avamar Administrator, click the Backup & Restore launcher button. The Backup and Restore window appears. 2. Browse the tree of domains and clients in the left pane, and select a client. 3. On the Select for Backup tab, select the data to back up. 4. Select Actions > Backup Now. The On Demand Backup Options dialog box appears. 5. Review and select the backup settings, including the client plug-in, retention period, and encryption method. 6. Click More Options. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 35

36 Selecting a Data Domain target for backups CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN The Backup Command Line Options dialog box appears, as shown in the following example for a SQL Server plug-in. 7. Select Use Data Domain system, and then select the Data Domain system to use from the list. 8. Specify other backup settings on the Backup Command Line Options dialog box as necessary. 9. Click OK to return to the On Demand Backup Options dialog box. 10. Click OK again. The On Demand Backup Options dialog box closes and the following status message appears: Backup initiated. 11. Click OK. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 36

37 Selecting a Data Domain target for backups CONFIGURING BACKUPS WITH AVAMAR AND DATA DOMAIN Selecting a Data Domain target for a scheduled backup To perform backups on a regular schedule, you create a dataset and create a group. When you create the group, you assign the dataset to the group. To select a Data Domain target for backups that occur on a regular schedule, select the Data Domain system on the Options tab for the dataset, as shown in the following example for a VMware Image Backup plug-in. The EMC Avamar Administration Guide provides details on how to create a dataset. The Avamar client guides provide details on how to perform backups on a regular schedule. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 37

38 REPLICATION The following sections describe the replication process when you use a Data Domain system as a backup target for Avamar: How replication works with Avamar and Data Domain (page 38) Configuring replication (page 42) How replication works with Avamar and Data Domain The Avamar replication feature transfers data from a source Avamar server to a destination Avamar server. If you use a Data Domain system as a backup target for Avamar, then the replication process also transfers Avamar data from the source Data Domain system to a destination Data Domain system, as shown in the following figure. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 38

39 How replication works with Avamar and Data Domain REPLICATION If a Data Domain system is configured with a source Avamar server, then there must be a corresponding Data Domain system configured with a destination server. If there is no destination Data Domain system configured with the destination Avamar server, then replication fails for backups that are stored on the source Data Domain system. Replication control belongs to Avamar. Avamar controls the replication of Avamar data from the source Data Domain system to the destination Data Domain system. The Data Domain replication feature is not used. As a result, configuration and monitoring of the replication process occurs on the Avamar server, and there is no way to track the replication through Data Domain administration tools. A Data Domain replication license is required to enable the copying of data from one system to another. Replication is a direct copy. Avamar replicates the data directly from one Data Domain system to another. In other words, the data is not copied from the source Data Domain system to the Avamar server before it replicates to the destination Data Domain system. Replication occurs on the Avamar replication schedule. The replication of Avamar data on a Data Domain system occurs when data replicates from the source Avamar server to the destination Avamar server according to the schedule defined on the source Avamar server. You cannot schedule replication of data on the Data Domain system separately from the replication of the data on the Avamar server. Replication is supported in multiple environments. If there is more than one Data Domain system configured with the source Avamar server, then you can use either a single destination Data Domain system or multiple destination systems. Also, if there is a single Data Domain system configured with the source Avamar server, then you can use either a single destination Data Domain system or multiple destination systems. Finally, you can replicate from a standard Data Domain system to a Data Domain Archiver. The reverse is also true. If the replication source is a Data Domain Archiver, then the replicated data can be on the active tier, an target archive tier, or a sealed archive tier. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 39

40 How replication works with Avamar and Data Domain REPLICATION The following figure illustrates an environment where there are multiple Data Domain systems configured with the source Avamar system, all of which replicate to a single destination Data Domain system. NOTE: The capacity of the destination Data Domain system must be able to accommodate the replicated data from both source Data Domain systems. Use caution when planning the architecture of such an environment. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 40

41 How replication works with Avamar and Data Domain REPLICATION Alternatively, there can be multiple destination Data Domain systems, as shown in the following figure. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 41

42 Configuring replication REPLICATION You also can replicate data from a single source Data Domain system to multiple destination Data Domain systems, as shown in the following figure. If there are multiple destination Data Domain systems, you can control which system receives the data that replicates from the source Data Domain system by mapping a domain on the source Avamar server to a destination Data Domain system. Mapping a domain to a Data Domain system (page 43) provides details. Configuring replication To configure replication when you use a Data Domain system as a backup target for Avamar: 1. Configure replication from the source Avamar server to the destination Avamar server by using either Avamar Administrator or Avamar Enterprise Manager: On the Services Administration tab in the Administration window of Avamar Administrator, update the properties for the Replication cron job entry to include information about the destination server, backups to replicate, schedule, and other replication settings. On the Replicator Setup page in Avamar Enterprise Manager, click the link for the source Avamar server, and then specify information about the destination server, backups to replicate, schedule, and other replication settings. The EMC Avamar Administration Guide provides detailed steps to configure replication in either Avamar Administrator or Avamar Enterprise Manager. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 42

43 Configuring replication REPLICATION 2. If there is more than one destination Data Domain system, specify which Data Domain system is the default destination. Setting the default Data Domain destination (page 43) provides detailed steps. 3. If there is more than one destination Data Domain system, map the domains on the source Avamar server to a destination Data Domain system. Mapping a domain to a Data Domain system (page 43) provides detailed steps. Setting the default Data Domain destination If there is more than one destination Data Domain system in a replication environment, you must specify which Data Domain system is the default destination. The default destination is the Data Domain system to which Avamar replicates data when a destination Data Domain system is not identified on the Replication Storage Mapping tab. Mapping a domain to a Data Domain system (page 43) provides details on mapping a domain on a source Avamar server to a destination Data Domain system for replication. To set the Data Domain system that is the default replication destination: 1. In Avamar Administrator for the destination Avamar server, click the Server launcher button. The Avamar Server window appears. 2. Click the Server Management tab. 3. Select the destination Data Domain system. 4. Select Actions > Edit Data Domain System. The Edit Data Domain System dialog box appears. 5. On the System tab, select the Use system as default replication storage checkbox. 6. Click OK. Mapping a domain to a Data Domain system If there are multiple destination Data Domain systems, you can control which system receives the data that replicates from the source Data Domain system by mapping a domain on the source Avamar server to a destination Data Domain system. If you do not provide a mapping, then Avamar replicates the data from the source Data Domain system to the default destination that you identified in Setting the default Data Domain destination (page 43). NOTE: You cannot map the domains on the source Avamar server to a destination Data Domain system until after the first replication occurs. During the first replication, the data replicates to the default destination. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 43

44 Configuring replication REPLICATION To map a domain on a source Avamar server to a destination Data Domain system: 1. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 2. Click the Replication Storage Mapping tab. 3. Click Add Domain. The Select a Domain dialog box appears. 4. Browse to and select a domain from the tree. 5. From the Map to Data Domain System list, select the Data Domain system to use as the replication target. 6. Click OK. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 44

45 Configuring replication REPLICATION Deleting a domain mapping When you delete a mapping between a domain on a source Avamar server and a destination Data Domain system, any data that has already replicated to the destination system remains there. However, any new data replicates to the default destination system unless you create a new mapping to a different Data Domain system. To delete a mapping between a domain on a source Avamar server and a destination Data Domain system: 1. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 2. Click the Replication Storage Mapping tab. 3. Select the mapping and click Delete. 4. Click Yes on the confirmation message. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 45

46 MONITORING AND REPORTING The following topics provide details on how to monitor and report on a Data Domain system that is configured as a backup target for Avamar: Monitoring Data Domain with SNMP (page 46) Backup and restore monitoring (page 47) Server monitoring (page 49) Event monitoring (page 52) Data Domain capacity monitoring (page 53) Replication monitoring (page 58) Reports (page 59) Additional Data Domain system monitoring tools are available through the Data Domain Enterprise Manager. The Data Domain documentation provides details. Monitoring Data Domain with SNMP Avamar can collect and display data for health monitoring, system alerts, and capacity reporting on a configured Data Domain system using SNMP. To enable this functionality, specify the port number on which to receive traps when you add the Data Domain system to the Avamar configuration. Adding a Data Domain system (page 30) provides detailed steps. The Data Domain SNMP service on the Avamar server receives and manages the SNMP traps for all configured Data Domain systems. You can manage the service in Avamar Administrator. To manage the SNMP service for Data Domain: 1. In Avamar Administrator, click the Administration launcher button. The Administration window appears. 2. Click the Services Administration tab. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 46

47 Backup and restore monitoring MONITORING AND REPORTING The Data Domain SNMP Manager service is the SNMP service for Data Domain. 3. To stop or start the service, right-click the service and select Stop Data Domain SNMP Manager or Start Data Domain SNMP Manager, respectively. Backup and restore monitoring You can monitor recent backup, restore, and validation activities by using the Activity Monitor in Avamar Administrator. The Server column in the Activity Monitor lists the server either the Avamar server or the Data Domain system on which the activity occurred. The Activity Monitor displays the most recent 5,000 client activities during the past 72 hours. You can filter the Activity Monitor to view only activities for data on a Data Domain system. To filter backup, restore, and validation activities for Data Domain: 1. In Avamar Administrator, click the Activity launcher button. The Activity window appears. 2. Click the Activity Monitor tab. 3. Select Actions > Filter. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 47

48 Backup and restore monitoring MONITORING AND REPORTING The Filter Activity dialog box appears. 4. Select the criteria by which to filter the list of activities. To filter by Data Domain systems: (a) Select Data Domain Systems from the Source list. (b) Select the systems for which to view activities: To view activities for all configured Data Domain systems, select All Systems. To view activities for a specific Data Domain system, select System and then click the... button. Select the Data Domain system in the Select Data Domain System dialog box, and then click OK. NOTE: Details on the remaining settings in the Filter Activity dialog box are available in the EMC Avamar Administration Guide. 5. Click OK on the Filter Activity dialog box. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 48

49 Server monitoring MONITORING AND REPORTING Server monitoring Avamar Administrator provides CPU, disk activity, and network activity for each Data Domain system. NOTE: You also can view an overall status for each Data Domain system configured on an Avamar server by viewing the System Status page for the server in Avamar Enterprise Manager. To monitor the status of a Data Domain system using Avamar Administrator: 1. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 2. Click the Server Monitor tab. 3. Click the Data Domain tab. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 49

50 The following data appears on the Data Domain tab: Server monitoring MONITORING AND REPORTING PROPERTY Status indicators One of the following: OK (green) DESCRIPTION The Data Domain system is functioning properly. NODE Warning (yellow) Error (red) There is a problem with the Data Domain system, but backups and restores can continue. There is a problem with the Data Domain system, and backups and restores will not occur until the problem is resolved. If the status is yellow or red, you can view additional status information so that you can determine and resolve the problem. Troubleshooting (page 63) provides details. Name Hostname of the Data Domain system as defined in corporate DNS. CPU DISK (KIB/S) Busy Avg. Max Read Write Busy Average CPU usage as a percentage of total possible CPU usage. Maximum CPU usage that has occurred as a percentage of total possible CPU usage. Disk read throughput in kilobytes per second. Disk write throughput in kilobytes per second. Disk I/O usage as a percentage of total possible disk I/O usage. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 50

51 Server monitoring MONITORING AND REPORTING PROPERTY DESCRIPTION Eth#1 Desc Description of the network interface. In/Out Network bandwidth usage in kilobytes per second on network interface 1. Eth#2 Desc Description of the network interface. NETWORK (KB/S) In/Out Network bandwidth usage in kilobytes per second on network interface 2. Eth#3 Desc Description of the network interface. In/Out Network bandwidth usage in kilobytes per second on network interface 3. Eth#4 Desc Description of the network interface. In/Out Network bandwidth usage in kilobytes per second on network interface 4. NOTE: The number of Eth# columns depends on the maximum number of network interfaces that the configured Data Domain systems support. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 51

52 Event monitoring MONITORING AND REPORTING Event monitoring When you configure SNMP communication for Avamar and Data Domain, the Avamar Event Monitor displays relevant events for the Data Domain system. You can filter the events to display only those events for a Data Domain system. To filter events in the Avamar Event Monitor for a Data Domain system: 1. In Avamar Administrator, click the Administration launcher button. The Administration window appears. 2. Click the Event Management tab. 3. Select Actions > Event Management > Filter. The Filter dialog box appears. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 52

53 Data Domain capacity monitoring MONITORING AND REPORTING 4. Select the criteria by which to filter events. To filter by Data Domain systems: (a) Select Data Domain Systems from the Source list. (b) Select the systems for which to view events: To view events for all configured Data Domain systems, select All Systems. To view events for a specific Data Domain system, select System and then click the... button. Select the Data Domain system in the Select Data Domain System dialog box, and then click OK. NOTE: The EMC Avamar Administration Guide provides details on the remaining settings on the Filter dialog box. 5. Click OK on the Filter dialog box. Data Domain capacity monitoring Avamar checks the capacity of each configured Data Domain system every 24 hours. If the capacity reaches 95% full, or if the forecast number of days until the capacity is full is less than or equal to 90 days, then an event is logged in the Event Monitor. You also can monitor the capacity of a configured Data Domain system by using either Avamar Administrator or Enterprise Manager. Monitoring capacity in Avamar Administrator Data Domain system capacity summary statistics are available in the Server window in Avamar Administrator. To view capacity statistics in Avamar Administrator for a Data Domain system: 1. In Avamar Administrator, click the Server launcher button. The Avamar Server window appears. 2. Click the Server Management tab. 3. Select the Data Domain system from the tree in the left pane. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 53

54 Data Domain capacity monitoring MONITORING AND REPORTING Data Domain system details appear in the right pane, as shown in the following figure. The fields in the following table provide Data Domain system capacity information. FIELD Total Capacity (post-comp size) Server Utilization (post-comp use%) Bytes Protected File System Available (postcomp avail) File System Used (post-comp used) DESCRIPTION The total capacity for compressed data on the Data Domain system. The percentage of capacity used on the Data Domain system for any reason after compression of the data. The total number of bytes of data that are protected, or backed up, on the Data Domain system. This value is the number of bytes before the data is compressed. The total amount of disk space available for compressed data in the DDFS. The total amount of disk space used in the DDFS for compressed data. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 54

55 Monitoring capacity in Avamar Enterprise Manager Data Domain capacity monitoring MONITORING AND REPORTING The Capacity column on the Dashboard page in Avamar Enterprise Manager provides used and forecast capacity information for the Data Domain system, as shown in the following figure. If there are multiple Data Domain systems configured for the Avamar server, then the Data Domain columns provide a combined set of statistics. NOTE: You also can view the percentage of used and forecast capacity for configured Data Domain systems during a specific time period by selecting the Data Domain Capacity Usage Report and Data Domain Capacity Forecast Report, respectively, in the Reports list on the Avamar Enterprise Manager Reports page. The System Status page in Avamar Enterprise Manager also provides capacity statistics for each Data Domain system configured on an Avamar server, including the following information: Capacity forecast in days Total capacity Percentage of used capacity (utilization) Number of bytes protected EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 55

56 Used capacity on the Dashboard Data Domain capacity monitoring MONITORING AND REPORTING The Used column on the Avamar Enterprise Manager Dashboard shows summary status of how storage capacity is being used on the Data Domain system. Detailed information includes: The amount of storage capacity consumed in bytes The amount of free storage capacity available as a percentage of total available storage capacity Used state icons communicate the following conditions: ICON DESCRIPTION Less than 80% of total storage capacity is in use on the Data Domain system. More than 80% but less than 95% of total storage capacity is in use on the Data Domain system. Consider adding additional capacity or deleting old backups. More than 95% of total storage capacity is in use on the Data Domain system. IMPORTANT: No new backups will be taken until additional capacity is added or old backups are deleted. Contact EMC Technical Support. NOTE: Click a used capacity icon to open the Capacity Utilization and Forecast page, which provides a graph of used and forecast capacity. Forecast capacity on the Dashboard The Forecast column on the Avamar Enterprise Manager Dashboard shows the predicted capacity usage for the Data Domain system. Forecast state icons communicate the following conditions: ICON DESCRIPTION The Data Domain system is forecast to have 90 days or more storage capacity. The Data Domain system is forecast to have less than 90 days of storage capacity. The Data Domain system is forecast to have less than 30 days of storage capacity. NOTE: Click a capacity forecast icon to open the Capacity Utilization and Forecast page, which provides a graph of used and forecast capacity. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 56

57 Data Domain capacity monitoring MONITORING AND REPORTING Viewing a graph of capacity usage The Capacity Utilization and Forecast page in Avamar Enterprise Manager provides a graph of used and forecast capacity for a Data Domain system. To graph used and forecast capacity for a Data Domain system: 1. Open the Capacity Utilization and Forecast page by using one of the following methods: Open the System menu and select Capacity. Click a used or capacity forecast icon on the Dashboard. 2. From the Systems list, select the Avamar server with the configured Data Domain system. 3. Select the checkbox next to the Data Domain systems. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 57

58 Replication monitoring MONITORING AND REPORTING 4. Select whether to view capacity data for a certain time period in months or date range: To limit the amount of data in the graph to a certain time period in months, select Period. Then select the period for used capacity data from the Utilization for the list, and the period for forecast capacity data from the Forecast out list. To limit the amount of data in the graph to a date range, select Date Range. Then specify the start and end dates for the range in the From Date and To Date text boxes, and the period for forecast capacity data from the Forecast out list. 5. Click Run. Replication monitoring There are several ways to monitor replication activity in Avamar, including replication activities associated with a Data Domain system: The Avamar Activity Monitor in Avamar Administrator provides a list of recent replication activities. If you select a Replication Source or Replication Destination activity and select Actions > View Statistics, then you can view additional statistics about the replication, including a list of backups that replicated, the clients associated with the backups, the scheduled and actual start and end times for the replication, and a list of errors that occurred, if any. The EMC Avamar Administration Guide provides details on how to access the Activity Monitor and the statistics that are available. The Replication Report in Avamar Administrator also provides details on recent replication activities. You can filter the report to view only replication activities associated with a Data Domain system. Filtering existing reports (page 59) provides details on how to access and filter the Replication Report. The Replicator Status page in Avamar Enterprise Manager provides a consolidated daily replication status summary for each Avamar system that you monitor. The EMC Avamar Administration Guide provides details on how to access the Replicator Status page and the information that is available. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 58

59 Reports MONITORING AND REPORTING Reports The Avamar Activity Report and Replication Report list the server either the Avamar server or the Data Domain system on which the activity occurred. This information appears in the server and ddr_hostname columns of each report. However, if there are a significant number of activities in a report, you can limit the report to view only information related to a Data Domain system. In addition, when you create a custom report, you can limit the report to information related to a Data Domain system. The following topics provide details: Filtering existing reports (page 59) Filtering a custom report (page 61) Filtering existing reports To filter the Avamar Activity and Replication Reports by Data Domain system: 1. In Avamar Administrator, navigate to the report. REPORT Activity Replication HOW TO ACCESS 1. Click the Activity launcher button. The Activity window appears. 2. Click the Activity Report tab. A blank Activity Report window appears. 1. Click the Activity launcher button. The Activity window appears. 2. Click the Replication Report tab. A blank Replication Report window appears. 2. Click Retrieve to retrieve report data. 3. Select Actions > Filter. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 59

60 Reports MONITORING AND REPORTING The Report Filter dialog box appears. 4. Select the criteria by which to filter the report data. To filter by Data Domain systems: (a) Select Data Domain Systems from the Source list. (b) Select the systems for which to view activities: To view report data for all configured Data Domain systems, select All Systems. To view report data for a specific Data Domain system, select System and then click the... button. Select the Data Domain system in the Select Data Domain System dialog box, and then click OK. NOTE: The EMC Avamar Administration Guide provides details on the remaining settings on the Report Filter dialog box. 5. Click OK on the Report Filter dialog box. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 60

61 Reports MONITORING AND REPORTING Filtering a custom report To filter a custom report that you create: 1. In Avamar Administrator, select Tools > Manage Reports. The Manage All Reports dialog box appears. 2. In the clients tree, select the domain to which to add the report, and click New. The New Report dialog box appears. 3. Specify the settings for the report, including a name, title, description, and database view. The EMC Avamar Administration Guide provides details on the settings in the New Report dialog box. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 61

62 Reports MONITORING AND REPORTING 4. If you select Activities or Replication Activities from the Report View and Settings list, select the filtering options for the report. To filter by Data Domain systems: (a) Select Data Domain Systems from the Source list. (b) Select the systems for which to filter the report data: To view report data for all configured Data Domain systems, select All Systems. To view report data for a specific Data Domain system, select System and then click the... button. Select the Data Domain system in the Select Data Domain System dialog box, and then click OK. NOTE: The EMC Avamar Administration Guide provides details on the remaining settings on the New Report dialog box. 5. Click OK on the New Report dialog box. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 62

63 TROUBLESHOOTING The following topics provide details on how to view detailed status for and troubleshoot problems when you use a Data Domain system with Avamar: Viewing detailed status information for troubleshooting (page 63) Data Domain status and resolutions (page 64) Monitoring status details (page 69) Re-creating the SSH public/private key pair (page 72) Viewing detailed status information for troubleshooting The status bar in Avamar Administrator indicates whether there is a problem either with the Avamar connection to a Data Domain system or with a Data Domain system itself, as shown in the following table. STATUS BAR ICON DESCRIPTION Avamar cannot retrieve information from a Data Domain system. However, backups and restores can continue during this condition. Avamar cannot connect to a Data Domain system, or a Data Domain system is disabled in some way. Backups and restores do not occur during this condition. More detailed status information about the problem is available on the Server Management tab in the Server window. To view detailed Data Domain status information: 1. In Avamar Administrator, select Navigation > Server. 2. Select the Server Management tab, and then select the Data Domain system in the tree. EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 63

64 Data Domain status and resolutions TROUBLESHOOTING The Monitoring Status row in the right pane provides a detailed status of the Data Domain system, as shown in the following figure. Data Domain status and resolutions The following table lists the available values for the Monitoring Status row on the Server Management tab in the Server window in Avamar Administrator. If the status indicates a problem, a proposed resolution is provided. MONITORING STATUS RESOLUTION OK SNMP Getter/Setter disabled Unable to get CPU, disk, and network statistics data Unable to get CPU and disk statistics data Unable to get network statistics data Unable to get file system statistics data No resolution is required. Use the Data Domain SSH CLI to enable SNMP by typing: snmp enable Use the Data Domain SSH CLI to enable SNMP by typing: snmp enable Use the Data Domain SSH CLI to enable SNMP by typing: snmp enable Use the Data Domain SSH CLI to enable SNMP by typing: snmp enable Use the Data Domain SSH CLI to enable SNMP by typing: snmp enable EMC AVAMAR 6.0 AND DATA DOMAIN INTEGRATION GUIDE 64