Dell EMC Avamar Virtual Edition for Azure

Version 7.5.1

Installation and Upgrade Guide

302-004-298
REV 03
Copyright © 2016-2018 Dell Inc. or its subsidiaries. All rights reserved.

Published May 2018

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.

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

2 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
CONTENTS

Preface 5

Chapter 1 Introduction 9
Overview of Avamar Virtual Edition for Azure............................................. 10
Appropriate environments for AVE..............................................................10

Chapter 2 Installation 13
Preinstallation requirements and best practices.......................................... 14
System requirements..................................................................... 14
AVE virtual disk requirements.........................................................14
Software requirements.................................................................. 15
Installation.................................................................................................. 15
Deploying AVE from the Azure Marketplace...................................16
Deploy AVE and DDVE together from the Azure Marketplace........ 19
Network security group..................................................................21
AVE and DDVE deployment via Azure solution template............................. 24
Uploading the AVE image.............................................................. 25
Solution template parameters........................................................26
Deploying AVE and DDVE from the Azure Resource Manager....... 28
Deploying AVE and DDVE from Azure Powershell..........................29
Post-deployment configuration..................................................... 30
Azure security best practices...................................................................... 31
Installing and configuring the Avamar software.......................................... 33
Upgrading the Avamar software................................................................. 34
Post-installation and post-upgrade tasks................................................... 35

Appendix A Using NAT 37

Configuring AVE to use NAT.......................................................................38

Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide 3
CONTENTS

4 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
PREFACE

As part of an effort to improve the product lines, revisions of the software and
hardware are periodically released. Therefore, some functions that are described in
this document might not be supported by all versions of the software or hardware
currently in use. The product release notes provide the most up-to-date information
on product features.
Contact the technical support professional when a product does not function correctly
or does not function as described in this document.

Note

This document was accurate at publication time. To find the latest version of this
document, go to Online Support (https://support.EMC.com).

Purpose
This guide describes how to install the Avamar Virtual Edition solution, a single-node,
non-RAIN server that runs as a virtual machine in a Microsoft Azure environment.
Audience
The information in this guide is primarily intended for system administrators who are
responsible for installing and maintaining Avamar virtual servers.
Revision history
The following table presents the revision history of this document.

Revision Date Description

01 February 1, 2018 GA release of Avamar 7.5.1

02 February 23, 2018 Additional updates for Avamar

7.5.1.

03 May 03, 2018 Added a new section

Deploying DDVE and AVE
from the Azure Marketplace.

Related documentation
The following publications provide additional information:
l Avamar Release Notes
l Avamar Administration Guide
l Avamar Operational Best Practices Guide
l Avamar Product Security Guide
l Avamar Backup Clients User Guide

Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide 5
PREFACE

Special notice conventions used in this document

These conventions are used for special notices.

DANGER

Indicates a hazardous situation which, if not avoided, results in death or serious

injury.

WARNING

Indicates a hazardous situation which, if not avoided, could result in death or

serious injury.

CAUTION

Indicates a hazardous situation which, if not avoided, could result in minor or

moderate injury.

NOTICE

Addresses practices that are not related to personal injury.

Note

Presents information that is important, but not hazard-related.

Typographical conventions
These type style conventions are used in this document.

Table 1 Typographical conventions

Bold Used for names of interface elements, such as names of windows,

dialog boxes, buttons, fields, tab names, key names, and menu paths
(what the user specifically selects or clicks)

Italic Used for full titles of publications that are referenced in text
Monospace Used for:
l System code
l System output, such as an error message or script
l Pathnames, filenames, prompts, and syntax
l Commands and options

Monospace italic Used for variables

Monospace bold Used for user input

[] Square brackets enclose optional values

| Vertical bar indicates alternate selections - the bar means “or”

{} Braces enclose content that the user must specify, such as x or y or

z

... Ellipses indicate nonessential information that is omitted from the

example

6 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 PREFACE

Where to get help

The Avamar support page provides access to licensing information, product
documentation, advisories, and downloads, as well as how-to and troubleshooting
information. This information may resolve a product issue before contacting Customer
Support.
To access the Avamar support page:
1. Go to https://support.EMC.com/products.
2. Type a product name in the Find a Product by Name box.
3. Select the product from the list that appears.
4. Click the arrow next to the Find a Product by Name box.
5. (Optional) Add the product to the My Products list by clicking Add to My Saved
Products in the upper right corner of the Support by Product page.
Comments and suggestions
Comments and suggestions help to continue to improve the accuracy, organization,
and overall quality of the user publications. Send comments and suggestions about
this document to [email protected].
Please include the following information:
l Product name and version
l Document name, part number, and revision (for example, 01)
l Page numbers
l Other details to help address documentation issues

Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide 7
PREFACE

8 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
CHAPTER 1
Introduction

This chapter includes the following topics:

l Overview of Avamar Virtual Edition for Azure.....................................................10

l Appropriate environments for AVE..................................................................... 10

Introduction 9
Introduction

Overview of Avamar Virtual Edition for Azure

Avamar Virtual Edition (AVE) is a single-node non-RAIN (Redundant Array of
Independent Nodes) Avamar server that runs as a virtual machine in a Microsoft Azure
environment. AVE integrates the latest version of Avamar software with SUSE Linux
as a Hyper-V virtual machine.
AVE is similar to single-node Avamar servers in the following ways:
l Runs autonomously as a target for all Avamar client backups
l Supports replication in the cloud.
AVE on Azure can be used to replicate on-premises physical Avamar servers and
AVEs, including non-Azure types of AVEs. However, because of security
considerations, replication should be performed by using a VPN, VPC, or a direct
connect link.
AVE supports four configurations: 0.5 TB, 1 TB, 2 TB, and 4 TB licensed capacity. AVE
is not scalable to a multi-node Avamar server and resizing the virtual machine is not
supported. You can increase storage capacity by deploying additional AVE virtual
machines, and then divide backups among them. Or you can replicate the data to
another AVE server, delete the smaller virtual machine, create a larger virtual machine,
and replicate the data back to the larger virtual machine.

Appropriate environments for AVE

The following factors have the most direct impact on the long-term reliability,
availability, and supportability of the AVE virtual machine:
l I/O performance capability of the AVE storage subsystem
l Amount of data added daily to the AVE virtual machine (change rate)
l Capacity that is utilized within the AVE virtual machine
Specifications in this section and AVE virtual disk requirements on page 14 describe
minimum or maximum requirements for these factors. AVE generally performs better
when I/O performance is higher. Change rate and utilized capacity are also lower. To
maximize the capacity the AVE virtual machine can use, the daily change rate of the
data AVE protects must be balanced with adequate I/O performance.
The first step in determining the proper implementation of AVE is to establish which
kind of customer environment AVE is used to protect, file server or mixed
environment. File server environments include file system data and mixed
environments include file system data and structured data (for example, database
data).
The following table describes the maximum change rates that AVE supports for file
server and mixed environments.

Table 2 Maximum change rates AVE supports for file server and mixed environments

Configuration File server data Mixed data

0.5 TB AVE Less than 2 GB per day Less than 5 GB per day

1 TB AVE Less than 4 GB per day Less than 10 GB per day

2 TB AVE Less than 8 GB per day Less than 20 GB per day

10 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Introduction

Table 2 Maximum change rates AVE supports for file server and mixed
environments (continued)

Configuration File server data Mixed data

4 TB AVE Less than 20 GB per day Less than 20 GB per day

Actual results depend on the retention policy and the actual data change rate. When
the daily change rate exceeds the limits that are specified in the previous table, deploy
a single or multi-node Avamar server.

Appropriate environments for AVE 11

Introduction

12 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
CHAPTER 2
Installation

This chapter include the following topics:

l Preinstallation requirements and best practices................................................. 14

l Installation.......................................................................................................... 15
l AVE and DDVE deployment via Azure solution template.....................................24
l Azure security best practices............................................................................. 31
l Installing and configuring the Avamar software..................................................33
l Upgrading the Avamar software.........................................................................34
l Post-installation and post-upgrade tasks........................................................... 35

Installation 13
Installation

Preinstallation requirements and best practices

Before you install an AVE virtual machine, follow the preinstallation requirements and
review the best practices in the following sections.
The following items are new for Avamar 7.5.1:
l The default password is no longer a fixed value. Instead, the default password is
now the private IPv4 address for the AVE virtual machine.
l Direct root access via SSH is no longer allowed, before or after installation of the
Avamar software.

Note

Using third party tools to create clones or exact copies of deployed Avamar Virtual
Edition systems is known to cause issues. Cloning of Avamar Virtual Edition systems is
not supported.

System requirements
Avamar Virtual Edition (AVE) is supported on Microsoft Azure.
The following table defines the minimum system requirements for each size of AVE.

Table 3 Minimum requirements for AVE

0.5 TB AVE 1 TB AVE 2TB AVE 4 TB AVE

Processors Minimum two 2 Minimum two 2 Minimum two 2 Minimum four 2
GHz processors GHz processors GHz processors GHz processors

Memory 6 GB 6 GB 14 GB 28 GB

Disk space 850 GB 1,600 GB 3,100 GB 6,100 GB

Network 1 GbE connection 1 GbE connection 1 GbE connection 1 GbE connection

connection

Azure Standard A5 A6 A5 A6
Tier

AVE virtual disk requirements

The AVE disk layout comprises one operating system disk (126 GB) and several
storage partitions (250 GB, 500 GB, or 1000 GB, depending on the AVE
configuration).
The OS disk stores the operating system, Avamar application, and log files.
The storage partitions store the backup data. Backup data is evenly distributed across
the storage partitions. The primary amount of the disk read, write, and seek usage
occurs on the storage partitions.
In addition to the OS partition, the following table defines the number and size of
virtual disks that are required for each AVE configuration.

14 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

Table 4 AVE virtual disk requirements

AVE configuration Number of virtual disks

0.5 TB 3 storage partitions (250 GB each)

1 TB 6 storage partitions (250 GB each)

2 TB 3 storage partitions (1000 GB each)

4 TB 6 storage partitions (1000 GB each)

Software requirements
Before you install AVE, ensure that you have the software that is listed in the following
table.

Table 5 Additional AVE software installation requirements

Requirement Description
Applications Azure Cloud subscription

7zip to decompress virtual hard drive file (.vhd) from Avamar

Azure Powershell to execute Azure specific Powershell commands

Files AVE Package, operating system security patches (if applicable)

Support for application databases in standalone configuration only

Backup and recovery of the following applications are supported with AVE on Azure.
However, these applications are supported in standalone configuration only. Clustered
configurations of application databases are not supported with AVE on Azure.
l SQL
l Exchange
l SharePoint
l Lotus
l DB2
l Sybase
l SAP
l Oracle

Installation
The following sections are describe how to install an AVE virtual machine in Microsoft
Azure environments.
This section provides instructions for preparing the virtual machine in the Azure Portal
(also known as the Azure Resource Manager).

Software requirements 15
Installation

Deploying AVE from the Azure Marketplace

The Avamar Virtual Edition (AVE) software is available in the Microsoft Azure
marketplace.

Note

For security considerations, deploy AVE in a private network and configure a secure
gateway from which you can install, configure, and manage the Avamar server. Azure
security best practices provides detailed information on how to set up an additional
secure gateway system for AVE maintenance in the cloud.

Procedure
1. Open the Azure portal at https://portal.azure.com and log in to the Azure
account.
2. In the Azure Marketplace, search for and deploy the Avamar Virtual edition
application.
3. To start the Avamar Virtual Edition Deployment wizard, click Create.
4. Configure the basic setting for the virtual machine:
a. In the Name field, type a name for the virtual machine.

Note

The maximum length of the virtual machine name is 10 characters.

b. In the VM disk type field, select HDD.

c. In the User name field, type a username.
d. In the Authentication type field, select one of the following options:
l In the SSH Public Key field, type the public key.
l In the Password field, type the password.

e. Verify the subscription information.

f. In the Resource Group, perform one of the following steps:
l To create a resource group, click Create new.
l To select a resource group, click Use existing and then select the
resource group that you would like to use.

g. In the Location field, select a location to deploy the virtual machine.

h. Click OK to continue.
5. Choose the size of the virtual machine:
a. Select at least A5 Standard for the VM size that you would like to deploy.
Refer to the following table for minimum system requirements for each size
of AVE.

16 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

Table 6 Minimum requirements for AVE

0.5 TB AVE 1 TB AVE 2TB AVE 4 TB AVE

Processors Minimum two Minimum two Minimum two Minimum four
2 GHz 2 GHz 2 GHz 2 GHz
processors processors processors processors

Memory 6 GB 6 GB 14 GB 28 GB

Disk space 850 GB 1,600 GB 3,100 GB 6,100 GB

Network 1 GbE 1 GbE 1 GbE 1 GbE

connection connection connection connection connection

Azure A5 A6 A5 A6
Standard Tier

b. Click Select to continue.

6. Configure settings for the virtual machine.
a. In the Availability set field, select None.
b. In the Storage field, keep the default setting of Yes.
c. In the Virtual network field, select an existing or create a new virtual
network.
d. In the Subnet field, select a subnet.
e. In the Public IP address field, select None.

Note

For security considerations, deploy AVE in a private network and leave the
Public IP address field set to None.

f. In the Network security group (firewall) field, add inboud/outbound rules.

Network security group on page 21 contains information about required
inbound/outbound rules for the AVE.

g. In the Extensions field, keep the default setting of No extensions.

h. In the Enable auto-shutdown field, keep the default setting of Off.
i. In the Boot diagnostics field, keep the default setting of Enabled.
j. In the Guest OS diagnostics field, keep the default setting of Disabled.
k. In the Diagnostics storage account field, select an existing or create a
storage account.
l. Click OK to continue.
7. Review the summary for the Avamar Virtual Edition (AVE) software and then
click Create.
8. Create the data disks for AVE by performing the following steps:
a. From the disks configuration page for the virtual machine, click Add data
disk.
b. Click Create new.

Deploying AVE from the Azure Marketplace 17

Installation

c. Type a name for the data disk.

d. Select Use existing for Resource Group and select the resource group that
you created in the previous step.
e. Select Standard_LRS for Account type.
f. Select empty disk for Source type.
g. Create the following disks, as specified for the AVE size:

Table 7 AVE virtual disk requirements

AVE configuration Number of virtual disks

0.5 TB 3 storage partitions (250 GB each)

1 TB 6 storage partitions (250 GB each)

2 TB 3 storage partitions (1000 GB each)

4 TB 6 storage partitions (1000 GB each)

Note

Verify that all of the storage partitions are the same size before continuing.

9. Create a static IP address for the virtual machine by performing the following
substeps:
a. From the network interface configuration page for the virtual machine, click
IP Configurations.
b. Click the network name.
c. Select Static for the Private IP Address.
10. Obtain the AVE private IPv4 address by performing one of the following
substeps:
a. Use the Azure Portal to obtain the private IPv4 address.
The Microsoft documentation for the Azure Portal provides more
information.

b. Use the Azure CLI to obtain the private IPv4 address by typing the following
command:
az vm list-ip-addresses --name vm-name

c. Record the private IPv4 address for future use. This value is the default
password for AVE.
11. Install the AVE.
Installing and configuring the Avamar software on page 33 contains
instructions.

18 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

Note

After launching the instance, the AVE initializes and restarts automatically.
During this process, which takes 15–25 minutes, the AVE installs drivers and an
updated kernel. You cannot install the AVE until this process is complete
because the AVE installation package, ave-config, is not available in the
Avamar Installation Manager. SSH is also unavailable during this time.

Deploy AVE and DDVE together from the Azure Marketplace

This section provides information on how to deploy the AVE and DDVE software
together from the Microsoft Azure Marketplace.

Note

For security considerations, deploy AVE in a private network and configure a secure
gateway from which you can install, configure, and manage the Avamar server. Azure
security best practices provides detailed information on how to set up an additional
secure gateway system for AVE maintenance in the cloud.

Procedure
1. Open the Azure portal at https://portal.azure.com and log in to the Azure
account.
2. In the Azure Marketplace, search for and deploy the Dell EMC Avamar and Data
Domain Virtual Edition.
3. To start the Dell EMC Avamar and Data Domain Virtual Edition wizard, click
Create.
4. Configure the basic setting for the virtual machine:
a. In the Subscription field, select a type of subscription from the options
available from the list.
b. In the Resource Group, perform one of the following steps:
l To create a resource group, click Create new.
l To select a resource group, click Use existing and then select the
resource group that you would like to use.

c. In the Location field, select a location to deploy the virtual machine.

d. Click OK to continue.
5. Configure the infrastructure for the virtual machine:
a. In the Virtual network field, select an existing or create a new virtual
network.
b. In the Subnet field, select a subnet.
c. In the Diagnostics storage account field, select an existing or create a
storage account.
d. Click OK to continue.
6. Configure AVE for the virtual machine:
a. In the AVE Version field, select the version from the list.

Deploy AVE and DDVE together from the Azure Marketplace 19

Installation

b. In the AVE Name field, enter the host name of the AVE.
You can enter a maximum of ten characters for the AVE host name.

c. In the AVE Size field, select an option available from the options available in
the list.
d. In the Admin User Name field, enter the name for the administrator.
You can ssh to the AVE with this user, admin or root is not allowed for the
user name.

e. In the Admin Authentication Type field, select one of the following options:
l If you select SSH Public Key, enter the public key.
l If you select Password, type the password you want in the Password
and Confirm Password fields.

f. Click OK to continue.
7. Configure DDVE for the virtual machine:
a. In the DDVE Version field, select the version from the list.
b. In the DDVE Name field, enter the host name of the DDVE.
You can enter a maximum of ten characters for the DDVE host name.

c. In the DDVE VM Size field, select an option available from the options
available in the list.
d. In the Data Disk Size field, select the size of the disk from the options
available in the list.
e. In the SysAdmin Authentication Type field, select one of the following
options:
l If you select SSH Public Key, enter the public key.
l If you select Password, type the password you want in the Password
and Confirm Password fields.

f. Click OK to continue.
8. Review the summary for the AVE and DDVE software and then click OK.
9. In the Buy section, review the terms of use and click Create.
The application displays the Azure user account and the status of the
deployment.

Note

To monitor and view the details of the deployment, click on the deployment.
After the deployment is complete, you can get a private IP of AVE and DDVE
from the output of the deployment.

Note

After the deployment is complete you need to complete the post deployment
configuration. For more information on post deployment configuration, see
Post-deployment Configuration.

20 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

Network security group

The following tables describe the rules that should be added to an Azure network
security group.

Inbound ports for the Azure network security group

The following tables describe the rules that should be added to an Azure network
security group.

Note

If you want to restrict the source of traffic, set the source with IPv4 or IPv6 CIDR
block, or a single IPv4 or IPv6 address.

Note

Avamar 7.5.1 removes support for HTTP access to TCP port 80. Use the HTTPS ports
443 to access these services instead.

Table 8 Inbound ports for the Azure network security group

Type Protocol Port Range Source

SSH TCP 22 0.0.0.0/0

SSH TCP 22 ::/0

Custom TCP Rule TCP 161 0.0.0.0/0

Custom TCP Rule TCP 161 ::/0

Custom UDP Rule UDP 161 0.0.0.0/0

Custom UDP Rule UDP 161 ::/0

Custom TCP Rule TCP 163 0.0.0.0/0

Custom TCP Rule TCP 163 ::/0

Custom UDP Rule UDP 163 0.0.0.0/0

Custom UDP Rule UDP 163 ::/0

HTTPS TCP 443 0.0.0.0/0

HTTPS TCP 443 ::/0

Custom TCP Rule TCP 700 0.0.0.0/0

Custom TCP Rule TCP 700 ::/0

Custom TCP Rule TCP 7543 0.0.0.0/0

Custom TCP Rule TCP 7543 ::/0

Custom TCP Rule TCP 7778 - 7781 0.0.0.0/0

Custom TCP Rule TCP 7778 - 7781 ::/0

Custom TCP Rule TCP 8543 0.0.0.0/0

Custom TCP Rule TCP 8543 ::/0

Network security group 21

Installation

Table 8 Inbound ports for the Azure network security group (continued)

Type Protocol Port Range Source

Custom TCP Rule TCP 9090 0.0.0.0/0

Custom TCP Rule TCP 9090 ::/0

Custom TCP Rule TCP 9443 0.0.0.0/0

Custom TCP Rule TCP 9443 ::/0

Custom TCP Rule TCP 27000 0.0.0.0/0

Custom TCP Rule TCP 27000 ::/0

Custom TCP Rule TCP 28001 - 28002 0.0.0.0/0

Custom TCP Rule TCP 28001 - 28002 ::/0

Custom TCP Rule TCP 28810 - 28819 0.0.0.0/0

Custom TCP Rule TCP 28810 - 28819 ::/0

Custom TCP Rule TCP 29000 0.0.0.0/0

Custom TCP Rule TCP 29000 ::/0

Custom TCP Rule TCP 30001 - 30010 0.0.0.0/0

Custom TCP Rule TCP 30001 - 30010 ::/0

Outbound ports for the Azure network security group

Note

If you want to restrict the source of traffic, set the source with IPv4 or IPv6 CIDR
block, or a single IPv4 or IPv6 address.

By default, Azure has a rule AllowInternetOutBound with priority 65001 to allow all
outbound internet traffic. Override this rule by adding a rule with a priority (that is, an
integer number) that is greater than all customized rules' priority, and less than
65000: source: *, destination: *, protocol: *, action: Deny. Azure
documentation contains information about creating a firewall rule.

Table 9 Outbound ports for the Azure network security group

Type Protocol Port Range Source

Custom TCP Rule TCP 7 0.0.0.0/0

Custom TCP Rule TCP 7 ::/0

SSH TCP 22 0.0.0.0/0

SSH TCP 22 ::/0

SMTP TCP 25 0.0.0.0/0

SMTP TCP 25 ::/0

DNS (UDP) UDP 53 0.0.0.0/0

DNS (UDP) UDP 53 ::/0

22 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

Table 9 Outbound ports for the Azure network security group (continued)

Type Protocol Port Range Source

Custom TCP Rule TCP 111 0.0.0.0/0

Custom TCP Rule TCP 111 ::/0

Custom TCP Rule UDP 111 0.0.0.0/0

Custom TCP Rule UDP 111 ::/0

Custom TCP Rule TCP 161 0.0.0.0/0

Custom TCP Rule TCP 161 ::/0

Custom UDP Rule UDP 161 0.0.0.0/0

Custom UDP Rule UDP 161 ::/0

Custom TCP Rule TCP 163 0.0.0.0/0

Custom TCP Rule TCP 163 ::/0

Custom UDP Rule UDP 163 0.0.0.0/0

Custom UDP Rule UDP 163 ::/0

HTTPS TCP 443 0.0.0.0/0

HTTPS TCP 443 ::/0

Custom TCP Rule TCP 700 0.0.0.0/0

Custom TCP Rule TCP 700 ::/0

Custom TCP Rule TCP 2049 0.0.0.0/0

Custom TCP Rule TCP 2049 ::/0

Custom UDP Rule UDP 2049 0.0.0.0/0

Custom UDP Rule UDP 2049 ::/0

Custom TCP Rule TCP 2052 0.0.0.0/0

Custom TCP Rule TCP 2052 ::/0

Custom UDP Rule UDP 2052 0.0.0.0/0

Custom UDP Rule UDP 2052 ::/0

Custom TCP Rule TCP 3008 0.0.0.0/0

Custom TCP Rule TCP 3008 ::/0

Custom TCP Rule TCP 8443 0.0.0.0/0

Custom TCP Rule TCP 8443 ::/0

Custom TCP Rule TCP 8888 0.0.0.0/0

Custom TCP Rule TCP 8888 ::/0

Custom TCP Rule TCP 9090 0.0.0.0/0

Custom TCP Rule TCP 9090 ::/0

Custom TCP Rule TCP 9443 0.0.0.0/0

Network security group 23

Installation

Table 9 Outbound ports for the Azure network security group (continued)

Type Protocol Port Range Source

Custom TCP Rule TCP 9443 ::/0

Custom TCP Rule TCP 27000 0.0.0.0/0

Custom TCP Rule TCP 27000 ::/0

Custom TCP Rule TCP 28001-28010 0.0.0.0/0

Custom TCP Rule TCP 28001-28010 ::/0

Custom TCP Rule TCP 29000 0.0.0.0/0

Custom TCP Rule TCP 29000 ::/0

Custom TCP Rule TCP 30001-30010 0.0.0.0/0

Custom TCP Rule TCP 30001-30010 ::/0

AVE and DDVE deployment via Azure solution template

The following topics describe how to deploy AVE and Data Domain Virtual Edition
(DDVE) virtual machines in Azure by using a solution template. The solution template
uses the DDVE 6.1.0 image in the Azure marketplace (ddve-31-ver-060100).
Solution templates are JSON files that simplify the deployment of multiple Azure
resources and dependencies. Use the template to programmatically deploy the
combined AVE and DDVE solution.
Obtain the solution template for AVE and DDVE from Online Support (https://
support.emc.com/) before proceeding. The solution template contains two files:
l AVE_DDVE_SolutionTemplate.json
l AVE_DDVE_SolutionTemplate_parameters.json
The parameter file is only required for deployment via Powershell.
The complete deployment process consists of the following steps:
1. Upload an AVE virtual machine image to Azure and configure prerequisite items.
2. Deploy AVE and DDVE using the solution template.
3. Configure a secure gateway system.
4. Configure DDVE.
5. Configure AVE.
6. Attach the DDVE system to AVE.
Steps 3–6 are outside the scope of this installation guide. The following publications
provide additional information to complete the deployment process:
l Avamar Administration Guide
l Avamar and Data Domain System Integration Guide
l Data Domain Operating System Initial Configuration Guide
l Data Domain Operating System Administration Guide
This installation guide includes steps for the Azure Resource Manager and for
Powershell. The following Microsoft documentation provides additional information
about using solution templates with both interfaces:

24 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

l Deploy resources with Resource Manager templates and Azure portal

l Deploy resources with Resource Manager templates and Azure CLI
l Deploy resources with Resource Manager templates and Azure PowerShell
l Parameter files

Uploading the AVE image

The solution template uses this AVE image for each automatic deployment. This task
also configures several important prerequisite items. Record the indicated values for
later use.
Procedure
1. Download and decompress the AVE virtual appliance file.
Download the required software from https://support.emc.com/.
2. Open the Azure portal at https://portal.azure.com and log in to the Azure
account.
3. Create a resource group by selecting New > Management > Resource Group.
4. Record the name of the new resource group.
5. Create a storage account under this resource group by performing the following
substeps:
a. Select New > Storage > Storage Account.
b. Select Use existing for Resource Group and select the resource group that
you created in the previous step.
6. Record the name of the new storage account.
The storage account also stores the diagnostic logs from the deployment.
7. Create a container under this storage account by performing the following
substeps:
a. Click All Resources in the Navigation page.
b. Select the storage account.
c. Click Containers.
d. Click + Containers.
8. Upload the AVE virtual appliance file to the container by performing the
following substeps:
a. In the container, click Upload.
b. Transfer the AVE virtual appliance file as a Page blob.
Transferring the file may take some time.

If you encounter difficulty while uploading the AVE virtual appliance file, retry
the upload with the Azure command line tool AzCopy or the Azure command-
line interface (CLI).
l https://docs.microsoft.com/en-us/azure/storage/common/storage-use-
azcopy provides more information about AzCopy, including download
instructions and usage examples.
l https://docs.microsoft.com/en-us/azure/virtual-machines/linux/classic/
create-upload-vhd provides more information about the Azure CLI, including
usage examples.

Uploading the AVE image 25

Installation

Transfer the AVE virtual appliance file as a Page blob.

9. Create a virtual network by clicking New > Networking > Virtual network.
Select the resource group that you created in the previous step, and select the
same location as is used by the resource group.
10. Record the name of the new virtual network.
11. Create a subnet by performing the following substeps:
a. Select Virtual networks.
b. Select the new virtual network.
c. Click Subnets.
d. Click +Subnet.
e. Type a name for the subnet.
f. Type a unique address range within the virtual network.
g. (Optional) Associate a network security group with the subnet.
h. (Optional) Associate a route table with the subnet.
i. (Optional) Associate users and roles with the subnet.
j. Click OK.
12. Record the name of the new subnet.
13. Create an image by performing the following substeps:
a. In the Portal, click the plus (+) sign to create a resource.
b. Select Image.
c. Click Create.
d. Type a name for the image.
e. Select Use existing for Resource Group and select the resource group that
you created in the previous step.
f. Select the same location as is used by the resource group.
g. Select Linux for OS type.
h. Browse to the uploaded .vhd file for Storage blob.
i. Select HDD for Account Type.
j. Select Read/write for Host caching.
14. Record the resource ID that is associated with the new AVE image.

Solution template parameters

These template parameters are common, whether you deploy the solution through the
Azure Resource Manager or through Azure Powershell. Use the following descriptions
to provide parameters to the template:
AVE Name
Required. Type the hostname to assign to AVE. Limited to 10 characters, special
characters are prohibited.

AVE Image Resource ID

Required. Provide the value that you recorded when you uploaded the AVE image.

26 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

AVE Size in TB
Select the installed capacity for this AVE instance: either 2 or 4 TB. This selection
governs the choice of Azure standard tier, as detailed in Table 3 on page 14, and
the automatic creation of virtual disks, as detailed in Table 4 on page 15.

AVE Username
Required. Type the name of a new user with administrative privileges for AVE.
Cannot be root or admin.

AVE Authentication Mode

Select the method by which users are authenticated when initiating an SSH
connection: either Password or SSH Public Key.

AVE User Password

Type a password for the new user. Input must be 12–72 characters that include
any three of the following: one lowercase letter, one uppercase letter, one
number, and one special character. Complete this field even if using an SSH
public key for authentication. The Avamar Product Security Guide provides more
information.
The default is Changeme123#.

AVE Ssh Public Key

Required. Provide the representation of the new user's SSH public key. This field
applies only when SSH Public Key authentication is selected. Complete this field
even if using a password for authentication.

DDVE Name
Required. Type the hostname to assign to DDVE. Limited to 10 characters, special
characters are prohibited.

DDVE Virtual Machine Size

Select the maximum installed capacity for this DDVE instance: either
Standard_F4 or Standard_F8. This selection governs the choice of Azure
standard tier and the automatic creation of virtual disks. All virtual disks are 1000
GB.
Standard_F4 supports a maximum capacity of 7 TB. Standard_F8 supports a
maximum capacity of 15 TB.

DDVE Data Disk Size in TB

Select the actual installed capacity for this DDVE instance: integer values
between 1–15 TB. The choice of DDVE Virtual Machine Size limits the values
that are available for selection.
The 0.5 TB value is only for use with the evaluation license. Do not use this value
for any other installations.

DDVE Authentication Mode

Select the method by which users are authenticated when initiating an SSH
connection: either Password or SSH Public Key.

DDVE Sysadmin Password

Type a password for the sysadmin user. Input must be 12–72 characters that
include any three of the following: one lowercase letter, one uppercase letter, one
number, and one special character. Complete this field even if using an SSH

Solution template parameters 27

Installation

public key for authentication. The Data Domain Product Security Guide provides
more information.
The default is Changeme123#.

DDVE Ssh Public Key

Provide the representation of the sysadmin user's SSH public key. This field
applies only when SSH Public Key authentication is selected.

Vnet Existing Resource Group

Required. Type the name of the resource group in which you created the virtual
network.

Vnet Name
Required. Type the name of the new virtual network.

Vnet Subnet Name

Required. Type the name of the subnet that you created within the new virtual
network.

Diagnostics Storage Account Existing Resource Group

Required. Type the name of the resource group in which you created the storage
account.

Diagnostics Storage Account Name

Required. Type the name of the new storage account.

Deploying AVE and DDVE from the Azure Resource Manager

The Azure Resource manager provides a graphical interface for deployment of the
appliances.
Procedure
1. Extract AVE_DDVE_SolutionTemplate.json to a temporary folder on the
local computer.
2. Return to the Azure portal.
3. Click My Dashboard > Template Deployment.
If you do not see Template Deployment, use the dashboard search field to
locate it.
4. Click Create.
The Custom Deployment page opens.
5. Click Build your own template in the editor.
The Edit Template page opens to an empty template and default values in the
editor.
6. Click Load File.
7. Browse to AVE_DDVE_SolutionTemplate.json and then click Open.
The AVE/DDVE template opens in the editor.
8. Click Save.
The Custom Deployment page opens and displays the new template.
9. The Basics section is common to all Azure deployments. Choose an appropriate
Subscription, Resource Group, and Location.

28 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

10. Provide all required AVE and DDVE parameters.

Some fields are preconfigured. Mandatory fields have red names and an *.
Validated fields have a purple border and a green check mark.
Solution template parameters on page 26 provides additional information on
parameter values.

11. Review the terms and conditions, and then check I agree to the terms and
conditions stated above.
12. Click Purchase.
Deployment may take 15–30 minutes. Note all of the return values from the
deployment process.

Deploying AVE and DDVE from Azure Powershell

You can also deploy the appliances from the command line by using Azure Powershell.
This method provides the required parameters in the
AVE_DDVE_SolutionTemplate_parameters.json file.
Procedure
1. Extract AVE_DDVE_SolutionTemplate.json and
AVE_DDVE_SolutionTemplate_parameters.json to a temporary folder
on the local computer.
2. Edit AVE_DDVE_SolutionTemplate_parameters.json with a text editor
and provide the required values.
Solution template parameters on page 26 provides additional information. Each
parameter in this file corresponds to an input field in the Azure Resource
Manager method.
For example:
{
"$schema": "https://schema.management.azure.com/schemas/
2015-01-01/deploymentParameters.json#",
"contentVersion": "1.0.0.0",
"parameters": {
"AVEName": {
"value": "AVE-test"
},
"AVEImageResourceID": {
"value": "/subscriptions/azure-test/resourceGroups/rg-
test/providers/provider-test/vm-image/ave-image"
},
"AVESizeInTB": {
"value": "2"
},
"AVEUsername": {
"value": "test"
},
"AVEAuthenticationMode": {
"value": "Password"
},
"AVEUserPwd": {
"value": "S3cure#P@ssW0rd!"
},
"AVESshPublicKey": {
"value": "Input only when SSH Public Key is selected as
the authentication mode."
},
"DDVEName": {
"value": "DDVE-test"
},

Deploying AVE and DDVE from Azure Powershell 29

Installation

"DDVEVirtualMachineSize": {
"value": "Standard_F4"
},
"DDVEDataDiskSizeInTB": {
"value": "1"
},
"DDVEAuthenticationMode": {
"value": "Password"
},
"DDVESysadminPwd": {
"value": ".DdV3#P@ssW0rd%"
},
"DDVESshPublicKey": {
"value": "Input only when SSH Public Key is selected as
the authentication mode."
},
"vnetExistingResourceGroup": {
"value": "rg-test"
},
"vnetName": {
"value": "vnet-test"
},
"vnetSubnetName": {
"value": "subnet-test"
},
"diagnosticsStorageAccountExistingResourceGroup": {
"value": "rg-test"
},
"diagnosticsStorageAccountName": {
"value": "storage-test"
}
}
}
3. Save and close the file.
4. In the Azure Powershell interface, log in and select an appropriate subscription.
5. In the Azure Powershell interface, type the following command on one line:
New-AzureRmResourceGroupDeployment -Name <DeploymentName> -
ResourceGroupName <ResourceGroupName> -TemplateFile
AVE_DDVE_SolutionTemplate.json -TemplateParameterFile
AVE_DDVE_SolutionTemplate_parameters.json
where:
l <DeploymentName> is a unique name for this AVE and DDVE deployment.
l <ResourceGroupName> is a resource group in which to place the new
instances of AVE and DDVE.

Deployment may take 15–30 minutes. Note all of the return values from the
deployment process.

Post-deployment configuration
These steps prepare the deployed AVE for installation of the Avamar software.
Before you begin
Note and record the deployment status, and the AVAMARURL and DDSMURL values
from the deployment task. Access to these URLs requires a secure gateway system,
which is beyond the scope of this installation guide.
Procedure
1. Create a static IP address for the virtual machine by performing the following
substeps:

30 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

a. From the network interface configuration page for the virtual machine, click
IP Configurations.
b. Click the network name.
c. Select Static for the Private IP Address.
2. Obtain the AVE private IPv4 address by performing one of the following
substeps:
a. Use the Azure Portal to obtain the private IPv4 address.
The Microsoft documentation for the Azure Portal provides more
information.

b. Use the Azure CLI to obtain the private IPv4 address by typing the following
command:
az vm list-ip-addresses --name vm-name

c. Record the private IPv4 address for future use. This value is the default
password for AVE.
3. Configure a secure gateway system.
4. Install the AVE.
Installing and configuring the Avamar software on page 33 contains
instructions.

Note

After launching the instance, the AVE initializes and restarts automatically.
During this process, which takes 15–25 minutes, the AVE installs drivers and an
updated kernel. You cannot install the AVE until this process is complete
because the AVE installation package, ave-config, is not available in the
Avamar Installation Manager. SSH is also unavailable during this time.

5. Configure the DDVE instance.

If you cannot access the DDVE instance from the secure gateway via HTTP or
HTTPS, perform the following substeps:

a. SSH to the DDVE instance and log in as the sysadmin user.

b. Type the following command:
adminaccess enable http/https

6. Attach the DDVE system to AVE.

Azure security best practices

Consider the following issues when deploying AVE to an Azure environment, to create
as secure an environment as possible.
Follow the Azure network security best practices
Follow the Azure network security best practices at https://docs.microsoft.com/en-
us/azure/best-practices-network-security to define an Information Security
Management System (ISMS). Build a set of security policies and processes for the
organization to protect the Avamar server and clients in the Azure cloud.

Azure security best practices 31

Installation

Disable the public IP address when launching AVE

Because AVE in the cloud only backs up resources in the same Virtual Private Cloud
(VPC), AVE does not need a public IP address. Isolating AVE from public network
access helps to secure AVE in a cloud environment.
When creating the virtual machine, select None for the public IP address setting to
disable the public IP address for AVE.
Set up an additional secure gateway system for AVE maintenance in the cloud
You can also set up a secure gateway system, with a public IP address, in the same
VPC as AVE and the clients. Perform all operation and maintenance of AVE through
this secure gateway system. Configure the gateway system for high security by, for
example, defining the security group to enable only a must-have level of network
access.
l For Linux gateways, enable only the SSH port, with key-based SSH access, and
the VNC port range. Restrict the permitted original network address (a white-
listed IP address or range is suggested).
l For Window gateways, enable only the RDP port. Restrict the permitted original
network address (a white-listed IP address or range is suggested).
You can install Avamar Administrator on the Secure gateway system. In this case,
configure a security group for the following ports:

Table 10 Inbound ports for Linux gateways

Type Protocol Port range Source

Custom TCP rule TCP 7778-7781 Subnet IPv4 CIDR

HTTPS TCP 443 Subnet IPv4 CIDR

SSH TCP 22 0.0.0.0/0

Table 11 Inbound ports for Windows gateways

Type Protocol Port range Source

Custom TCP rule TCP 7778-7781 Subnet IPv4 CIDR

RDP TCP 3389 0.0.0.0/0

HTTPS TCP 443 Subnet IPv4 CIDR

SSH TCP 22 Subnet IPv4 CIDR

Use only key-based SSH access

Use an SSH public key when launching AVE in Azure. Select SSH public key as the
Authentication type when creating the virtual machine.
Use a security group with custom IP address ranges
In addition to the ports, restrict the source and destination network address ranges in
the inbound/outbound security group. Enable only the necessary ports for both
inbound and outbound network access, as defined in Network security group on page
21.
Timely application of Avamar security patches
Avamar releases quarterly OS security patch roll-ups. Apply these patches to AVE on a
regular basis.

32 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

Installing and configuring the Avamar software

To install Avamar software on a new AVE virtual machine, follow the instructions that
are included in the help file for the AVE installation workflow on the SW Releases
page of the Avamar Installation Manager.
Procedure
1. Open a web browser and log in to Avamar Installation Manager:
The Avamar Administration Guide contains information about the Avamar
Installation Manager.

a. Type the following URL:

https://Avamar-server:7543/avi
where Avamar-server is the IP address or the resolvable hostname of the
Avamar server.

Note

Ensure that the hostname does not contain more than 63 characters.

The Avamar Installation Manager login page appears.

b. Log in as the root user for the Avamar software with the default password.

Note

The default password is either changeme or the private IPv4 address for the
virtual machine, depending on the environment.

c. Click Login.
2. Click SW Releases.
3. Click the ? button for the AVE installation package ave-config to open the help
file for the AVE installation workflow.
4. Click Install next to the AVE installation package ave-config.
5. Monitor the installation progress on the Installation Progress page and
respond to any installation problems:
a. To resolve the problem, take the appropriate action.
b. After resolving the problem, click Call Support.
The Call Support dialog box appears.
c. Click Issue resolved, continuing the installation.
The installation resumes.
d. Repeat these steps for all problems that occur during the installation.

Installing and configuring the Avamar software 33

Installation

Upgrading the Avamar software

To upgrade the Avamar software on an AVE virtual machine, follow the instructions
that are included in the workflow guide for the AVE upgrade workflow package on the
SW Releases page of the Avamar Installation Manager.
Procedure
1. Download the AVE upgrade workflow package for the appropriate version of
AVE.
Download the required software from https://support.emc.com/.
You can also use the Avamar Download Manager or Local Downloader Service
to download the software. The Avamar Administration Guide contains information
about configuring and using the Avamar Download Manager and the Local
Downloader Service.

2. Log in to the Avamar Installation Manager by performing the following substeps:

a. Open a web browser and type the following URL:
https://Avamar-server:7543/avi
where Avamar-server is the IP address or the resolvable hostname of the
Avamar server.

Note

Ensure that the hostname does not contain more than 63 characters.

The Avamar Installation Manager login page appears. The Avamar

Administration Guide contains information about the Avamar Installation
Manager.
b. Log in as the Avamar software root user.
The root user password is typically created with the ave_config workflow
when you install the Avamar software.

c. Click Login.
3. Upload the AVE upgrade workflow package that you downloaded in step 1 on
page 34 by performing the following substeps:
a. Click Repository.
The Repository tab appears.
b. For Package Upload, click Browse and select the package to upload.
Once the package upload completes, it automatically appears in the
Repository table.
4. Click SW Upgrade.
The SW Upgrade tab appears.
5. Click the ? button for the AVE upgrade workflow package (AvamarUpgrade-
version.avp) to open the workflow guide.
6. Click Upgrade.
7. Monitor the upgrade progress on the Installation Progress page and respond
to any problems:

34 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Installation

a. To resolve the problem, take the appropriate action.

b. After resolving the problem, click Call Support.
The Call Support dialog box appears.
c. Click Issue resolved, continuing the installation.
The upgrade resumes.
d. Repeat these substeps for all problems that occur during the upgrade.

Post-installation and post-upgrade tasks

Perform the following tasks after completing the installation or upgrade of the AVE
server.
Restarting the backup scheduler
The pre-upgrade steps included suspending the backup scheduler. Restart the backup
scheduler by typing the following command as the admin user:
dpnctl start sched
Output similar to the following appears:

Identity added: /home/admin/.ssh/dpnid

(/home/admin/.ssh/dpnid)
dpnctl: INFO: Resuming backup scheduler...
dpnctl: INFO: Backup scheduler resumed.

Restarting the maintenance scheduler

The pre-upgrade steps included suspending the maintenance scheduler. Restart the
maintenance scheduler by typing the following command as the admin user:
dpnctl start maint
Output similar to the following appears:

Identity added: /home/admin/.ssh/dpnid (/home/admin/.ssh/dpnid)

dpnctl: INFO: Resuming maintenance windows scheduler...
dpnctl: INFO: maintenance windows scheduler resumed.

Rebooting Avamar proxy clients

If Avamar proxy clients are installed, reboot the proxy clients by typing the following
commands:
su -
mccli mcs reboot-proxy --all=true
exit
Output similar to the following appears:

0,22357,Initiated request to recycle proxy power.

Testing Data Domain integration

If you use AVE with Data Domain, verify the status of the Data Domain integration and
open any necessary service requests with Customer Support when problems occur.
The Avamar and Data Domain System Integration Guide contains information about
replication.

Post-installation and post-upgrade tasks 35

Installation

Generating new certificates with Data Domain systems

When you upgrade an AVE that is connected to a Data Domain system to Avamar
release 7.3 or greater, and session ticket authentication is enabled during upgrade, you
must generate new certificates on the Data Domain system. The Avamar Product
Security Guide contains more information.
Setting the passphrase on Data Domain systems
When you upgrade an AVE that is connected to a Data Domain system to Avamar
release 7.3 or greater, enable a passphrase for the DD Boost user by performing the
following steps:
1. Log in to the Data Domain system.
2. Type the following command at the Data Domain CLI:
system passphrase set
3. When prompted, type a passphrase.

Note

The DD Boost user must have admin rights.

Testing replication
If replication was configured before the AVE upgrade, verify the status of replication
and open any necessary service requests with Customer Support when problems
occur. The Avamar Administration Guide contains information about replication.
Upgrading the Avamar client downloads
The Avamar Client Downloads and Client Manager Installer Upgrades Technical Note,
which is available on Online Support (https://support.emc.com) contains information
about the procedures to upgrade client installation packages.
Installing the server hotfixes and the Avamar platform security patch rollup
Server hotfixes and the Avamar platform security patch rollup are released on a
periodic basis. When available, you should install these hotfixes and the Avamar
platform security patch rollup on new and existing AVE systems.
The Avamar Administration Guide contains information about installing hotfixes, and the
Support KB article https://support.emc.com/kb/335359 provides instructions for
installing the Avamar platform security patch rollup.

36 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
APPENDIX A
Using NAT

If you intend to use the public IP address to back up data to AVE, configuring NAT
allows external clients to cross the network boundary.

l Configuring AVE to use NAT.............................................................................. 38

Using NAT 37
Using NAT

Configuring AVE to use NAT

The following instructions explain how to set up the probe.xml file to enable AVE to
use Network Address Translation (NAT). These instructions assume that AVE has a
unique address (from the Avamar client's perspective), and that you configure the
virtual network to apply transparent one-to-one network address translation.
Some or all Avamar clients can access AVE by using an IP address that undergoes
NAT. To make NAT information known to AVE, the probe.xml file (node resource
database) must contain nat-address elements. After a client makes initial contact
with AVE, Avamar provides a routable address to each client. In the absence of a nat-
address element, Avamar supplies a "real" (untranslated) virtual network interface
address.
The following figure illustrates an example in which AVE uses NAT.
Figure 1 NAT configuration

Procedure
1. Open a command shell and log in to the server as admin.
2. Add a NAT address to probe.xml with the nodedb command:
Example:
nodedb update if --addr=10.6.250.87 --new-nat=INITIAL=TARGET
where both INITIAL and TARGET are the AVE NAT IP address.

Note

AVE is a special case of a single-node server.

The nodedb command updates an existing network interface element in the

probe.xml file with NAT information that corresponds to the example diagram
shown above.

3. If the Avamar storage subsystem is currently stopped, restart it by typing the

following command:
dpnctl start gsan

4. Re-read the probe.xml file by typing the following command:

avmaint networkconfig /usr/local/avamar/var/probe.xml --
avamaronly

38 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide
 Using NAT

5. Register clients by using the avregister (UNIX) or avregister.bat

(Windows) commands, or by using Avamar Administrator.
"Client registration" in the Avamar Administration Guide provides more
information about registering clients.
6. Open /usr/local/avamar/var/mc/server_data/prefs/
mcserver.xml in a plain text editor.
7. Change the property of the external_nonat_addr to contain a hostname that is
resolvable from the client and server sides.
8. Save the change and close the text editor.
9. Restart the MCS and the scheduler by typing the following commands:
dpnctl start mcs

dpnctl start sched

Configuring AVE to use NAT 39

Using NAT

40 Avamar Virtual Edition for Azure 7.5.1 Installation and Upgrade Guide