Docu96425 - Avamar Virtual Edition 19.2 Installation and Upgrade Guide
Docu96425 - Avamar Virtual Edition 19.2 Installation and Upgrade Guide
Version 19.2
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 Technologies, Dell, EMC, 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
Figures 7
Tables 9
Preface 11
Chapter 1 Introduction 15
Overview of Avamar Virtual Edition..............................................16
Supported environments................................................................................... 16
Licensed capacity configurations.......................................................................17
Scaling and resizing AVE....................................................................................17
Environment-specific information......................................................................17
Appropriate environments for AVE.............................................. 18
Maximum change rates......................................................................................18
Preinstallation requirements and best practices........................... 19
System requirements........................................................................................ 19
Virtual disk requirements.................................................................................. 22
Virtual disk configuration best practices........................................................... 23
Software requirements..................................................................................... 24
Verify the DNS configuration............................................................................ 25
Network requirements...................................................................................... 26
NTP server best practices................................................................................ 26
Upgrade requirements and best practices.................................... 27
Other components in the Avamar environment................................................. 27
Stop replication tasks....................................................................................... 28
1 Revision history..................................................................................................................11
2 Typographical conventions................................................................................................ 12
3 Licensed capacity configurations by environment..............................................................17
4 Maximum supported change rates for file server and mixed environments........................ 18
5 Minimum system requirements for AVE on AWS...............................................................20
6 Minimum system requirements for AVE on Azure............................................................. 20
7 Minimum system requirements for AVE on KVM............................................................... 21
8 Minimum system requirements for AVE on VMware.......................................................... 21
9 Virtual disk requirements...................................................................................................22
10 Common AVE software installation requirements..............................................................24
11 Additional environment-specific applications.................................................................... 24
12 Mode options.................................................................................................................... 32
13 Inbound ports for the AWS security group........................................................................59
14 Outbound ports for the AWS security group.....................................................................60
15 Inbound ports for Linux gateways...................................................................................... 71
16 Inbound ports for Windows gateways................................................................................ 71
17 Inbound ports for the Azure network security group.........................................................94
18 Outbound ports for the Azure network security group......................................................95
19 Inbound ports for Linux gateways..................................................................................... 96
20 Inbound ports for Windows gateways............................................................................... 97
21 EC2 instance type selection by AVE instance size........................................................... 129
22 EC2 volume size by DDVE instance size.......................................................................... 129
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
Avamar server that runs as a virtual machine in a variety of environments.
This guide supersedes the following documents:
l Avamar Virtual Edition for VMware Installation and Upgrade Guide
l Avamar Virtual Edition for Microsoft Azure Installation and Upgrade Guide
l Avamar Virtual Edition for Microsoft Hyper-V Installation and Upgrade Guide
l Avamar Virtual Edition for OpenStack KVM Installation and Upgrade Guide
l Avamar Virtual Edition for Amazon Web Services Installation and Upgrade Guide
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 history
Table 1 Revision history
Related documentation
The following publications provide additional information:
l E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome
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
l Avamar and Data Domain System Integration Guide
Typographical conventions
These type style conventions are used in this document.
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
3. Select the product from the list that appears. When you select a product, the Product
Support page loads automatically.
4. (Optional) Add the product to the My Products list by clicking Add to My Saved Products in
the upper right corner of the Product Support page.
Documentation
The Avamar product documentation provides a comprehensive set of feature overview, operational
task, and technical reference information. To supplement the information in product administration
and user guides, review the following documents:
l Release notes provide an overview of new features and known limitations for a release.
l Technical notes provide technical details about specific product features, including step-by-
step tasks, where necessary.
l White papers provide an in-depth technical perspective of a product or products as applied to
critical business issues or requirements.
Knowledgebase
The Knowledgebase contains applicable solutions that you can search for either by solution
number (for example, KB000xxxxxx) or by keyword.
To search the Knowledgebase:
1. Go to https://www.dell.com/support/home/us/en/19.
2. Under the Support tab, click Knowledge Base.
3. Type either the solution number or keywords in the search box. Optionally, you can limit the
search to specific products by typing a product name in the search box and then selecting the
product from the list that appears.
Online communities
Go to Community Network at http://community.EMC.com for peer contacts, conversations, and
content on product support and solutions. Interactively engage online with customers, partners,
and certified professionals for all products.
Live chat
To engage Customer Support by using live interactive chat, click Join Live Chat on the Service
Center panel of the Avamar support page.
Service Requests
For in-depth help from Customer Support, submit a service request by clicking Create Service
Requests on the Service Center panel of the Avamar support page.
Note: To open a service request, you must have a valid support agreement. Contact a sales
representative for details about obtaining a valid support agreement or with questions about an
account.
To review an open service request, click the Service Center link on the Service Center panel, and
then click View and manage service requests.
Enhancing support
It is recommended to enable ConnectEMC and Email Home on all Avamar systems:
l ConnectEMC automatically generates service requests for high priority events.
l Email Home sends configuration, capacity, and general system information to Customer
Support.
Supported environments
Supported environments include:
l VMware ESXi 6.0, 6.5, or 6.7
l Microsoft Azure
l Windows, using Hyper-V Manager
l KVM
l Amazon Web Services (AWS) cloud
See the E-LAB Navigator at https://elabnavigator.emc.com/eln/elnhome for specific information
about supported environments and software versions.
Note: For Avamar 19.2 and later, this guide does not contain installation instructions for
OpenStack KVM.
Capacity AVE on VMware AVE on Azure AVE on Hyper-V AVE on KVM AVE on AWS
configuration
Environment-specific information
AVE on VMware
AVE on VMware supports backup of both physical and virtual clients. For physical clients,
install the Avamar client software on each client. For virtual clients, there are two options for
backups.
Virtual clients can be backed up through:
l Guest OS backups (requires installing the Avamar client software on each virtual
machine).
l Host-based backups (requires a proxy server).
AVE on Azure
AVE on Azure is certified to support Azure Government Cloud (US), which provides the ability
for U.S. residents (government agencies and customers) to move sensitive workloads into the
cloud. Azure Government Cloud (US) addresses specific regulatory and compliance
requirements. The Azure Government Cloud (US) User Guide provides information about, and
details on, setting up an Azure Government Cloud (US) account.
AVE on Azure supports replication in the cloud and can be used to replicate on-premises
physical and virtual Avamar servers, 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 on AWS
AVE on AWS is certified to support AWS GovCloud (US), which provides the ability for U.S.
residents (government agencies and customers) to move sensitive workloads into the cloud.
AWS GovCloud (US) addresses specific regulatory and compliance requirements. The AWS
GovCloud (US) User Guide provides information about, and details on, setting up an AWS
GovCloud (US) account.
AVE on AWS supports replication in the cloud and can be used to replicate on-premises
physical and virtual Avamar servers, including non-AWS types of AVEs. However, because of
security considerations, replication should be performed by using a VPN, VPC, or a direct
connect link.
Table 4 Maximum supported change rates for file server and mixed environments
0.5 TB AVE Less than 2 GB per day Less than 5 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.
Environment-specific notes
AVE on AWS
When you create the AWS instance for AVE, select the correct instance type for the change
rates.
AVE on AWS
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.
l The SSH interface is no longer accessible via username/password authentication. Instead,
authentication requires SSH keys. This restriction applies even if you install AVE without
an SSH key.
System requirements
The following topics list the minimum system requirements for an AVE instance in each virtual
environment.
Consult the E-lab Navigator for supported versions of each virtual environment.
Increase CPU and memory resources on an existing AVE instance on page 116 provides steps to
increase resource allocations on a running instance of AVE.
NOTICE The Avamar server must maintain time synchronization for correct operation. NTP
server best practices on page 26 provides more information.
Processors Minimum two 2 GHz Minimum two 2 GHz Minimum two 2 GHz
processors processors processors
Memory 6 GB 8 GB 16 GB
Processors Minimum four 2 GHz Minimum four 2 GHz Minimum four 2 GHz
processors processors processors
Memory 36 GB 48 GB 96 GB
Processors Minimum two 2 GHz Minimum two 2 GHz Minimum two 2 GHz
processors processors processors
Memory 6 GB 6 GB 14 GB
Processors Minimum four 2 GHz Minimum four 2 GHz Minimum four 2 GHz
processors processors processors
Memory 28 GB 48 GB 96 GB
Processors Minimum two 2 GHz Minimum two 2 GHz Minimum two 2 GHz
processors processors processors
Memory 6 GB 8 GB 16 GB
a. Figures include both the primary bootable disk, and required amounts of storage
Memory 36 GB 48 GB 96 GB
Processors Minimum two 2 GHz Minimum two 2 GHz Minimum two 2 GHz
processors processors processors
Memory 6 GB 8 GB 16 GB
Memory 36 GB 48 GB 96 GB
The task to prepare the virtual machine instance contains steps to ensure that all of the storage
partitions are the same size.
Environment-specific notes
AVE on VMware
The AVE .ova installation creates three 250 GB storage partitions along with the OS disk and
so requires approximately 935 GB of free disk space at installation.
However, the AVE .ovf installation does not create storage partitions during installation and
therefore requires only enough disk space for the OS disk at installation. You can
subsequently create storage partitions on other datastores.
AVE on KVM
AVE requires approximately 935 GB of free disk space at installation.
AVE on AWS
Because SSD volumes have better performance than other volume types, Dell EMC
recommends SSD for all volumes. However, SSD volumes incur a larger cost to the customer.
Customers should balance performance and budget when selecting the volume type.
After the initial installation, if you configure the virtual disks for the Thick Provision Eager Zeroed,
you will get better initial performance because the first write to the disk will require fewer
operations.
Note: See the VMware documentation for information on converting Lazy zeroed virtual disks
to Eager zeroed virtual disks. Converting a disk from Thick Provisioned Lazy Zeroed to Thick
Provisioned Eager Zeroed is so time consuming that uses a significant number of storage I/O
processes.
A virtual machine running AVE aggressively uses disk I/O and is almost never idle. VMware's
recommendations for appropriate resources for high-performance database virtual machines are
generally applicable to an AVE virtual machine.
A virtual machine running AVE aggressively uses disk I/O and is almost never idle. Microsoft's
recommendations for appropriate resources for high-performance database virtual machines are
generally applicable to an AVE virtual machine. In particular, a storage pool that is allocated from a
group of dedicated physical disks in a RAID 1 (mirror) or RAID 10 (combines RAID 0 with RAID 1)
configuration provides the best performance.
Software requirements
Before you install AVE, ensure that you have the software that is listed in the following tables.
All environments require the software listed in the following table:
Requirement Description
Applications l PuTTYa
l WinSCPa
Other up-to-date SSH and SCP clients are also acceptable.
The following table lists any additional requirements for software that is specific to each
installation environment:
a. The AWS CLI must run on a separate system from the AVE instance.
Support for application databases in standalone configuration only in AVE on Azure and AWS
Backup and recovery of the following applications are supported with AVE on Azure and AWS.
However, these applications are supported in standalone configuration only. Clustered
configurations of application databases are not supported with AVE on Azure or AWS.
l SQL
l Exchange
l SharePoint
l Lotus
l DB2
l Sybase
l SAP
l Oracle
Environment Command
AVE on VMware nslookup AVE_IP_address DNS_Server_IP_address
AVE on Hyper-V
Environment Command
AVE on VMware nslookup AVE_FQDN DNS_Server_IP_address
AVE on Hyper-V
Environment Command
AVE on VMware nslookup FQDN_of_vCenter DNS_Server_IP_address
The command returns the IP address of the vCenter Server or the Hyper-V Server.
5. If the commands return the proper information, close the command prompt. If the
commands do not return proper information, resolve the DNS configuration before you
install AVE.
Network requirements
Before you install AVE, gather the following information:
l Hostnames and IP addresses for the AVE virtual machine and the DNS server
Note:
AVE supports only alphanumeric characters (a-z, A-Z, and 0–9) and hyphens (-) in
hostnames. Hyphens are only allowed if surrounded by other characters.
Some workflow inputs may not accept hostnames or FQDNs with hyphens. In this case,
replace the name with the corresponding IP address to complete these workflow inputs.
l Gateway, netmask, and domain of the AVE virtual machine
l Firewall openings, if applicable
The Avamar Product Security Guide provides client-server data port usage and firewall
requirements.
Note: AVE on KVM supports only fixed IP addresses. NAT (floating IP addresses) is not
supported.
During network configuration, you can type one or more optional NTP servers in either IPv4 or
IPv6 format or in hostname format.
The following chapters describe instructions for installing AVE in different local virtual
environments:
The following topics describe how to install an AVE virtual machine in a Microsoft Hyper-V
environment:
5. Launch Server Manager, select Hyper-V, then right-click the Hyper-V host and select
Hyper-V Manager.
6. Expand Hyper-V Manager, on the left side of the dialog box select the Hyper-V host. On
the right side under Actions, click Import Virtual Machine…
7. From Locate Folder click Browse… and select the folder where you extracted the
compressed file. Click Select Folder and then click Next.
8. From Select Virtual Machine highlight the Virtual Machine, and click Next.
9. From Choose Import Type, select Copy the virtual machine (create a new unique ID)
and click Next.
10. From Choose Destination, accept the default settings and click Next.
11. From Choose Folders to Store Virtual Hard Disks, accept the default settings and click
Next.
12. From Summary, review the selections and if correct, click Finish.
13. Once the system has finished importing the virtual machine, right-click the virtual machine
and select Settings…
14. In the Settings window, under Hardware, choose SCSI Controller. Select Hard Drive and
click Add.
15. In the Hard Drive window, select Virtual hard disk: and click Browse.
16. In the Open window, select the File Name and click Open.
17. Repeat steps 14 to 16 for each VHD associated with the AVE virtual machine size. Click
Apply.
18. In the Settings window, under Hardware, select Add Hardware and for the type choose
Network Adapter Click Add.
19. Select the new Network Adapter. The Network Adapter settings are available on the right
side of the dialog box. Under Virtual switch, select the network connection's virtual switch
from the drop-down menu. If you need the virtual machines connection to be tagged with a
VLAN ID, under the VLAN ID section, select the checkbox Enable virtual LAN
identification and assign the VLAN ID identifier. Click Apply.
20. In the Processor window, update the number of virtual CPUs based on the size of the AVE
license and click Apply.
l For 0.5 TB AVE, specify 2 CPUs.
l For 1 TB AVE, specify 2 CPUs.
l For 2 TB AVE, specify 2 CPUs.
l For 4 TB AVE, specify 4 CPUs.
l For 8 TB AVE, specify 8 CPUs.
l For 16 TB AVE, specify 16 CPUs.
21. In the Memory window, update the memory size which is based on the size of the AVE
license and click Apply click OK.
l For 0.5 TB AVE, specify 6144 MB.
l For 1 TB AVE, specify 8192 MB.
l For 2 TB AVE, specify 16384 MB.
l For 4 TB AVE, specify 36864 MB.
l For 8 TB AVE, specify 49152 MB.
l For 16 TB AVE, specify 98304 MB.
22. Power on the virtual machine. The system will reboot once after initial power on.
8. At the main menu, review the configuration and press 5 to save the changes and exit.
9. Shut down the AVE virtual machine.
10. Right-click the AVE virtual machine in Hyper-V manager and select Settings.
11. Select Network Adapter > Advanced Features from the left pane.
12. Select Static from the list of MAC Address options.
Hyper-V populates a default MAC address in the six fields.
13. Click OK.
Hyper-V saves the settings.
14. Power on the AVE virtual machine.
c. Click Login.
The Avamar Installation Manager opens to the Package Selection page.
2. In the menu bar, click SW Releases, and then select the ave-config workflow package from
the Package List.
3. Click the ? button next to the ave-config package.
The Avamar Virtual Edition Configuration Workflow Guide opens.
4. Review the workflow guide for information about the required and optional user input fields.
After you click Install, you are no longer able to access the workflow guide.
5. Click Install next to the AVE installation package ave-config.
The Installation Setup page displays.
6. On the Installation Setup page, provide the required information in the user input fields for
each tab, and then click Continue.
Note:
If you do not specify a Data Domain system when you create an 8 TB or 16 TB AVE that
is intended to be used with Data Domain, you must make additional configuration
changes to the Avamar subsystem settings before you can configure the Data Domain
system later.
These changes improve system performance. The Avamar Administration Guide provides
more information about system requirements for Data Domain integration.
The following topics describe how to install an AVE virtual machine in a VMware environment:
l Installation.............................................................................................................................38
l OVA deployment................................................................................................................... 38
l OVF deployment....................................................................................................................42
l Install and configure the Avamar software.............................................................................47
Installation
Deployment in a VMware environment follows one of two possible paths, depending on whether
you choose to deploy from the OVA or OVF template. Select the template that best matches your
environment and needs.
Both paths follow the same steps to install and configure the Avamar software after deployment.
OVA deployment
The AVE OVA template deploys three 250 GB virtual disks that match the 0.5 TB configuration.
These virtual disks can be reused for the 1 TB configuration. Deploying other configurations
requires you to remove these virtual disks and create new disks of the appropriate size.
The following tasks provide information about deploying from the OVA template:
1. Prepare a virtual machine (OVA) on page 38
2. Create additional virtual hard disks (OVA) on page 41
3. Install and configure the Avamar software on page 47
8. Verify that the template details are correct and click Next.
The End User License Agreement page opens.
9. Click Accept to accept the End User License Agreement and click Next.
The Name and Location page opens.
10. Type in the AVE name, select the inventory location, and then click Next.
The Storage page opens.
11. Select the storage for AVE and click Next.
The Disk Format page opens.
12. Select Thick Provision Lazy Zeroed format and click Next.
AVE does not support thin provisioning.
Note:
For the Hostname FQDN field, the hostname can only include alphanumeric characters
(a-z, A-Z, and 0-9), hyphen (-), and period(.).
Hyphen and periods are only permitted if surrounded by other characters. Some
workflow inputs may not accept hostnames or FQDNs with hyphens. In this case,
replace the name with the corresponding IP address to complete these workflow inputs.
a. Right-click the AVE virtual machine and then select Edit Settings.
b. Select hard disk 2 from the table.
c. Select Remove.
d. Click OK to confirm drive removal.
5. Click Next.
6. For Disk Size, type 250 GB, 1000 GB, or 2000 GB as required.
7. For Disk Provisioning, select Thick Provision Lazy Zeroed format.
Thin provisioning is not supported with AVE. If you select Thick Provision Eager Zeroed
during the installation, the installation could take several hours. Time-out errors could also
occur.
Virtual disk configuration best practices on page 23 provides information about disk
formatting after you complete the installation process.
8. For Location, select either Store with virtual machine or Specify a datastore.
9. Click Next.
10. For Mode, select Independent. Use the default setting for Persistent.
11. Click Next.
12. Verify the configuration and select Finish.
After you finish
Verify that all of the storage partitions are the same size before continuing.
OVF deployment
The AVE OVF template deploys no virtual disks. This procedure contains steps to create virtual
disks of the appropriate size and quantity. OVF deployment also requires additional network
configuration.
The following tasks provide information about deploying from the OVF template:
1. Prepare a virtual machine (OVF) on page 42
2. Create additional virtual hard disks (OVF) on page 45
3. Configure the network settings (OVF) on page 46
4. Install and configure the Avamar software on page 47
9. Verify that the template details are correct and click Next.
The End User License Agreement page opens.
10. Click Accept to accept the End User License Agreement and click Next.
The Name and Location page opens.
11. Type in the AVE name, select the inventory location, and then click Next.
The Storage page opens.
12. Select the storage for AVE and click Next.
The Disk Format page opens.
13. Select Thick Provision Lazy Zeroed format and click Next.
AVE does not support thin provisioning.
The Network Mapping page opens.
Note:
Networking settings are not available for OVF deployment. Instead, configure
networking with the avenetconfig command after the deployment completes.
Configure the network settings (OVF) on page 46 provides more information.
15. Confirm that the deployment settings are correct and then click Finish.
The installation may take several minutes. The wizard displays a Deployment Completed
Successfully message when the installation completes.
16. Click Close to close the deployment dialog box.
17. Supply the networking properties information by using the avenetconfig script, as
described in Configure the network settings (OVF) on page 46.
18. Right-click the AVE virtual machine and then select Edit Settings.
The Virtual Machine Properties window opens.
19. On the Hardware tab, select Memory, and then set Memory Size, based on the AVE
capacity configuration.
System requirements on page 19 provides more information.
20. On the Hardware tab, select CPUs, and then change the number of virtual CPUs, based on
the AVE capacity configuration.
System requirements on page 19 provides more information.
21. On the Hardware tab, select Network adapter 1, select Network Connection (Network
label), and then select the correct network.
22. Complete the steps in Create additional virtual hard disks (OVF) on page 45 to create
virtual disks, as appropriate for the capacity configuration.
23. Finish the virtual machine configuration by completing the following steps:
a. Click OK.
b. In the Recent Tasks status area at the bottom of the screen, observe the hard disk
creation progress.
When the virtual machine reconfiguration completes, the wizard displays a Completed
message.
24. To start the AVE virtual machine, right-click the virtual machine and select Power > Power
On.
25. Open the Virtual Console and monitor the installation progress.
An insufficient licensing message at this point might indicate either a shortage of ESXi
server licenses or an inability to connect to a license server. Resolve this problem with the
network administrator.
26. On the Summary tab, verify that the status for VMware Tools changes to Running,
Unmanaged, or out-of-date.
8. For Location, select either Store with virtual machine or Specify a datastore.
9. Click Next.
10. For Mode, select Independent. Use the default setting for Persistent.
11. Click Next.
12. Verify the configuration and select Finish.
c. Click Login.
The Avamar Installation Manager opens to the Package Selection page.
2. In the menu bar, click SW Releases, and then select the ave-config workflow package from
the Package List.
3. Click the ? button next to the ave-config package.
The Avamar Virtual Edition Configuration Workflow Guide opens.
4. Review the workflow guide for information about the required and optional user input fields.
After you click Install, you are no longer able to access the workflow guide.
5. Click Install next to the AVE installation package ave-config.
The Installation Setup page displays.
6. On the Installation Setup page, provide the required information in the user input fields for
each tab, and then click Continue.
Note:
If you do not specify a Data Domain system when you create an 8 TB or 16 TB AVE that
is intended to be used with Data Domain, you must make additional configuration
changes to the Avamar subsystem settings before you can configure the Data Domain
system later.
These changes improve system performance. The Avamar Administration Guide provides
more information about system requirements for Data Domain integration.
The following topics describe how to install an AVE virtual machine in a KVM environment:
l Install and configure AVE on KVM using the KVM Virtual Machine Manager......................... 50
l Install and configure AVE on KVM using the command line.................................................... 51
l Configure the network settings............................................................................................. 52
4. Create the primary disk for the operating system by typing the following command on one
line:
qemu-img create -f qcow2 -o backing_file=KVM_IMAGE_FILE_NAME
PRIMARY_DISK_NAME
5. Create the disks used for storage by typing the following commands for each disk used for
storage. For example:
qemu-img create -f qcow2 FIRST_DISK_NAME FIRST_DISK_SIZE
qemu-img create -f qcow2 SECOND_DISK_NAME SECOND_DISK_SIZE
qemu-img create -f qcow2 THIRD_DISK_NAME THIRD_DISK_SIZE
Note: Between 3-6 data disks can be used for storage. The section Virtual disk
requirements on page 22 provides more information.
6. Launch the KVM Virtual Machine Manager wizard to create a new AVE instance.
7. On the Create a new virtual machine (step 1 of 4) page, for Choose how you would like
to install the operating system, select Import existing disk image, and then click
Forward.
8. Import the primary disk, and then click Forward.
9. For the memory requirements, specify 6144MB memory + 2 CPUs, and then click Forward.
10. On the Show virtual hardware details pane of the Basic Details window, click Add
Hardware.
The Add New Virtual Hardware dialog opens.
11. Add new storage disks one at a time.
When adding the storage disks, click Select or create custom storage, and then click
Manage... to select the primary disk.
12. In the left navigation pane of the Basic Details window, select the NIC.
13. From the Virtual Network Interface fields, configure the NIC to ensure that you can access
AVE from outside of the KVM host.
14. Start the AVE VM and log in using the root user, with the default password changeme.
15. Configure the network by typing:
/usr/local/avamar/bin/avenetconfig
4. Create the primary disk for the operating system by typing the following command on one
line:
qemu-img create -f qcow2 -o backing_file=KVM_IMAGE_FILE_NAME
PRIMARY_DISK_NAME
5. Create the disks used for storage by typing the following commands for each disk used for
storage. For example:
qemu-img create -f qcow2 FIRST_DISK_NAME FIRST_DISK_SIZE
qemu-img create -f qcow2 SECOND_DISK_NAME SECOND_DISK_SIZE
qemu-img create -f qcow2 THIRD_DISK_NAME THIRD_DISK_SIZE
Note: Between 3-6 data disks can be used for storage. The section Virtual disk
requirements on page 22 provides more information.
6. Open a command prompt, and type the following to create a new AVE instance:
virt-install \
--name="VM-NAME" \
--import \
--disk path="FULL_PATH_OF_PRIMARY_DISK",bus="virtio",format=qcow2 \
--disk path="FULL_PATH_OF_FIRST_DISK",bus="virtio",format="qcow2" \
--disk path="FULL_PATH_OF_SECOND_DISK",bus="virtio",format="qcow2" \
--disk path="FULL_PATH_OF_THIRD_DISK",bus="virtio",format="qcow2" \
--memory 6144 \
--vcpus 2 \
--network type=YOUR_NETWORK_ENVIRONMENT,source=BRIDGE,source_mode=bridge \
--os-type=linux \
--os-variant=sles12 \
--noreboot
where:
l YOUR_NETWORK_ENVIRONMENT is a configuration appropriate to your network
environment, such as direct.
l BRIDGE is the virtual bridge (NIC) on the KVM server host.
Note that Avamar enables DHCP mode by default, but you can assign a static IP to the
virtual machine in the DHCP server.
7. Start the AVE VM and log in using the root user, with the default password changeme.
8. Configure the network by typing:
/usr/local/avamar/bin/avenetconfig
Configure the network settings on page 52 provides more information.
The following chapters describe instructions for installing AVE in different cloud virtual
environments:
The following topics describe how to install an AVE virtual machine in an Amazon Web Services
(AWS) environment:
l Installation.............................................................................................................................58
l Prerequisites......................................................................................................................... 58
l Install AVE from the AWS Marketplace................................................................................. 62
l Install AVE/DDVE from the AWS Marketplace with CloudFormation.................................... 65
l AWS security best practices................................................................................................. 70
l Install and configure the Avamar software............................................................................. 71
Installation
Avamar provides multiple deployment methods for virtual machines on AWS. This chapter includes
the following preferred installation methods:
l Installing AVE from the AVE Amazon Machine Image (AMI) image in the AWS marketplace.
l Installing AVE and Data Domain Virtual Edition (DDVE) together with AWS CloudFormation.
Alternate AWS Installation Methods on page 117 contains more information about installation
methods that are not covered here, but which provide additional flexibility or options. Most
alternate installation methods are variations on the methods in this chapter.
Prerequisites
Before you select an installation method, complete the following items that apply to all installation
methods:
Procedure
1. (Optional) Install the AWS CLI tools.
Some alternate installation methods use the AWS CLI tools.
2. Open the AWS EC2 Console and select the region where you want to run the instance.
3. Create or select a virtual private cloud (VPC) to contain the AVE (and DDVE, where
applicable) instance.
The AWS documentation provides more information. Place the AVE and DDVE instances in
the same VPC as the workloads that they protect.
Note the name of the VPC, as well as the associated subnet and availability zone for later
use.
4. If you are deploying DDVE, create a VPC endpoint for connectivity to Amazon S3 storage.
The Data Domain Virtual Edition Installation and Administration Guide provides more
information.
5. If you are deploying DDVE, create an S3 bucket and an identity and access management
(IAM) role.
The Data Domain Virtual Edition Installation and Administration Guide provides more
information.
Note the name of the S3 bucket and IAM role for later use.
Outbound ports
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, when you create a security group, AWS adds a predefined rule that allows all
outbound traffic. Remove this default rule when you create a security group.
i. Click Associate.
The EC2 console displays a status notification.
j. Click Close.
25. Obtain the AVE private IPv4 address by performing one of the following substeps:
If you configured an elastic IP address, you may already have this value.
a. Use the AWS EC2 web console to obtain the private IPv4 address.
The AWS documentation provides more information.
b. Use the AWS CLI to obtain the private IPv4 address by typing the following command:
aws ec2 describe-instances --instance-ids instance | grep
PrivateIpAddress
Record the private IPv4 address for later use. This value is the default password for AVE.
8. For Subnet, select the ID of the subnet that you created within the VPC.
9. For Availability Zone, select the availability zone that you chose for the VPC.
10. For SSH Location, type an IP address range from which AVE and DDVE should permit SSH
access, in the format 10.2.3.4/24.
Since AVE and DDVE receive private IP addresses, supply an IP address range within the
private network to which the secure gateway provides access. Addresses outside this range
are not permitted SSH access.
11. For Key Pair, select the name of the SSH keypair that you created for AVE and DDVE.
2. For AVE Volume Type, select the volume type for the AVE instance: either gp2 or st1.
The AWS documentation provides more information on the different volume types:
3. For AVE Common Password and AVE Common Password Confirmation, type a password
for the AVE OS admin and root user accounts, and for the Avamar software.
The Avamar Product Security Guide provides information about password complexity rules.
4. For System Time Zone Name, select the POSIX time zone name.
5. For Email Sender Address, type the email address from which to send ConnectEMC
notifications and alerts.
6. For Email Server, type the hostname or IP address of the email server from which
ConnectEMC should send emails.
This is also the email server that sends EmailHome messages for high priority events.
7. For Site Name, type a description for the AVE location.
For example:
l Company name
l Company’s site ID
l Company’s address
8. For Dell EMC Site ID/CSI Party ID, type the assigned site ID or CSI party ID (maximum 32
characters).
You can find this ID on the Service Center at http://support.emc.com/servicecenter by
clicking Administration > View and manage company information. An incorrect site ID
may lead to delays when you contact Customer Support.
If you cannot determine your site ID, leave the field blank. In this case, AVE does not send
dial-home requests to Dell EMC.
9. For Company Name, type the name of the company that owns the AVE instance.
10. For Company Contact Name, type the name of the administrator managing the AVE
instance.
11. For Company Contact Phone Number, type the phone number of the administrator
managing the AVE instance.
12. For Company Contact Email Address, type the email address of the administrator
managing the AVE instance.
2. For IAM Role for S3 Access, type the name of the IAM role that you created during the
prerequisites for access to S3 storage.
3. For S3 Bucket Name, type the name of the S3 bucket that you created during the
prerequisites.
4. For DDBoost Login Name, type the login name for the DDBoost user.
This name can be a new or existing account. Valid characters include letters, numbers,
hyphen (-), and underscore (_).
5. For DDVE Common Password and DDVE Common Password Confirmation, type a
password for the DDVE admin accounts.
The Data Domain Virtual Edition Installation and Administration Guide provides information
about password complexity rules.
6. For SNMP Community String, type the SNMP community string that is used to monitor
the Data Domain systems.
Blank spaces, colon (:), semicolon (;), dollar-sign ($), single quotes ('), and backquotes (`)
are not allowed.
7. Click Next.
The Create stack page opens to the Options tab.
i. Click Associate.
The EC2 console displays a status notification.
j. Click Close.
6. Obtain the AVE private IPv4 address by performing one of the following substeps:
If you configured an elastic IP address, you may already have this value.
a. Use the AWS EC2 web console to obtain the private IPv4 address.
The AWS documentation provides more information.
b. Use the AWS CLI to obtain the private IPv4 address by typing the following command:
aws ec2 describe-instances --instance-ids instance | grep
PrivateIpAddress
When configuration completes successfully, the following message appears in the log
file:
Completed ave-config
In these tables, the term 'private subnet' refers to the virtual network that contains AVE and
related virtual machines.
Key-based SSH access is required
Use an SSH public key when launching AVE in AWS. Prerequisites on page 58 contains information
about creating a key pair and selecting it when launching the instance. If you do not select a key
pair when launching an instance, you cannot log in to the SSH interface with username/password
authentication.
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 Security group settings on page 59.
Timely application of Avamar security patches
Avamar releases quarterly OS security patch roll-ups. Apply these patches to AVE on a regular
basis.
Enable terminal protection
Accidentally terminating or deleting AVE could result in a disaster scenario with potential data loss.
Therefore, it is a best practice to select the Enable terminal protection option when configuring
the AVE instance.
where Avamar-server is the IP address or the resolvable hostname of the Avamar server.
c. Click Login.
The Avamar Installation Manager opens to the Package Selection page.
2. In the menu bar, click SW Releases, and then select the ave-config workflow package from
the Package List.
3. Click the ? button next to the ave-config package.
The Avamar Virtual Edition Configuration Workflow Guide opens.
4. Review the workflow guide for information about the required and optional user input fields.
After you click Install, you are no longer able to access the workflow guide.
5. Click Install next to the AVE installation package ave-config.
The Installation Setup page displays.
6. On the Installation Setup page, provide the required information in the user input fields for
each tab, and then click Continue.
The Installation Progress page displays.
7. On the Installation Progress page, monitor the installation 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 substeps for all problems that occur during the installation.
The following topics describe how to install an AVE virtual machine in a Microsoft Azure
environment:
l Installation............................................................................................................................. 74
l Deploying from the Azure Marketplace..................................................................................74
l Deploy AVE and DDVE with an Azure solution template........................................................ 83
l Network security group.........................................................................................................94
l Azure security best practices................................................................................................ 96
l Install and configure the Avamar software.............................................................................97
Installation
Avamar provides multiple deployment methods for AVE virtual machines on Microsoft Azure.
Select a method from the following list:
l By deploying AVE, or AVE and DDVE together, from the Azure Marketplace.
Deploying from the Azure Marketplace on page 74 provides more information.
l By deploying AVE and DDVE together via the Azure solution template.
Deploy AVE and DDVE with an Azure solution template on page 83 provides more information,
and provides instructions for the following options:
n Azure Resource Manager
n Azure Powershell
n Azure CLI
Option Description
None For environments where the protected clients reside in the Azure
cloud and that require no public Internet access.
Allow selected For environments where the protected clients may reside outside of
ports the Azure cloud, or that require access from the public Internet.
a. If you selected Allow selected ports, check values from the Select inbound ports
drop-down.
Network security group on page 94 contains information about required inbound/
outbound rules for AVE.
10. Click Next : Disks.
Results
The Create a virtual machine wizard moves to the Disks tab.
5. From the Configure network security group drop-down, select an existing security group
or click Create new.
Creating a network security group is beyond the scope of this publication. The Azure portal
documentation provides more information.
Ensure that the selected network security group contains all of the required inbound/
outbound rules. Network security group on page 94 provides more information.
5. Create a static IP address for the AVE VM by performing the following substeps:
a. From the network interface configuration page for the AVE VM, click IP configurations.
b. Click the network name.
c. Select Static for the Private IP address assignment.
d. Specify a private IP address or accept the default private IP address from Azure.
e. Record the private IPv4 address for future use. This value is the default password for
AVE.
f. Click Save.
6. Install the Avamar software.
Install and configure the Avamar software on page 97 contains instructions.
Note: After launching the instance, the AVE initializes and restarts automatically. During
this process, which takes 15 to 25 minutes, the AVE installs drivers and an updated
kernel. You cannot install the Avamar software until this process is complete because
the installation package, ave-config, is not available in the Avamar Installation
Manager. SSH is also unavailable during this time.
2. From the Resource group drop-down, select an existing resource group or click Create
new.
Create a resource group on page 84 and the Azure portal documentation provide more
information.
3. From the Location drop-down, select an available location in which to deploy AVE and
DDVE.
4. Click OK.
Results
The Create Avamar and Data Domain Virtual Edition wizard moves to the Infrastructure
Configuration tab.
c. Click OK to continue.
The Subnets pane closes.
5. Click Diagnostics storage account.
The Choose storage account pane opens.
6. Select an existing storage account or click Create new.
To create a storage account by using the wizard, complete the following substeps:
3. Using the information in System requirements on page 19, select a value for AVE VM Size.
This field offers a selection of values that correspond to the sizes that are listed in the
resource requirement tables.
4. From the AVE Capacity drop-down, select the correct capacity configuration.
5. In the Admin User Name field, type the name for the administrator.
You can use this username to ssh into the AVE instance. The values admin and root are
not permitted.
6. For Admin Authentication Type, select Password or SSH public key.
a. If you selected Password, complete the Password and Confirm password fields.
b. If you selected SSH public key, complete the SSH public key field.
The installation process creates an OS account with this username and password.
7. In the AVE Common password and Confirm AVE Common password fields, type a
password for the OS admin and root accounts, and for the Avamar software.
8. From the AVE Time Zone drop-down, select the applicable time zone.
9. (Optional) In the Email sender address field, type the email address from which notification
emails are sent to Dell EMC.
10. (Optional) In the Email server field, type the hostname or IP address of the email server
that ConnectEMC uses to send email to Dell EMC. This is also the email server that sends
EmailHome messages for high priority events.
11. (Optional) In the Site name field, type a name for the site where the Avamar server is
physically located.
12. (Optional) In the Dell EMC Site ID/CSI Party ID field, type the assigned site ID or CSI party
ID (maximum 32 characters).
3. Using the information from the DDVE system requirements, select a value for DDVE VM
Size.
Select a size that meets or exceeds the DDVE system requirements for the chosen capacity
configuration.
4. In the DDVE VM Size field, select an option from the options available in the list.
5. In the DDVE Capacity (TB) field, select a storage capacity from the options available in the
list.
6. For Sysadmin Authentication type, select Password or SSH public key.
a. If you selected Password, complete the Password and Confirm password fields.
b. If you selected SSH public key, complete the SSH public key field.
7. In the DDBoost user name field, type the login name for the DDBoost user.
8. In the DDVE common password and Confirm password fields, type a password for the
DDVE passphrase, DDBoost user account, and sysadmin account (if DDVE authentication is
key-based).
9. In the SNMP community string field, type the SNMP community string used to monitor
the DDVE. Blank spaces are not allowed.
10. In the Resource ID of the blob storage account field, type the resource ID for the Azure
blob storage account.
The account type must be blob storage. If you do not have an Azure blob storage account,
create one before continuing.
To obtain the resource ID from the Azure portal, click Storage accounts, select the storage
account from the list, and then click Properties. A valid resource ID follows this format:
/subscriptions/<subscription GUID>/resourceGroups/<resource group name>/
providers/Microsoft.Storage/storageAccounts/<storage account name>
11. In the Container name field, type the name of the empty container that will store data for
DDVE backups. The container must be empty or the configuration fails. If you do not have
an empty container, create one before continuing.
12. Click OK.
Results
The Create Avamar and Data Domain Virtual Edition wizard moves to the Summary tab.
After the configuration completes, the log file contains the following lines:
Completed ave-config
Config AVE successsfully
8. Create a static IP address for the AVE and DDVE virtual machines:
a. From the Azure portal, select the virtual machine, and then select Networking.
b. Select the network interface that is assigned to the virtual machine.
The Azure portal opens the network interface overview.
c. Click IP Configurations.
The Azure portal lists the available IP configurations.
d. Click the IP configuration that is currently assigned to the virtual machine.
The IP configuration window opens.
e. In the Private IP address settings section, for the Assignment field, select Static.
f. Verify the current setting or type a new static IP address for the virtual machine.
g. Click Save.
Repeat this step for both the AVE and DDVE virtual machines.
The Create storage account wizard moves to the Review + create tab.
12. Wait for the Azure portal to validate the storage account configuration.
Review and correct any errors.
13. Click Create.
The Azure portal starts to deploy the storage account. The deployment process can take
several minutes to complete.
14. Observe the output from the deployment process and respond to any problems.
The Azure portal displays a notification when the deployment completes.
After you finish
Record the name of the new storage account.
Create a container
Create a container for solution template deployment by performing the following steps:
Procedure
1. From the Favorites list, click Storage accounts.
2. Select the new storage account.
3. From the navigation pane for the new storage account, click Blobs.
4. Click + Container.
5. In the Name field, type a name for the container.
6. For Public access level, select Private (no anonymous access).
Results
The Blobs pane lists the new container.
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.
Transfer the AVE virtual appliance file as a page blob.
Procedure
1. Select the new container.
The Azure portal opens the contents of the container.
2. Click Upload.
3. Select the AVE virtual appliance file that you downloaded and decompressed earlier.
4. Click Advanced.
5. For Blob type, select Page blob.
6. Ensure that Upload .vhd files as page blobs is checked.
7. Click Upload.
After you finish
The upload progresses in the background. You can continue to complete tasks in the Azure portal
while uploading the AVE virtual appliance file.
Create an image
Create an image for solution template deployment by performing the following steps:
Procedure
1. From the Azure portal navigation pane, click + Create a resource.
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 System requirements on page 19, and the
automatic creation of virtual disks, as detailed in Virtual disk requirements on page 22.
AVE Username
Required. Type the name of a new user with administrative privileges for AVE. Cannot be
root or admin.
DDVE Name
Required. Type the hostname to assign to DDVE. Limited to 10 characters, special characters
are prohibited.
Vnet Name
Required. Type the name of the new virtual network.
12. Review the terms and conditions, and then check I agree to the terms and conditions
stated above.
13. Click Purchase.
Deployment may take 15–30 minutes. Note all of the return values from the deployment
process.
"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.
},
"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"
},
"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 CLI, log in and select an appropriate subscription.
5. In the Azure CLI, type the following command on one line:
az group deployment create --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.
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 Avamar software.
Install and configure the Avamar software on page 97 contains instructions.
Note: After launching the instance, the AVE initializes and restarts automatically. During
this process, which takes 15 to 25 minutes, the AVE installs drivers and an updated
kernel. You cannot install the Avamar software until this process is complete because
the installation package, ave-config, is not available in the Avamar Installation
Manager. SSH is also unavailable during this time.
SSH TCP 22
SSH TCP 22
SMTP TCP 25
Table 18 Outbound ports for the Azure network security group (continued)
c. Click Login.
The Avamar Installation Manager opens to the Package Selection page.
2. In the menu bar, click SW Releases, and then select the ave-config workflow package from
the Package List.
The following chapters describe instructions that are common to all virtual environments.
100 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
CHAPTER 7
Completing post-installation activities
Review the following activities after you install the Avamar software and complete any that apply:
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 101
Completing post-installation activities
102 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Completing post-installation activities
Procedure
1. In Avamar Administrator, click the Server launcher link.
The Server window is displayed.
2. Click the Server Management tab.
3. Select a Data Domain system.
4. Click Actions > Edit Data Domain System.
The Edit Data Domain System window opens.
5. Click the System tab and then select Use system as target for Avamar Checkpoint
Backups.
6. Click OK.
7. Click Close.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 103
Completing post-installation activities
Procedure
1. Open a command shell and log in by using one of the following methods:
l For a single-node server, log in to the server as admin.
l For a multi-node server, log in to the utility node as admin.
2. Load the admin OpenSSH key by typing:
ssh-agent bash
ssh-add ~admin/.ssh/admin_key
10. Verify that all services are up and running by typing the following:
dpnctl status
12. If there are no errors or issues that are seen in the flush command, log out of the
command line.
13. (Optional) To verify that the changes were successful, perform a test backup:
a. Log in to the Avamar Administrator GUI.
b. Perform an on-demand backup using any client.
Ensure that you specify Avamar as the backend storage.
admin@avamarave1:/usr/local/avamar/var/mc/server_data/prefs/>: grep
"dd_only_mode" mcserver.xml
104 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Completing post-installation activities
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 105
Completing post-installation activities
106 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
CHAPTER 8
Upgrading AVE
The following topics describe how to upgrade AVE in any supported virtual environment:
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 107
Upgrading AVE
Upgrade AVE
The Avamar Installation Manager and upgrade workflow package enable customers to upgrade the
Avamar software on AVE virtual machines. This chapter provides information about how to use the
upgrade workflow, and on additional tasks to complete after you upgrade the Avamar software.
As of Avamar 19.1, to reduce total downtime, the upgrade workflow supports parallel upgrades to
any attached physical and virtual Data Domain systems. Since the Data Domain system may be
unavailable when the workflow takes an Avamar checkpoint, performing a parallel upgrade requires
the administrator to manually create checkpoints before and after the upgrade workflow.
Administrators must also select an additional user input to skip the automatic checkpoint.
Validating the checkpoints is not necessary.
The Avamar Administration Guide provides information about checkpoint creation through the
Avamar Administrator or the AUI.
108 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Upgrading AVE
where Avamar-server is the IP address or the resolvable hostname of the Avamar server.
c. Click Login.
The Avamar Installation Manager opens to the Package Selection page.
4. Upload the AVE upgrade workflow package 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 upload completes, the workflow package automatically appears in the
Repository table.
5. Click SW Upgrade.
The SW Upgrade tab appears.
6. Click the ? button next to the AVE upgrade workflow package (AvamarUpgrade-
version.avp).
The workflow guide opens.
7. Review the workflow guide for information about the required and optional user input fields.
After you click Upgrade, you are no longer able to access the workflow guide.
8. Click Upgrade next to the AVE upgrade workflow package.
The Installation Setup page displays.
9. For parallel upgrades, select the Skip automatic checkpoint user input.
10. On the Installation Progress page, monitor the upgrade and respond to any 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 upgrade resumes.
d. Repeat these substeps for all problems that occur during the upgrade.
11. After the upgrade completes, install the following optional, but recommended, workflow
packages:
l Avamar platform OS security patch rollup
(AvPlatformOsRollup_<year>R<r>.avp)
l Upgrade client downloads (UpgradeClientDownloads-<version>.avp)
l Upgrade client plugin catalog (UpgradeClientPluginCatalog-<version>.avp)
The Avamar Administration Guide provides more information.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 109
Upgrading AVE
Post-upgrade activities
Review the following activities after you upgrade the Avamar software and complete any that
apply:
l If the swap partition is enabled, then the console displays information similar to the
following:
Filename Type Size Used Priority
/dev/xvda5 partition 15999996 0 -1
Note the swap partition name. In this example, the swap partition is /dev/xvda5.
5. Using a Linux text editor, such as vi, open /etc/fstab:
vi /etc/fstab
10. Check the swap partition status by typing the following command:
110 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Upgrading AVE
swapon -s
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 111
Upgrading AVE
Procedure
1. Log in to the Data Domain system.
2. Type the following command at the Data Domain CLI:
system passphrase set
Test replication
If you perform an AVE upgrade and replication was configured before the 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.
112 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Upgrading AVE
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 113
Upgrading AVE
114 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
CHAPTER 9
Additional activities
The following topics contain additional reference material for AVE servers:
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 115
Additional activities
If the Avamar subsystem is running, the command returns the following output:
dpnctl: INFO: gsan status: up
7. If the Avamar subsystem is not running, start the Avamar subsystem by typing the following
command:
dpnctl start all
The AVE server attempts to start all of the Avamar services. This operation may take some
time.
116 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
APPENDIX
Alternate AWS Installation Methods
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 117
Overview of alternate AWS installation methods
This appendix provides instructions to install AVE virtual machines or combined AVE/DDVE virtual
appliances on AWS by methods that are not covered in the Installation chapter. Use this appendix
for environments where those methods are not available or are otherwise undesirable.
Perform the Prerequisites on page 58 before you start the procedures in this appendix.
118 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
12. From the Security Group Settings, select the security group that you created during the
prerequisite task.
13. From the Key Pair Settings drop-down, select the key pair that you created during the
prerequisite task.
14. Click Launch.
EC2 starts the deployment process.
15. Record the ID for the new AVE instance for later use.
16. Use the EC2 console to monitor the deployment progress and respond to any problems.
The EC2 console displays a notification when the deployment completes.
c. For Size, type the size that corresponds to the storage volumes for the selected
capacity configuration.
Virtual disk requirements on page 22 provides information about required disk sizes.
d. From the Availability Zone drop-down, select a zone within the current region.
e. Click Add tag.
f. For Key, type Name.
g. For Value, type a unique name for the data disk so that you can identify it later.
h. Click Create Volume.
The EC2 console displays a status notification.
i. Click Close.
The EC2 console returns to the list of volumes.
Repeat this step for all required volumes. Virtual disk requirements on page 22 provides
information about the number of required disks and sizes.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 119
Note: Verify that all of the storage volumes are identical before continuing.
4. For each new volume, attach the volume to the instance by performing the following
substeps:
a. Right-click the volume and then select Attach Volume.
The Attach Volume dialog box opens.
b. Type the name or ID of the new AVE instance.
c. Verify the default device mount point that AWS proposes.
d. Click Attach.
5. From the navigation pane, select Instances > Instances.
The EC2 console displays a list of available instances.
6. Start the new instance.
Wait for the instance to start before continuing.
7. (Optional) Configure an elastic IP address for the instance by completing the following
substeps:
a. From the navigation pane, select Network & Security > Elastic IPs.
The EC2 console displays a list of available elastic IP addresses.
b. If there are no available elastic IP addresses, click Allocate new address.
c. For IPv4 address pool, select an available option that corresponds to your network
environment.
d. Click Allocate.
The EC2 console displays a status notification.
e. Click Close.
The EC2 console returns to the list of elastic IP addresses.
f. Right-click an available elastic IP address and select Associate address.
The Associate address window opens.
g. From the Instance drop-down, select the new AVE instance.
h. From the Private IP drop-down, select an available private IP address.
Note the private IP address for later use. This value is the default password for AVE.
i. Click Associate.
The EC2 console displays a status notification.
j. Click Close.
8. Obtain the AVE private IPv4 address by performing one of the following substeps:
If you configured an elastic IP address, you may already have this value.
a. Use the AWS EC2 web console to obtain the private IPv4 address.
The AWS documentation provides more information.
b. Use the AWS CLI to obtain the private IPv4 address by typing the following command:
aws ec2 describe-instances --instance-ids instance | grep
PrivateIpAddress
120 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Record the private IPv4 address for later use. This value is the default password for AVE.
9. Install the AVE.
Install and configure the Avamar software on page 71 contains instructions.
Note: After launching the instance, the AVE initializes and reboots automatically. During
this process, which takes 10 to 20 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.
4. Create or select a user with a minimum of Programmatic access and AWS Management
Console access.
Download a .csv file and save the Access key ID and Secret access key values. These
values are very important.
NOTICE You must have the Access key ID and Secret access key available later in this
procedure. When creating a user, save these values locally by selecting Download csv.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 121
e. Click Upload.
f. Click Add files and select the virtual appliance file that you downloaded in a previous
step.
6. Import the virtual appliance file from the S3 bucket to an Amazon Machine Image (AMI) by
performing the following substeps:
a. From the command line, type the following command:
aws ec2 import-image --architecture x86_64 --platform Linux --region
REGION --disk-containers "[{ \"Format\" : \"vmdk\", \"UserBucket\" :
{\"S3Bucket\" : \"BUCKET_NAME\", \"S3Key\": \"VMDK_FILENAME\"}}]"
where:
l REGION is the region where you want to run the instance. For example, us-west-1.
l BUCKET_NAME is the name of the S3 bucket.
l VMDK_FILENAME is the name of the virtual appliance file that you downloaded in a
previous step.
Output similar to the following appears:
{
"Status": "active",
"Platform": "Linux",
"Architecture": "x86_64",
"SnapshotDetails": [
{
"UserBucket": {
"S3Bucket": "<BUCKET_NAME>",
"S3Key": "<VMDK_FILENAME>"
},
"DiskImageSize": 0.0,
"Format": "VMDK"
}
],
"Progress": "2",
"StatusMessage": "pending",
"ImportTaskId": "import-ami-12mbx7hu"
}
b. Use the ImportTaskID to monitor the task status by typing the following command on
one line:
aws ec2 describe-import-image-tasks --import-task-ids IMPORT_TASK_ID --
region REGION
where:
l IMPORT_TASK_ID is the ImportTaskID from the previous command.
l REGION is the region where you want to run the instance. For example, us-west-1.
Output similar to the following appears:
{
"ImportImageTasks": [
{
"Status": "completed",
"LicenseType": "BYOL",
"ImageId": "ami-2bbd994b",
"Platform": "Linux",
"Architecture": "x86_64",
"SnapshotDetails": [
{
"UserBucket": {
"S3Bucket": "<BUCKET_NAME>",
"S3Key": "<VMDK_FILENAME>"
},
122 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
"SnapshotId": "snap-0b8fdb6bc5ace3d61",
"DiskImageSize": 5740812288.0,
"DeviceName": "/dev/sda1",
"Format": "VMDK"
}
],
"ImportTaskId": "import-ami-ffmbx7hu"
}
]
}
When the import-image task completes, the Status field changes to completed
and ImageId provides the AMI ID.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 123
Repeat this step for all required volumes. Virtual disk requirements on page 22 provides
information about the number of required disks and sizes.
Note: Verify that all of the storage partitions are the same size before continuing.
16. Review the summary of the AVE configuration, including the estimated pricing and the
terms.
17. Click Launch.
The Select an existing key pair or create a new key pair dialog box opens.
18. Select Choose an existing key pair from the drop-down.
19. From the Select a key pair drop-down, select the key pair that you created during the
prerequisite task.
20. Check the box to acknowledge the warning regarding access to the private key file.
The wizard enables the Launch instances button.
21. Click Launch instances.
The Launch instance wizard starts the deployment process.
22. Use the EC2 console to monitor the deployment progress and respond to any problems.
The EC2 console displays a notification when the deployment completes.
23. (Optional) Configure an elastic IP address for the instance by completing the following
substeps:
a. From the navigation pane, select Network & Security > Elastic IPs.
The EC2 console displays a list of available elastic IP addresses.
b. If there are no available elastic IP addresses, click Allocate new address.
c. For IPv4 address pool, select an available option that corresponds to your network
environment.
d. Click Allocate.
The EC2 console displays a status notification.
e. Click Close.
The EC2 console returns to the list of elastic IP addresses.
124 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
f. Right-click an available elastic IP address and select Associate address.
The Associate address window opens.
g. From the Instance drop-down, select the new AVE instance.
h. From the Private IP drop-down, select an available private IP address.
Note the private IP address for later use. This value is the default password for AVE.
i. Click Associate.
The EC2 console displays a status notification.
j. Click Close.
24. Obtain the AVE private IPv4 address by performing one of the following substeps:
If you configured an elastic IP address, you may already have this value.
a. Use the AWS EC2 web console to obtain the private IPv4 address.
The AWS documentation provides more information.
b. Use the AWS CLI to obtain the private IPv4 address by typing the following command:
aws ec2 describe-instances --instance-ids instance | grep
PrivateIpAddress
Record the private IPv4 address for later use. This value is the default password for AVE.
25. Install the AVE.
Install and configure the Avamar software on page 71 contains instructions.
Note: After launching the instance, the AVE initializes and reboots automatically. During
this process, which takes 10 to 20 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.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 125
n Deploy AVE/DDVE via CloudFormation from the AWS console (alternate) on page 130.
n Deploy AVE/DDVE via CloudFormation from the AWS CLI on page 131.
Locate the AWS Marketplace AVE and DDVE machine image IDs
Locate and subscribe to the AVE and DDVE AMI images in the AWS Marketplace, and then locate
the AMI IDs for later use.
Procedure
1. Create a virtual private cloud (VPC) for AVE and DDVE.
The AWS documentation provides additional information.
2. Create a subnet for the VPC and specify an availability zone.
The AWS documentation provides additional information.
3. Open the AWS Console Identity and Access Management (IAM) page.
4. Create or select a group. The group must have a minimum of the following permissions:
l AmazonEC2FullAccess
l AmazonS3FullAccess
5. Create or select a user with a minimum of Programmatic access and AWS Management
Console access.
Download a .csv file and save the Access key ID and Secret access key values. These
values are very important.
NOTICE You must have the Access key ID and Secret access key available later in this
procedure. When creating a user, save these values locally by selecting Download csv.
126 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
17. Record the DDVE AMI ID for later use.
After you finish
Use the recorded AMI IDs to complete the CloudFormation template.
4. Create or select a user with a minimum of Programmatic access and AWS Management
Console access.
Download a .csv file and save the Access key ID and Secret access key values. These
values are very important.
NOTICE You must have the Access key ID and Secret access key available later in this
procedure. When creating a user, save these values locally by selecting Download csv.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 127
l VMDK_FILENAME is the name of the virtual appliance file that you downloaded in a
previous step.
Output similar to the following appears:
{
"Status": "active",
"Platform": "Linux",
"Architecture": "x86_64",
"SnapshotDetails": [
{
"UserBucket": {
"S3Bucket": "<BUCKET_NAME>",
"S3Key": "<VMDK_FILENAME>"
},
"DiskImageSize": 0.0,
"Format": "VMDK"
}
],
"Progress": "2",
"StatusMessage": "pending",
"ImportTaskId": "import-ami-12mbx7hu"
}
b. Use the ImportTaskID to monitor the task status by typing the following command on
one line:
aws ec2 describe-import-image-tasks --import-task-ids IMPORT_TASK_ID --
region REGION
where:
l IMPORT_TASK_ID is the ImportTaskID from the previous command.
l REGION is the region where you want to run the instance. For example, us-west-1.
Output similar to the following appears:
{
"ImportImageTasks": [
{
"Status": "completed",
"LicenseType": "BYOL",
"ImageId": "ami-2bbd994b",
"Platform": "Linux",
"Architecture": "x86_64",
"SnapshotDetails": [
{
"UserBucket": {
"S3Bucket": "<BUCKET_NAME>",
"S3Key": "<VMDK_FILENAME>"
},
"SnapshotId": "snap-0b8fdb6bc5ace3d61",
"DiskImageSize": 5740812288.0,
"DeviceName": "/dev/sda1",
"Format": "VMDK"
}
],
"ImportTaskId": "import-ami-ffmbx7hu"
}
]
}
When the import-image task completes, the Status field changes to completed
and ImageId provides the AMI ID.
128 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
8. Create a subnet for the VPC and specify an availability zone.
The AWS documentation provides additional information.
2TB m4.xlarge
4TB m4.2xlarge
8TB r4.2xlarge
16TB r4.4xlarge
1 to 10 TB 1 TB
11 to 20 TB 2 TB
21 to 30 TB 3 TB
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 129
Table 22 EC2 volume size by DDVE instance size (continued)
31 to 40 TB 4 TB
41 to 50 TB 5 TB
51 to 60 TB 6 TB
61 to 70 TB 7 TB
71 to 80 TB 8 TB
81 to 90 TB 9 TB
91 to 96 TB 10 TB
The 0.5 TB value is only for use with the evaluation license. Do not use this value for any other
installations.
VPC ID (VpcId)
Required. Select the ID of the new VPC that you created for AVE and DDVE.
Subnet ID (SubnetId)
Required. Select the ID of the subnet that you created within the new VPC. AVE and DDVE are
both deployed in this subnet.
Availability Zone (AvailabilityZoneName)
Required. Select the availability zone that you chose for the new VPC.
Key Pair Name (KeyName)
Required. Select the name of the new SSH keypair that you created for AVE and DDVE.
130 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
Some fields are preconfigured. CloudFormation template parameters on page 129 provides
additional information on parameter values.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 131
"ParameterValue": "1TB"
},
{
"ParameterKey": "VpcId",
"ParameterValue": "vpc-abcdef03"
},
{
"ParameterKey": "SubnetId",
"ParameterValue": "subnet-abcdef04"
},
{
"ParameterKey": "AvailabilityZoneName",
"ParameterValue": "us-west-2a"
},
{
"ParameterKey": "KeyName",
"ParameterValue": "AVE_DDVE_Keypair"
}
]
3. Save and close the file.
4. In the AWS CLI, type the following command on one line:
aws cloudformation create-stack --stack-name <StackName> --template-body
file://AVE_DDVE_CloudFormation.json --parameters file://
AVE_DDVE_CloudFormation_parameters.json
where <StackName> is a unique name for this AVE and DDVE stack.
Note: You can also store the JSON files in an AWS S3 bucket and supply the URL of
each file. The AWS documentation provides additional information.
Deployment may take 15–30 minutes. The CloudFormation console describes the progress
of the stack creation process. Note all of the outputs from the stack creation process.
After you finish
Complete post-deployment configuration on page 132.
132 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide
e. Click Close.
The EC2 console returns to the list of elastic IP addresses.
f. Right-click an available elastic IP address and select Associate address.
The Associate address window opens.
g. From the Instance drop-down, select the new AVE instance.
h. From the Private IP drop-down, select an available private IP address.
Note the private IP address for later use. This value is the default password for AVE.
i. Click Associate.
The EC2 console displays a status notification.
j. Click Close.
2. Obtain the AVE private IPv4 address by performing one of the following substeps:
If you configured an elastic IP address, you may already have this value.
a. Use the AWS EC2 web console to obtain the private IPv4 address.
The AWS documentation provides more information.
b. Use the AWS CLI to obtain the private IPv4 address by typing the following command:
aws ec2 describe-instances --instance-ids instance | grep
PrivateIpAddress
Record the private IPv4 address for later use. This value is the default password for AVE.
3. Configure a secure gateway system.
4. Configure the AVE instance.
Install and configure the Avamar software on page 71 contains instructions.
Note: After launching the instance, the AVE initializes and reboots automatically. During
this process, which takes 10–20 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.
Dell EMC Avamar Virtual Edition Installation and Upgrade Guide 133
134 Dell EMC Avamar Virtual Edition Installation and Upgrade Guide