Avamar Admin 19.2 Participant Guide

AVAMAR
ADMINISTRATION
DOWNLOADABLE CONTENT
DOWNLOADABLE CONTENT
Internal Use - Confidential
Table of Contents
Avamar Overview ....................................................................................................... 8

Avamar Administration Tools ............................................................................................... 8
Avamar Desktop/Laptop....................................................................................................... 9
Connection Limit ................................................................................................................ 10
Avamar Server Process – Notification and Reporting ......................................................... 11
Avamar Client Processes ................................................................................................... 12
Avamar Backup Process Flow ........................................................................................... 14
Client-Server Data Port Usage and Firewall Requirements ................................................ 15
Usage Environment ........................................................................................................... 18
Backup Process ................................................................................................................. 19
DD Boost Process.............................................................................................................. 20
Avamar Backups Stored on Data Domain System ............................................................. 22
Avamar Backup Content on Data Domain System ............................................................. 23
Maintenance Activities ....................................................................................................... 24
ddrmaint Process ............................................................................................................... 25
Types of Data Domain Configuration in Avamar Environment ............................................ 26
Additional Data Domain Integration Features ..................................................................... 28
Avamar Integration with Data Domain - Required Ports ..................................................... 30
Avamar Data Deduplication Workflow ................................................................................ 32
More About Sticky-Byte Factoring ...................................................................................... 34
More About Compression .................................................................................................. 35
Client Cache Files and the Backup Process....................................................................... 36
SHA-1 Hashing .................................................................................................................. 37
Cloud Tier .......................................................................................................................... 38
Data Protection Advisor (DPA) with Avamar ...................................................................... 39
Search with Avamar ........................................................................................................... 41
Exporting Avamar Data to Tape ......................................................................................... 43
Backing Up Databases versus File System Data ............................................................... 44
Avamar Database Clients .................................................................................................. 45
Avamar – Database Backup Options ................................................................................. 46
Avamar Administration-Participant Guide

Page ii © Copyright 2020 Dell Inc.
AUI Overview ............................................................................................................ 47
AUI Navigation Pane.......................................................................................................... 49
AUI Dashboard .................................................................................................................. 53
Installing Avamar Backup Client Software ............................................................ 60

Avamar Backup Client Software......................................................................................... 60
Verify Avamar Backup Client System Requirements .......................................................... 61
Installing Avamar Windows Client Software ....................................................................... 63
Windows Client Software Plug-ins ..................................................................................... 67
Client Installation in Multiple Systems ................................................................................ 69
Avamar Client Processes and Services (Windows) ............................................................ 71
Avamar Client Directory Structure ...................................................................................... 72
Account Management .............................................................................................. 73

Avamar Domains ............................................................................................................... 73
Default and Special Domains ............................................................................................. 74
Avamar Users .................................................................................................................... 76
Avamar User Roles ............................................................................................................ 77
Avamar Users in the Domain Hierarchy ............................................................................. 78
Preconfigured User Accounts............................................................................................. 79
Avamar Authentication ....................................................................................................... 80
Avamar Domain Tree Structure.......................................................................................... 84
Account Management Tasks .............................................................................................. 85
Account Management Task - Create a Domain .................................................................. 87
Account Management Task - Edit a Domain ...................................................................... 88
Account Management Task - Delete a Domain .................................................................. 89
Avamar Management Task - Create a New User ............................................................... 90
Avamar Management Task - Edit a User ........................................................................... 91
Account Management Task - Delete a User ....................................................................... 92
Managing Directory Services ............................................................................................. 93
Create an LDAP Group ...................................................................................................... 94
Adding an LDAP ................................................................................................................ 95
Registering Avamar Client ................................................................................................. 97
©
Internal Use - Confidential Copyright 2020 Dell Inc. Page iii
Inviting Avamar Clients to Activate - AUI and Avamar Administrator .................................. 99
Activating Clients - Windows and Linux ............................................................................ 100
Client ID and Activation Status ......................................................................................... 102
Activating Clients Using Avamar Client Manager ............................................................. 103
Account Management for Clients - AUI and Avamar Administrator .................................. 104
Disabling Client Backup ................................................................................................... 105
Account Management for Clients - Avamar Client Manager ............................................. 107
Using the MCCLI Command ............................................................................................ 108
Best Practices: Domains, Users, and Clients ................................................................... 110
Adding a Data Domain System Using AUI ....................................................................... 111
Using Client Manager ............................................................................................ 113

Avamar Client Manager Overview .................................................................................... 113
Avamar Client Manager for Multiple Avamar Servers ....................................................... 114
Client Filtering .................................................................................................................. 116
Managing Clients with Avamar Client Manager ................................................................ 118
Moving a Client to a New Avamar Server ......................................................................... 122
Preparing a Client List ...................................................................................................... 127
Activating Clients in Avamar Client Manager.................................................................... 128
Avamar Backups .................................................................................................... 133

Scheduled Backups ......................................................................................................... 133
On-Demand Backups ....................................................................................................... 162
Avamar Desktop/Laptop................................................................................................... 173
Managing and Monitoring Backup Activity ........................................................................ 187
Performing Restores.............................................................................................. 196

Client Server Recovery with Avamar ................................................................................ 214
Avamar Replication................................................................................................ 220

Avamar - Data Domain Replication .................................................................................. 220
Replication Process and Topologies ................................................................................ 221
Avamar Replication Types ............................................................................................... 223
Pre-Requisites ................................................................................................................. 223

Page iv © Copyright 2020 Dell Inc.
Replication Destination .................................................................................................... 224
Define a Schedule............................................................................................................ 226
Replication with Data Domain Systems............................................................................ 227
Data Domain Destination Settings ................................................................................... 228
Create a Replication Policy .............................................................................................. 230
How to Perform an On-Demand Replication .................................................................... 234
Monitor Replication in AUI ................................................................................................ 235
Replicas at Source ........................................................................................................... 236
Restore Replicated Backups on a Destination System ..................................................... 237
Restore Replicas at Source ............................................................................................. 238
Cloud Tier ............................................................................................................... 239

Cloud Tier ........................................................................................................................ 239
Add or Edit a Data Domain with Cloud Tier ...................................................................... 241
Add a Cloud Tier Policy.................................................................................................... 244
Perform Restore from Cloud Tier ..................................................................................... 251
Recall a Cloud Tier Backup .............................................................................................. 252
File or Granular Level Restore for Cloud Tier ................................................................... 258
System Monitoring and Maintenance ................................................................... 260

Avamar Server Environment ............................................................................................ 260
Avamar Server Directory Structure .................................................................................. 262
Avamar Node Numbers.................................................................................................... 264
Probe.xml Files ................................................................................................................ 265
Nodenumbers Utility......................................................................................................... 265
Loading SSH Keys ........................................................................................................... 266
Mapall Utility .................................................................................................................... 267
Activity Monitoring ............................................................................................................ 267
Activity Summary ............................................................................................................. 271
Event Monitoring .............................................................................................................. 272
Event Monitoring - Audit Log ............................................................................................ 276
Event Management in AUI ............................................................................................... 279
Managing Profiles ............................................................................................................ 281
©
Internal Use - Confidential Copyright 2020 Dell Inc. Page v
Editing System Event Profile ............................................................................................ 283
Create a Custom Event Profile ......................................................................................... 285
Server Monitoring............................................................................................................. 294
System Management ....................................................................................................... 296
Avamar Server Status and Processes.............................................................................. 299
Email Home Notification ................................................................................................... 303
ConnectEMC ................................................................................................................... 304
Server Maintenance Activities Overview .......................................................................... 307
Scheduling Activities: Backup/Maintenance Window ........................................................ 309
Daily Maintenance: Garbage Collection ........................................................................... 313
Daily Maintenance: Checkpoints ...................................................................................... 314
Managing Checkpoints .................................................................................................... 316
Best Practices for Scheduling .......................................................................................... 317
Impact of Maintenance Activities and Backups ................................................................ 317
Impacts of Maintenance Activities on Data Domain.......................................................... 319
Avamar Server Capacity Definitions ................................................................................. 321
Avamar Server Lifecycle Management............................................................................. 323
Factors Affecting Capacity Utilization ............................................................................... 324
Understanding Checkpoint Overhead .............................................................................. 324
Factors Affecting Checkpoint Overhead ........................................................................... 325
Important Capacity Thresholds ........................................................................................ 326
When OS View Exceeds 85 Percent ................................................................................ 328
Capacity Warning Threshold ............................................................................................ 328
Capacity Read-Only Threshold ........................................................................................ 330
Managing Capacity Utilization .......................................................................................... 330
Checkpoint Utilization ...................................................................................................... 334
capacity.sh ....................................................................................................................... 335
DPN Summary Report ..................................................................................................... 337
Backup Statistics.............................................................................................................. 339
Logs, Troubleshooting, and Reporting ................................................................ 342

Avamar Processes and Logs ........................................................................................... 342
Troubleshooting ............................................................................................................... 355
Avamar Fitness Analyzer and Reports ............................................................................. 362

Page vi © Copyright 2020 Dell Inc.
Course Summary ................................................................................................... 384
Course Summary ............................................................................................................. 384
Appendix ............................................................................................... 385
Glossary ................................................................................................ 415
©
Internal Use - Confidential Copyright 2020 Dell Inc. Page vii
Avamar Overview
Avamar Overview
Avamar Administration Tools
Avamar enables central administration through its remote access interfaces. The
following interfaces are used to administer an Avamar server:
Avamar Web User Interface (AUI) Avamar Administrator
Management Console Command Line Orchestra REST API

Interface (MCCLI)
Page
Internal Use - Confidential 8 © Copyright 2020 Dell Inc.
Avamar Overview
Avamar Desktop/Laptop
Click to enlarge image.
Avamar Desktop/Laptop1 enables the end users to restore their data without the
intervention of the backup administrator. The following are some of the features of
Avamar Desktop/Laptop:
• Provides a secure Avamar interface for end-users

• Enables end users to perform backup and restore without the intervention of the
backup administrator
• No separate login is required, as the users are integrated with Active
Directory/LDAP for authentication
• Users are allowed to perform predefined backups and restore files that they
own
1Avamar Desktop/Laptop is a version of the Avamar client software for Windows

and Macintosh that adds enhanced features for enterprise desktop and laptop
computers. Many of the features are also available on supported Linux computers.
© Copyright
Internal Use - Confidential 2020 Dell Inc. Page 9
Avamar Overview
Connection Limit
Avamar server supports 72 connections. Avamar integrated with Data Domain

can support 336 Jobs.
Click to enlarge
The Avamar Administrator server allows a maximum of 72 concurrent backup

connections for each active storage node. This includes one connection reserved
for restores.
When Avamar is integrated with Data Domain system, Avamar can support up to
336 concurrent backup connections. Each connection can consist of multiple
streams, a maximum of 500 streams.
Page
Avamar Overview
Avamar Server Process – Notification and Reporting
Several processes run on Avamar server nodes. Key processes include:
• Avamar Administrator Server2

• Avamar Data Server3
Administrator server is responsible for two important functions:
• Notification4
• Reporting5
2System activities and operational status are reported as events to the

administrator server. Avamar Administration processes include MCS, EMT, ASCD,
MCDB and more.
3 The Avamar data server stores, processes, and manages variable-sized chunks
that the client sends during a backup. Data server is also known as Global Storage
Area Network (GSAN).
4 Various kinds of notifications are created when specific events occur. Events can
be viewed using the Avamar Administrator Event Management and AUI. Events
can be configured as pop-up alerts to the GUI and notifications via email messages
to designated recipients. Examples of events include client activation, and
successful or failed backups.
5 Third-party tools and applications can be used to monitor and report on the syslog
files and SNMP traps that include Dell EMC Smarts and Dell EMC Data Protection
AdvisorSystem events. Actions initiated by users, such as user logins, are
maintained in an audit log for enforcement and accountability of security policies.
Avamar activities and events can also be accessed to run pre-configured and ad
hoc reports through read-only view of the Management Console Database.
© Copyright
Avamar Overview
Avamar Client Processes
Avamar client6 software runs on each computer being backed up. Avamar client
software consists of two main processes apart from avscc7. They are:
• avagent
• avtar
6 Avamar clients are networked computers or workstations that access the Avamar
server over a network connection. You can organize and segregate clients by
using Avamar domains. Domains provide enhanced security by enabling you to
define administrative user accounts on a domain-by-domain basis. Before Avamar
can backup and restore data on a client you must add, or register, the client with
the Avamar server, and then activate the client.
7 avscc process is used to access the Avamar client GUI.
Page
Avamar Overview
Backup metadata and log files
OS level backup and metadata
Avamar Server
Work order for backup
Work order OS level backup
Backup data
Avamar Client
Data Domain
© Copyright
Avamar Overview
Avamar Backup Process Flow
During a scheduled backup:
Utility Node Webserver

MCS
2800
avscc
2800
Storage node 0.n
avagent
avtar
Storage node 0.1
Avamar Client
27000/29000
Storage node 0.0
Avamar Server
Click to enlarge image
1. The administrator server (MCS) generates

a work order.
2. MCS pages the client avagent. avagent

picks up the work order.
3. On the client, avagent starts avtar to

begin the backup process.
4. avtar communicates to a GSAN process

and sends backup data to the GSAN.
5. GSAN distributes the data across the

available storage nodes.
Page
Avamar Overview
Client-Server Data Port Usage and Firewall Requirements
The table below shows the details of some of the data ports used in communication
between Avamar clients and the Avamar server:
Port/Protocol Purpose Source Destination Remarks
30001/TCP MCS using Utility node Storage • Required port

SSL node • Secure agent
registration in
secure mode
30001/TCP MCS using Storage Utility node • Required port

SSL node • Secure agent
registration in
secure mode
30002/TCP Avamar client Avamar Avamar

using SSL server client • Required port
• Paging support
in secure mode
30002/TCP Avamar client Avamar Avamar • Required port

using SSL client server • Paging support
in secure mode
443/TCP HTTPS for User-defined Utility node • Required port

implements, web client • Access to all
web restore, hosts clients or remote
docs, and proxy web
downloads server is
recommended
© Copyright
Avamar Overview
7778/TCP - RMI - Avamar Avamar Utility node • Required port

7781/TCP administrator administrator • Recommend
server management permitting
console access only from
trusted
administrative
hosts
27000/TCP Avamar client Avamar All nodes Blocked by Avamar

communication client firewall by default
with Avamar network
server hosts
27000/TCP Avamar server All nodes Replicator Blocked by Avamar

communication target firewall by default
with Replicator server
target server
28001/TCP Avamar client Avamar Utility node Required port

communication clients
with
administrator
server
28002/TCP Administrator Utility node Avamar Optional for

server clients browsing clients
communication and canceling
with Avamar backups from
client Avamar
administrator
management
console
Page
Avamar Overview
29000/TCP Avamar client Avamar All nodes Required

Secure clients
Sockets Layer
(SSL)
communication
with Avamar
Server
29000/TCP Avamar Server All nodes All Required if server is

SSL replicator the replicator
communication target source
with Replicator server
target server nodes
Note: Please see the Avamar Product Security Guide for complete
data port usage and firewall requirements.
© Copyright
Avamar Overview
Usage Environment
The following is the environment where the Data Domain usage is best suited:
Best for database and heterogeneous backup environments
Large databases: 2 TB or larger
Environments with high change rate and short retention
Example:
- 4% daily change, 30 day retention
- 8% daily change, 45 day retention
Page
Avamar Overview
Backup Process
In an Avamar-Data Domain environment:
• Backup metadata8 is stored in the Avamar system9.

• Backup data is stored in the Data Domain system10.
Avamar
Metadata
Client Backup
Data Domain
Important: References to Data Domain systems in this course, in the

UI, and elsewhere in the product include Data Domain systems and
the new PowerProtect DD systems.
8Backup metadata is used to identify files and backup data that is stored on the
Data Domain system.
9Based on the metadata, the Avamar system manages the backup data. The
backup process uses Avamar-Data Domain deduplication methods, which can
provide faster backup and recovery, especially for large active databases.
10Data Domain integration can also provide flexibility, since the Data Domain
storage can be shared with other Avamar servers and/or other applications.
© Copyright
Avamar Overview
DD Boost Process
Avamar clients use the Data Domain Bandwidth Optimized Open Storage (DD
Boost11) with Distributed Segment Processing to access a Data Domain system.
The DD Boost SDK is installed automatically on the client computer when you
install the Avamar client.
1. ID Segment 2. Unique?
DD Boost
3. Compress 4. Write
Client Data Domain
The following processes are included during a backup when integrated with Data
Domain:
 ID Segments12
 Uniqueness13
11DD Boost provides deduplication at the client so that only unique data is sent
across the network. The method is similar to how Avamar provides deduplication
except that the file cache is not used (with the exception of file system backups).
12When a backup request is made, DD Boost software on the client will divide the
data into variable size segments and determine a unique fingerprint ID for the
segment.
Page
Avamar Overview
 Compress14
 Write15
 File cache not used16 (exception: file systems)
Important: As the DD Boost is used to send data to the Data Domain,

the Data Domain system must be configured to accept DD Boost
data.

13 The client checks to see if the segment has already been stored.
14If it is a unique segment, the client will compress the data and send it to the Data
Domain.
15 The Data Domain system will write the data to disk.
16Note that for most backup types, the file cache on the client is not used. File
system backups, however, do use a file cache. This means that if a file has not
changed since the last backup, it does not need to be segmented, and its
segments do not need to be queried against the Data Domain.
© Copyright
Avamar Overview
Avamar Backups Stored on Data Domain System
End users should never need to know or access data directly on the Data Domain
server, since all files and folders on Data Domain are managed by the Avamar
server.
An Avamar server owns all the folders that it creates on a

Data Domain system. Here is an example of the Avamar
folder structure:
Relative paths from CIFS:

- \\datadomain1\data\col1\
clients
Relative dpn associated path:

- Storage unit: ..\avamar-<dpnid>\
backups
Temporary backup path:
- ../avamar-<dpnid>/STAGING/<cid>/BACKUP-<GUID>/
- In-progress backups, incomplete, cancelled
Final path on a successful backup:
- Moves successful backups from staging to ../avamar- In-progress

<dpnid>/cur/<cid>/<backup hex-time>/ backups

Page
Avamar Overview
Avamar Backup Content on Data Domain System
Client Data Stored in Data Domain System as:
Data packaged into container files on the Data Domain

Flat directory Backup name is the
file system can have few exceptions. For example,
structure hex-time
Exchange DBs stored in native Exchange format
© Copyright
Avamar Overview
Maintenance Activities
When Data Domain is integrated with Avamar:
• Maintenance activities17 performed on Avamar server are also performed on

data stored in Data Domain.
• Expired or deleted backups on Avamar server are also deleted from Data
Domain18.
17Maintenance operations that are performed by Avamar for backup data on a

Data Domain system are HFS Checks, Checkpoints, and Garbage Collection.
18Data Domain may have a different maintenance schedule from Avamar. Though
the backups are deleted from Data Domain, the space is freed only after Data
Domain performs cleaning activities.
Page
Avamar Overview
ddrmaint Process
ddrmaint installed on utility node
Communicates maintenance commands to Data Domain
Part of Avamar Installation/Upgrade
ddrmaint
Maintenance Commands
© Copyright
Avamar Overview
Types of Data Domain Configuration in Avamar Environment
The following are the three different types of backup configurations when Data
Domain system is integrated with Avamar:
Basic Configuration19 Multiple Data Domain Shared Data Domain

Systems20 System21
19 The basic configuration consists of a single Data Domain system with a single
Avamar system backing up a number of Avamar clients. During the backup, the
Avamar sends a backup request to the Avamar client.If the backup request
includes the option to use a Data Domain system as the target, the Avamar client
sends the backup data directly to the Data Domain system. The backup data is not
staged on the Avamar before it is sent to the Data Domain.Metadata for the backup
is sent from the Avamar client to the Avamar server. This enables the Avamar to
manage the backup even though the data is stored on a Data Domain system.
Metadata is stored on the Avamar system, and the backup data is sent to and
stored on the Data Domain.
20This environment has an Avamar system with multiple Data Domain systems.To
segregate data, use multiple Data Domain systems with a single Avamar server.
This type of configuration provides a large amount of storage by using multiple
Data Domains. When using this type of configuration, be sure that the Avamar
server is sized properly so that it is able to store all metadata. Having multiple Data
Domains also increases the amount of simultaneous backups allowed.Although it is
possible to direct the backups from one client to two different Data Domain
systems, remember that the data from one system will not deduplicate against a
separate one. Therefore, deduplication rates may be lower. Also, backup clients
that use incremental backup strategies must store the incrementals on the same
Data Domain system as their associated full backups.
Page
Avamar Overview
21 This is an environment where there is an Avamar system and another backup

system with a shared Data Domain system. The other backup solution can be any
other backup product that uses a Data Domain system, or it can be another
Avamar server.The Data Domain logically segregates the data from different
sources by storing it in different directories. However, deduplication still occurs
between data from different sources. Deduplication occurs across the entire Data
Domain.When using a single Data Domain with multiple Avamar servers, be sure
that there is enough capacity on the Data Domain. Capacity planning can be more
difficult when Data Domain storage is shared amongst multiple systems. Also, keep
in mind that each Data Domain System has a limited number of network
connections and CPU available. These resources must be shared amongst the
Avamar and other backup application.
© Copyright
Avamar Overview
Additional Data Domain Integration Features
Integrating Avamar with Data Domain provides a few additional features. These
include Instant Access, Checkpoint backups to Data Domain, Token-based
Authentication, REST API, and Cloud Tier.
1 2 3 4 5
1: Instant Access
When performing image level backups of virtual machines, a virtual machine may
be booted from the backup data without the must perform a restore. This feature of
Data Domain integration is known as Instant Access.
2: Checkpoint Backup to Data Domain
Single-node servers and AVE servers enable Avamar to perform backups of

checkpoint data to a Data Domain system. Disaster recovery is possible without the
need for a second Avamar server. In the event of a disaster, the checkpoint can be
restored.
3: Token-Based Authentication
Page
Avamar Overview
Avamar can establish a connection to a Data Domain system using Data Domain
Boost Token-based Authentication22. This allows Avamar clients to connect
securely to the Data Domain system without going through login formalities.
4: REST API
REST API facilitates:
• Quota management
• Data Domain physical capacity reporting
5: Cloud Tier
Avamar leverages the Data Domain Cloud Tiering Feature. The feature allows
older backups to be tiered to cloud-based storage. Some of the cloud tier features
include:
• Age-based policy support for DD Cloud Tier

• Single Administrative Step Backup Recall from Cloud
• Restore to Clients

22In Token-based Authentication, each token is unique. The token exists only for
the duration of a backup. The clients do not store any of the credentials. Therefore,
the risk of breach into a system is greatly reduced. This feature is important for
multi-tenant BaaS environments.
© Copyright
Avamar Overview
Avamar Integration with Data Domain - Required Ports
The table in the slide lists some of the ports used in communication between
Avamar clients, Avamar server, and integrated Data Domain system:
Port Protocol Source Destination Remarks
7 TCP Utility node Data Domain Required to register Data

System Domain systems
22 TCP Utility node Data Domain Secure shell

System communication with Data
Domain systems
111 TCP/UDP Utility node Data Domain Access to RPC and NFS
System port mapper functionality
on Data Domain systems
161 UDP Data Utility node Getter/setter port for

Domain SNMP objects from Data
System Domain
163 UDP Utility node Data Domain None

System
2049 TCP/UDP Utility node Data Domain None

System
2052 TCP/UDP Utility node Data Domain Outbound communication

System must be open for TCP and
UDP
3008 TCP Avamar Data Domain Only required when

Client System archive tier is used
Page
Avamar Overview

© Copyright
Avamar Overview
Avamar Data Deduplication Workflow
The Avamar agent running on the backup client (avtar) traverses each directory in
the backup. A set of tasks and comparisons determine if the data is present in the
Avamar server before backup.
1 2 3 4 5
1: The avtar process checks the client’s f_cache.dat file to see if the file was
backed up before. If the file was backed up, it is skipped from processing.
2: If there is no match in the f_cache.dat file, the data is processed. First, sticky-
byte factoring divides the data into variable-sized chunks.
3: The data chunk from sticky-byte factoring goes through a process of

compression. A file can be compressed by more than 25% only based on a list of
supported file types in the client software.
4: After compression, the following processes take place:
• Chunks are hashed. The hash created from a data chunk is referred to as an
atomic hash. Atomic hashes are combined to create Composite hashes.
• Each atomic hash is compared to the entries in the client’s p_cache.dat file to
determine if it has been stored before. If a match is found composites are
created.
• If there is no match in the p_cache.dat file, the p_cache.dat file is updated, and
the hash is sent to the Avamar server with an is-present command.
Page
Avamar Overview
5: If there is no match on the Avamar server, the Avamar server stores the hash
and the data corresponding to the hash. The process repeats during every backup.
The local p_cache.dat file updates with the hashes for the atomic and composite
hashes.
Note: A Data Domain system performs deduplication through DD OS

software. Avamar source-based deduplication to a Data Domain
system is facilitated through the use of the Data Domain Boost
library. Please refer to Avamar and Data Domain System Integration
Guide for more information.
© Copyright
Avamar Overview
More About Sticky-Byte Factoring
A. No change in sizes of chunks as the data is identical to previous backup
STICKY-BYTE
FACTORING
B. Due to change in data, the chunks are updated and synchronized with data from the
previous backup
STICKY-BYTE
FACTORING
With sticky-byte factoring, avtar divides raw data into chunks that vary in size 23.
The chunk sizes remain the same if the data is identical to the previous backup. If
there is a change in data, sticky-byte factoring:
• Locates where the data has been changed.

• Synchronizes the chunking process to match data chunks created during the
previous backup.
23The chunks vary in size between 2KB and 64 KB. The size of data chunks
average to 24 KB.
Page
Avamar Overview
More About Compression
Sticky-byte
Factoring
Compression
After sticky-byte factoring, a compression algorithm compresses the chunks.

Compression:
• Reduces the chunk size24 by 30 to 50 percent to an average size of 12KB to

16KB
• Uses a compression algorithm optimized for speed
• Does not compress chunks with unfavorable compression ratios
24 The original source file can be compressed by more than 25% only based on a
list of compressible file types contained in the client software.
© Copyright
Avamar Overview
Client Cache Files and the Backup Process
avtar uses the following filtering process to filter out previously backed up files and
chunks.
Stat file, compute SHA-1
Does file hash

exist in the file Process the next file
cache?
Chunk, compress and compute hash

of chunk
Does chunk hash

exist in the hash Process the next chunk
cache?
Issue 'is present' request to Avamar

data server
Does chunk hash

exist on the the Process the next chunk
Avamar server?
Send the chunk and chunk hash to

Avamar server
Page
Avamar Overview
SHA-1 Hashing
Compression is followed by hashing. During hashing, the following processes take

place:
• The SHA-1 hashing algorithm processes data chunks to create unique

hashes25.
• The hash obtained is used for Avamar deduplication.
Compressio
n
25 Hashes are unique data strings created through the hashing process.
© Copyright
Avamar Overview
Cloud Tier
Avamar Cloud Tier Enables movement of Avamar Backups26 in Data Domain to the
cloud. Its important features are:
• Works in tandem with the Data Domain Cloud Tier

• Facilitates long-term storage of Avamar backups
Note: In Avamar 19.2, Cloud Tier supports performing virtual

machine FLR operations on backups in the cloud.
26Avamar Cloud Tier allows seamless and secure tiering of backups to the cloud.
From the AUI, configure cloud tier to move Avamar backups from Data Domain to
the cloud, as well as perform seamless recovery of these backups.
Page
Avamar Overview

Data Protection Advisor (DPA) with Avamar
Data Protection Advisor (DPA)27 eliminates the need for multiple reporting and
analysis tools to manage and monitor the backup environment. DPA provides:
27DPA is a customizable, backup-reporting, alerting, monitoring, and correlation

analysis software tool for Dell EMC and third-party backup software products.
Reports with Data Protection Advisor can be customized extensively to suit the
demands of any business.
© Copyright
Avamar Overview
• Improved monitoring28
• Single-window view of the infrastructure29
Important: Data Protection Advisor is a part of the DP Suite. The DP

Suite has to be purchased and installed to access Data Protection
Advisor.
28DPA can be used in Avamar environments to provide increased monitoring

abilities. DPA provides the ability to monitor the entire backup environment in
addition to Avamar servers. It is able to predict future trends to prevent problems
before occurring.
29DPA provides a single view of the entire infrastructure through data discovery,
analysis, and reporting that leverages key backup management functions. DPA
incorporates backup solutions, replication technologies, virtual environments,
tape/VTL storage, SAN and NAS systems, and the business applications protected
by the infrastructure.
Page
Avamar Overview
Search with Avamar
Search is a scalable, fault-tolerant virtual appliance used for indexing and search of
backup data.
2 1
1: Search
Search provides a powerful way to:
• Search backup data across one or more Avamar servers

• Restore or download the search results.
2: Indexing
Scheduled collection activities gather and index the metadata and the content of
backups. It is stored within the Search node or cluster. Search can:
• Index multiple Avamar servers simultaneously.

• Register multiple Avamar File System clients on each Search node.
© Copyright
Avamar Overview
Important: Search is a part of the DP Suite. The DP Suite has to be

purchased and installed to access Search.
Page
Avamar Overview
Exporting Avamar Data to Tape
Avamar Server Staging Server Tape
Avamar Data Migration Enabler (ADMe)30 provides methods of exporting backup

data to tape for long-term storage. ADMe facilitates:
• Migration31
• Recovery32
30
ADMe is a software tool used for migrating Avamar backup data to other storage
mediums, such as tape drives, cloud, or USB drives.
31During migration, ADMe re-hydrates the backup data to a staging server before
the data is exported to a tape-based backup product.
ADMe supports both incremental, as well as non-incremental staging. It also

supports multiple staging servers, which mean the administrator can have multiple,
concurrent migration threads open. Email notifications and chain of custody
reporting are also supported.
32Migrated files can be retrieved from tape using native recovery tools of ADME. A
new GUI has been added to the software to simplify migration and recovery of
Avamar backups.
© Copyright
Avamar Overview
Backing Up Databases versus File System Data
File System storage has few advantages over databases. The advantages are
illustrated in the following table.
Require Daily rate Initial Less Faster

less of change deduplication bandwidth backups
storage. in data: rate across usage and compared
0.3% all clients: CPU to
70% utilization databases
File Systems
Require Daily rate Initial High Database

more of change deduplication bandwidth backups
storage - in data rate across usage and take more
databases 3% to 5% all clients: CPU time
have more 35% utilization
unique data
Databases
Page
Avamar Overview
Avamar Database Clients
Avamar Client
(avtar)
Database Plug-
in
Database
Application
Avamar Client
Avamar Server
Avamar Database clients are specialized client software for backing up and
restoring databases33. The software allows the users to choose between different
configurations depending upon the placement and type of agents.
33Avamar supports databases including Microsoft SQL Server, Exchange,

SharePoint, Lotus Domino, DB2, Sybase, SAP, and Oracle databases.
© Copyright
Avamar Overview
Avamar – Database Backup Options
There are several options for installing client agents when backing up databases.
The options are defined by the placement of agents and the types of agents
required.
Avamar Database Agent 'hot' Database Dump with 'hot' snapshot copy with
on Database Server Proxy Proxy
Page
AUI Overview
AUI Overview
Introduction to AUI
What is AUI?
Avamar Web User Interface (AUI) is a web management application that is used to
administer an Avamar server.
AUI is used to:

• Monitor backups, restore operations, and system maintenance activities.
• Configure backup policies.
• Manage clients and user accounts.
• Configure other system settings.
How to Access the AUI?
The AUI can be accessed through a web browser.
© Copyright
AUI Overview
The follow the steps must be performed to access the AUI:

1. Open a web browser and type URL: https://Avamar_server_address/aui,
where Avamar_server_address is the DNS name or IP address of the
Avamar server.
2. Enter the username and password.
3. Type the Avamar domain to which the user has to login under the Avamar
Domain field.
4. Click LOG IN to display the AUI dashboard.
Page
AUI Overview
AUI Navigation Pane
Navigation Pane Overview
Once you log in to the AUI, you can see the navigation pane towards the left of the
screen. You can use the navigation pane to quickly browse through different panes
in the AUI. It provides links that open other panes to perform tasks in the AUI.
The AUI is divided into five parts:

• Dashboard
• Asset Management
• Policy
• Administration
• Monitor
Expanding the Navigation Pane
To view all the parts of AUI, you must expand the

navigation pane. To perform this operation, you must click
>> option from the AUI as shown in the image.
Similarly, you can collapse the navigation pane for a broader view of the dashboard
by clicking << option from the AUI as shown in the image.
© Copyright
AUI Overview
AUI Navigation Pane - Dashboard and Asset Management
The Dashboard34 page provides an at-a-glance view of Avamar system status.
The Asset Management35 page provides the ability to manage Avamar domains
and client-related operations such as create/edit/delete/refresh Avamar domains,
add/edit/delete/sync clients on the Avamar server, and perform backup and restore
of the clients.
34The dashboard view is available for the users who have ADMIN (root and
vCenter) and REPL_USER privileges. These user accounts and permissions can
be defined within the AUI.
35The Asset Management view is available for the users who have ADMIN,
ADMIN_CANNOT_RETIRE, BACKUP_ONLY_USER,
BACKUP_RESTORE_USER, BACKUP_ADMIN, BACKUP_RESTORE_ADMIN,
REPL_USER, RESTORE_ONLY_USER, RESTORE_ADMIN privileges.
Page
AUI Overview
1 7
8
10 11 12 13 14
6
4
3
5
1: The Assets | Overview panel indicates the number of integrated and

unprotected assets on the Avamar server.
2: The Capacity | Overview panel provides system capacity usage information for
the Avamar server and any Data Domain systems that have been added.
3: The Events | All panel displays the unacknowledged serious system errors and
warnings that have occurred, and certain defined system alerts.
4: The Client | Information panel displays Avamar client details, such as the plug-
in type, total client count, and total protected Gigabytes (GB).
5: The Activities | Replication panel indicates the current backup status of groups
that are configured with replication.
6: The Activities | Backup panel indicates whether scheduled backups occur at

the scheduled time or if there is a problem that is preventing backups from
occurring.
7: Displays the number of clients, activities, and policies that are created for a
specific domain.
8: The DOMAIN ACTIONS tab allows the user to edit, delete, and refresh any
domains.
9: The Client Summary tab displays the summary of the client that is created
under a specific domain.
10: The ADD CLIENT option allows the user to add a client for a specific domain.
11: The BACKUP option allows the user to run a backup for the client.
12: The RESTORE option allows the user to run a restore for a client.
© Copyright
AUI Overview
13: The ADD POLICY option allows the user to add a policy to run a backup.
14: The MORE ACTIONS option allows the user to invite, edit, delete, sync clients
that are added to a domain.
AUI Navigation Pane - Policy
The Policy pane allows you to add Backup, Advanced, Replication, and Cloud Tier
Policies.
Backup Policy Advanced Policy Replication Policy Cloud Tier Policy
AUI Navigation Pane - Administration
The Administration pane allows you to add accounts to the system, and to create
and manage schedules, datasets, retention policies, and rules. This pane allows
you to deploy and manage Avamar proxies. Similarly, it allows you to configure
vCenter-to-Avamar authentication, register the Avamar Plug-in for vSphere Web
Client, and add a Data Domain system to Avamar.
Settings Proxy Management System
Page
AUI Overview
AUI Navigation Pane - Monitor
The Monitor pane allows you to view the job activities, various events, and different
types of reports using FItness Analyzer tool.
Activity Event Fitness Analyzer
AUI Dashboard
AUI Dashboard - Overview
The AUI Dashboard provides an at-a-glance view of Avamar system status. It is

displayed when you log in to the AUI based on the user privileges 36. The AUI
Dashboard is divided into sections with each section displaying the summary
information.
36 Only users with ADMIN privileges have access to the dashboard view.
© Copyright
AUI Overview
The following sections are available in the dashboard:

• Integrated and unprotected assets on the Avamar server
• System capacity usage for the Avamar server and Data Domain systems
• Events
• Client information
• Backup activity status
• Replication activity status
Page
AUI Overview
AUI Dashboard Widgets
Monitoring Assets Widget
The Assets | Overview panel indicates the number of Integrated37 and

Unprotected38 assets on the Avamar server.
Monitoring System Capacity Widget
The Capacity | Overview panel provides information about system capacity usage
for the Avamar server and Data Domain systems.
37 Integrated indicates how many clients are integrated into the server.
38Unprotected indicates that a scheduled backup policy has not been defined for
the client.
© Copyright
AUI Overview
Viewing Events Widget
The Events | All panel displays any unacknowledged system errors and warnings
that have occurred, as well as system alerts39.
39The type of alerts that are displayed under the Events | All panel include HFS
check failures, Capacity warnings, and Capacity usage warnings. All the events are
categorized as Critical, Error, and Warning.
Page
AUI Overview
Note: All the events40 are displayed in the list with the name, date, and time that
they occurred.
Monitoring Backup Jobs Widget
The Activities | Backup panel indicates if the scheduled backups occur at the
correct time or if there is any problem that is preventing the backups from
occurring. Various color codes41 represent the status of the backups.
40To display all the critical events, click View More option in the AUI. The user
must explicitly acknowledge the events to clear these serious system errors and
warnings.
41The blue color indicates the backup jobs that have completed successfully. The
green color indicates scheduled backup jobs that are in-progress. The yellow color
© Copyright
AUI Overview
Note: To view errors and troubleshooting while performing any backup or restore
jobs, you need to navigate to the Event pane in the AUI.
Monitoring Replication Jobs Widget
The Activities | Replication panel indicates the replication status of groups that
are configured with replication42.
indicates the backup jobs that are scheduled but have not yet started. And finally,
the red color indicates the backup jobs that did not complete successfully or
completed with errors.
42All the replication jobs are configured from the AUI by selecting Replication
Policy in the navigation pane.
Page
AUI Overview
• Blue color: Indicates the replication jobs are completed successfully

• Green color: Indicates schedule replication jobs which are in progress
• Yellow color: Indicates replication jobs that are scheduled but have not yet
started
• Red color: Indicates replication jobs that did not complete successfully or
completed with errors
Viewing Client Information Widget
The Client | Information panel displays Avamar client information which includes
plug-in type, total client count, and total protected Gigabytes (GB).
© Copyright
Installing Avamar Backup Client Software
Avamar Backup Client Software
Avamar
Backup Clients
Administrator
Avamar Backup Clients43 are:

• Machines that contain data to be backed up to the Avamar server
• Networked computers or workstations accessing Avamar server through a
network connection
• File servers or database servers in an IT environment
43Avamar backup client software is installed and run on each client. Similarly,
specialized database client software plug-ins are installed for backing up and
restoring databases.
Page
Verify Avamar Backup Client System Requirements
The following requirements must be reviewed before installing an Avamar client

software:
System
Requirements
Disk Space
Network Connectivity
• System Requirements44
• Client on the same network as Avamar server
• Must be able to ping Avamar server45
44System requirements include operating system, file system, memory, hard drive
space, network interface, and browser.
45 Use these commands to ping Avamar server:
C:\> ping avamarserver
C:\> nslookup
© Copyright
Important: Refer to the E-Lab Navigatorfor an up-to-date and

complete list of supported operating system, platforms, databases,
and other system requirements.
Page
Installing Avamar Windows Client Software
The following steps demonstrate how to install an Avamar Windows client software:
Step One
Open a web browser and navigate to the Avamar Web Restore by entering
https://<Avamar server hostname>/dtlt/home.html.
Once the page opens, click Downloads to access the Windows client software.
Step Two
Expand Windows (64-bit) and click the Windows client software to download the
.msi file.
Click the downloaded file and choose Run to start with the installation process.
© Copyright
Click to enlarge
Step Three
Once the installer begins, click Next and accept the license agreement. Then, click
Next.
Page
Click to enlarge
Step Four
The Avamar Desktop/Laptop features46 are installed by default on supported

Windows and Mac computers.
By default, the Avamar software on a Windows machine is installed under

C:\Program Files\avs. Click Next to continue.
46This feature provides you the ability to run their own backups and restores. If this
feature is not desired, click the down arrow next to Avamar Client User Interface
and can make the entire feature unavailable.
© Copyright
Click to enlarge
Step Five
During the installation, you are asked to provide server information. This
information is used to activate the current client with an Avamar server. Activating
the client enables the client to perform backup and restore to that server.
You can either activate the client to a server at the time of installation or later. Click
Next and Install to start with the installation.
Page
Click to enlarge
Step Six
You can see the progress of the installation. Once the installation is complete, click
Finish to close the installer prompt.
Windows Client Software Plug-ins
With the installation of client software on a Windows machine, you may notice three
plug-ins appear for the client in the AUI and Avamar Administrator.
These three plug-ins are all included in the Windows client installation and have
different purposes.
© Copyright
Windows File System47 Windows VSS48 Windows Update49
Avamar Administrator View Avamar Web User Interface (AUI) View
47The Windows File System plug-in is used to perform backups and restores of file
system data. It allows backup and restore of individual files.
48 The Windows VSS plug-in is used to backup the entire system state and any
critical disks. This type of backup can be used for bare metal recoveries.
The Windows VSS plug-in also creates VSS snapshots to provide a consistent
point-in-time copy of the volume. You can select this plug-in to perform full system
backups.
VSS is used during backup to handle the backup of open files. You can select the
VSS plug-in when performing regular file system backups.
49The Windows Update plug-in is not used for backups or restores, but for “push”
upgrades from Client Manager. It allows an administrator to remotely update
Avamar client software on the client machine. You should not select this plug-in
when performing any backups.
Page
Client Installation in Multiple Systems
The Avamar Client software can be installed on a large number of Windows or Mac
computers using a systems management tool50.
The systems management tools which are used to remotely push install the
Avamar client software include:
• Microsoft System Center Configuration Manager
• Quest Management Xtensions on Mac
• IBM Tivoli Management Framework
• HP OpenView ServiceCenter
• Symantec Altiris
• Apple Remote Desktop
Important: The steps required to push a software to a set of

computers depends on the tool. Please review the documentation for
the tool to determine the steps.
Launching Avamar Windows Client Interface

Once the avscc process launches automatically, the Dell EMC Avamar Client
applet is placed in the Windows system tray.
50 A systems management tool can remotely push install the software to a large
number of computers in a short amount of time.A systems management tool can
often generate a list of the computers where the software is successfully installed.
You can use this list in Avamar Client Manager to register and activate computers.
© Copyright
You can launch the Avamar Windows Client interface in two ways:
1. Windows System Tray
View Activity Status51 Client Initiated Backups52
Double-
2. Windows Start Menu
If the Avamar client icon is not visible in the Windows System Tray, then you
can start up the avscc by searching for the Avamar client application in the
Windows Start menu.
51You can double-click the Avamar client icon in the windows system tray to view a
quick activity status.
52 You can right-click the Avamar client icon for client initiated backup/restores.
Similarly, you can click Back Up... option to open the Avamar Desktop/Laptop
interface.
Page
Avamar Client Processes and Services (Windows)
While performing a Windows client installation, the Backup Agent, avagent, and
avscc are started automatically.
The Task Manager can be used to verify that the processes are running.
Task Manager:
avagent.exe
avscc.exe
Services:
Backup Agent
Important: The Windows Services application can be used to start,

stop, or restart Backup Agent.
© Copyright
Avamar Client Directory Structure
On an Avamar Windows client, the Avamar binaries, utilities, and log files are
located in C:\Program Files\avs by default.
• bin: Binaries and scripts

• etc: Configuration files
• var: logs for the Avamar client processes: avscc, avagent, and avtar
On an Avamar LINUX client, the Avamar files are located in root folder (/) by
default.
Windows
Linux
Page
Account Management
Account Management
Avamar Domains
Avamar Client Domains are distinct zones that are used to organize and separate
backup clients for administrative purposes. The server provides enhanced security
by enabling you to define administrative user accounts on a domain-by-domain
basis.
Nesting domains within domains allows you to create a hierarchy for managing
organizations and clients within the organizations.
Root
domain
Sub-domain
© Copyright
Account Management
Default and Special Domains
The following are some of the default and special domains that are used in
Avamar:
REPLICATE53 MC_RETIRED54 clients55 MC_SYSTEM56
53The REPLICATE domain contains replicated data from other Avamar servers.
This domain is created once the server receives replication data.
54The MC_RETIRED domain holds clients that have been retired which means
they are no longer being backed up.
55The clients domain is a regular domain that comes preconfigured on the Avamar
server. It can be used for the backup clients.
56The MC_SYSTEM domain holds the Avamar server. Since replication uses client
software that is installed on the Avamar server, the Avamar server itself must
appear in the tree. This domain serves as a container for this client.
Page
Account Management
Important: Of the domains listed here, only the /clients domain can
be deleted.
© Copyright
Account Management
Avamar Users
Security in Avamar is implemented with the help of user accounts.
Users can be added to:

• Domains for administering the domain and any domains within the domain
• Individual clients to perform backup and restore of client data
The privileges assigned to a user determine the tasks that the user can perform in
AUI. Also, the privileges determine the ability of the user to initiate backups and
restores.
Page
Account Management
Avamar User Roles
Roles define the allowable operations for each user account.
There are three categories of user roles which have its own roles:
Administrator Operator User
© Copyright
Account Management
Avamar Users in the Domain Hierarchy
The level at which a user account is added to the Avamar system and the role that
is assigned to the user determine the access and privileges that are assigned to
that user.
Root
Users57
Admin Administrator
Avamar server
Root User Restore Only Operator
Backup Only Operator

Operator
Backup/Restore Operator
Activity Operator
Domain
Users58
Administrator
Avamar Domain Admin
Domain User Restore Only Operator
Backup Only Operator

Operator Backup/Restore Operator
Activity Operator
57Root users are created at the root domain, represented by the Avamar server in
the domain tree.
Root users can perform tasks for all domains in the hierarchy and the clients within
the domains.
Page
Account Management
Client
Users59
Avamar Client Restore (Read) Only User
Client User User Backup Only User
Backup/Restore User
Preconfigured User Accounts
Avamar provides several preconfigured user accounts at the root domain level
which include:
MCUser60 repluser61 backuponly62
58Domain Users are created at the Avamar domain level. Users at the domain level
can perform tasks for that domain, the clients assigned to the domain, and any
domain or client beneath the domain in the domain hierarchy.
59Client Users are created for an individual Avamar client. The tasks a client user
can perform are limited to that specific client.
60 MCUser is used to administer the Avamar server at the root domain level.
61 repluser is an account for replication between two Avamar systems.
62 Backup only user role
© Copyright
Account Management
backuprestore63 root64 restoreonly65
Avamar Administrator View
AUI View
Avamar Authentication
Avamar users are authenticated at login to AUI, Avamar Administrator, Client

Manager, and Web Restore using a username and password.
Users are authenticated with either Internal Authentication or Directory Service

Authentication (LDAP and NIS).
63 Backup/Restore user role
64 Administrator role
65 Restore (Read) role.
Page
Account Management
Type One
ClientUser has access

only to DesktopClient
domain
With Internal Authentication system:

• User names and passwords are maintained in Avamar.
• Use an assigned user account to log in to specific domain in AUI and other
Avamar interfaces.
• Avamar domain names are specified as /domain/sub-domain1/sub-domain2/
An example66 using Avamar Internal Authentication is shown in the image.
66In the example shown in the image, a user is logged in with the ClientUser
account into the /clients/DekstopClient domain. Because the user is a domain
administrator, ClientUser has access to the /clients/DesktopClient domain and any
sub-domains that are created under /clients/DesktopClient. This role gives the user
with administrative, backup, and restore privileges for these domains and clients
within the domains.
However, because the user is not a root domain administrator, ClientUser only has
access to /clients/DesktopClient and its sub-domains.
© Copyright
Account Management
Type Two
Logging in with LDAP

configuration
Click to enlarge
With Directory Service Authentication:

• User name format: username@externalauthdomain
• Password for a particular user is maintained and authenticated by the external
authentication system
• Passwords not maintained in Avamar
• User group must be mapped to correspond with an Avamar domain and role
All users within the user group are granted configured privileges to the Avamar
server.
• Can be configured only in Avamar Administrator
Page
Account Management
• Available in AUI, Avamar Administrator, Avamar Client Manager, and Avamar

Web Restore
• Not available for server-level administration67 and special system administrative
accounts68
67 root, admin, and dpn user accounts
68 MCUser and root
© Copyright
Account Management
Avamar Domain Tree Structure
In Avamar, the domain hierarchy in an AUI and Avamar Administrator is depicted in

the form of a tree structure.
The root domain is represented by:

• Slash (/) in an AUI
• Avamar server name in Avamar Administrator
You can expand the tree to view sub-domains and clients that are assigned to the
domain.
Hierarchical domain
"tree structure"
win01 client belongs to the

/clients/DesktopClient domain
AUI View
Avamar Administrator View
Page
Account Management
Account Management Tasks
Avamar allows you to perform various account management tasks using the AUI.
Add and move a client
Add a domain
Add a user
• Create, edit, and delete domains69

• Create, edit, and delete users70
69 The user must be logged into the root domain with the Administrator privilege.
70 The user must be logged into a domain with the Administrator privilege.
© Copyright
Account Management
• Create, edit, and delete clients71

• Move clients to a different domain72
Important: Account Management tasks can be performed using

Avamar Administrator as well.
Page
Account Management
Account Management Task - Create a Domain
The web version of this content contains an interactive activity.
The following steps must be performed to create a domain in an AUI:

1. From the AUI navigation on the left, click the Asset Management pane
2. Select a location in the tree and click the + icon
3. Enter the name of the domain and other optional details
4. Click OK to create a domain
© Copyright
Account Management
Account Management Task - Edit a Domain
OR
Follow the steps to edit a domain using AUI:

2. Select a domain, and choose Edit Domain option in the DOMAIN ACTIONS
pane
You can also edit a domain by clicking the overflow button next to the domain
name and select Edit Domain.
3. Edit the information and click OK
Page
Account Management
Account Management Task - Delete a Domain
When you delete a domain, all clients that are associated with the specific domain
are deleted.
If you use directory service authentication, Avamar removes the LDAP maps that
use that domain for access.
OR
Follow the steps to delete a domain using AUI:

2. Select the domain and choose the Delete Domain option in the DOMAIN
ACTIONS pane
You can also edit a domain by clicking the overflow button next to the domain
name and select Delete Domain.
3. Click Yes to confirm the delete operation
Warning: To preserve the clients and their backups in the system,

you must move the clients to a new domain before performing a
deletion.
© Copyright
Account Management
Avamar Management Task - Create a New User
Follow the steps to create a user using AUI:

1. From the AUI navigation pane, click >> and click the Setting pane
2. In the Setting pane, click the User tab
3. Select the domain for the new user and click Add
4. From the User Management window, select an authentication system
5. Enter the username and password, and select a role for the user from the list
6. Click OK to create a user
Page
Account Management
Avamar Management Task - Edit a User
Edit the Role Edit the Password
Follow the steps to edit the user information using AUI:

1. From the AUI navigation pane, click >> option
3. Select the user from the domain
4. To change the role for the user click Edit, select a role for the user, and click
OK
5. To change the password for the user, click Edit Password and enter the new
password
6. Click OK to reflect the changes
© Copyright
Account Management
Account Management Task - Delete a User
Follow the steps to delete a user using AUI:

1. From the AUI navigation pane, click >>, and click Setting
3. In the domain tree, select the domain and respective user
4. Click Delete and click Yes to confirm the deletion
Page
Account Management
Managing Directory Services
An Avamar server must be configured first to authenticate with the directory service
in order to use a directory service authentication.
The following are some of the important notes about directory service
authentication:
• Can be configured from the Administration interface in Avamar Administrator
• Not available in Avamar Web User Interface (AUI)
• Edits the necessary LDAP and kerberos configuration files to allow
authentication
• NIS authentication is also supported
Click to enlarge
The following steps allow you to add a directory service:

1. Select LDAP Management tab from the Administration interface in Avamar
Administrator
2. Click Directory Service Management
3. Click ADD to enter the fully qualified domain name and directory service type
4. Click Add
5. Click Yes to confirm
© Copyright
Account Management
The Desktop Laptop (DTLT) service is restarted as a part of this procedure.
Create an LDAP Group
In order to allow an LDAP access, you must create a user group. You may have to
create multiple groups to grant access to different Avamar domains or different
roles depending on the requirements.
Click to enlarge
The following steps allow you to create an LDAP group and add a user:
1. Open the Active Directory Users and Computers application
2. Select Users
Page
Account Management
3. Click Action > New > Group

4. Enter a group name, and click OK
5. Right-click the user and select Add to a group..
6. Find the group name and click OK
Adding an LDAP
An LDAP map73 must be created to allow LDAP users to access Avamar. When an
LDAP map is configured, all users who are assigned to the group have access to
an Avamar domain as defined by the user role.
You can add an LDAP map in the Administration interface of Avamar

Administrator. The map must be created in the Avamar domain or client to which
the users have access. When creating an LDAP map, select the LDAP group
created previously and assign a user role.
73LDAP map is an association between an LDAP user group and an Avamar

domain and role.
© Copyright
Account Management
Click to enlarge
The following steps allow you to add an LDAP map:

1. Select LDAP Maps under Account Management tab in the Administration
interface
2. Select the root domain and click Actions > Account Management > New
LDAP Map...
3. Search for a group created early and assign a role to the group
4. Click OK to add the LDAP map
Page
Account Management
Registering Avamar Client
An Avamar client must be registered74 and activated with Avamar server before
performing any backup or restore of the data.
Client Client Client
Server Server Server
Client registered to a server Client registered to a different server
There are multiple ways to register an Avamar client:
Client-side registration and activation75
74Registering an Avamar client establishes an identity with the Avamar server.

Once Avamar knows the client, activation can occur that assigns a unique client ID
(CID), which passes back to the client during activation. A client can be registered
and activated only on one Avamar server at a time. Activation to multiple Avamar
servers is not supported.
© Copyright
Account Management
Server-side registration76
Batch client registration77
Client Manager78
75 With Client-side registration and activation, the registration is initiated from the
client which may have already been done during the client software installation
process. If not, register after installing the client software.In Windows, the installer
can initiate registration by right-clicking the Avamar client (avscc) tray icon and
choosing Manage > Activate Client.In Linux and UNIX, you may run the avregister
command that is located in the Avamar software bin directory. Both of these
methods also activate the client simultaneously.
76Server-side registration of an Avamar client can be done using AUI and Avamar
Administrator. In this way, you can add the client to an Avamar system in the
desired domain.
77Batch client registration is used to define multiple clients using a single client
definition file. The file is then imported to the Avamar server to register them.
78Avamar Client Manager is a centralized client management interface which can

be used to activate clients with an Avamar server.
Page
Account Management
Inviting Avamar Clients to Activate - AUI and Avamar

Administrator
AUI View Avamar Administrator View
Clients can be activated from the Avamar server using:
• AUI79
• Avamar Administrator80
79
To activate a client using AUI, select the client under a domain and click MORE
ACTIONS > Invite Client.
80To activate a client using Avamar Administrator, after the client is added to a
domain, select the client and choose Actions > Account Management > Invite
Client.
© Copyright
Account Management
Important: In order for activation to succeed, the client must be

present on the network, the client software must be installed and
running, and the Avamar server must be able to resolve the hostname
that is used to register the client.
Activating Clients - Windows and Linux
During the activation of a Windows or Linux/Unix client, the domain must be

existing and the capitalization must be matching to ensure that the activation of
client is completed successfully.
Windows
In Windows, once the client software is installed, you can activate the client by
right-clicking the Avamar client (avscc) tray icon and choosing Manage >
Activate.
Linux and UNIX
In Linux and Unix, the client registration process using the avregister command
also activates the client.
Page
Account Management
© Copyright
Account Management
Client ID and Activation Status
During the activation process, the Avamar server passes the client ID (CID) to the
client. The client ID is stored in an encrypted file on the client file system.
A client can only be activated81 to one Avamar server at a time.
The details of the client can be viewed in the VIEW MORE option after selecting
the client.
81 To activate a client with another Avamar server using Avamar Administrator,

from the Policy view > Policy Management tab > Clients tab, select the client’s
domain in the tree, then select the client in the right-hand pane and click Edit.
Uncheck the Activated box. Then, you can activate the client with the other Avamar
server either from the client machine or from Avamar Administrator when logged
into the other Avamar server.
In order to activate a client another Avamar server using AUI, you need to navigate
to Asset Management and select the client under a domain. Then, you need to
select MORE OPTIONS and click Edit Client. You need to uncheck the Activated
box. Then, you can activate the client with the other Avamar server either from the
client machine or from AUI when logged into the other Avamar server.
Page
Account Management
Activating Clients Using Avamar Client Manager
Avamar Client Manager provides a centralized facility for activating clients with an
Avamar server.
Avamar Client Manager allows you to:

• Populate list of clients by either importing a client list or querying a defined
directory service.
• Drag and drop clients to specific Avamar domains and policies.
• Initiate the registration and activation of clients.
© Copyright
Account Management
Account Management for Clients - AUI and Avamar

Administrator
Administrators can perform additional tasks with clients from the AUI or Avamar
Administrator Administration interface.
The following tasks can be performed on a client:
Edit Client82 Move Client83 Retire Client84 Delete Client85 Invite Client86
82 The Edit Client option can be used to change the client name and optional
descriptive information. It also allows the administrator to enable, activate, and
initiate any client backups.
83 The Move Client option is used to move a client to another domain.
84 Retiring a client is less destructive than deleting a client. Retired clients do not
participate in regular backups, however, previous backups are still maintained and
files can be restored using a directed restore. All the retired clients are moved to
the MC_RETIRED domain.
If the client has been replicated to another Avamar server, you may optionally
change the retention times of the replicated backups as well.
85 The Delete Client option permanently deletes all backups that are stored that are
for the client. If there is any chance that you want to restore data from this client,
retire the client instead.
86 The Invite Client option is used to register and activate a client.
Page
Account Management
AUI View Avamar Administrator View
Disabling Client Backup
You can disable a client backup from the AUI and Avamar Administrator. When a
client is disabled, it cannot use the Avamar server to backup any files.
Disable Client in AUI
To disable a client in AUI:

• Select a client which is registered to a domain
• Click MORE ACTIONS, and then click Edit Client
• Uncheck the Enabled box, and click UPDATE
Result: Disabled client has false value under the Enabled column.
© Copyright
Account Management
Disable Client in Avamar Administrator
To disable a client from Avamar Administrator:

• Choose Policy > Policy Management tab > Clients tab
• Select the client in the tree, then choose Actions > Client > Disable all
backups of selected client
Note: Disabled clients have an X placed next to their icon when the client is
displayed in the tree.
Important: You cannot initiate any backup, restore, replication, or

cloud tier when a client is diabled.
Page
Account Management
Account Management for Clients - Avamar Client Manager
All additional tasks that are performed on a client in the AUI and Avamar
Administrator can also be performed from an Avamar Client Manager87.
Clients can also be moved from one Avamar server to another.
87 Avamar Client Manager is useful for managing large number of clients.
© Copyright
Account Management
Using the MCCLI Command
The MCCLI is a Java software application that provides command-line access to

the features and functions88 available in an AUI or Avamar Administrator.
The MCCLI is installed on the Avamar server utility node during server installation
and can be run from a command line89 on the utility node.
Shown below is an example of listing the available domains in an AUI or Avamar

Administrator using the mccli domain show command.
88Most of the tasks that can be performed in an AUI or Avamar Administrator can
also be performed from the command line with MCCLI.
89 The user must have a valid Avamar Administrator credential in order to connect
to an Avamar server using the MCCLI.
Page
Account Management
MCCLI
Avamar Administrator View AUI View
© Copyright
Account Management
Best Practices: Domains, Users, and Clients
Following are some of the best practices to keep in mind when planning for the
Avamar domains, users, and clients in an Avamar environment.
Minimize the number of domains for easy Use only /clients domain if Manage users and
management additional domains are not needed password
Do not place clients in the root

domain Take advantage of a hierarchical 1. Create an account with appropriate
domain structure to separate privileges for each user of the Avamar
interfaces
clients when:
This creates hassle in future system migration 2. Do not use MCUser user ID
1. Using domain-level administrators for management and security
2. Separating clients for management
Page
Account Management
Adding a Data Domain System Using AUI
You can integrate a Data Domain using Avamar Web User Interface (AUI).
The following steps demonstrate how to attach a Data Domain with Avamar using
AUI.
Step One
Log in to the AUI with the credentials.
Step Two
Once logged in, expand the

navigation pane and select System.
Click Data Domain tab and click
ADD.
Step Three
Under the System tab, enter the Data Domain system name and DD Boost
credentials, and, then, click VALIDATE.
Once validated, click NEXT.
© Copyright
Account Management
Step Four
Under the SNMP tab, enter the SNMP Community String and click NEXT.
Keep the default setting under Tiering tab and click FINISH to attach the Data
Domain.
Page
Using Client Manager
Avamar Client Manager Overview
Avamar Client Manager is a web-based management application that provides

centralized administration of many Avamar clients. The Avamar Client Manager
can analyze both failed and successful backups and restores. The Client Manager
also is capable of pushing client software upgrades.
The Avamar Client Manager has the ability to:
• Activate
• Move
• Upgrade
• Retire
• Delete
• Change Group Associations
The login page authenticates the username and the password with administrator
accounts that are registered on the Avamar server. Avamar Client Manager only
allows access for accounts with administrator privileges on the Avamar server that
is running the Avamar Client Manager process.
© Copyright
Avamar Client Manager for Multiple Avamar Servers
The Avamar Client Manager software runs on the Avamar utility node. Users can
register multiple Avamar servers with a single instance of Client Manager so they
all appear in one interface. This makes managing multiple systems easier, and also
enables features such as migrating clients from one Avamar server to another.
From the Server Summary screen, click Add Server and provide the Avamar
servers hostname or IP, then enter the MCUser account password to add the new
server.
Page
1:
© Copyright
Client Filtering
The Client Manager uses multiple filters. Different types of clients can be selected
from the panel on left in the interface. Further filtering can be applied from the
Filters bar at the top of the window.
2
3
1: With Registered Clients the filters available are Operating System (OS), Client
Status, and Client Name.
Under the Client Status, you can filter by Activation failure or Pending
response.
The Client Name drop-down allows you to put in the name of the client the Client
Manager examines.
In the Registered Clients section, you can perform the following client-related
tasks:
• Activate or Delete clients

• Associate with groups
• View and edit details
• Add and remove group override settings
Page
2: Selecting Failed Clients from the left panel shows the clients that have had
failures. The clients can be further filtered by selecting a date range of when those
failures occurred.
The Period and Activity filter specifies the period that Client Manager examines.
The Failure Criteria defines the threshold that is used by the Client Manager.
In the Failed Clients section you can perform the following tasks:
• Delete a client
• Manage a client's group associates
• View and edit a client's details
3: Selecting Idle Clients, from the left panel show clients that do not have any
backups. These clients can be further filtered by selecting a date range of when
those clients. Idle Clients, uses the Period filter to specify the period that the
© Copyright
Client Manager examines for activity, and the Activity Type filter uses the specific
type of activity to filter.
In the Idle Clients section, you can perform the following tasks:
• Delete a client
• Manage a client's group associations
• View and edit a client's details
Managing Clients with Avamar Client Manager
The Client Manager provides tools for managing clients within Avamar. These tools
can move clients to a new server, move clients to a new domain, delete or retire
clients, activate clients, and modify groups.
3 4 5 6 7
1
1: The Clients section will open up the menu for Add Clients, Registered Clients,
Activated Clients, Failed Clients, Idle Clients, and Upgrade Clients.
Page
2: Activated Clients panel gives the ability to move clients between Avamar
servers or domains, retire, delete clients, modify groups, and edit client details.
3: Users can change the Avamar client and an Avamar server. By moving the client
to a different Avamar domain or a new one.
Select a client, and then in the Actions bar, click Move. The Client Move dialog
appears as shown here.
In the Domain Section pane select a target domain and click Next. Then select a
new group or create another new group. Click Finish.
4: Avamar Client manager can also retire a client whose backups are no longer
needed.
The Retire menu allows you to select more than one client and the retention policy
setting allows the selection to apply to all selected clients.
© Copyright
Option Description
Retire client and retain backups with The Avamar server retains the backups for
existing expiration date the existing retention period
Retire client and retain all backups The Avamar server retains the backups
indefinitely until you manually delete them
Retire client and reset backup The Avamar server retains the backups
expiration date until the date set in New Expiration Date
5: To remove the backups of a client from an Avamar server, delete the client from
the server. When the Avamar Client Manager deletes a client, it stops all activities
with that client, delete the client's backups, and removes all records of the client
from the server's database.
Page
6: Group Association shows the policies applied to that client as well as view or
add groups that include the client.
In the Dataset, Schedule, and Retention columns, select any of the blue links for
more details.
7: View/Edit Details show more details about the client and is similar to the Edit
Client window in the Policy interface of Avamar Administrator. Here you may
disable backups of the client, temporarily deactivate the client, and edit end-user
permissions for Desktop/Laptop.
The Summary tab shows information about the client, also a list of users who are
associated with the client.
The Backups tab shows the backup history associated with On-Demand,
Scheduled, and From and To filters.
The Plug-ins tab shows the Avamar plug-ins that are installed on the client.
The Advanced tab allows for overriding, disabling, allowing client-initiated

backups, file selection for client-initiated backups, allow client to add files to
datasets, allow client to override daily group schedules, and allow client to override
retention policies on client-activated backups.
© Copyright
Moving a Client to a New Avamar Server
Step One
With the Avamar Client Manager, administrators can move the clients registration,
activation, and backups to a new Avamar server.
From the left-side menu, click Clients and select Activated Clients.
Page
Step Two
Select a client under the Client pane. Do not select an NDMP client or a client that
has backups on a Data Domain server.
Step Three
From the Actions bar, click Move. The Domain Selection pane of the Client
Move dialog box appears.
© Copyright
Step Four
From the top of the Domain Selection pane, the server selection drop-down list,
select the Avamar server that is the target of the move and click Next.
Step Five
In the Group Selection pane, select the target domain. You can optionally select
more than one target group.
Page
In the Replicate Existing Backups at the bottom of the Group Selection Pane,
select a value. Then click Finish.
• All: Replicate all the clients backups to the target server

• Last: Replicate only the last backup
• None: Replicate none of the backups
Optionally, in the Delete From Source can be checked to remove all the clients
backups from the source server. Then click Finish.
Step Six
The Confirm Replication Authentication dialog box appears.
In the Source Server, type the password for the repluser account on the source
server.
In the Target Server, type the password for the repluser account on the target
server
© Copyright
Click OK.
The Avamar Client Manager moves the client to the selected target.
Page
Preparing a Client List
Preparing a Client List With Avamar Client Manager
As an alternative to using a directory service to provide client information to Client

Manager, you can import a client list90 file.
• Fully Qualified Domain Name (FQDN).

• Directory service logical group name; in LDAP and Active Directory, this is the
client’s organization unit (optional value).
This list91 must be available on the machine running the Client Manager web
browser.
90 The client list file is a plain text, comma-separated value (CSV) file containing up
to two values for each client.
91This list can be manually created, or you can create it by using the output of a
systems management tool such as the Microsoft System Center Configuration
Manager or the Microsoft Systems Management Server.
© Copyright
Activating Clients in Avamar Client Manager
Avamar Client Manager can be used to activate Avamar for desktops and laptops
and for other systems, such as enterprise servers. Before activating the clients with
Client Manager, install the Avamar Client software on the client machine.
Avamar Client Manager populates a list of clients by either querying a defined

LDAP-compliant directory service or by importing a CSV client list.
Step One
To activate a client from the Avamar Client Manager, click Add Clients from the
Clients section in left panel.
Step Two
Click New Clients. You can enter directory service authentication information, or
browse for a .CSV file containing a client list.
The Client Information source opens, enter the username and password, and
click OK.
Page
Step Three
In the Summary window, a list of all clients in the LDAP domain appears. Select a
client for activation and click Activate.
Step Four
In the Server-Domain Selection, select a domain. You can also create a new
domain by clicking the Create Domain button.
© Copyright
Step Five
From the Server - Group Selection, choose a backup group. You can also create
a new domain or a new group. However, you can only select the datasets,
schedules, and retention policies that have been previously created. Click Finish to
activate.
Page
Step Six
The activation occurs as a background process. Click OK.
Step Seven
If the client is not available during the activation request, the activation job is
queued and retried every two hours for the next two days.
Queued jobs can be viewed and optionally canceled from the Queues section from
the left panel.
© Copyright
Page
Avamar Backups
Avamar Backups
Scheduled Backups
Avamar Backup Types
Avamar backups can be categorized into Scheduled and On-Demand.
Scheduled92 On-Demand93
92Scheduled backups are run automatically according to specifications that can be

customized by the administrator using the AUI or Avamar Administrator.
93 On-Demand Backups are the types of client backups that are initiated instantly.
On-Demand Backups can be initiated from the AUI, Avamar Administrator, and the
Management Console Command Line interface (MCCLI).
On-demand backups can also be run from a client machine using the Avamar
Client, Avamar Desktop Laptop interface, and with the avtar command from the
command line.
© Copyright
Avamar Backups
Scheduled Backups
Backup Policy
Avamar uses backup policies for automating backups and enforcing consistent
rules across a collection of clients.
Backups are scheduled to run automatically by configuring and enabling the

backup policy.
The following are the components of a backup policy:
Dataset94 Schedule95 Retention96 Clients97
94Datasets define the persistent backup selections for the file systems, directories,
or files that are in a backup. You can also narrow the scope by specifying certain
content, such as file types, to exclude or include.
Datasets can be created at any domain level and can be assigned to one or more
policies and clients within the assigned domain.
Page
Avamar Backups
95The Schedule for a group determines when and how often a backup will
automatically run.
Schedules can be created at any domain level and can be assigned to one or more
policies within the assigned domain.
96Retention Policies specify how long each backup is retained. Any backups older
than the specified retention are automatically dropped from the system.
Retention policies can be created at any domain level and can be assigned to one
or more policies and clients within the assigned domain.
Note that the retention policies can still be reused even if the client is deleted or
retired.
97 Avamar client is a device from which files can be backed up or a device to which
files can be restored. Typically this is a laptop, desktop, server, or a virtual
machine.
© Copyright
Avamar Backups
Creating a Dataset
A single dataset definition can use more than one plug-in type. When backing up,
Avamar uses the appropriate plug-in type based on the client definition98.
The following steps show how to create a dataset:
Step One
Log in to the AUI, and go to Setting pane.
Note: Add the dataset to a domain.
Step Two
Select the Dataset tab, and click +ADD.
98 Usually, you have to use the default dataset to back up all local file systems for
all clients. However, there may be instances where you must create a dataset to
define specific persistent requirements.
Page
Avamar Backups
Step Three
In the Create Dataset page, enter the following information, and click SUBMIT.
• Dataset Name99
• Plugins100
• Options101
99 Provide a name for the dataset.
100 Select the types of plugins that need to be part of the backup policy.
101Selecting a plug-in enables the options available for the specific plug-in. A single
dataset can include options selections for more than one plug-in type.
Options can be selected from the items presented in the AUI or entered as
attribute/value text. For example, you can enter a label for the backup by supplying
a value for the Backup label attribute in the AUI.
© Copyright
Avamar Backups
• Source Data102
• Inclusions103
• Exclusions104
There are other options like backup storage on the Data Domain system as well.
Checking Show Advanced Options expands the list of options displayed to include
options that may be of interest to those troubleshooting or fine-tuning the system.
For example, if you are troubleshooting a problem with a specific backup, you may
want to enable debugging messages for a period of time.
102On the Source Data tab, identify the data backed up by this dataset
specification. You can choose to either select all data for all local file systems or to
enter explicit file systems, directories, or files per plug-in type.
If entering explicit items, the default all local file systems entry for that plug-in type
is removed.
Similarly, clients create a backup for every plug-in installed on the client, if those
plugins have been specified in the same dataset.
103The Inclusions tab specify the items that you want to include in the backup. Be
sure that the correct plug-in is selected from the list.
104 The Exclusions tab specify items to exclude from the backup dataset specified
in Source Data. Be sure to select the correct plug-in.Also, the exclusions only apply
to the plug-in selected when adding them to the list.
Page
Avamar Backups
Best Practices: Datasets
The following list specifies some of the best practices while using a dataset:
Minimize the number of datasets
- One dataset can be used to backup all types

of platforms.
- Input different retentions for different subsets of data. Do not configure more
than one dataset per
- Input different subsets of data to be backed up
client
on different days of the week.
© Copyright
Avamar Backups
About Schedules
Schedules determine when and how often a backup is automatically run.

Schedules are also used to determine when custom event profile email notifications
are sent.
Schedules that are created at the root domain level can be assigned to any backup
policy throughout the hierarchy.
The following preconfigured schedules are defined at the root domain level in
Avamar:
Daily Schedule105 Default Replication Default Default Tiering

Schedule106 Schedule107 Schedule108
105Daily Schedule is configured to run once every day. It is initially configured

similarly to the default schedule.
106Default Replication Schedule is used for replication jobs. It is set to run daily at
11 PM.
107 The Default Schedule is assigned to the Default Group. It is initially configured
to run once a day with the earliest start time of 10 P.M. US Pacific time for a
maximum of 8 hours.
108 Default Tiering Schedule is for the Cloud Tier feature.
Page
Avamar Backups
Evaluation Notification Schedule110 Override Daily

Schedule109 Schedule111
109Evaluation Schedule controls when the Evaluation Profile email notification is

sent.
110
Notification Schedule controls when custom event profile email notification
messages are sent.
111
Override Daily Schedule is used to define the available start times for Avamar
Desktop Laptop clients that have overridden their normal schedule.
© Copyright
Avamar Backups
Recurrence Types
The recurrence types in Avamar schedules are of various types, including Daily,
Weekly, Monthly, and On-Demand112.
Daily
If Daily schedule is selected, the policies associated with the schedule run on a
daily basis.113
Weekly
If Weekly is selected, the policies associated with the schedule run on a weekly
basis114.
112On-demand schedules will never run. Theses schedules are typically assigned
to backup policies that run on-demand.
113If the Daily recurrence type is selected, then the backup jobs are repeated every
day at one or more times of the day.
With daily schedules, you must also limit the duration of the activity to prevent job
overlap.
Page
Avamar Backups
Monthly
If Monthly is selected, the policies associated with the schedule run on a monthly
basis115.
114
If the Weekly recurrence type is selected, then the backup job is repeated every
week on one or more days of the week.
With weekly schedules, you must also define the earliest start time for the activity,
as well as the time at which the activity is stopped, even if it is still in progress.
115If the Monthly recurrence type is selected, the backup jobs repeat on a specific
calendar date or on a designated day of the week each month, such as the first
Sunday of every month.
With monthly schedules, you must also define the earliest start time for the activity,
as well as the time at which the activity is stopped, even if it is still in progress.
© Copyright
Avamar Backups
On-Demand
The On-Demand schedules will never run. Schedules of this type are typically
assigned to policies that are only run on-demand.
Time Basis for Schedules
The times displayed when editing or creating a schedule, and the times displayed
in the AUI and Avamar Administrator interfaces, are in the local time zone.
The following time zones are used by various Avamar components:

• Time basis for the Avamar server utility node116 is the local time where the
Avamar server resides.
• Time basis for the Avamar storage nodes/AVE, administrator server database,
and reports is GMT.
• Time basis for an Avamar client117 is in local time of client machine.
116 Includes administrator server
117
The time that is displayed in most client log files is the local time of the client.
However, there are some client log files that are time/date-stamped in GMT.
Page
Avamar Backups
Pacific Time Mountain Time Central Time Eastern Time
AUI or
Avamar Avamar Avamar
Server Client Administrator
Interface
11.00 P.M. 12.00 A.M

10.00 P.M. Monday 1.00 A.M. Tuesday
Monday
Operational Windows
Avamar divides each day into two operational windows during which various
system activities are performed.
Backup118 Maintenance119
118The Backup window defines the period of time the Avamar server reserves for
performing regular, scheduled backups. During the Backup window, the Avamar
server does not run any server maintenance activities.
By default, the Backup window is configured to start at 8 P.M. and end at 8 A.M.
You need to configure all backup schedules used to run backups to start, run, and
complete during the period of time that is defined by the Backup window. Also,
avoid creating any schedules that extend into the Maintenance window, as backups
that are running cause garbage collection performance to drop.
119 The Maintenance Window is reserved only to perform maintenance activities on

Avamar with the Data Domain system. During the Maintenance window, the
Avamar server that is integrated with Data Domain runs a checkpoint, garbage
collection, checkpoint validation (HFS check), and a final checkpoint.
© Copyright
Avamar Backups
Important: The start times and duration of the operational windows

can be customized120 to meet specific site requirements.
120 However, the customization should be done cautiously, as any changes made
to the windows have the potential to negatively impact server maintenance
activities.
Page
Avamar Backups
Allowing Overtime
The benefits of having the overtime feature on a client include:

• Attribute automatically set to Overtime until successful backup121
• Attribute automatically changed to No overtime allowed122
121The Overtime attribute for a client is set automatically to Overtime until

successful backup when a client registers with the Avamar server.
122After the first successful backup for the client, the Overtime attribute is changed
automatically to No overtime allowed.
© Copyright
Avamar Backups
• Set the Overtime attribute to Overtime on next backup only123

• Set the Overtime attribute to Always allow overtime 124
Define a Schedule
The following steps show how to define a schedule:
Step One
123 If you are running a full initial client backup where the time to complete the
backup could potentially exceed the schedule duration period, set the Overtime
attribute to Overtime on next backup only. This allows the backup to run beyond
the duration period.
124 When overtime is allowed, the duration settings on a schedule are ignored,
allowing scheduled backups to run as long as necessary to complete.
Page
Avamar Backups
Step Two
Select Schedule tab, and click +ADD.
Note: Add the schedule to a domain.
Step Three
Under the Basic Configuration tab, enter the following information, and click
NEXT.
• Schedule Name
• Backup Window
• Retention Type
Step Four
Under the Recurrence Pattern tab, provide the recurrence pattern for the schedule
based on the recurrence type selected, and click NEXT.
Note: The information entry varies based on the recurrence type selection.
© Copyright
Avamar Backups
Step Five
Under the Activities Constraint tab, provide the schedule start and end time, and
click NEXT.
Step Six
Review the summary of the schedule configuration under the Summary tab, and
click FINISH.
Note: The information entry varies based on the recurrence type selection.
Page
Avamar Backups
Best Practices: Schedules
The following list specifies some of the best practices while using a schedule:
- Do not overlap with

maintenance window
- If clients require backup during the day
- Do not exceed 8 to 10 hours per day
Run backup towards

Use a single backup end of Maintenance
schedule wherever window
possible
Set appropriate Change

expectations Backup/Maintenance
window if needed
- How long the longest
backups should run every night - If majority clients need to
backup during the day
Best Practice: Scheduled backups may not occur during daylight

savings time transitions125.
125If a backup is scheduled to begin from 2:00 AM to 2:59 AM during the spring
transition, or from 1:00 AM to 1:59 AM during the autumn transition, the backup
does not begin.
It is always recommended to avoid scheduling backups to start during these hours.
© Copyright
Avamar Backups
About Retention
Retention Policies specify how long the backup is retained. Any backups older than
the specified retention are automatically dropped126 from the system.
Retention policies can be created at any domain level and can be assigned to one
or more groups and clients within the respective domain/sub-domain.
The following preconfigured retention policies are defined at the root domain level
in Avamar:
Default End User On Minimal Monthly Weekly

Retention127 Demand Retention129 Retention130 Retention131
Retention128
126 The actual deletion of backup data from the system depends on several factors,
including whether the data is referenced by another backup that has not yet expired
and the garbage collection cycle.
127Default Retention is assigned to the group, Default Group. It is configured with

an expiration period of 60 days.
128End User On Demand Retention is a special policy that controls how long on-
demand backups that are initiated by the client are kept in the system. This policy
only applies to server-class operating systems that use the Back Up Now menu
option. It does not apply to on-demand backups initiated from DTLT.
129Minimal Retention is a special retention policy that controls the minimal retention
feature. When enabled, this retention enforces a minimum level of retention across
an entire site. By default, this retention type is disabled.
130 Monthly Retention has an expiration of one month.
Page
Avamar Backups
Define a Retention Policy
The following steps show how to define a retention policy:
Step One
131 Weekly Retention has an expiration of one week.
© Copyright
Avamar Backups
Step Two
Select Retention tab, and click +ADD.
Note: Add the retention to a domain.
Step Three
In the Add Retention Policy page, enter the following information, and click SAVE.
• Retention Name
• Retention Period (if selected)
• End Date Period (optional)
• No end date (optional)
Note: If you check Override basic retention policy for scheduled backups
option, then you need to enter customized retention period.
Page
Avamar Backups
Best Practices: Retention
The following list specifies some of the best practices when planning for a retention
policy:
- Set the minimum retention period to at least 14

days - Changing retention policy do not
- Prevent cache files from becoming invalid, ensure client change retention of past backups
has backup to restore
Ensure last successful backup Plan and implement retention

does not expire before a new policies before taking
backup production backups
Use advanced retention policy

whenever possible
- Works well with daily backups
- Helps to reduce the amount of

backup storage used
© Copyright
Avamar Backups
Pre-Configured Backup Policies
Within the root domain, Avamar includes two preconfigured backup policies:
Default Group132 and Default Proxy Group133.
AUI View Avamar Administrator
Creating a Backup Policy
The following steps show how to create a backup policy:
132The Default Group automatically includes all new clients, if no other groups
have been configured.
The Default Group always uses the system default dataset, schedule, and retention
policy. This cannot be changed; however, the specifications of the default dataset,
schedule, and retention can be changed.
By default, this group is disabled.
133The Default Proxy Group is also a preconfigured backup policy and is used to
support VMware Image Proxy clients.
The RUN option in the AUI initiates a backup job on demand. By default, this group
is disabled.
Page
Avamar Backups
Step One
Log in to the AUI, and go to Backup Policy pane.
Step Two
Select a domain where you need to create a backup policy, and click +ADD.
Step Three
Under the Properties tab, enter a name for the backup policy, and mark check for
the Enabled option, and click NEXT.
© Copyright
Avamar Backups
Step Four
Under the Members tab, include a client that needs to be backed up, and click
NEXT.
Step Five
Under the Dataset tab, select a dataset based on the backup requirement, and
click NEXT.
Note: You can include Windows VSS and Windows SQL if needed.
Page
Avamar Backups
Step Six
Under the Schedules tab, select a specific schedule based on the schedule
requirement, and click NEXT.
Step Seven
Under the Retention tab, select a retention, and click NEXT.
© Copyright
Avamar Backups
Step Eight
Under the Summary tab, you can review the summary information of the backup
policy and click FINISH to create a backup policy.
Note: Avamar provides you an option to Override Dataset in the summary page.
Scheduled Backup Using Backup Policy
Once the backup policy is created, the backup job is initiated automatically based
on the schedule that is associated with the backup policy.
Page
Avamar Backups
Important: You can also initiate an on-demand backup of a backup

policy using the RUN option.
Best Practices: Backup Policies
The following list specifies some of the best practices when planning for a backup
policy:
By default, all activated clients are

members of /Default policy which may
result in automatic backups
Minimize the number of
groups Add clients to the appropriate enabled
backup policy
A separate group is not needed for each Leave the /Default

OS platform type of client backup policies disabled
© Copyright
Avamar Backups
On-Demand Backups
Running On-Demand Backups - Interfaces
On-demand backups by definition are run manually at the time the backup request
is initiated. The on-demand backup can be initiated from different interfaces.
On-Demand Backup
Avamar Web User Interface

Client Initiated MCCLI Avamar Administrator
(AUI)
Avamar Windows Client

Asset Management View Backup and Restore
Interface
View
Backup Policy View avtar command Policy View - Backup

Group Now
Policy View - Backup

Client Now
Running On-Demand Backup - AUI
Avamar allows you to initiate an on-demand backup of a client or a backup policy

using AUI.
On-Demand Backup of a Client
The following steps show how to initiate an on-demand backup of a client using
AUI:
1. Log in to the AUI, and go to Asset Management pane.
2. Select the client that is registered to a domain.
3. Click BACKUP to initiate an on-demand backup.
Page
Avamar Backups
On-Demand Backup of a Backup Policy
The following steps shows how to initiate an on-demand backup of a backup policy:
1. Log in to the AUI, and navigate to Backup Policy pane.
2. Select the backup policy, and click RUN to initiate an on-demand backup of a
policy.
© Copyright
Avamar Backups
Important: You can initiate an on-demand backup of VMware,

Exchange, and SQL clients134 in a similar manner.
Running On-Demand Backup - Client Initiated
On-demand backups can also be initiated by the end user from an Avamar
Windows client using the Avamar Client (avscc), Avamar Desktop Laptop interface,
or with the avtar command.
Avamar Client
The following steps show how to initiate an on-demand backup of a client using an
Avamar client:
1. Right-click Avamar client icon from the system tray
2. Click Back Up Now
Result: The Back Up Now option135 initiates a backup in AUI or Avamar

Administrator.
134All the client plug-ins must be installed, registered, and activated to the Avamar
server before initiating a backup.
135 This option works even if Avamar Desktop Laptop is not installed.
To perform this operation, the client initiated backups option must be enabled in the
client.
Page
Avamar Backups
Avamar Desktop Laptop
With the Avamar Desktop Laptop interface, the end-user is limited to performing
on-demand backups of the dataset assigned to the client’s policy136 only.
The following steps shows how to initiate an on-demand backup of a policy using
an Avamar Desktop Laptop:
1. Right-click Avamar client icon from the system tray
2. Click Back Up...
3. Under Backup tab in Avamar Desktop Laptop, select a policy, and click Back
Up Now.
136If the client is assigned to multiple policies, then the end-user can choose which
group policy to be backed up.
© Copyright
Avamar Backups
History tab displays 10 most

recent activities
avtar
avtar137 is the Avamar executable that runs on the client and is used to backup and
restore files.
The following list shows the location in different clients where the command can be
executed:
• Server utility node: /usr/local/avamar/bin
• LINUX/UNIX clients: /usr/local/avamar/bin
• Windows clients: C:\Program Files\avs\bin
137The avtar command can be run from a command line on the client to perform a
backup.
Page
Avamar Backups
Running On-Demand Backup - Avamar Administrator
Avamar allows you to initiate an on-demand backup of a client and a backup policy
using Avamar Administrator Backup and Restore or Policy interfaces.
Backup and Restore View
Avamar allows you to initiate an on-demand backup from the Backup and Restore
view in an Avamar Administrator.
The More Options138 is used to specify plug-in options with the backup.
138Options that are displayed are similar to those displayed when configuring a
dataset specification. Most often you want to set the retention period for each on-
demand backup, a name for the backup, and, if running the backup for
troubleshooting purposes, then run with statistics and diagnostics.
© Copyright
Avamar Backups
Policy View - Backup Group Now
Avamar allows you to initiate an on-demand backup of a backup policy using an

Avamar Administrator Policy view.
OR
Page
Avamar Backups
Policy View - Backup Client Now
Similarly, Avamar allows you to initiate an on-demand backup for a specific

client139.
Running On-Demand Backup Using MCCLI
The MCCLI command allows you to initiate an on-demand backup of a client as

well as a backup policy.
Here are two examples:
139You need to select a client and then click Back Up. Then, select a specific
backup policy with a dataset that needs to be initiated.
© Copyright
Avamar Backups
Example 1: Run mccli command to back up a directory (Abackup) for a specific client
Example 2: Run mccli command to backup a specific backup policy (Daily_Backup_Policy)
Backup to 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 sends140 the backup data directly to the Data Domain
system.
As a result, backup data is stored on the Data Domain while tracking metadata is
stored on the Avamar server.
140 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.
Page
Avamar Backups
Avamar
Backup Request
Metadata
avagent
DD Boost
Data Domain
Client
Deduplicated Data
Avamar Checkpoint Backup
Avamar has the ability to store Avamar checkpoints141 on an integrated Data

Domain system (with DD OS 5.3 or higher). This is supported only on single-node
and virtual edition Avamar servers.
Since an Avamar checkpoint is effectively a copy of all Avamar data, this provides
disaster recovery.
141If a disaster were to occur and the Avamar server is destroyed, the checkpoint
data can be restored.
© Copyright
Avamar Backups
Important: In case of an issue with the Avamar server, the Avamar

checkpoint backups can also be used for restore. However, it does
not provide offline protection like replication.
Page
Avamar Backups
Avamar Desktop Laptop (DTLT) Overview
Avamar Desktop/Laptop is a version of the Avamar client software for Windows

and Macintosh that adds enhanced features for enterprise desktop and laptop
computers. Many DTLT features are also available on supported Linux computers.
The following are some of the features of DTLT:
Client User User Backup Restore Activity

Installation Authentication Interfaces 145 146 History147
and 143 144
Management
142
142
In a corporate environment, you can install Avamar Desktop/Laptop on
Windows and Macintosh desktop and laptop computers by using systems
management tools such as Microsoft Systems Management Server 2003 (SMS).
You can also install the Avamar Desktop/Laptop software locally by launching an
installation wizard.
After client installation, you can activate, upgrade, analyze, and manage clients by
using the Avamar Client Manager web browser UI.
143
Avamar Client Manager users authenticate through the Active Directory or
OpenLDAP-compliant directory service, with or without Kerberos encryption.
Users can also authenticate by using built-in Avamar authentication, or a

combination of Avamar authentication and LDAP authentication.
© Copyright
Avamar Backups
Pass-through authentication enables users to access the web UI without using the
login screen. A secure message mechanism authenticates users that are based on
information from the client computer. It also enables administrators to allow non-
domain users to restore files to their local account on the computer.
144 Avamar Desktop/Laptop functionality is available through the client local user
interface (client UI) and web browser user interface (web UI).
With the client UI, an Avamar icon appears in the notification area, or system tray,
or on Windows computers or on the menu bar on Mac computers.
You can right-click the icon on Windows or click the icon on Mac to open the client
menu, which provides access to backup and restore, program settings, and logs.
145
Users can start an on-demand backup with a single click on the client menu, or
open the web UI for an interactive on-demand backup.
Users can also perform scheduled backups of all the Avamar Desktop/Laptop
clients.
146 Users can search for or browse to folders, files, and file versions to either the
original location or to a new location on the same computer.
Users can restore data with the same name or a new name.
147
The History page in the web UI provides a 14-day history of the status of restore
and backup tasks for a client computer. Also, it provides the listing of the folders
and files that are backed up during that period.
Page
Avamar Backups
Deploying Avamar Client Software
© Copyright
Avamar Backups
The following are the important points to keep in mind while deploying an Avamar
client software:
• Windows and Macintosh clients only148
• Optionally Client User Interface must be installed
• Can be selected for interactive installation
− Deploying thousands of clients is time consuming
• Command-line installation149
− System management tools can use the command line for mass deployment
Avamar Desktop/Laptop User Authentication

Avamar Desktop/Laptop protects backup data by authenticating users and
enforcing access rights.
The following types of user authentications are used in Avamar DTLT:
3. Pass-through Authentication
148 The recommended method to install the Avamar client software on large
numbers of Windows or Mac computers is to use a systems management tool. A
systems management tool can remotely push install the software on large numbers
of computers in a short amount of time. Avamar 19.2 supports some Linux clients
as well, including DTLT on RHEL, SUSE, Ubuntu, CentOS and Debian
149For Windows, the msiexec command is used to install the Avamar client
package. The Avamar-specific option UICOMPONENT=1 is used to install the
optional Client User Interface.
On Macintosh, the /usr/bin/installer command is used to install the Avamar client

package and optional Client User Interface.
Page
Avamar Backups
The following are some of the important notes about Pass-through

Authentication:
• Default authentication method
• Uses encrypted channels to access user credentials from a client computer
• Client OS receives credentials during login or using Common Access Card

(CAC) technology
• Users can backup and restore files without viewing the login screen
• Limited to users on Windows computers and Mac computers
• Supported with LDAP authentication
4. LDAP Authentication
The following are some of the important notes about LDAP Authentication:
• Authentication process uses Kerberos in a Simple Authentication and

Security Layer (SASL)
• Users log in to the client computer with a domain account
• Local user access is enabled to use a local account
• Do not use the root account on a Mac to restore files from backups
5. Avamar Authentication
The following are some of the important notes about Avamar Authentication:
• Uses internal Avamar domain information
• Works with users who authenticate at the Avamar root level, domain levels,
or sub-domain levels
• First checks at the sub-domain level followed by other levels till username is
found
• Client computers must have a static, resolvable, fully qualified domain name
• Users must have a local or domain login account
© Copyright
Avamar Backups
6. Mixed Authentication
The following are some of the important notes about Mixed Authentication:
• Users on a client in an Avamar domain are authenticated by using Avamar

authentication
• Users not logged in to a client in an Avamar domain are authenticated by

using pass-through authentication
• When mixed authentication is enabled and LDAP is configured,

authenticated users are not logged in to a client assigned to a specified
Avamar domain through LDAP
Avamar Desktop/Laptop Backup Policies
In Avamar DTLT, you need to define the backup policies before performing a
backup.
The following are some of the components of a backup policy:

• Dataset150
• Schedule151
• Retention152
• Clients153
150 Define what data the end user must backup.
151Define the time at which the backup is initiated. Backups should be scheduled to
run during the day when end users are connected to the network.
152 Defines how long the backups are available for restore.
Page
Avamar Backups
Creating a Desktop/Laptop Dataset
The following points have to be kept in mind while creating a DTLT dataset:
• Back up only user files and folders
• Exclude common data: apps, OS files, and non-business files
Operating Dataset Tab Folders

System
Windows Source Data • #USERDOCS#\*\Desktop

• #USERDOCS#\*\Documents
• #USERDOCS#\*\My Documents
• #USERDOCS#\*\Favorites
Exclusions • *\Recent\*.lnk
• *\catalog.wci
• *\windows.edb
• *.avi, *.mp3, *.wmv, etc.
Mac Source Data • /Users

• /Users/*/Desktop
• /Users/*/Documents
• /Users/*/Library/Safari
153 User machines that are being backed up.
© Copyright
Avamar Backups
Exclusions • */.Trash/
• */Library/Caches/
• */Library/Cookies/
• */Library/Logs/
• */Library/PubSub/Feeds/
• */Library/Application
• Support/SyncServices/Local/
Desktop/Laptop Scheduled Backups
The following are some of the important points about the DTLT backup schedule:
• Avamar Desktop/Laptop backup should run during the day
• Maintenance Window moved to overnight
• Avoid backup during maintenance window
Important: If the backup environment contains both Desktop/Laptop

users that must backup during the day, and servers that backup
during the night, it may be necessary to have separate Avamar
servers for Desktop/Laptop clients and for servers.
Page
Avamar Backups
Enabling End User Changes to Scheduled Start Time
The following points needs to be performed while enabling end-user changes to the
scheduled start time:
• Add times to Override Daily Schedule 154
• Enable Allow override group daily schedule in Edit Client dialog
• Client uses Daily schedule policy
154 The Avamar administrator can allow end-users to override the scheduled time.
This is done by modifying the schedule policy named “Override Daily Schedule” in
order to provide a list of acceptable backup start times that the end-user may
choose from. It is recommended to remove anytime from this schedule that would
interfere with the maintenance window.
© Copyright
Avamar Backups
Back up with Avamar Desktop/Laptop
Avamar Desktop/Laptop provides several methods for starting a client backup.
The following table describes the methods for starting a client backup:
Scheduled155 Single-click156 Interactive157
155The scheduled backups of Avamar Desktop/Laptop client computers can be

performed the same way that you back up other Avamar client computers in the
environment. You need to create datasets, schedules, retention policies, and
backup policies for the backups by using the AUI. Users see the groups that are
associated with an Avamar Desktop/Laptop client on the Backup page in the
Avamar Desktop/Laptop web UI. The next scheduled backup time for each group
that is associated with an Avamar Desktop/Laptop client also appears on the
Backup page.
156
Users can start an on-demand backup on an Avamar Desktop/Laptop client
computer by a single-click on the Back Up Now button on the client menu.
157Interactive backups allow users to select a backup group that is associated with
the client and back up the client by using the group's settings.
When on-demand backup sets are enabled, interactive backups also allow users to
choose instead to back up only selected files and folders.
Page
Avamar Backups
Avamar Desktop/Laptop Web User Interface
© Copyright
Avamar Backups
The following are some of the useful information about Avamar DTLT web
interface:
• Avamar Desktop/Laptop software must be installed on applicable clients158
• Interface available in 14 languages
− Automatically appears in the locale of the OS, if supported
− End-user can switch to any of the supported locales
• Interface can be re-branded by replacing the logo graphic
• Launched via “system tray” icon by clicking Back Up
Restore with Avamar Desktop/Laptop
Avamar Desktop/Laptop users can use the web UI to either browse to or search for
folders, files, and file versions to restore.
158The Client User Interface optional component should be selected during the
installation of the Avamar client software on the client machine.
Page
Avamar Backups
Browsing for data to Searching for data to Selecting a file version161

restore159 restore160
159 From the left-side menu of the web UI, you need to select Browse to view the
backups for a client computer in a tree view that you can browse to find folders and
files to restore.
To browse a specific backup instead of all backups for the client, use Backup Date
and Time to select the date and time of the backup.
160From the left-side menu in the web UI, you need to select Search to search for
specific folders and files to restore.
To start a search, type a search string in the search field, and click Search. Results
appear as they are gathered, and a progress indicator provides information about
the length of the search.
161 The backups for a client computer contain more than one version of many of the
files that are backed up. When a file is backed up and then subsequently edited,
the next backup contains a new version of the file. Each version is kept for the
retention period set by the administrator.
The number of versions of a file in the client backups depends on many factors
such as length of time that backed up data is retained, frequency of backups, and
how often the file is edited.
When there are multiple versions of a file in the backups for a client, a version icon
appears next to the file name when you browse or search for data to restore. To
select a version of the file other than the most recent version, click the version icon
and then select the version. Then choose whether to overwrite the existing file on
the client computer or to restore the file version with a new name.
© Copyright
Avamar Backups
Avamar Desktop/Laptop users can restore data to:

• Original location
• New location
Best Practices: Avamar Desktop/Laptop Client
The following are some of the best practices that needs to be kept in mind while
using an Avamar Desktop/Laptop Client interface:
Minimize impact of initial Instruct end users about backup

backups by bringing clients Determine the duration of the
practices, limitations and
online in smaller groups Desktop/Laptop backup
restrictions,such as when to run on-
window
demand backups
Regularly monitor the amount of Do not include maintenance

Examine impact of
used backup storage to ensure hours in Override Daily Backup
Desktop/Laptop backups on
that server capacity limits are not Schedule
daily operational schedules
exceeded
Page
Avamar Backups
Managing and Monitoring Backup Activity
Monitoring Activity
Avamar provides several ways to monitor backup, restore, replication, and tiering
activities162 to report on backup status, and to manage backups.
AUI Activity View Avamar Administrator Activity Avamar Client

View View
1621) In progress
2) Completed
3) Failed
© Copyright
Avamar Backups
Features: Features: • Display most

• Enables you to • Provides central facility to recent activity
monitor backup, monitor backup progress and status
restore, backup- status • Display the
validation, and status
• Can view activities for the last
replication activity information and
72 hours up to a maximum of
• Detailed log of a 5,000 rows work order
client session for status
• Can cancel the activity in
analysis and • To access,
progress
troubleshooting double-click the
• Filter activities by Avamar icon in
duration163 the system tray
• Filter activities by
domain164
• Filter activities by
status165
163By default, the Activity tab displays the most recent 5,000 client activities. To
select a different duration, in the Filter activities by duration drop-down list, select
the last 24 hours or Last 72 hours.
164 By default, the Activity tab displays all activities regardless of domain. To display
only the activities for a specific domain, in the Filter activities by domain drop-down
list, select a domain or sub-domain.
165 By default, the Activity tab displays all activities regardless of status.
Page
Avamar Backups
Important: Detailed client session log can be viewed in AUI by

selecting an activity and clicking VIEW LOGS.
Managing Backups
Avamar allows you to manage backups from the AUI and Avamar Administrator.
You can list the backups run for a particular client by selecting the client registered
to a domain under the Asset Management tab and clicking VIEW MORE.
The following management tasks can be performed on an Avamar backup using

the AUI:
Search a Backup166 Restore a Backup167 Recall a Backup168
166Avamar allows you to find a completed backup by searching for a backup that
occurred on a specific calendar date or during a specific date range, or by
searching for a backup with a specific retention type.
© Copyright
Avamar Backups
Delete a Backup169 Change Expiration Date170 Change Retention

Type171
167 Avamar allows you to restore a regular or replicated backup to the original client
or to a different client based on the requirement.
168Avamar allows you to recall the backup directly to the client from a cloud unit if
the tier status of the backup is CLOUD.
169Avamar allows you to delete a backup. This will permanently delete all data from
the backup that is stored in the server.
170The expiration date can be a specific date that you select or a retention period
of a certain number of days, weeks, months, or years.
Avamar allows you to configure a backup to remain in backup storage for as long
as the client remains active on the Avamar server.
171
To support certain advanced features, the administrator automatically assigns
one or more retention types to every backup.
For example, the first backup that is created on an Avamar system is tagged as
daily, weekly, monthly, or yearly. You can manually change the retention types
assigned to a backup.
Page
Avamar Backups
Controlling Client-Initiated Backups
AUI
Avamar
Administrator
Administrators can control user access to the client on-demand backup process
and determine other client-initiated settings through client configuration options.
© Copyright
Avamar Backups
• Allow client initiated backups172

• Allow file selection on client initiated backups173
• Override retention policy on client initiated backups174
Important: The Override retention policy on client initiated

backups option has not been migrated to AUI.
Global Client Settings
Avamar agents are platform-specific software processes running on the client that
communicates with the Avamar server and with any plug-ins installed on that client.
172When this attribute is enabled, any authorized users can initiate client-initiated
on-demand backups of this client.
173 When this attribute is enabled, users can select specific folders and files for
client-initiated on-demand backups.
174When this attribute is enabled, the client uses a new retention policy and not the
backup policy retention policy for the client-initiated on-demand backups.
Page
Avamar Backups
The following list provides some information about the client settings:
• Two types of plug-in: File system and Database
• Avamar sends the following while communicating with a client
− Client ID
− Specific Agent Version
− Build running on the client
− List of plug-ins (version and build) currently installed on the client
• Operations can be controlled for all clients on an agent or plug-in basis
• Functions are accessed from Tools > Manage Agents and Plug-ins
• Global Client Settings
− Globally disabling client-initiated backups for all clients

− Denying Avamar server access to all clients running a specific version or
build of a client or plug-in
− Selectively allowing/disallowing individual plug-in operations for all clients
running a specific plug-in
Important: Global Client Setting feature is currently available only in

Avamar Administrator.
© Copyright
Avamar Backups
Partial Backup
Avamar protects data created by cancelled backups from being deleted:
- Backup is stored on the Avamar server and tagged as "partial"
- Retention is set to seven day by default
- Partial backups are not displayed in the AUI or Avamar Administrator
- Partial backups do not reduce subsequent scans as the file cache is not updated for canceled backups
Replicator may also create partial backups:
- Partially replicated data is "Safe" from being deleted
- No need to disable the backup deletion process for long, multi-day replications
Secure Backup Deletion: Data Shredding
Avamar supports data shredding to help facilitate the secure deletion of data from
an Avamar server when classified data is accidentally backed up to a non-classified
server. The secure backup deletion feature is a seven-pass overwrite process
executed via securedelete CLI command.
The following are some of the important points about data shredding:
• Level of granularity at client backup level
• Deletes only a single client backup at a time
Page
Avamar Backups
• Must run securedelete for all client backups containing data to be

shredded175
• Must roll back any checkpoints that also contain the data and then run
securedelete on those backups
• Must run securedelete on any remotely replicated176 copies of the client
backups
175After running securedelete on a client backup, it is possible the data may remain
on the Avamar server, since the same files that consist of that backup may also
reside in multiple checkpoints.
176If backups that contain the data to be deleted have also been replicated to other
Avamar servers, then the same actions need to be repeated on the replication
targets.
© Copyright
Performing Restores
Performing Restores
Restoring Client Data
Avamar Restores
The first step to restore data is to find the backup with the data you must restore.
To locate backups by a date when one or more of the following situations apply.
• All data is saved for the client in a single backup set.

• The exact pathname or name of the data restore is unknown.
• The backup that you need is before a specific date or event.
• The specific types of backups are known.
Finding a Backup by Date - Step One
In the AUI navigation pane click the on the left double arrows >>, and click Asset
Management. In the Asset Management pane select the domain for the client.
Finding a Backup by Date continued Step Two
Select the client in the list, in the Client Summary pane on the right, click VIEW
MORE.
Page
Performing Restores
Finding a Backup by Date continued Step Three
From the list select the client and click on SEARCH. Click in the Date Range field
to open the calendar view. Select the date range needed for the restore, and click
RETRIEVE.
© Copyright
Performing Restores
Finding a Backup by Date continued Step Four
Select the backup to restore, and click RESTORE.
Restore a Client Backup Step One
In the Destination Client pane, select Restore to original client, and click NEXT.
You can also Restore to a different client.
Restore a Client Backup continued Step Two
In the Backup Content pane, select the location for the restore. (In this case its the
whole C:) and click NEXT.
Page
Performing Restores
Restore a Client Backup continued Step Three
In the Destination Location, select Restore everything to its original location.

Then click NEXT.
The other option is also Restore everything to a different location.
Restore a Client Backup continued Step Four
From the More Option pane (Optional) select the filters as needed for the restore.
Refer to the users guide for each plug-in for more details of these options. Then
click NEXT.
© Copyright
Performing Restores
Restore a Client Backup Summary
The Summary page will display. Review the information, and click FINISH.
MCCLI Restores
The Avamar administrator can use the mccli interface at a command line to
perform restores of backups to Avamar clients. The mccli backup show
command includes options to show backups with a specified retention type and
display the contents of a backup.
Page
Performing Restores
To restore a backup, select the backup to restore from the list and run the mccli
backup restore command.
Important: The --plugin flag specifies the client plug-in used

during the restore. For example, 3001 refers to the Windows file
system plug-in. A complete list of plug-in numbers can be found with
the mccli plug-in show command.
avtar Restores
The avtar command can be run from a command line on the client to perform a
restore.
By default, the command can be run from these locations:
• Server utility node: /usr/local/avamar/bin
© Copyright
Performing Restores
• Windows clients: C:\Program Files\avs\bin
• AIX, HP-UX, Linux, and Solaris clients: /usr/local/avamar/bin
Use the avtar to list all backups with a label. In this example we used the label
"Kimbkup".
C:\Program Files\avs\bin\avtar --create --id=MCUser --

path=/clients/win01.emc.edu "C:\Abackup" --label="Backup1"
Use the avtar to restore a file to C:\Temp.
C:\Program Files\avs\bin\avtar --extract --label="Backup1" --

id=MCUser --path=/clients/win01.emc.edu --target="C:Temp"
Page
Performing Restores
Using Avamar Desktop/Laptop Clients
Avamar Desktop/Laptop allows the end users to perform restores of their data
independently. Users can search for items to restore, or they can browse a backup
directory tree to display and select files and folders to restore.
1: The Backup button allows users to pick a file or folder for a backup. If the user
has multiple machines, a drop-down menu is available to select which machine to
be used for the source of the backup data.
© Copyright
Performing Restores
2: The History button allows the users to view the past history of this backup.
3: Users can use the Search or Browse buttons to show a list of files and folders.
From the list the users can choose the file or folder to restore.
Page
Performing Restores
From the list the users can choose the file or folder to restore.
Monitoring Restore Activities
To access the Activity Monitor, open the navigation pane, and then click Activity.
The Activity Monitor appears with a list of all activities.
1 2
4
1: Filter activities by domain: By default, the Activity Monitor displays all

activities regardless of domain. To display only the activities for a specific domain,
in the Filter activities by domain drop-down list, select a domain or subdomain.
© Copyright
Performing Restores
2: Filter activities by duration: By default, the Activity Monitor displays the most
recent 5,000 client activities. To select a different duration, in the Filter activities
by duration drop-down list, select Last 24 hours or Last 72 hours.
3: Filter activities by status—By default, the Activity Monitor displays all

activities regardless of status.
To display only activities with a specific status, at the top of the Activity Monitor,
select one of the following options:
• Completed
• Failed
• Running
• Waiting
4: To filter activities by client, start time, plug-in, or type, click in their respective
column.
The Activity Monitor displays the date and time that an activity began, and the
total number of bytes examined during an activity.
Page
Performing Restores
Restoring from Data Domain
When the restore of the backup177 is initiated, the Avamar server uses the stored
metadata from the backup178 to locate the data on the Data Domain. Then, data is
restored179 back to the appropriate client.
177 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 backup, then the data is stored on the Data Domain system and
metadata is stored on the Avamar server.
178
All data for a backup is stored under a single dedicated MTree on a single Data
Domain system.
179The recovery process is transparent to the administrator. Since the backup and
restore processes use both the Avamar and the Data Domain, if either is
unavailable, backups and restores are not possible.
© Copyright
Performing Restores
Avamar
Metadata
Request
avagent
Restore Data
DD Boost
Data Domain
Page
Performing Restores
Search
Search180 processes content from multiple input sources for Avamar servers in
Data Protection Suite. It supports the following types of indexing:
180Search is a highly scalable, fault tolerant Elasticsearch platform. It provides a

powerful way to search backup data across one or more Avamar servers, and then
restore or download the search results.
© Copyright
Performing Restores
Metadata only indexing181 Full content indexing182
Advanced Options for Restores
The Advance Options pane allows the administrator more ability to narrow down
the restore. Also this allows for more details log and use of scripts for a backup.
1: Overwrite existing files
181Metadata only indexing is a lightweight search for the name, location, size, and
date for files.
182Full content index expands on metadata only index by drilling in to the body of
the files to index the content.
Page
Performing Restores
Restoration of open files
2: Restore the system profile
Restore Reparse Points as
Encryption method from Data Domain
© Copyright
Performing Restores
1
2
3
4
5
6
7
8
9
1: Check client-side caches and reports inconsistencies does not restore data,
only performs validation check of client-side cache with the Avamar server.
2: Check and repair client-side caches does not restore data, only performs
client cache validation checks with Avamar server and repairs the inconsistencies.
3: Rebuild client-side caches from the most recent backup does not restore data.
This uses contents of last backup to re-create client-side file cache.
4: Do not descend into subfolder restores only the specific folder and no
subfolders.
5: Re-create original path beneath target folder, re-creates the original path to
the files and folders beneath the specified target.
6: Restore hidden folders and files, restores files and folders that have the
HIDDEN attribute set in the backup.
7: Restore folders and files with SYSTEM attribute, restores the files and folders
with the SYSTEM attribute.
Page
Performing Restores
8: Directly connect to all server nodes, this may improve the performance by
establishing more than one connection to the server.
9: Run as user name, allows the plug-in to run as the user on the client.
© Copyright
Performing Restores
Client Server Recovery with Avamar
Recovery Pre-Requisites
Before performing a disaster recovery, ensure a completed system backup of the

Windows client exists. This backup must include the system state data captured
with the Windows VSS plug-in.
• Check contents of the backup183

• Download the WinPE image184
• Provision new hardware or virtual hardware185
183Check the contents of the backup in the Backup and Restore interface to ensure
there is an entry for the Automated System Recovery (ASR) writer.
184Download the WinPE ISO image from the Avamar server, that is located in the
Documents and Settings webpage in the Windows Disaster Recovery Wizard
Section. 32-bit and 64-bit versions are available. The ISO includes many common
NIC and disk device drivers. However, if the ISO does not contain the drivers
needed, you may add them into the ISO. Drivers do not require a reboot. To
discover if the ISO already has the proper drivers, you may run the Avamar System
Recovery Wizard on your system at any time to see if it recognizes the NIC and
disk devices. Burn the ISO to a CD or to a bootable USB drive.
185To recover from a disaster, provision new hardware that is similar to the original
hardware. The disk size must be at least the same size as the source. Also, be
sure to have the same number of disks with the same LUN numbering.
Page
Performing Restores
OS-Specific Server Recovery Solutions
Avamar can be used with native OS-specific server recover solutions to achieve
various levels of server disaster recovery.
Windows Windows RedHat188 Linux189 Oracle190

Operating Server
System186 Operating
System187
186 Windows 7,8,10 and VSS
187 Windows Server 2012, 2016, 2019, and 2020.
188 RHEL 6.0- 8.1
189 SUSE SLES 11, 12, 15
190 Oracle Solaris 10 Sparc, 10x86, 11 SPARC, 11x86
© Copyright
Performing Restores
Avamar Windows Server Disaster Recovery
Avamar backup for bare-metal recovery191 includes the system-state. The Avamar
leverages Microsoft VSS service to create backups of system state information.
When the WinPE192 boot disk is loaded, it starts the Avamar System Recovery
Wizard. This wizard performs a basic configuration of the network, then contacts
the Avamar server and restores all the server data.
191The bare-metal recovery uses a customized Windows Preinstallation

Environment (WinPE) boot disk that provides a minimal set of Windows features so
installation of the full OS is not required. The new server can boot from the WinPE
disk and restore all data back onto the hard drive, including the original OS. The
ISO for this disk is included in the Avamar Downloads webpage.
192The WinPE ISO can also be added as a boot image to a Windows Deployment
Services server. This allows the new bare-metal server to boot the image from the
network instead of a local CD. Restoring a physical server to a virtual machine is
also supported. This can be useful if a server must be recovered immediately
before new hardware is available. During the disaster recovery, all critical disks are
formatted. A critical disk is defined as one that contains operating system files or
Page
Performing Restores
Windows Full System Backup
Windows full system backup for the client must be performed to successfully
recover a Windows 2008, 2012, and 2016 server. A full system backup is
performed using the Windows VSS plug-in193.
1: Select Plug-in Type, use the Windows VSS option. The Backup is performed
using the Windows VSS plug-in.
2: Clear out all other plug-in options, and add in the VSS options. The dataset
should have client file system and system state data.
It is recommended to perform the full system backup for the client on a regular,
scheduled basis. The dataset for the group backup must include the entire client
application services. Dell recommends any application data, such as database or

Exchange files, be located on a separate disk.
193The VSS plug-in does not back up critical disks on shared storage in a cluster. If
the server has shared cluster storage, this must be backed up using a file system
plug-in.
© Copyright
Performing Restores
file system and the system state data. Ensure the retention on the backup is
sufficient to ensure the backup of the system state is always available.
3: The Options tab you can add a Snapup Label and have options to select for
Create Disaster Recovery Backup.
Important: AUI supports on-demand backup of a full system.
Avamar Bare Metal Recovery Wizard
When the new client is booted from the WinPE disk, the Avamar System Recovery
Wizard194 is displayed. The wizard asks for date and time information, networking
194 The Avamar System Recovery Wizard asks for date and time, networking
information, Avamar server address, location for the recovered backup, details
Page
Performing Restores
information, the address of the Avamar server, and the backup to recover from. It
also confirms which disks195 are formatted and to which disk it is recovered.
about the disks, operating system, system settings, and all the files are restored.
Applications, such as databases and Exchange, must be restored from their most
recent backup.
195If any disks or NICs do not appear during this process, you may have to add
their drivers onto the ISO and manually select them.
© Copyright
Avamar Replication
Avamar Replication
Avamar - Data Domain Replication
If you use a Data Domain system as a backup target for Avamar196, then the
replication process also transfers Avamar data from the source Data Domain
system to a destination Data Domain system.
Replication197 control belongs to Avamar, however, a Data Domain replication

license is required to enable the copying of data from one system to another.
196If a Data Domain system is configured with a source Avamar server, then there
must be a corresponding Data Domain system that is configured with a destination
server, otherwise, the replication fails for backups that are stored on the source
Data Domain system.
197 Replication is a direct copy and occurs on the Avamar replication schedules and
is supported in multiple environments.
Page
Avamar Replication
Avamar Avamar
Metadata
Backup Data
Data Domain Data Domain
Replication Process and Topologies
Here is the replication process and various topologies that are used when a Data
Domain system is integrated with Avamar.
© Copyright
Avamar Replication
Replication Process198 Replication Topologies199
198 The replication process is initiated from the source Avamar server. If the data
that has been selected for replication includes data stored on the source Data
Domain, the source Avamar queries the target Avamar server to ensure that there
is a target Data Domain. The source Avamar also communicates with the target
Data Domain to ensure that replication is possible. Then, the source Avamar
replicates meta data to the target Avamar while the source Data Domain sends
backup data directly to the target Data Domain. Data is not staged on the Avamar
server.Since the source Avamar server must communicate with the target Data
Domain, it is not possible to separate the Avamar and Data Domain traffic onto
separate networks. Also, be aware that if the source Data Domain is used to store
data other than the Avamar backup data, it will not be replicated. Configure
replication for this data separately through the Data Domain interface.
199Ensure that the target site must have a target Avamar server configured with its
own Data Domain. Be sure that the destination systems have enough capacity to
store all data, especially when multiple systems are replicating to one.
Page
Avamar Replication
Avamar Replication Types
An Avamar replication job copies client backups from the source Avamar system to
an alternate destination200.
Replicating backups to an alternate destination protects against data loss if the

source Avamar system fails.
Avamar provides the option to perform policy-based replication and command-line

replication.
Policy-Based Replication Command Line Replication
Pre-Requisites
The following are the pre-requisites for performing a replication

job:
1. Add a replication destination for each system
2. Create daily, weekly, or monthly schedules (optional)
3. Create one or more replication groups to define the settings
200The alternate destination can be an environment either having an Avamar

system or an Avamar system that is integrated with the Data Domain system.
© Copyright
Avamar Replication
Replication Destination
The initial step during a policy-based replication is to add a replication destination.

The connection details201 for a supported data storage system have to be specified.
The Avamar system supports replication to other Avamar systems and to Data
Domain (DD) systems through DD Boost.
The following steps describe how to add a replication destination:
Step 1
Log in to the AUI and click System pane.
Click to enlarge
201An Avamar system can also replicate to another Avamar system that is running
a different version of the Avamar server software. However, the best results occur
with the same software version.
Page
Avamar Replication
Step 2
Click the Replication Destination tab, and then click +ADD.
Click to enlarge
Step 3
In the popup window that appears, enter the destination server details with repluser
privilege, and click VALIDATE.
Step 4
Once the validation is successful, click OK to add the destination.
© Copyright
Avamar Replication
Result: You can see the destination is added successfully.
Click to enlarge
Define a Schedule
The method of scheduling replication tasks depends on the type of replication that
is used. In a policy-based replication, schedules are defined in a similar way to
back up schedules.
To configure schedules for a policy-based replication, the first step is to log in to the
AUI.
Once logged in to the AUI, follow the steps that are shown below:
1. Navigate to Setting pane, and select a domain.
Page
Avamar Replication
2. Click Schedules tab, and then click + ADD.

3. Define a schedule for the replication task on a daily, weekly, or monthly interval.
You can also configure the retention period based on the requirement.
Replication with Data Domain Systems
When an Avamar system stores backups on a Data Domain system, Avamar

replication uses DD Boost to copy backups from the original Data Domain system
and to create replicas on another Data Domain system.
The following table lists the supported replication configurations for Avamar
replication using DD Boost.
Backup Storage Replication Storage
Single Data Domain System Single Data Domain System
Single Data Domain System Multiple Data Domain Systems
Multiple Data Domain Systems Single Data Domain System
Multiple Data Domain Systems Multiple Data Domain Systems
© Copyright
Avamar Replication
Data Domain Destination Settings
In a replication environment with more than one destination Data Domain system,
you can set the system202 that receives the replicas by mapping a domain on the
source Avamar server to a destination Data Domain system.
Set Default Data Domain Destination
202You can specify a Data Domain system as a default destination. The Avamar
server replicates to a default destination when a destination Data Domain system is
not identified in the Storage Mapping tab.
Page
Avamar Replication
The following steps must be followed in order to set a default Data Domain
destination system:
1. Log in to the AUI, and go to the System pane.
2. Click the Data Domain tab.
3. Click +ADD if the Data Domain system does not already exist in the list.
Continue to step 4.
4. Select the Data Domain, and click EDIT.
5. Scroll down to the Misc section, and select Use system as default replication
storage checkbox.
6. Click VALIDATE and OK.
Map Avamar Domain to the destination Data Domain
If there are multiple destination Data Domain systems, you can control which
system receives the data that replicates203 from the source Data Domain system.
203
To specify the destination system, a domain should be mapped on the source
Avamar system to a destination Data Domain system.
If the mapping is not done, then Avamar replicates the data from the source Data
Domain system to the default destination.
© Copyright
Avamar Replication
To map a domain:
1. Log in to the AUI, and navigate to System pane.
2. Click Storage Mapping tab, and click +ADD.
3. Select the Data Domain system from the list to use as replication target.
4. Click SUBMIT.
Create a Replication Policy
The replication policy enables you to define the settings for policy-based
replication. The replication policy also enables you to perform a scheduled as well
as on-demand replication from source to destination systems.
The following steps describe how to create a replication policy in the AUI:
Step 1
Log in to the AUI, and navigate to Replication Policy pane, and click +ADD.
Page
Avamar Replication
Step 2
Under the Properties tab, enter a name for the policy.
You can have the replication of the backups either in alphabetical order or parallel.
Click NEXT to continue.
Step 3
Under the Members tab, you can either replicate all clients or choose any specific
client that you want to replicate.
Once the client is selected, click NEXT.
© Copyright
Avamar Replication
Step 4
Under the Backup Filters tab, you can either replicate all the backups or you can
include/exclude any specific backups by type, date etc.
Once the backup is selected, click NEXT.
Step 5
Under the Schedule tab, you can either select the Default Replication Schedule or
you can choose a schedule created by the user.
Once you select the schedule, click NEXT.
Page
Avamar Replication
Step 6
Under the Retention tab, you can either keep the default retention or you can edit
the retention period.
Once the retention is set, click NEXT.
Step 7
Under the Destination tab, select the destination Avamar server and click NEXT.
© Copyright
Avamar Replication
Note: If you have not configured a destination server, then you can add a
destination server by clicking +ADD DESTINATION option.
Step 8
Finally, review the summary and click FINISH to create a replication policy.
Result: A replication policy is successfully created.
How to Perform an On-Demand Replication
An on-demand replication is an instant replication job initiation that is performed by

the user by running the replication policy.
Page
Avamar Replication
To perform an on-demand replication:

1. Log in to the AUI, and navigate to Replication Policy pane.
2. Select the replication policy, and click RUN.
Result: An on-demand replication is initiated successfully. Navigate to the Activity

pane to view the progress of the replication activity.
Monitor Replication in AUI
The Activity window in the AUI enables you to view status information for both on-
demand and scheduled replication activity.
Display specific
type of activity
Follow the steps to monitor replication activity in the AUI:

1. Navigate to the Activity pane in the AUI
© Copyright
Avamar Replication
Displays a list of all activities which are in-progress, completed, or failed.

2. Click filter option next to the Type column, and enter Replication source to
display only the replication activity.
Replicas at Source
The Replicas at Source204 feature allows you to view, manage, and restore
replicated backups while logged into the source Avamar server.
To enable this feature:

1. Log in to the Avamar server using a command shell.
2. Stop the MCS process with dpnctl stop mcs command.
204This feature is convenient when the destination server is used exclusively to

store replicated data. The administrator no longer must log into the target server to
manage the backups that were replicated to it.
Page
Avamar Replication
3. Edit the mcserver.xml file located in

/usr/local/avamar/var/mc/server_data/prefs.
4. Set the following values to true:
− allow_dest_replica_management
− show_external_backups
− allow_manage_remote_backups_at_source
5. Save the file, and restart MCS process with dpnctl start mcs command.
Restore Replicated Backups on a Destination System
Avamar allows you to restore the replicated backups on a destination system using
AUI. This method is used when the source Avamar server is unavailable and the
Replicas at Source feature is not enabled on the source Avamar system.
To perform a restore operation:

1. Log in to the destination Avamar system, and navigate to Asset Management
pane.
2. In the domain tree, expand the REPLICATE domain and hostname to view the
client.
3. Select the client, and click VIEW MORE under Client Summary pane.
© Copyright
Avamar Replication
4. Click the Backup tab.

Result: All replicated backups associated to the client are displayed.
5. Select a backup, and click RESTORE.
Restore Replicas at Source
Replicas at Source feature allow you to restore replicated backups on the source
Avamar server using the AUI.
The following steps allow you to restore replicas at source:

1. Log in to source Avamar, and click Asset Management from the AUI.
2. Select the domain that contains the client.
3. Select the client from the list.
4. In the Client Summary pane on the right, click VIEW MORE.
5. Click the Backup tab, and select Include Remote option.
6. Select a local or remote backup, and click Restore.
Page
Cloud Tier
Cloud Tier
Cloud Tier
The Avamar Cloud Tier feature enables you to move Avamar backups from a Data
Domain system to the cloud. The Cloud Tier feature provides long-term storage of
Avamar backups by seamlessly and securely tiering data to the cloud.
Avamar - Data Domain Integrated
Cloud Tier
Avamar backup
data stored in
Data Domain Active Tier Data is moved to cloud for long-term
retention
Click to enlarge.
The following are some of the important points to be remembered while using cloud
tier in Avamar:
• Configure cloud tier to move Avamar backups on the Data Domain to the cloud
using AUI.
• Perform efficient recovery of the backups to the client.
© Copyright
Cloud Tier
• Need to configure Data Domain cloud storage units before configuring cloud tier
in AUI.
• AUI supports virtual machine File Level Recovery (FLR) operations for backups
in the cloud.
The following two tasks are performed as part of configuring the Avamar server to
manage the Cloud Tier feature:
Add or Edit a Data Domain system to enable Cloud Tier205
Create a Cloud Tier group206
205You can switch from one cloud unit to another. Each Avamar server can have
only one active cloud unit simultaneously. After you switch the cloud unit, Avamar
moves the existing backups that have been marked for tiering to the new cloud unit
when the Data Domain system triggers data movement.
206 For the backups stored on the cloud, Granular, or File Level Restore (GLR/FLR)
is the method to restore a piece of data or files to the client. With this feature, you
do not recall the whole backup from the cloud to the active tier. Instead, you can
restore only the file which the client needs.
The GLR/FLR feature saves the data transfer rate and time. GLR is supported on
AUI if the cloud unit that is configured on Data Domain is Elastic Cloud Storage
(ECS). GLR is not supported on AUI if the cloud unit that is configured on the Data
Domain are other types. If the backup is on Active Tier (local Data Domain), the
GLR function does not have such a limitation.
Page
Cloud Tier

Add or Edit a Data Domain with Cloud Tier
To use the Cloud Tier feature, you should have a Data Domain system with Cloud
Tier enabled.
To add or edit a Data Domain system, the first step is to log in to the AUI.
Step One
From the navigation pane, click System.
From the Data Domain tab, click + ADD or EDIT.
© Copyright
Cloud Tier
Step Two
Page
Cloud Tier
Click to enlarge
Under the System tab, enter the IPV4 DD System Name, DDBoost Username and
Password, and click VALIDATE.
Once validation is successful, click NEXT.
Step Three
Under the SNMP tab, enter a value to the SNMP Community String and click
NEXT.
Step Four
Under the Tiering tab, select the Enable Cloud Tier option.
Then, select the cloud unit from the drop-down and click FINISH.
© Copyright
Cloud Tier
Important: The cloud tier feature can be enabled only after adding a
Data Domain system. The Enable Cloud Tier option is not available
for you while adding a new DD system. The cloud tier feature has to
be purchased and deployed on the Data Domain.
Add a Cloud Tier Policy
To run a Cloud Tier operation, you have to create a Cloud Tier policy.
To create a Cloud Tier policy, the first step is to log in to the AUI.
Step One
From the navigation pane, click Cloud Tier Policy and click + ADD.
Page
Cloud Tier
Step Two
Under the Properties tab, enter the name of the policy.
Then, check the Enabled option and click NEXT.
Step Three
Under the Members tab, choose individual client under a domain and click NEXT.
© Copyright
Cloud Tier
Step Four
Under the Backup Filters tab, enter the following information and click NEXT.
• Age Threshold: Determine how long backup resides on the Data Domain
before tiered to cloud
• Backup Filter: Select either tier all backups or filter backup tiering by including
or excluding backups
• Backup Types: Select the type of backup
• Maximum backups per client: Select how many backups to tier to the cloud
each time the schedule is run
Page
Cloud Tier
Step Five
Under the Schedule tab, select a schedule and click NEXT.
Step Six
Under the Retention tab, you can either keep the current expiration or set
expiration by backup type and click NEXT.
Step Seven
Under the Destination tab, you can see list of Data Domains with cloud units
enabled and then click NEXT.
© Copyright
Cloud Tier
Step Eight
Under the Summary tab, review the Cloud Tier policy information and click
FINISH.
Result: You can see that the Cloud Tier policy is created successfully.
Perform Backup of a Cloud Tier Policy

Cloud Tier policy backup can be performed in either scheduled or on-demand.
7. Scheduled Backup of a Cloud Tier Policy
Page
Cloud Tier
In a scheduled backup, the backup of a

Cloud Tier policy runs as per the schedule
that is configured within the policy.
To ensure that the backup run as per the
schedule, review the steps that are shown
below:
1. Once logged in to the AUI, click Asset
Management.
2. Select the client from the /clients
domain, and click VIEW MORE in the
Client Summary pane
3. Check the status in the Tier column
indicating ACTIVE
If the status of the backup is ACTIVE, then

the backup runs as per the schedule that is
configured in the Cloud Tier policy.
8. On-Demand Backup of a Cloud Tier Policy
© Copyright
Cloud Tier
On-Demand backup of a
Cloud Tier policy is the
process of running the
policy instantly by the
user.
To perform an on-
demand backup of the
policy, follow the steps
that are shown below:
1. Once logged in to the
AUI, click Cloud Tier
Policy from the
navigation pane
2. Select the Cloud Tier
policy, and click RUN
The status in the Tier

column changes from
MARKED to CLOUD after
Data Domain moves the
backup data to the cloud.
Page
Cloud Tier
Perform Restore from Cloud Tier
The process of restoring backups207 that are tiered to the cloud are identical to the
normal restore operation.
207 First, Avamar recalls a copy of backup from the cloud to the active tier of the
Data Domain. Then, the restore of backup is performed from the active tier to the
client.
The status of the backup is Cloud. It is because the backup is stored on the Data
Domain cloud tier after the restoration. The copy of the backup on the active tier is
used for the restore operation and is deleted after 10 days.
© Copyright
Cloud Tier
Avamar - Data Domain
Cloud Tier
Restore
backup
Recall
DD backup
Active
Client
Recall a Cloud Tier Backup
A recall operation allows you to move a backup residing on cloud tier storage back
to the active tier on the Data Domain system. In the AUI, you can enable recall at
the policy level.
To enable recall a cloud tier backup at the policy level, follow the steps that are
shown below:
Step One
In the AUI navigation pane, click Cloud TIer Policy pane.
Page
Cloud Tier
Step Two
Select the Cloud Tier policy that requires the recall

operation and click EDIT.
Step Three
Under the Properties tab, select Undo Tier, then select one of the options based
on the requirement and click NEXT.
• Unmark backup only208

• Unmark and recall backups209
208 Unmark previously marked backup and changes the status to ACTIVE.
209 Unmark and recalls backups that are moved to cloud tier.
© Copyright
Cloud Tier
Step Four
Under the Members tab, keep the default client and click NEXT.
Page
Cloud Tier
Step Five
Under the Backup Filters tab, keep the default values which were configured
before and click NEXT.
Step Six
If the Undo Tier option is enabled, then the Schedule tab is disabled. Click NEXT to
continue.
© Copyright
Cloud Tier
Step Seven
Under the Retention tab, you can either keep the current expiration or set
expiration by backup type and click NEXT.
Page
Cloud Tier
Step Eight
Under the Destination tab, you can see list of Data Domains with cloud units
enabled and click NEXT.
Step Nine
Under the Summary tab, review the recall of the Cloud Tier at the policy level
information and click FINISH to save the changes.
© Copyright
Cloud Tier
File or Granular Level Restore for Cloud Tier
Avamar supports File or Granular Level Restore only from the Dell EMC Elastic
Cloud Storage (ECS) cloud unit210.
Avamar does not support File or Granular Level restore from a non-ECS cloud
unit211.
210
To restore a single file from the backup that is in the ECS cloud unit, you do not
must recall the whole backup from the cloud to the active tier of the Data Domain.
You can directly restore the single file from the cloud.
211With a non-ECS cloud unit, you have to first recall the whole backup from the
cloud to the active tier of Data Domain. Then, you can restore a single file from the
active tier of Data Domain to the client.
Page
Cloud Tier
Avamar - Data Domain Cloud Tier
Non-ECS Cloud Unit

Whole backup
ECS Cloud
Recall whole
Active backup
Single File
Tier
Whole backup
Restor
e Work File or Granular Level
Job Restore File or Granular Level Restore directly
from cloud
Client
Single File
Click to enlarge
Important: The process of restore from a backup that is tiered to the

ECS cloud unit is identical to normal File or Granular Level restore
operations.
© Copyright
System Monitoring and Maintenance
Avamar Server Environment
The Avamar Operating System has two login accounts, root212 and admin213. Most
support operations on the Avamar server nodes are performed as user admin.
Avamar also has internal accounts and BASH214. The internal server accounts are:
212
Root is the standard operating system superuser which is required to install
RPMs and starting and stopping.
213The admin is the owner for all the Avamar system data. Most support operations
on Avamar server nodes are performed as user admins.
214 The standard operating system command-line interface
Page
• root
• MCUser215
• repluser216
• viewuser
215 This is the Administrative account.
216 This is the replication account.
© Copyright
Avamar Server Directory Structure
Avamar binaries, utilities, and logs are located in /usr/local/avamar single-

node Avamar server and utility node of a multinode Avamar server.
1
3
2
4
1: The bin directory is where the binaries and scripts reside.
2: The src directory is where the customer tar and web downloaded files reside.
3: The etc directory is where the configuration files reside.
4: The var-cron directory is the location of the administrator logs.
Data, checkpoints, and logs are located in one or more /data0n directories on a
single-node Avamar server and on each storage node of a multinode Avamar
server.
Page
1: The cp* files are the checkpoint directories.
2: The cur directories contain data and log files. Some of the files that are found in
the directory are:
• *.inx index stripes

• *.dat data stripes
• *chd chunk header list, these files provide mapping and offsets for data stripe
lookups.
• *par local parity stripes
• *usd user accounting data
© Copyright
• *wlg write logfile.

• stripeidA.stripeidB change logfile that specifies the data range that has been
made for stripeidA by parity stripeidB
Avamar Node Numbers
Avamar nodes are designated in MODULE.NODE217 format.
Avamar sees the storage nodes in two ways.
• Physical Node Numbers218

• Logical Node Numbers219
The Module.Node format is 0.s for Utility node and 0.0, 0.1, 0.2...0.9, 0.a, 0.b and
so on, for multinodes. Shown here is a single node format, showing Node.0.0.
217The format, where MODULE is the number that are assigned to the Avamar
server/grid and NODE = 0, 1, 2,…9, a, b, and so on, for storage nodes. The utility
node of a multi-node server of module 0 is referred to as 0.s. The first accelerator
node is 0.accelerar.0.
218 Based on node's IP address and position in the probe.xml file.
219Are number generated when a node is added to the Avamar system and it does
not change when IP address or position in probe.xml changes.
Page
Probe.xml Files
The probe.xml file is a node resource database file that stores the types and IP
addresses of Avamar server nodes which are located in
/usr/local/avamar/var directory. This is created during the Avamar
installation, and the nodedb command is used to maintain the file.
Nodenumbers Utility
The logical and physical node numbers are the same, except when nodes are
added, decommissioned, or replaced, it is possible the physical and logical node
numbers to get out of sync.
© Copyright
To keep the physical and logical node numbers the same, during node
replacement, the same physical node number as that of the node being replaced
can be used, use the Avamar utility, nodenumbers.
Nodenumbers compares the probe.xml to the output of the avmaint nodelist

command and denotes any out of sequential order conditions.
Loading SSH Keys
Some of the Avamar commands and utilities authenticate against all nodes in a
multi-node Avamar system. The mapall command provides the password for each
node, thus not having to enter passwords for every node.
Loading the SSH keys prior to using any commands using the admin_key file.
Loading the admin_key is done from the utility node.
To run this command, as user admin load the admin SSH keys:
1. su - admin
2. ssh-agent bash
3. ssh-add ~/ssh/admin_key
Enter the password for admin if prompted.
Page
Mapall Utility
The mapall is a utility that is used to perform operations on all the nodes in an
Avamar server. The mapall utility uses the information in probe.xml to resolve
MODULE.NODE designations into IP addresses. To avoid password prompts, first
load the SSH keys.
The mapall command format is mapall <options> 'command'.
Common options include:
• -all Runs command on all node in the system. (if not used the command only
runs on the storage node).
• --bg Runs command in the background and does not wait for it to complete.
• --nodes = NODELIST Runs command on specific nodes.
• --noerror Continues if error occurs.
• --parallel Runs command on each node simultaneously.
Activity Monitoring
By default, the Activity Monitor tab displays the most recent 5,000 client activities
during the past 24 to 72 hours.
You can increase or reduce the amount of information in the Activity Monitor by
editing the mcserver.xml file located:
© Copyright
/usr/local/avamar/var/mc/server_data/prefs/mcserver.xml
To view the activity from Left Menu, select Activity, and all clients status appear in
the Activity window.
1 4
1: The VIEW LOGS shows the details of the clients backup or restores. You can
also choose to download and send to support.
2: In this window, the view is based on these details.
Page
Column Description
Status Status of the backup, restore, or validation

activity. The Avamar Administrator online help
provides details on each status.
Error Code If the activity did not successfully complete, a

numeric error code appears. To view a detailed
explanation, double-click the error code.
Start Time Date and time that this activity began, adjusted
for the prevailing time zone, which is shown in
parentheses. Daylight Savings Time (DST)
transitions are automatically compensated.
Elapsed Time Elapsed time for this activity.
End Time Date and time that this activity completed,

adjusted for the prevailing time zone, which is
shown in parentheses. Daylight Savings Time
(DST) transitions are automatically
compensated.
Type Type of activity
Server Server on which the activity occurred, either the

Avamar server or a Data Domain system.
Progress Bytes Total number of bytes examined during this

activity.
New Bytes Percentage of new bytes backed up to either the

Avamar server or a Data Domain system. Low
numbers indicate high levels of data
deduplication.
3: The Details available are:
© Copyright
Column Description
Client Avamar client name.
Domain Full location of the client in the Avamar server.
OS Client operating system.
Client Release Avamar client software version. If this activity is

a VMware image backup or restore, then this
value is the Avamar client software version
running on the image proxy client.
Proxy If this activity is a VMware image backup or

restore, then this value is the name of the proxy
client performing the backup or restore
4: Filter by duration allows the view to be All, Last 72 hours, and Last 24 hours.
Page
Activity Summary
The Activity Summary tab displays the view of Group and VMware container
success and failures.
1
7
2 3 4 5 6 8 9
1: The Summary View can be changed either to show the Group or the VMware
Container.
2: Group: Group name “On-Demand” is a special logical grouping that summarizes

on-demand backup activity initiated by Avamar clients or Avamar Administrator;
and is not an Avamar group.
3: Start Time: Time the group became eligible to run.
4: Total: Number of backups initiated by the group.
5: Queued: Number of backups for the group currently in the scheduler queue.
© Copyright
6: Active: Number of backups currently being performed.
7: Completed: Number of backups completed successfully, canceled before

completion, and failed.
8: Time Queued: Interval between start time and the first client work order is
started by any client in the group.
9: Time Active: Total amount of time used to perform all backup activities for this
group (the time between when the first client work order is started and the last
client work order is finished).
Important: This feature has not been migrated to the AUI.
Event Monitoring
The Avamar Administrator Administration view Event Management > Event

Monitor tab in Monitor mode displays the most recent 5,000 system events during
the past 24 hours. The listing can be filtered by event code, category, type,
severity, and domain. The report can also be exported to a .CSV file.
There are four categories of events:
• SYSTEM
• APPLICATION
• USER
• SECURITY
There are six types of events: INTERNAL, ERROR, WARNING, INFORMATION,

AUDIT, and DEBUG.
Page
2 3 4
1: Mode can be displayed in either Monitor or Query mode. For Query mode, use
the filters to select a range of dates for the events to display by using From Date
and To Date fields.
© Copyright
2: The Event Details window displays more details on the actual event. Use the
Help button for more details on this option.
3: Event Filter allows the use of Filters to be applied to the selected event.
4: Export Events Report allows the event to saved off as a .csv report.
Page
5: Double-click any event to quickly view event details.
© Copyright
Event Monitoring - Audit Log
Certain system events initiated by users, those with a category of Security and type
of Audit, are recorded in the Audit Log220.
To view the audit login Event Management, select the Audit Log tab. Double-click
an event in the log to display details about the selected event.
2 3 4
1: Mode allows the filter chose Monitor or Query.
220Administrators can use this information to enforce security policies and detect
deviation from those policies.
Page
2: Select a log, and click the View Detail. Event Detail will open and provide
details.
3: The Filter will allow for administrator to select Date Range, To Date, Category,
Type, Severity, and Domains. The More button will offer Code filters, which can
be used to include or exclude.
© Copyright
4: Export Events Report allows the event to saved off as a .csv report.
Page
Event Management in AUI
The Event Management in the AUI, is seen from Event Management window.
Filters can be used to narrow down the event viewing and a selection can be reset
of retrieved by dates.
1: The Event Management offers views for Critical, Error, and Warnings.
2: Filters can be set to narrow down the events. Administrators can use a date
range, Type, and Categories. Selecting the Unacknowledge event only then
select RETRIEVE.
© Copyright
3: By selecting an event or events from the Event ID column, users can

acknowledge them by clicking on ACKNOWLEDGE.
In the image below the Errors were 6 and after acknowledging two events, the
Error results are now 4.
Page
Managing Profiles
Avamar provides notifications when any event occurs, including pop-up alerts, the
acknowledgement-required list, email messages, syslog files, and SNMP traps. In
addition, third-party tools and applications can also be used to monitor and report
on the syslog files and SNMP traps.
1
2
1: The System Profile lists all possible event codes and when the event occurs,
whether a GUI Alert is sent and/or an acknowledgment is required. You can
change either of these options for each event code. There is only one system
profile.
© Copyright
2: Custom profiles can be used or created to send notifications when specified

event occurs. The Avamar Reports Guide provides more details.
Various preconfigured custom profiles are the following:
• Evaluation Profile: Used to support system evaluation.

• High Priority Events: Send email status, warning, and server error messages
to Technical Support automatically twice a day. The only change that can be
made is to add email addresses to the Recipient Email List. If you require
custom High Priority Events profile settings, copy the profile and then edit the
copy.
Page
• Local SNMP Trap: Verify if Traps are successfully generated and received.
This is read-only and is intended for test purposes only.
• Local Syslog: If enabled, provides the status reports by the syslogd process
on the Avamar server.
• Usage Intelligence: Enables the Avamar server to automatically transfer

reporting information to Avamar Support via ESRS gateway.
Editing System Event Profile
The System Profile contains all possible system event codes. You can edit the
system-event profile to control whether an event generates a pop-up alert in
Avamar Administrator, an entry in the common unacknowledged events list, or
neither.
© Copyright
1: From the System Profile users can see All Codes and Audit Codes. To add or
remove specific codes, select the appropriate box and click OK.
The Types of codes are WARNING, ERROR, and INFORMATIONAL.
To show a graphical pop-up alert in Avamar Administrator each time an event

occurs, select the GUI Alert checkbox next to the event.
To add an entry to the common unacknowledged events list each time that an
event occurs, select the Acknowledgement Required checkbox.
Page
Create a Custom Event Profile
Step One
Custom event profiles enables the user to send notifications when specific system
events occur.
You cannot view system events and profiles outside the domain that you are
logged in to. This step affects the profiles that you can edit and the events that you
can add to a profile.
In the Avamar Administrator, select Tools > Manage Profiles.
Step Two
In the left pane, select the domain for the custom event profile, and click New
© Copyright
Step Three
In the Profile Name box, type in a name for the new event profile.
For Profile Type, leave the default setting of Email, Syslog, and SNMP Trap
Notification. The Usage Intelligence feature uses the preconfigured Usage
Intelligence profile, do not create a profile that is based on this profile type. This
step results in redundant data being sent to Avamar Support.
Choose whether to enable or disable the profile by selecting or clearing the

Profile Enabled checkbox and the Email Enabled checkbox.
Page
Step Three continued
If you enabled email notifications, then specify whether to send email notifications
as soon as events occur or on a scheduled basis:
• To send email notifications as soon as events occur, select Send data as

events occur.
• To send email notifications on a scheduled basis, select Send data on a
schedule, and
then select the schedule from the list.
© Copyright
Step Three continued
Choose whether to enable or disable syslog notification for the profile by selecting
or clearing the Syslog Notification – Enabled checkbox.
Choose whether to enable or disable SNMP notification for the profile by selecting
or clearing the SNMP Trap Notification – Enabled checkbox. Click Next.
Page
Step Four
The Event Codes page appears, click the All Codes tab. Then select the Notify
on the errors that are needed to trigger the notification.
Click the Audit Codes tab, and then select the Notify checkbox next to the audit
events221 that needed to trigger the notifications.
Click on Finish or Next.
221An asterisk (*) next to an event code indicates an event of such severity that a
notification is sent when that event occurs, even if other event notifications are sent
on a schedule.
© Copyright
Step Five
If you click Next, then the options for Email Notification page appears. In the
Email Subject Header box, type an email subject line for the notification message.
Add an email recipient to the list by typing a valid email address in the Enter
Recipient box and then clicking +. Use the - to remove an email recipient. Click
Next.
You can send a test email message222, by clicking Send Email.
222If the test email message is sent successfully, an Email accepted by transport
layer confirmation message appears.
Page
Step Six
The Syslog Notification page appears.
If the profile includes syslog notification messages, then specify the syslog
notification parameters:
• In the Address (IP or hostname) box, type the IP address or hostname of the
Avamar server node running the syslogd process.
• In the Port Number box, type the port number that is used for syslog
communication.
• Choose whether to include extended event-code information in the syslog
message by selecting or clearing the Include extended event data checkbox.
• From the Facility list, select one of the following: user, local0, local1, local2,
local3, local4, local5, local6, or local7.
Click Next.
© Copyright
Step Seven
If the SNMP Trap Notification message is needed, specify the SNMP parameters:
• SNMP Trap address (IP or hostname)223

• Port Number224
• SNMP Community225
223Type the IP address or hostname of the computer running an application that

can receive and process an SNMP trap.
224Type the port number on the host server that is listening for SNMP traps. The
default data port is 162.
Page
Click Finish.
225Type the name of the SNMP community that the SNMP trap listener is
configured to use. This is a test string that the local Net-SNMP agent uses to
authenticate with SNMP management application.
© Copyright
Server Monitoring
The Avamar Administrator Server view is a primary system status monitoring

tool. The Server Monitor226 tab presents a summarized view of CPU, network, and
hard drive performance statistics for each node.
5
1 2 3 4
1: Node details on the Avamar tab of the Server Monitor are as follows:
• Online (green): The node is functioning correctly.

• Read-Only (blue): This status occurs normally as background operations are
performed and when backups have been suspended.
• Time-Out (gray): MCS could not communicate with this node.
• Unknown (yellow): Node status cannot be determined.
• Offline (red): The node has experienced a problem. If ConnectEMC has been
enabled, a Service Request (SR) is logged.
2: CPU details on the Avamar tab of the Server Monitor are:
• Load: Avamar number of CPU threads over the past minute
226The Server Monitor tab on the Server window in Avamar Administrator includes
separate tabs for the Avamar server and any configured Data Domain systems
Page
• User: Percentage of CPU capacity that is consumed by running server

instructions (anything other than operating system overhead).
• Sys: Percentage of CPU capacity that is consumed by the operating system
overhead
3: Network details on the Avamar tab of the Server Monitor are:
• Ping: Time in seconds that this node took to respond to a ping request
• In: Received packet throughput reported in KB per second
• Out: Sent packet throughput reported in KB per second
4: Disk details on the Avamar tab of the Server Monitor:
• Reads: Average number of hard drive reads per second as reported by the
operating system
• Writes: Average number of hard drive writes per second as reported by the
operating system.
• Utilization: Percentage of total available server storage capacity currently used.
5: The Data Domain tab in the Server Monitor provides CPU, disk activity, and
network activity for each node on the Data Domain system.
If the status is yellow or red, you can view additional status information to
determine and resolve the problem.
6: The following tabs appear on the Server window.
• Server Monitor tab presents a summarized view of CPU, network, and hard
drive performance statistics for the Avamar server. A separate subtab provides
the same information for any configured Data Domain systems.
• Server Management tab shows a detailed view of the server hardware
resources for the Avamar server and any configured Data Domain systems.
© Copyright
• Session Monitor tab shows a list of active client backups and restores
sessions.
• Checkpoint Management tab shows detailed information for all system
checkpoints that are performed for this Avamar server.
• Data Domain NFS Datastores tab lists the temporary NFS share for VMware
instant access on any configured Data Domain systems. The Avamar for
VMware User Guide provides more information about instant access.
System Management
From the left menu, select System, and click Server Management. In this view
administrators can review Checkpoints, Backup Window, Garbage Collection,
and Services.
Server Management in the AUI
1 2 3 4
Page
1: Checkpoints tab displays the latest checkpoints that have been validated (green
checkmark) and unvalidated (red question mark).
• Tag: List the checkpoints on the Avamar system.

• Validated: Red question mark is unvalidated, and green checkmark means it
has been validated.
• Creation Time: The time the checkpoint was generated.
• Nodes: The node number of the system node.
• Stripes: How many stripes in the node.
• Validation Start Time: Time the checkpoint was started.
• Validation End Time: Time the checkpoint finished.
• Errors: Lists any errors that may have occurred during the validation time of
checkpoint.
2: The Backup Window, displays the Backup and maintenance window

duration periods. Administrators can edit the Window start time(in 24 hours),
Duration, and Time Zone.
3: The Garbage Collection window displays the information on the last garbage
collection. The Garbage collection history will provide an overall view of past
garbage collections and display a graphical chart.
© Copyright
4: Services provides details for Core services and Additional services.
The BACKUP GROUP SCHEDULER STATE and MAINTENANCE SCHEDULER

STATE can be changed from either Suspend or Resume.
In the Additional services pane, the details of the services running or not running
are displayed.
Page
Avamar Server Status and Processes
The Avamar server components must be running for successful system operation.
Avamar provides the dpnctl script to allow you to manually start, stop, and check
the status of Avamar server subsystems.
dpnctl status
The dpnctl script is run as user admin from the command line on the Avamar
single node server or utility node of a multi-node server.
For information about the dpnctl command options, type: dpnctl help.
To view the status of the Avamar system components, use the command dpnctl
status.
© Copyright
dpnctl stop
Running dpnctl stop performs a graceful shut-down of the Avamar server

subsystems. Before running the command, verify that the last validated checkpoint
shows a recent date. If not, create and validate a server checkpoint.
To stop the Avamar server subsystems, type dpnctl stop.
dpnctl start
Use dpnctl start to bring an Avamar server back online after a system shut-
down. After the server is back online, verify all server subsystems are up and
running.
Page
To run dpnctl status | start | stop for a particular subsystem, type the
command followed by the subsystem name.
For example, to stop MCS only, type: dpnctl stop mcs.
Executing dpnctl start starts any subsystems that are not already running.
Using dpnctl stop mcs stops both the MCS process and the backup scheduler,
sched. However, using dpnctl start mcs does not restart the backup
scheduler. Be sure to run dpnctl start sched to resume the scheduler.
Avamar Server Data Backup
To protect itself from hardware failures, mcs backs up or flushes its data to the
Avamar server it manages. This preserves all mcs data for a system restoration.
Flushes are done automatically via an avtar227 client session every hour and as
part of system checkpoints.
227 The avtar session used to backup the administrator server is run as MCUser.
© Copyright
Before every flush, a special timestamp file is created in the

/usr/local/avamar/var/mc/server_data directory that includes the time
and date of the flush228.
228
By default, flush backups are stored in the special system domain that is
/MC_BACKUPS.
Page
Email Home Notification
Avamar uses two systems to automatically send events, alerts, and system
information to Customer Support.
• Email Home229
• ConnectEMC
Although they may be disabled, these notifications allow Customer Support to be

aware of any issues with the Avamar server and provide better customer service.
229By default, notification schedule email messages are sent at 6 a.m. and 3 p.m.
each day.
© Copyright
ConnectEMC
ConnectEMC is a standardized application that automatically transfers event data

and product information, such as the serial number of active utility and storage
nodes, from customer sites to Customer Support. ConnectEMC230 is enabled and
configured during installation of the Avamar server.
ConnectEMC can be accessed by selecting Tools > Manage ConnectEMC.
4
2
1
3
1: To edit the Failover Transport, highlight Failover Transport, and click Edit.
230 ConnectEMC is integrated with Secure Remote Support (SRS). Primary and
failover transport can be configured to use FTP or HTML communication. SRS
gives customer support the ability to provide remote Avamar support.
Page
ConnectEMC is integrated with Secure Remote Support (ESRS). Failover transport

can be configured to use FTP or HTML communication. ESRS gives customer
support the ability to provide remote Avamar support.
Clicking the Advanced button opens the settings for Retries, Timeout,
Description, and Email Subject.
Click on the Help button for more details.
2: To edit the Primary Transport, highlight Primary Transport, and click Edit.
ConnectEMC is integrated with Secure Remote Support (ESRS). Primary transport

can be configured to use Email, FTP, or HTML communication. ESRS gives
customer support the ability to provide remote Avamar support.
© Copyright
3: To edit the Notification Transport highlight Notification Transport, and click

Edit.
4: Disable, Stop, and Test can be used to test any of these transports as well as
to test any new changes that are made.
5: The Help button can be used at any time to provide more details for the
ConnectEMC feature.
Page
Server Maintenance Activities Overview
Avamar performs the system-maintenance operations for backup data on the Data
Domain system, including HFS checks, checkpoints, rollbacks, and garbage
collection.
The three important maintenance activities are:
• Garbage collection
© Copyright
• Checkpoints
• HFS checks
These activities are managed internally during the period of time defined in the
Backup/Maintenance Window.231
231During the Maintenance window, the Avamar server runs garbage collection,
checkpoint, checkpoint validation (HFS check), and a final checkpoint.
Page
Scheduling Activities: Backup/Maintenance Window
The Backup Window is that portion of each day reserved to perform normal
scheduled backups. The Backup window232 defines a period of time when the
server does not perform any maintenance activities, including checkpoint, garbage
collection, and checkpoint validation.
The Maintenance Window is reserved for performing routine server

maintenance233 activities.
Any backup or administrative activities234 should be minimized during the

Maintenance window.
232The default Backup window begins at 8 p.m. local server time and continues
uninterrupted for 12 hours until 8 a.m. You can customize the Backup window start
time and duration.
233 This includes garbage collection, asynchronous crunching, a checkpoint, and

checkpoint validation. A second checkpoint is taken and validated during the
Maintenance window. Asynchronous crunching is a process that reorganizes data
inside stripe files to eliminate empty spaces created by garbage collection.
234Backups can be run during garbage collection, checkpoint creation, and HFS
check, and may be paused during HFS check start up. However, running backups
while these activities are running causes both backups and the maintenance
activities to take longer to complete and possibly even to fail.
© Copyright
1: The Window start time can be customized around the scheduled backups, and
does not automatically coordinate with the various backup schedules. May require
manual adjustment if there are any conflicts with the backup schedule.
Page
2: The Duration can be customized, and does not automatically coordinate with
various backup schedules.
Any changes may require a manual adjustment if there is any conflict with backup
schedules.
© Copyright
3: Time Zone can be changed as needed for the scheduling of the

Backup/Maintenance window.
Page
Daily Maintenance: Garbage Collection
Garbage collection is the process of removing235 unused chunks from backups that
have expired. This frees up capacity on the Avamar server.
Garbage collection236 runs once daily starting at the beginning of the Maintenance
window.
235Types of backup data that may be deleted during garbage collection include
expired backups, deleted backups, and partial backups older than seven days.
236
When Avamar is integrated with Data Domain, the space is not reclaimed until
Data Domain runs its maintenance activities, which run on a different schedule.
© Copyright
Daily Maintenance: Checkpoints
A checkpoint237 is a read-only snapshot of the Avamar server taken to enable

server rollbacks. A rollback restores the Avamar server to a known good state
using data stored in a validated checkpoint.
By default, a checkpoint is created238 during the Maintenance window. A second

checkpoint is created towards the end of the Maintenance window after the first
checkpoint has been validated239.
If the checkpoints are being stored on the Data Domain then this is not a validation
process.
It t is a best practice to leave this checkpoint retention policy at the default values.
237 Checkpoints are created using hard links to all the stripes. A checkpoint
directory is created on each active disk of each storage node of the Avamar server.
The directory contains the stripes on the disk as they were at the time the
checkpoint was taken.
238Checkpoints can also be manually created by the Avamar Administrator when

required. By default, Avamar always retains the last two checkpoints including the
last validated checkpoint.
239 Checkpoint validation is performed by running a Hash File System (HFS) check
on a checkpoint. The process that performs HFS checks is hfscheck, which is
similar to the UNIX fsck command. While an HFS check is being initiated, the
server is briefly placed in read-only mode until it finishes. HFS check validates the
integrity of a checkpoint by performing a series of checks on the stripes. If HFS
check detects errors in one or more stripes, it automatically attempts to repair
them.
Page
By default, a rolling HFS check240 is automatically run once a day, usually during
the period defined by the Maintenance window. The default settings for HFS
checks can be modified to accommodate an environment for an individual site.
240A full HFS check performs checks of all the stripes. A rolling HFS check
performs checks of all new and modified stripes and a subset of unmodified stripes.
When a checkpoint has passed either type of HFS check, it is considered reliable
enough to be used for a system rollback. Rollback is the process of restoring the
Avamar server to a known good state using data stored in a validated checkpoint.
© Copyright
Managing Checkpoints
Under the Server Management tab, select Checkpoints tab. In the window you
can see the two checkpoints that are created, and the details on the right side in
the Details pane.
From this pane, a new checkpoint can be created. Click the +CREATE for a new
checkpoint.
Page
Best Practices for Scheduling
It is best practice to use the following when scheduling backups:
Use the default241 operational window schedule.

Schedule242 the backups to run and complete during the
Backup window.
Limit on-demand243 backups during the Maintenance
window.
Limit starting on-demand maintenance activities.244
Make sure the Maintenance scheduler is enabled.
Impact of Maintenance Activities and Backups
Avamar minimizes the impact of maintenance activities on backups by internally

managing the maintenance activities according to the operational windows.
When the system is in a read-only state (during checkpoint and garbage collection),
these system administration tasks cannot be performed:
• Adding, editing, or deleting a user, client or domain
241 Only change the start times/durations of the windows if necessary.
242 Do not schedule backups close to or during the Maintenance window.
243 Avoid starting any on-demand backups during HFS check process.
244
Running on-demand maintenance temporarily disables ALL scheduled
maintenance activities.
© Copyright
• Deleting a backup
• Changing a backup retention
The following table shows the operational impact on backups:
Checkpoint • No other maintenance jobs can start.

• All backup orders are queued until
checkpoint completes.
Garbage Collection • No other maintenance jobs can start

• New backups are queued.245
HFS Checks • Garbage collection cannot start246.

• All backup work orders will be queued
until the HFS has started.
• New backups are queued247.
Backups Checkpoints248 can start.
245 Queued if more than eight backups per node, less 1 for the overall system.
246 All other maintenance jobs, such as checkpoint, replication, etc., can start.
247 If more than 8 backups per node, less 1 for the overall system.
248 Backups are suspended while a checkpoint is running.
Page
Impacts of Maintenance Activities on Data Domain
Avamar performs the system-maintenance operations for backup data on the Data
Domain system, including HFS checks, checkpoints, rollbacks, and garbage
collection.
Avamar runs maintenance every day for 12 hours249, it communicates the same to
Data Domain250 as well. Data Domain does not run any maintenance on a daily
basis, only cleaning weekly.
Avamar and Data Domain operations impacted are:
Garbage Collection (GC) GC runs daily and identifies hashes that

have expired and hashes from cancelled or
failed backups. At same time the hashes are
sent to the Data Domain251 to clear the
corresponding data.
249During this 12 hour period Garbage collection runs 3 hours, the other time is
spent on checkpoints and HFS checks. If the HFS check completes before the 12
hour window, the maintenance will complete.
250When Avamar and DD are integrated, the Data on DD has to match the Meta
Data on Avamar; the sync between Avamar and Data Domain is critical in terms of
data and meta data.
251Data Domain runs cleaning only once a week. On a daily basis, it moves the
data to /DELETED directory under its cur directory under the Avamar Mtree. By
default, on Tuesday when Data Domain runs cleaning, it clears the entire
/DELETED directory. Recoveries of backups are not possible after hashes are
deleted from Avamar, and the space is reclaimed from Data Domain only after
weekly cleaning is successful.
© Copyright
Checkpoint Avamar creates a checkpoint, then the Data

Domain takes a snapshot252 of the entire
directory /CUR.
HFS Check HFS verifies the integrity of the data.
252In the event of a roll back on Avamar, the cp allows the Data Domain to run a
fast copy operation of that snapshot back to its point in time.
Page
1: The ddrmaint utility implements all required operations on the Data Domain
system for the Avamar server.
The ddrmaint utility is installed on the utility node of a multi-node server, or the
single node of a single-node server, during Avamar server installation. The
ddrmaint utility is not installed on the data nodes of the Avamar server.
ddrmaint utility:
• Implements all required operations

• Installed on utility node of multi-node server, or single node of single-node
server
• Not installed on data node
Avamar Server Capacity Definitions
The goal of managing the capacity of the Avamar server is to achieve a “steady
state253” capacity where the rate at which new data chunks are added to the server
is equal to or less than the rate expired data chunks removed from the server.
New bytes are added to the Avamar server through the backup process. Old bytes
are removed from the server through expiring or deleting backups.
Avamar Server Capacity Definitions
OS View Total file system usage254
253 Steady state is the rate at which new data chunks added to the Avamar server
is equal to or less than the rate expired data chunks are removed from the server.
© Copyright
GSAN View255 The total allocated to stripes minus the

space that is freed by garbage collection
100% User Capacity When gsan capacity hits 65 percent256 of

Avamar storage
cur View The amount of data that is measured by the

OS in the current working directory257
254 The total amount of data in each data partition which is measured by the OS.
This includes the total data in the cur directory, plus checkpoint overhead and
additional overhead in other directories. Approximately 20 to 25 percent is reserved
for checkpoint overhead. The remaining capacity is used for maintenance and
other OS activities.
255The gsan or Storage subsystem capacity is the total amount of commonality

factored data and RAIN parity data (net after garbage collection) on each data
partition of the server node. The gsan view of capacity utilization is defined as the
total allocated to stripes (du of the cur directory) minus the space that is freed by
garbage collection plus the RAIN parity data stored on each data partition on each
Avamar server node.
256The Avamar server transitions to a read-only state when this occurs. This is
referred as the read-only threshold.
257The cur view of capacity utilization is the amount of data as measured by the
OS that is in the current working directory in each of the data partitions (data0#/cur)
on each Avamar server node. This capacity is approximately equal to the sum of
the maximum allocated sizes of all the stripes in the /data0#/cur directories.
Page
Avamar Server Lifecycle Management
A new deployed Avamar system typically fills rapidly for the first few weeks. This is
because nearly every client backed up contains large amounts of unique data.
Avamar’s commonality feature is not leveraged until several similar clients have
been backed up or the same clients have been backed up at least one time.
Once each client has been backed up a “settling” occurs. At this time it is possible
to consider and measure the ability of the system to store about as much new data
each day as it frees during the maintenance windows.
This is referred to as achieving a “steady-state”258 of capacity utilization. Achieving

steady-state capacity259 utilization is especially important for single-node Avamar
servers because the capacity cannot be increased.
Achieving steady-state capacity utilization is also important for multi-node servers

to minimize the number of additional nodes required to manage the capacity.
258The system achieves steady state shortly after the longest retention period for
the backups.
259The system achieves steady state shortly after the longest retention period for
the backup.
© Copyright
Factors Affecting Capacity Utilization
The following are factors affecting capacity utilization:
• Amount of primary data being backed

up
• Initial backup commonality260
• Day-over-day backup commonality261
• Retention period262
Understanding Checkpoint Overhead
Checkpoints263 require storage overhead. The more

data per node, the greater the time required to perform checkpoints.
During the backup process, the Avamar client generates variable-sized data
chunks and the hashes of these chunks. Data is sent to the Avamar server, where
it is stored in stripes264. There is a hard link to data stripes from the cur directory.
260
Initial deduplication rate for the Avamar server across all clients is typically
about 70 percent for file system data, 35 percent for database data.
261Typically file system backups yield a 0.3% daily change rate, database backups
with a moderate change rate yield a three to five percent daily change rate.
262The number of daily, weekly, monthly, and yearly backups are retained. A best
practice is to use the advanced retention policy for backups.
263When a checkpoint is created, a hard link is created from the checkpoint

directory to the stripes and the stripes are set as read-only.
Page
CU CP CUR CP CUR
Stripe A Stripe A Stripe A Stripe A

Read/Write Read only Read only Read/Write
The metadata stripes are 36 Megabytes and data stripes are 40 Megabytes.
Factors Affecting Checkpoint Overhead
Factors affecting checkpoint overhead are:
• How empty stripes are when they are re-used265.

• System daily change rate
264 When there is an activity requiring modification of a stripe, such as adding new
data to a stripe, the read-only stripe, is copied to a writable stripe. The original
stripe associated with a checkpoint is maintained for the life of the checkpoint.
Creating the new stripe is checkpoint overhead.
265 Fuller stripes create more overhead.
© Copyright
• Checkpoint retention
• Whether HFS check succeeds every day
In steady state, Avamar places new data in the emptiest space.266 When re-using
existing stripes, the stripes are filled with chunks to the maximum267 allocated size
of the stripe.
Checkpoint overhead grows faster as the system disk space usage increases, due
to stripes that are more full being reused.
Important: Be sure garbage collection runs every day so emptier

stripes are created and are available to be reused.
Important Capacity Thresholds
It is important to manage the capacity of the system daily. The administrator can
control the gsan capacity through dataset definitions, retention policies, the clients
backed up to the Avamar server, and by ensuring garbage collection runs regularly
to remove expired data.
Important warnings are as follows:
266 Either reuses existing stripes or creates new stripes.
267After reaching the maximum size, even when data is deleted and removed from
a stripe, the size of the stripe remains the maximum size.
Page
• Capacity Warning is
issued when utilization
exceeds 80 percent of the
user capacity268.
• Garbage collection does
not run when OS capacity
utilization exceeds 85
percent.
• New stripes are not
created when OS
capacity exceeds 90
percent.
• Health Check Limit
occurs when 95
percent269 of user
capacity is consumed.
• New checkpoints are not created after the OS capacity utilization reaches 96
percent.
Important: Coordinate with Technical Support before making any

changes to Avamar maintenance windows.
268 The administrator has to take actions when you start to receive warnings.
269
Backup activity is suspended, although existing backups are allowed to
complete.
© Copyright
When OS View Exceeds 85 Percent
When the OS view of capacity utilization exceeds 85 percent, the garbage

collection process stops running. As checkpoints roll off, garbage collection
resumes until the OS view once again exceeds 85 percent.
Be advised, Dell Technical Support intervention is required when:
• Look for extraneous directories and files on

each node
• Reduce the number of checkpoints retained:
1. Always retain at least two most recent.

2. Delete the oldest checkpoint
Important: It is recommended to always retain at least the two most

recent checkpoints. When deleting checkpoints to free up space,
delete the oldest first.
Capacity Warning Threshold
When data is added to stripes, the stripes are filled with chunks up to the maximum
allocated stripe size. Even when data is deleted and removed from a stripe, the
size of the stripe remains the same.
Page
The implications are, if on a data partition, the GSAN view of capacity utilization
grows to 50 percent 270of the total available OS capacity.
Possible causes for warning issued when utilization reaches 80 percent of user
capacity are:
• Do not add271 more clients to system

• Examine the client backing up to the Avamar
• Reassess retention272 policies
• Make sure garbage collection273 is running
daily
• Is is possible to decrease the GSAN view of
capacity utilization but you cannot decrease the cur capacity utilization view. 274
270For an example, and half of the data is expired over time as garbage collection
removes the deleted data and the GSAN view of capacity utilization will reduce
down to 25 percent. However, the cur view of capacity utilization remains at 50
percent.
271 Consider adding more nodes to the Avamar system.
272 Use advanced retention policies on scheduled backups.
273Check to be sure the garbage collection is freeing up the same amount of data
that is being added. And check is the time allocated to the Maintenance window
sufficient for adequate collection to take place.
274 The capacity allocated to the stripes.
© Copyright
Important: The duration of key maintenance activities such as HFS

check and checkpoint operations are directly proportional to the cur
capacity.
Capacity Read-Only Threshold
When user capacity utilization is at 100 percent, the Avamar server transitions to a
read-only state.
• No more data can be backed up to the server.

• Restores are possible, and all maintenance activities
continue to run.
• Stop all replication.
Technical Support must be contacted to make the

Avamar server writable again.
The following are a couple of actions that may be taken by Dell Technical Support:
• If it is planned to expand system capacity within a few days, Technical Support

may temporarily raise the threshold until the new capacity is added.
• If it is not possible to expand the capacity within a few days, backups must be
deleted and aggressive garbage collection must be run.
Managing Capacity Utilization
Administrators need to monitor the capacity utilization of the Avamar server daily
and understand how to interpret the system reported warnings and errors.
Avamar checks the capacity of each Data Domain system every 24 hours. Avamar
then logs an event in the Event Monitor if the capacity reaches 95 percent full, or if
the forecast number of days until the capacity is full and less than or equal to 90
days.
Page
2
1
1: By selecting the Data Domain system from the tree in the left pane, the Data
Domain system details appears on the right.
Here are the Data Domain system capacity details.
Total Capacity (post-comp size) The total capacity for compressed data on
the Data Domain system.
Server Utilization (post-comp size) The percentage of capacity used on the Data
Domain system for any reason after
compression of the data.
Bytes Protected 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.
File System Available (post-comp The total amount of disk space available for
size) compressed data in the Data Domain File
System.
File System Used (post-comp size) The total amount of disk space used in the
Data Domain File System for compressed
data.
© Copyright
2: The Server Management tab in the Avamar Administrator server view

provides the details for the Avamar server. Select the Avamar server, and details
appear on the right.
Total Capacity Total amount of server storage capacity
Server Utilization Percentage of total available server storage

capacity currently used
Bytes Protected An estimation of the total amount of client

data in bytes that has been backed up on
this server
3: This table describes the behavior of various threshold limits.
Less than 75 percent The system is considered to have adequate

capacity for future backups.
Page
75 percent Study server storage utilization to determine

whether the server has
adequate capacity to store future backups.
80 percent A pop-up notification warns you that the server

has consumed 80 percent of its available storage
capacity. Study server storage utilization to
determine whether the server has adequate
capacity to store future backups.
90 percent Study server storage utilization to determine

whether the server has adequate capacity to store
future backups.
95 percent The server has reached the default health check

limit, which is the amount of storage capacity that
can be used and still have a “healthy” server.
Avamar completes all in-progress backups, but the
dispatcher stops new backup activity.
100 percent The server has reached the read-only limit and
automatically becomes read-only to protect the
integrity of the data that is already stored on the
server. If ConnectEMC has been enabled, a
Service Request (SR) is automatically logged.
4: This view is in the Avamar UI, and it shows the Capacity Overview.
This provides an overview of the Location, Full%, Space Used, and Space Left of
the Avamar.
This image shows the following:
• 43 GB Storage Used
• 767 GB Storage Available
© Copyright
Checkpoint Utilization
Checkpoints reside on each storage node on the Avamar server. This information
can be used to determine the overhead space of each checkpoint.
The cps command shows the total amount of data in cur for each checkpoint
directory on the node in which the command is run.
Tip: The cps command can only be run from single-node server or
multi-node server storage nodes. In a multi-node server environment,
you must first copy the cps executable file from the utility node to
each storage node.
Page
capacity.sh
Click to enlarge the image.
The capacity.sh utility provides the net rate of change275 in the system for each
day over a period of the last two weeks. It also identifies the clients with the highest
rate of change.
Some useful commands include:
275This information can be used to assess whether the system is running in steady
state, including the average rate of change in the environment and the
effectiveness of garbage collection.
© Copyright
capacity.sh –days=20 –-top=10 Check capacity of the storage over the

last 20 days for the top 20 clients
capacity. sh --days=20 -- Check capacity of the storage over the

top=20 --domain=ddr last 20 days for the top 10 clients in
Data Domain
Important: If capacity.sh script is not available, it can be added by

Dell EMC support.
Page
DPN Summary Report
The DPN Summary report276 lists the summary information about data stored in the
Avamar server and statistical data for each client backup. This report can also be
generated with the Fitness Analyzer.
1: Select from the list DPN Summary and click Run.
The Date Range will appear. Select the dates needed for the report. Click
Continue and the DPN Summary Report will appear.
276 This is used to determine daily change rates for each client, high change rate
clients, amount of data protected, number of clients being protected, abnormal
client behavior, and estimate of commonality factoring and compression.
© Copyright
1: Bytes for files modified (sum of ModReduced + ModNotSent + ModSent) is

equivalent to what a traditional backup sends in an incremental backup.
Avamar change rate is equivalent to the ModSent divided by TotalBytes: ModSent

/TotalBytes. The Avamar commonality equal 1 minus the change rate
In the DPN Summary some of the data contained in the report are:
Host Client hostname
StartTime Date and time the backup was initiated
Seconds Duration of the backup
Page
ModReduced Bytes from modified files reduced by

compression
ModNotSent Bytes from modified files that are not

sent to the server
ModSent Bytes from modified files that are sent

to the server
TotalBytes Total number of bytes examined during

backup (This is equivalent to what a
traditional backup sends in a full
backup).
PcntCommon Commonality % during backup
Status Final Status of the client backup
NumFiles Number of files scanned
NumModified Number of modified files
Backup Statistics
For detailed information about a specific backup, look at the backup statistics
available from the Avamar Administrator; Backup, Restore, and Manage view,
under the Manage tab.
Locate the backup, then select Actions > View Statistics.
© Copyright
1 2
1: The Details tab shows detailed information including the client name, completion
date and time, bytes excluded, bytes new, bytes modified, bytes modified sent, and
bytes modified not sent.
This information is also available for backups less than 72 hours old from the
Activity view as well as in AUI Details pane.
Page
2: The Files tab shows total bytes, percent present, and percent new for a sample
of files in the backup.
The files selected for the sample tend to be the largest files and those with the
highest change rate.
3: The Backup Statistic report can be exported out to .csv and used or saved for
other reports. Click Export.
The Save window appears. Select the name for the report and click Save.
© Copyright
Logs, Troubleshooting, and Reporting
Avamar Processes and Logs
Administrative Processes
Administrative processes carry out all administrative and management activities of

Avamar. The following administrative processes run on single-node servers and on
utility nodes of multi-node servers:
Administrator server (MCS) Other Administrative Processes
Page
MCS and cron Logs
Administrator
server logs
Logs for activities run

by cron
Click to enlarge image.
Administrator server logs277 include mcserver.log*, flush.log*, and restore.log.
Logs for activities run by cron278 include health_check.log and replicate.log.
MCS Logs cron Logs
277Administrator server logs are located at /usr/local/avamar/var/mc/server_log on

the utility node.
278 Logs for activities run by cron are located at /usr/local/avamar/var/cron on the
utility node.
© Copyright
Include mcserver.log*, flush.log*, and Include health_check.log and

restore.log replicate.log.
Located at Located at /usr/local/avamar/var/cron on

/usr/local/avamar/var/mc/server_log on the utility node
the utility node
Maintenance Activities Logs
Checkpoint, HFS check, and garbage collection are located in the

persistent store at location /sysinfo/log.
avmaint and dumpmaintlogs commands are used to view the

contents of /sysinfo/log directory.
the avmaint and dumpmaintlogs commands should be used to
view these logs, since the directory, /sysinfo/log, is not available to
the regular file system. Given below are few examples of using
these commands.
• To create a file containing checkpoint logs for February 2020:
avmaint cat /sysinfo/log/2020/02/cp >
cpfeb2020.log
• To create a file containing garbage collection activity of the
previous day:
dumpmaintlogs --days=1 --types=gc >
gcyesterday.log
• To view HFS activity from February 2020:
avmaint cat /sysinfo/log/2020/02/hfscheck |

view -
Page
Client Log Message Severity Levels
Info: Standard,
Warn: Investigation
informational; no
required
action required
Error: Problem
encountered, FATAL: Root cause
requires corrective analysis required
action
Click to enlarge
Log messages contain the following parameters:
• Time279
• Event Codes280
• Severity Levels281
279
The time displayed in log messages is the local time of the client machine.
However, there may be instances where the server time is used.
280 Event codes are numbers given between '<' and '>' in the error message.
281
As shown in the image, security levels indicate four levels of information: Info,
Warn, Error, and Fatal. Except Info, all other levels require corrective action.
© Copyright
Data Server Logs
Data server logs are located in /data01/cur on single-node

servers, and on each storage node of multi-node servers.
Page
Data server logs include gsan.log282 and err.log283. The size of the
log file is limited to 25 MiB284. The file contains the most recent
information.
282 gsan.log is the log file for the gsan process.
283err.log contains warnings and errors that are useful for troubleshooting specific
error conditions and issues.
284When a gsan.log file reaches the limit, it is renamed to gsan.log.001; the

existing gsan.log.001 is renamed to gsan.log.002, and so on. By default, the
maximum number of log files retained is 100.
© Copyright
Data Server Log Entries
When examining the logs for error conditions, search for the following severity
levels:
• WARN: Recoverable issue, investigation required

• ERROR: Serious error, requires immediate corrective action
• FATAL: Critical problem, requires immediate corrective action
Note:
• Logs on the storage nodes use GMT timestamps.
• Avoid searching for the word, 'ERR, as 'ERR' is used in
many messages such as 'MSG_ERR_NONE' and does not
necessarily indicate an error.
Page
getlogs Utility
The output of the getlogs script is a single tar file that contains the compressed logs
from all nodes.
On a multinode
server, load the SSH
keys
Each sub-directory
contains the compressed
logs of corresponding
nodes
Click to enlarge
© Copyright
Client Logs
Client logs located on client machines provide information about backup and
restore operations, and the user interface.
avtar logs Workorder logs285 avagent logs286 avscc logs287
285 Provide detailed information about a specific task.
286
Provide information about the status of all backup and restore activity on the
computer.
287 Provide information about the performance of the user interface. A console log
is created for each user on a computer.
Page
Adding More Details to Client Logs
Several useful options288 are available to enhance client logs and provide more
information about a backup for troubleshooting purposes. Some of the useful
options are:
288
The options can be specified when configuring backups from Avamar
Administrator or included in the avtar.cmd file or other tag files.
© Copyright
--stats289 --comstats290 --verbose=2291 --debug292
Note: As these options potentially increase the size of the logs, it is

important to discontinue their use after the information they provide is
no longer required.
Client Cache Files
Avamar maintains two cache files on each backup client:
File Cache Hash Cache
289 Displays throughput statistics at the end of the avtar operation.
290
Used rarely; prints throughput performance every second and is useful for
understanding network performance issues.
291Turns on highly verbose messages including the avtar session ID and mount
point information for each backup.
Verbose= 3 or 4: shows every file being backed up.
292 Used rarely; turns on debugging messages.
Any requirement to escalate a client issue to Dell EMC Technical Support. Debug
messages are enclosed in brackets and display GMT timestamps.
Page
The file cache plays an important role The hash cache screens out duplicate
when backing up file systems: compressed chunk data.
• The file cache, f_cache.dat, is used • The hash cache, p_cache.dat, is used
to determine if a file has previously to determine if a sub-file object has
been backed up. previously been backed up without
having to communicate with the
• Every entry in the file cache is 44
Avamar server.
bytes, which constitutes various
hashes of the file, metadata, and a • The hash cache includes a 20-byte
header for each entry. SHA-1 hash for each chunk, which is a
hash of the contents of the chunk. A 4-
byte header is also also included.
Effectiveness of Cache Files
1 TB FIle Cache 20 GB Hash cache 3 MB

screens out 98% reduces the size of
of files data to 0.3%
File system data
1 TB FIle Cache is not 1 TB Hash cache 30-50 GB

effective in the reduces the size of
case of databases data to 3% - 5%
Database data
Avamar Server
Click to enlarge
File cache and hash cache help reduce the time for backup, as well as CPU
utilization at the client and server.
© Copyright
• In file systems, file cache screens out 98% of the data293.

• In the case of databases, the hash cache reduces the data to 3% to 5% of the
original data294.
Default Size of Cache Files
File Hash Cache Main Memory
The size of cache files grows with the increase in the number of backups295.
• File Cache can grow up to 1/8th the size of main memory.

• Hash Cache can grow up to 1/16th the size of main memory.
293The remaining data is further reduced by the hash cache before being sent to
the Avamar server.
294In the case of databases, the file cache is not effective, since the whole
database is treated as a single file.
295 During a backup, the caches are read into memory and then written out at the
end of the backup. The sizes of the cache files are printed near the beginning and
at the end of the avtar logs.
Page
Troubleshooting
Troubleshooting
Challenges when Managing Backups
Some of the challenges in achieving successful backups are:
© Copyright
Client I/O High Client Operator Incorrect Disconnected

Network
Errors297 Activity298 Actions299 Input300 Client301
Errors296
Managing Backups Successfully
The following actions help reduce errors and perform successful backups.
296 Network issues that interrupt the connection can cause backup failures.
297 Input/output errors on the client can lead to incomplete backups as some data is
left behind.
298High client activity levels can prevent files from being backed up. These tasks
have 'completed with exceptions' as their status. High client activity can prevent
backups from completing within the backup window.
299 Sometimes operator actions, such as rebooting or canceling, cause backup

failures.
300
Backup failures can be caused by incorrect or incomplete dataset definitions
and retention periods.
301 Data from client machines that may be disconnected from the network can lead
to incomplete backups.
Page
Monitor daily activities302 Resolve exceptions Schedule maintenance

activities303
302
Regularly review the Activity Monitor and other backup activity reports to ensure
healthy backups.
303Ensure the maintenance activities are scheduled in such a way that they do not
overlap with backup activities.
© Copyright
cid.bin File
cid.bin file is essential for the client to communicate with the Avamar Server.
• Located at /<Install Location>304/var on the client machine

• File contains:
− Name of the Avamar server

− Client ID (CID)
− UNIX time of the creation of the file
Potential Client Initialization Issues
Initial backups can be large, and this may lead to issues with client initialization.
Potential issues include:
304In windows, it is located at C:\program files\avs\var. In Linux machines, it is

located at /usr/local/avamar/var.
Page
Time-out
 Large backups time out at the end of backup window or

schedules305
 Overtime306
 Partial Backups307
305
As initial backups are larger than daily backups, initial backups time out at the
end of the backup window that is configured to meet daily backup requirements.
306
'Overtime' must be enabled so that initial backups don't get timed out, but
complete by taking extra time.
307
Partial backups may be created on the server due to timed out backups. The
Avamar completes the partial backups during subsequent scheduled backups.
© Copyright
Network Issues
Initial backups may fail due to network issues at the

customer environment, as well as manual interventions.
• Available WAN bandwidth308

• Backup using LAN309
• Fragment backups310
• Run 'ping' test311
308 Sometimes the available WAN bandwidth may limit the backup throughput of
large initial backups that run for long time.
309To perform initial backups across a LAN connection, seed the Avamar server
with the remote client's data via a local connection.
310Partial backups may not be saved if the backup ends abruptly. Hence, it is a
good practice to break the backup into smaller datasets to avoid such situatons.
311Always run "ping" test between server and client to validate any network
connectivity issues.
Page
Manual Interventions
Manual interventions, such as cancelling a backup, result in

failed backups. Manually cancelled backups generate
different error codes:
• 10013: Canceled by client

• 10019: Canceled by the administrator
Identifying Server Issues
HFS checks validate the integrity of the Avamar data server. A failed HFS check
requires immediate attention.
Event Code Event Description What does it mean?
4003 hfscheck_cron - completed Data server is working fine.

hfscheck of cp.<ID>
4004 hfscheck_cron - failed hfscheck of • Requires immediate

cp.<ID> attention
• HFS check - manually
terminated.
© Copyright
Rolling Back to a Checkpoint
Rollback is the process of restoring the Avamar server to a previous state using
validated checkpoint data.
• Perform rollbacks using rollback.dpn

• Force rollbacks using --force_rollback option
• Look for exceptions
Avamar Fitness Analyzer and Reports
About Fitness Analyzer
Page
Avamar Fitness Analyzer312 organizes information from disparate sources into

cohesive reports.
• Reports: provide a history of recent activities and events

• Summaries: provide a visual analysis of trends and server behavior
• Component structure313
• Avamar Web User Interface (AUI): used to access Fitness Analyzer
About the Interface
Like the AUI, the Fitness Analyzer portal provides access to all functional areas
through the navigation pane on the left. The navigation pane provides access to the
following Fitness Analyzer features:
312 The Avamar Fitness Analyzer is a reporting and analysis portal that provides a
visual representation of server health and functionality. Reports generated by the
Fitness Analyzer help administrators troubleshoot issues and optimize system
performance.
313Fitness Analyzer allows administrators to dive deep into preferred areas of

analysis. Apart from creating the reports using predefined workflows, the tool
focuses on a subsequent analysis based on preceding steps.
© Copyright
Overview314 Reports315 Client

Group Replication Summary318
Summary316 Summary317
314 Provides a high-level view of Avamar server status and recent history.
315Generates and displays Avamar server reports that capture a snapshot of the
server at one point in time.
316Displays statistics and summaries of recent group activity. Provides a

breakdown of group activity to the client.
317 Summarizes trends for replication activities between Avamar servers.
Page
Proxy Backup System Metadata System

Summary319 Summary320 Utilization321 Utilization322 Summary323
Overview and Header Pane
Overview Pane
The Fitness Analyzer Overview pane presents a graphical timeline of recent server
activity.
318Provides a history of recent client activities and a graphical summary of backups

from each client.
319
Displays statistics and summaries for all VMware proxies and vCenters in the
Avamar environment.
320Reports completed and failed backup jobs with a summary of reports by error
code.
321 Illustrates trends of system health information at the node or resource level.
322 Displays recent server metadata usage history.
323Displays a detailed account of the Avamar server and configuration

specifications.
© Copyright
Timeline324 Legend Server Health325
324The timeline identifies areas of interest, such as high traffic, delayed backups or
replication jobs, and interference between backup activities and server
maintenance. The summaries in the navigation pane provide a breakdown of the
trends indicated here.
Page
Flags326 Scale Bytes View
Header Pane
The Fitness Analyzer header pane at the top-right corner of the window contains
common controls that apply to all functional areas. It provides access to the
following features:
325Fitness Analyzer marks important server health events, such as checkpoint

creation and validation, and garbage collection, as vertical lines that correspond to
the start and finish times of the event.
326Flags are bubbles on the timeline that carry a number and a character. These
values identify important events for specific data series. For example, the flag '1R'
means that a replication group started at the time indicated by the flag's location.
The flag '1G' means that a backup group started at the indicated time.
© Copyright
Reload327 Configuration328 User329 Help330
Limitations of Fitness Analyzer
The Fitness Analyzer has few limitations in the following areas:
Active Jobs Initial Creation of Panes Results Cache
327 Refreshes the reporting data across all summaries and server health panels
328Changes between the default timeline reporting period and a user-defined

custom reporting period. The default timeline reporting period is seven days.
However, the administrator can customize the timeline for specific dates.
329 Logs the administrator out of the interface
330 Redirects to the Fitness Analyzer online help
Page
Reports and summaries During the initial creation Results are cached for
do not show active or of each pane, Fitness approximately 15 minutes
running jobs. These jobs Analyzer takes more time from their time of creation.
appear in reports pane than usual to display If moved away from a
and summary panes after results. The subsequent pane, the data may not
completion. results are cached to regenerate until the cache
provide faster results. expires.
Reports
Apart from reports available in MCS and Avamar Administrator, Fitness Analyzer
reporting331 provides two additional reports332.
331Fitness Analyzer reports are snapshots of different aspects of the server at

particular points in time.
332Pending Replication shows the number of backups and the amount of primary
data that are awaiting scheduled replication. Avamar - Capacity Report shows the
© Copyright
• Generate reports from the Reports pane

• Download and review generated reports
Summaries
Summaries333 provided by Fitness analyzer include Group summary, Replication

summary, Client summary, Proxy summary, Backup summary, and System
summary.
1
2
3
4
5
1: Group Summary
daily changes in capacity usage, such as new data backed up to the Avamar
subsystem, and capacity freed by garbage collection.
333Summaries or Data Summaries in the navigation pane focus on individual

aspects of the server history presented in the Overview pane. Summaries can be
accessed from the Fitness Analyzer pane on the left.
Page
The Group summary tab presents the group summary report334. Its features
include:
• Summary of activities of a group

• Tabular chart that lists performance statistics
• Information about clients and plug-ins335
• Backup Timeline tab shows start and stop times of activities
• Groups Timeline tab shows scheduled start and stop times of activities
2: Replication Summary
334Group summary report is a high-level overview of backup group activities within

the reporting period.
335The Group Summary tab shows information about clients and plug-ins that took
part in an activity. This information includes the client name and domain, plug-in
name, start and completion times, duration, amount of data transferred, and result
codes.
© Copyright
The Replication summary pane provides statistics about the performance of

replication jobs in the server.
• The pane contains the Replication summary report.

• Presents an overview of replication group activities within the reporting period.
• The Not Replicated column identifies the number of backups for which
replication is still pending
3: Client Summary
The Client summary pane provides statistics that summarize the behavior and
attributes of individual Avamar clients.
Page
• View history page opens to the Statistics tab.336

• The Backup Timeline tab shows start and stop times of client activities.
4: Proxy Summary
The Proxy summary pane summarizes the performance of entities within a vCenter
environment. This pane contains two tabs:
• Proxy Summary337
• Proxy Timeline338
5: Backup Summary
336The Statistics tab contains two panels: a tabular report at left and a graphical
report at right. The tabular report displays all of the recorded client activities over
the duration of the reporting period. The graphical report breaks down the
completion codes for each job in the tabular report.
337The Proxy summary tab presents a high-level overview and statistics of

activities in virtual environments within the reporting period. The tabular chart lists
performance statistics, such as the numbers of known VMs, containers, VMs within
containers, proxies, and automatically discovered VMs, in each vCenter.
338The Proxy timeline tab presents a graphical report that plots the scheduled start
and stop times for each activity in the virtual environment within the reporting
period. The timeline displays proxy servers and associated activities in a selected
vCenter.
© Copyright
The Backup summary pane provides statistics that summarize the results of
individual backups on the server. This pane contains three tabs:
• Status codes339
• Error codes340
• History341
6: System Summary
The System summary pane provides a detailed breakdown of the server

configuration. The configuration tree provides access to the following:
• System configuration
339The Status codes tab presents a top-level summary of backups, sorted based
on result codes, within the reporting period.
340The Error codes tab presents a top-level summary of backups based on error
codes within the reporting period. Fitness Analyzer displays a table with a summary
of each backup, including the client, plug-in, domain and group, backup type, start
and stop times, and related error codes.
341Backup History page displays a table with a summary of each backup, including
the client, plug-in, domain and group, backup type, start and stop times, and result
codes.
Page
• Network configuration
• Software versions
• License information
• Schedule of operations
• Additional Avamar services
• Miscellaneous services
• Detailed node information
Custom Profile - Email Notification
Custom event profiles enable you to send notifications, such as emails, when
specific system events occur.
• Email notifications can be configured to send immediately or at scheduled

times.
• A custom profile needs to be configured to send email notifications.
© Copyright
Creating reports with Avamar Administrator
The Avamar Administrator tool can be used to generate reports for several of the
administrator server database views. To create a report:
• Select Manage All Reports under Tools.

• Select the domain and click New.
• In the New Report window, enter necessary details342, and click Ok.
342 In the New Report window, enter necessary details such as name, title, and
description of the report. select the report view from the drop-down list, and set
filter options. After clicking OK, the report name is listed under the selected domain
in Manage All Reports.
Page
Note: If the report is intended to be sent as an email notification,

create the report at the root domain level.
© Copyright
Using Administrator Server Database for Reporting
The Administrator server uses a PostgreSQL343 database to store data:
• Accessed using: PostgreSQL compliant ODBC interface344
343
PostgreSQL is an open-source Relational Database Management System
(RDMS).
344
Information in PostgreSQL can be accessed through any PostgreSQL-compliant
Open DataBase Connectivity (ODBC) interface. ODBC includes Crystal Reports,
Page
• Filename of Administrator server database: mcdb

• Located at: /usr/local/avamar/var/mc/server_data/postgres
Important: Do not modify any data in mcdb tables manually. Directly

modifying administrative server operational data can lead to loss of
referential integrity, which could result in loss of data. Only read-only
views of the database are supported and maintained as customer
interfaces.
Database Views
MCS database views define the types of information you can access from the
Avamar Administrator. Shown below are some of the supported database views:
Database Views (1 of 2)
Database Views Description
v_activities_2 Contains a record of each backup,

restore, or validation activity
v_dpnsummary Contains a record of each backup,

restore, or validation activity on a
client-by-client basis
MS Query, and Microsoft Excel. You can also access the information with a local or
remote psql tool.
© Copyright
v_clients_2 Contains a record of each client

that is known to the MCS
v_plugins Contains a record of each plug-in

installed on any client known to
the MCS
v_datasets Contains a record of each dataset

that is known to the MCS
v_ds_targets Contains a record of each source

target that is defined for each
dataset
v_ds_commands Contains a record of each optional

plug-in command that is defined
for each dataset
v_events Contains a record of each event

logged by the MCS
Database Views (2 of 2)
Database Views Description
v_groups Contains a record of each group

known to the MCS
v_group_members Contains a record of each client

organized by group assignment
v_retention policies Contains a record of each

retention policy known to the
MCS
v_schedules_2 Contains a record of each

schedule known to the MCS
Page
v_node_util Contains a record of node

statistics retrieved or calculated
per node at a particular date and
time
v_node_space Contains a record of disk

capacity data retrieved or
calculated per disk, as well as
per node
Note: For a complete list of the available database views and

detailed information about each view, please refer to the Avamar
Reports Guide.
Accessing Database Views with PSQL
Data in PostgreSQL database on the Avamar server can be accessed using psql:
• Login to PostgreSQL as administrator

• To log in using psql, type psql -p 5555 mcdb
• Other useful commands include:
© Copyright
\d Displays all
tables and views
\d v_groups Shows columns

in tables
\o /tmp/sample_report_output Redirect output

to a file
Accessing Database Views with Microsoft Query
Click to enlarge
Microsoft Query can be used to access the administrator server database and
prepare reports with the information from database views.
Page
• Install and configure PostgreSQL

• Access Microsoft Query using Microsoft Excel345
345In Microsoft Excel, select Data > Get Data > From Other Sources > From
Microsoft Query, and select MCDatabase as the data source.
© Copyright
Course Summary
Course Summary
Course Summary
You have reached the end of the course.
Key points covered in this course:

• Avamar features, functions, and terminologies
• Scheduled and on-demand backups and restores
• Avamar Client Manager and Desktop/Laptop interfaces
• Avamar replication and cloud tier
• Avamar monitoring, management, replication, and maintenance activities
Page
Appendix
Avamar Web User Interface (AUI)
The Avamar Web User Interface is a web management application that is used to
administer an Avamar server. The AUI can monitor and configure the Avamar
servers, as well as perform all management activities.
Avamar Administrator
© Copyright 2020 Dell Inc. Page 385

Appendix
Avamar Administrator is a graphical management console software application that

is used to administer an Avamar system from a supported Windows or Linux client
computer. it is the primary user interface used to:
• Monitor and restore backups.

• Perform system maintenance activities.
• Configure backup policies.
• Manage clients and user accounts.
• Configure system settings.
Management Console Command Line Interface (MCCLI)
Management Console Command Line Interface (MCCLI) is a Java application that

provides command-line access to Avamar features and functions that are available
using the Avamar Administrator or the AUI.
Orchestra REST API
Page 386 © Copyright 2020 Dell Inc.

Appendix
The Orchestra REST API extends the native Avamar server REST API to facilitate
the management of multiple Avamar servers. Once you register an Avamar server
with Orchestra, the API provides a single point of interface for management
operations. Orchestra obtains, holds, and supplies the required authentication
tokens on your behalf.
avagent
avagent runs as a service on the client. It establishes and maintains
communication with MCS on the Avamar server. avagent listens for incoming
work orders from MCS on the Avamar server. In response to a work order, such as
a backup or a restore, avagent will spawn avtar. avagent listens on port 28002.
avtar
avtar is the primary process for backups and restores. avtar communicates with the
GSAN processes on the storage nodes. The two types of plug-ins are file system
and application plug-ins.
• File system plug-ins browse, backup, and restore files or directories on a

specific client file system, such as Windows or Linux.
• Application plug-ins support backups and restores of applications and
databases, including SQL Server, Exchange, Oracle, and SAP.
Note: For the updated list of Avamar supported client file systems,
operating systems, platforms, and applications, please refer to Dell
EMC Avamar Interoperability and Compatibility Matrix available on
the Dell EMC Online Support website.
The Backup Process

The following actions are performed for each file in the backup:
1. avtar stats the file and computes a hash of file attributes.

Appendix
2. avtar checks in the file cache to see if the file has been backed up before.
3. If there is no match, the file is divided into variable-sized data chunks, and each
chunk is compressed and hashed.
4. The hash cache is checked to determine if each data chunk has been stored
before.
5. If there is no match in the hash cache, avtar checks the Avamar data server
for the hash value.
6. If the hash does not exist on the Avamar server, the backup data, in the form of
the compressed data chunk, and the hash are sent to the Avamar server.
7. The client caches are updated with the applicable hashes.
Hashing Algorithm
Hashing is the process of creating a short fixed-length data string from a large
block of data.
• During hashing, data chunks obtained from compression are input to the SHA-1
hashing algorithm.
• The hash created from each data object is called an atomic hash.
− Atomic hashes are combined to create composites.

− Hashing is repeated until a single root hash for the backup is created.
Note: Hashing does not effect the original data chunk. The original
chunk remains intact. Though it is used in hashing, it is not converted
into a hash. After the hashing process, both the data chunk and the
hash exist.
Data Domain Cloud Storage

Data Domain cloud storage units must be pre-configured on Data Domain before
they can be configured for cloud tier in the AUI. The 'Data Domain Operating
System Administration Guide' provides further information.

Appendix
Avamar Database Clients - Configurations

The following activities take place when the Avamar client and the Avamar
database client are installed on the database server:
• During installation, the Avamar database clients add plug-ins to the database
server.
• During a backup, the database plug-ins communicate with the database API or
backup facility, and pass data to be backed up to avtar. avtar sends the data to
the Avamar server.
The following are true when the client is running on a separate host that has access
to data in the database:
• Backups can be sent as file system data using avtar.

• The CPU utilization of the database server is less as the backup processing is
offloaded to the host machine.
Avamar Database Agent on Database Server
Avamar Oracle
Agent
Oracle API
Oracle
Database
Server
Avamar
Server
Database

Appendix
Pros Cons
Unassisted, single-click backup and High CPU utilization on client

restore
No additional primary storage required Limited to supported databases
Avamar client only scans changed data346
'hot' Database Dump with Proxy

In this option, the database is dumped to a local disk cache. The cache is
accessible to a proxy machine in which the Avamar agent is installed.
346With Oracle RMAN incremental backups, Avamar client only scans changed
data. However, all incrementals need to be applied during restore process.

Appendix
Database Server Proxy
Oracle avtar
Database Database Avamar Server
Pros Cons
Fast restore347 Additional primary storage required
Modest CPU utilization on database Additional server required

server
Standard file system backup Two step restore process
Works with non-supported databases
347Backup copy is immediately available on local “disk cache” making restores

faster.

Appendix
Avamar client agent only scans changed

data
'hot' snapshot copy with Proxy

In this option, the Avamar agent is installed on a client machine with access to the
snapshot. The client backs up the snapshot. The client machine owns the backup.
Database Server Proxy
Oracle avtar
Primary
Database
Snapshot
Avamar Server

Appendix
Pros Cons
Faster restores348 Additional primary storage required to

store snapshot
Modest CPU utilization on database Additional server required

server
Standard file system backup
Works with non-supported databases
Single-step restore process
Backup Policy
The Backup Policy page enables you to create a backup policy to automate the
backup. The page also enables you to enforce consistent rules and system
behavior across a group of the user community. It is visible to the users who have
ADMIN, ADMIN_CANNOT_RETIRE, BACKUP_ONLY_USER, BACKUP_ADMIN,
REPL_USER privileges. The dataset, schedule, and retention policy comprise the
Backup Policy. The backup policy controls the backup behavior of all the members.
348Backup copy is immediately available on local “disk cache” making restores

faster.

Appendix
1 2 3
1: The + ADD option allows the user to add a backup policy to run a
backup/restore.
2: The EDIT option allows the user to edit the backup policy that is already created.
3: The MORE ACTIONS option allows you to enable a policy if the policy is
disabled before. Similarly, it also allows you to copy a policy.
4: The Policy details display shows details about dataset, schedule, and retention
settings for the selected policy.
5: Displays all the default policies and user-defined policies.
Advanced Policy
The Advanced Policy page allows you to manage all application-consistent SQL
virtual machine backups, including automatic MS-SQL application discovery,
automatic backup group management, and automatic MS-SQL plug in and client
installation and registration. This view is visible to the users who have ADMIN,
ADMIN_CANNOT_RETIRE, REPL_USER privileges.

Appendix
Replication Policy
The Replication Policy page helps the administrators to copy client backups from
the source Avamar system to an alternate destination that has an Avamar system
or an Avamar system integrated with Data Domain. Replicating backups to an
alternate destination protects against data loss if the source Avamar system fails. It
is visible to the users who have ADMIN and REPL_USER privileges.
1: The + ADD option allows you to create a replication policy to perform a

replication job which replicates the data from source location to a target system.
2: Displays all the replication policies.

Appendix
Cloud Tier Policy

The Cloud Tier Policy page helps the administrator to move Avamar backups from
Data Domain to the cloud and performs seamless recovery of these backups. It is
visible to the users who have ADMIN, ADMIN_CANNOT_RETIRE, and
REPL_USER privileges.
1: The + ADD option in the cloud tier policy pane helps you to create a policy to
perform a cloud tier operation.
Setting
The Setting page assists administrators with adding user accounts to the system,
and creating and managing schedules, datasets, retention policies, and rules. It is
visible to the users who have ADMIN, ADMIN_CANNOT_RETIRE, and
REPL_USER, privileges.

Appendix
1 2 3 4 5
1: Scheduled backups run automatically to ensure that backups occur on an

ongoing basis. You can schedule backups to run daily, weekly, or monthly. The
Policy wizard allows you to create a policy for a backup.
2: Backup retention policies enable you to specify how long to keep a backup in the
system. A retention policy is assigned to each backup when the backup occurs.
Here, you can specify a custom retention policy when you perform an on-demand
backup, or create a retention policy that is assigned automatically to a group of
clients during a scheduled backup.
3: The Avamar system includes a set of preconfigured datasets by default. Here,

you can use these datasets for scheduled backups of clients, or you can create a
custom dataset.
4: Here, you can create a rule, edit an existing rule, or delete a rule. Rules are used
by the Avamar Server for domain map and automatic backup policy assignment for
auto-discovered VMs.
5: Here, you can create a user account that defines an authentication system that
is used to grant users access to the Avamar server. A user account in Avamar can
administer a domain or client. It also defines the role for a user which controls the
operations that the user can perform.
6: The + ADD option allows you to add a schedule, dataset, retention, rule, and
user for a domain or client.

Appendix
Proxy Management
VMware VM image backups and restores require the deployment of proxy virtual
machines within the vCenter. Proxies run Avamar software inside a Linux virtual
machine, and are deployed using an appliance template (.ova) file. The Avamar
proxy that you deploy is used for backing up your virtual environment. At a time
eight VMs can be backed up. If you want to backup more than 8 VMs, then you
need to deploy additional Avamar proxies.
The Proxy Management page assists the administrators with deploying and
managing Avamar proxies. This is done by recommending the number of proxies
that should be deployed in each vCenter, and a recommended ESX host location
for each proxy. It is visible to the users who have ADMIN,
ADMIN_CANNOT_RETIRE, and REPL_USER privileges.
System
The System page assists the administrator with configuring vCenter-to-Avamar
authentication, registering the Avamar Plug-in for vSphere Web Client, and adding
a Data Domain system to Avamar. In Avamar 19.1 version, you can add or edit the
RSA Authentication Manager to enable two-factor authentication (2FA) on virtual
machines. This feature provides additional authentication when you perform a VM
restore to ensure security. The System pane is visible to the users who have
ADMIN, ADMIN_CANNOT_RETIRE, and REPL_USER privileges.

Appendix
For more details about the functionality of each tab, refer to Dell EMC Avamar
Administration Guide.
1 2 3 4 5 6 7
1: The VMware Plugin tab helps the vSphere users to initiate image backups and
restores of virtual machines in their environment.
2: The DD NFS Datastores tab lists the temporary NFS share for VMware instant
access on a configured Data Domain system.
3: The Data Domain tab allows you to add a Data Domain system and edit or
delete an existing system. Similarly, you can also specify a default DD destination
system in a replication environment with more than one destination DD system.
4: The Replication Destination tab allows you to add a replication destination which
is configured before running a replication job.
5: The Storage Mapping tab allows you to map a domain to a Data Domain system,
which is useful where there are multiple destination DD systems available. In such
situations, you can specify the specific system that receives the data that replicates
from the source Data Domain system.
6: The RSA Authentication Manager tab allows you to enable two-factor

authentication (2FA) on virtual machines, which is useful during VM restores.
7: The Server Management tab allows you to perform maintenance activities that
include checkpoints, garbage collection, reviewing the backup window.
8: Allows you to import the certificate file from your local system.

Appendix
Activity
The Activity page provides status and detailed information for backup and
replication jobs. It is visible to the users who have ADMIN,
ADMIN_CANNOT_RETIRE, BACKUP_ONLY_USER,
BACKUP_RESTORE_USER, BACKUP_ADMIN, BACKUP_RESTORE_ADMIN,
REPL_USER, RESTORE_ONLY_USER, RESTORE_ADMIN, and
ACTIVITY_OPERATOR privileges.
2 3
1: It displays all the activities that are in-progress, failed, and completed. The
activities include backup, restore, replication, cloud tier job etc.

Appendix
2: This option allows you to restart a backup that is complete/failed directly from the
Activity tab.
3: It displays the log information of a specific backup activity. This is useful for any
troubleshooting activities.
4: The Details option displays the complete information about the backup activity
that includes the domain, client, OS, policy, schedule time, retention, and so on.
Event
The Event page helps the administrator to monitor operational status and server
activity. Examples of Avamar events include client registration and activation,
successful and failed backups, and hard disk status. It is visible to the users who
have ADMIN, ADMIN_CANNOT_RETIRE, and REPL_USER privileges.
2 3
4 5
1: It displays the number of events giving warning message, error message, and
critical messages.
2: The FILTER option allows you to filter the events based on date, time, type, and
category.

Appendix
3: The option allows you to acknowledge those events which are not
acknowledged.
4: Here, you can see all the events that are critical, warning, and errors based on
the filter selected.
5: The Event data option gives an overview of the selected event.
Fitness Analyzer
The Fitness Analyzer page allows the administrator to view the server health and
functionality. This allows the administrator to troubleshoot issues, optimize system
performance, or plan future changes.
1: By default, the timeline contains one day of data. To view detailed information for
more than one day, select a different number of days from the Zoom option.
2: Each pane provides detailed information regarding the server health and
summaries.
3: The Overview pane provides a high-level overview about the system.

Appendix
Avamar - Server Capacity Information

The Avamar server capacity information tab displays the amount of available
storage and used storage for the Avamar server in Gigabytes (GB). Also,
information about the percentage of total capacity that is used is also displayed. If
the Avamar system configuration includes a Data Domain system, then the server
capacity calculations include metadata that is used for the Data Domain system as
well.
Data Domain - Server Capacity Information

All the configured Data Domain systems are listed in the Capacity | Overview
panel. This panel indicates the amount of available as well as used storage for the
Data Domain system in GB. Also, information about the percentage of total
capacity used is also displayed.

Appendix
Administrator
The users with the admin role can perform administrative tasks, backups, and
restores affecting their domain and any sub-domains within their domain. A root
level administrator has full control of the system.
Avamar introduces the concept of a domain administrator without privileges to retire

clients (ADMIN_CANNOT_RETIRE). This role applies to both AUI and Avamar
Administrator. This domain administrator has the same privileges as a root
administrator except that it cannot retire clients. This role is for domain level only
and not for root domain.
Operator
The users with operator role have access to the specific Avamar Administrator
features they are entitled to use based on their assigned role.
Following are the various operator roles available:

• Restore only Operator: Perform and monitor restores
• Backup Only Operator: Perform backups and monitor those activities
• Backup/Restore User: Initiate backups and restores, and monitor activities
• Replication User: Default replication user account on the Avamar server
• Activity Operator: Monitor backup and restore activities, and create reports
User
The users are not allowed to log in to Avamar Administrator.
Following are the various user roles available:

• Backup Only User: Initiate backups from the client using the avtar CLI
command
• Restore Only User: Initiate restores directly from the client
• Backup/Restore User: Initiate backups and restores from the client

Appendix
Policy-based Replication in AUI

Policy-based replication provides greater control of the replication process.
With policy-based replication, you can create replication groups in the AUI that
define the following replication settings:
• Replication group members, either domains or clients
• Priority order for replication tasks
• Backups to replicate, based on the retention setting or the backup date
• Maximum number of backups to replicate for each client
• Destination system for the replicas (replication to another Avamar system,
Cloud Tier, or Data
Domain system)
• Replication schedule
• Retention of replicas

Appendix
Additionally, you can use the AUI to view and manage replicated backups349.
Command Line Replication in CLI

Perform on-demand replication from the command line by logging in to the utility
node and using the avrepl command line interface (CLI). Command-line
replication provides greater control of the replication process.
The following replication settings are defined by the avrepl command:
• Domains or clients to replicate

• Backups to replicate based on plug-in, retention setting, and backup date
• Maximum number of backups to replicate for each client
• Destination system for the replicas
• Retention of replicas
Administrator server (MCS)

Administrative processes include Java-based mcserver processes and
PostgreSQL. The following commands are used to check whether the MCS
processes are running:
349 Change the expiration date
Change the retention type
Remove a replicated backup
Restore from a replicated backup

Appendix
• ps -efm | grep -c java

• ps -efm | grep -c post
Other Administrative Processes

Other administrative processes include Tomcat web service, BIND name
resolution, mail transport processes, maintenance cron jobs, and Avamar external
authentication service, also called the login manager. The administrator can check
for cron jobs by typing: ps -elf | grep _cron
Client Logs - Location

Depending on the platform, client logs are located in the following directories:
• Windows
Workorder: %SystemDrive%\Program Files\avs\var\clientlogs\
Agent: %SystemDrive%\Program Files\avs\var\
Console: %APPDATA%\Avamar\
• Linux and Mac
Workorder: /usr/local/avamar/clientlogs
Agent: /var/avamar/
Console On Linux: $HOME/
Console on Mac: On Mac:$HOME/.avamardata/
Avtar logs are labeled: <backup_label>-<plugin>.log. Listed below are the formats
of a few of the logs:
• Scheduled backups:
− <Schedule name>-<Group name>-<Unix time in msec>
• Ad-hoc group or client backups using a defined group policy:
− <Group name>-<Unix time in msec>
• Ad-hoc backups that are performed through Backup and Restore:
− MOD-<Unix time in msec>

Appendix
− MOD stands for Management On Demand

• Ad-hoc backups performed through the Avamar Backup Now client interface on
Windows clients
− COD-<Unix time in msec>
− COD stands for Client On Demand.
• Command-line executions of avtar: avtar.log or specify a log file name with --
logfile
Resolve Exceptions
Do not ignore exceptions and failures, since it may lead to missing files or data.
Check for the following exceptions.
• Completed with Exceptions: The message indicates that the backup is complete
with files missing.
• Timed Out - End: The status requires special attention. This indicates a large
amount of activity without any backup data being restored.
• Dropped Session: The status indicates that the activity was forcefully canceled.
The two possible causes are:
− Client reboot
− More than an hour of communication outage
• Completed: The status indicates that backup was completed as per defined
policies. However, make sure the policies are defined correctly.
Performing a Rollback
To rollback to a specific checkpoint:
• Load the admin ssh keys

• run dpnctl stop
To start the rollback, run: rollback.dpn --cptag=cp.datetime >& filename, where
• Run: rollback.dpn --cptag=cp.datetime >& filename

Appendix
− cp.datetime name of a checkpoint

− filename: user-defined file to hold the rollback log information
Forced Rollbacks
If a data server (gsan) did not shut down correctly, dpnctl prompts for a rollback
upon restart. A rollback can also be forced using the --force_rollback option
in dpnctl start.
• Always, rollback to a validated checkpoint

• To obtain a list of current checkpoints, run cplist

Appendix
Exceptions
The following exceptions need to be considered.
• In a multinode Avamar server, if nodes have been added since a checkpoint,

remove the IP address of those nodes from the probe.xml file.
• If there has been a change in the password, it has to be updated in the
/usr/local/avamar/etc/usersettings.cfg file of the checkpoint to be restored.
Fitness Analyzer Reports

Fitness Analyzer reporting addresses multiple areas that include:
• Maintenance and backup window optimization

• Capacity utilization
• Replication performance
• Job completion times
• Proxy utilization
• Policy and client organization
• Troubleshooting system health and configuration issues
Fitness Analyzer also works with existing Management Console Server (MCS)
reporting functions to provide old reports that were available through Avamar
Administrator.
Legend
Legends, situated below the timeline, identify each data series and the type of
activity. Legends interpret graphical, color-coded data in the timeline.

Appendix
Legend Description
BkpWaiting The number of backups that are currently waiting to

start
BkpRunning The number of active backups
ReplSrcWaiting The number of replication jobs that are waiting to be

started
ReplSrcRunning The number of active replication jobs
ReplDstWaiting The number of replication jobs, from other servers to

this one, that are waiting to be started
ReplDstRunning The number of active replication jobs, from other

servers to this one

Appendix
Scale
By default, the timeline contains one day of data. A Scale placed below the timeline
enables the administrator to view data for other time periods of time.
The Zoom control above the timeline can be used to view information from different
set of dates. The Overview pane displays a maximum of one week of data.
Bytes View
The Bytes view toggle button, at the top-right corner of the timeline, changes the
display units for the horizontal axis to Giga Bytes, so that the timeline represents
the amount of raw data that is transferred to the Avamar server. This view
distinguishes the relative impact of each group on the server.
Generating Reports
Use the following procedure to generate a report:
1. Select a type of report from the table on the Reports pane.

Appendix
2. If the report requires start and end dates to be generated, select appropriate
values from the 'From Date' and 'To Date' fields.
3. Click on the Generate button
4. Select a report format from the drop-down
Accessing Reports
After the report is generated, the finished report becomes available in the
Completed Reports panel.
• To retrieve a completed report:

1. Select the report from the list in the Completed Reports panel.
2. Click the Download button.
• To remove unneeded reports:
1. Select the report from the list in the Completed Reports panel.
2. Click the Delete button.
• To view reports of a specific type, select the required type from the list in the
reports pane. Similar reports appear in the Completed Reports panel.
Configuring Custom Profiles

The following procedure can be used to enable email notifications in a custom
profile:
1. In Avamar Administrator, select Tools > Manage Profiles. The Manage All
Profiles window is displayed.
2. In the left pane, select the domain for the custom event profile, and click New.
The New Profile wizard appears.

Appendix
3. In the Profile Name box, type a name for the event profile.
4. For Profile Type, keep the default setting of Email, Syslog, and SNMP Trap
Notification.
5. Enable the profile by checking the Profile Enabled checkbox.
6. Enable email notifications by checking the Email Enabled checkbox.
7. Select either 'Send data as events occur' or 'Send data on a schedule', as per
requirement.
8. In the Email Notification tab, add the recipient email list, and finally click OK to
confirm the settings.
Install and Configure PostgreSQL

PostgreSQL must be installed on a Windows machine with network access. The
parameters for PostgreSQL are:
• Data Source: MCDatabase

• Database: mcdb
• Server: <avamar server name>, where <avamar server name> is the hostname
of the Avamar server
• Port: 5555
• User Name: viewuser
• Password: Configured during Avamar installation

Glossary
Avamar Client
An Avamar client is a device from which files can be backed up or a device to
which files can be restored. Typically this is a laptop, desktop, server, or a virtual
machine.
nodenumbers
Used to display the logical node number, physical node number, IP address, and
MAC address of the storage nodes in the Avamar server.
Plug-in
A plug-in is a software component that adds a specific feature to an existing client.
When a client supports plug-ins, it enables customization for the customer.
The plug-in type indicates the top 10 most frequently used plug-ins by the clients.
The total client count indicates the number of clients that use a specific plug-in.
Similarly, the total protected GB indicates the total amount of data in GB that the
system protects for each plug-in type.
probe.xml
The probe.xml file supports both Network Address Translation (NAT) and multiple
network interfaces. Node types can be specified in probe.xml include utility,
storage, access, accelerator, spare, single-node server, and unclassified.


Avamar Admin 19.2 Participant Guide

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Avamar Admin 19.2 Participant Guide

Uploaded by

Copyright:

Available Formats

AVAMAR

Avamar Overview ....................................................................................................... 8

Avamar Administration-Participant Guide

Internal Use - Confidential

Installing Avamar Backup Client Software ............................................................ 60

Account Management .............................................................................................. 73

Avamar Administration-Participant Guide

Using Client Manager ............................................................................................ 113

Avamar Backups .................................................................................................... 133

Performing Restores.............................................................................................. 196

Avamar Replication................................................................................................ 220

Avamar Administration-Participant Guide

Internal Use - Confidential

Cloud Tier ............................................................................................................... 239

System Monitoring and Maintenance ................................................................... 260

Avamar Administration-Participant Guide

Logs, Troubleshooting, and Reporting ................................................................ 342

Avamar Administration-Participant Guide

Internal Use - Confidential

Appendix ............................................................................................... 385

Glossary ................................................................................................ 415

Avamar Administration-Participant Guide

Avamar Administration Tools

Avamar Web User Interface (AUI) Avamar Administrator

Management Console Command Line Orchestra REST API

Avamar Administration-Participant Guide

Click to enlarge image.

• Provides a secure Avamar interface for end-users

1Avamar Desktop/Laptop is a version of the Avamar client software for Windows

Avamar Administration-Participant Guide

Avamar server supports 72 connections. Avamar integrated with Data Domain

The Avamar Administrator server allows a maximum of 72 concurrent backup

Avamar Administration-Participant Guide

Avamar Server Process – Notification and Reporting

Several processes run on Avamar server nodes. Key processes include:

• Avamar Administrator Server2

Administrator server is responsible for two important functions:

2System activities and operational status are reported as events to the

Avamar Administration-Participant Guide

Avamar Client Processes

7 avscc process is used to access the Avamar client GUI.

Avamar Administration-Participant Guide

Backup metadata and log files

OS level backup and metadata

Work order OS level backup

Avamar Administration-Participant Guide

Avamar Backup Process Flow

During a scheduled backup:

Utility Node Webserver

Click to enlarge image

1. The administrator server (MCS) generates

2. MCS pages the client avagent. avagent

3. On the client, avagent starts avtar to

4. avtar communicates to a GSAN process

5. GSAN distributes the data across the

Avamar Administration-Participant Guide

Client-Server Data Port Usage and Firewall Requirements

Port/Protocol Purpose Source Destination Remarks

30001/TCP MCS using Utility node Storage • Required port

30001/TCP MCS using Storage Utility node • Required port

30002/TCP Avamar client Avamar Avamar

30002/TCP Avamar client Avamar Avamar • Required port

443/TCP HTTPS for User-defined Utility node • Required port

Avamar Administration-Participant Guide