300 013-365 avamar-virtualedition6.1installationguide

EMC CONFIDENTIAL

EMC® Avamar® Virtual Edition 6.1

Installation GuideP/N 300-013-365REV 05

EMC Avamar Virtual Edition 6.1 Installation Guide

EMC CONFIDENTIALEMC CONFIDENTIAL

2

Copyright © 2001- 2012 EMC Corporation. All rights reserved. Published in the USA.

Published October, 2012

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

The information in this publication is provided as is. EMC Corporation makes no representations or warranties of any kind with respect to the information in this publication, and specifically disclaims implied warranties of merchantability or fitness for a particular purpose. Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.

EMC2, EMC, and the EMC logo are registered trademarks or trademarks of EMC Corporation in the United States and other countries. All other trademarks used herein are the property of their respective owners.

For the most up-to-date regulatory document for your product line, go to the technical documentation and advisories section on the EMC online support website.

EMC CONFIDENTIAL

CONTENTS

Preface

Chapter 1 Introduction

Overview of Avamar Virtual Edition.............................................................. 10 Appropriate environments for AVE............................................................... 10 Pre-sales performance analysis ................................................................... 12

Chapter 2 Installation

System requirements .................................................................................. 14 Preinstallation requirements ....................................................................... 14

Preinstallation DNS configuration.......................................................... 14AVE disk configuration .......................................................................... 15Additional requirements........................................................................ 15Best practices ....................................................................................... 16

Installation ................................................................................................. 17Installation roadmap............................................................................. 17Preparing the virtual machine................................................................ 17Running ave-part.pl............................................................................... 20Configuring network settings................................................................. 21Installing AvInstaller ............................................................................. 23Installing and configuring Avamar software ........................................... 24Running ave-post.sh ............................................................................. 27Installing server software patches ......................................................... 27

Viewing installation history information ...................................................... 30

Chapter 3 Post-Installation Configuration

Task 1: Obtain and install a server license................................................... 32License installation road map ............................................................... 32Generating a license key information file............................................... 33Generating a permanent license key file ................................................ 34Installing and activating the license ...................................................... 37Installing the software without a license key ......................................... 38

Task 2: Set up replication............................................................................ 38 Task 3: Change Avamar passwords.............................................................. 38 Task 4: Product registration......................................................................... 38

Product registration for EMC personnel ................................................. 38Product registration for partners............................................................ 41

Task 5: Add a custom security notification to web login pages..................... 41 Task 6: Configure ConnectEMC after the installation .................................... 41

EMC Avamar Virtual Edition 6.1 Installation Guide 3

Contents

EMC CONFIDENTIAL

Appendix A Benchmark Testing

Running benchmark testing......................................................................... 44 Manually ending benchmark testing............................................................ 45 Analyzing benchmark results ...................................................................... 45

Read and write test results .................................................................... 46Seek test results ................................................................................... 47

Benchmark removal .................................................................................... 48 Benchmark failure....................................................................................... 48

Glossary

4 EMC Avamar Virtual Edition 6.1 Installation Guide

EMC CONFIDENTIAL

PREFACE

As part of an effort to improve its product lines, EMC periodically releases revisions of its software and hardware. Therefore, some functions 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 your EMC representative if a product does not function properly or does not function as described in this document.

This document was accurate at publication time. New versions of this document might be released on the EMC online support website. Check the EMC online support website to ensure that you are using the latest version of this document.

PurposeThis document describes how to install Avamar Virtual Edition (AVE).

AudienceThis document is intended for EMC Professional Services employees who will install AVE.

Revision history

The following table presents the revision history of this document.

Related documentationThe following EMC publications provide additional information:

◆ EMC Avamar Release Notes

◆ EMC Avamar Administration Guide

◆ EMC Avamar Operational Best Practices

◆ EMC Avamar Product Security Guide

◆ EMC Avamar Backup Clients User Guide

Table 1 Revision history

Revision Date Description

05 October 25, 2012 For release 6.1 Service Pack 1, added support for VMware 5.1.

04 August 31, 2012 Corrected missing graphics.

03 July 31, 2012 Updated “Where to get help” on page 7 in the Preface.

A02 June 15, 2012 Fixed typos.

A01 April 25, 2012 Initial release of Avamar 6.1.


Preface

EMC CONFIDENTIAL

Conventions used in this documentEMC uses the following conventions for special notices:

DANGER indicates a hazardous situation which, if not avoided, will result in death or serious injury.

WARNING indicates a hazardous situation which, if not avoided, could result in death or serious injury.

CAUTION, used with the safety alert symbol, indicates a hazardous situation which, if not avoided, could result in minor or moderate injury.

NOTICE is used to address practices not related to personal injury.

IMPORTANT

An important notice contains information essential to software or hardware operation.

Typographical conventions

EMC uses the following type style conventions in this document:

Normal Used in running (nonprocedural) text for:• Names of interface elements, such as names of windows, dialog boxes,

buttons, fields, and menus• Names of resources, attributes, pools, Boolean expressions, buttons,

DQL statements, keywords, clauses, environment variables, functions, and utilities

• URLs, pathnames, filenames, directory names, computer names, links, groups, service keys, file systems, and notifications

Bold Used in running (nonprocedural) text for names of commands, daemons, options, programs, processes, services, applications, utilities, kernels, notifications, system calls, and man pages

Used in procedures for:• Names of interface elements, such as names of windows, dialog boxes,

buttons, fields, and menus• What the user specifically selects, clicks, presses, or types

Italic Used in all text (including procedures) for:• Full titles of publications referenced in text• Emphasis, for example, a new term• Variables

Courier Used for:• System output, such as an error message or script• URLs, complete paths, filenames, prompts, and syntax when shown

outside of running text

Courier bold Used for specific user input, such as commands


Preface

EMC CONFIDENTIAL

Where to get helpThe Avamar support page provides access to licensing information, product documentation, advisories, and downloads, as well as how-to and troubleshooting information. This information may enable you to resolve a product issue before you contact EMC Customer Service.

To access the Avamar support page:

1. Go to https://support.EMC.com/products.

2. Type a product name in the Find a Product box.

3. Select the product from the list that appears.

4. Click the arrow next to the Find a Product box.

5. (Optional) Add the product to the My Products list by clicking Add to my products in the top right corner of the Support by Product page.

Documentation

The Avamar product documentation provides a comprehensive set of feature overview, operational task, and technical reference information. Review the following documents in addition to product administration and user guides:

◆ Release notes provide an overview of new features and known limitations for a release.

◆ Technical notes provide technical details about specific product features, including step-by-step tasks, where necessary.

◆ White papers provide an in-depth technical perspective of a product or products as applied to critical business issues or requirements.

Knowledgebase

The EMC Knowledgebase contains applicable solutions that you can search for either by solution number (for example, esgxxxxxx) or by keyword.

To search the EMC Knowledgebase:

1. Click the Search link at the top of the page.

2. Type either the solution number or keywords in the search box.

3. (Optional) Limit the search to specific products by typing a product name in the Scope by product box and then selecting the product from the list that appears.

4. Select Knowledgebase from the Scope by resource list.

Courier italic Used in procedures for:• Variables on the command line• User input variables

< > Angle brackets enclose parameter or variable values supplied by the user

[ ] 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 omitted from the example


https://support.emc.com/products

Preface

EMC CONFIDENTIAL

5. (Optional) Specify advanced options by clicking Advanced options and specifying values in the available fields.

6. Click the search button.

Live chat

To engage EMC Customer Service 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 EMC Customer Service, 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 your EMC sales representative for details about obtaining a valid support agreement or with questions about your 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.

Facilitating support

EMC recommends that you enable ConnectEMC and Email Home on all Avamar systems:

◆ ConnectEMC automatically generates service requests for high priority events.

◆ Email Home emails configuration, capacity, and general system information to EMC Customer Service.

Your commentsYour suggestions help us to continue to improve the accuracy, organization, and overall quality of the user publications. Send your opinions of this document to:

[email protected]

Please include the following information:

◆ Product name and version

◆ Document name, part number, and revision (for example, 01)

◆ Page numbers

◆ Other details that will help us address the documentation issue


mailto:[email protected]

EMC CONFIDENTIAL

CHAPTER 1Introduction

This chapter includes the following sections:

◆ Overview of Avamar Virtual Edition.......................................................................... 10◆ Appropriate environments for AVE........................................................................... 10◆ Pre-sales performance analysis ............................................................................... 12

Introduction 9

Introduction

EMC CONFIDENTIAL

Overview of Avamar Virtual EditionEMC® 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 VMware® ESX/ESXi 4.1 or ESXi 5.0/5.1 environment. It integrates the latest version of Avamar software with SUSE Linux as a VMware virtual machine.

AVE is similar to single-node Avamar offerings on physical machines in the following ways:

◆ Runs autonomously as a target for all Avamar client backups

◆ Performs replication to a physical Avamar system or another AVE

AVE is available in three configurations: 0.5 TB, 1 TB, and 2 TB licensed capacity. It 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 AVEs and dividing backups among them. Or you can replicate your data to another Avamar server, delete the smaller virtual machine, create a larger virtual machine, and replicate your data back to the larger virtual machine.

AVE supports backup of physical and virtual clients:

◆ For physical clients, install Avamar client software on each client

◆ Virtual clients can be backed up through guest OS backups (requires installing Avamar client software on each virtual machine) or through host based backups (requires a proxy server)

See the EMC Avamar Compatibility and Interoperability Matrix on the EMC online support web site at http://Powerlink.EMC.com for a complete list of supported ESX/ESXi Server/AVE configuration scenarios.

Appropriate environments for AVEThe following factors have the most direct impact on the long-term reliability, availability and supportability of the AVE virtual machine:

◆ I/O performance capability of the AVE storage subsystem

◆ Amount of data added daily to the AVE virtual machine (change rate)

◆ Capacity utilized within the AVE virtual machine

Specifications in this section and “AVE disk configuration” on page 15 describe minimum or maximum requirements for these factors. AVE generally performs better when I/O performance is higher, and change rate and utilized capacity are lower. To maximize the capacity that can be utilized within the AVE virtual machine, the daily change rate of the data being protected by AVE 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 will be used to protect, file server or mixed environment. File server environment includes file system data and mixed environments include file system data and structured data (for example, database data).


Introduction

EMC CONFIDENTIAL

The following table describes the maximum change rates supported by AVE for file server and mixed environments.

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

Configuration File server data Mixed data

0.5 TB AVE Less than 2 GB per dayFor example, this change rate corresponds to 650 GB of 100% file server data capacity or 0.3% daily change rate. See note that follows.

Less than 5 GB per dayFor example, this change rate corresponds to 500 GB or less than 20% Microsoft Exchange or SQL Server database data and greater than 80% file server data capacity. That is 3% daily change rate for Exchange and SQL Server data, 0.3% for file server data or 1% overall. See note that follows.

1 TB AVE Less than 4 GB per dayFor example, this change rate corresponds to 1.3 TB of 100% file server data capacity or 0.3% daily change rate. See note that follows.

Less than 10 GB per dayFor example, this change rate corresponds to 1.0 TB or less than 20% Microsoft Exchange or SQL Server database data and greater than 80% file server data capacity. That is 3% daily change rate for Exchange and SQL Server data, 0.3% for file server data or 1% overall. See note that follows.

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

Actual results depend on retention policy and actual data change rate. If the daily change rate is greater than 5 GB per day for a 0.5 TB configuration, 10 GB per day for a 1 TB configuration or 20 GB for a 2 TB configuration, deployment of a single or multi-node Avamar Data Store is required.

Appropriate environments for AVE 11

Introduction

EMC CONFIDENTIAL

Pre-sales performance analysisPre-sales performance analysis for AVE is required. It is performed by EMC-trained personnel. Server hardware and the virtual environment must meet resource capability benchmarks according to results from the AVE Performance Assurance Tool (PAT). This tool also simulates the load imposed on the ESX/ESXi Server so that the customer can gauge the potential impact on the targeted ESX/ESXi Server. After the PAT is complete, the instructions contain information on how to analyze the data collected and determine if the ESX/ESXi Server is a good candidate for AVE.

The AVE PAT must be run for a minimum of 24 hours prior to sale. For presales purposes, download the PAT tool and its associated checksum file with the following FTP commands: ftp://[email protected]/PAT-3.0/PAT-3.0.zip ftp://[email protected]/PAT-3.0/PAT-3.0.zip.md5sum Use the checksum file to verify the PAT file was properly downloaded.

Previous versions of AVE also required running the Benchmark Test prior to installation. If the PAT completes successfully with acceptable load levels, the Benchmark Test is not required. If you experience problems during installation and suspect it is bandwidth related, “Benchmark Testing” on page 43 is documented for troubleshooting purposes.


EMC CONFIDENTIAL

CHAPTER 2Installation


◆ System requirements .............................................................................................. 14◆ Preinstallation requirements ................................................................................... 14◆ Installation ............................................................................................................. 17◆ Viewing installation history information .................................................................. 30

Installation 13

Installation

EMC CONFIDENTIAL

System requirements Avamar Virtual Edition (AVE) is supported on VMware ESX/ESXi 4.1 and ESXi 5.0/5.1.

The following table lists the minimum requirements for AVE.

Table 3 Minimum requirements for AVE

0.5 TB AVE 1 TB AVE 2 TB AVE

Processors dedicated to AVE

Minimum two 2 GHz processors available to AVE at all times



Physical memory dedicated to AVE

6 GB 8 GB 16 GB

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

Network connection 1 GbE connection 1 GbE connection 1 GbE connection

Preinstallation requirementsPrior to installing AVE, the following requirements must be met:

◆ “Preinstallation DNS configuration” on page 14

◆ “AVE disk configuration” on page 15

◆ “Additional requirements” on page 15

“Best practices” on page 16 provides guidance on disk configuration.

Preinstallation DNS configuration

Verify that the IP address you intend to deploy the AVE to already has a reverse and forward DNS name assigned to it. Proper DNS configuration is important. Failure to have DNS set up properly can cause many runtime or configuration issues.

To confirm that DNS is configured properly:

1. Open a command prompt and type:

nslookup <AVE_IP_address> <IP_address_of_DNS_Server>

The nslookup command will return the FQDN for AVE.

2. Type the following command:

nslookup <AVE_FQDN> <IP_address_of_DNS_Server>

The nslookup command will return the IP address for AVE.

3. If the nslookup commands returned the proper information, close the command prompt, if not resolve the DNS configuration prior to AVE installation.


Installation

EMC CONFIDENTIAL

AVE disk configuration

Prior to AVE installation, the disks should be partitioned as follows:

0.5 TB AVE is installed into four partitions:

◆ One operating system partition (100 GB)

◆ Three storage partitions (250 GB each)

1 TB AVE is installed into seven partitions:


◆ Six storage partitions (250 GB each)

2 TB AVE is installed into 13 partitions:


◆ 12 storage partitions (250 GB each)

1 GB is defined here as 230 bytes = 10243 bytes.

Additional requirements

Before installation, obtain the items listed in the following table.

Table 4 Additional installation requirements

Requirement Description

Applications PuTTY, WinSCP and VMware vSphere Client

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

Licensing data Customer Number (Customer ID), Reference ID (Asset Reference ID)

Customer-supplied information

Hostnames and IP addresses for:• AVE virtual machine• DNS server• SMTP serverGateway, netmask and domain of the AVE virtual machineFirewall openings (if appropriate)Email address for ConnectEMC

The EMC Avamar Product Security Guide provides basic client-server data port usage and firewall requirements.

Preinstallation requirements 15

Installation

EMC CONFIDENTIAL

Best practices

ESX/ESXi supports multiple disk formats. For AVE virtual machines, storage used to host the virtual disk should be configured as thick provisioned with eager zeroing. These and other related terms are described as follows:

◆ Thick provisioning — A thick disk has all space allocated when it is created. It has optimal I/O latencies during usage but may be a security issue as it may contain stale data as it exists on the physical media at creation.

◆ Thin provisioning — Space is allocated and zeroed on demand as opposed to upon creation. There is a higher I/O penalty during the first write to an unwritten file block, but the same performance as thick and eager zeroed on subsequent writes.

◆ Eager zeroed — An eager zeroed thick disk has all space allocated and zeroed out when it is created. It has a longer creation time, but optimal performance and better security.

◆ Lazy zeroed — Zeroes out the block on first write, but has the same performance as thick and eager zeroed on subsequent writes.

By default, in ESX 4.x, disks created on NFS storage use thin provisioning and disks created on block-based (SAN) storage use lazy zeroing. Both thin provisioned and lazy zeroed thick provisioned disks produce misleading benchmark testing results; EMC does not recommend thin/lazy zeroed provisioned disk configuration for production use of AVE.

Convert a thin provision disk to thick by right-clicking the disk's.vmdk file in the datastore browser and choose Inflate. Convert a lazy zeroed thick provision disk to eager zeroed by using the -k option with vmkfstools on an ESX/ESXi console command line. If a disk is thin provisioned, it must be converted to thick before converting it to eager zero. See VMware documentation for details and other methods to perform these conversions.

Both conversion steps are time consuming and can consume 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 a high performance database server virtual machine are generally applicable to an AVE virtual machine. In particular, a storage pool allocated from a group of dedicated physical disks in a RAID 1 (mirror) or RAID 10 configuration are likely to provide best performance.


Installation

EMC CONFIDENTIAL

InstallationThe following topics describe how to install an AVE virtual machine.

Installation roadmap

The following steps are required to install an AVE virtual machine.

1. “Preparing the virtual machine” on page 17

2. “Running ave-part.pl” on page 20

3. “Configuring network settings” on page 21

4. “Installing AvInstaller” on page 23

5. “Installing and configuring Avamar software” on page 24

6. “Running ave-post.sh” on page 27

7. “Installing server software patches” on page 27

Preparing the virtual machine

1. Download the AVE virtual appliance and checksum file.

EMC recommends using Windows FTP utilities WinSCP or FileZilla to perform the download. Use the checksum file to verify the AVE virtual appliance was properly downloaded.

2. Extract the AVE virtual appliance.

EMC recommends using the WinRaR utility to extract the package. Using WinZip can produce inconsistent results.

3. Launch a VMware vSphere Client and connect to vCenter or directly to the ESX/ESXi host that will host the AVE virtual machine.

4. Login with administrative rights.

5. If you logged into vCenter, select the ESX/ESXi server that will host the AVE virtual machine.

6. Select File > Deploy OVF Template.

The Source page appears.

7. Select Deploy from a file and browse to the AVE virtual machine file (OVF extension).

8. Click Next.

The OVF Template details page appears.

9. Click Next.

The Name and Location page appears.

Installation 17

Installation

EMC CONFIDENTIAL

10. Type in the AVE name and select the inventory location.

11. Click Next.

The Storage page appears.

12. Select the storage for AVE .

13. Click Next.

The Disk Format page appears.

14. Select one the following.

• For ESX/ESXi 4.1, select Thick Provisioned Format.

• For ESXi 5.0/5.1, select Thick Provision Lazy Zero format.

15. Click Next.

The Network Mapping page appears.

16. Map the network to the OVF template.

17. Click Next.

The Ready to Complete page appears.

18. Confirm the deployment settings are correct.

19. Click Finish.

The installation may take several minutes. A Completed Successfully message indicates the end of the installation process.

20. Click Close.

21. Select the AVE virtual machine you imported.

22. Right-click the AVE virtual machine and select Edit Settings.

The Virtual Machine Properties window appears.

23. Select Memory and set Memory Size based on the size of the AVE license.

• For 0.5 TB AVE, specify 6 GB.

• For 1 TB AVE, specify 8 GB.

• For 2 TB AVE, specify 16 GB.

24. Select Network adapter 1 and choose the Network Connection (virtual machine port group) appropriate to the customer environment.

25. Create additional 250 GB hard drives (VMDKs) for the AVE virtual machine based on the specifications from “AVE disk configuration” on page 15.

a. Select Add.

The Add Hardware Wizard appears.

b. Select Hard Disk.

c. Click Next.

d. Select Create a new virtual disk.


Installation

EMC CONFIDENTIAL

e. Click Next.

f. For Disk Size, type 250 GB.

g. For Disk Provisioning select:

– For ESX/ESXi 4.1, Thick Provisioned Format

– For ESXi 5.0/5.1, Thick Provision Lazy Zero format

If you select Thick Provision Eager Zeroed during the installation, the installation could take several hours and/or time out errors could occur. See “Best practices” on page 16 for disk formatting after the installation process is complete.

h. For Location, select either Store with virtual machine or Specify a datastore.

i. If you set Store with virtual machine, go to step k. If not, select Browse and go to step j.

j. In the Browse for Datastore window, navigate to the desired datastore location.

k. Click OK.

l. Click Next.

m. For Mode select Independent (use the default setting for Persistent).

n. Click Next.

o. Verify the configuration and select Finish.

p. Repeat steps a through o.

– For 0.5 TB AVE, repeat two more times (for a total of three 250 GB hard drives).

– For 1 TB AVE, repeat five more times (for a total of six 250 GB hard drives).

– For 2 TB AVE, repeat 11 more times (for a total of 12 250 GB hard drives).

26. Finalize virtual machine configuration by doing the following:

a. Click OK.

b. In the Recent Tasks status area (bottom of screen), observe the progress of the hard drive creation.

When the status of the reconfigured Virtual Machine is complete, a Completed message appears.

27. Right-click the virtual machine and select Power > Power On.

This command boots the virtual machine.

An insufficient licensing message at this point might indicate either a shortage of ESX Server licenses or an inability to connect to a license server. Resolve this problem with your network administrator.

28. On the Summary tab, verify the status for VMware Tools changes to Running or Unmanaged.

Installation 19

Installation

EMC CONFIDENTIAL

Running ave-part.pl

The ave-part.pl command is used to perform the following tasks on the specified AVE partitions:

◆ Sense system configuration

◆ Partitions the hard drives

◆ Creates the filesystems

◆ Labels the filesystems

◆ Mounts the filesystems

◆ Modifies /etc/fstab

◆ Creates symbolic links

The following steps are used to run ave-part.pl:

1. In the vSphere Client, select the AVE virtual machine and click the Console tab.

2. Click in the middle of the Console to put it into command mode and press Enter.

Press CTRL+ALT to regain mouse control.

3. Log in to the guest as user root.

When prompted for a password, type changeme and press Enter.

4. Configure the virtual hard drives by entering the following command and pressing Enter:

#/usr/local/avamar/bin/ave-part.pl

5. Wait until all actions are completed and a Script Complete! message appears in the command shell. This can take several minutes.


Installation

EMC CONFIDENTIAL

Configuring network settings

1. On the vSphere Client Console tab, log in to the guest as root user.

2. When prompted for a password, type changeme and press Enter.

3. At the command prompt, type the following command:

yast2

4. Press Enter.

The YaST2 Control Center dialog box appears.

In YaST2, pressing Ctrl+H backspaces over data to delete existing data.

5. Select Network Devices and press Enter.

The Network Devices dialog box appears.

6. From Network Devices, select Network Settings and press Enter.

Installation 21

Installation

EMC CONFIDENTIAL

7. From Network Settings use the Tab key to access the Edit option and press Enter.

8. From the Network Card Setup use the Tab key to access and select Statically assigned IP Address (select using the spacebar) and type in the IP Address, Subnet Mask, and Hostname of the AVE virtual machine.

9. Use the Tab key to select Next and press Enter.

10. From Network Settings use the Tab key to select Overview. Use the right-arrow key to select Hostname/DNS. Use the Tab key to specify the following fields:

a. Hostname

b. Domain Name

c. Name Server 1

d. Name Server 2

e. Domain Search


Installation

EMC CONFIDENTIAL

11. Tab to Hostname/DNS and right-arrow to Routing. Type in the Default Gateway for the AVE virtual machine. Tab to OK and press Enter.

12. From the YaST Control Center, Tab to Quit and press Enter.

13. Verify the preceding data by entering:

ifconfig

14. Verify basic network configuration of eth0 by entering:

ping <Static-IP-Address>

where Static-IP-Address is the static IP address defined in the YaST2 configuration.

15. Verify that the drives are mounted with the following command:

df -h | grep data

16. Verify basic network configuration with the following commands:

ping gateway - basic network

ping DNS / gateway

nslookup - dns verification

Installing AvInstaller

AvInstaller is a backend service that executes and reports package installations.

To install AvInstaller:

1. From the vSphere Client, log in as root user to the guest console.

2. When prompted for a password, type changeme and press Enter.

3. Change directory by typing:

cd /usr/local/avamar/src/

4. Run bootstrap by typing:

./avinstaller-bootstrap-6.1-version.sles11_64.x86_64.run

where version is the product version.

The Installation script will run. After the installation script is complete, an Installation of SLES11 Bootstrap RPMs completed message appears.

Installation 23

Installation

EMC CONFIDENTIAL

Installing and configuring Avamar software

To install Avamar software on a new AVE virtual machine:

1. Log in to the Avamar Installation Manager user interface as the root user.

2. Open a web browser and type the following:

https://Avamar-Server:8543/avi/avigui.html

where Avamar-Server is the hostname (as defined in DNS) or the IP address of the Avamar virtual machine.

The EMC Avamar Installation Manager login page appears.

3. If any security messages appear, click Continue.

The EMC Avamar Installation Manager dialog box appears.

4. In the User field type root.

5. In the password field type changeme.

6. Click Login.

7. Confirm that you are on the SW Releases tab and click the Unlock icon in the upper right hand corner of the dialog box.

The Passcode dialog box appears.

8. Type in Supp0rt0nly for the password (use zero instead of o) and click OK.


Installation

EMC CONFIDENTIAL

The SW Releases dialog box appears. This screen can take a few minutes to populate. After a few minutes, click the Refresh icon to see the installation package.

9. Click the Install button.

The installation initialization begins. The initialization extracts files from the package and prepares the environment for the installation. The process can take a few minutes.

Once the initialization completes, the Installation Setup page appears. Note that the tabs with an ! are required for installation.

10. Click the Network Config tab. Enter a value of 0 and click Save.

11. Click the ConnectEMC tab.

Specify the following on the ConnectEMC tab:

a. For Email sender address: sender email address for email notification

b. For Email server: Hostname of email server for notification emails to EMC

c. For Site name: Description of Avamar server location

d. Click Save

Installation 25

Installation

EMC CONFIDENTIAL

12. (Optional) Click the Passwords tab and make any desired edits to the default passwords.

13. Click the Password Validation tab. Type and confirm the Linux root password for the AVE virtual machine. By default this password is changeme.

14. Click the Server Settings tab. Select the applicable timezone and click Save. Click Continue.

The Installation Progress dialog box appears.

When the installation is complete, the following message appears:

Congratulations! The installation has completed and the application server is now restarting Please allow about 2 minutes before clicking the buttons below.

15. Select the appropriate action:

• Go to Avamar Enterprise Manager

• Close

After a successful installation, the installation package is automatically deleted from the Avamar system. The package is still available from the Windows system that runs the Avamar Downloader Service.


Installation

EMC CONFIDENTIAL

Running ave-post.sh

The ave-post.sh script is used to complete installation tasks.

1. On the vSphere Client Console tab, log in as user root and when prompted for a password, type changeme and press Enter.

2. Run the following script:

/usr/local/avamar/bin/ave-post.sh

The following information appears in your command shell:

Changing permissions on messages file...DONE Changing permissions on mcserver.log.0...DONE Changing permissions on mcserver.log.0.1...DONE Changing zzdpn shutdown order...DONEScript complete.

3. Exit the command environment.

Installing server software patches

This section describes how to use the System Maintenance tab in the Avamar Enterprise Manager to install Avamar server software patches, hotfixes, and updates. The System Maintenance tab is available after successful AVE installation.

Installing patches, hotfixes, and server software updatesThe System Maintenance tab in the Avamar Enterprise Manager is used to install server patches and updates, to delete packages, and to view history information about installed packages.

The System Maintenance tab includes three pages that provide these features:

◆ SW Updates — Downloads and installs patches and hotfixes.

◆ SW Upgrades — Downloads and installs restricted updates, upgrades, and hotfix patches.

Access to the SW Upgrades page is restricted to EMC Customer Support. The SW Upgrades page is not visible until you log in to the EMC Customer Support account.

◆ History — Displays status information for all packages that have been installed.

The icon to the left of the System Maintenance tab indicates that packages are available for installation.

Installation 27

Installation

EMC CONFIDENTIAL

Installing updates and upgradesTo install updates or upgrades:

1. To start the Avamar Enterprise Manager, open a web browser and type:

https://Avamar-server:8543/avi/avigui.html

where Avamar-server is the hostname (as defined in DNS) or the IP address.


2. Type root in the User field and the changeme in the Password field.

3. Click Login.

The main screen of the EMC Avamar Installation Manager appears.

4. Click System Maintenance.

The SW Updates page appears.

5. Click the EMC Customer Support Login icon.

The Passcode dialog box appears.

6. Type in Supp0rt0nly for the password (use zero instead of o) and click OK.

7. The lock icon opens and the SW Upgrade page appears.

8. Select a system from the Systems list.

If packages are available, they appear in the Package List.

9. Install the package on the Avamar system.

a. If the package is not in the local repository, a Download button appears. Click Download to download the package to the local repository. Otherwise, continue to step b.

Once the download completes, the Download button changes to the Install button.

b. Click the Install button to start the installation.

The Initiating the installation process status message appears, then the Installation Setup page appears.

10. Complete the installation setup by providing the requested information.

11. Click Show advanced settings to view optional settings.

12. Provide the requested information for advanced settings.

13. Click Continue.

14. Respond to all installation problems:

a. Take action to correct the problem.

b. Click the appropriate button to resume the installation.


Installation

EMC CONFIDENTIAL

15. After the installation completes, log out of the EMC Customer Support account:

a. Click the EMC Customer Support Logged-In icon.

The Support Log Out dialog box appears

b. Click OK.

Deleting packagesThe following steps are used to delete packages.






3. Click Login.


4. Select the SW Updates page.


If packages are available for deletion, a Delete button appears.

6. Click Delete to delete the package.

A Confirmation dialog box appears.

7. In the Confirmation dialog box, click Yes to confirm the package deletion.

Installation 29

Installation

EMC CONFIDENTIAL

Viewing installation history informationThe History page displays a table that contains installation history for all packages. The default sort order of the table is ascending order based on the date in the Last Updated column. The most recently installed package, therefore, is listed as the last item in the table.

To view the History page:






3. Click Login.


4. Click System Maintenance.

5. Click History.

The History page appears.


All packages for the selected system appear in the History table.

7. Click a row in the History table to view more details about a specific package.

8. In the Details table, click Logs to view log information about specific tasks.

9. To save the log information to a file, click Export.

The Export as dialog box appears.

10. Choose one of format buttons (Excel or PDF):

• Clicking Excel displays the File Download dialog box and the file can be opened or saved.

• Clicking PDF displays the log information in a new tab or window by using the Adobe Acrobat Reader.


EMC CONFIDENTIAL

CHAPTER 3Post-Installation Configuration


◆ Task 1: Obtain and install a server license............................................................... 32◆ Task 2: Set up replication........................................................................................ 38◆ Task 3: Change Avamar passwords.......................................................................... 38◆ Task 4: Product registration..................................................................................... 38◆ Task 5: Add a custom security notification to web login pages................................. 41◆ Task 6: Configure ConnectEMC after the installation ................................................ 41

Post-Installation Configuration 31

Post-Installation Configuration

EMC CONFIDENTIAL

Task 1: Obtain and install a server licenseAVE requires a license key for permanent operation. Upon acceptance of your order, EMC licensing provides you with assigned license keys for the Avamar software.

The assigned license keys for standard Avamar products are available from the Avamar download center: Subscribenet. To access Subscribenet, type the login credentials provided in the email sent to you from [email protected]. If you cannot find the email from [email protected]:

1. Send an email to [email protected] to request the Avamar license keys.

2. Include the EMC product SO number in the email.

The EMC product SO number is required.

The return time for an email response is 48 hours.

The following is an example of an assigned license key:

EMC Avamar Software License Key Information Avamar System Customer Account ID: CN-10062734404 Avamar System Asset ID: A-2010014578

License installation road map

Use the following road map for all license installations except if you are replacing a failed utility node. If you are replacing a failed utility node with a new utility node, follow the instructions described in “Installing the software without a license key” on page 38.

Follow these instructions to install an Avamar server license:

1. Generate a gsankeydata.xml license key information file as described in “Generating a license key information file” on page 33.

The gsankeydata.xml license key information file is later used to generate the permanent license key.

You may have already generated this file during the Avamar server software installation and configuration. If so, you do not need to perform the steps in “Generating a license key information file” on page 33.

2. If you have login credentials to the Avamar License Portal, use the portal to generate a license key file as described in “Generating a permanent license key file” on page 34.

3. Install the license on the Avamar server as described in “Installing and activating the license” on page 37.



EMC CONFIDENTIAL

Generating a license key information file

To generate a gsankeydata.xml license key information file:

1. Open a command shell and log in by using one of the following methods:

• To log in to a single-node server, log in to the server as admin.

• To log in to a multi-node server:

a. Log in to the utility node as admin, and then load the admin OpenSSH key by typing:

ssh-agent bashssh-add ~admin/.ssh/admin_key

b. When prompted, type the admin_key passphrase and press Enter.

2. Type:

gathergsankeydata

The following information appears in the command shell:

Enter your Avamar system customer account number:

3. Type the Avamar system customer account number and press Enter.

A valid Avamar system customer account number (account ID) conforms to the following format:

CN-YYMMDDNNNNN

where:

• YY is a two-digit year.• MM is a two-digit month.• DD is a two-digit day of the month.• NNNNN is a five-digit numerical sequence.


Enter your Avamar system asset ID number:

4. Type the Avamar system asset ID number and press Enter.

A valid Avamar system asset ID number (asset reference ID) conforms to the following format:

A-YYYYNNNNNN

where:

• YYYY is a four-digit year.• NNNNNN is a six-digit numerical sequence.


Please enter the Internet domain for this account:

Task 1: Obtain and install a server license 33


EMC CONFIDENTIAL

5. Type the Internet domain and press Enter.

Information similar to the following appears in the command shell:

Your answers were: Customer account ID: [CN-10062212345] Customer asset ID: [A-2010123456] Internet domain: [emc.com] Is this correct? [y(es), n(o), e(xit)]:

6. Type y and press Enter.

The local directory now contains the gsankeydata.xml license key information file. This file is used to generate the permanent license key.

Generating a permanent license key file

To generate a permanent license key file, you must have login credentials to the Avamar License Portal. You receive login credentials to the Avamar License Portal after you complete Avamar installation training certification and accept the EMC confidentiality agreement.

If you do not have login credentials to the Avamar License Portal:

1. Open a support ticket with EMC Support and request an Avamar license key generation.

Note: [email protected] does not generate license keys.

2. Provide the gsankeydata.xml file and the authorized quantity of Terabyte Licenses you want to allocate to the system.

EMC Support then provides you with an XML file that contains an activated license key.

3. You can skip the steps in the following procedure and add the license key to the system, as described in “Installing and activating the license” on page 37.

To generate a permanent license key file if you have login credentials to the Avamar License Portal:

1. Open a web browser and go to http://www.avamar.com/support1.html.

The EMC Avamar License Portal page appears.

2. Type the username and password and click Submit.

The EMC Avamar Support page appears.


http://www.avamar.com/support1.html


EMC CONFIDENTIAL

3. Click Avamar Key Generation.

The EMC Avamar Key Generation page appears.

4. Click Browse, navigate to the license key information file that you generated either during Avamar server software installation and configuration or during “Generating a license key information file” on page 33, and then click Open.

The Upload Key Data XML text box now contains the license key information file.

5. In the Send To Email Address text box, type the email address to which EMC should send the license key file.

The email account must be an account from which you can save the attached license key file and copy it to the Avamar server.



EMC CONFIDENTIAL

6. Click Generate Key.

The EMC Avamar Support Enter Terabytes page appears.

Use the same assigned license keys for each Avamar server. Type only the number of Terabyte Licenses that you purchased as specified in the contractual agreement and purchase quantity with EMC. Licensing is subject to audit. If you exceed the software TB license purchased, contact your EMC Account Manager or Reseller for order compliance.

7. In the Terabytes text box, type the number of terabyte licenses to allocate to the Avamar server. Use the following table to help you determine the required terabytes based on the type of Avamar environment.

Table 5 Licensing options

Avamar Virtual Edition Required terabytes value

Avamar Virtual Edition 0.5 TB .5

Avamar Virtual Edition 1 TB 1

Avamar Virtual Edition 2 TB 2

If you purchase additional storage capacity, you must generate a new license key file.

8. Click Generate Key.

The EMC Avamar Support page displays a confirmation message that the license key file has been sent by email.



EMC CONFIDENTIAL

Installing and activating the license

After you receive the license key file from either EMC Support or from the key generation process in “Generating a permanent license key file” on page 34, you can install and activate the license.

To install and activate the license:

1. Log in to the email account to which the license key file was sent.

2. Open the email message from [email protected] with a subject line of EMC Avamar Key Information.

The email message contains the license key file as an attachment. The file uses the following naming convention:

ASSET-NAME_Key.xml

where ASSET-NAME is typically the Avamar server hostname as defined in DNS.

3. Save the ASSET-NAME.xml email attachment to a temporary directory or folder.

4. Use WinSCP or an equivalent program to copy the ASSET-NAME.xml license key file from the temporary directory or folder to /tmp directory on the AVE server.

5. Switch to the command shell session and ensure that you are still logged in as user admin, and that the admin OpenSSH key is loaded.

6. Ensure that the Avamar server subsystem (also known as GSAN) is running by typing:

dpnctl status gsan

If gsan is running, then the following information appears in the command shell:

dpnctl: INFO: gsan status: ready

7. Change file permissions on the ASSET-NAME.xml license key file and activate the license by typing the appropriate commands depending on server status:

• If the server is running, type:

chmod 644 /tmp/ASSET-NAME.xmlavmaint license /tmp/ASSET-NAME.xml --avamaronly

• If the server is not running, type:

cd /usr/local/avamar/etcmv license.xml license.xml.oldcp /tmp/ASSET-NAME.xml license.xmlchmod 644 license.xml

where ASSET-NAME.xml is the license key file.

8. If the Avamar server is not running, start it.

9. Verify that the server license is correctly installed by typing:

avmaint license --avamaronly

License information appears in the command shell.



EMC CONFIDENTIAL

Installing the software without a license key

Installing the server software without a license key enables the Avamar system to operate for a 30-day grace period. After the 30-day grace period, AVE stops performing several functions. To avoid any interruptions to the Avamar server, you must enter the assigned license key before the 30-day grace period ends.

Enter the assigned license key at installation time to avoid expiration issues.

Task 2: Set up replicationIf applicable, configure replication according to instructions in the EMC Avamar Administration Guide.

Task 3: Change Avamar passwordsChange the default Avamar passwords according to instructions in the EMC Avamar Administration Guide.

Task 4: Product registrationIt is mandatory for EMC personnel and partners to register the new Avamar installation by following the appropriate procedure:

◆ “Product registration for EMC personnel” on page 38

◆ “Product registration for partners” on page 41

Registration is required to ensure the CSI/Oracle database is updated for each customer.

Product registration for EMC personnel

The following procedure requires the use of EMC Avamar Procedure Generator. If this application is not installed on your laptop, download it from one of the following locations:

◆ EMC Online Support

http://support.EMC.com

Type Avamar Procedure Generator in the Find a Product box.

◆ Global CS website

http://www.cs.isus.emc.com/csweb2/dgweb/AvamarPG/revision_history.asp



EMC CONFIDENTIAL

◆ Global Services Intranet

http://www.cs.isus.emc.com/csweb2/proc_gen.htm

BookMark the site to find all Generators:

Site Index > (P) Procedure Generators > Avamar Procedure Generator

The EMC Avamar Procedure Generator is not a customer facing tool at this time. Do not provide details about this tool to non-EMC service personnel or non-EMC Authorized Service Partners.

If you need help to complete this task, call the Install Base Group number (1-508-249-9410). Sending this information is essential to both the EMC call tracking system and EMC Technical Support. Until this task is done, installation is not complete.

Using the EMC Avamar Procedure GeneratorTo complete the Avamar Install Audit Form:

1. Open Avamar Procedure Generator.

2. Read the EULA and click YES (I accept).

3. From the Select a procedure from list, select Avamar Install Audit Form.

4. Click Next.

5. Select Avamar Install Audit Form.

6. Click Next.

7. Click Generate.

8. Follow the generated procedure, completing the Avamar Install Audit Form, and then emailing it to IBGroup ([email protected]).

A DialHome contact is a person contacted by EMC Technical Support when an alert is received through ConnectEMC and a service request is automatically generated. More than one alternate DialHome contact is allowed. Provide contact information for each of them. The primary contact is the first person contacted. Alternate contacts are contacted in any order.

Task 4: Product registration 39


EMC CONFIDENTIAL

When EMC Avamar Procedure Generator is not availableWhen the EMC Avamar Procedure Generator is not available, send an email to IBGroup ([email protected]) with a subject line of “Avamar Data Store Installation Notification” and the following message:

◆ Status: Installed

◆ Company Name: CUSTNAME

◆ Party ID: PARTYID

◆ Microcode Number: MICROCODENO

◆ Avamar System ID: SYSTEMID

◆ Primary DialHome Contact Info: INFO1

◆ Alternate DialHome Contact Info: INFO2

Each of these options is covered in the following table.

Table 6 Installation notification options defined

Variable Description

CUSTNAME Customer's company name

PARTY ID CSI Party Number (formerly known as Site ID)

MICROCODENO EMC CSI Item Number for the Avamar Application Image.

SYSTEMID Unique System Identifier used to identify the software that manages the solution. Hardware-only installations do not require a System ID.Obtain the Avamar System ID in one of two ways:• From a command prompt on the utility node, type:

mccli server show-prop

• On the Server Management tab of Avamar Administrator:Locate the System ID value in the Server Information pane.System ID is not available until implementation of Avamar software is complete. A separate communication to the Install Base Group using the Avamar Install Base Audit Form (located in the Avamar Procedure Generator) must be made to provide the System ID after implementation.

INFO1 The following primary DialHome contact information:• Contact name• Contact phone number• Contact email address

INFO2 The following alternate DialHome contact information:• Contact name• Contact phone number• Contact email address



EMC CONFIDENTIAL

Product registration for partners

To register the product use the Partner Notification Tool on EMC Services Partner web site:

1. Open a browser and connect to http://Powerlink.EMC.com.

2. From the Navigator list in the upper right corner, select EMC Services Partner Web.

The EMC Services Partner Web page appears.

3. Click the Tools & Forms link in the menu bar.

The Tools and Forms page appears.

4. Under Partner Notification Tool, click PNT Tool.

The Partner Notification Tool page appears.

5. Select Install with Remote Connection.

The browser displays Select a Product Family options.

6. Select Avamar.

The browser displays the registration form.

7. Complete the form.

8. Click Submit This PNT.

Task 5: Add a custom security notification to web login pagesIf applicable, add a custom security notification to web login pages according to instructions in the EMC Avamar Administration Guide.

Task 6: Configure ConnectEMC after the installationYou can configure ConnectEMC after the installation by using Avamar Administrator. The EMC Avamar Administration Guide provides more information.

Task 5: Add a custom security notification to web login pages 41

http://Powerlink.EMC.com


EMC CONFIDENTIAL


EMC CONFIDENTIAL

APPENDIX ABenchmark Testing

This appendix includes the following sections:

◆ Running benchmark testing..................................................................................... 44◆ Manually ending benchmark testing........................................................................ 45◆ Analyzing benchmark results .................................................................................. 45◆ Benchmark removal ................................................................................................ 48◆ Benchmark failure................................................................................................... 48

Benchmark Testing 43

Benchmark Testing

EMC CONFIDENTIAL

Running benchmark testingThe benchmark test is essentially the same as the Performance Analysis Tool (PAT). If the PAT passes, you should not need to use the benchmark test. However, if the configuration changes or additional load is added to the ESX/ESXi Server between the PAT and the AVE deployment, I/O performance might change to unacceptable levels.

The benchmark test is a troublehooting tool that can be run to ensure that AVE can function at an acceptable level in the virtual environment. This chapter describes how to set up, start, and end the testing.

There are two purposes for this test:

◆ To ensure AVE runs in an environment with acceptable I/O performance.

◆ To stress virtual machine resources to determine whether the impact of running AVE is acceptable to other applications on the ESX Server.

Before running the benchmark test, warn the customer that the test will induce a high load on the host ESX Server. Monitor the ESX Server’s performance while the tool is running to determine whether the stress on resources is acceptable. If not, end the test by following the instructions in Manually ending benchmark testing (page 45).

The following steps are used to start the benchmark test:

1. On the vSphere Client Console tab, log in to the guest as user root.


All remaining instructions in this procedure assume that you are logged in to the guest, and not to the ESX Server.

2. Run the benchmark test by entering:

/usr/local/avamar/bin/24hr-benchmark.sh &

The test runs for 24 hours unless it is manually ended (see next section).

This command also copies operational status data to a log file.

While the test is running, monitor the host ESX Server’s performance. If the stress on resources is unacceptable, end the test with the instructions in the next section.

3. After 24 hours, confirm the test has successfully ended by typing:

ps -ax | grep benchmark

Blank output indicates the test has been completed.


Benchmark Testing

EMC CONFIDENTIAL

4. Save test results by entering:

cd /root

tar –cvf CUSTOMERNAME_benchmark-results.tar YYYYMMDD_benchmark

where YYYYMMDD_benchmark is the directory automatically created in step 2.

Manually ending benchmark testing

By default, the benchmark test runs for 24 hours and does not need to be manually ended. If the stress on resources is unacceptable, the following steps can be used to manually end benchmark testing.

1. Type the following on the vCenter Client Console tab.

/usr/local/avamar/bin/kill-benchmark.sh

2. Wait at least 30 seconds, and then type:

ps ax | grep benchmark

Blank output indicates the test has been stopped.

3. Delete data from the directory created in step 2 of the previous section.

Analyzing benchmark resultsTest results are written to the /DIRECTORY/dt_std_HOSTNAME_summary and /DIRECTORY/seektest_only_summary_1 files, where HOSTNAME is the hostname of the virtual machine and DIRECTORY is the directory /root/YYYYMMDD_benchmark. In the sample output from each file that follows, significant data is displayed in bold text.

Manually ending benchmark testing 45

Benchmark Testing

EMC CONFIDENTIAL

Read and write test results

To review sequential read and write test results, open dt_std_HOSTNAME_summary. Typical output follows:

RESULTS FOR: dt_ax150test1_resultsax150test1__data01_dt.log:Tue Sep 11 14:38:05 2011 24.9601 MB / Second writtenax150test1__data02_dt.log:Tue Sep 11 14:38:02 2011 25.0557 MB / Second writtenax150test1__data03_dt.log:Tue Sep 11 14:38:02 2011 25.0428 MB / Second writtenax150test1__data04_dt.log:Tue Sep 11 14:38:05 2011 24.9315 MB / Second writtenax150test1__data05_dt.log:Tue Sep 11 14:37:57 2011 25.1910 MB / Second writtenax150test1__data06_dt.log:Tue Sep 11 14:37:41 2011 25.7286 MB / Second writtenax150test1__data01_dt.log:Tue Sep 11 14:51:19 2011 25.8599 MB / Second readax150test1__data02_dt.log:Tue Sep 11 14:48:58 2011 31.4723 MB / Second readax150test1__data03_dt.log:Tue Sep 11 14:49:23 2011 30.2847 MB / Second readax150test1__data04_dt.log:Tue Sep 11 14:51:17 2011 25.9244 MB / Second readax150test1__data05_dt.log:Tue Sep 11 14:51:37 2011 25.2861 MB / Second readax150test1__data06_dt.log:Tue Sep 11 14:51:44 2011 25.0609 MB / Second readTOTAL MINIMAL WRITE THROUGHPUT (24.9315 * 6): 149.589 MB / Second writeTOTAL MINIMAL READ THROUGHPUT (25.0609 * 6): 150.3654 MB / Second writeTOTAL WRITE THROUGHPUT (SUM): 150.9097 MB / Second writeTOTAL READ THROUGHPUT (SUM): 163.8883 MB / Second read


Benchmark Testing

EMC CONFIDENTIAL

Seek test results

To review seek test results, open seektest_only_summary_1. Ignore other similarly-named files with alternate last digits. The part of the file’s contents that you need to analyze is “FOR 4 THREADS.” Typical output follows:

seektest.ax150test1.devsda8.4threads.run:average seeks/sec = 67.643333seektest.ax150test1.devsda7.4threads.run:average seeks/sec = 108.650000seektest.ax150test1.devsda6.4threads.run:average seeks/sec = 137.106667seektest.ax150test1.devsda5.4threads.run:average seeks/sec = 144.833333seektest.ax150test1.devsda3.4threads.run:average seeks/sec = 124.143333seektest.ax150test1.devsda2.4threads.run:average seeks/sec = 87.016667TOTAL SEEK MINIMAL THROUGHPUT FOR 4 THREADS (67.643333 * 6): 405.859998TOTAL SEEK THROUGHPUT FOR 4 THREADS (SUM): 669.393333

The following table lists minimal acceptable benchmark test results for 0.5 TB AVE:

Table 7 0.5 TB AVE minimum benchmark test results

ConditionsFile server data value

Mixeddata value

Total Minimal Read Throughput 60 MB/sec 75 MB/sec

Total Read Throughput 60 MB/sec 75 MB/sec

Total Minimal Write Throughput 30 MB/sec 60 MB/sec

Total Write Throughput 30 MB/sec 60 MB/sec

Total Seek Minimal Throughput for 4 Threads 320 seeks/sec 320 seeks/sec

Total Seek Throughput for 4 Threads 400 seeks/sec 400 seeks/sec

The following table lists minimal acceptable benchmark test results for 1 TB AVE:

Table 8 1 TB AVE minimum benchmark test results


Mixeddata value







Analyzing benchmark results 47

Benchmark Testing

EMC CONFIDENTIAL

The following table lists minimal acceptable benchmark test results for 2 TB AVE:

Table 9 2 TB AVE minimum benchmark test results


Mixeddata value







If benchmark testing does not yield satisfactory results, attempt to resolve I/O issues before AVE installation.

Benchmark removalOnce the benchmark test is complete, it can be removed by typing the following command in the vSphere Client Console tab as root user:

/usr/local/avamar/bin/dtsh --cleanup

Benchmark failureIf minimum acceptable benchmark results cannot be achieved, delete the virtual machine by performing the following:

Do not perform the following procedure if benchmark results are satisfactory. In that case, continue installing AVE.

1. Log in as root user.


2. On the vSphere Client Console tab, type:

poweroff

3. In left pane, right-click the virtual machine you want to remove.

4. Select Delete from Disk.


EMC CONFIDENTIAL

This glossary provides definitions for terms used in this guide.

administrator Person who normally installs, configures, and maintains software on network computers, and who adds users and defines user privileges.

ADS Avamar Data Store. A bundled EMC solution that combines Avamar software and EMC hardware in a preconfigured, turnkey solution for ordering, installation, and service. ADS scales from a single-node to a multi-node solution in order to meet the needs of remote offices to data centers.

Avamar Administrator Avamar Administrator is a graphical management console software application that is used to remotely administer an Avamar system from a supported Windows or client computer.

Avamar client A computer or workstation that runs Avamar software and accesses the Avamar server over a network connection. Avamar client software comprises a client agent and one or more plug-ins.

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

Avamar server The server component of the Avamar client/server system. Avamar server is a fault-tolerant, high-availability system that efficiently stores the backups from all protected clients. It also provides essential processes and services required for data restores, client access, and remote system administration. Avamar server runs as a distributed application across multiple networked storage nodes.

AVE Avamar Virtual Edition. Avamar deployed as a virtual appliance for backup and recovery. With AVE, an Avamar server can be deployed as a virtual appliance on an existing VMware ESX Server, leveraging the attached disk storage and infrastructure.

AvInstaller A backend service that executes and reports package installations.

backup A point-in-time copy of client data that can be restored as individual files, selected directories, or as entire filesystems. Although more efficient than a conventional incremental backup, a backup is always a full, just copy of client data that can be restored immediately from an Avamar server.

client activation The process of passing the client ID (CID) back to the client, where it is stored in an encrypted file on the client filesystem.

client agent An Avamar client agent is a platform-specific software process that runs on the client and communicates with the MCS (page 169) and with any plug-ins installed on that client.

GLOSSARY

Glossary 49

Glossary

EMC CONFIDENTIAL

client registration The process of establishing an identity with the Avamar server. When Avamar recognizes the client, it assigns a unique client ID (CID), which it passes back to the client during activation.

ConnectEMC A Linux-based program that transfers event data from an Avamar server to EMC Technical Support. An Avamar server software installation or upgrade automatically initializes ConnectEMC by passing values from configuration attributes to the ConnectEMC_config.xml file.

dataset A policy that defines a set of files, directories, and filesystems for each supported platform that are included or excluded in backups across a group of clients. A dataset is a persistent and reusable Avamar policy that can be named and attached to multiple groups.

disaster recovery Recovery from any disruptive situation, such as hardware failure or software corruption, in which ordinary data recovery procedures are not sufficient to restore a system and its data to normal day-to-day operations. A disaster recovery may or may not be a bare metal recovery.

DNS Domain Name Server. A dynamic and distributed directory service for assigning domain names to specific IP addresses.

domain A feature in Avamar Administrator that is used to organize large numbers of clients into named areas of control and management.

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

EMC repository A repository that contains server installation packages, client installation packages, and manifest files. The EMC repository currently spans two locations: ftp://ftp.avamar.com and EMC Subscribenet.

group A level of organization in Avamar Administrator for one or more Avamar clients. All clients in an Avamar group use the same group policies, which include the dataset, backup schedule, and retention policy.

group policy The dataset, schedule, and backup retention policy attached to a group that is used by all clients in a group, unless these policy settings are overridden by an administrator at the client level.

Management Console Server (MCS)

The MCS provides centralized administration (scheduling, monitoring, and management) for the Avamar server. The MCS also runs the server-side processes used by the Avamar Administrator graphical management console.

manifest file An XML file listing all packages currently available for download from the EMC repository. When the EMC Subscribenet team adds a package to the EMC repository, it then adds an entry that describes the package to the manifest file. When the EMC Subscribenet team removes the package from the repository, it then removes the entry for the package from the manifest file.


Glossary

EMC CONFIDENTIAL

metadata Hash information that identifies stored sub-file information for deduplication, and is required to revert deduplicated client backup data to the regular non-deduplicated format.

plug-in An Avamar plug-in is a software process that recognizes a particular kind of data resident on that client.

policy A set of defined rules for client backups that can be named and applied to multiple groups. Groups have dataset, schedule, and retention policies.

Raw Disk Mapping (RDM) A construct that maps a virtual disk to a pass-through SCSI device.

restore File or object restore. An operation that retrieves one or more filesystems, directories, files, or data objects from a backup and writes the data to a designated location.

retention The ability to control the length of time that backups are kept in an Avamar server before automated deletion. Retention can be set to permanent for backups that should not be deleted from an Avamar server. Retention is a persistent and reusable Avamar policy that can be named and attached to multiple groups.

schedule The ability to control the frequency and the start and end time each day for backups of clients in a group. A schedule is a persistent and reusable Avamar policy that can be named and attached to multiple groups.

vMotion VMware technology that enables the live migration of running virtual machines from one physical server to another with zero downtime, continuous service availability, and complete transaction integrity.

VMware ESX/ESXi Server The foundation for delivering virtualization-based distributed service to IT environments. A core building block of VMware Infrastructure, ESX/ESXi Server is a virtualization layer that abstracts processor, memory, storage, and networking resources into multiple virtual machines running side-by-side on the same server.

VMware Virtual Machine File System (VMFS)

A high-performance cluster file system for ESX/ESXi Server virtual machines. Each virtual machine is encapsulated in a small set of files and VMFS is the default storage system for these files on physical SCSI disks and partitions.

vSphere Client VMware interface that allows administrators and users to connect remotely to the vSphere Server or individual ESX Server installations from any Windows PC.

vSphere Server VMware central point for configuring, provisioning, and managing a virtualized IT infrastructure.

51

Glossary

EMC CONFIDENTIAL


300 013-365 avamar-virtualedition6.1installationguide

Technology

Transcript of 300 013-365 avamar-virtualedition6.1installationguide