Avamar Data Store Gen4T

Comprehensive Reference Guide

302-002-893
REV 03
Copyright 2016 Dell Inc. or its subsidiaries All rights reserved.

Published December 2016

Dell believes the information in this publication is accurate as of its publication date. The information is subject to change
without notice.

THE INFORMATION IN THIS PUBLICATION IS PROVIDED AS-IS. DELL MAKES NO REPRESENTATIONS OR

WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. USE,
COPYING, AND DISTRIBUTION OF ANY DELL SOFTWARE DESCRIBED IN THIS PUBLICATION REQUIRES AN
APPLICABLE SOFTWARE LICENSE.

Dell, EMC, and other trademarks are trademarks of Dell Inc. or its subsidiaries. Other trademarks may be the property of
their respective owners. Published in the USA.

EMC Corporation
Hopkinton, Massachusetts 01748-9103
1-508-435-1000 In North America 1-866-464-7381
www.EMC.com

2 Avamar Data Store Gen4T Comprehensive Reference Guide

CONTENTS

Chapter 1 Introduction 5
Important Avamar terms and concepts.........................................................6
Nodes.............................................................................................. 6
Utility node...................................................................................... 7
Storage nodes................................................................................. 7
Single-node servers......................................................................... 7
NDMP accelerator node.................................................................. 7
Node resource database (probe.xml)...............................................7
Avamar Downloader Service............................................................ 7
Local downloader service.................................................................7
Avamar FTP site.............................................................................. 8
Avamar Installation Manager........................................................... 8
Avamar login manager..................................................................... 8
Packages......................................................................................... 8
EMC repository............................................................................... 8
Local repository............................................................................... 8
Manifest file.................................................................................... 9
Segregated networks...................................................................... 9
Bonded network interfaces..............................................................9
High-availability network................................................................. 9
ConnectEMC................................................................................... 9
Email home.....................................................................................10
Data deduplication......................................................................... 10
Replication...................................................................................... 11
Avamar clients................................................................................ 11
Encryption......................................................................................12
Information for customers...........................................................................12
Fundamental Avamar principles...................................................... 13
Avamar 7.x installation features overview................................................... 13
How long will the Avamar software installation take?.....................13
Avamar Installation Manager.......................................................... 13
Process flow.................................................................................. 14
Log files......................................................................................... 15
In-flight encryption........................................................................ 15
Avamar Downloader Service...........................................................15

Chapter 2 Hardware Specifications 17

Multi-node server component locations...................................................... 18
Hardware specifications..............................................................................19
Utility node.....................................................................................19
M600 (2.0 TB licensed capacity)................................................... 19
M1200 (3.9 TB licensed capacity).................................................. 19
M2400 (7.8 TB licensed capacity)..................................................19
Avamar Business Edition/S2400 node (7.8 TB licensed capacity)....
20
NDMP accelerator node................................................................ 20
Service port connectivity........................................................................... 20
Node components....................................................................................... 21

Avamar Data Store Gen4T Comprehensive Reference Guide 3

CONTENTS

Chapter 3 Networking 25
Overview.................................................................................................... 26
Default port configuration.......................................................................... 26
Multi-node servers........................................................................ 26
Single-node servers....................................................................... 27
Basic networking configuration.................................................................. 28
Multi-node servers.........................................................................28
Supported network configurations............................................................. 29
Multi-node servers........................................................................ 29
Single-node servers....................................................................... 32
Advanced network configuration dpnnetutil utility.............................34
Features provided by dpnnetutil...............................................35
Replication................................................................................................. 36
Single-node servers....................................................................... 36
Multi-node servers.........................................................................38

Chapter 4 Installation and Beyond 41

Avamar "installation" process..................................................................... 42
Siting............................................................................................. 42
Installation..................................................................................... 42
Implementation.............................................................................. 42
Everyday use of Avamar servers.................................................................42
Maintenance of the server..........................................................................43

4 Avamar Data Store Gen4T Comprehensive Reference Guide

CHAPTER 1
Introduction

The following topics introduce Avamar and the Avamar Data Store (ADS) Gen4T
family of hardware components:

l Important Avamar terms and concepts................................................................ 6

l Information for customers.................................................................................. 12
l Avamar 7.x installation features overview........................................................... 13

Introduction 5
Introduction

Important Avamar terms and concepts

Avamar solves the challenges associated with traditional backup, enabling fast, reliable
backup and recovery for remote offices, data center LANs, and VMware
environments.
Avamar is backup and recovery software that uses patented global data deduplication
technology to identify redundant sub-file data segments at the source, reducing daily
backup data by up to 500x - before it is transferred across the network and stored to
disk. This enables companies to perform daily full backups even across congested
networks and limited WAN links.
Key Avamar differentiators are:
l Deduplication of backup data at the source - before transfer across the network
l Enabling of fast, daily full backups across existing networks and infrastructure
l Reduction of required daily network bandwidth by up to 500x
l Up to 10x faster backups
l Encryption of data in flight and at rest
l Patented RAIN technology that provides fault tolerance across nodes and
eliminates single points of failure
l Scalable grid architecture
l Reduction of total backup storage by up to 50x due to global data deduplication
l Daily verification of recoverability - no surprises
l Centralized web-based management
l Simple one-step recovery
l Flexible deployment options, including the Avamar Data Store package
The remainder of this section provides descriptions of key terms used in this guide and
other Avamar core software guides.

Nodes
The primary building block in any Avamar system is a node. Each node is a self-
contained, rack-mountable, network-addressable server that runs Avamar software on
the Linux operating system. All Avamar nodes are Domain Name System (DNS)
clients.

Note

The term "server" in the previous definition is used in the typical industry context
(that is, a computer that provides services to other computers or devices). However,
for the remainder of this guide, unless otherwise specified, the term "server" is used
to refer to a single node or multi-node Avamar system. The term "node" is used to
refer to the individual computer/storage platforms that make up an Avamar server.

All nodes run the Linux operating system and use RAID data protection. Nodes have 2,
4, 6, 8, or 12 hard drives, depending on node type and storage capacity. The primary
differences between node types are:
l The amount of internal data storage (if any)
l How internal data storage is configured and allocated (that is, RAID level, number
of logical units [LUNs] and so forth)

6 Avamar Data Store Gen4T Comprehensive Reference Guide

 Introduction

l The Avamar application software that is installed on each node type

Hardware Specifications on page 17 provides additional information.

Utility node
In scalable multi-node Avamar servers, a single utility node provides essential internal
services for the server (for example, administrator server, replication, external
authentication, network time protocol [NTP], and Web access). Because utility nodes
are dedicated to running these essential services, they cannot be used to store
backups.

Storage nodes
The remaining nodes in scalable multi-node Avamar servers are storage nodes, which
store the actual backups. There are three storage node models, the primary difference
being the amount of usable storage available: the M600, M1200, and M2400. They are
also offered as single node Avamar servers.

Single-node servers
Single node Avamar servers combine all the features and functions of utility and
storage nodes on a single node. There are four single-node server models: the M600,
M1200, M2400, and S2400. The S2400 (the Avamar Business Edition) is offered only
as a single-node server and features no requirement for replication.

NDMP accelerator node

An Avamar NDMP accelerator (accelerator node) is a dedicated single-node Avamar
client that, when used as part of an Avamar system, provides a complete backup and
recovery solution for supported EMC Isilon, Unity, VNX, VNXe, and Celerra systems,
Oracle NAS systems, and NetApp filers by using Network Data Management Protocol
(NDMP) to communicate with these storage devices. It is not part of the ADS server.
For installation instructions, refer to the EMC Avamar NDMP Accelerator User Guide.

Node resource database (probe.xml)

An XML file that stores the types and IP addresses of Avamar server nodes. In
addition, probe.xml stores the types and IP addresses of optional nodes, and
supports both Network Address Translation (NAT) and multiple network interfaces.

Avamar Downloader Service

A Windows-based file distribution system that delivers software installation packages
to target Avamar systems. Avamar Downloader Service on page 15 provides more
information.

Local downloader service

A component integrated into the Avamar Installation Manager. The local downloader
service (LDLS) allows administrators to check the EMC repository for updated
software packages by using the Avamar Installation Manager web interface. The LDLS
supports environments where local Windows hosts are unavailable, removing the
requirement to copy files directly to the local repository.

Utility node 7
Introduction

Avamar FTP site

An EMC FTP site that provides anonymous access to Avamar hotfixes and operating
system (OS) patches. The FTP site is ftp://ftp.avamar.com. Typically, access to this
site is for EMC personnel (there may be exceptions). The contents of the FTP site are
not browsable.

Avamar Installation Manager

A web interface that manages installation, upgrade, and maintenance packages.
Avamar Installation Manager on page 13 provides more information.

Avamar login manager

A process that provides access to an external authentication database, which enables
the Avamar system to use existing username and password information for Avamar
authentication. Without the login manager, Avamar can only use its internal
authentication mechanism. An Avamar server installation or upgrade installs the login
manager, and then starts it. The login manager uses the domains configuration file to
identify the supported domains.

Packages
Avamar software installation files, hotfix patches, and operating system (OS) patches
available from the EMC repository. Packages comprise three types:
l Client - A release of Avamar file system or application backup software.
l Server - A new release of Avamar server software, a service pack, or a patch for
the operating system, management console, or Avamar software.
l Workflow - A package that runs operations such as replacing a node or changing
the session security configuration.
Package files use the extension .avp.

EMC repository
A repository that contains server installation packages, client installation packages,
and manifest files. The EMC repository currently spans two locations: ftp://
ftp.avamar.com and EMC Subscribenet:
l High urgency packages such as hot fixes and OS patches are available from ftp://
ftp.avamar.com.
l Low urgency packages that have security and entitlement considerations are
available from EMC Subscribenet.
The actual source location of a package is transparent to the user.
The repository is located on the EMC network. Each EMC customer has its own
download center that contains files available to it. These files are maintained by the
EMC Subscribenet team. Outgoing communication from the Avamar Downloader
Service and LDLS to the EMC repository is encrypted with SSL over an HTTP
connection.

Local repository
The /data01/avamar/repo/packages directory on the utility node or single-node
server. The directory contains the most current manifest file from the EMC

8 Avamar Data Store Gen4T Comprehensive Reference Guide

 Introduction

repository, installation packages, and workflow packages. The Avamar Downloader

Service and LDLS push packages from the EMC repository to the local repository. If a
customer site does not allow Internet access, you can manually copy packages into
the local repository.

Manifest file
An XML file listing all packages currently available for download from the EMC
repository. When the EMC Subscribenet team adds a package to the EMC repository,
it then adds an entry to the manifest file that describes the package. When the EMC
Subscribenet team removes the package from the repository, it then removes the
entry for the package from the manifest file.
The Avamar Downloader Service automatically downloads the manifest file from the
EMC repository once a day and determines if new download packages are available.
The Avamar Downloader Service sends the new manifest file to the local repository for
each Avamar system.
The LDLS manages changes to the manifest file in a similar way to the Avamar
Downloader Service. However, the LDLS downloads the manifest file directly to each
Avamar system without the requirement for an intermediate host.

Segregated networks
In multi-node ADS servers, inter-node traffic is carried over an internal network that
includes dual dedicated switches with specific utility node and storage node ports. All
other data traffic is carried directly to external customer switches for access to
backup, replication, and management sources or targets. Both internal and external
networks provide protection against single points of failure.
Bonded network interfaces on page 9 and Networking on page 25 provide more
information.

Bonded network interfaces

Bonded network interfaces are used in high-availability (HA) configurations that try to
eliminate node ports and switches as single points of failure. Two separate customer
network switches are required, one connected to each of two physical interfaces of an
ADS node. Outgoing replication and management networks can be configured for
bonding through the additional ports on the utility node or single-node server.
Networking on page 25 provides more information.

High-availability network
HA configuration provides for continued operation in the event of a single point of
failure between network components. The primary objective is to provide multiple
paths to the internal ADS network and the external customer network so that the
system can recover from an individual device or link failure. To do this, HA
configuration employs bonded network interfaces and dual dedicated ADS switches.
Each switch is connected to one of two physical interfaces of an ADS node.
Networking on page 25 provides more information.

ConnectEMC
A Linux-based program that transfers event data from an Avamar server to EMC
Technical Support. Installation of the Avamar software automatically initializes

Manifest file 9
Introduction

ConnectEMC by passing values from the workflow to the ConnectEMC configuration

files.
The server software installation requires you to set the ConnectEMC attributes listed
in the following table:

Table 1 ConnectEMC attributes

Attribute Example setting

Site name ABC Company, Site ID: 123456

Address: 123 Main Street, Anytown, CA 92618 US

Email server mail.example.com

Email sender address [email protected]

You can set other ConnectEMC attributes after the installation by using Avamar
Administrator. Additional information about ConnectEMC is available from the
following resources:
l EMC Avamar Administration Guide
l ConnectEMC for Linux 3.0 Reference Guide

Email home
An Avamar feature that automatically emails configuration, capacity, and general
system information to EMC Technical Support once daily, and critical alerts in near-
real time on an as-needed basis. Email home uses the same email server that you
configure for ConnectEMC.

Data deduplication
Data deduplication is a key feature of the Avamar system. Data deduplication ensures
that each unique sub-file object is stored only once across sites and servers.
During backups, Avamar client software examines the client file system, applies a data
deduplication algorithm that identifies redundant data sequences and breaks the client
file system into sub-file data segments. Each data segment is assigned a unique ID.
The client software then determines whether this unique ID has already been stored
on the Avamar server.
If this object resides on the Avamar server, a link to the stored object is referenced in
the backup. Once an object has been stored on the server, it never has to be re-sent
over the network, no matter how many times it is encountered on any number of
clients. This feature significantly reduces network traffic and provides for greatly
enhanced storage efficiency on the server.

10 Avamar Data Store Gen4T Comprehensive Reference Guide

 Introduction

Figure 1 Avamar Global Data Deduplication

Replication
A feature that enables efficient, encrypted, and asynchronous exchange of data that is
stored in an Avamar server to another Avamar server deployed in a remote location,
without the requirement to ship tapes. Replication is a scheduled process between
two independent Avamar servers that provides a higher level of reliability for stored
backups. Replication can be scheduled to run at off-peak hours to minimize bandwidth
impact.

Avamar clients
Avamar provides client software for various computing platforms. Each client
comprises a client agent and one or more plug-ins.
Figure 2 Avamar Client Operation

Agents
Avamar agents are platform-specific software processes that run on the client and
communicate with the Management Console Server (MCS) and any plug-ins installed
on that client.

Plug-ins
Avamar provides two types of plug-ins:
l File system used to browse, back up, and restore files or directories on a specific
client file system (such as Linux, Mac OS, Microsoft Windows, and Sun Solaris).

Replication 11
Introduction

l Application support backup and restore of databases or other special

applications (such as Microsoft Exchange or SQL Server, Oracle, and NDMP for
NAS devices).

Encryption
Avamar can encrypt all data sent between clients and the server in flight. To provide
enhanced security during client/server data transfers, Avamar supports two levels of
in-flight encryption: medium and high. You can set the encryption level on a client-
by-client basis in client properties, or for an entire group of clients in group properties.
You also can disable in-flight encryption entirely.
Each Avamar server can also be configured to encrypt data that is stored on the
server (at rest). The decision to encrypt all data that is stored in an Avamar server is
typically a one-time decision that is made when the server is initially deployed at a
customer site.
Starting in Avamar 7.3.x, additional security features use encryption during
authentication of both the server and client. The EMC Avamar Product Security Guide
provides more information.

Information for customers

The following is a collection of information about Avamar and the ADS that can guide
you when installing and using this product.
The EMC Online Support site is a great resource for information and links: https://
support.emc.com/products/
Avamar software downloads are located on the Avamar FTP site: ftp://
ftp.avamar.com
Obtaining an Avamar license key file requires an account for the EMC Software
Licensing Central (SLC) on the EMC Online Support site. EMC Technical Support is
responsible for obtaining a license key file for your system.
For information about cross-version and cross-equipment compatibility, refer to the
EMC Avamar Compatibility and Interoperability Matrix on the EMC Online Support site.
For numerous best-practice tips about installing, configuring, upgrading, and using
Avamar, refer to the EMC Avamar Operational Best Practices Guide on the EMC Online
Support site.
Numerous technical notes provide supplemental information about rare, unique, or
version-specific installation, implementation, and configuration scenarios. Find
technical notes by title on the EMC Online Support site.
For instance, one technical note, Avamar Client Downloads and Client Manager Installer
Upgrades Technical Note, describes how to upgrade client downloads and Avamar
Client Manager client installers.

Note

Starting in Avamar 7.2.x, Avamar Enterprise Manager is no longer available. The

technical note Avamar Enterprise Manager Transition to Backup and Recovery Manager
provides more information.

12 Avamar Data Store Gen4T Comprehensive Reference Guide

 Introduction

Fundamental Avamar principles

When working with Avamar, always consider the following:
l All nodes in an Avamar server must run the same version of the Avamar software.
l All storage nodes in a multi-node Avamar server must be the same size (capacity).
l The best practice for replication is to move data from an older generation Avamar
server to a newer one and not the reverse. This scenario is typically used to
replicate data from the old server as a first step before upgrading it to the latest
version of Avamar software, after which the data can be replicated back.
l All non-RAIN systems must be replicated, except the S2400 (Avamar Business
Edition, see Hardware Specifications on page 17).

Avamar 7.x installation features overview

Avamar uses the Avamar Installation Manager user interface to automate the software
installation process on servers. The Avamar Installation Manager runs on single-node
servers and on the utility node of multi-node systems. EMC Technical Support uses
this utility during implementation.
Avamar 7.x also includes the Avamar Downloader Service, a Microsoft Windows-based
application that automates the installation of future patches and other packages to
your Avamar system. Starting in Avamar 7.3, the LDLS is also available for direct
download of packages.

How long will the Avamar software installation take?

Completing the Avamar server software installation takes about two hours, plus the
amount of time it takes to upload the Avamar software installation packages to the
server.

Note

Uploading the installation package can take a significant amount of time, depending on
the method used. Installing and configuring the Avamar Downloader Service and LDLS
are considered post-installation tasks because they are not required to perform
Avamar software installation.

Avamar Installation Manager

During installation, the Avamar Installation Manager user interface is installed on the
utility node or single-node server. The Avamar Installation Manager user interface
enables EMC personnel to:
l Install or upgrade the Avamar software
l Install OS, Avamar software, or other hotfix patches after initial Avamar software
installation
Avamar Installation Manager controls the following:
l The EMC repository manifest file
l Downloading of packages from the Avamar Downloader Service and LDLS

Fundamental Avamar principles 13

Introduction

l Monitoring the local repository for any software packages manually added to the
server
l Dependency and version checks of the downloaded packages
l Management of the temporary directory that is used to extract the packages
l Deletion of software packages after a successful installation or upgrade

Process flow
The following diagram shows how the Avamar Downloader Service, LDLS, and Avamar
Installation Manager work together with other components to automatically provide
installation, upgrade, and hot fix packages.
Figure 3 Process Flow for Packages

Process flow tasks:

1. The Avamar Downloader Service or LDLS checks with the EMC repository for new
manifest files. This check is done automatically every 24 hours.
l The Avamar Downloader Service downloads the manifest from the EMC
repository and pushes it to the Avamar Installation Manager, or
l The LDLS downloads the manifest from the EMC repository directly to the
Avamar Installation Manager.

Note

During the first communication handshake between the Avamar Downloader

Service and Avamar Installation Manager, the Avamar Downloader Service passes
information such as its version, its host and IP address, and so forth, to the
Avamar Installation Manager.
2. The Avamar Installation Manager processes the manifest file and notifies the user
of new packages.
3. The user requests the package by clicking the Download button in the Avamar
Installation Manager.

14 Avamar Data Store Gen4T Comprehensive Reference Guide

 Introduction

l The Avamar Downloader Service then downloads the package and pushes it to
the Avamar Installation Manager, or
l The Avamar Installation Manager downloads the package directly using the
LDLS.
4. The user installs the package by clicking the Install button in the Avamar
Installation Manager.

Log files
The Avamar Installation Manager provides log file information through the web
interface. The log information can be exported to a file (.xls or .pdf).
The Avamar Installation Manager also provides the Download all system logs icon
, which enables you to download all system log files for troubleshooting issues, for
example.
You must log in to the EMC Customer Support account to use the Download all
system logs icon.

In-flight encryption
A new installation of Avamar sets in-flight encryption to High as the default setting.
An upgrade does not change the current in-flight encryption setting. The EMC Avamar
Administration Guide provides more information about in-flight encryption.

Avamar Downloader Service

The Avamar Downloader Service is a file distribution system that delivers software
installation packages to target Avamar systems. The distribution process uses minimal
bandwidth by downloading only files that you request through the Avamar Installation
Manager.
The Avamar Downloader Service uses a local file cache to ensure that a file is fetched
only once from the EMC repository, no matter how many times an Avamar system
requests the file. You can remove old files from the local repository to free disk space.
The Avamar Downloader Service software runs on a stand-alone Microsoft Windows
server. The Windows server must have network access to the EMC repository and the
Avamar server.
The Avamar Downloader Service is installed as an automatic-startup service. You can
view the Avamar Downloader Service from the Microsoft Management Console. After
you install the Avamar Downloader Service, use the Avamar Downloader Service
application to configure it.
The installation of the Avamar Downloader Service installs these components:

Table 2 Avamar Downloader Service components

Component Description

Avamar Downloader Monitors the EMC repository. When a package is available for the
Service Windows Avamar system, the Avamar Downloader Service service
service automatically downloads the package and pushes it to the local
repository on the Avamar utility node or single-node server.

Avamar Downloader A process that provides status message about the Avamar
Service monitor Downloader Service.

Log files 15
Introduction

Table 2 Avamar Downloader Service components (continued)

Component Description

Moving the mouse over the tray icon displays status messages
from the Avamar Downloader Service monitor.

Right-clicking the icon displays these options:

Configure Service Opens the Avamar Downloader Service

configuration application.

Open Repository Opens the local file cache directory on

the Windows server (C:\Program
Files\EMC\Avamar Downloader
Service\repository).

Run Diagnosis Runs a test of packages in the local

manifest file and for network
connectivity to the EMC repository.

Check for New Packages Queries the EMC repository for a new
manifest file.

Show Advanced Settings Allows the input of new EMC

repository credentials or the
restoration of Avamar Downloader
Service to default settings.

Check for Updates Checks for an updated version of the

Avamar Downloader Service software.

About Shows the version of the Avamar

Downloader Service.

Exit Closes the Avamar Downloader

Service.

The Avamar Downloader Service installation also creates:

l A local repository in the installation directory.
This directory is where the Avamar Downloader Service puts packages it fetches
from the EMC repository.
l A Start menu program group: EMC Avamar Downloader Service <version>,
where <version> is the version of the Avamar system software that is installed on
the server. The program group contains:
n Avamar Downloader Service Configuration
n Avamar Downloader Service Monitor
l A desktop shortcut to the Avamar Downloader Service configuration application.

16 Avamar Data Store Gen4T Comprehensive Reference Guide

CHAPTER 2
Hardware Specifications

The following topics describe the set of ADS Gen4T hardware:

l Multi-node server component locations..............................................................18

l Hardware specifications..................................................................................... 19
l Service port connectivity................................................................................... 20
l Node components...............................................................................................21

Hardware Specifications 17
Hardware Specifications

Multi-node server component locations

A 14-node example (1 utility node and 13 active storage nodes) of the initial
configuration of a standard ADS multi-node server is shown here. Initial configurations
range from 4 to 18 nodes (one utility node plus a maximum of 16 active storage nodes
and one optional spare storage node).
Figure 4 Multi-Node Layout

Previous component replacement might have changed the arrangement of nodes in

your rack. Since a spare can replace any defective storage node, and because a
replacement node can become the new spare, the location of any specific storage
node can vary over time.
Each rack configuration has 40U capacity. For Gen4T, the utility node takes up a 2U
increment. All storage nodes take up 2U increments. The utility node is at the bottom
of a multi-node configuration, with active storage nodes and an optional spare storage
node stacked above it. Additional nodes can be added in expansion slots starting with
the lowest available slot.
Switches A and B at the top are ADS internal network switches. Switch A is the
bottom one.

18 Avamar Data Store Gen4T Comprehensive Reference Guide

 Hardware Specifications

The minimum ADS multi-node configuration is one utility node and three storage
nodes. The maximum is 1 utility node, 16 active storage nodes, and an optional spare
storage node.

Hardware specifications
Each node runs the SuSE Linux Enterprise Server v11 SP3 operating system and
features a service port. See Service port connectivity on page 20 for more
information.
The M600, M1200, and M2400 can be used as single-node servers or as storage
nodes within a multi-node server.
The S2400 (Avamar Business Edition) is available only as a single-node server and
does not require replication.
The NDMP Accelerator node is an optional node associated with, but not part of, the
Avamar server.

Utility node
l Two 3.5" hard drives
l Dual 1100W power supplies
l Two SLICs, each containing four 10GbE network ports:
n Bay 0: 10GBase-T or 10GbE Twinax/Optical
n Bay 1: 10GBase-T
l RMC shared and dedicated management ports

M600 (2.0 TB licensed capacity)

l Four 3.5" hard drives
l Dual 1100W power supplies
l Two SLICs, each containing four 10GbE network ports:
n Bay 0: 10GBase-T or 10GbE Twinax/Optical
n Bay 1: 10GBase-T
l RMC shared and dedicated management ports

M1200 (3.9 TB licensed capacity)

l Six 3.5" hard drives
l Dual 1100W power supplies
l Two SLICs, each containing four 10GbE network ports:
n Bay 0: 10GBase-T or 10GbE Twinax/Optical
n Bay 1: 10GBase-T
l RMC shared and dedicated management ports

M2400 (7.8 TB licensed capacity)

l Twelve 3.5" hard drives

Hardware specifications 19
Hardware Specifications

l One 2.5 SSD drive

l Dual 1100W power supplies
l Two SLICs, each containing four 10GbE network ports:
n Bay 0: 10GBase-T or 10GbE Twinax/Optical
n Bay 1: 10GBase-T
l RMC shared and dedicated management ports

Avamar Business Edition/S2400 node (7.8 TB licensed capacity)

l Eight 3.5" hard drives
l One 2.5 SSD drive
l Dual 1100W power supplies
l Two SLICs, each containing four 10GbE network ports:
n Bay 0: 10GBase-T
n Bay 1: 10GBase-T
l RMC shared and dedicated management ports

NDMP accelerator node

l Two 3.5" hard drives
l Dual 1100W power supplies
l One SLIC, containing four 10GbE network ports:
n Bay 0: 10GBase-T or 10GbE Twinax/Optical
l RMC shared and dedicated management ports

Service port connectivity

For all ADS Gen4T nodes, service is performed via the following ports. Connection to
the internal and external network ports is possible only after the node has booted.

Note
Traffic for the remote management console (RMC) may be configured during
installation to share the primary backup network port or use the dedicated RMC port.
The default ports for both configurations are listed in the following table, where
applicable.

Table 3 Service ports

Node state Service port Notes

All Serial port l Authorized EMC personnel use the serial
port to configure nodes, install the Avamar
software, and perform maintenance.
l Customers use the serial port to perform
the initial network configuration when
installing a single-node server.

20 Avamar Data Store Gen4T Comprehensive Reference Guide

 Hardware Specifications

Table 3 Service ports (continued)

Node state Service port Notes

l The serial port is always available, including

when the node is straight from
manufacturing and after rekickstart.

After Avamar multi-node Internal network l Use the internal network IP address
installation switch port 24 assigned to each node during installation.
l The default internal network IP addresses
typically start at 192.168.255.1 for the utility
node.

After Avamar single-node eth1 The primary backup network port.

installation (SLIC0NIC0)
l Use the external (backup) network IP
eth0 (RMC address assigned to the server during
shared) installation.

After Avamar single- or RMC dedicated The dedicated or shared RMC port.
multi-node installation
eth0 (RMC l Use the RMC port IP address assigned to
shared) the node during installation.
l Because configuration of the RMC ports is
optional, the RMC may not always be
accessible.
l When configured, the RMC ports are always
available, including before the system has
booted and when the node is off.

Node components
Before handling ADS Gen4T equipment, first familiarize yourself with the Gen4T node
types and component locations for your specific hardware. See the figures and tables
that follow for details.
Figure 5 Front View

Node components 21
Hardware Specifications

Table 4 Front panel components

Feature Description
Hard drives Hot swappable 3.5 hard drives:
l Utility node - Two in the 0 and 1 drive locations. All others are
blank.
l M600 node - Four in the 0 through 3 drive locations. All others
are blank.
l M1200 node - Six in the 0 through 5 drive locations. All others
are blank.
l M2400 node - 12 in the 0 through 11 drive locations.
l Avamar Business Edition (S2400) node - Eight in the 0
through 7 drive locations. All others are blank.
l Accelerator node - Two in the 0 and 1 drive locations. All
others are blank.

Figure 6 Rear View

Table 5 Rear panel components

Feature Description
Service tag A pull-out label with the serial number and other system
information.

Power supply #0 1100W power supply.

Power supply #1 1100W power supply.

SLIC bays Hosts for network interfaces. Each 10GBase-T or 10GbE Twinax/
Optical SLIC hosts four network ports. All unoccupied bays contain
fillers.

SSD bays Host for SSD storage devices. Only the S2400 and M2400 contain
an SSD. All other models contain two fillers.

22 Avamar Data Store Gen4T Comprehensive Reference Guide

 Hardware Specifications

Table 5 Rear panel components (continued)

Feature Description
RMC shared port The remote management port that is used to share remote
management traffic and backup traffic.

RMC dedicated port The remote management port that is used when remote
management traffic is not shared.

USB port Connects a USB device.

Serial port Connects a device via RS-232 to provide direct access to the
console.

Gen4T hardware does not support direct monitor and keyboard

connectivity.

Do Not Unplug LED Indicates that the node should not be powered off or unplugged.

Service LED Indicates that the node requires some type of service.

Power LED Indicates that the node is powered on.

Reset Reset the node by using the end of a paper clip to press the Reset
button. Use this button only if directed to do so by qualified
support personnel.

Node components 23
Hardware Specifications

24 Avamar Data Store Gen4T Comprehensive Reference Guide

CHAPTER 3
Networking

This chapter provides a comprehensive description of optional networking features

and requirements for both single-node and multi-node ADS Gen4T systems, including
the following topics:

l Overview............................................................................................................26
l Default port configuration.................................................................................. 26
l Basic networking configuration.......................................................................... 28
l Supported network configurations.....................................................................29
l Advanced network configuration dpnnetutil utility.......................................... 34
l Replication......................................................................................................... 36

Networking 25
Networking

Overview
The information in this chapter is for reference only. If advanced network or
replication configuration is required, EMC personnel must perform those activities
before installing the Avamar software.
Included in this chapter are:
l General overview of ADS Gen4T networking principles
l Descriptions of different network configurations ADS servers can interconnect
with
l An overview of the optional dpnnetutil advanced configuration utility
l Descriptions of replication schemes supported by ADS Gen4T

Default port configuration

Notation
With ADS Gen4T, the notation SLICXNICY is used to describe the physical location of
network ports residing on SLICs, where X and Y are the SLIC number and the network
port number on that SLIC, respectively.
l SLICs are numbered from left to right, starting at 0
l Network ports on SLICs are numbered from bottom to top, starting at 0
Location
The dedicated and shared remote management console ports are located on the rear
I/O panel. All other network ports reside on SLICs.
Figure 7 Gen4T Network Ports

Default network configuration is performed during Avamar software installation. The

default configuration and basic networking principles are described below.

Multi-node servers
A multi-node ADS Gen4T server divides network traffic between internal Avamar
traffic and external customer communications. Multi-node systems have two internal
switches (to support high-availability) on an isolated network for internal Avamar
traffic between nodes. Customers provide external switching and connections to
match their infrastructure for backups, replication, and node management.
All nodes are connected to dual dedicated switches through the eth7 (SLIC1NIC2) and
eth8 (SLIC1NIC3) ports. These ports are normally bonded together as bond1.

26 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

l eth7 (SLIC1NIC2) is the primary, eth8 (SLIC1NIC3) is the secondary

The internal network is a redundant, high availability, fault-tolerant network
connecting all nodes in the cluster for RAIN, rebuilding, and maintenance functions. It
carries all Avamar internal operations and data management traffic.
For the ADS external network, the default configuration depends on whether the
remote management console (RMC) port is dedicated or shared.
When high availability is desired, the primary and secondary external network ports
are normally bonded together as bond0 for backing up customer data.
For systems configured with dedicated RMC ports:
All nodes are connected directly to a customer network switch through the eth1
(SLIC0NIC0) port. If high availability is desired, all nodes can also be connected to a
different customer network switch through the eth2 (SLIC0NIC1) port.
eth1 (SLIC0NIC0) is the primary, eth2 (SLIC0NIC1) is the secondary.
The remote management connection is made through the RMC dedicated port on the
rear I/O panel.
For systems configured with shared RMC ports:
All nodes are connected directly to a customer network switch through the eth0
(RMC shared) port. If high availability is desired, all nodes can also be connected to a
different customer network switch through the eth1 (SLIC0NIC0) port.
eth0 (RMC shared) is the primary, eth1 (SLIC0NIC0) is the secondary.
The remote management connection is made through the eth0 (RMC shared) port on
the rear I/O panel.
The default settings can be changed through the dpnnetutil utility described in
Advanced network configuration dpnnetutil utility on page 34.

Single-node servers
A single-node ADS Gen4T server divides different types of network traffic onto
different network interfaces. Customers provide external switching and connections
to match their infrastructure for backups, replication, and management.
For the ADS external network, the default configuration depends on whether the
remote management console (RMC) port is dedicated or shared.
When high availability is desired, the primary and secondary external network ports
are normally bonded together as bond0 for backing up customer data.
For systems configured with dedicated RMC ports:
The server is connected directly to a customer network switch through the eth1
(SLIC0NIC0) port. If high availability is desired, the server can also be connected to a
different customer network switch through the eth2 (SLIC0NIC1) port.
eth1 (SLIC0NIC0) is the primary, eth2 (SLIC0NIC1) is the secondary.
The remote management connection is made through the RMC dedicated port on the
rear I/O panel.
For systems configured with shared RMC ports:
The server is connected directly to a customer network switch through the eth0
(RMC shared) port. If high availability is desired, the server can also be connected to a
different customer network switch through the eth1 (SLIC0NIC0) port.
eth0 (RMC shared) is the primary, eth1 (SLIC0NIC0) is the secondary.

Single-node servers 27
Networking

The remote management connection is made through the eth0 (RMC shared) port on
the rear I/O panel.
The default settings can be changed through the dpnnetutil utility described in
Advanced network configuration dpnnetutil utility on page 34.

Basic networking configuration

ADS Gen4T systems follow these configuration principles:
l All connections to the customer network are standard leaf connections.
l The external customer network switch can be shared with other applications.
l All networking ports are bonded in pairs, by default.
l Both remote management ports on the rear I/O panel auto-negotiate to 1 Gb
Ethernet (full duplex).
l All four network ports on a 10GBase-T SLIC in bay 0 auto-negotiate to 1 Gb or 10
Gb Ethernet (full duplex).
l All four network ports on a 10GbE Twinax/Optical SLIC in bay 0 operate at 10 Gb
Ethernet (full duplex).
l Both management network ports eth5 (SLIC1NIC0) and eth6 (SLIC1NIC1)
autonegotiate to 1 Gb Ethernet (full duplex).
If the customer network environment is segregated using backup virtual local area
networks (VLANs), corresponding VLANs must be configured on the Avamar server.
The customer network administrator must provide a list of VLAN IDs to be used by
EMC personnel when running the dpnnetutil utility.
For ADS networks that do not require advanced configuration like VLAN and network
address translation (NAT) support, the network configuration included in the standard
software installation is used. The exception is the primary backup network port, which
must be configured by EMC personnel in advance of software installation.

Note

As noted in this list of basic network configurations, Avamar systems support the use
of VLANs and separately support the use of NAT. However, Avamar does not support
the use of NAT on VLANs.

If all backup, replication, and management interfaces are used, ensure that they are
configured for different subnets.
See Node components on page 21 for descriptions and images related to node
components. The following images provide further clarification of possible ADS Gen4T
networking configurations.

Multi-node servers
For multi-node servers, primary and secondary port bonding on storage nodes can be
broken to facilitate incoming replication, which is delivered directly to storage nodes,
or for node management. If this bond is broken, high availability backup capability is
not possible.
The utility node can also be plugged in to a customer network switch for optional
outgoing replication and node management through its additional four network
interfaces. These interfaces are also bonded in pairs for high availability configuration:

28 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

l Outgoing replication: eth3 (SLIC0NIC2) and eth4 (SLIC0NIC3)

l Management: eth5 (SLIC1NIC0) and eth6 (SLIC1NIC1)
The ADS internal switches are not connected to the customer network. They have
redundant power to support fault tolerance.
Both internal network ports eth7 (SLIC1NIC2) and eth8 (SLIC1NIC3) autonegotiate to
1 Gb Ethernet (full duplex).

Supported network configurations

The following sections describe networking scenarios supported by ADS Gen4T
servers.
l Single uplink to an external customer network
l Dual uplink to an external customer network
l Dual uplink plus options to an external customer network

Multi-node servers
Single uplink to external customer network
The following figures illustrate dual dedicated ADS switches (ADS Switch A and B)
and a single uplink from all nodes to the customer network switch.
Figure 8 Single Uplink (Dedicated RMC Port)

Supported network configurations 29

Networking

Figure 9 Single Uplink (Shared RMC Port)

Dual uplink to external customer network

For high-availability configurations, the following figures illustrate dual dedicated ADS
switches (ADS Switch A and B) and dual uplinks from all nodes to the customer
network.
Figure 10 Dual Uplink (Dedicated RMC Port)

Figure 11 Dual Uplink (Shared RMC Port)

The high-availability external network provides an Avamar server that continues

operating through any single network component failure, including:

30 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

l Any ADS network interface on the external network

l Any single uplink cable from the ADS to the customer network
l Any port on the customer network used in the uplink
l An entire customer switch used in the uplink
l Connectivity between customer switches used in the uplink

Dual uplink plus options to external customer network

For high-availability configurations plus replication and management traffic options,
the following figures illustrate:
l Dual dedicated ADS switches (ADS Switch A and B),
l Dual uplinks from all nodes to the customer network switch for high-availability
backups, and
l Single or dual connections to the customer network for outgoing replication or
administration traffic.
Figure 12 Dual Uplink plus Options (Dedicated RMC Port)

Figure 13 Dual Uplink plus Options (Shared RMC Port)

Multi-node servers 31
Networking

This high-availability external network provides an Avamar server that continues

operating through any single failure in a default or optional network component,
including:
l Any ADS network interface on the external network
l Any single uplink cable from the ADS to the customer network
l Any port on the customer network used in the uplink
l An entire customer switch used in the uplink
l Connectivity between customer switches used in the uplink

Single-node servers
Single uplink to external customer network
The following figures illustrate a single uplink from the server to the customer network
switch.
Figure 14 Single Uplink (Dedicated RMC Port)

Figure 15 Single Uplink (Shared RMC Port)

32 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

Dual uplink to external customer network

For high-availability configurations, the following figures illustrate dual uplinks from
the server to the customer network.
Figure 16 Dual Uplink (Dedicated RMC Port)

Figure 17 Dual Uplink (Shared RMC Port)

The high-availability external network provides an Avamar server that continues

operating through any single network component failure, including:
l Any ADS network interface on the external network
l Any single uplink cable from the ADS to the customer network
l Any port on the customer network used in the uplink
l An entire customer switch used in the uplink
l Connectivity between customer switches used in the uplink

Dual uplink plus options to external customer network

For high-availability configurations plus replication and management traffic options,
the following figures illustrate:
l Dual uplinks from the server to the customer network switch for high-availability
backups, and
l Single or dual connections to the customer network for outgoing replication or
administration traffic.

Single-node servers 33
Networking

Figure 18 Dual Uplink plus Options (Dedicated RMC Port)

Figure 19 Dual Uplink plus Options (Shared RMC Port)

This high-availability external network provides an Avamar server that continues

operating through any single failure in a default or optional network component,
including:
l Any ADS network interface on the external network
l Any single uplink cable from the ADS to the customer network
l Any port on the customer network used in the uplink
l An entire customer switch used in the uplink
l Connectivity between customer switches used in the uplink

Advanced network configuration dpnnetutil utility

For ordinary implementations, the normal software installation process provides all
functionality that is required to configure networking on ADS systems.
For more advanced configurations, the interactive dpnnetutil utility must be run
before software installation. Advanced configuration scenarios include:

34 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

l Support for VLAN interfaces to backup networks

l Setting custom hostnames
l Configuring Network Address Translation (NAT)
l Circumstances in which the Avamar internal network subnet must be changed due
to a conflict with existing customer network devices

Note

Only EMC personnel can run the dpnnetutil utility. If the customer site requires
advanced network configuration, alert the EMC Account Team that the
implementation specialist must run dpnnetutil before installing the Avamar
software. While dpnnetutil is running, the customer may be asked to check certain
hardware-related connectivity errors that the utility might report.

Features provided by dpnnetutil

Running dpnnetutil provides the following features:

Single-node Gen4T systems

For single-node systems, the feature set includes:
l Detection of cabling and connectivity errors during configuration, including:
n No link detected on a network interface
n Link speed below 1GB
n Auto negotiation
n Full duplex
When an error is detected, a dialog box is displayed that describes the error and
the network interfaces affected.
l Determination of the cabling schema based on the number of physical network
interfaces and link presence.
l Configuration of the backup, replication, and management networks, including:
n Requesting IP addresses and netmask for replication and management
networks
n Allowing edit and confirmation later

Note

Remember, if all backup, replication, and management interfaces are configured

for use on the single node server, they must be configured for different subnets.
l Configuration of backup VLAN interfaces, including:
n Requesting a list of VLAN IDs available on the customer network switch
n Requesting corresponding parameters for each VLAN ID (IP, netmask)
The customer network administrator must provide a list of correct VLAN IDs
(typically in the range 1 to 4094). The site networking topology must be such that
all clients are able to resolve the Avamar server by the same hostname from
different VLANs. Otherwise, backup failures may occur.
The dpnnetutil utility populates probe.xml with information obtained during the
configuration procedure.

Features provided by dpnnetutil 35

Networking

Multi-node Gen4T systems

For multi-node systems, the feature set includes:
l Detection of cabling and connectivity errors during configuration, including:
n No link detected on a network interface
n Link speed below 1GB
n Auto negotiation
n Full duplex
When an error is detected, a dialog box is displayed that describes the error and
the network interfaces affected.
l Determination of the cabling schema based on the number of physical network
interfaces and link presence.
l Configuration of the internal network for advanced schemas, including:
n Offering predefined IP ranges for the internal network
n Allowing modification of the IP addresses and netmask later
The internal network isolates internal switches and internal traffic between ADS
nodes from the external customer network. To simplify internal network
configuration, dpnnetutil offers predefined ranges of IP addresses.
You can either select an IP subnet from this list or, to avoid ambiguous routing that
is caused by one of the predefined IP addresses existing on the customer network
or for other reasons, configure new IP addresses manually.
l Configuration of the backup, replication, and management networks, including:
n Requesting IP addresses and netmask for replication and management
networks
n Allowing edit and confirmation later
l Configuration of backup VLAN interfaces, including:
n Requesting a list of VLAN IDs available on the customer network switch
n Requesting corresponding parameters for each VLAN ID (IP, netmask)
The customer network administrator must provide a list of correct VLAN IDs
(typically in the range 1 to 4094). The site networking topology must be such that
all clients are able to resolve the Avamar server by the same hostname from
different VLANs. Otherwise, backup failures may occur.
The dpnnetutil utility populates probe.xml with information obtained during the
configuration procedure.

Replication
The following sections describe the types of replication architectures supported by
ADS systems. For complete instructions on setting up and performing replication,
including terms and concepts, capabilities and limitations, and best practices, see the
EMC Avamar Administration Guide.

Single-node servers
The networking architecture of ADS Gen4T and the Avamar software provide two
types of replication: Basic and Dedicated. They are described in the following sections.

36 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

Basic replication
The source and target systems each have a single network for traffic of all purposes.
Replication is in and out on this single network between the source and target pair.
The target system can be either a multi-node or single-node Avamar server. The
following image shows a multi-node server as the target.
Figure 20 Basic Replication Network

To configure basic replication, the Avamar software must be installed. The EMC
Avamar Administration Guide provides more information about configuring basic
replication.
Dedicated replication
A system that is configured for dedicated replication has dedicated networks on both
source and target systems. On the source system, dedicated backup, replication, and
management ports can be configured. The following image shows a multi-node server
as the target.
Figure 21 Dedicated Replication Network

To configure dedicated replication, the Avamar software must be installed. An EMC

implementation specialist must manually perform additional steps.

Single-node servers 37
Networking

Multi-node servers
The networking architecture of ADS Gen4T and the Avamar software provide three
types of replication: Basic, Dedicated, and Disaster Recovery (DR). They are
described in the following sections.
Basic replication
The source and target systems each have a single network for traffic of all purposes.
Replication is in and out on the single network between the source and target pair.
Cross-replication between source and target systems is also supported by performing
the same procedure on the target.
Figure 22 Basic Replication Network

To configure basic replication, the Avamar software must be installed. The EMC
Avamar Administration Guide provides more information about configuring basic
replication.
Dedicated replication
A system that is configured for dedicated replication has dedicated networks on both
source and target systems. On the source system, dedicated backup, replication, and
management ports can be configured on the utility node. On the target system, the
bonds between primary and secondary backup ports on the storage nodes are broken,
and the secondary backup ports are dedicated to replication traffic.
Cross-replication between source and target systems is also supported by performing
the same procedure on the target.

38 Avamar Data Store Gen4T Comprehensive Reference Guide

 Networking

Figure 23 Dedicated Replication Network

To configure dedicated replication, the Avamar software must be installed. An EMC

implementation specialist must manually perform additional steps.
Disaster Recovery (DR) replication
This configuration is similar to dedicated replication, except replication is configured
to the backup ports on the target system. Replication traffic is only segregated from
backup traffic on the source system. DR replication is for providing a target system as
a standby to the source in case of disaster.
Cross-replication between source and target systems is not supported.
Figure 24 DR Replication

To configure DR replication, the Avamar software must be installed. An EMC

implementation specialist must manually perform additional steps.

Multi-node servers 39
Networking

40 Avamar Data Store Gen4T Comprehensive Reference Guide

CHAPTER 4
Installation and Beyond

The following topics describe setup procedures for an ADS system and followup
activities:

l Avamar "installation" process............................................................................ 42

l Everyday use of Avamar servers........................................................................ 42
l Maintenance of the server................................................................................. 43

Installation and Beyond 41

Installation and Beyond

Avamar "installation" process

The industry term "installation" is generally used to describe the entire process of
installing a product. For ADS hardware, at a high level, installation is actually a three-
step process:
l Siting
l Installation
l Implementation

Siting
Siting is the process of determining where ADS equipment will be located. Numerous
thermal, acoustic, electrical, regulatory, and environmental requirements must be
taken into account before going forward with installation and implementation.
See the EMC Avamar Data Store Gen4, Gen4S, and Gen4T Site Prep Technical
Specifications document on the EMC Online Support site (http://support.emc.com)
for comprehensive information about siting ADS hardware.

Installation
Installation consists of racking, stacking, and cabling the ADS equipment and then
performing a minimal amount of network configuration to place the system on the
customers network for remote implementation.
ADS multi-node server installation must be performed by EMC personnel. Instructions
for doing so are contained in the SolVe Desktop utility and are accessible only to EMC
personnel.
ADS single-node server installation can be performed by customers. Instructions for
doing so are contained in the EMC Avamar Data Store Single Node Customer Installation
Guide, which can be found on the EMC Online Support site. If EMC is contracted to do
the installation, those instructions are located in the SolVe Desktop utility.

Implementation
Implementation consists of copying and configuring the Avamar software on each
node in the ADS system and preparing the Avamar subsystem to function as a backup
and restore tool. Implementation also involves procedures for setting up the initial
Avamar configuration as it relates to the unique backup, restore, and replication
requirements of the customer environment.

Everyday use of Avamar servers

The customer is responsible for the everyday configuration and use of the backup,
restore, and replication functions of the Avamar server. Those activities are described
in detail in the Avamar core documentation set, which provide a comprehensive set of
feature overview, operational task, and technical reference information.
The primary user document is the EMC Avamar Administration Guide but that is just one
of a wide range of guides that help define the possible uses of the Avamar server,
including the following:
l EMC Avamar Release Notes

42 Avamar Data Store Gen4T Comprehensive Reference Guide

 Installation and Beyond

l EMC Avamar Product Security Guide

l EMC Avamar Operational Best Practices Guide
l EMC Avamar and EMC Data Domain System Integration Guide
l EMC Avamar Backup Clients User Guide
l EMC Avamar for VMware User Guide
l EMC Avamar for Exchange VSS User Guide
l EMC Avamar for Lotus Domino User Guide
l EMC Avamar for Oracle User Guide
l EMC Avamar for SharePoint VSS User Guide
l EMC Avamar for SQL Server User Guide
l EMC Avamar for Hyper-V VSS User Guide
l EMC Avamar for SAP with Oracle User Guide
l EMC Avamar for Sybase ASE User Guide
l EMC Avamar for Windows Server User Guide
l EMC Avamar for IBM DB2 User Guide
l EMC Avamar Management Console Command Line Interface (MCCLI) Programmer
Guide
l EMC Avamar NDMP Accelerator User Guide
l EMC Backup & Recovery Manager User Guide
Before implementation, these documents can be found by using the search function
on the EMC Online Support site. Search for each by the name shown above. After
implementation, these documents can be found on the Avamar Documentation page
on the Avamar server and on the EMC Online Support site.
In addition, various EMC technical notes provide details about specific product
features, including step-by-step tasks, where necessary. These documents usually
focus on supplemental information about rare, unique, or version-specific installation,
implementation, and configuration scenarios. They are also located on the EMC Online
Support site.

Maintenance of the server

ADS servers require maintenance from time to time, including replacement of
defective components, upgrading software, and adding capacity to servers running
out of backup space.
Replacement of components is an activity performed mostly by EMC personnel.
Customers can replace defective hard drives and power supplies (see the EMC Avamar
Data Store Customer Service Guide for instructions). To fix any other node component,
contact EMC Customer Support.
An Avamar software upgrade is an activity performed only by EMC personnel.
Software upgrades consist of changes to the Linux operating system, hardware
firmware, and patches to the Avamar software itself.
Adding capacity to an existing ADS server is another activity performed only by EMC
personnel. Adding capacity to a multi-node server consists of installing and configuring
additional nodes, and then including the additional nodes as part of the server.

Maintenance of the server 43

Installation and Beyond

44 Avamar Data Store Gen4T Comprehensive Reference Guide

Copyright 2015 EMC Corporation. All rights reserved. Published in USA.

EMC believes the information in this publication is accurate as of its publication date. The information is
subject to change without notice.
The information in this publication is provided as is. EMC Corporation makes no representations or
warranties of any kind with respect to the information in this publication, and specifically disclaims
implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution
of any EMC software described in this publication requires an applicable software license.
EMC, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the
United States and other countries.
All other trademarks used herein are the property of their respective owners.
For the most up-to-date regulatory document for your product line, go to EMC Online Support
(https://support.emc.com).