emc avamar 7.2 extended retention user guide · emc avamar 7.2 extended retention user guide 9....

EMC® Avamar® 7.2 ExtendedRetention

User Guide302-001-943

REV 01

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

Published June, 2015

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

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

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

For the most up-to-date regulatory document for your product line, go to EMC Online Support (https://support.emc.com).

EMC CorporationHopkinton, Massachusetts 01748-91031-508-435-1000 In North America 1-866-464-7381www.EMC.com

2 EMC Avamar 7.2 Extended Retention User Guide

7

9

Introduction 13

Overview....................................................................................................... 14Capabilities and limitations...........................................................................14Important terms and definitions.................................................................... 15Operational best practices............................................................................ 16

Getting started 19

Supported browsers......................................................................................20Using Avamar Extended Retention for the first time....................................... 20Logging in for the first time............................................................................20

Login-failures................................................................................... 21Session timeouts............................................................................. 21

Accessing workspaces.................................................................................. 21The Administration workspace......................................................... 21The Avamar Extended Retention workspace..................................... 22My Workspace..................................................................................22

Using online help.......................................................................................... 23Avamar Extended Retention online help........................................... 23Springboard and page-level help......................................................23

Logging out................................................................................................... 24

Using the Avamar Extended Retention Workspace 25

Opening Avamar Extended Retention springboards....................................... 26The Media Management springboard............................................... 27The Scheduled Exports springboard................................................. 27The Import & Restore springboard.................................................... 27The Configuration springboard......................................................... 28The Recent Events springboard........................................................ 29The Task Monitoring springboard..................................................... 30The Import & Export Job History springboard.................................... 32

Managing library media.................................................................................32Working with custom tape pools...................................................... 34Working with custom retention periods............................................ 37Working with tape volumes.............................................................. 39

Exporting Avamar backups to tape................................................................ 43Viewing Avamar server and export policy details.............................. 44Creating an export policy..................................................................45Editing an export policy....................................................................49Activating or deactivating an export policy....................................... 49Deleting an export policy..................................................................50Performing on-demand exports........................................................ 50Viewing export job details for active policies in the Task Viewer....... 51

Tables

Preface

Chapter 1

Chapter 2

Chapter 3

CONTENTS

EMC Avamar 7.2 Extended Retention User Guide 3

Browsing and importing Avamar backups......................................................51Restore limitations........................................................................... 53Locating exported backups.............................................................. 54Importing backups from tape........................................................... 55Customizing columns in the Backup panel....................................... 56Editing backup retention periods..................................................... 58Resetting the Import Server.............................................................. 58Restoring imported backups to a client............................................ 58

Generating an import and export job history report........................................59

Using the Administration Workspace 61

User management......................................................................................... 62Searching for a user......................................................................... 62Creating a user account....................................................................62Editing a user account......................................................................63Disabling a user account.................................................................. 63Unlocking a user account................................................................. 64

Role management......................................................................................... 64Editing user roles............................................................................. 65Generating a user role report............................................................66

User profile management.............................................................................. 66Changing a user name or an email address...................................... 66Changing a password.......................................................................67Changing email message settings.................................................... 67

System configuration.................................................................................... 67Configuring system settings............................................................. 68Configuring email notifications.........................................................69Enabling SNMP................................................................................ 70

System events...............................................................................................70Viewing event details in the Event Viewer.........................................71Acknowledging events..................................................................... 72Exporting events to a CSV file........................................................... 72Filtering events.................................................................................73Updating events...............................................................................73

Tasks............................................................................................................ 73Viewing task details in the Task Viewer............................................ 74Filtering tasks.................................................................................. 75

Security events..............................................................................................76Viewing event details in the Security Event Viewer........................... 76Filtering security events....................................................................77Deleting security events................................................................... 77Archiving security events..................................................................77Clearing the security threat level...................................................... 78

Log information.............................................................................................78

Administration 81

Customizing drop-down text in the login dialog box.......................................82Configuring the maximum value for parallel jobs........................................... 82Changing the root password on the Media Access node................................ 83Configuring SNMP traps................................................................................ 84

Configuring Avamar server traps.......................................................84Configuring tape management system traps.....................................85The Management Information Base.................................................. 87

Configuring the system to use an ACSLS library............................................. 89

Chapter 4

Chapter 5

CONTENTS


Viewing current software versions................................................................. 93Shutting down the Media Access node.......................................................... 93Setting up a VMware vCenter client............................................................... 94

Modifying the mcserver.xml file........................................................94Setting up the VMware vCenter client on the Media Access node......94

Disaster Recovery 97

Definition of a disaster.................................................................................. 98Creating a disaster recovery image................................................................ 98Recovering the Avamar Extended Retention server.........................................98

Install Avamar Extended Retention...................................................98Set up the lockbox password and the superuser account................. 99Apply the Avamar Extended Retention disaster recovery image........ 99Recover the bootstrap.................................................................... 100

Troubleshooting 103

Software component modification caveats.................................................. 104Import server issues....................................................................................104

The Import server does not display in the GUI.................................104The Import server appears to be offline in the GUI.......................... 107

External Avamar server issues..................................................................... 108Avamar servers incorrectly appear offline in the GUI....................... 108Avamar servers do not appear in the GUI........................................108Avamar server performance is affected by Avamar Extended Retentionactivities........................................................................................ 110

Import failures.............................................................................................110Import failed and did not display in the Avamar Management ConsoleActivity Monitor..............................................................................110Import failed and can be seen in the Import server's AvamarManagement Console.................................................................... 111Backups do not appear in the Backup Browse/Import page............111An Avamar client does not appear in the Backup Browse/ Import page...................................................................................................... 111

Export failures.............................................................................................112Exports are failing in general.......................................................... 112Exports do not appear in the Avamar Management Console and fail inAvamar Extended Retention........................................................... 113An export failed and appears in the MC Activity Monitor................. 114Not all exports were written to tape, but the export task completed...................................................................................................... 114The Event Viewer indicates that an export event was skipped.........114An export worked but the client is not in the import list.................. 114

Jobs take a long time to run.........................................................................115Library issues..............................................................................................115

The library does not appear in the GUI............................................115The library appears as UNKNOWN in the GUI.................................. 115An eject-tape request failed........................................................... 116

A task failed or completed with exceptions..................................................116The file index is reporting that it is full.........................................................116JavaScript errors..........................................................................................117Timeout messages...................................................................................... 117

Chapter 6

Chapter 7

CONTENTS


CONTENTS


Event severity icons....................................................................................................... 30Task type icons..............................................................................................................31Task state icons.............................................................................................................31Library Detail descriptions............................................................................................. 33Volumes panel columns................................................................................................ 40Backups panel columns.................................................................................................41Avamar server details.................................................................................................... 44Backup panel columns.................................................................................................. 52Avamar Extended Retention functions and required roles.............................................. 64Event Viewer column descriptions................................................................................. 72Task Viewer column descriptions...................................................................................74Security Event Viewer column descriptions.................................................................... 76Log Viewer detail descriptions....................................................................................... 79

12345678910111213

TABLES


TABLES


PREFACE

As part of an effort to improve its product lines, EMC periodically releases revisions of itssoftware and hardware. Therefore, some functions described in this document might notbe supported by all versions of the software or hardware currently in use. The productrelease notes provide the most up-to-date information on product features.

Contact your EMC technical support professional if a product does not function properlyor does not function as described in this document.

Note

This document was accurate at publication time. Go to EMC Online Support (https://support.EMC.com) to ensure that you are using the latest version of this document.

PurposeThis document describes how to use Avamar Extended Retention.

AudienceThis document is intended for system administrators who will be using Avamar ExtendedRetention.

Revision historyThe following table presents the revision history of this document.

Revision Date Description

01 June, 2015 GA release of Avamar 7.2

Related documentationThe following EMC publications provide additional information:

l EMC Avamar Extended Retention Release Notes

l EMC Avamar Extended Retention Security Guide

l EMC Avamar Media Access Node Customer Hardware Installation Guide

l EMC Avamar Compatibility and Interoperability Matrix

l EMC Avamar Data Store Customer Service Guide

l EMC Avamar Data Store Site Prep Technical Specifications

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

NOTICE

Addresses practices not related to personal injury.

Note

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

Typographical conventionsEMC uses the following type style conventions in this document:


https://support.emc.com/

https://support.emc.com/

Bold Use for names of interface elements, such as names of windows, dialogboxes, buttons, fields, tab names, key names, and menu paths (whatthe user specifically selects or clicks)

Italic Use for full titles of publications referenced in text

Monospace Use for:

l System code

l System output, such as an error message or script

l Pathnames, file names, prompts, and syntax

l Commands and options

Monospace italic Use for variables

Monospace bold Use for user input

[ ] Square brackets enclose optional values

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

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

... Ellipses indicate nonessential information omitted from the example

Where to get helpThe Avamar support page provides access to licensing information, productdocumentation, advisories, and downloads, as well as how-to and troubleshootinginformation. This information may enable you to resolve a product issue before youcontact EMC Customer Support.

To access the Avamar support page:

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

2. Type a product name in the Find a Product 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 inthe top right corner of the Support by Product page.

DocumentationThe Avamar product documentation provides a comprehensive set of featureoverview, operational task, and technical reference information. Review thefollowing documents in addition to product administration and user guides:

l Release notes provide an overview of new features and known limitations for arelease.

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 productsas applied to critical business issues or requirements.

PREFACE


https://support.emc.com/products

KnowledgebaseThe EMC Knowledgebase contains applicable solutions that you can search for eitherby 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 theScope by product box and then selecting the product from the list that appears.

4. Select Knowledgebase from the Scope by resource list.

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

6. Click the search button.

Online communitiesVisit EMC Community Network at http://community.EMC.com for peer contacts,conversations, and content on product support and solutions. Interactively engageonline with customers, partners and certified professionals for all EMC products.

Live chatTo engage EMC Customer Support by using live interactive chat, click Join Live Chaton the Service Center panel of the Avamar support page.

Service RequestsFor in-depth help from EMC Customer Support, submit a service request by clickingCreate 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 yourEMC sales representative for details about obtaining a valid support agreement orwith questions about your account.

To review an open service request, click the Service Center link on the ServiceCenter panel, and then click View and manage service requests.

Facilitating supportEMC recommends that you enable ConnectEMC and Email Home on all Avamarsystems:

l ConnectEMC automatically generates service requests for high priority events.

l Email Home emails configuration, capacity, and general system information toEMC Customer Support.

Your commentsYour suggestions will help us continue to improve the accuracy, organization, and overallquality of the user publications. Send your opinions of this document to [email protected].

Please include the following information:

l Product name and version

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

l Page numbers

PREFACE


HTTP://COMMUNITY.EMC.COM/

mailto:[email protected]

l Other details that will help us address the documentation issue

PREFACE


CHAPTER 1

Introduction

This chapter includes the following topics:

l Overview............................................................................................................... 14l Capabilities and limitations...................................................................................14l Important terms and definitions............................................................................ 15l Operational best practices.................................................................................... 16

Introduction 13

OverviewAvamar Extended Retention is a solution that exports backup data from an Avamar serverto a tape library (physical or virtual) for long term retention purposes. Administrators canimport (or restore) this backup data from tape as needed. A dedicated server, called theMedia Access node, hosts Avamar Extended Retention. Tape devices connect directly tothe node or to a fiber SCSI bridge with fiber-optic cable.

Avamar Extended Retention fully automates the execution of customer-defined exportpolicies. These policies specify the Avamar backups to export, the schedules on whichthose backups export, and the retention periods for which the backups and informationabout them will remain on tape. Avamar Extended Retention streams the backups directlyto tape, in rehydrated format, without staging the data during the export process. Whenthe backups are imported from tape, they are staged onto an instance of the Avamarserver software that is installed on the Media Access node.

Avamar Extended Retention allows users to browse backups that have been exported totape before selecting specific backups for import. It also provides alerts for exceptionsand historical reporting.

The following figure illustrates the processes for exporting Avamar backups to tapethrough the Media Access node, and for restoring them to an Avamar client.

Backup data is exported from either an Avamar or a Data Domain server, and isstreamlined through the Media Access node and written to tape in a physical or virtualtape library. Data that has been exported to tape can be imported back to the Avamarserver on the Media Access node, and then restored directly to a compatible Avamarclient.

Capabilities and limitationsAvamar Extended Retention provides several capabilities and benefits to customers,including:

l Allowing customers to put Avamar backups on tape

l Lowering the cost of storage for Avamar long-term retention of backups

l Producing transportable media for storing offsite

Introduction


l Producing transportable media for restoring at an alternative site

The following sections describe limitations associated with Avamar Extended Retention.

Avamar Extended Retention requires Avamar 7.1Avamar Extended Retention is included in the Avamar 7.1 release. Customers must alsoupgrade the Avamar grids that Avamar Extended Retention will use to Avamar 7.1.

Avamar Extended Retention is intended for long-term retentionAvamar Extended Retention is to be used for long-term retention of data, and is notintended for operational recovery purposes. Administrators can use Avamar ExtendedRetention to initiate the import of backups that have been exported to tape. However, it isnot intended for end-users to perform their own imports. It is also not suitable for use asan alternative to replication or for use as a complete disaster recovery solution.

Exports and imports can take a significant amount of timeExports and imports may take a long time depending upon the amount of data that isinvolved.

A single physical or virtual tape library is supportedCurrently, Avamar Extended Retention can export Avamar backups to a single physical orvirtual tape library. The use of multiple libraries is not supported.

Standalone tape drives are not supportedAvamar Extended Retention requires the use of a tape library with a robotic arm, or anequivalent virtual tape library. Standalone tape drives are not supported.

Avamar Extended Retention must also have exclusive control of the tape library and alldrives that are allocated to it. The first release of Avamar Extended Retention has notbeen designed to coordinate access with any other tape management implementation.

Important terms and definitionsThe following terms are used throughout this guide.

Avamar Extended Retention agentThe Avamar Extended Retention software component, which transforms a backup datastream from Avamar format into a proprietary format (during export) and vice versa(during restore). The agent is one of several distinct components that collectively makeup Avamar Extended Retention.

Avamar Extended Retention applicationThe Avamar Extended Retention software component where the overall extendedretention capability is administered. The Avamar Extended Retention applicationmaintains schedules and policies, kicks off jobs accordingly and drives the extendedretention user interface.

BackupAn object that contains all the data that an Avamar client or plug-in stores about a filesystem or application at the time a backup is created. The Avamar term is Dataset.

Backup metadataAttributes of the backups that have been exported by Avamar Extended Retention, suchas the host machine it was taken from, the date/time it was taken, and the tape(s) it wasexported to.

EjectThe action of unloading a tape from a tape drive or off-line storage slot (library) for thepurpose of physically relocating the media to another location.

Introduction

Important terms and definitions 15

ExportThe action of transporting (extracting) a backup from an Avamar server and ultimatelywriting it onto long-term storage media.

External Avamar serversThe Avamar servers (also known as grids) whose backups will be exported to tape. In thisguide, these servers are referred to as “external” to distinguish them from the importserver.

Export policyDefines the schedule on which a group of client backups will be exported to tape byAvamar Extended Retention. The export policy defines the group of clients that share acommon schedule and retention periods for backup metadata and file-level metadata.

ImportThe first phase of performing a restore operation, during which backups are transferredfrom tape to the internal Avamar server instance residing on the Media Access node.

Import serverThe Avamar server that is installed on the Media Access node. Backups are importedfrom tape to this server.

Media Access nodeA 7.8 TB, Gen4 node that has an HBA port, which allows a tape device to be connecteddirectly to the node via fiber-optic cable. Avamar Extended Retention and an instance ofAvamar run on this node.

RestoreThe action of recovering a backup from long-term storage media to a target clientmachine such that the data is returned to its original state at the time the backup wastaken by the original Avamar server.

Retention periodsConfigurable options for backups and the files contained in the backups. The retentionperiod specifies how long the backups and files can be browsed in the system. After aretention period lapses, the backups do not expire until a disaster recovery image iscreated.

SpringboardA control feature that displays in a workspace. Springboards allow you to view status andschedule information, to configure system settings, to view events, logs, and tasks, tomanage users, and to open additional web pages in which you can perform keyconfiguration and administrative tasks within Avamar Extended Retention.

Storage Management SystemThe Avamar Extended Retention software component that manages the library and tapemedia.

WorkspaceA web page in the Avamar Extended Retention user interface that contains springboardsthat are used to perform specific tasks. Currently, the user interface provides threeworkspaces: Administration, Avamar Extended Retention, and My Workspace.

Operational best practicesThe following best practices provide tips for helping to ensure the most efficientoperation of the Avamar Extended Retention system.

Introduction


Creating an administrative user accountThe first time you log in to the Avamar Extended Retention application, you have toprovide credentials for the super user account, suser. This account should be reserved forperforming administrative activities only, such as dealing with emergencies and lockouts.

We recommend that, after you have logged in as suser, you immediately create a newuser account and assign all available roles to the user with the exception of the EMCSupport role, which is for internal purposes only. Instructions for creating user accountsand assigning roles are provided in Creating a user account on page 62 and in Editing auser account on page 63.

Exporting backups to tapeMake sure that the export policy schedules line up with the Avamar backups in such away that exports to tape happen only once after a backup is executed. Instructions forcreating export policies are provided in Creating an export policy on page 45.

After you create an export policy, run it once manually, and then verify that the expectednumber of jobs are running.

1. Open the Task Viewer.

2. When the export policy shows as being in Active state, click the information icon nextto it and make sure that the number of jobs running and waiting match what youexpect.If the number is not what you expect, one option is to increase the number ofmaximum jobs that can run in parallel. This setting is under System Properties in theMedia Access node tab on the Configuration springboard. However, be aware thatincreasing this number directly impacts the performance of the external grids.

Do not run exports during maintenance or blackout windows that are scheduled on theexternal Avamar servers.

Always make sure that the library has labeled media available for exports.

Labeling tape volumesLabel at least two tape volumes as bootstrap tapes. Instructions for labeling bootstraptapes are provided in Labeling volumes on page 39.

Labeling tapes can take time. After initiating a request to label a tape, verify that it hasbeen labeled.

1. Open the Event Viewer and wait for the “Successfully labeled volume xxx” event toappear.

2. In the Media Management page, make sure that the newly labeled tape shows asbeing labeled in the Volumes panel.Volumes that have not been labeled have “unlabeled” in the Volume Name column.

Creating disaster recovery imagesAsk the administrator to set up a cron job to create a disaster recovery imageautomatically when the system is not busy with other tasks, such as exports and imports.Recovery images should be created regularly to ensure that the most current datapossible can be recovered when needed. Instructions for creating a recovery image areprovided in Creating a disaster recovery image on page 98.

Clearing the browser cache before logging in for the first timeIf you have re-installed Avamar Extended Retention, delete the browser cache beforelogging in to the new installation for the first time.

Introduction

Operational best practices 17

Introduction


CHAPTER 2

Getting started


l Supported browsers..............................................................................................20l Using Avamar Extended Retention for the first time............................................... 20l Logging in for the first time....................................................................................20l Accessing workspaces.......................................................................................... 21l Using online help.................................................................................................. 23l Logging out........................................................................................................... 24

Getting started 19

Supported browsersAvamar Extended Retention supports the following web browsers:

l Microsoft Internet Explorer

l Mozilla Firefox

l Google Chrome

Refer to the EMC Avamar Compatibility and Interoperability Matrix for supported browserversions.

Using Avamar Extended Retention for the first timeThe first time you use Avamar Extended Retention, perform the following tasks.

Procedure

1. Log in Avamar Extended Retention, and set up the lockbox password and theframework administrator account as described in Logging in for the first time on page20.

2. In the Administration workspace, create at least one user and assign administratorroles to the user as described in Creating a user account on page 62 and in Editinguser roles on page 65.

3. Access the Avamar Extended Retention workspace, and open springboards asdescribed in The Avamar Extended Retention workspace on page 22 and in OpeningAvamar Extended Retention springboards on page 26.

4. Label volumes in the library as described in Labeling volumes on page 39.

5. Create an export policy as described in Creating an export policy on page 45.

When the exports are running, you can begin monitoring events and tasks, andbrowsing and importing Avamar backups.

Logging in for the first timeThe first time you log in to Avamar Extended Retention, you must set a lockbox passwordand create an administrator account.

Procedure

1. Open a web browser and type the following:

https//:media_access_node_IP_address:7443/imf.actionwhere media_access_node_IP_address is the IP address of the Media Access node onwhich Avamar Extended Retention is running.

The Setup Lockbox Password dialog box opens.

2. Type a lockbox password.

3. Type the password again to confirm it, and click Save Lockbox Changes.

The Create Framework Admin Account dialog box appears.

4. Type the name, email address, and password for the Avamar Extended Retentionframework administrator account, suser.

Getting started


The administrator, suser, will use this password to log in to Avamar ExtendedRetention, and can create additional users within the Administration workspace.

5. Click Save Administrator Account.

The EMC Avamar Extended Retention login screen appears.

6. Type suser in the User Name box, and the password in the Password box.

7. Click Login.

The Administration workspace appears. Instructions for using the workspace areprovided in Chapter 4. Using the Administration Workspace on page 61.

Login-failuresIf you type incorrect login information, an "Authentication Failed" error appears.

Procedure

1. Click OK and type the correct password in the Password box.

If you exceed three login tries without entering the correct login information, an Errordialog box appears with the following message:

This user account has been locked by the system forexceeding the maximum number of unsuccessful login attempts.Please contact an administrator for assistance.

2. If you receive this error, click OK, and contact the administrator to unlock the account.

Results

Each failed login attempt creates a warning security event.

Session timeoutsThe amount of time a logged-in session remains active depends on the session timeoutsetting. The default setting is 45 minutes. No notification appears when a session timesout; however, you cannot interact with the user interface after it has timed out. If thesession times out, you must log back in to Avamar Extended Retention.

Accessing workspacesAvamar Extended Retention provides three workspaces—areas in which to performspecific tasks: Administration, Avamar Extended Retention, and My Workspace. Youselect the workspace that you want to use in the WORKSPACES tab.

Workspaces provide screen space for dialog boxes known as springboards. Thespringboards enable you to perform the tasks that are specific to the workspace you areusing. You can customize each workspace by adding or removing springboards, or bycopying springboards to My Workspace for a more personalized work area.

The Administration workspaceWhen you log in, you see the Administration workspace in the EMC Avamar ExtendedRetention page. This is where you can perform a number of administrative tasks. TheAdministration workspace initially contains the Event Summary, Role Management, andUser Management springboards.

Chapter 4. Using the Administration Workspace on page 61 describes the springboardsand the tasks that you can perform.

Getting started

Login-failures 21

The Avamar Extended Retention workspaceThe Avamar Extended Retention workspace contains springboards that let you managelibrary media, and export and import Avamar backups to and from tape. Chapter 3. Usingthe Avamar Extended Retention Workspace on page 25 describes the springboards andthe tasks that you can perform.

My WorkspaceMy Workspace is a user-defined workspace. Initially, it contains three rectangles, whichrepresent drop zones for springboards. It also provides an area for you to organizefrequently used springboards.

You can customize My Workspace by copying springboards from other workspaces, andby adding springboards to the Springboards list.

Copying springboards from other workspacesYou can copy any of the springboards from the Administration and Avamar ExtendedRetention workspaces to My Workspace.

To copy a springboard to My Workspace, click the house ( ) icon located in the upper-right corner of the springboard.

The springboard now appears in both My Workspace and in the active workspace.

Adding springboards to the Springboards list

You can add more springboards to the Springboards list in My Workspace if needed.

Procedure

1. Select the WORKSPACES tab, and click My Workspace.

The My Workspace screen appears.

2. Select the TOOLBAR tab.

3. Under Springboards, click Edit.

The My Workspace Springboards dialog box opens.

4. Select Administration or Avamar Extended Retention.

A list of springboards that are available for the selected workspace appears in theAvailable Springboards panel.

5. Do the following:

l To include a springboard in the workspace's Springboards list, select thecheckbox next to the springboard's name.

l To exclude a springboard from the workspace's Springboards list, clear thecheckbox next to the springboard's name.

6. Repeat steps 4 and 5 to add springboards from the other workspace as needed.

7. Click OK.

Removing springboards from the Springboards list

You can remove springboards from the Springboards list for My Workspace.

Getting started


Procedure

1. Select the WORKSPACES tab, and click My Workspace.

The My Workspace screen appears.

2. Select the TOOLBAR tab.

3. In the Springboards list, click the “X” icon next to the springboard that you want toremove.

An Alert dialog box appears.

4. Click OK to remove the springboard from the Springboards list.

Using online helpOnline help for Avamar Extended Retention is available in the user interface. You canopen the entire help system, or you can open help topics that are specific to eachspringboard and page.

Avamar Extended Retention online helpYou can view the entire Avamar Extended Retention online help system.

Procedure

1. Click the question mark icon located in the upper right corner of the workspace.

2. Select an option from the menu:

l The Avamar Extended Retention Help option opens the online help for theapplication.

l The About EMC Avamar Extended Retention option opens a dialog box thatcontains copyright and version information about Avamar Extended Retention.

Springboard and page-level helpYou can also view springboard and page-level online help.

l Click the question mark icon in the upper right corner of a springboard to see a helptopic that describes that springboard.

l Click the question mark icon in the upper right corner of a page, and select the pagename to display a topic that explains how to perform the tasks that are available onthat page.

Getting started

Using online help 23

Logging outTo log out of the Avamar Extended Retention interface, click the door icon located in theupper-right corner of the workspace.

Getting started


CHAPTER 3

Using the Avamar Extended Retention Workspace


l Opening Avamar Extended Retention springboards............................................... 26l Managing library media.........................................................................................32l Exporting Avamar backups to tape........................................................................ 43l Browsing and importing Avamar backups..............................................................51l Generating an import and export job history report................................................59

Using the Avamar Extended Retention Workspace 25

Opening Avamar Extended Retention springboardsThe Avamar Extended Retention workspace provides several springboards that you use toperform different tasks. By default, the Import & Restore, Media Management, andScheduled Exports springboards are already open when you access the workspace.

You can select other springboards that you want to appear in the Avamar ExtendedRetention workspace.

Procedure

1. Click the TOOLBAR tab on the left side of the Avamar Extended Retention workspace.

The list of springboards appears.

2. Select the checkbox next to each springboard that you want to appear in theworkspace.

3. After you have selected the springboards, click the TOOLBAR tab again to close it.



The Media Management springboardThe Media Management springboard contains the library that Avamar Extended Retentionmanages.

Managing library media on page 32 describes how to manage the library and the tapemedia.

The Scheduled Exports springboardAfter you have set up the tape media, you can create export policies and begin usingAvamar Extended Retention to export Avamar backups to tape. You can create, manage,and run export policies on the Export Policy Management page, which opens when youclick Configure Export Policies on the Scheduled Exports springboard.

The springboard also lists the export jobs that are scheduled to run in the next 24-hourperiod.

Exporting Avamar backups to tape on page 43 describes how to create and work withexport policies.

The Import & Restore springboardAfter you have exported Avamar backups to tape, you can locate specific backups, andimport them to the internal Avamar server on the Media Access node. You can alsochange the retention dates for backups as needed.

The Browse Exported Backups button on the Import & Restore springboard opens theBackup Browse/Import page, where you browse and import Avamar backups.


The Media Management springboard 27

Optionally, on the springboard itself, you can filter backups by client name and daterange before accessing the Backup Browse/Import page. Or, if you prefer, you can specifyfilter criteria after you access the page.

Browsing and importing Avamar backups on page 51 describes how to locate andimport Avamar backups.

The Configuration springboardThe Configuration springboard displays information about the Avamar servers and theMedia Access node. The Avamar Servers tab in the springboard displays the Avamargrids that are being used by Avamar Extended Retention.

The Media Access node tab contains two sections: Import Server and System Properties.The Import Server section displays information about the Media Access node.



The System Properties section allows you to set the maximum number of jobs that can berun concurrently against the Avamar server. It also allows you to test EMC Call Home.

The Recent Events springboardThe Recent Events springboard lists the twenty most-recent events that are associatedwith the Avamar Extended Retention’s storage management system, which manages thelibrary and tape media.

The Recent Events springboard displays icons that indicate the severity of each event.The following table describes these icons.


The Recent Events springboard 29

Table 1 Event severity icons

Icon Description

Informational event.

Warning event.

Severe event.

Critical event.

The Launch Event Viewer button opens the Event Viewer, which contains all of the eventsin the system. To see the most recent events, go to the last page of the viewer.

Detailed information about the Event Viewer is provided in System events on page 70.You can also click the question mark icon in the upper right corner of the Event Viewer toaccess online help.

The Task Monitoring springboardThe Task Monitoring springboard displays Avamar Extended Retention tasks and theircurrent states.

To filter the tasks by state, select a state in the Task State list. The possible task statesinclude All, Scheduled, Running, Completed, Failed, and Canceled.

The Task Monitoring springboard displays icons that indicate the type and the state ofeach task. The following table describes the icons used to indicate task type.



Table 2 Task type icons

Icon Description

A backup is being exported to tape.

A backup is being imported from tape.

The Import server is being cleansed.

The following table describes the icons used to indicate task state.

Table 3 Task state icons

Icon Description

The task has completed.

The task is scheduled.

The task is running.

The task was canceled.

The task failed.

The Launch Task Viewer button opens the Task Viewer, which displays all of the tasks. Tosee the most recent tasks, go to the last page of the viewer.

Tasks on page 73 provides detailed information about the Task Viewer.


The Task Monitoring springboard 31

The Import & Export Job History springboardThe Import & Export Job History springboard lets you generate a report for jobs of aspecified type and state that have run within a certain date range.

Managing library mediaManaging library media involves working with tape pools, retention periods, and tapevolumes. You manage library media in the Media Management page, which is accessedby clicking Manage Export Media on the Media Management springboard in the AvamarExtended Retention workspace.

The Media Management page is shown in the following figure.

You should see only one library in the Libraries panel.



Note

If you need to add or remove a library drive after the system has been configured, youmust contact EMC Professional Services.

To view details about the library, select the library in the Libraries panel. Informationabout the library appears in the Library Details panel.

The following table describes the library details.

Table 4 Library Detail descriptions

Detail Description

Name The name of the library, followed by the fully qualified domain name.

Type The type of library. Values can be NDMP, SILO, SCSI, UNKNOWN.

SCSI Address The library's SCSI address: SCSI bus, device ID, and Logical Unit Numberrespectively. If the library has a Type of Silo, SCSI Address is not shown.

Status The library's status: either ONLINE or OFFLINE.


Managing library media 33

Table 4 Library Detail descriptions (continued)

Detail Description

Managed Indicates whether or not the library is being managed by AvamarExtended Retention: either true or false

Model The library's model.

Number of Devices The number of tape drives that the library has, the drives themselves, andthe status of each drive.

Number of Import/Export Slots

The number of slots in the library that are used for importing andexporting Avamar backup data.

Working with custom tape poolsAvamar Extended Retention uses tape pools to organize the volumes on which an exportpolicy’s backups will be stored.

From the Media Management page, you can create custom tape pools that can beassigned to export policies. You can also edit and delete custom tape pools asnecessary.

To create, edit, and delete custom tape pools, click the expand + button beside Pools inthe Media Management page as shown here.

The Pools panel expands.

Two default system pools exist: Avamar Tape and Default. The Avamar Tape poolcontains volumes that have not been assigned to another pool, and the Default poolcontains bootstrap tapes. You cannot edit or delete the system pools.



Note

If the pools do not appear in the list, click Refresh.

Any custom tape pools that you create will also be listed in the Pools panel.

The following sections describe how to view the details of and the volumes contained inany pool, and how to create, edit, and delete custom tape pools.

Viewing the details of a tape poolTo view the details about a tape pool, select the pool in the list. The Pool Details panelopens underneath the list.

Viewing the volumes in a tape poolIn the Pools panel, select the pool whose volumes you want to see.

The volumes contained in the pool appear in the Volumes panel on the right-hand side ofthe Media Management page.


Working with custom tape pools 35

Creating a custom tape poolYou can create a custom tape pool, and assign it an existing custom or default retentionperiod.

Procedure

1. In the Pools panel, click Create Pool.

The Create Custom Tape Pool dialog box appears.

2. Type a name for the pool in the Name box.

Note

Pool names do not support the use of international characters. Use ASCII characterswhen naming a pool.

3. Leave the Enabled box checked if you want to be able to assign volumes to this pool.

4. Optionally, select a period in the Retention Period list.

You can use one of the default retention periods or a custom one that you havecreated. Instructions for creating custom retention periods are provided in Workingwith custom retention periods on page 37.

Note

The retention period that you assign to a pool takes precedence over any retentionperiod that is defined for an export policy. Therefore, if you assign a pool to an exportpolicy, the pool’s retention period will be used. Conversely, if the pool does not havea retention period, the export policy’s retention will be used.

5. Optionally, type some information about the pool in the Comment box.

6. Click Create Tape Pool.

7. Click OK when you see the Success message.

The new tape pool appears in the list of pools.

Editing a custom tape poolYou can edit the retention period and comments only for custom tape pools that do notcontain volumes. You cannot edit the name of a pool, the Avamar Tape and Default pools,nor custom pools that contain one or more volumes.

Procedure

1. In the list of pools, select the pool that you want to edit, and click Edit Pool.

The Edit Tape Pool dialog box appears.

2. Modify the Retention Period and Comment entries as needed.

3. Click Edit Tape Pool.




Deleting a custom tape poolYou can delete only custom tape pools that do not contain any volumes. You cannotdelete the Avamar Tape and Default pools.

Procedure

1. In the list of pools, select the empty pool that you want to delete, and click DeletePool.

2. Click Yes when you are asked to confirm the deletion.


The pool is removed from the list of tape pools.

Working with custom retention periodsAvamar Extended Retention uses retention periods to control how long the backups thathave been exported to tape can be viewed, imported, and restored. Retention periodscan be assigned to the backups that are specified in export policies and to custom tapepools.

Note

When a retention period lapses, the backups do not expire until you create a disasterrecovery image. See Creating a disaster recovery image on page 98.

From the Media Management page, you can create custom retention periods that can beassigned to export policies and tape pools. You can delete custom retention periods asnecessary.

To create and delete custom retention periods, click the + button beside Retentions inthe Media Management page as shown here.

The Retentions panel expands. Twelve default system retention periods exist by default,as shown in the following figure. You can assign these retention periods to custom tapepools and to export policies, but you cannot delete them.


Working with custom retention periods 37

Note

If the retention periods do not appear in the list, click Refresh.

Any custom retention periods that you create will also be listed in the Retentions panel.

The following sections describe how to view the details of a retention period, and how tocreate and delete custom retention periods.

Viewing the details of a retention periodTo view information about a retention period, select the retention in the list.

The Retention Details and Pools panels appear on the right-hand side of the MediaManagement page. The Retention Details panel provides details about the retentionperiod, and the Pools panel provides information about the tape pools that use theretention period.

Creating a custom retention periodYou can create custom retention periods that you can apply to tape pools and to exportpolicies.

Procedure

1. In the Retentions panel, click Create Retention.

The Create Custom Retention Period dialog box appears.

2. Type a name for the retention period in the Name box.

3. Select a number and a duration in the Period lists.

4. Click Create Retention Period.


The new retention period appears in the list of retentions.



Deleting a retention periodYou can delete only custom retention periods that are not being used by a tape pool. Youcannot delete any of the default system retention periods.

Procedure

1. In the Retentions panel, select the custom retention period that you want to delete.

2. Click Delete Retention.

3. Click Yes when you are asked to confirm the deletion.


The retention period is removed from the list of retentions.

Working with tape volumesThe following sections describe the tasks that you can perform with the tape volumescontained in the library.

Labeling volumesYou must label the volumes in the library that you want to use as export tapes, and youmust also label at least one volume as a bootstrap tape. The bootstrap tape is used fordisaster recovery purposes.

Note

Labeling media takes time. The Event Viewer states that the labeling is queued; however,the amount of time required to label the media depends on the library’s current activity.

Procedure

1. In the Media Management page, select the library in the Libraries panel.

The volumes in the library are displayed in the Volumes panel. Any volumes that havenot been labeled are indicated as unlabeled.

2. Click Label Media.

The Label Media dialog box appears. It contains a list of the volumes in the librarythat have not been labeled.

3. Select the checkboxes beside the volumes that you want to label for export.

4. Under Label for export, select the tape pool in which you want the volumes to becontained.

Note

Instructions for creating tape pools are provided in Working with custom tapepools on page 34.



The Label Media dialog box closes, and the selected volumes are named using thecorresponding barcode.

7. In the Media Management page, click Label Media again.

8. In the Label Media dialog box, select at least one volume that you want to use as abootstrap tape.


Working with tape volumes 39

Note

Bootstrap tapes are put into the Default tape pool, and are used to back up the mediamanagement and file databases. In the event you need to recover data, you canperform disaster recovery procedures using these tapes.

9. Select Label for bootstrap (“Default” pool), and then click Label Media.

10.Click OK when you see the Success message.

Relabeling volumes to a different tape pool (not recommended)The Label Media dialog box gives you the ability to relabel a volume into a different tapepool. However, if you do this, be aware of the negative consequences.

Note

If you relabel a volume to a different tape pool, all non-expired backups on that volumewill be removed. RELABELING VOLUMES IS NOT RECOMMENDED.

Procedure

1. In the Media Management page, select the library in the Libraries panel.


The Label Media dialog box appears. All of the volumes in the library that have notbeen labeled are listed.

3. Select Display all labeled and unlabeled volumes.

All volumes in the library are listed, and the Pool column appears. Volumes with anentry in the Pool column are labeled into the respective pool.

4. Select one or more volumes that you want to relabel.

5. Select the new pool in the Label for export list.


7. Click Yes when you see the first Relabeling Volume warning message.

8. Click Yes again to reconfirm your decision in the second warning message.


Viewing the tape volumes in the libraryTo view the tape volumes in the library, select the library in the Libraries panel. The tapevolumes contained in that library appear in the Volumes panel.

The following table describes the columns in the Volumes panel.

Table 5 Volumes panel columns

Column Description

Volume Name The name of the volume. Volumes that have not yet been associatedwith the Avamar Tape pool are designated as unlabeled. See Labelingvolumes on page 39 for instructions on associating volumes with thepool.

Barcode The barcode of the tape volume.

Pool The tape pool to which the volume has been assigned.



Table 5 Volumes panel columns (continued)

Column Description

Location The name of the library in which the volume is contained.

% used The percentage of the volume that is being used.

Expiration The date the data on the volume expires.

Last Access Time The last time the volume was accessed.

Viewing the backups on a tape volume

The Show Backups button allows you to view the backups on a tape volume.

Procedure

1. Select the library in the Libraries panel.

The volumes in the library are listed in the Volumes panel.

2. Select the volume whose backups you want to see.

3. Click Show Backups, located in the upper-right corner of the panel.

The Backups panel appears. It contains the backups that are on the selected volume.

The following table describes the columns in the Backups panel.

Table 6 Backups panel columns

Column Description

Backups The name of the backup.

Plug-In The file system running on the client from which the backup wascreated.

Volume(s) The volume or volumes on which the backup resides.

Client Name The name of the client from which the backup was created.

Avamar Grid The name of the Avamar Grid that created the backup.

Backup Expiration The date and time the backup will expire.

Avamar Backup Date The date the backup was created by Avamar.

Export Timestamp The date and time the backup was exported to tape.

Ejecting tape volumes

The Eject Tape(s) button allows you to eject one or more tapes from the library.

Procedure

1. Select the library In the Libraries panel.

2. In the Volumes panel, select one or more volumes.

3. Click Eject Tape(s).

4. If at least one of the tapes that you are ejecting is labeled, you see the Eject Tape(s)dialog box shown in the following figure. Optionally, type a description of where themedia will be stored after it is ejected, and then click Yes.


Working with tape volumes 41

5. If the tapes that you are ejecting are not labeled, you see the following dialog box.Click Yes to eject the tape.

Note

If another tape is in the drive when you try to eject one or more tapes, the tapes thatthe you selected cannot be ejected. An error appears.

Inventorying the contents of the libraryYou can inventory the entire contents of the library, or you can inventory selectedvolumes. Each volume that you inventory is mounted to a free drive, its barcode isscanned, and its header is read. The inventory updates the Avamar Extended Retentiondatabase tables.

Note

In most instances, an inventory is not required. However, if you do have to inventory thelibrary, make sure that the library is idle when the inventory takes place. If you try toinventory the library while the robot is busy performing an import or export, the inventorywill fail.

The inventory process can take a long time. If the library has only one drive, no backupsand restores can occur while the inventory is taking place.

Procedure


2. Click Inventory.

The Inventory Library dialog box appears.

3. In the Inventory Library dialog box, do one of the following:

l Select Inventory entire library.

l Select Inventory the given slots, and then type the slot numbers in the box.Separate individual slots with commas, and use a dash to type a range of slots. Forexample:

3, 4, 6-9



Note

If you enter invalid slot numbers, you receive an error such aserr.action.exception, server could not complete yourrequest.

4. Click Inventory.

A progress bar appears.


Exporting Avamar backups to tapeExporting Avamar backups involves creating and managing export policies that runscheduled exports of Avamar backup data to tape. You can also perform on-demandexports. You perform these tasks in the Export Policy Management page, which isaccessed by clicking Configure Export Policies on the Scheduled Exports springboard inthe Avamar Extended Retention workspace.

The Export Policy Management page is shown in the following figure.


Exporting Avamar backups to tape 43

Viewing Avamar server and export policy detailsOn the Export Policy Management page, you can view detailed information about theAvamar servers and the export policies that have been created for the servers.

Viewing Avamar server detailsTo view the details about an Avamar server, select the server in the Avamar Serverspanel. Information about the server appears beneath the panel.

The following table describes the Avamar server details.

Table 7 Avamar server details

Detail Description

Name The hostname of the server.

Total Capacity The total capacity of the server and the number of megabytes being used.

Status The status of the server. Statuses can be:FULL_ACCESS: The Avamar server is in its normal operating state.

SUSPENDED: Normal operations have been suspended temporarily.

ADMIN ONLY: The Avamar server is in an administrative state in which onlythe server or root user can read or write data.

READ ONLY: The Avamar server is in a read-only administrative state inwhich all users can read data, but writing data is not allowed.

Server Version The Avamar software version running on the server.

IP Address The IP address of the Avamar server.

Viewing export policy detailsYou can view all of the export policies that have been created for an Avamar server. Youcan also display a policy's summary and the list of clients that are associated with thepolicy.

Procedure

1. In the Avamar Servers panel, select the server for which you want to view the existingpolicies.

The export policies that have been created for that server are listed in the ExportPolicies panel.

2. To view a policy's summary, select a policy in the list.

The Policy Summary panel opens from the right-hand side of the page.

3. To see the clients associated with a policy, select the policy in the list, and clickPreview Policy Clients.

The All Avamar Clients Included in Policy dialog box opens. It lists all of the clientsthat are included in that export policy.



Creating an export policyExport policies determine what plug-ins, domains, groups, and clients on an Avamarserver are backed up, when they are backed up, and how long backups are kept.

Export policies may include VMware container clients (Resource Pool, Folder, and vApps)either explicitly or through a domain or group. When a policy includes one of theseVMware container clients, backups of VMs directly under the container client will beexported. If the container is a Resource Pool or Folder, vApps directly under the containerwill also be clients.

Note

For Avamar Extended Retention systems that are attached to a library that has only onedrive, exports that are started while an import is in progress will fail due to drivecontention.

Procedure

1. In the Avamar Servers panel, select the server for which you want to create the policy.

2. Click Create Policy.

Results

The Create a New Export Policy wizard opens and displays the Policy Details screen,which is the first of five screens that you will use to create the policy.The wizard screens include:

l Policy Details

l Export Schedule

l Avamar Client Filter

l Avamar Backup Filter

l Summary & Save

Configuring policy detailsIn the Policy Details screen, you configure a name for the export, and the backupretention period.

Procedure

1. Make sure that the Active option is selected. This option should be selected bydefault.

If you clear the Active option, the export policy cannot be run.

2. In the Policy Name box, type a name for the policy.

Policy names must contain no more than 200 characters.

3. In the Pool Name list, select a tape pool. The backups in this policy will be exported tovolumes that are in this pool.

If you select a pool that does not have a retention, the Backup Retention list appears,and you can optionally select a retention period for the policy.

4. Optionally, type a note about this policy.

5. Click Next.

The Export Schedule screen appears.


Creating an export policy 45

Configuring the export scheduleIn the Export Schedule screen, you configure the schedule on which exports will occur forthis policy. You specify the frequency at which the schedule will run, and you configuredetailed settings based on the selected frequency.

Note

The export schedule that you create is based on the Avamar Extended Retention servertime.

Procedure

1. Select a Frequency option.

The frequency option that you select determines the configuration options that appearon the right side of the screen.

l The Regular Intervals frequency lets you schedule the export to run at regularintervals; every specified number of days, weeks, or months.

l The Specific Weekdays frequency lets you schedule the export to run on a specificday each week.

l The Nth Day of each Month frequency lets you schedule the export to run on aspecific weekday of each month.

l The Specific Date each Month frequency lets you schedule the export to run on aspecific date each month.

l The On Demand frequency does not have configuration options.

2. Configure the options for the selected frequency.

After you have configured the export frequency, the next five scheduled exports areshown in the lower panel of the Export Schedule screen.

3. Click Next.

The Avamar Client Filter screen appears.

Configuring the Avamar client filterIn the Avamar Client Filter screen, you select the domains, groups, and clients that will beincluded in this export policy.

Procedure

1. Click Create/Edit Client Filter.

The Avamar Domains, Avamar Groups, and Avamar Clients panels expand from theleft side of the screen.

2. In the Avamar Domains panel, select a domain.

Any client groups and clients that are associated with that domain appear in theAvamar Groups and Avamar Clients panels respectively.

3. To include a domain and its clients in the policy, click and drag the domain to theIncluded Avamar Domains panel.



Note

When you drag a domain to the Included Avamar Domains panel, its subdomains arenot included in the export policy. You must drag each domain and subdomainseparately.

When you include domains and subdomains in a policy by dragging them to theIncluded Avamar Domains panel, the clients in those domains and subdomains arealso included in the policy.

4. In the Avamar Groups panel, select one or more groups (if they exist), and drag themto the Avamar Groups panel on the right.

When you select a group, all of the backups for the clients that belong to that groupwill be included in the export policy.

5. In the Avamar Clients panel, optionally select one or more clients, and drag them tothe Explicit Avamar Clients panel.

Note

You can include specific clients in the policy even if you do not include the clients’domain.

Clients in the Explicit Avamar Clients panel will be backed up even if they are removedfrom the selected domain or client group at some point in the future.

6. If you need to remove a domain, client group, or explicit client from the policy, select itin the respective panel on the right side of the screen, and drag it back to thecorresponding panel on the left.

7. If you want to clear all of the selections and start over creating the client filter, clickClear Client Filter.

8. To see a summary of the selections, click Preview Client Filter.

The Preview Client Filter dialog box appears.

9. When you have finished creating the client filter, click Next.

The Avamar Backup Filter screen appears.

Configuring the Avamar backup filterIn the Avamar Backup Filter screen, you select the client backups that will be exported totape when the policy runs. You can select to export only the most recent backup, or youcan select a range of backups that will be exported to tape when the policy runs.

Procedure

1. In the Backup Types panel, select a backup type.

Note

Untagged backups are those that were run manually in Avamar.

2. If you want to export multiple backups rather than just the most recent one:

a. After selecting the backup type, select Enable Multiple Backups in the MultipleBackups panel.

b. Select the number of hours prior to the most recent backup.

All backups that occurred during the time between the most recent backup and thetime specified will be included in this export policy.


Creating an export policy 47

Note

You must configure the multiple backup feature for any plug-in that requires multiplebackups for a full restore. For example, you must do this for exporting and importingOracle CLI database backups.

3. In the Avamar Plug-ins panel, select one of the options:

l Include backups for all Avamar plug-in types into the Export Policy. Select thisoption if you want to include all Avamar plug-ins that meet the filter criteria in thispolicy.

l Include only backups for the specific plug-in types into the Export Policy. Selectthis option if you want to include only backups from specific plug-ins. Then selectone or more plug-ins in the Select Avamar Plug-Ins to Include panel, and dragthem to the Included Avamar Plug-Ins panel. (Press and hold the Ctrl key to selectmultiple plug-ins.)

To remove a plug-in from the Included Avamar Plug-Ins panel, select the plug-in,and drag it back to the Select Avamar Plug-Ins to Include panel.

4. Click Next.

The Summary & Save screen appears.

Viewing the export policy's summaryThe Summary & Save screen provides a configuration summary of the export policy thatyou are creating.

Procedure

1. Review the export policy configuration.

2. If you need to make changes to the policy, navigate back through the Create a newExport Policy wizard using the Prev button or the bread crumbs located at the top ofthe screen (shown in the following figure).

3. When you are satisfied with the export policy, click Finish & Save.

The Create a new Export Policy wizard closes, and the new policy is listed in theExport Policies panel on the Export Policy Management page.

Note

If the library drives are busy when an export is scheduled to run, the export will fail if adrive does not become available within 30 minutes. The failure appears in the EventViewer. You must perform an on-demand export when a drive becomes available.



Editing an export policyYou can edit the export policies that you have created when you need to update policydetails, export schedules, and Avamar backup and client filters.

Note

You must edit an export policy when changes that affect that policy have been made tothe tree structure in the Avamar Administrator Management Console. Such changes caninclude moving clients, and changing, adding, or deleting groups and domains. Thesechanges are not reflected dynamically in the Avamar Extended Retention user interface;therefore, you must update the policy manually to reflect these changes.

If you do not update the policy to match the changes in Avamar, the policy will fail when ittries to run.

Procedure

1. In the Export Policies panel, select the policy that you want to edit.

2. Click Edit Policy.

The Editing 'policy_name' wizard opens to the policy's Summary & Save screen.

3. Navigate through the wizard using the Prev button or the bread crumbs located at thetop of the screen (shown in the following figure).

4. Edit the policy as needed, and then click Finish & Save.

Activating or deactivating an export policyYou can deactivate an export policy if you want to prevent if from running, but do notwant to delete it. You can re-activate it later when you want it to resume its exportschedule.

In the Export Policies panel, policy statuses appear in the Active column: Yes for currentlyactive, and No for currently deactivated.

Procedure

1. In the Avamar Servers panel, select the server for which you want to activate ordeactivate a policy.

The policies associated with that server appear in the Export Policies panel.

2. Select the policy that you want to activate or deactivate.

3. Click Activate/Deactivate Policy.

The Activate/Deactivate Policies dialog box opens.

4. In the Action list, select Activate or Deactivate, and then click Save.

The policy’s status changes in the Active column.


Editing an export policy 49

Deleting an export policyThe Delete Policy button allows you to delete a selected export policy.

Procedure

1. In the Avamar Servers panel, select the server for which you want to delete the policy.

The policies associated with that server appear in the Export Policies panel.

2. Select the policy that you want to delete.

3. Click Delete Policy.

4. Click Yes when you see the message asking you to confirm the deletion.

Performing on-demand exportsYou can perform an on-demand export on a policy or on an individual client that isincluded in a policy.

An on-demand export request starts the export immediately unless the export policy isinactive or another export job is currently running. If another job is currently running, theon-demand export will run immediately after it has finished.

Performing policy on-demand exportsA policy must be active for an on-demand export to be performed. You cannot perform anon-demand export on a policy that is inactive.

Procedure

1. In the Avamar Servers panel, select the server for which you want to perform theexport.

The export policies that exist for that server are listed in the Export Policies panel.

2. In the Export Policies panel, select the policy for which you want to perform theexport.

3. Make sure that the Active column for the policy contains Yes.

4. Click Perform On-Demand Export.

5. Click Yes when you see the message asking you to confirm the execution of the policy.

Performing client on-demand exportsThe policy that includes the client must be active for an on-demand export to beperformed. You cannot perform an on-demand export for a client when the parent policyis inactive.

Procedure

1. In the Avamar Servers panel, select the server for which you want to perform theexport.

The export policies that exist for that server are listed in the Export Policies panel.

2. In the Export Policies panel, select the policy for which you want to perform theexport.

3. Click Preview Policy Clients.

The Preview Clients for 'policy' dialog box appears.

4. In the Preview Clients dialog box, select the client for which you want to perform theon-demand export.



5. Click Perform On-Demand Export.

6. Click Yes in the confirmation message.

Viewing export job details for active policies in the Task ViewerOnce an export policy begins executing, it will show as running in Active state in the TaskMonitoring springboard. You can view details about the job by clicking Launch TaskViewer on the springboard to open the Task Viewer, and then clicking the Details iconbeside the task.

An export policy can contain multiple export jobs, some of which can run concurrently.The number of jobs that can run at the same time depends on the Maximum Parallel Jobssetting, which is described in The Configuration springboard on page 28.

In the Task Viewer, you can see details about how many jobs within the export policy arerunning, how many are waiting to run, and how many have completed.

The information you see depends on the number of export jobs within the policy, andhow many jobs can run concurrently. For example, if an export policy contains threeexport jobs and Maximum Parallel Jobs is set to 2, the task details might containinformation similar to the following:

2 running, 1 waiting to run, 0 completedIn another example, if four policies are running at the same time and Maximum ParallelJobs is set to 2, the task details for two of the policies might contain information similarto the following:

1 Running, 0 waiting, 0 completedThe details for the remaining two policies might say something like this:

0 running, 1 waiting to be run, 0 completed

Browsing and importing Avamar backupsBrowsing and importing Avamar backups is done from the Backup Browse/Import page,on which you can locate and import the Avamar backups that have been exported totape. You can also edit retention periods and reset the import server.

You access the Backup Browse/Import page by clicking Browse Exported Backups on theImport & Restore springboard. If preferred, you can select a client and a date range in thespringboard before you open the Backup Browse/Import page. If you do this, only thatclient’s backups that were exported during the selected date range will be listed in theBackup Browse/Import page.

The Backup Browse/Import page is shown in the following figure.


Viewing export job details for active policies in the Task Viewer 51

The panels in the Backup Browse/Import page are described as follows:

l The Filter Clients panel lets you search for specific clients. You can type a client nameif you know it, or you can use a wildcard character to list multiple clients. The clientsthat meet the criteria appear in the Avamar Clients panel.

l The Avamar Clients panel lists the clients that match the filter criteria.

l The Import Server panel contains information about the Media Access node on whichAvamar Extended Retention is running.

l The Backup panel lists the backups that are associated with the selected client. Customizing columns in the Backup panel on page 56 provides instructions forcustomizing the columns that display and for sorting the information they contain inascending and descending order.

The following table describes the columns in the Backup panel.

Table 8 Backup panel columns

Column Description

Original Client The hostname of the client from which the backup was created.

Backup The name of the backup as it is known by Avamar Extended Retention.

Plug-in The type of file system running on the client from which the backup wascreated.

Volume(s) The volume or volumes in the library to which the backup was exported.

Size The size of the backup.

Pool The pool that contains the volume(s) on which the backup is located.

Policy The name and identifier of the export policy that initiated the backup.Backups that are associated with policies having the same name andidentifier were exported together when the policy ran.



Table 8 Backup panel columns (continued)

Column Description

For example, in the following figure, the backups that are associatedwith the first two policies in the list were exported together.

Avamar Grid The IP address of the Avamar grid on which the client was activatedwhen it was backed up.

Backup Expiration The date and time the backup will expire.

Avamar Backup Date The date and time the backup was created by the Avamar server towhich the client was activated.

Export Timestamp The date and time the backup was exported to tape by AvamarExtended Retention.

Restore limitationsAvamar Extended Retention does not support the following Avamar advanced restoreoptions:

l Granular-level restore for:

n Exchange

n Microsoft Office SharePoint Server

n Hyper-v

l File-level restore for VMware image-level backups

l Change block-based restores for:

n Linux

n VMware image-level backups

l Multi-stream restore for:

n Windows VSS Exchange

n Hyper-v

n Microsoft Office SharePoint Server

l Sub-volume and Sub-database restores through the Avamar Management Console's“browse for restore” feature


Restore limitations 53

Locating exported backupsIn the Backup Browse/Import page, you can view all the exported Avamar backups for theclient that you select. You can also narrow down the list of Avamar backups by usingseveral filter criteria.

Tips for locating exported VM backupsWhen you run an export policy that includes a vApp client, a backup is exported foreach first-level VM in the vApp. You can then import these VM backups individually.(You cannot import the vApp itself.)

You can filter the list of backups for a particular vApp name to list the exported VMbackups associated with the vApp. When you filter on the vApp name, each backupdisplayed in the list begins with the name of the vApp and ends with the name of theVM backup. You can then sort the Policy column to group the backups that wereexported in the same policy run.

Finally, display the Original Client column in the Backup panel to see which VM abackup is from. Customizing columns in the Backup panel on page 56 providesinstructions for selecting the columns that are displayed.

Procedure

1. In the Filter Clients panel in the Client Name box, type an asterisk (*) to list all clients,or type part of a client name using one or more asterisks as wildcard characters.

Note

If you type the entire client name and the system is unable to make a complete match,the client will not be listed in the Client Name panel. Using an asterisk in the searchcriteria is highly recommended.

2. Press Enter or click Apply.

The clients that match the filter criteria appear in the Avamar Clients panel.

3. In the Avamar Clients panel, select the client whose backups you want to see.

The backups for that client appear in the Backup panel. By default, the list of backupscontains those that were exported during the previous 3-month period.

4. If you want to see the backups that were exported during a different time frame, or ifyou want to use additional filter criteria, click Filter to display filter options.

5. Type and select the filter criteria, and then click Apply.

You can use an asterisk as a wildcard character when typing a Backup Name, anOriginal Client, a Policy Name, and a Grid Server Name.

Note

To remove the filter, click Clear, and then click Apply.

6. Browse through the backups to locate the backup(s) that you want to import.



Importing backups from tapeYou can import a full backup or a partial backup, if available, from tape. Avamar ExtendedRetention retrieves the full or partial backup from tape, and imports it to the Avamarserver that is installed on the Media Access node.

From there, you can restore it to a client as described in Restoring imported backups to aclient on page 58.

Note

For Avamar Extended Retention systems that are attached to a library that has only onedrive, an import that is started while an export is in progress will fail due to drivecontention.

Procedure

1. Locate the backup that you want to import as described in Locating exportedbackups on page 54.

2. In the Backup panel, select the backup, and click Import From Tape.

One of three possible Import From Tape dialog boxes opens.

l For backups that were exported using the latest version of Avamar ExtendedRetention, the following dialog box opens. These backups support partial imports.Select the item or items that you want to import, and then click Import.

Note

When you select a parent item in the tree structure, everything below it isautomatically selected.

l For backups that were exported using the previous version of Avamar ExtendedRetention, the following dialog box opens. If you want to perform a partial import,click Build Partial Import File. If you want to import the entire backup, click Import.


Importing backups from tape 55

l For backups that do not support partial imports, the following dialog box opens.Click Import to import the full backup.

3. Click OK, and then click OK again when you see the success message.

Note

If the library drives are busy when you request an import, the import will fail if a drivedoes not become available within 30 minutes. The failure appears in the EventViewer, and you must resubmit the import request.

4. When the import has completed, use the instructions in Restoring imported backupsto a client on page 58 to restore the backup to a client.

Customizing columns in the Backup panelIn the Backup panel, you can select the columns that you want to view. You can also sortthe information in the columns in ascending or descending order.

Sorting in ascending or descending orderYou can sort the information in each column in ascending or in descending order.

Procedure

1. Mouse over the name of a column in the Backup panel.

A down-arrow appears beside the name.

2. Click the down-arrow to display the menu.



3. Select a sort option in the menu.

Selecting columns to viewYou can select which columns you want to view in the Backup panel.

Procedure

1. Mouse over the name of a column in the Backup panel.

A down-arrow appears beside the name.

2. Click the down-arrow to display the menu, and then click Columns.

The list of available columns appears.

3. Click the checkboxes beside the columns that you want to view.

4. Clear the checkboxes beside any column that you want to hide.


Customizing columns in the Backup panel 57

Editing backup retention periodsThe backup retention period specifies how long backups that have been exported to tapewill be kept. When you edit the backup retention period, you can select another retentionperiod, or you can expire the backup now.

Note

If you choose to expire a backup now, the backup will still be visible in the AvamarExtended Retention interface. Backups do not expire until you create a disaster recoveryimage (see Creating a disaster recovery image on page 98). Once a disaster recoveryimage is created, expired backups will no longer be visible in the Avamar ExtendedRetention interface.

Procedure

1. Select one or more backups in the Backup panel. (Press and hold Shift to select agroup of consecutive backups or Ctrl to select multiple non-consecutive backups.)

2. Click Edit Backup Retention.

The Edit Backup Retention Period dialog box appears.

3. If you want to configure a new backup retention period, select the Select a newretention period in the list option, then click the down-arrow and select a time periodin the list.

4. If you want the backup to expire immediately, select the Expire retention period nowoption.

5. Click Save.

Resetting the Import ServerPeriodically, you need to reset (or cleanse) the Avamar server that is installed on theMedia Access node in order to make room for new imports. Resetting the server removesall previous backups that have been imported from tape.

Procedure

1. Click Reset Import Server.

2. Click OK in the Reset Import Server confirmation message.

Note

You cannot cancel a reset request after you have submitted it.

Restoring imported backups to a clientAfter a backup has been imported, you must perform the following tasks to restore thebackup to its original client or to another location:



l Install the Avamar Administrator from the Media Access node's Avamar server on themachine you are using to perform backups and restores.

l Identify the Avamar clients to which you are planning to restore backups, and activatethem to the Media Access node's Avamar server.

l Use the Avamar Administrator to restore the backups to a client.

Note

The EMC Avamar Administration Guide contains instructions for performing these tasks.

Generating an import and export job history reportFrom the Import & Export Job History springboard, you can generate a report that showsthe import and export jobs that have run within the specified date range.

You can generate a report that contains information about all import and export jobs thatcompleted, failed, or were canceled, or you can filter the jobs by type and state beforegenerating the report. You can also specify a date range for the jobs that are included inthe report.

Procedure

1. In the Import & Export Job History springboard, select a Job Type.

You can select Both (the default), to generate the report for both export and importjobs, or you can select Export or Import to generate the report only for the respectivejob type.

2. Select a Job State.

You can select All (the default) to generate the report for jobs that are in any state, oryou can select Completed, Failed, or Canceled to generate the report only for jobs inthe respective state.

3. If you want to filter the report by tape pool, select Filter Pool. Click the Pool Name textbox to open the list of pools, and then select a pool.

4. Type a From: date and a To: date to specify the range of dates when the jobs ran.

The default range is today's date.

5. Click Generate Report to see the report immediately, or click Generate XML Report tocreate the report in XML format.

The following figure shows part of an example Import and Export Job History reportthat was filtered for the AvamarTape pool.


Generating an import and export job history report 59

CHAPTER 4

Using the Administration Workspace


l User management................................................................................................. 62l Role management................................................................................................. 64l User profile management...................................................................................... 66l System configuration............................................................................................ 67l System events.......................................................................................................70l Tasks.................................................................................................................... 73l Security events......................................................................................................76l Log information.....................................................................................................78

Using the Administration Workspace 61

User managementAs an Avamar Extended Retention administrator, you manage other users through theUser Management springboard, shown below. This springboard allows you to create,edit, and disable user accounts. It also lets you unlock the accounts of users whoseaccounts were locked after three failed login attempts.

Searching for a userThe User Management springboard allows you to search for and display users who matchthe search criteria.

Procedure

1. Type the user’s last name in the Name (last, first) box.

2. If you want to include the first name, type a comma and a space after the last name,and then type the first name.

Users whose names match the search criteria are listed under Name.

Creating a user accountAnyone who logs in to Avamar Extended Retention must have a user account. By default,all new user accounts have the User role.

Procedure

1. In the User Management springboard, click Create User.

The Create User dialog box appears.

Note

Red asterisks indicate required information.

2. In the User Name box, type a unique name.

Maximum length is 32 alphanumeric characters. Do not use special characters, orleading or trailing spaces. The username is case insensitive.

3. In the First Name box, type the user's last name.

Maximum length is 32 alphanumeric characters. Do not use special characters, orleading or trailing spaces.

4. In the Last Name box, type user's last name.

Maximum length is 32 alphanumeric characters. Do not use special characters, orleading or trailing spaces.



5. In the Email Address box, type the user's email address in the standard email format:

[email protected] email addresses contain from 5 to 64 characters.

6. For Status, select Active to enable the user account, or Inactive to disable it.

7. In the Password box, type a password containing from 8 to 32 characters.

The password must contain at least 8 characters including uppercase characters andlowercase characters, one numeric character, and one special character from thefollowing characters:

! @ # $ % ^ & * ( ) ? _ < > " : ; ', . /

Do not use any of the following characters in a password:

l Leading or trailing spaces

l Minus (-), plus (+), or equal (=)

The password is case sensitive.

Note

For security, passwords are masked by asterisks.

8. In the Confirm Password box, type the password again to confirm it.

9. Click OK.

Editing a user accountYou can edit the name, email address, status, and password for a user account.

Procedure

1. In the User Management springboard, type the user's last name or a portion of it inthe Name (last, first) box.

2. Select the user from the list of names that appears, and click Edit User.

The Edit User dialog box appears.

Note

Red asterisks indicate required information.

3. Edit the information as needed, and click OK.

Disabling a user accountYou cannot delete a user account from the application. You can only disable an account.

Procedure



The Edit User dialog box appears.

3. Beside Status, select the Inactive option, and click OK.


Editing a user account 63

Unlocking a user accountThe software locks a user’s account after the user fails to log in after three attempts. Thefourth login attempt and all subsequent logins result in an error message. When thishappens, an administrator must unlock the account.

Procedure



The Edit User dialog box appears with an additional option, Login Status.

The Login Status option only appears in the Edit User dialog box when a user'saccount is locked.

3. Click Locked next to Login Status.

The locked image changes to an unlocked image.

4. Click OK to unlock the user account.

Role managementAs an Avamar Extended Retention administrator, you manage roles through the RoleManagement springboard, shown below. The springboard allows you to add or deleteroles to or from a user account.

The following table describes the relationships between Avamar Extended Retentionfunctions and the required roles.

Table 9 Avamar Extended Retention functions and required roles

Functions Required roles

Administrator Auditor User

Create or edit users Yes No No

Create or apply images Yes No No

Edit configuration options Yes No No

Edit user roles Yes No No

Launch Event Viewer Yes No Yes



Table 9 Avamar Extended Retention functions and required roles (continued)

Functions Required roles

Administrator Auditor User

Launch Security Event Viewer Yes Yes No

Launch Task Viewer Yes No Yes

Make changes from My Profile springboard Yes Yes Yes

View Framework Configuration springboard Yes No No

View Event Summary springboard Yes No Yes

View Log Information springboard Yes No No

View My Profile springboard Yes Yes Yes

View Role Management springboard Yes No No

View Security Events springboard Yes Yes Yes

View Task Summary springboard Yes No Yes

View tasks in Task Viewer Yes No Yes

View threat level Yes Yes Yes

View User Management springboard Yes No No

Editing user rolesOnly users with the Administrator role can edit a user’s roles.

Procedure

1. In the Role Management springboard, type the user's last name or a portion of it inthe Name (last,first) box.

2. Select the user from the list of names that appears, and click Edit User Roles.

The Edit Role Assignments dialog box appears in the Framework view, which lists theFramework roles that are available.

Note

The EMC Support role is for EMC Support use only. Do not select this role.

3. Select either the Framework or the Avamar Extended Retention component.

4. Select or clear checkboxes as needed to edit the user’s roles.

When you clear a checkbox, the user no longer has that role.

5. Click OK.


Editing user roles 65

Generating a user role reportThe User Role Report contains user information, including the roles that each user has. Togenerate a user role report, click Generate Role Report in the Role Managementspringboard.

The report opens in a new browser tab if you are using tabs or in a new browser window ifyou are not. The following figure shows an example report. An example report is shownbelow.

User profile managementThe My Profile springboard allows users to make changes to their profiles. A user canonly change the profile for the user account under which they are logged in.

Changing a user name or an email addressIn the Change information dialog box, you can change your name and email address.

Procedure

1. In the My Profile springboard, select Change information.

The Change information dialog box appears.

2. Change the first and last names if needed.

Do not use special characters, or leading or trailing spaces. Maximum length is 32alphanumeric characters.

3. Change the email address, if needed, using the standard email format:

[email protected] email addresses contain 5 to 64 characters.

4. Click OK.



Changing a passwordIn the Change password dialog box, you can change your password.

Procedure

1. In the My Profile springboard, select Change password.

The Change password dialog box appears.

2. Type the old password in the Old Password box.

3. Type a new password in the Password box.

The password must contain 8 to 32 characters, including one numeric character,lowercase characters, uppercase characters, and one special character from thefollowing character set:

! @ # $ % ^ & * ( ) ? _ < > " : ; ' , . /

Do not use any of the following characters in a password:

l Leading or trailing spaces

l Minus (-), plus (+), or equal (=)

The password is case sensitive.

4. Retype the password in the Confirm Password box.

5. Click OK.

Changing email message settingsIn the Edit message settings dialog box, you can change a user’s email message settingsfor the Framework and for Avamar Extended Retention.

Procedure

1. In the My Profile springboard, select Change message settings.

The Change message settings dialog box appears.

2. Select Framework or Avamar Extended Retention from the drop-down list.

3. Select one or more message types.

4. When you have finished, click OK.

System configurationAs an Avamar Extended Retention administrator, you can use the FrameworkConfiguration springboard to configure the framework's system and message settings.

This springboard contains two expandable and collapsible panels:

l The Systems Settings panel includes settings for log levels, a session's timeoutinterval, and the maximum number of acknowledged events.


Changing a password 67

l The Message Settings panel, includes settings that allow you to enable emailnotifications and SNMP.

Clicking either panel expands or collapses its contents. The Framework Configurationspringboard shows only one panel at a time.

Configuring system settingsSystem settings include log level, session timeout interval, and the maximum number ofacknowledged events to retain in the events database.

Procedure

1. In the Framework Configuration springboard, click the System Settings panel.

The System Settings panel opens.

2. In the Log Level list, select the level of logging for the framework:

l The Debug log level reports all types of system activities.

Setting the log level to Debug creates large log files. Use this level only whendebugging problems with the framework.

l The Info log level reports informational messages only.

l The Warning log level (the default setting) reports conditions in the framework thatmight result in an operational failure.

l The Severe log level reports conditions in the framework for which an operation orcomponent require immediate attention in order to continue working properly.

l The Critical log level reports conditions in the framework for which an operation orcomponent has failed.

3. For Session Timeout, select the amount of time before Avamar Extended Retentionlogs out an inactive user. A session’s timeouts range from 1 to 9999 minutes with adefault of 45 minutes.



No notification appears when a session times out; however, the user cannot interactwith the interface after it has timed out. If a session times out, the user must log backin to Avamar Extended Retention.

4. For Max Ack. Events, select the number of acknowledged events to retain in theevents database. The number of acknowledged events range from 100 to 9999 with adefault of 2000.

If the number of acknowledged events exceeds the Max Ack. Events setting, AvamarExtended Retention deletes the oldest events in the events database to manage thesize of the database.

5. Click Apply.

The Configuration dialog box opens.

6. Click OK.

Configuring email notificationsOne of the message settings that you can configure is for email notifications using theSimple Mail Transfer Protocol (SMTP).

Procedure

1. In the Framework Configuration springboard, click the Message Settings panel.

The Message Settings panel opens.

2. To enable the framework server to send email to users, select Enabled Email.

The SMTP Server and From Email boxes appear.

3. In the SMTP Server box, type the SMTP server address.

The SMTP server address can be an IP address, a valid fully qualified name (FQN), or aDomain Name System (DNS) address. You can type a maximum of 255 characters.

4. In the From Email box, type the email address using the standard email format:

[email protected] can type a maximum of 255 characters.

5. Click Apply.

The Configuration dialog box appears.


Configuring email notifications 69

6. Click OK.

Enabling SNMPSimple Network Management Protocol (SNMP) is an "Internet-standard protocol formanaging devices on IP networks." It is used mostly in network management systems tomonitor network-attached devices for conditions that warrant administrative attention.1

In Avamar Extended Retention, any event that is visible in the Event Viewer will generatean SNMP trap. To configure SNMP, you must enable it in the Framework Configurationspringboard, and then configure registered targets for the SNMP traps. See ConfiguringSNMP traps on page 84 for instructions on setting traps.

Procedure

1. In the Framework Configuration springboard, click the Message Settings panel.

The Message Settings panel opens.

2. Select Enabled SNMP.

3. Click Apply.

4. Click OK when you see the message that the configuration changes were successful.

System eventsSystem events are summarized in the Event Summary springboard, from which you canopen the Event Viewer. The Event Summary springboard and the Event Viewerautomatically refresh their contents every 30 seconds.

The Event Summary springboard uses a heatpad to provide event notifications. Thefollowing figure illustrates the possible event colors.

The top bar shows event notifications. The heatpad distributes the events into fourcategories.

l Red for critical event notifications.

l Orange for severe event notifications.

l Yellow for warning event notifications.

l Blue for informational event notifications.

1. en.wikipedia.org/wiki/Simple_Network_Management_Protocol#cite_note-ESNMP-0



Note

Acknowledged events do not appear in the totals.

When no unacknowledged events exist, the top bar contains the text, “0 EventNotifications,” and the bottom bar is solid blue and contains a 0 (zero).

Viewing event details in the Event ViewerThe Event Viewer provides system event details. To open the Event Viewer, click LaunchEvent Viewer in the Event Summary springboard. The Event Viewer lists only those eventsfor which a user has roles to view.

The Event Viewer contains several columns that display details about the events. Thesecolumns are described in the following table.


Viewing event details in the Event Viewer 71

Table 10 Event Viewer column descriptions

Column Description

Time The time the event occurred. Click the Time column heading to sortevents by time.

Severity The severity of the event. Click the Severity column heading to sortevents by severity.

Message Event messages. Click the Message column heading to sort eventsalphabetically.

Acknowledge Contains checkboxes. Click an event's checkbox to acknowledge the

event. The event disappears from the Event Viewer.

Acknowledge Time The date and time that the corresponding event was acknowledged. Tosee entries in this column, select the “Acknowledged” event filter or the“Both” event filter (see Filtering events on page 73).

Note

You can resize the columns in the Event Viewer by clicking and dragging the vertical linesbetween the columns to the preferred width.

Acknowledging eventsWhen you acknowledge an event, it no longer appears in the Event Viewer.

Do any of the following:

l To acknowledge a specific event, click the checkbox next to the event in theAcknowledge column.

l To acknowledge all events, click Acknowledge All.

l To acknowledge only the events on the current page, click Acknowledge Events inPage.

Exporting events to a CSV fileYou can export system events in CSV format so that you can view them in an applicationthat can display CSV files, such as Microsoft Excel.

Procedure

1. Click Export to CSV.

The Opening event.csv dialog box opens.

2. Do one of the following:

l Select the Open with option, and then select an application in which to open thefile.

l Select the Save File option.

3. Click OK.



Filtering eventsYou can filter the events that appear in the Event Viewer if you prefer to see only certaintypes of events.

Procedure

1. In the upper-left corner of the Event Viewer, click the double-arrow button.

The Event Filters panel expands.

2. Select the criteria that you want to use to filter the events, and then click Apply.

Events appear in the Event Viewer based on the filter criteria.

Updating eventsThe information in the Event Viewer updates when you:

l Launch the Event Viewer.

l Click the Refresh icon .

l Add a filter.

By default, the information in the Event Viewer updates every 30 seconds.

TasksTasks are jobs that have been initiated by the system scheduler and by users. You canview all of the tasks and their current statuses in the Task Viewer, which is accessed fromthe Task Summary springboard.


Filtering events 73

Viewing task details in the Task ViewerThe Task Viewer provides detailed information about each task. To open the Task Viewer,click Launch Task Viewer on the Task Summary springboard.

The following table describes the columns in the Task Viewer.

Table 11 Task Viewer column descriptions

Column Description

Type The icon that represents the corresponding task.

Name The task’s name. Click the Names column heading to sort tasksalphabetically.

Description A short description of the task. Click the Description column heading tosort tasks alphabetically by the description.

State The current state of the task. Possible states are:

l Running

l Completed

l Failed

l Scheduled

l Canceled

Click the State column heading to sort tasks alphabetically by state.

Start Time The date and the start time of a task shown in the following format:

yyyy-mm-dd hh:mm:ss



Table 11 Task Viewer column descriptions (continued)

Column Description

End Time The date and the time a task completed shown in the following format:

yyyy-mm-dd hh:mm:ss

Current Step Details about the current phase or step for the task.

Click the Current Step column heading to sort tasks alphabetically bycurrent step.

Progress A color-coded bar that indicates the progress of active, canceled, or failedtasks:

l Active tasks use a green progress bar.

l Completed tasks use a blue progress bar.

l Canceled and failed tasks use a red progress bar.

Action The action that is possible while the task is running.

Details Information icons for each task. To display the details for an individualtask, click the icon in the task’s row. To display the details for every task,

click the Show Details icon located above the Details column.

Filtering tasksYou can filter the tasks in the Task Viewer if you prefer to see only certain types of tasks.

Procedure

1. In the upper-left corner of the Task Viewer, click the double-arrow button.

The Task Filters panel expands.

2. Select the criteria that you want to use to filter the tasks, and click Apply.

The Task Viewer lists tasks based on the filter criteria.


Filtering tasks 75

Security eventsSecurity events appear in the Security Events springboard and in the Security EventViewer. The Security Events springboard uses color-coded graphics to indicate thecurrent security threat level in the system.

Threat levels are categorized using the following colors:

l Green for a low threat level

l Yellow for a medium threat level

l Orange for a high threat level

l Red for a critical threat level

l Gray for an unknown threat level (the server may be down)

The highest, or most critical event, determines the current threat level. For example, if 99out of 100 security events are informational security events, and 1 is a critical securityevent, the threat level is categorized as high.

Viewing event details in the Security Event ViewerThe Security Event Viewer provides security event details. To open the viewer, clickLaunch Security Event Viewer in the Security Events springboard.

The following table describes the columns in the Security Event Viewer.

Table 12 Security Event Viewer column descriptions

Column Description

Time Lists the time the security event occurred. Click the Time column heading tosort security events by time.



Table 12 Security Event Viewer column descriptions (continued)

Column Description

Severity Lists severity icons and labels. Click the Severity column heading to sortsecurity events by severity.

User Lists the user account associated with the security event.

Message Lists all security event messages. Click the Message column heading to sortsecurity events alphabetically.

Filtering security eventsYou can filter security events in the Security Event Viewer using several criteria.

Procedure

1. In the upper-left corner of the Security Event Viewer, click the double-arrow button.

The Event Filters panel expands.

2. Select the criteria that you want to use to filter the events, and click Apply.

The Security Event Viewer displays events based on the filter criteria.

Deleting security eventsYou can delete selected or all events that are displayed in the Security Event Viewer.

Procedure

1. In the Security Event Viewer, do one of the following:

l Press and hold the Ctrl key to select multiple events, and click Delete Events.

l Click Delete All.

An informational dialog box appears.

2. Click Yes to delete the events.

Archiving security eventsYou can archive selected or all events that are displayed in the Security Event Viewer.

Security events are written to the SecurityArchive.xml file, which is located in afolder on the Media Access node. You must specify the folder’s location between the<archiveLocation></archiveLocation> tags in the /opt/EMC/securitylogger/config/SecurityLog.config file.


Filtering security events 77

Procedure

1. In the Security Event Viewer, do one of the following:

l Press and hold the Ctrl key to select multiple events, and click Archive Events.

l Click Archive All.


2. Click Yes to archive the events.

Clearing the security threat levelAfter you address security events, you can clear the threat level in the Security EventViewer.

Procedure

1. Click Clear Threat Level.


2. Click Yes.

Log informationLog information is available through the Log Information springboard. Only AvamarExtended Retention administrators can view log information.

The Log Information springboard enables you to open the Log Viewer to see a list of logfiles, and to view details about the log files.

Procedure

1. In the Log Information springboard, select a component, and click Launch Log Viewer.



2. In the Select Application list, select Framework or Avamar Extended Retention.

3. In the Components panel, click a component to display the details of the hosts onwhich the component is running and the logs that have been generated.

The following table describes each column in the Details panel.

Table 13 Log Viewer detail descriptions

Column Description

Host The fully qualified domain name of the host on which the component isrunning.

Key The column heading contained in the server database.

Value The value that corresponds to the Key.

Name The name of the log file.

Location The location of the log file.

Size The size of the log file.

Modified The date and timestamp that corresponds to the last time the log filechanged.


Log information 79

CHAPTER 5

Administration


l Customizing drop-down text in the login dialog box...............................................82l Configuring the maximum value for parallel jobs................................................... 82l Changing the root password on the Media Access node........................................ 83l Configuring SNMP traps.........................................................................................84l Configuring the system to use an ACSLS library..................................................... 89l Viewing current software versions......................................................................... 93l Shutting down the Media Access node.................................................................. 93l Setting up a VMware vCenter client....................................................................... 94

Administration 81

Customizing drop-down text in the login dialog boxIn the EMC Avamar Extended Retention login dialog box, you can customize the text thatdrops down when a user mouses over Warning: Authorized Users Only.

The text is contained in the system.properties file, and you can customize it asneeded.

Procedure

1. Enter the following command to change to the directory that contains thesystem.properties file:

cd /opt/EMC/IMF/apache-tomcat/catalina_base/imf/WEB-INF/classes/

2. Open the system.properties file in a text editor. For example:

vi system.properties

3. Beside user_message=, type the text that you want to display.

4. Save and close the file.

Configuring the maximum value for parallel jobsBy default, the maximum number of jobs that can run in parallel is set to 8. This value isselectable in the Configuration springboard's Media Access node tab under System

Administration


Properties. (The Configuration springboard is in the Avamar Extended Retentionworkspace.)

You can change the maximum value for parallel jobs as needed by editing thesystem.properties file.

Procedure

1. Enter the following command to change to the directory that contains thesystem.properties file:

cd /opt/EMC/IMF/apache-tomcat/catalina_base/imf/WEB-INF/classes/

2. Open the system.properties file in a text editor. For example:

vi system.properties

3. Beside max_parallel=, type the maximum number.


Changing the root password on the Media Access nodeIf you want to change the root password on the Media Access node, you must use thechange-passwords command. If you use another method, the cleanse function will nolonger work correctly.

Procedure

1. Log in to the Media Access node as root.

2. Change to the dpn user by entering the following command:

su dpn

3. Enter the following command:

change-passwords

4. Follow the prompts to change the password.

Administration

Changing the root password on the Media Access node 83

Configuring SNMP trapsTo use SNMP with Avamar Extended Retention, you must configure traps for the Avamarserver and the tape management system running on the Media Access node.

Note

In order for the SNMP management software to accept traps sent by the Media Accessnode, it must be configured to recognize the traps. Configuration procedures vary by thetype of management software you are using.

For specific instructions on configuring the types of acceptable traps, refer to your SNMPmanagement software documentation.

Configuring Avamar server trapsThis topic describes how to configure traps on the Avamar server.

Procedure


2. Enter the following command to change to the directory that contains thesnmpTrapTragets.xml file:

cd /opt/EMC/IMF/apache-tomcat/catalina_base/imf/WEB-INF/classes

3. Open the snmpTrapTargets.xml file in a text editor. The contents look like this:

<RegisteredTargets> <set>  </set></RegisteredTargets>

4. Edit the file so that it looks like the following example, where 10.10.10.10/162 is theaddress where the trap listener is running.

<RegisteredTargets> <set> <registeredTarget>

Administration

<udpAddress> <UdpAddress>10.10.10.10/162</UdpAddress> </udpAddress> <trapApplications> <appToSeverity> <vaappName>Framework</vaappName> <severityLevels enumtype="com.emc.imf.core.model.Severity$ImfLevel"> INFO,WARN,SEVERE,CRITICAL</severityLevels> </appToSeverity> <appToSeverity> <vaappName>dto-app</vaappName> <severityLevels enumtype="com.emc.imf.core.model.Severity$ImfLevel"> INFO,WARN,SEVERE,CRITICAL</severityLevels> </appToSeverity> <appToSeverity> <vaappName>backupmgr</vaappName> <severityLevels enumtype="com.emc.imf.core.model.ifs.SeverityIf$ImfLevel"> INFO,WARN,SEVERE,CRITICAL</severityLevels> </appToSeverity> <appToSeverity> <vaappName>gridresourcemgr</vaappName> <severityLevels enumtype="com.emc.imf.core.model.ifs.SeverityIf$ImfLevel"> INFO,WARN,SEVERE,CRITICAL</severityLevels> </appToSeverity> </trapApplications> </registeredTarget> </set></RegisteredTargets>

5. Save and close the snmpTrapTargets.xml file.

Configuring tape management system trapsWhen Avamar Extended Retention has been installed, a configuration file, snmp-event.properties, is located in /opt/EMC/avamarer/config. This file contains instructionsfor configuring events and notification priorities. Default values have been set in the file,and you can modify it if you want different behavior.

You use the NWsnmp configuration utility, which is located in /opt/EMC/avamarer/bin/, to configure the tape management system running on the Media Access node tosend event notification messages to the SNMP management software. Any changes youmake to the snmp-event.properties file take effect when you run NWsnmp.

Procedure


2. If you want to view or modify the default SNMP behavior:

a. Enter the following command to change to the directory that contains the snmp-event.properties file:

cd /opt/EMC/avamarer/config

b. Open the file in a text editor. For example:

vi snmp-event.propertiesThe contents of the file are shown here.

## Copyright (C) 2012, All Rights Reserved, by EMC Corporation, Hopkinton, Mass.

Administration

Configuring tape management system traps 85

## This software is furnished under a license and may be used and copied only in# accordance with the terms of such license and with the inclusion of the above# copyright notice. This software or any other copies thereof may not be provided# or otherwise made available to any other person. No title to and ownership of the# software is hereby transferred.## The information in this software is subject to change without notice and should# not be construed as a commitment by EMC Corporation.## EMC Corporation assumes no responsibility for the use or reliability of its# software on equipment which is not supplied by EMC Corporation.#### NOTE:# to enable any of the following Networker traps, change the "off" to "on"# to disable any of the following Networker traps, change the "on" to "off"## Once all the changes have been made run the NWsnmp command.##

# default is for the following to be enabled ( on ).snmp.event.media = onsnmp.event.server = onsnmp.event.device.cleaning.required = onsnmp.event.device.disabled = onsnmp.event.storage.node = onsnmp.event.media.request = onsnmp.event.device.disabled.2 = on

# default is for the following to be disabled ( off ).snmp.event.device.cleaned = offsnmp.event.cleaning.cartridge.required = offsnmp.event.cleaning.cartridge.expired = offsnmp.event.media.capacity = offsnmp.event.netWorker.daemons = offsnmp.event.savegroup.failure = offsnmp.event.device.ordering.issue.detect = offsnmp.event.resource.file = offsnmp.event.savegroup = offsnmp.event.index = offsnmp.event.registration = offsnmp.event.bootstrap = offsnmp.event.license.expiration = offsnmp.event.client = offsnmp.event.bus.device.reset = offsnmp.event.deleted.media = offsnmp.event.write.completion = offsnmp.event.task.manager = offsnmp.event.hypervisor = off

# default enabled prioritiessnmp.priority.critical = onsnmp.priority.alert = onsnmp.priority.emergency = on

# default disabled prioritiessnmp.priority.info = offsnmp.priority.notice = offsnmp.priority.warning = offsnmp.priority.waiting = off

c. Make any necessary changes, and then save and close the file.

3. Enter the following command to change to the directory that contains the NWsnmputility:

cd /opt/EMC/avamarer/bin/

Administration


4. Type the following command, and press Enter:

./NWsnmp [option...]where option... can be one or more of the following:

--helpPrint a usage message briefly summarizing command-line options.

--enable=[ yes | no ]Enable or disable SNMP traps from the tape management system.

--priority=[ Info | Notice | Warning | Waiting | Critical | Alert | Emergency ]The priority of the traps to forward.

--name=network_management_station_hostnameThe host name of the server running the SNMP management software.

--server=media_access_node_hostnameThe host name of the Media Access node.

The Management Information BaseThe SNMP Management Information Base (MIB) that Avamar Extended Retention uses isprovided below.

---------------------------------------------------------------------------- Copyright (c) 2005,2006 All rights reserved by---- EMC Corporation-- 171 South Street-- Hopkinton, MA 01748 USA---- This software is furnished under a license and may be used and copied-- inclusion of the above copyright notice. This software or any other-- only in accordance with the terms of such license and with the-- copies thereof may not be provided or otherwise made available to any-- other person. No title to and ownership of the software is hereby-- transferred.---- The information in this software is subject to change without notice-- and should not be construed as a commitment by EMC Corporation.---- EMC Corporation assumes no responsibility for the use or reliability-- of this software.------------------------------------------------------------------------------ -- Author Identification---- SMC Shannon J Moyes Clark, EMC------------------------------------------------------------------------------------ 000 SMC 02-18-2009 Created Original Model------------------------------------------------------------------------------

EMCIMF-MIB

DEFINITIONS ::= BEGIN

IMPORTS enterprises FROM RFC1155-SMI OBJECT-TYPE FROM RFC-1212 TRAP-TYPE

Administration

The Management Information Base 87

FROM RFC-1215; DisplayString FROM RFC1213-MIB MODULE-IDENTITY FROM SNMPv2-SMI-------------------------------------------------------------Textual conventions for this MIB

emc OBJECT IDENTIFIER ::= { enterprises 1139 }

IMF OBJECT IDENTIFIER ::= { emc 20 }--------------------------------------------------------------Groups in IMF

event OBJECT IDENTIFIER ::= {IMF 1}

imfComponent OBJECT IDENTIFIER ::={IMF 2}

imfSeverity OBJECT IDENTIFIER ::={IMF 3}

imfEventType OBJECT-TYPE SYNTAX DisplayString (SIZE (0..61)) ACCESS read-only STATUS mandatory DESCRIPTION "This is the textual value to define the event type, as defined by all IMF Events." ::= { event 1 }

eventTimestamp OBJECT-TYPE SYNTAX DisplayString (SIZE (0..100)) ACCESS read-only STATUS mandatory DESCRIPTION "Date event was reported" ::= { event 2 }

eventSummary OBJECT-TYPE SYNTAX DisplayString (SIZE (0..256)) ACCESS read-only STATUS mandatory DESCRIPTION "One summary description of event reported, English text only" ::= { event 3 }

isAcknowledged OBJECT-TYPE SYNTAX INTEGER { true(0), false(1), } ACCESS read-only STATUS optional DESCRIPTION "This value indicates if the event has been acknowledged within in the IMF system." ::= { event 4 }

acknowledgedTimestamp OBJECT-TYPE SYNTAX DisplayString (SIZE (0..100)) ACCESS read-only STATUS optional DESCRIPTION "The time that the event was acknoweldged within the IMF" ::= { event 5 }

componentName OBJECT-TYPE SYNTAX DisplayString(SIZE (0..51)) ACCESS read-only STATUS mandatory DESCRIPTION "This is the name of the IMF Component. The name must be unique accross the IMF System. " ::= { imfComponent 1 }

Administration


componentVersion OBJECT-TYPE SYNTAX DisplayString(SIZE (0..51)) ACCESS read-only STATUS mandatory DESCRIPTION "This is the version of the IMF Component." ::= { imfComponent 2 }

componentType OBJECT-TYPE SYNTAX INTEGER { IMFComponent(0), IMFModule(1), IMFServive(2) } ACCESS read-only STATUS optional DESCRIPTION "This is the component type as defined by the IMF." ::= { imfComponent 3 }

severity OBJECT-TYPE SYNTAX INTEGER { info(0), warning(1), severe(2), critical(3) } ACCESS read-only STATUS mandatory DESCRIPTION "This is the severity of the event, as an enumeration." ::= { imfSeverity 1 }

severityText OBJECT-TYPE SYNTAX DisplayString(SIZE (0..20)) ACCESS read-only STATUS mandatory DESCRIPTION "This is the severity of the event as a text value. This should not be used for processing, but only for display as needed. Use the severity enumeration for any dependency processing." ::= { imfSeverity 2 }

-- Traps for IMF

imfEventTrap TRAP-TYPE ENTERPRISE IMF VARIABLES { imfEventType, eventTimestamp, eventSummary, isAcknowledged, acknowledgedTimestamp, componentName, componentType, componentVersion, severity, severityText } DESCRIPTION "An Imf event, which was generated by the specified component and at the specified severity level. Any event in the IMF defined to through SNMP traps, will default to this trap if no other trap specifications are provided" ::= 1END

Configuring the system to use an ACSLS libraryThis section describes how to configure your Avamar Extended Retention system to usean ACSLS library.

Before you beginVerify that the tape drives are attached to the Media Access node using fibre optic cable.

Administration

Configuring the system to use an ACSLS library 89

Ask your administrator to make sure that the drives are zoned for exclusive use by theMedia Access node.

Procedure

1. Obtain the following information from your ACSLS administrator:

l ACSLS host name

l The number of physical tape drives to be configured for the ACSLS silo

l ACSLS identifier (name) for all tape drives that have been partitioned for use byAvamar Extended Retention

l Drive type(s)


3. Enter the following command to obtain the drive paths:

lsscsi

Example output is shown here. The lines that contain tape information are highlightedin bold:

[0:0:32:0] enclosu DP BACKPLANE 1.10 -[0:2:0:0] disk DELL PERC H700 2.10 /dev/sda[0:2:1:0] disk DELL PERC H700 2.10 /dev/sdb[0:2:2:0] disk DELL PERC H700 2.10 /dev/sdc[0:2:3:0] disk DELL PERC H700 2.10 /dev/sdd[0:2:4:0] disk DELL PERC H700 2.10 /dev/sde[0:2:5:0] disk DELL PERC H700 2.10 /dev/sdf[0:2:6:0] disk DELL PERC H700 2.10 /dev/sdg[1:0:0:0] mediumx STK SL500 1200 /dev/sch0[1:0:0:1] tape HP ULTRIUM 4-SCSI H44S /dev/st0[1:0:0:2] tape HP ULTRIUM 4-SCSI H44S /dev/st1

4. Look for "tape" in the enclosu column. In this example, the drive paths for tapeare /dev/st0 and /dev/st1.

There will be a tape entry with a path for every drive that is attached to the MediaAccess node.

5. Write down the drive paths, because you will be asked for this information during theconfiguration.

6. Enter the following command to begin the ACSLS library configuration:

jbconfig

7. Respond to the prompts as follows:

Jbconfig is running on host media_access_node_hostname (Linux 2.6.32.12-0.7.1.3786.0.PTF-default), and is using media_access_node_hostname as the NetWorker server. 1) Configure an AlphaStor Library. 2) Configure an Autodetected SCSI Jukebox. 3) Configure an Autodetected NDMP SCSI Jukebox. 4) Configure an SJI Jukebox. 5) Configure an STL Silo. 6) Exit.which activity do you want to perform? [1]

a. Type 5, and press Enter.

Administration


The following information appears:

Supported Silo types for this system are:1) ACSLS Silo (StorageTek)Enter the number corresponding to the type of silo you are installing:Choice?

b. Type 1, and press Enter.


Installing a StorageTek Silo.What name do you want to assign to this Silo device?

c. Type a name for the ACSLS silo device, and press Enter. You can use any name thatyou want.


Name of the host running the ACSLS software?

d. Type the ACSLS host name, and press Enter.


Pathname of the STL library for the ACSLS silo? [pathname]

e. Press Enter to accept the default path name.


How many physical drives are to be configured for this silo (1 to 256)? [4]

f. Type the number of drives that are to be used by Avamar Extended Retention, andpress Enter.


The drives in this jukebox cannot be auto-configured with the available information. You will need to provide the path for the drives.

Is (any path of) any drive intended for NDMP use? (yes / no) [no]

g. Press Enter to accept the default value of no.


Is any drive going to have more than one path defined? (yes / no) [no]

h. Press Enter to accept the default value of no.


Please enter the device path information in one of the following formats:/dev/nst0 --for local path orhost:device-path --for remote node or NDMP device(s) orhost:drive-letter:directory path --for Windows disk fileFor every device we configure, we're going to need the silo name as well as the path name(s).When you are done entering the system paths for a silo device, we will ask for the corresponding silo name. An example of the name we need for this type of

Administration

Configuring the system to use an ACSLS library 91

silo is: 1,0,1,0Drive 1, element 1Drive path ?

i. Type the drive path, and press Enter.


Corresponding silo name value ?j. Type the drive identifier, and press Enter.

The following information appears, followed by a list of drive types:

Please choose a model from the following typesEnter the drive type of drive 1?

k. Locate the drive type in the list.

l. Type the number corresponding to the drive type, and press Enter.


Jukebox has been added successfully

The following configuration options have been set: > Silo software managed tape autocleaning on. > Barcode reading to on because this is a silo. > Volume labels that match the barcodes.You can review and change the characteristics of the autochanger and its associated devices using the NetWorker Management Console.Would you like to configure another jukebox? (yes/no) [no]

m. Press Enter to accept the default of no.

8. Open the /etc/init.d/networker script in a text editor. For example:

vi /etc/init.d/networker

9. Add the following lines above the start session:

export CSI_HOSTNAME='<acsls_hostname>'export SSI_HOSTNAME='<media_access_node_hostname>'

10.Add the following lines to the start session:

if [ -f /usr/sbin/ssi ]; then /usr/sbin/ssi > /nsr/logs/ssi.log 2>&1 & (echo ' ssi') > /dev/consolefiif [ -f /usr/sbin/mini_el ]; then /usr/sbin/mini_el -l /nsr/logs/mini_el.log 2>&1 & (echo ' mini_el') > /dev/consolefi

11.Add the following lines to the stop session:

if [ -f /usr/sbin/ssi ]; then /usr/bin/pkill -9 ssi (echo ' ssi') > /dev/consolefiif [ -f /usr/sbin/mini_el ]; then /usr/bin/pkill -9 mini_el (echo ' mini_el') > /dev/consolefi

Administration


12.Save and close the networker script.

13.Restart the tape library management system by entering the following commands:

service networker stop

service networker start

14.Verify that the ACSLS library is ready to access commands by entering the followingcommand:

nsrjb -C -j <acsls_name>

where acsls_name is the name of the silo device.

15.Look for the following message:

Jukebox acsls_name: (Ready to accept commands)

Note

It may take several minutes for the device to become "ready."

16.Allocate media to the ACSLS device using the following command:

nsrjb -a -j <acsls_name> -s <media_access_node_hostname> -T<media_identifier>

Viewing current software versionsYou can view the current versions of all Avamar Extended Retention-related software.

Procedure


2. Type the following command, and press Enter:

/opt/EMC/avamarer/bin/AERVersion

Shutting down the Media Access nodeIf you need to shut down the Media Access node for any reason, you must stop AvamarExtended Retention and the internal Avamar server instance first.

Procedure


2. Enter the following command to stop Avamar Extended Retention:

/opt/EMC/avamarer/bin/aerctl stop

3. Enter the following command to stop Avamar:

/opt/EMC/avamarer/bin/dpnctl stop

4. Shut down the Media Access node.

Administration

Viewing current software versions 93

Setting up a VMware vCenter clientThis topic describes how to import VMware vCenter clients to the Media Access node.This procedure is necessary to enable Avamar Extended Retention to import VMwarebackups that have been exported to tape.

The instructions in this section assume that you have already configured and set up theVMware vCenter on an external Avamar server, and that you have deployed virtualmachine proxy clients. See the EMC Avamar for VMware User Guide for more information.

Setting up VMware vCenter clients for Avamar Extended Retention involves performingthese steps on the Media Access node:

l Modifying the mcserver.xml file

l Setting up the VMware vCenter client on the Media Access node

Modifying the mcserver.xml fileBefore you set up the VMware client, you must modify a setting in the mcserver.xml fileon the Media Access node.

Procedure


2. Change to the directory that contains the mcserver.xml file by typing:

cd /usr/local/avamar/var/nc/server_data/prefs

3. Open the mcserver.xml file in a text editor.

4. Locate the following line under <node name="vmware">:

<entry key="ignore_vc_cert" value="false" />5. Change the value to "true".


7. Enter the following commands:

dpnctl stop mcs

dpnctl start mcs

Setting up the VMware vCenter client on the Media Access nodeThese instructions describe how to create the VMware vCenter client on and importmultiple clients to the Media Access node. You do this using the MCGUI on the Avamarserver that is running on the Media Access node.

Procedure

1. Log in to the Avamar MCGUI on the Media Access node.

2. Select Administration.

3. In the Account Management tab, right-click the root directory, and select New Client.

The New Client dialog box appears.

4. Select VMware vCenter in the drop-down list.

The dialog box expands.

Administration


5. In the New Client Name or IP box, type the VMware vCenter's fully qualified DNS nameor IP address.

6. In the User Name box, type the VMware vCenter's user name.

7. In the Password box, type the VMware vCenter's password.

8. In the Verify Password box, retype the password.

9. Click OK.

10.In the client tree, select a vCenter domain or subdoman, and then select Actions >Account Management > New Client(s).

The Select VMware Entity dialog box appears.

11.In the right-hand pane, select Show sub-entities to list the available virtual machinesthat the vCenter administers.

12.Select the virtual machines that you want to import to the Media Access node, andclick OK.

Results

You can now use Avamar Extended Retention to import VMware backups that have beenexported to tape. When you are ready to restore backups to a VMware proxy client, youmust activate the client with the Avamar server on the Media Access node.

Administration

Setting up the VMware vCenter client on the Media Access node 95

Administration


CHAPTER 6

Disaster Recovery

This chapter includes the following topics.

l Definition of a disaster.......................................................................................... 98l Creating a disaster recovery image........................................................................ 98l Recovering the Avamar Extended Retention server.................................................98

Disaster Recovery 97

Definition of a disasterA disaster is any situation in which the day-to-day access to data (for example, workingfiles, software programs, or system files) is disrupted. A disaster also can damagenetwork components, such as data, devices, hardware, media, and software.

A disaster can result from these situations:

l Hardware and software failures

l Infrastructure interruptions, inconsistencies, or loss of services, such ascommunication or network connections

The degree of loss during a disaster can range from one or more files to an entirecomputer system. The severity of the disaster determines the procedures necessary torecover data.

Creating a disaster recovery imageDisaster recovery images can be used to recover the Avamar Extended Retention server inthe event of a disaster.

You should create a cron job to perform this procedure on a regular basis so that youalways have a recent recovery image in case you need it.

Procedure


2. Change to the disaster recovery directory by typing:

cd /opt/EMC/avamarer/bin/

3. Enter the following command to create the recovery image:

./avamar-er-dr --export --pass=<postgres_super_user_password>This command creates a zip file containing the recovery image in the /opt/EMC/snapshot directory. The file name uses the following format:

[mmddyyyy-hhmmss]-avamar-er-dr-[Avamar-ER-Version#]-Snapshot.zip

For example:

12212012-115415-avamar-er-dr-1.0.0.0-Snapshot.zip

The example file was created December 21, 2012 at 11:54:15 am.

4. Copy this file to another system for safekeeping.

Recovering the Avamar Extended Retention serverThis section describes the tasks involved in recovering the Avamar Extended Retentionserver.

Install Avamar Extended RetentionContact EMC Support to do the following:

Disaster Recovery


Procedure

1. Kickstart the Media Access node.

2. Install Avamar Extended Retention software on the Media Access node.

Set up the lockbox password and the superuser accountAfter Avamar Extended Retention has been installed, you must set up a lockbox passwordand create an administrator account.

Procedure

1. Open a web browser and access the following URL:

https://media_access_node_IP_address:7433/imf.action

The Setup Lockbox Password dialog box appears.

2. Type a lockbox password.

3. Type the password again to confirm it, and click Save Lockbox Changes.

The Create Framework Admin Account dialog box appears.

4. Type the first and last names, email address, and password for the Avamar ExtendedRetention framework administrator account, suser.

The administrator, suser, will use this password to log in to the Avamar ExtendedRetention user interface.

5. Click Save Administrator Account.

The EMC Avamar Extended Retention login screen appears. You do not have to log in.

Note

Do not label media. Labeling media will result in data loss.

Apply the Avamar Extended Retention disaster recovery imageThis procedure performs a full recovery of the databases and configuration files from thedisaster recovery image.

Procedure


2. Stop the IMF service by typing:

service imf-server stop

3. Change to the disaster recovery directory by typing:

cd /opt/EMC/avamarer/bin/4. Enter the following command to perform a full recovery using the disaster recovery

image:

avamar-er-dr --import --pass=<postgres_super_user_password> --file=<full_path_to_DR_image>where full_path_to_DR_image is the path to the disaster recovery image that youcreated earlier.

The command's output is in the following format:

BOOTSTRAP: Most Recent bootstrap media barcode is<bootstrap_media_barcode>, Library name is <library_name>,

Disaster Recovery

Set up the lockbox password and the superuser account 99

device path is <device_path>, with bootstrap save set id<save_set_id>, created on <date_bootstrap_was_created>

For example:

BOOTSTRAP: Most Recent bootstrap media barcode is 000040,Library name is [email protected], device path is /dev/nst0,with bootstrap save set id 3859495220, created on Jan 9,2012 12:00:04 PM

5. Write down the bootstrap media details. You will need to use them when you recoverthe bootstrap.

Recover the bootstrapRecovering the bootstrap overwrites the media database and recovers the resource files.For this task, use the bootstrap media details that you captured when you applied thedisaster recovery image.

Procedure

1. Mount the bootstrap media using the following command:

/usr/sbin/nsrjb -l -r -v -n -f <device _path> -T<bootstrap_media_barcode>

where device_path is the path name for the drive in which the bootstrap media will beloaded, and bootstrap_media _barcode is the media identifier.

2. Enter the following command to scan and recover the bootstrap media:

/usr/sbin/scanner -i -v <device_path>

where device_path is the path name for the drive in which the bootstrap volume isloaded.

3. Enter the following command to recover the database and resource files:

mmrecov

If the server has devices configured and enabled, the following prompt appears:

What is the name of the device you plan on using[device_path]?

where device_path is the path name for the drive in which the bootstrap media isloaded.

4. At the following prompt, enter the save set ID that was displayed when you appliedthe disaster recovery image.

Enter the latest bootstrap save set ID []:5. At the following prompt, press Enter to accept the default.

Enter starting file number (if known) [0]:6. At the following prompt, press Enter to accept the default.

Enter starting record number (if known) [0]:7. Stop Networker by entering the following command:

service networker stop

Disaster Recovery


8. Rename the res directory for the current installation by entering the followingcommand:

mv /nsr/res /nsr/res.orig

9. Rename the recovered res folder by entering the following command:

mv /nsr/res.R /nsr/res

10.Restart Networker by entering the following command:

service networker start

11.Enter the following command:

nsrck

Example output is shown below:

nsrck: checking index for 'host1.domain.com'nsrck: /DTO/nsr/index/host1.domain.com contains 13275 records occupying 3998 KBnsrck: checking index for 'host2.domain.com'nsrck: /DTO/nsr/index/host2.domain.com contains 0 records occupying 0 KBnsrck: Completed checking 2 client(s)

12.Verify that the export backups exist by entering the following command:

mminfo -av


volume type client date time size ssid fl lvl name000039 LTO Ultrium-5 FQND 01/03/12 10:38:02 1734 MB 4228070705 cr manual DTO-1315425730@A4:BA000039 LTO Ultrium-5 FQND 01/03/12 13:36:18 1734 MB 4160972491 cr manual DTO-1315425730@A4:BA000040 LTO Ultrium-5 FQND 01/03/12 12:00:00 3637 KB 4211298415 cr full index:FQDN000040 LTO Ultrium-5 FQND 01/03/12 12:00:01 408 B 4194521199 cr full index:FQDN000040 LTO Ultrium-5 FQND 01/03/12 12:01:08 89 KB 4177743988 cr full bootstrap000040 LTO Ultrium-5 FQND 01/09/12 12:00:01 3637 KB 3876272433 cr full index:FQDN000040 LTO Ultrium-5 FQND 01/09/12 12:00:04 97 KB 3859495220 cr full bootstrap

Disaster Recovery

Recover the bootstrap 101

Disaster Recovery


CHAPTER 7

Troubleshooting


l Software component modification caveats.......................................................... 104l Import server issues............................................................................................104l External Avamar server issues............................................................................. 108l Import failures.....................................................................................................110l Export failures.....................................................................................................112l Jobs take a long time to run.................................................................................115l Library issues......................................................................................................115l A task failed or completed with exceptions..........................................................116l The file index is reporting that it is full.................................................................116l JavaScript errors..................................................................................................117l Timeout messages.............................................................................................. 117

Troubleshooting 103

Software component modification caveatsThe Avamar Extended Retention feature contains a number of components that enableselected Avamar client backups to be exported to and imported from a tape library, andrestored to an Avamar client. The following list states what you are and are not permittedto do regarding changing the configuration of any component.

Note

Making unauthorized changes to any Avamar Extended Retention component will resultin an unsupported configuration.

The following list states what you are and are not permitted to do when changing theconfiguration of any component.

l You can use read-only operations against components to assist in diagnosing issues.

l You must not make any changes to component configurations except:

n Through the Avamar Extended Retention user interface

n As documented by formal Avamar Extended Retention documentation or TechnicalNotes

n As directed by Avamar Extended Retention Support, Applications Engineering, orEngineering

l You must not apply hot fixes, patches, or upgrades unless officially supported byAvamar Extended Retention.

Import server issuesThe Import server is the instance of the Avamar server that is running on the MediaAccess node.

The Import server does not display in the GUIThe Import server appears in the Avamar Extended Retention GUI in the followinglocations:

l The Configuration springboard in the Media Access node tab

l The Task Monitoring springboard when tasks are scheduled, running, or completed

l In the Export Policy Management page

l The Import Server panel in the Backup Browse/Import page

If you do not see the Import server in the GUI, one of the following issues may be causingthe problem:

l The transport system service may be down.

l The transport system service may not be configured correctly.

l The MCS or GSAN may not be running on the external Avamar server.

l The external Avamar server may not be running the supported Avamar build.

Troubleshooting


The transport system service may be downIf the transport system service is down, you must restart the service.

Procedure



ps -ef | grep Tran

Two processes should be running, with one the child of the other.

3. If the processes are not running, enter the following command:

service zzgridservice restart

4. Enter the following command again to make sure that the processes are running:

ps -ef | grep Tran

5. If the problem persists, check the grid service's configuration.

The transport system service may not be configured correctlyOnce you know that the transport system service is running, if you still cannot see theImport server in the GUI, the service may not be configured correctly.

Procedure

1. On the Media Access node, open the following file in a text editor:

/opt/EMC/TransportSystemService/config/GridService.xml

An example GridService.xml file is shown here:

<NodeConfig> <com.emc.imf.service.common.ServiceConfig> <logLevel> <level>WARN</level> </logLevel> <brokerHostName>10.5.123.234</brokerHostName> <brokerport>61617</brokerport> <configFileName>/opt/EMC/TransportSystemService/config/DefaultConfig</configFileName> </com.emc.imf.service.common.ServiceConfig></NodeConfig>

2. Verify that the <brokerHostName> element is set to the IP address of the MediaAccess node.

3. Verify that the <brokerport> element matches the port you assigned to AvamarExtended Retention when you installed it.


5. Restart the transport system service by entering the following command:


Troubleshooting

The Import server does not display in the GUI 105

The MCS or GSAN may not be running on the external Avamar serverBoth the MCS and GSAN must be running on the external Avamar servers.

Procedure

1. Log on to the external Avamar server as root.


dpnctl status

Example output is shown below. It shows the GSAN and MCS status as up.

Identity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)dpnctl: INFO: gsan status: updpnctl: INFO: MCS status: up.dpnctl: INFO: EMS status: down.dpnctl: INFO: Backup scheduler status: down.dpnctl: INFO: dtlt status: down.dpnctl: INFO: Maintenance windows scheduler status: suspended.dpnctl: INFO: Unattended startup status: enabled.dpnctl: INFO: [see log file "/usr/local/avamar/var/log/dpnctl.log"]

3. If either or both services are down, restart them.

The external Avamar server may not be running the supported build of AvamarThe external Avamar servers and the Media Access node must be running the sameversion of Avamar.

Procedure

1. Log in to the Avamar server as root.

2. To see which version of Avamar is running, enter the following command:

avtar --version

Example output is shown below.

version: 7.0.100-280build date: Feb 8 2013 21:34:29msg format: 13-10SSL: TLSv1 OpenSSL 0.9.8r-fips 8 Feb 2011Zlib: 1.2.3LZO: 1.08 Jul 12 2002platform: LinuxOS version: SLES-64Processor: x86_64

3. If the Avamar server version does not match the version running on the Media Accessnode, upgrade the server.

Troubleshooting


The Import server appears to be offline in the GUIIf the import server displays in the GUI as being offline, check the status of avdto andthe GSAN.

The avdto process may be downIf the avtdo process is down, you must restart it.

Procedure



ps -ef | grep avdto

If avdto is running, you will see output like the following:

root 1078 1023 0 14:56 pts/0 00:00:00 grep avdtoroot 7590 1 0 Mar01 ? 00:00:00/usr/local/avamar/bin/dto/avdto.bin--vardir=/usr/local/avamar/var/dto--bindir=/usr/local/avamar/bin/dto--vardir=/usr/local/avamar/var/dto --daemon--logfile=/usr/local/avamar/var/dto/avdto_daemon.log

3. If avdto is not running, enter the following command:

service avdto start

The GSAN may have failed on the Media Access nodeIf the GSAN has gone down, you must reset the import server.

Procedure



dpnctl status



3. If the GSAN is down, reset the Import server as follows:

a. In the Avamar Extended Retention workspace, click Browse Exported Backups onthe Import & Restore springboard.

b. In the Backup Browse/Import page, click Reset Import Server.

c. Click OK when you see the Reset Import Server message.

Troubleshooting

The Import server appears to be offline in the GUI 107

External Avamar server issuesThe following issues are specific to the external Avamar servers whose backups are beingexported by the Avamar Extended Retention system.

Note

These Avamar servers are referred to as “external” to distinguish them from the Avamarserver that is running on the Media Access node.

Avamar servers incorrectly appear offline in the GUISynchronize the clocks between the external Avamar servers and the Media Access node.

Avamar servers do not appear in the GUIThe external Avamar grids appear in the Avamar Extended Retention GUI in the followinglocations:

l The Configuration springboard in the Avamar Servers tab

l The Task Monitoring springboard when tasks are scheduled, running, or completed

l In the Export Policy Management page

If you do not see the Avamar servers in the GUI, one of the following issues may becausing the problem:

l The transport system service may be down.

l The transport system service may not be configured correctly.

The transport system service may be downIf the transport system service is down, you must restart it.

Procedure

1. Log in to the external Avamar server as root.

2. Enter the following command to determine if the transport system services arerunning:

ps -ef | grep Tran

Two processes should be running, one being the child of the other.

3. If the processes are not running, enter the following command:


4. Enter the following command again to make sure that the processes are running:

ps -ef | grep Tran

5. Repeat this process on each of the external Avamar servers.

Troubleshooting


The transport system service may not be configured correctlyOnce you know that the transport system service is running, if you still cannot see theexternal Avamar servers in the GUI, you may have miss-configured the service, causing itnot to communicate with the Media Access node.

Procedure

1. On the Media Access node, open the following file in a text editor:

/opt/EMC/TransportSystemService/config/GridService.xml

An example GridService.xml file is shown here:

<NodeConfig> <com.emc.imf.service.common.ServiceConfig> <logLevel> <level>WARN</level> </logLevel> <brokerHostName>10.5.123.234</brokerHostName> <brokerport>61617</brokerport> <configFileName>/opt/EMC/TransportSystemService/config/DefaultConfig</configFileName> </com.emc.imf.service.common.ServiceConfig></NodeConfig>

2. Verify that the <brokerHostName> element is set to the IP address of the MediaAccess node.

3. Verify that the <brokerport> element matches the port you assigned to AvamarExtended Retention when you installed it.


5. Restart the transport system service by entering the following command:


The MCS or GSAN may not be running on the external Avamar serverBoth the MCS and GSAN must be running on the external Avamar servers.

Procedure

1. Log on to the external Avamar server as root.


dpnctl status

Example output is shown below. It shows the GSAN and MCS status as up.


3. If either or both services are down, restart them.

Troubleshooting

Avamar servers do not appear in the GUI 109

The external Avamar server may not be running the supported build of AvamarThe external Avamar servers and the Media Access node must be running the sameversion of Avamar.

Procedure

1. Log in to the Avamar server as root.

2. To see which version of Avamar is running, enter the following command:

avtar --version

Example output is shown below.

version: 7.0.100-280build date: Feb 8 2013 21:34:29msg format: 13-10SSL: TLSv1 OpenSSL 0.9.8r-fips 8 Feb 2011Zlib: 1.2.3LZO: 1.08 Jul 12 2002platform: LinuxOS version: SLES-64Processor: x86_64

3. If the Avamar server version does not match the version running on the Media Accessnode, upgrade the server.

Avamar server performance is affected by Avamar Extended Retention activitiesIf the performance of the external Avamar servers is being negatively affected by AvamarExtended Retention activities, try reducing the number of jobs that are running in parallel.

Procedure

1. Log into the Avamar Extended Retention GUI.

2. Access the Avamar Extended Retention workspace.

3. In the Configuration springboard, click the Media Access node tab.

4. Click System Properties.

5. Select a lower number for the Maximum Parallel Jobs setting, and click Apply.

Import failuresThe following topics describe possible import failure scenarios.

Import failed and did not display in the Avamar Management Console ActivityMonitor

Try the following:

l Make sure the MCS and GSAN are running on the Media Access node.

l Make sure the avagent is running and configured for the Media Access node toitself.

l Check that the Extended Retention client (avagent) is running and in the avagentlog, and check that it has the 1024 and 1034 plug-ins registered.

Troubleshooting


l Check that each avagent on the Media Access node is on a separate port.

Import failed and can be seen in the Import server's Avamar Management ConsoleTry one or more of the following:

l Make sure that the avdto process on the Media Access node is running. To do this:


2. Enter the following command:ps -ef | grep avdtoIf avdto is running, you will see output like the following:

root 1078 1023 0 14:56 pts/0 00:00:00 grep avdtoroot 7590 1 0 Mar01 ? 00:00:00/usr/local/avamar/bin/dto/avdto.bin--vardir=/usr/local/avamar/var/dto--bindir=/usr/local/avamar/bin/dto--vardir=/usr/local/avamar/var/dto --daemon--logfile=/usr/local/avamar/var/dto/avdto_daemon.log

3. If avdto is not running, enter the following command:service avdto start

l Check the Event Viewer for events that might provide more information.

l Make sure that imports are not trying to run while the library drives are being used forexports.

Backups do not appear in the Backup Browse/Import pageYou can determine whether any backups have been exported to tape.

Procedure


2. Run the following command to verify that the backup exists:

mminfo -av

If no backups are displayed, that means they have not been exported to tape.

An Avamar client does not appear in the Backup Browse/ Import pageIf you do not see an Avamar client in the Backup Browse/Import page, the followingsections may provide information about what is causing the problem.

Avamar clients in generalSometimes, the Avamar server on the Media Access node cannot create a client during anexport operation due to nslookup issues; in other words, the server cannot “see” theclient for which it is exporting the backup. When this happens, the backup is stillexported to tape, but it will be “archived” under the Media Access node client itself.When you select that backup and restore it, the system restores the original client thatcould not be created because of the lookup issues.

To avoid this problem, make sure that the DNS or the /etc/hosts file on the MediaAccess node has been configured to “see” all of the clients that are being backed up bythe external Avamar servers.

Troubleshooting

Import failed and can be seen in the Import server's Avamar Management Console 111

Note

If you create a backup on a client that is using an alias that is not DNS resolvable, theclient backup will be exported, but it will show up under the Avamar Extended Retentionclient name rather than under is own name.

Celerra NDMP clientsFor Celerra NDMP clients, when you configure an Avamar Accelerator node to be part ofthe Avamar Extended Retention environment, you are prompted to enter a name that willbe used to register the NDMP client with Avamar. This client name must be the fullyqualified domain name of the Data Mover, which in this case is the Media Access node.

The configuration prompts are shown below:

Choose an action: 1. Add a new system 2. Edit an existing system 3. Remove a system from the list 4. Exit setup Enter action: [4]: 1 Setting up a new system accountWhat kind of system do you want to setup? 1. EMC Celerra 2. NetApp Filer Enter choice: 1 Starting setup for EMC Celerra Network address or DNS name of the EMC Celerra [filer.company.com]: hostname.example.comThe ndmp user password on "hostname.example.com": Repeat password:Password encoding scheme ("md5" or "text") to use for "hostname.example.com" [md5]:Checking username and password... avndmp returning with exitcode 0 verified Avamar account name for "hostname.example.com" [hostname.example.com]:

Export failuresThe sections in this topic describe possible export failure scenarios.

Exports are failing in generalMake sure that the Avamar Extended Retention client has been registered with theinternal and external Avamar servers.

Procedure



cd /data01/avamar/var/dto

3. Enter the following command to list the contents of the directory:

ls -al

For each server with which the Avamar Extended Retention client was registered,including the instance of Avamar that is running on the Media Access node, youshould see a directory named with the following format:

AvamarServerIPAddress-MediaAccessNode

Troubleshooting


where MediaAccessNode can be the FQDN or IP address of the Media Access node.

Example output is shown here:

drwxr-xr-x 2 root root 4096 Feb 7 10.5.123.234-MediaAccessNode.example.comdrwxr-xr-x 2 root root 4096 Feb 7 10.5.160.185-10.5.160.195drwxr-xr-x 2 root root 4096 Feb 7 10.5.170.165-MediaAccessNode.example.com

4. If the internal Avamar server or an external Avamar server is missing from the list, youmust register the Avamar Extended Retention client with that server.

Do the following:

a. Enter the following command:

/user/local/avamar/bin/dto/avmultiregister.pl

The following output appears:

=== DTO Registration and Activation ===---------------------------------------This script will register and activate the DTO plugin with the Avamar Administrator server.Agent status(es):-----------------=== DTO Registration and Activation ===---------------------------------------1. Register to a new server2. Remove a current registration3. Show current agent status4. ExitYour choice:

b. Enter 1, and then respond to the prompts to register the client with the Avamarserver.

Exports do not appear in the Avamar Management Console and fail in AvamarExtended Retention

Try the following:

l Make sure that the Media Access node is registered as a client with the externalAvamar servers as described in Exports are failing in general on page 112.

l Make sure that the MCS and GSAN are running on the external Avamar server asdescribed in The MCS or GSAN may not be running on the external Avamar server onpage 106.

l Check that the avagent processes are running. To do this, enter the followingcommand:ps -ef | grep avagentYou should see output like the following:

root 692 1 0 Feb29 ? 00:00:01 /usr/local/avamar/bin/dto/avagent.bin --bindir="/usr/local/avamar/bin/dto" --sysdir="/usr/local/avamar/etc" --flagfile="/usr/local/avamar/etc/agentsettings.cfg" --vardir="/data01/avamar/var/dto/10.5.150.246-host3219.example.com" --logfile="/data01/avamar/var/dto/10.5.150.246-host3219.example.com/avagent.log " --listenport=28004root 810 1 0 Feb29 ? 00:00:00 /usr/local/avamar/bin/dto/avagent.bin --bindir="/usr/local/avamar/bin/dto" --sysdir="/usr/local/avamar/etc" --flagfile="/usr/local/avamar/etc/agentsettings.cfg"

Troubleshooting

Exports do not appear in the Avamar Management Console and fail in Avamar Extended Retention 113

--vardir="/data01/avamar/var/dto/10.5.150.247-host3219.example.com" --logfile="/data01/avamar/var/dto/10.5.150.247-host3219.example.com/avagent.log " --listenport=28005root 7733 1 0 Mar01 ? 00:00:01 /usr/local/avamar/bin/dto/avagent.bin --bindir="/usr/local/avamar/bin/dto" --sysdir="/usr/local/avamar/etc" --flagfile="/usr/local/avamar/etc/agentsettings.cfg" --vardir="/data01/avamar/var/dto/10.5.139.219-host3219.example.com" --logfile="/data01/avamar/var/dto/10.5.139.219-host3219.example.com/avagent.log " --listenport=28003

l Make sure that each avagent on the Media Access node is on a separate port. The--listenport setting in the ps output displays the port.

l Make sure that the Avamar Extended Retention client (avagent) is running and inthe avagent log. The --logfile setting in the ps output displays the log location.The log should indicate that plugins 1034 and 1024 have been registeredsuccessfully. For example:

2012-03-05 14:19:28 avagent Info <7502>: Registration of client /clients/host3219.example.comwith MCS 10.5.123.219:28001 successful.2012-03-05 14:19:28 avagent Info <5928>: Registration of plugin 1034 Unix successful.2012-03-05 14:19:28 avagent Info <5928>: Registration of plugin 1024 dto successful.2012-03-05 14:19:28 avagent Info <5619>: Registration of client and plugins complete.

An export failed and appears in the MC Activity MonitorDo one or both of the following:

l Follow standard troubleshooting for all Avamar plug-ins.

l If you have a single drive, make sure that an import is not running at the same time asthe export. Try the export again when the drive is available.

Not all exports were written to tape, but the export task completedDo one or both of the following:

l Check the Event Viewer to see if a client was skipped because it did not match thepolicy.

l Check the Avamar MC to confirm that a backup is found within the rules of the policy.

The Event Viewer indicates that an export event was skippedTry performing an on-demand export of the backup that was not exported.

An export worked but the client is not in the import listIf the Media Access node cannot resolve the host name for a given client, it will create auser event indicating that it cannot resolve the client and store the backup under theAvamar Extended Retention client.

You can do one or both of the following:

l Look for the backup under the Avamar Extended Retention client.

l Add the client to the network lookup for the Media Access node.

Troubleshooting


Jobs take a long time to runCommunication may have failed between the Avamar Management Console and AvamarExtended Retention. The job may have actually completed, but Avamar ExtendedRetention still shows it as running.

Library issuesThe following issues pertain to the tape library attached to the Media Access node.

The library does not appear in the GUIThe tape library that is used by Avamar Extended Retention must not be shared. It mustbe zoned for exclusive use by the Media Access node, and the robot must be controlledonly by Avamar Extended Retention.

Procedure



cd /opt/EMC/scsilibdetector/bin


./scsilibdetector

You should see information similar to the following for the library:

Vendor: IBM Version: A.50 SCSI ID: 2.0.1 Slots ( Storage: 44 Import/Export: 3 Drives: 2 )

4. If the library is detected, wait for it to display in the GUI.

5. If the library is not detected, do the following:

l Check the fiber connection between the Media Access node and the library.

l Ask the IT department to check the zoning.

l Restart the Media Access node.

The library appears as UNKNOWN in the GUIIf the library is shown as UNKNOWN in the Media Management springboard, AvamarExtended Retention was not able to configure it automatically.

You can configure the library manually.

Procedure

1. On the Media Management springboard, click Manage Export Media.

The Media Management page opens.


3. Click Configure.

The Configure Library dialog box appears.

Troubleshooting

Jobs take a long time to run 115

4. Click Configure Library.

A progress bar appears.


After you configure the library, it should appear in the Libraries panel.

An eject-tape request failedWhen an eject-tape request fails, you can view a log to determine why it failed.

Procedure



nsr_render_log -l -s 24 /nsr/logs/daemon.raw

3. Look for errors that explain why the eject failed.

A task failed or completed with exceptionsWhen a task fails of completes with exceptions, you can view a log to help determinewhat happened.

Procedure



nsr_render_log -l -s 24 /nsr/logs/daemon.raw

3. Look for errors that explain why the task failed.

The file index is reporting that it is fullThe Media Access node's Avamar server disk is getting full. You need to change thesecondary retention period for one or more backups.

Procedure

1. Log in to Avamar Extended Retention, and access the Avamar Extended Retentionworkspace.

2. On the Import & Restore springboard, click Browse Exported Backups to open theBackup Browse/Import page.

3. In the Filter Clients panel, type * in the Client Name box, and then click Apply.

4. Select a client in the Avamar Clients panel to display the backups for that client in theBackup panel.

5. Select one or more backups in the Backup panel.

6. Click Edit Secondary Retention.

The Edit Secondary Retention Period dialog box appears.

7. Select a shorter retention period, or select to expire the retention period now, andthen click Save.

Troubleshooting


JavaScript errorsIf you get a Java script error, try refreshing the browser. If that does not work, try restartingthe browser.

Timeout messagesIf you receive a timeout message while trying to perform a task, refresh the browser, andthen retry the operation.

Troubleshooting

JavaScript errors 117

Troubleshooting


emc avamar 7.2 extended retention user guide · emc avamar 7.2 extended retention user guide 9....

Documents