emc avamar data transport® avamar data transport 1.0 sp3 installation guide and reference manual...

EMC® AvamarData Transport1.0 SP3

Installation Guide and Reference ManualP/N 300-012-527REV 06

EMC Avamar Data Transport Installation and Reference Guide2

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

Published October, 2012

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

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

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

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

http://support.emc.com

CONTENTS

Chapter 1 Introduction

General information .................................................................................... 12 Important terms and concepts .................................................................... 12

Avamar ................................................................................................. 12Avamar Data Transport.......................................................................... 13VMware................................................................................................. 13

Chapter 2 Hardware and Software Requirements

About Avamar Data Transport...................................................................... 16 Requirements for the Avamar server............................................................ 16 Requirements for the ESX server ................................................................. 17

Networking for the ESX server................................................................ 18 Requirements for the tape backup server .................................................... 18 Requirements for the tape library ................................................................ 18 Requirements for tape media ...................................................................... 19

Chapter 3 Pre-installation Requirements

About the Avamar Data Transport system components ................................ 22 What you need to know to complete the installation.................................... 22

Avamar servers ..................................................................................... 22ESX server............................................................................................. 23Tape backup server ............................................................................... 23

About the configuration of the Avamar server .............................................. 23Verifying that the Avamar server is running............................................ 23Verifying time sync on the Avamar server............................................... 24Verifying network connectivity............................................................... 24

About the configuration of the ESX server.................................................... 24Verifying memory and disk availability on the ESX server....................... 24Verifying time sync on the ESX server .................................................... 25Verifying network connectivity............................................................... 25

About the configuration of the tape backup server ...................................... 25Verifying SSH server .............................................................................. 25Verifying time sync on the tape backup server ....................................... 25Verifying network connectivity............................................................... 25Verifying adequate media in the tape library ......................................... 25

Avamar Data Transport components to install.............................................. 26

Chapter 4 Installing and Configuring the Control Node

About the control node ............................................................................... 30 About the installation phases ..................................................................... 31 Phase 1: Importing and starting a control node ........................................... 31

Importing the Avamar ADT appliance..................................................... 31Starting the imported appliance ............................................................ 33

Phase 2: Host pre-configuration .................................................................. 35Check network connectivity................................................................... 35Synchronize Avamar Data Transport hosts with NTP .............................. 35

Phase 3: Installing the Avamar Data Transport framework............................ 36

Contents 3

Contents

Phase 4: Installing PostgreSQL 8.3 .............................................................. 37Post-Installation configuration .............................................................. 38

Phase 5: Installing security logger ............................................................... 42Configuring security events archiving .................................................... 43

Phase 6: Configuring Avamar Data Transport framework .............................. 44 Phase 7: Installing the Avamar Data Transport application........................... 46

Chapter 5 Installing the Avamar Data Transport System Service

About the Avamar Data Transport system service ........................................ 54 Check network connectivity......................................................................... 54 Synchronizing with NTP ............................................................................... 54 Identifying the highest plug-in version ........................................................ 55 Installing the Avamar Data Transport system service................................... 55 Updating the lockbox with transport node passwords ................................. 56

Chapter 6 Installing Transport Nodes

About transport nodes ................................................................................ 58 Pertinent sections of the AVE install guide................................................... 58 Using the Avamar Data Transport appliance ................................................ 59 Modifying the install.conf file ...................................................................... 59 Updating client plug-ins .............................................................................. 60 Running the adt-ave.sh script...................................................................... 60 Licensing transport nodes ........................................................................... 61 Installing and configuring the NetWorker client ........................................... 61 Installing and configuring the NetBackup client........................................... 62

Chapter 7 Configuring Tape Backup Servers

About tape backup servers.......................................................................... 64 Checking network connectivity .................................................................... 64 Synchronizing with NTP ............................................................................... 64 Configuring the EMC NetWorker tape backup server .................................... 65

Testing the NetWorker configuration...................................................... 72Specifying the ADT tape library.............................................................. 74

Configuring the Symantec NetBackup tape backup server ........................... 75 Testing the NetBackup configuration ........................................................... 79

Chapter 8 Installing Transport Node Services

About transport node services .................................................................... 82 Check network connectivity......................................................................... 82 Installing transport node services ............................................................... 82

Choosing a library in NetWorker ............................................................ 84Configuring SSH keys ............................................................................ 86

Changing the tape backup server user......................................................... 87 Changing the tape backup server password ................................................ 87 Changing database communication settings ............................................... 88

Chapter 9 Verifying Avamar Data Transport Installation

Verifying Avamar servers ............................................................................. 90 Verifying transport nodes ............................................................................ 91 Verifying the tape backup server ................................................................. 91

4 EMC Avamar Data Transport Installation and Reference Guide

Contents

Chapter 10 Troubleshooting

About logging ............................................................................................. 94 About services ............................................................................................ 94 Troubleshooting Avamar Data Transport GUI issues ..................................... 95

Transport or recover tasks are failing..................................................... 95Transport tasks seem to hang ............................................................... 95Replication to ADT is timing out............................................................. 95User events and other messages seem to be getting lost....................... 98Springboards do not seem to be added to my workspace ...................... 99

Troubleshooting problems with the control node......................................... 99Postgres user password does not work.................................................. 99

Troubleshooting problems with Avamar servers......................................... 100 Troubleshooting problems with transport nodes........................................ 102 Troubleshooting tape backup server errors................................................ 104

NetWorker Installed in non-standard location...................................... 104Media not available for transporting data............................................ 104Media not in library for recovery .......................................................... 105Failure to authenticate with tape backup server................................... 105

Appendix A Changing Communication Ports

Avamar Data Transport communication ports ............................................ 108 Changing the SSL port............................................................................... 108 Changing the message bus port ................................................................ 109 Changing the PostgreSQL database port.................................................... 111

Appendix B Uninstalling Avamar Data Transport

Uninstalling the Avamar Data Transport framework.................................... 114 Uninstalling the PostgreSQL database....................................................... 114 Uninstalling the Avamar Data Transport security logger ............................. 115 Uninstalling the Avamar Server’s transport system service ........................ 115 Uninstalling the transport node service ..................................................... 115

Appendix C Creating SSL Certificates

Appendix D Backing up PostgresSQL

Backing up the database........................................................................... 120Putting PostgreSQL backup in CRON (optional).................................... 121

Restoring the database ............................................................................. 122

Appendix E The adtUtil.sh Script

About the adtUtil.sh script ........................................................................ 124 ClientArchiveData ..................................................................................... 124

Example of adtUtil.sh with ClientArchiveData ...................................... 125 TransportClientData .................................................................................. 127

Example of adtUtil.sh with TransportClientData................................... 127 TransportMediaData ................................................................................. 128 TransportMediaExpire ............................................................................... 129

Example of adtUtil.sh with TransportMediaExpire................................ 129 RemoteRestore.......................................................................................... 130

Example of adtUtil.sh with RemoteRestore .......................................... 130

Contents 5

Contents

Appendix F Configuring ADT for Media Groups

Configuring NetWorker for media groups ................................................... 132 Configuring NetBackup for media groups................................................... 140


PREFACE

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

Contact your EMC technical support professional if a product does not function properly or 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 publication describes how to set up, install, and configure the EMC Avamar Data Transport.

AudienceThe information in this publication is primarily intended for persons responsible for configuring and installing new Avamar Data Transport components for use at customer sites. That person must have knowledge of VMware administration (ESX Server, in particular), including the creation of a Virtual Machine Disk Format (VMDK) environment. That person must also have the ability to install and configure tape backup software to work with tape library hardware.

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

Related documentationThe following EMC publications provide additional information:

◆ EMC Avamar Data Transport Release Notes

◆ EMC Avamar Data Transport Security Guide

◆ EMC Avamar Data Transport User Guide

◆ EMC Avamar Compatibility and Interoperability Matrix

Table 1 Revision history

Revision Date Description

06 October 18, 2012

GA release of 1.0 Service Pack 3 (SP3).• Revised the Preface.• Updated the install file’s version number.• Added the section, “Changing the tape backup server user” on

page 87.

A05 May 24, 2012 Includes bug fixes and support for transporting media groups.

Preface 7

http://support.emc.com

Preface

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

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

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

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

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

Note: A note presents information that is important, but not hazard-related.

IMPORTANT

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

Typographical conventions

EMC uses the following type style conventions in this document:

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

Italic Use for full titles of publications referenced in text

Monospace Use for:• System output, such as an error message or script• System code• Pathnames, filenames, prompts, and syntax• 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


Preface

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

To access the Avamar support page:

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

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

3. Select the product from the list that appears.

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

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

Documentation

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

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

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

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

Knowledgebase

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

To search the EMC Knowledgebase:

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

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

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

4. Select Knowledgebase from the Scope by resource list.

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

6. Click the search button.

Live chat

To engage EMC Customer Service by using live interactive chat, click Join Live Chat on the Service Center panel of the Avamar support page.

9

https://support.emc.com/products

Preface

Service Requests

For in-depth help from EMC Customer Service, submit a service request by clicking Create Service Requests on the Service Center panel of the Avamar support page.

Note: To open a service request, you must have a valid support agreement. Contact your EMC sales representative for details about obtaining a valid support agreement or with questions about your account.

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

Facilitating support

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

◆ ConnectEMC automatically generates service requests for high priority events.

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

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

[email protected]

Please include the following information:

◆ Product name and version

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

◆ Page numbers

◆ Other details that will help us address the documentation issue


mailto:[email protected]

CHAPTER 1Introduction

The following topics provide introductory information about Avamar Data Transport, and describe terms and concepts used in this guide.

◆ General information ................................................................................................ 12◆ Important terms and concepts ................................................................................ 12

Introduction 11

Introduction

General informationEMC® Avamar® Data Transport is a system of virtual machines that run in a VMware ESX Server environment in conjunction with tape backup software to transport de-duplicated Avamar data to tape.

A transport node functions as a target of replication from a primary Avamar server, which, after replication is complete, is moved to tape. Transport nodes can also be recovered from tape, allowing backed up data to be accessed by administrators or users. Transport nodes are sized at 1TB or 2TB nodes.

◆ Configurations — As transport nodes are used for both targets for replication and targets for recovery from tapes, it is strongly suggested that you configure at least two transport nodes in your systems. Avamar Data Transport 1.0 SP2 has been qualified with up to 10 transport nodes per control node.

◆ Installation — Installation of Avamar Data Transport can only be performed by EMC-trained personnel.

Important terms and conceptsThe definitions of the following terms and concepts deviate from the norm in that transport nodes, which have many of the capabilities of Avamar servers, are installed as virtual machines rather than specific rack-mountable hardware.

Avamar

◆ Avamar Grid — See Avamar Server.

◆ Avamar Server — The server component of the Avamar client/server system. An Avamar server is a fault tolerant, high-availability system, comprised of one or more nodes, used to store client backups. It also provides essential processes and services required for data restores, client access, and remote system administration. Sometimes also referred to as a “grid.”

◆ Backup — The process whereby Avamar clients "backup" to the Avamar server. An Avamar server may store multiple backups or the same client. In the context of ADT, the process of copying backups to tape is called "transporting."

◆ Data Server — See GSAN.

◆ Grid — See Avamar Server.

◆ GSAN — Global Storage Area Network. The GSAN is a component of the Avamar server. It is sometimes referred to as the data server or the storage server.

◆ Node — The primary building block in any Avamar system is a “node.” Each node is a self-contained network-addressable server that runs Avamar software on a virtual machine running the Linux operating system.

◆ Restore — The process whereby a backup stored on the Avamar server is "restored" back to a client machine. In the context of ADT, the process of bringing archived backups back from tape is called "recovery."


Introduction

◆ Single-Node Server — Single-node Avamar servers combine all the features and functions of Avamar software on a single node. Multi-node implementations of Avamar servers are capable of subdividing these features into utility and storage nodes. Avamar Data Transport does not support this type of scalable multi-node configuration.

◆ Storage Server — See GSAN.

Avamar Data Transport

◆ Archive Server — See Tape Backup Server.

◆ Avamar Data Transport Framework — The framework is a service oriented architecture that provides applications with common services like communication, security, and event logging.

◆ Control Node — The control node is a 64-bit Linux host where the Avamar Data Transport application and the Avamar Data Transport Framework run. The Avamar Data Transport user interface is accessed from a web server that is installed on this host. In addition, the database of all transported files is often located on the control node. There is only one control node in an Avamar Data Transport system.

◆ Purging — A process that prepares a transport node as a new target for replication, or as a new target for a recover operation.

◆ Recovery — The process where archived backups on tape are copied back to a transport node. Once the backups have been "recovered" to the transport node, Avamar clients can connect to the transport node and restore backups.

◆ Replication — The process whereby specified client backups on the primary Avamar server are copied to the transport node.

◆ Tape Backup Server — Avamar Data Transport supports the EMC NetWorker® or Symantec NetBackup tape backup products. Both of these products have a server component that drives the tape archiving process.

◆ Transport — The process where backups stored on an Avamar server are copied to tape.

◆ Transport Node — Transport nodes are Avamar Virtual Edition servers that have been modified specifically for use in the Avamar Data Transport system. They are the targets of replication from Avamar servers, and they are used as backup and restore targets by the tape backup server.

VMware

◆ Datastore — Virtual representations of combinations of underlying physical storage resources in the data center. These physical storage resources can be provisioned from the local SCSI disks of the server, the Fibre Channel SAN disk arrays, the iSCSI SAN disk arrays, or Network Attached Storage (NAS) arrays.

◆ Host — The virtual representation of the computing and memory resources of a physical machine running ESX Server.

◆ Networks — In the virtual environment, networks connect virtual machines to each other or to the physical network outside of the virtual data center.

Important terms and concepts 13

Introduction

◆ VirtualCenter Management Server — The user interface that delivers centralized management, operational automation, resource optimization, and high availability to IT environments.

◆ Virtual Infrastructure Client (VI Client) — An interface that allows administrators and users to connect remotely to the VirtualCenter Management Server or individual ESX Server installations from any Windows platform.

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

◆ VMware Virtual Machine — A representation of a physical machine by software. A virtual machine has its own set of virtual hardware (for example, RAM, CPU, NIC, hard disks, and so forth) upon which an operating system and applications are installed. The operating system sees a consistent, normalized set of hardware regardless of the actual physical hardware components. VMware virtual machines contain advanced hardware features such as 64-bit computing and virtual symmetric multiprocessing.

◆ VMware Virtual Machine File System (VMFS) — A high-performance cluster file system for ESX Server virtual machines. Each virtual machine is encapsulated in a small set of files and VMFS is the default storage system for these files on physical SCSI disks and partitions.

◆ vSphere Client — An interface that allows administrators and users to connect remotely to the vCenter Server or individual ESX Server installations from any Windows platform.


CHAPTER 2Hardware and Software Requirements

The following topics describe the hardware and software requirements for Avamar Data Transport.

◆ About Avamar Data Transport.................................................................................. 16◆ Requirements for the Avamar server........................................................................ 16◆ Requirements for the ESX server.............................................................................. 17◆ Requirements for the tape backup server ................................................................ 18◆ Requirements for the tape library ............................................................................ 18◆ Requirements for tape media .................................................................................. 19

Hardware and Software Requirements 15

Hardware and Software Requirements

About Avamar Data TransportThe Avamar Data Transport is a hardware and software system that transports deduplicated data from an Avamar server to tape. The system consists of the following physical components:

◆ Physical Avamar server◆ ESX server for hosting control and transport nodes◆ Tape backup server◆ Tape library, tape drives, and tapes.

Any version numbers for supported hardware or software referred to in this document are superseded by version numbers identified in the EMC Avamar Compatibility and Interoperability Matrix. A link to the document can be found on the following web page:

http://supportwip.emc.com/products/Avamar.aspx

Requirements for the Avamar serverThe Avamar Data Transport system supports configurations of Avamar specified in the “Avamar Data Transport v1.0 SP1 Compatibility Matrix” section of the latest EMC Avamar Compatibility and Interoperability Matrix. It is assumed that these Avamar servers already exist and are running in your environment.

The Avamar servers need to be connected to the network in a way that they can communicate with the other hardware components on the network.


http://supportwip.emc.com/products/Avamar.aspx


Requirements for the ESX server

It is strongly recommended that the ESX server only runs Avamar Data Transport components. Only the control node and the transport nodes should be running on the ESX server.

Avamar Data Transport requires the VMware ESX versions specified in the “Avamar Data Transport v1.0 SP1 Compatibility Matrix” section of the latest EMC Avamar Compatibility and Interoperability Matrix.

The hardware requirements for an ESX server that will support an Avamar Data Transport system vary, but are generally determined by adding the requirements of one ADT control node to the requirements of the number of transport nodes you are planning to deploy. Avamar Data Transport has been qualified with up to 10 transport nodes per control node.

The table below identifies the hardware requirements for transport nodes.

The disk space requirements for ADT assume that VMware has been installed and configured and that the recommended amounts of disk space are available in datastores to be provisioned through the VMware user interfaces.

Table 2 Transport node hardware requirements

Number of transport nodes

Number of virtual processors

Amount of memory

Disk space

1 TB nodes 2 TB nodes

1 2 4 GB 1.6 TB 3.2 TB

2 4 8 GB 3.2 TB 6.4 TB

3 6 12 GB 4.8 TB 9.6 TB

4 8 16 GB 6.4 TB 12.8 TB

Requirements for the ESX server 17


Networking for the ESX server

In addition to a dedicated ethernet connection for the ESX VMKernel and Service Console connections, you will need to have four additional gigabit Ethernet NICs that can be teamed for the Avamar Data Transport Virtual Machine Network.

The graphic below shows an example of how networking can be configured on an ESX server with six NICs.

Requirements for the tape backup serverThe supported tape backup products for Avamar Data Transport are identified in the “Avamar Data Transport v1.0 SP1 Compatibility Matrix” section of the latest EMC Avamar Compatibility and Interoperability Matrix.

Requirements for the tape libraryFor optimal efficiency it is strongly recommended that one tape drive per transport node be available in your tape library.



Requirements for tape mediaIt can be difficult to determine the amount of media that will be required for transport node backups. The number of tapes required will probably be less than the number required to backup the cumulative data size of original client backups, but it is difficult to determine how much deduplication is taking place on the client and on the Avamar server.

Ensure that there is sufficient media in your tape library’s “freepool.”

Requirements for tape media 19

CHAPTER 3Pre-installation Requirements

The following topics identify pre-installation requirements that will need to be met in order to successfully install the Avamar Data Transport system.

◆ About the Avamar Data Transport system components ............................................ 22◆ What you need to know to complete the installation................................................ 22◆ About the configuration of the Avamar server .......................................................... 23◆ About the configuration of the ESX server................................................................ 24◆ About the configuration of the tape backup server .................................................. 25◆ Avamar Data Transport components to install.......................................................... 26

Pre-installation Requirements 21

Pre-installation Requirements

About the Avamar Data Transport system componentsThe EMC Avamar Data Transport system is comprised of a number of hardware and software components. Before installing Avamar Data Transport, the following components must be running in your network environment:

◆ Avamar server◆ ESX server (with available space and memory)◆ Tape backup server configured with EMC NetWorker or Symantec NetBackup◆ Tape library with appropriate pool of tapes.

What you need to know to complete the installationIn order to successfully complete the Avamar Data Transport installation process, you will need the information identified below. This information is also required if you request technical support from EMC.

Avamar servers

For each Avamar server that you will be backing up with Avamar Data Transport, collect the following information:

❑ Avamar Server: Resolvable hostname or IP address of the Avamar server ______________

❑ Avamar Server: Root password to the Avamar server.

❑ NTP Server: NTP server used by Avamar server ______________

❑ Client Plug-ins: Identify the “Highest Plug-in Version” numbers __________



ESX server

Several Avamar Data Transport components are installed as virtual machines on the ESX server. Collect the following information:

❑ ESX Server: Resolvable hostname or IP address of the ESX server where the control node and transport nodes will reside, or the VirtualCenter server that will manage the control node and transport nodes ______________

❑ ESX Server: Password to an administrative account on the ESX server, or the VirtualCenter server that manages the ESX server.

❑ Control Node: Resolvable hostname or IP address (or anticipated hostname or IP address) of the control node (a 64-bit Red Hat Linux system). ______________

❑ Transport nodes: Resolvable hostnames or IP addresses (or anticipated hostnames and IP addresses) of each transport node planned for your system. (ADT has been qualified with up to 10 transport nodes per control node.) These will be Avamar Virtual Edition (AVE) servers that will be installed on the ESX server and then be converted to ADT transport nodes:

______________ ______________ ______________

______________

❑ Email Server: Resolvable hostname or IP address of an email server that the transport nodes can use to send email ______________

Tape backup server

❑ Tape Backup Server: Resolvable hostname or IP address of the tape backup server where the tape backup application is installed ______________

❑ Tape Backup Server: Password to an administrative account on tape backup server host.

About the configuration of the Avamar serverUsing a login with root permissions, you will need to examine the configuration of the Avamar server.

Verifying that the Avamar server is running

The Avamar server should be running. To verify this, log in to the Avamar server with root permissions and type the following command:

dpnctl status

The output should look something like this:

root@lava4031:~/#: dpnctl statusIdentity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)dpnctl: INFO: gsan status: readydpnctl: INFO: MCS status: up.dpnctl: INFO: EMS status: up.dpnctl: INFO: Scheduler status: up.dpnctl: INFO: Maintenance operations status: enabled.dpnctl: INFO: Unattended startup status: enabled.

About the configuration of the Avamar server 23


Verify that the output includes “gsan status: ready.” If the GSAN is down or not ready, restart it by issuing the following command on the Avamar server console:

dpnctl start gsan

Verifying time sync on the Avamar server

Take note of which NTP server the Avamar server is syncing with. If your Avamar Data Transport installation is going to support more than one Avamar server, ensure that all the Avamar servers are syncing to the same NTP server. Furthermore, all the hosts which are part of Avamar Data Transport configuration must sync with this same time server.

Every host must sync with the same NTP server as the Avamar server.

To display the NTP server that Avamar is using, type ntpq -p on the command line of the Avamar console. The NTP servers in use are listed in the remote column.

root@lava4055:~/#: ntpq -p remote refid st t when poll reach delay offset jitter===============================================================================*lava4016.dev.lo 10.254.140.22 4 u 4 64 377 0.262 -34.184 29.200

If for some reason the other hosts in the Avamar Data Transport system are unable to reach this NTP server, you can change the NTP server the Avamar server is using with the asktime utility.

Verifying network connectivity

When logged in to the Avamar server, ensure that you can ping all other hosts in the Avamar Data Transport system. You can configure Avamar Data Transport by using hostnames, fully qualified hostnames, or IP addresses. However, you must be consistent throughout. For example, if you start configuring the system using fully qualified hostnames, you must continue using fully qualified hostnames everywhere.

You can set up your network to resolve hostnames either using DNS or by making an entry for every host in the system in the /etc/hosts file on each host.

About the configuration of the ESX serverGenerally the control node and the transport nodes are installed as virtual machines on the ESX server.

Verifying memory and disk availability on the ESX server

Ensure that the ESX server has enough memory and disk space available for the control node and whatever number of transport nodes you want to deploy. “Requirements for the ESX server” on page 17 describes the minimum and recommended requirements.



Verifying time sync on the ESX server

Ensure that the ESX server is using the same NTP server as the Avamar servers. To display the NTP server that the ESX is using, type ntpq -p on the command line of the ESX server console. The NTP servers in use are listed in the remote column.

If the correct NTP server is not being used, add the correct NTP server:

1. Log in to the ESX server using the VMware Infrastructure client.

2. Select Configuration > Time Configuration > Properties > Options > NTP Settings > Add.

3. Click Remove to remove the previous NTP entries.


When logged in to the ESX server, ensure that you can ping all other hosts in the Avamar Data Transport system by hostname or IP address.

Perform this same check on each of the virtual machines you install on this ESX server that are part of the Avamar Data Transport system.

About the configuration of the tape backup serverAvamar Data Transport supports either EMC NetWorker or Symantec NetBackup, and the tape backup server can run on either a UNIX or Windows platform.

Verifying SSH server

In order to communicate with the tape backup server, Avamar Data Transport must connect with the tape backup server through Secure Shell (SSH). Consequently, you must ensure that the SSH server is running on the tape backup server host.

On Linux or Solaris, the SSH server is included as part of the operating system.

For Windows, the SSH server used must comply with the SSH-2 specification, and it can not be based on Cygwin or F-Secure. As examples, EMC has tested with the following tools:

◆ freeSSHd (http://www.freesshd.com/)◆ VShell (http://www.vandyke.com/products/vshell/)

Verifying time sync on the tape backup server

Ensure that the tape backup server uses the same NTP server as the Avamar servers. You can do this by typing ntpq -p


When logged in to the tape backup server, ensure that you can ping all other hosts in the Avamar Data Transport system by name or IP address.

Verifying adequate media in the tape library

Based on your estimates of how much data is being backed up, verify that you have sufficient media to hold the data you are backing up.

About the configuration of the tape backup server 25


Avamar Data Transport components to installAfter the pre-installation checks have been made, install and configure the following Avamar Data Transport components on the appropriate hosts in the system:

◆ Avamar Data Transport system service (on the Avamar servers)◆ Control node (on the ESX server)◆ Transport nodes (on ESX server)◆ Transport node services (on transport nodes)◆ Avamar Data Transport groups or policies on the tape backup server

Install and configure these components in the following order:

1. Control node

2. Avamar Data Transport system service on the Avamar server (or servers)

3. Transport nodes

4. Tape backup server and tape backup clients

5. Transport node services



After installing these components, Avamar Data Transport can be configured to transport deduplicated data to tape.

The following chapters describe the installation and configuration of each of these components.

Avamar Data Transport components to install 27

CHAPTER 4Installing and Configuring the Control Node

The following topics describe how to install and configure the control node.

◆ About the control node ........................................................................................... 30◆ About the installation phases ................................................................................. 31◆ Phase 1: Importing and starting a control node ....................................................... 31◆ Phase 2: Host pre-configuration .............................................................................. 35◆ Phase 3: Installing the Avamar Data Transport framework........................................ 36◆ Phase 4: Installing PostgreSQL 8.3 .......................................................................... 37◆ Phase 5: Installing security logger ........................................................................... 42◆ Phase 6: Configuring Avamar Data Transport framework .......................................... 44◆ Phase 7: Installing the Avamar Data Transport application....................................... 46

Installing and Configuring the Control Node 29

Installing and Configuring the Control Node

About the control nodeThe EMC Avamar Data Transport framework is the foundation on which the Avamar Data Transport application is built. You will need to install the framework on a virtual machine (VM) that runs Red Hat Linux 4 (64-bit). Afterwards, you will install Avamar Data Transport as an application.

After the framework and the Avamar Data Transport application are installed, the VM they are installed on functions as the control node.

These instructions assume that the Avamar Data Transport ISO image has been mounted as ADT-1.0.3-26730-NO_TNODE. If you have mounted the ISO image to a different location, replace ADT-1.0.3-26730-NO_TNODE with the correct mount point.

The disk space requirement for the Avamar Data Transport control node is determined by the ESX server version you are using. In general, the recommended disk space for the control node is outlined in the following table.

When creating datastores on ESX 4.0 for partitions that will need to hold more than 256GB, ensure that you set the block size to 4MB on the “Disk/LUN - Formatting” screen of the VMware Add Storage wizard.

Table 3 Recommended disk space for the control node

Partitions or mount point ESX 3.5 ESX 4.0

[Operating System] 60 GB 60 GB

/opt/postgres 250 GB 1 TB

/export/backup 250 GB 500 GB

560 GB Total Disk Space 1.56 TB Total Disk Space



Avamar Data Transport systems that will be transporting very large numbers of files (e.g. more than 500 million files) should be deployed on ESX 4.0 and will need to allocate more than the recommended amount of disk space.

About the installation phasesThe control node installation has seven phases:

◆ “Phase 1: Importing and starting a control node” on page 31◆ “Phase 2: Host pre-configuration” on page 35◆ “Phase 3: Installing the Avamar Data Transport framework” on page 36◆ “Phase 4: Installing PostgreSQL 8.3” on page 37◆ “Phase 5: Installing security logger” on page 42◆ “Phase 6: Configuring Avamar Data Transport framework” on page 44◆ “Phase 7: Installing the Avamar Data Transport application” on page 46

Phase 1: Importing and starting a control nodeThe Avamar Data Transport control node is a 64-bit Red Hat Linux host. It is distributed as a VMware appliance named adt-1.0.2.ovf and can be found in the /appliance directory of the Avamar Data Transport ISO.

There are two steps in the control node creation process:

◆ “Importing the Avamar ADT appliance” on page 31◆ “Starting the imported appliance” on page 33

These instructions assume that the Avamar Data Transport ISO image has been mounted as ADT-1.0.3-26730-NO_TNODE. If you have mounted the ISO image to a different location, replace ADT-1.0.3-26730-NO_TNODE with the correct mount point.

Importing the Avamar ADT appliance

To import the control node appliance:

1. Open the Virtual Infrastructure Client or vSphere Client.

2. Log in as the admin user.

3. Import the ADT appliance by clicking one of the following:

• For ESX 3.5 click File > Virtual Appliance > Import.• For ESX 4.0 and 4.1 click File > Deploy OVF Template

4. Import the ADT appliance by clicking one of the following:

• For ESX 3.5 click Import from file• For ESX 4.0 click Deploy from file • For ESX 4.1 skip to next step.

5. Click Browse and navigate to the location of the adt-1.0.2.ovf file.

About the installation phases 31


6. Select the adt-1.0.2.ovf file, and then click Open.

7. Click Next.

8. Click Next.

9. Type an ESX-specific Name for the control node, and click Next.

10. Select the datastore on which to create the control node, and click Next.

11. For ESX 4.1 click Thick provisioned format.

12. Click Finish.

The ADT appliance is copied to the ESX server.

After the ADT appliance has successfully imported, you will need to add two new disks to the VM.

13. Right-click on the virtual machine you just imported from the ADT appliance and click Edit Settings.

14. On the Hardware tab click Add.

15. Click Hard Disk, then click Next.

16. Click Create a new virtual disk, then click Next.

17. Type the Disk Size for the drive:

• If you are installing on an ESX 3.5 server, type 250 GB as the disk size.• If you are installing on an ESX 4.0 server, type 1 TB.

18. In the Location field, click Store with the virtual machine, then click Next.

19. In the Mode field, check both Independent and Persistent, then click Next.

20. Click Finish.

This disk should be Hard disk 2, SCSI device 1 ( SCSI(0:1) ).

21. On the Hardware tab click Add.

22. Click Hard Disk, then click Next.

23. Click Create a new virtual disk, then click Next.

24. Type the Disk Size for the drive:

• If you are installing on an ESX 3.5 server, type 250 GB as the disk size.• If you are installing on an ESX 4.0 server, type 500 GB.

25. in the Location field, check Store with the virtual machine, then click Next.

26. In the Mode field, check both Independent and Persistent, then click Next.

27. Click Finish. This disk should be Hard Disk 3, or SCSI device 2 ( SCSI(0:2) ).

28. Click OK.

29. If you are installing on ESX 4.x, right-click the control node virtual machine and select Upgrade Virtual Hardware.

The ADT appliance has now been imported, and it is now ready to be configured as the Avamar Data Transport control node.



Starting the imported appliance

To configure the imported appliance as an Avamar Data Transport control node:

1. Power on the control node VM.

2. From the Virtual Infrastructure Client or vSphere Client, open the console of the control node VM.

3. Log in to the control node as root.

4. Configure the basic networking capabilities of the node (eth0 network interface) by typing the following on a single command line:

/usr/sbin/netconfig --ip=STATIC-IP-ADDR --netmask=NETMASK --hostname=HOSTNAME --domain=DOMAIN --device=eth0 --gateway=GATEWAY

Where STATIC-IP-ADDR, NETMASK, HOSTNAME, DOMAIN, and GATEWAY are the static IP address, netmask, hostname, domain, and gateway settings for the control node.

For example, you might enter something like this:

/usr/sbin/netconfig --ip=10.5.10.33 --netmask=255.255.255.0 --hostname=magma33 --domain=corp --device=eth0 --gateway=10.5.10.1

5. Restart the network service by typing:

service network restart

6. Edit the file /etc/ssh/sshd_config and uncomment the line to PermitRootLogin.

7. Edit the file /etc/sysconfig/network and change HOSTNAME to the hostname for the control node.

For example, you might change the line to something like this:

HOSTNAME=lava4033.corp

8. Edit the file /etc/hosts and include an entry in the file that reflects the IP address of the control node, its hostname, and any aliases for the hostname. For example, you might type a line that looks something like this:

10.5.10.33 magma33.corp magma33

9. Type system-config-time and select the correct time zone for the control node.

10. From the /root directory, run the following script:

./adt-emf.sh

The adt-emf.sh script converts the appliance to an Avamar Data Transport control node.

11. After the script completes, type:

fdisk /dev/sdb

a. In the fdisk program, type n

b. Type p

c. Type 1

Phase 1: Importing and starting a control node 33


d. Accept the default first cylinder by pressing enter.

e. Accept the default last cylinder by pressing enter.

f. Change the partition system id by typing t

g. Type f0

h. Type w

12. Type:

fdisk /dev/sdc

a. In the fdisk program, type n

b. Type p

c. Type 1

d. Accept the default first cylinder by pressing enter.

e. Accept the default last cylinder by pressing enter.

f. Change the partition system id by typing t

g. Type f0

h. Type w

13. Type the following commands:

mkfs.ext3 -L /opt/PostgreSQL /dev/sdb1mkdir /opt/PostgreSQLchmod 755 /opt/PostgreSQL


mkfs.ext3 -L /export/backup /dev/sdc1mkdir /exportmkdir /export/backup

15. Open the /etc/fstab file and insert the following lines at the bottom of the file:

LABEL=/opt/PostgreSQL /opt/PostgreSQL ext3 defaults 1 2LABEL=/export/backup /export/backup ext3 defaults 1 2

16. Reboot the host.

After the host finishes rebooting, check to see that the mount points successfully mounted. Type df -h and the output in the “Mounted on” column should look similar to what is shown in bold below:

root@lava4033:/opt/PostgreSQL/#: df -hFilesystem Size Used Avail Use% Mounted on/dev/sda5 7.9G 1.9G 5.7G 25% //dev/sda1 122M 14M 102M 12% /bootnone 1.9G 0 1.9G 0% /dev/shm/dev/sda9 37G 584M 34G 2% /opt/dev/sda8 1.5G 80M 1.4G 6% /var/dev/sdb1 250G 231M 246G 1% /opt/PostgreSQL/dev/sdc1 250G 84M 246G 1% /export/backup



Phase 2: Host pre-configurationFrom the control node, complete the following:

◆ “Check network connectivity” on page 35◆ “Synchronize Avamar Data Transport hosts with NTP” on page 35

Check network connectivity

Using either DNS or entries in the /etc/hosts file, the host must be able to establish a network connection to all other hosts in the Avamar Data Transport system.

From the control node, check connectivity for each of the following hosts by using the ping command:

◆ Each Avamar server you are replicating from◆ Each tape backup server you will be using◆ The host where the security logger is installed (if not on the control node)

If you are using DNS to resolve hostnames between Avamar Data Transport hosts, type the address of the DNS server in the /etc/resolv.conf file.

Synchronize Avamar Data Transport hosts with NTP

All hosts in the Avamar Data Transport system must synchronize with the same NTP server.

It is strongly suggested that the control node synchronize with the same NTP server that is being used by the Avamar server.

To synchronize your Linux host with an NTP server:


2. At the command prompt, type:

service ntpd stop

If the ntpd service is already stopped, this command may fail. This is expected behavior; continue to the next step.

3. Check the firewall configuration by typing:

chkconfig --list ntpd

Output similar to the following appears in the command shell:

[root@lava4245 ~]# chkconfig --list ntpdntpd 0:off 1:off 2:off 3:off 4:off 5:off 6:off

If run levels 3, 4, and 5 are already set to on, skip to step 5.

4. Turn on run levels 3, 4, and 5 for the time service by typing the following command:

chkconfig --level 345 ntpd on

Phase 2: Host pre-configuration 35


You can verify that the command succeeded by retyping

chkconfig --list ntpd

If the command succeeded, output similar to the following appears:

[root@lava4245 ~]# chkconfig --list ntpdntpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off

5. Edit the /etc/ntp.conf file and enter a “server” entry that identifies the time server that will be used by all the servers and hosts in the Avamar Data Transport system.

For example, to configure the control node to synchronize with an NTP server that has an IP address of 10.100.10.1, a section of the ntp.conf file would look similar to the following:

# --- OUR TIMESERVERS -----# Use public servers from the pool.ntp.org project.# Please consider joining the pool (http://www.pool.ntp.org/join.html).server 10.100.10.1

6. After editing and saving the ntp.conf file, restart the ntpd service by typing:

service ntpd start

7. Verify that the Linux host is using the correct ntp server by typing:

ntpq -p

In the case of an NTP server with an IP address of 10.5.142.16, the output of the command appears similar to the following:

[root@lava4245 ~]# ntpq -p remote refid st t when poll reach delay offset jitter============================================================================== 10.5.142.16 10.254.140.22 4 u 5 64 1 10.312 455.605 0.001 LOCAL(0) LOCAL(0) 10 l 4 64 1 0.000 0.000 0.001

The control node is now configured to synchronize with the specified NTP server.

Phase 3: Installing the Avamar Data Transport frameworkThe following instructions describe how to install the Avamar Data Transport framework:


2. From the mounted ADT-1.0.3-26730-NO_TNODE ISO image, copy the/installers/ADTFramework-linux-x64-setup.bin file to the /opt directory.

3. From the /opt directory, change permissions on the setup file by typing:

chmod 755 ADT*

4. Start the installation by typing:

./ADTFramework-linux-x64-setup.bin



If your DISPLAY environment variable is set to anything, the install program attempts to run as an X-application. If you want to run in this mode you will need to have an X-server running on your local host and set the DISPLAY variable on the control node to point to your local host.

If the display variable is not set, or if you set it to nothing, the program runs in text mode.

5. Read and accept the license agreement.

6. Accept the default installation directory or type a different directory.

7. Accept the default message bus port of 61617.

8. After the Installation Summary appears, continue the installation.

9. Confirm that the installation information is correct.

10. Confirm that you want to continue installing.

After the setup program finishes, the Avamar Data Transport framework will be installed.

Phase 4: Installing PostgreSQL 8.3The PostgreSQL database stores metadata for all the files backed up from the transport nodes.

The following instructions describe how to install the PostgreSQL database:


2. Verify that there is a mount point for /opt/PostgreSQL by typing:

df -h

The output of the this command should show /opt/PostgreSQL is mounted similar to what is shown below in bold:


3. Type the following command:

chmod 755 /opt/PostgreSQL

4. From the mounted ADT-1.0.3-26730-NO_TNODE ISO image, copy the/ADT-1.0.3-26730-NO_TNODE.iso/postgreSQL/postgresql-8.3.5-1-linux-x64.bin to the /opt/PostgreSQL directory.

5. From the /opt/PostgreSQL directory, change permissions on the setup file by typing:

chmod 755 postgres*

Phase 4: Installing PostgreSQL 8.3 37


6. Run the install program in text mode by typing the following:

./postgresql-8.3.5-1-linux-x64.bin --mode text

7. When prompted, accept the default PostgreSQL install of /opt/PostgreSQL/8.3

8. When prompted, accept the default data directory of/opt/PostgreSQL/8.3/data

9. Type a password for the database superuser postgres.

The install script creates two users: one is a database role named postgres and the other is a Linux user also named postgres. The password you are typing is for the database role. (The password for the Linux user will be set later.)

It is extremely important to keep a record of all the passwords you set when installing Avamar Data Transport as these passwords may be necessary for maintaining or upgrading your system.

10. Retype the password.

11. Change the port number, by typing 5558.

12. For the locale setting, type 180

This will select en_US.utf8 as the locale.

13. Continue the install process.

14. Do not launch the stack builder at exit.

The PostgreSQL install finishes.

Post-Installation configuration

After the PostgreSQL install program finishes, the following configuration steps need to be performed:

◆ Setting a password for the postgres Linux user created during the PostgreSQL installation.

◆ Creating the tables in the database for the Avamar Data Transport application.

◆ Enabling encrypted communication between the database and Avamar Data Transport clients. Encrypted communication is implemented with ssh tunneling.

The following steps are required to perform the post-installation configuration:

1. At the command prompt, set a password for the Linux user postgres by typing:

passwd postgres

Then type and confirm the password.



2. Copy the database creation script and SQL file from the /scripts directory of the mounted ADT-1.0.3-26730-NO_TNODE.iso image by typing something similar to the following two commands:

cp /ADT-1.0.3-26730-NO_TNODE/scripts/create* /tmpcp /ADT-1.0.3-26730-NO_TNODE/scripts/install_public_key.sh /tmp

3. Change to the new directory. Using the example above change to the /tmp directory.

4. From the new directory, change permissions on the scripts by typing:

dos2unix create*dos2unix install_public_key.shchmod 755 create*chmod 755 install_public_key.sh

5. Change to user postgres by typing the following command:

su postgres

6. if you have changed the PostgreSQL database user password from the default, edit the create_catalog.sh script and enter the new password on line 77 of the file. By default, line 77 looks like this:

echo "localhost:$PORT:postgres:postgres:postgres" > $PGPASSFILE

Change the third instance of the word “postgres” to the new password. For example, if the PostgreSQL database user password was changed from the default to “master1” the line 77 would look like this:

echo "localhost:$PORT:postgres:postgres:master1" > $PGPASSFILE

7. From the /tmp directory, type the following command:

./create_catalog.sh

8. Press Y to continue.

9. Type the password for the database super user role that you entered in step step 9 of the section “Phase 4: Installing PostgreSQL 8.3” on page 37.

If the script completes with a “SUCCESS” message, the PostgreSQL database is now ready for use.

10. After the script finishes, type:

exit

11. As user root, type the following command:

./install_public_key.sh

Installing the public key allows Avamar Data Transport clients to connect to this host using ssh tunneling without typing a password. The public key is installed for the user who is the owner of the database, which by default is user postgres.

If you do not run install_public_key.sh, ADT will still function. There will be some initial errors reported in the Avamar Data Transport logs, and then all communication with the database will continue in an unencrypted manner.



12. Type the following:

y

After the install_public_key.sh script completes, the PostgreSQL database is configured and ready for use.

13. Delete the files you copied in step 2 above, either by removing the directory where you copied them or by deleting them individually.

Modifying database communication encryption settingsIf the PostgreSQL database is installed on the same host as the Avamar Data Transport application, then communication between the application and the database will by default be unencrypted.

However, if the PostgreSQL database is on a remote host, and communication must happen “over the wire,” then communication between the application and the database is by default encrypted.

You can modify the default behavior by inserting the entries below into the Catalog.properties file found in the following directory on the control node:

/opt/EMC/IMF/apache-tomcat/imf/WEB-INF/imfcomponents/ADT/resources

In most cases the entries identified below will not be present in the Catalog.properties file, so you will need to insert them:

◆ tunnel—This value can be set or not set according to the table below:

◆ tunnelPort—By default, the ssh tunneling port is set to the same port used by the database, which by default is 5558. You might need to change the tunnel port if the default port is being used by another process on the control node. If you want to use a different ssh tunneling port, type a new value for this entry.

◆ tunnelUser—By default, the ssh tunnel will be created using the user who owns the database. If the database was installed with an owner other than postgres, set this entry to the name of that user.

As an example, the following Catalog.Properties file is configured to use the host port 5080 for ssh tunneling using the user skerrit:

root@lava4033:/opt/EMC/IMF/apache-tomcat/imf/WEB-INF/imfcomponents/ADT/resources/#: cat Catalog.properties

Table 4 tunnel value descriptions

tunnel=true All communication with the database will be encrypted. If tunneling cannot be established, communications will fail.

tunnel=false All communication with the database will be unencrypted.

tunnel=or not present in file

If the “tunnel” entry is not in the Cataglog.properties file or if the “tunnel” entry is not set to any value, ADT will attempt to establish encrypted communication with the database. If it fails to establish tunneling, then ADT will establish communication with the database in an unencrypted manner.



serverName=localhostportNumber=5558databaseName=ada_cataloguser=ada_userssl=falsetunnel=truetunnelport=5080tunneluser=skerrit

Modifying PostgreSQL memory usage configurationYou will need to make some modifications to the PostgreSQL configuration in order to have the database use memory more efficiently.

To modify the PostgreSQL configuration:

1. As user root on the control node, type:

/etc/init.d/postgresql-8.3 stop

2. Edit the /opt/PostgreSQL/8.3/data/postgresql.conf file. Uncomment (where necessary) and set the specified values for the key-value pairs shown below:

shared_buffers = 1024MBwork_mem = 8MBmaintenance_work_mem = 512MBwal_buffers = 1024kBcheckpoint_segments = 16effective_cache_size = 1024MBdefault_statistics_target = 300log_line_prefix = '%m %h '

When entering the value for wal_buffers, please note that the “k” in kB is lowercase.


/etc/init.d/postgresql-8.3 start

Look in the /opt/PostgreSQL/8.3/data/pg_log/startup.log file to see if there were any errors in the database startup. If there were no errors, the PostgreSQL memory usage is configured.

Copying backup and restore scripts to control nodeYou will need to copy the backup and restore scripts from the distribution ISO to the control node.

To copy the scripts to the control node:

1. As user root on the control node, create the following directory by typing:

mkdir /opt/EMC/ADTmkdir /opt/EMC/ADT/scripts

2. Copy the scripts from the mounted distribution ISO, by typing:

cp /ADT-1.0.3-26730-NO_TNODE.iso/scripts/adt_pg_* /opt/EMC/ADT/scripts




cd /opt/EMC/ADT/scriptschmod 755 *chown postgres:postgres *


chmod 755 /export/backupchown postgres:postgres /export/backup

The PostgreSQL backup and restore scripts are now installed and ready to run.

Phase 5: Installing security loggerThe security logger will monitor and manage security events in the Avamar Data Transport system. It is recommended that you install the security logger on the control node.

To install the Security Logger:

1. Log in as root on the control node.

2. From the mounted ADT-1.0.3-26730-NO_TNODE.iso image, copy the/ADTFrameworkSecurityLogger-linux-x64-setup.bin to the /opt directory.


chmod 755 ADTFrameworkSecurityLogger*


./ADTFrameworkSecurityLogger-linux-x64-setup.bin

If your DISPLAY environment variable is set to anything, the install program will attempt to run as an X-application. If you want to run in this mode you will need to have an X-server running on your local host and set the DISPLAY variable on the control node to point to your local host.

If the display variable is not set, or if you set it to nothing, the program will run in text mode.

5. Read the license agreement and accept it.

6. Accept the default install location or type the location where you want the security logger to be installed.

7. Type the hostname where you installed the ADT framework software. In most cases this will be the name of the control node.

Be consistent in how you type hostnames. If you type just the hostname (for example, magma123), type all hostnames that same way. If you type fully qualified domain names (for example, magama123.test.local), type all hostnames that way.

8. Accept the default host port of 61617.



9. Type and then retype a password for the security logger lockbox.

The password must contain at least eight characters including at least one uppercase and one lowercase letter, at least one numeric character, and at least one special character ( !@#$%^&*()?_><”:;’,./ ). An example of a satisfactory password would be egp$PGE2.

10. After the installation summary appears, continue the installation.


12. Confirm that you are ready to continue installing.

After the setup program finishes, the security logger will be installed.

Configuring security events archiving

Using the Avamar Data Transport GUI, the user can archive security events. Archived security events are removed from the Avamar Data Transport display, and are written to the file SecurityArchive.xml.

This file exists at the location specified in the/opt/EMC/IMFSecurityLogger/config/SecurityLog.config file between the <archiveLocation> and </archiveLocation> tags. For example, setting the following line in the SecurityLog.config file:

<archiveLocation>/opt/EMC/IMFSecurityLogger</archiveLocation>

would place the SecurityArchive.xml file in the /opt/EMC/IMFSecurityLogger directory.

If no value is placed between the tags, the SecurityArchive.xml file will be written to the root directory (/).

After making any changes to SecurityLog.config, restart the security logger service by going to directory /etc/init.d and typing:

service securitylogger restart

Phase 5: Installing security logger 43


Phase 6: Configuring Avamar Data Transport frameworkThe Avamar Data Transport framework installation installs a web server. To access the framework you can use either Internet Explorer (IE) or Mozilla Firefox. Avamar Data Transport supports the versions of browsers identified in the EMC Avamar Compatibility and Interoperability Matrix.

With IE you need to turn off client side caching. You can do this by going to Tools > Internet Options > Browsing History > Settings, selecting Every time I visit the webpage, and then clicking OK.

With Firefox, you can clear client side caching by using the keyboard shortcut Ctrl-Shift-Delete and making sure Cache is selected and then clicking Clear Private Data Now.

To access and configure the framework:

1. Start the browser.

2. Type the hostname or IP address of the Avamar Data Transport control node in the browser's address field.

The connection uses HTTPS. Make sure to preface the name or address with https.

For example:

https://lava4245 or https://10.100.10.11

The Setup Lockbox Password screen appears.

3. In the Enter Password field, type a password for the framework lockbox.


4. Retype the password in the Confirm Password field, and click Save Lockbox Changes.

The Create ADT Admin Account screen appears.



5. On the Create ADT Admin Account screen, type information about the suser user. When finished, click Save Administrator Account.

6. On the EMC Avamar Data Transport screen, log in to the suser account using the password you specified in step 5.

The Avamar Data Transport framework is now configured.

Phase 6: Configuring Avamar Data Transport framework 45


Phase 7: Installing the Avamar Data Transport applicationAfter you have logged in to framework, use the Applications springboard in the Administration workspace to install the Avamar Data Transport application.

Before installing the Avamar Data Transport application, you must copy the file named adt.zip to a location where a client running a browser can access it. This file can be accessed from a local file system or a network file system.

To install the Avamar Data Transport application:

1. Start the browser.

2. Type the hostname or IP address of the Avamar Data Transport control node in the browser's address field.

The connection uses HTTPS. Make sure to preface the name or address with https.

For example:

https://lava4245 or https://10.100.10.11

The login screen appears.

3. On the EMC Avamar Data Transport screen, log in to the suser account.



4. On the upper-left corner of the screen, click WORKSPACES.

5. Click the Administration icon.

Phase 7: Installing the Avamar Data Transport application 47


6. Click TOOLBAR to expand the Administration Springboards list.

7. Select the Applications checkbox in the Springboards list.

8. Click TOOLBAR to close the Springboards list.

9. Click WORKSPACES to close the workspace selection screen.



10. On the Applications springboard, click Install.

11. On the Application Installation dialog box, click Browse, and browse to the location of ADT.zip, and then click Open.



The ADT.zip file can be found in the installers directory of the ADT-1.0.3-26730-NO_TNODE ISO image.

12. On the Application Installation dialog, click Install.

A message displays telling you the application installed successfully.

13. Click OK.

The Avamar Data Transport application is now installed.



Click WORKSPACES, and then click the ADT icon to view the Avamar Data Transport application springboards. If no springboards are displayed, click TOOLBAR and select the checkboxes next to the available springboards.

This host, where the Avamar Data Transport application is installed, is called the control node.


CHAPTER 5Installing the Avamar Data Transport System Service

The following topics describe how to install and configure the Avamar Data Transport System Service.

◆ About the Avamar Data Transport system service .................................................... 54◆ Check network connectivity..................................................................................... 54◆ Synchronizing with NTP ........................................................................................... 54◆ Identifying the highest plug-in version .................................................................... 55◆ Installing the Avamar Data Transport system service ............................................... 55◆ Updating the lockbox with transport node passwords.............................................. 56

Installing the Avamar Data Transport System Service 53

Installing the Avamar Data Transport System Service

About the Avamar Data Transport system serviceThe Avamar Data Transport system service is a small application that runs on the primary Avamar server or servers. This application provides the communication infrastructure for Avamar Data Transport to communicate with the Avamar server.

Check network connectivityUsing either DNS or entries in the /etc/hosts file, the Avamar server must be able to communicate with other hosts in the Avamar Data Transport system. From the Avamar server you must be able to successfully ping the following hosts by name:

◆ Control node◆ Each tape backup server you will be using

Synchronizing with NTPAll of the hosts of the Avamar Data Transport system must synchronize with the same NTP server, and it is recommended that they use the NTP server that the Avamar server is syncing with.

To determine which NTP server the Avamar server is using, log in to the Avamar server as root and type the following command:

ntpq -p

The output of the command looks similar to this:

[root@lava4245 ~]# ntpq -p remote refid st t when poll reach delay offset jitter============================================================================== 10.5.142.16 10.254.140.22 4 u 62 64 1 1.474 -670.18 0.001 LOCAL(0) LOCAL(0) 10 l 61 64 1 0.000 0.000 0.001

If all the hosts in the Avamar Data Transport system can use the NTP server that the Avamar server is currently configured to use, you will not need to change the NTP configuration on the Avamar server.



However, if for some reason, the other hosts cannot reach this NTP server, you will need to change the Avamar configuration to use an NTP server that all the hosts can reach.

To change the NTP server that the Avamar server is using, run the asktime utility as user dpn from the Avamar console.

Identifying the highest plug-in versionUsing the Avamar Administrator, identify the “Highest Plug-in Version” numbers that are installed on the Avamar server. You will need to install client plug-ins of the same version number or later on the transport node.

You can find the “Highest Plug-in Version” in the Avamar Administrator by logging in to the Avamar server and navigating to Tools > Manage Agents & Plug-ins.

Make a note of this information for later use.

Installing the Avamar Data Transport system serviceTo install the Avamar Data Transport system service:

1. Log in as root on the Avamar server.

2. From the mounted ADT-1.0.3-26730-NO_TNODE ISO image, copy the/ADT-1.0.3-26730-NO_TNODE/installers/TransportSystemService-linux-x64-setup.bin file to the /opt directory.


chmod 755 Transport*


./TransportSystemService-linux-x64-setup.bin

Identifying the highest plug-in version 55



6. Accept the default installation directory or type a different directory.

7. Type the name of the ADT framework host. This is the name of the control node.

8. Accept the default port of 61617 to communicate with the ADT framework.

9. Set a lockbox password for the system service.

10. After the installation summary displays, continue with the installation.


12. Confirm that you want to continue installing.

The Avamar Data Transport system service is now installed on the Avamar server.

Repeat the steps contained in this chapter on each Avamar server in your system.

Updating the lockbox with transport node passwordsBy default, the Avamar Data Transport system service assumes that the transport nodes will be installed with the default MC user password. If you are planning to install the transport nodes with a different MC user password, or if the transport nodes have already been installed with a different password, run the following script to update the Avamar Data Transport system service lockbox with the new password.

The MC user password can be different between Avamar servers as well as between Avamar servers and the transport nodes. However, the MC user password on all the transport nodes must be the same.

1. Log in to the Avamar server as root.

2. On the command line, type enter following command:

cd /opt/EMC/TransportSystemService/config

3. Type the following two commands:

export PATH=/opt/EMC/TransportSystemService/jre/bin/:$PATH

export LD_LIBRARY_PATH=/opt/EMC/TransportSystemService/lib/native/:$LD_LIBRARY_PATH


java -jar ../lib/LockBoxTool.jar set Node_MCUser_Password <transportNodePassword>

where transportNodePassword is the MC user password of the transport nodes.

The password for the transport nodes has now been successfully updated in the lockbox. To verify the password setting you can type:

java -jar ../lib/LockBoxTool.jar display Node_MCUser_Password


CHAPTER 6Installing Transport Nodes

The following topics describe how to install and configure the transport nodes.

◆ About transport nodes ............................................................................................ 58◆ Pertinent sections of the AVE install guide............................................................... 58◆ Using the Avamar Data Transport appliance ............................................................ 59◆ Modifying the install.conf file .................................................................................. 59◆ Updating client plug-ins .......................................................................................... 60◆ Running the adt-ave.sh script.................................................................................. 60◆ Licensing transport nodes ....................................................................................... 61◆ Installing and configuring the NetWorker client ....................................................... 61◆ Installing and configuring the NetBackup client....................................................... 62

Installing Transport Nodes 57

Installing Transport Nodes

About transport nodesThe transport node will serve as the target of replication from the Avamar servers in your system. The transport node is an AVE node that has been heavily modified for data transport purposes.

For the installation of transport nodes, do not use the standard Avamar Virtual Edition OVF appliance. You must use the adt-1.0.2.ovf appliance contained on the Avamar Data Transport ISO image.

As the transport node is a modified version of the AVE server, the first step is to install Avamar Data Transport appliance as if it were AVE 5.0. To do this, follow the instructions found in the EMC Avamar Virtual Edition 5.0 System Installation Guide.

Pertinent sections of the AVE install guideSpecifically, you will want to perform the installation steps in the following sections of the EMC Avamar Virtual Edition 5.0 System Installation Guide:

◆ “Preparing the Virtual Machine”—Before proceeding with these steps refer to “Using the Avamar Data Transport appliance” on page 59 below.

◆ “Running ave-part.pl”

◆ “Running netconfig”

◆ “Running dpnnetutil”

◆ “Running Benchmark Testing”—EMC requires that you perform benchmark testing and that you keep the test results. Your system must meet 80% of the minimal write and seek throughput values specified in the "Analyzing Benchmark Results" section of the EMC Avamar Virtual Edition 5.0 System Installation Guide.

◆ “Run avqinstall”—Before proceeding with these steps refer to “Modifying the install.conf file” on page 59 below.



Do not run ave-post.sh or perform other Post-Install tasks.

Using the Avamar Data Transport applianceWhen you prepare the transport node by following the instructions in the “Preparing the Virtual Machine” section of the EMC Avamar Virtual Edition 5.0 System Installation Guide, you will need to select the Avamar Data Transport appliance. In step 5, after you select Import or Deploy browse to the adt-1.0.2.ovf file on the mounted Avamar Data Transport ISO image. Then follow the rest of the instructions in “Preparing the Virtual Machine.”

In the Import or Deploy steps select only adt-1.0.2.ovf. Do not select Avamar “Virtual Edition 5.0.ovf,” ave-4.1.2.ovf, or ave-1.2.ovf.

Modifying the install.conf fileIn step 2 of the “Run avqinstall” section of the EMC Avamar Virtual Edition 5.0 System Installation Guide, you are asked to edit the following file:

/usr/local/avamar/var/install.conf

Edit the file by removing the # symbol from the following lines, and by providing the information specified below:

◆ lockbox_password=PASSWORD—where PASSWORD specifies the Avamar lockbox password.

All the transport nodes in the Avamar Data Transport system must have the same MC user password. If you do not use the default password for the transport nodes, you must update the Avamar Server’s lockbox with the alternate transport node password. “Updating the lockbox with transport node passwords” on page 56 provides instructions on how to do this.

◆ local_time_zone=TIMEZONE—where TIMEZONE is the time zone for the transport node. For example, this line might look similar to this:

local_time_zone=America/Boise

◆ time_servers=SERVER—where SERVER is the NTP server being used by all the hosts of the Avamar Data Transport system

After you have modified the install.conf file, save your changes.

In step 3 of the “Run avqinstall” section, you will need to run avquinstall with the --noconnectemc option. For example:

avqinstall --noconnectemc

Using the Avamar Data Transport appliance 59


If for some reason the avqinstall script does not complete successfully and you are able to determine the problem and correct it, you can re-run avqinstall using the --norequire_clean_system flag. For example, after correcting the problem you encountered, you could type the following on the command line:

avqinstall --noconnectemc --norequire_clean_system

After the avquintsall script completes, verify that the gsan status is “ready” by typing the following command:

dpnctl status

Output similar to the following appears on your screen.

root@lava4032:~/#: dpnctl statusIdentity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)dpnctl: INFO: gsan status: admindpnctl: INFO: MCS status: up.dpnctl: INFO: EMS status: up.dpnctl: INFO: Backup scheduler status: down.dpnctl: INFO: dtlt status: up.dpnctl: INFO: Maintenance windows scheduler status: suspended.dpnctl: INFO: Maintenance cron jobs status: enabled.dpnctl: INFO: Unattended startup status: enabled.

Updating client plug-insBy default, most of the client plug-in versions on the transport node will be 5.0.106. If any of your Avamar servers have “Highest Plug-in Versions” higher than those determined on “Identifying the highest plug-in version” on page 55, you will need to update the transport node client plug-ins to the latest version in use on any of the Avamar servers.

To update the transport node client plug-ins refer to the “Avamar Client-Only System Upgrades” section of the EMC Avamar System Upgrade Manual Rev A02.

Running the adt-ave.sh scriptAfter the dpnctl status command indicates that Avamar gsan status is “ready,” use the adt-ave.sh script to convert the AVE node to an ADT transport node.

To run the adt-ave.sh script:

1. Log in as root on the newly configured transport node.

2. From the /root directory, run the following command:

./adt-ave.sh

After adt-ave.sh has completed, the AVE node will have been configured as an ADT transport node.



Licensing transport nodesAfter running the adt-ave.sh script, you will need to obtain a valid, permanent license for the transport node. “Obtain and Install a Server License” in the EMC Avamar Virtual Edition 5.0 System Installation Guide provides information on how to do this.

Installing and configuring the NetWorker clientThe NetWorker client will need to be installed on each of the transport nodes that you want to back up using the Network server.

To install the NetWorker client to the default location on the transport node, perform the following steps:

1. Log in to the first transport node as root.

2. Copy the following files to the /opt directory:

• lgtoclnt-VERSION.x86_64.rpm• lgtoman-VERSION.x86_64.rpm (optional)

Where VERSION is the version of the client software that matches the version of the NetWorker server.

For example, if you were running version 7.6.3-1 of the NetWorker server, you would copy the following files:

– lgtoclnt-7.6.3-1.x86_64.rpm– lgtoman-7.6.3-1.x86_64.rpm

3. From the /opt directory, change permissions on the setup files by typing:

chmod 755 *.rpm


rpm -ivh lgtoclnt-[Version].x86_64.rpm

where Version is the version of the client software that matches the version of the NetWorker server.

The installer should generate an error message similar to the following:

root@lava4032:/opt/#: rpm -ivh lgtoclnt-7.6.3-1.x86_64.rpmerror: Failed dependencies: libXp.so.6()(64bit) is needed by lgtoclnt-7.6.3-1.x86_64 Suggested resolutions: /var/spool/up2datexorg-x11-deprecated-libs-6.8.2-1.EL.63.x86_64.rpm

If the only failed dependency is “libXp.so.6()(64bit)” then proceed to step 5. If other failed dependencies are reported, you will need to resolve these dependencies before continuing.

5. Type to the following command:

rpm -ivh --nodeps lgtoclnt-[Version].x86_64.rpm

where Version is the version of the client software that matches the version of the NetWorker server.

Licensing transport nodes 61


6. Then, if you want to install the NetWorker client man pages, type:

rpm -ivh lgtoman-VERSION.x86_64.rpm

Where VERSION is the version of the client software that matches the version of the NetWorker server.

7. Start the NetWorker daemons by typing the following command:

/etc/init.d/networker start

8. Because the NetWorker server is on a different host, you must create an /nsr/res/servers file. This file should include a line that identifies the hostname of the NetWorker server.

For example, if the NetWorker server were on a host named magma124 on a domain named test.local, the single entry in the /nsr/res/servers file would be magma124.test.local

The NetWorker client is now installed and running.

Repeat this process on each transport node in your system that you want to back up with NetWorker software.

The “Linux Installation” chapter of the EMC NetWorker Multiplatform Version Installation Guide provides additional information about installing the NetWorker client.

Installing and configuring the NetBackup clientThe NetBackup client software will be pushed to the transport nodes during the process of configuring the NetBackup server.

However, if your NetBackup server is running on Windows, you will not be able to push client software from the Windows NetBackup server to Avamar Data Transport control nodes. You will need to manually, or “locally,” install the NetBackup client on the transport nodes. The “Installing UNIX clients locally” section of the Symantec NetBackup 7.5 Installation Guide for UNIX and Linux provides additional information about installing the NetBackup client.


CHAPTER 7Configuring Tape Backup Servers

The following topics describe how to configure tape backup servers.

◆ About tape backup servers...................................................................................... 64◆ Checking network connectivity ................................................................................ 64◆ Synchronizing with NTP ........................................................................................... 64◆ Configuring the EMC NetWorker tape backup server ................................................ 65◆ Configuring the Symantec NetBackup tape backup server ....................................... 75◆ Testing the NetBackup configuration ....................................................................... 79

Configuring Tape Backup Servers 63

Configuring Tape Backup Servers

About tape backup serversOne of the required components of the Avamar Data Transport system is a functioning tape backup system. Supported tape backup systems are identified in the EMC Avamar Compatibility and Interoperability Matrix.

These instructions assume that the backup server has been installed and has been tested to ensure that files can be backed up to and restored from tape.

For EMC NetWorker, create a backup group for each transport node you want to back up. For Symantec NetBackup, create a policy for each transport node.

Checking network connectivityUsing either DNS or entries in the /etc/hosts file, the tape backup server must be able to communicate with other hosts in the Avamar Data Transport system. From the Avamar server, you must be able to successfully ping by name the following hosts:

◆ Avamar Server◆ Control node◆ Each transport node that you installed.

Synchronizing with NTPAll of the hosts of the Avamar Data Transport system need to synchronize with the same NTP server. Ensure that the operating system that is hosting your tape backup software is synchronized with the NTP server that the Avamar server is using.



Configuring the EMC NetWorker tape backup serverTo configure the EMC NetWorker server, use the NetWorker Management Console.

These instructions assume that the NetWorker server has been installed and is properly configured to back up to and restore from tape. It also assumes the NetWorker Management Console has been installed on a client that can connect with the NetWorker server.

To configure NetWorker:

1. Log in to the NetWorker Management Console as a user who has rights to configure the server.

2. At the top left of the screen, click the Enterprise icon.

3. In the left pane, click the host you want to back up with.

4. Under Managed Application, right-click NetWorker.

5. Click Launch Application.

The NetWorker Administration window appears.

6. At the top left of the NetWorker Administration window, click the Configuration icon.

Configuring the EMC NetWorker tape backup server 65


7. In the tree panel on the left of the NetWorker Administration screen, right-click Groups, and then click New.



8. In the Name field, type the name of the transport node you want to back up. This name should resolve through DNS or entries in the /etc/hosts file to the IP address of the transport node.



9. On the Advanced tab, select full from the Level list and clear the Force incremental checkbox.

If you do not clear Force incremental, it is possible to lose access to the data that is written to tape permanently.

10. Click OK.



11. In the tree panel on the left, right-click Clients, and then click New.

12. In the Name field, type the name of the transport node you want to back up. This name should resolve through DNS or entries in the /etc/hosts file to the IP address of the transport node.

13. In the Browse policy field, select Day.

14. Ensure that the Scheduled backup option is selected.



15. In the Save set field, type all of the data mount points, one per line.

For full TB transport nodes, there are typically six mount points: /data01,/data02, /data03, /data04, /data05, and /data06.

For 2 TB transport nodes, there are typically twelve mount points: /data01,/data02, /data03, /data04, /data05, /data06, /data07, /data08, /data09, /data10, /data11, /data12.

You can also set Index Policy Retention on this page. However, be aware that tape-level retention is determined by the following precedence: • Pool Retention Policy • Overrides to Index Policy Retention (such as those coming from the Avamar Data Transport application) • Index Policy Retention (which is set on this screen)

For example, if you were to set the Index Policy Retention on this screen to one year, then any Avamar Data Transport overrides would take precedence as would any Pool Retention Policies set on media pools assigned to this client.



16. In the Group field, clear the Default checkbox and select the checkbox next to the group you want the client files backed up to. (This is the group you created in steps 7–10.)

17. Click the Globals (2 of 2) tab.



18. In the Remote access text box, type *@*

This will allow data backed up from any transport node to be recovered to this transport node.

19. Click OK.

20. Repeat steps 2–19 for each transport node that you want to back up to tape.

NetWorker is now configured to work with the Avamar Data Transport application.

Testing the NetWorker configuration

Before continuing with the installation process, test that NetWorker can back up each of the transport nodes you have installed.

To test the NetWorker configuration:

1. Log in to the NetWorker Management Console as a user who has rights to run backups.








6. At the top left of the NetWorker Administration window, click the Monitoring icon.

7. Right-click one of the groups you have configured to back up a transport node, and click Start.

8. Confirm that you want to start the backup.



9. Right-click the group you just backed up and select Show details.

After the manual backup completes, check to see if all the following conditions are met:

• Percentage Complete is 100%

• The details window reports “Completed Successfully” for each of your save set volumes (for example, /data01, /data02, /data03, and so on.)

• The details window reports nothing in the “Failed” fields

10. Repeat steps 6 – 9 for each group you have configured to back up transport nodes.

When test backups of each of the groups have completed successfully, NetWorker is ready to back up transport nodes.

Specifying the ADT tape library

If your Networker server is connected to multiple libraries, you need to identify the library you want ADT to use for transport and recovery jobs. This configuration step is included as part of the ADT transport node services install described in the next chapter. “Choosing a library in NetWorker” on page 84 provides details.



Configuring the Symantec NetBackup tape backup serverTo configure the Symantec NetBackup server, use the NetBackup Administration Console and the command line of the tape backup server.

These instructions assume that the NetBackup server has been installed and is properly configured to back up to and restore from tape. It also assumes that the NetBackup Administration console has been installed.

To configure NetBackup:

1. From the NetBackup server command line, type:

/usr/openv/netbackup/bin/jnbSA

The NetBackup Administration Console starts.

2. Log in to the NetBackup Administration Console as a user who has privileges to configure NetBackup installation.

3. In the far left-hand pane, expand NetBackup Management, and then click Policies.

4. In the All Policies pane, right-click a blank area of the pane, and then select New Policy.

5. Type a policy name in the Add a new Policy dialog box.

It is strongly suggested that you include “transport” and node size in the policy name. For example, you might type “Backup_transport_1TB” as the policy name.

6. Click OK.

Configuring the Symantec NetBackup tape backup server 75


7. On the Attributes tab of the Change Policy dialog box, you can set whatever attributes your environment requires.

Ensure that the “Cross mount points” and “take checkpoint” checkboxes are not selected.

8. On the Schedules tab, click New.

9. In the Name field of the Attributes tab of the Add Schedule dialog box, type a name for the schedule.

10. Ensure that Type of Backup is set to Full Backup.

If, on the Add Schedule dialog box, you change Type of backup to any selection other than Full Backup, you may lose access to data that is written to tape permanently.

11. Click OK.

12. On the Clients tab, click New.

13. In the Client Name field, type the hostname of a transport node you want to back up.

The client name should be resolvable through DNS or through the /etc/hosts file on the tape backup server.



14. From the Hardware and operating system list, select Linux, Redhat2.6, and then click Add.

When adding policies you can optionally set retention periods from the Schedules tab. Retention policies set in the Avamar Data Transport application override these values.

15. Repeat steps 12–14 until all the transport nodes have been added.

16. Click Close.

17. On the Backup Selections tab of the Change Policy dialog box, click New.

18. In the Add Backup Selection dialog box, type the first data mount point in the Pathname or directive field.

19. Click Add.

For full TB transport nodes, there are typically six mount points: /data01, /data02, /data03, /data04, /data05, and /data06

For 2 TB transport nodes, there are typically twelve mount points:/data01, /data02, /data03, /data04, /data05, /data06, /data07, /data08, /data09, /data10, /data11, /data12

Configuring the Symantec NetBackup tape backup server 77


20. Repeat steps 18 – 19 until the six (or twelve) mount points have been added.

21. Click OK, and then click Close.

22. Close the NetBackup Administration Console, by selecting File > Exit from the main menu.

You now need to “push” the NetBackup client software to each transport node in your system.

23. From the tape backup server command line, type the following commands:

cd /usr/openv/netbackup/bin./install_client_files ssh ADTNODE

Where ADTNODE is the name of a transport node that needs to be backed up to tape.

For example, in the following command, lava4031 is the name of the transport node:

./install_client_files ssh lava4031

24. Repeat step 23 for all the transport nodes that will be backed up by the tape backup server.

NetBackup is now configured to work with the Avamar Data Transport application.



Testing the NetBackup configurationBefore continuing with the installation process, test that NetBackup can back up each of the transport nodes you have installed:

1. From the NetBackup server command line, type:



2. Log in to the NetBackup Administration Console as a user with privileges to configure NetBackup installation.

3. In the All Policies column, expand the policy that you created to back up transport nodes.

4. Click Schedules.

5. In the far right-hand pane, right-click the schedule name and select Manual Backup.

6. Click a schedule.

7. Click the transport node you want to back up (which should be displayed in the Clients field).

8. Click OK.

9. In the far left pane, click Activity Monitor.

Testing the NetBackup configuration 79


10. In the Jobs pane, right-click the job you just started and select Details.

After the manual backup completes, check to see if all the following conditions are met:

• Percent complete is 100%• The status field reports the operation “successfully completed”

11. Repeat steps 3–10 for each policy you have configured to back up transport nodes.

When test backups of each of the policies have completed successfully, the NetBackup is ready to back up transport nodes.


CHAPTER 8Installing Transport Node Services

The following topics describe how to install transport node services.

◆ About transport node services ................................................................................ 82◆ Check network connectivity..................................................................................... 82◆ Installing transport node services ........................................................................... 82◆ Changing the tape backup server user..................................................................... 87◆ Changing the tape backup server password ............................................................ 87◆ Changing database communication settings ........................................................... 88

Installing Transport Node Services 81

Installing Transport Node Services

About transport node servicesTransport node services facilitate communication between the transport nodes and other components in the Avamar Data Transport system. Installing transport node services provides the infrastructure for Avamar Data Transport to communicate with transport nodes.

Check network connectivityUsing either DNS or entries in the /etc/hosts file, each transport node must be able to communicate with other hosts in the Avamar Data Transport system. From each transport node, you must be able to successfully ping by name the following hosts:

◆ Control node◆ Each Avamar server that will replicate to the transport node◆ Each tape backup server that will be backing up the transport node

Installing transport node servicesTransport node services must be installed on each transport node in the system. To install transport node services:

1. Log in to the transport node as root.

2. From the mounted ADT-1.0.3-26730-NO_TNODE ISO image, copy the/ADT-1.0.3-26730-NO_TNODE/installers/TransportNodeService-linux-x64-setup.bin file to the /opt directory.


chmod 755 TransportNodeService*


./TransportNodeService-linux-x64-setup.bin



If your DISPLAY environment variable is set to anything, the install program will attempt to run as an X-application. If you want to run in this mode you will need to have an X-server running on your local host and set the DISPLAY variable on the control node to point to your local host.

If the display variable is not set, or if you set it to nothing, the program will run in text mode.


6. Specify the directory where you want node services installed.

7. Type the name of the host where you installed the Avamar Data Transport framework (your control node).

8. Accept the default port 61617 to communicate with the framework.

9. Set a lockbox password for the system service.


10. Type the name of the tape backup server where your backup software is installed.

11. Type the root user on the tape backup server. (If the tape backup server is running on Windows, type the administrator user.)

12. Type the root user’s password. (If the tape backup server is running on Windows, type the administrator password.)

If you want to authenticate using SSH keys, leave the password for the tape backup server blank, and then after you have installed transport node services perform the steps in the “Configuring SSH keys” on page 86.

13. Type the name of the archive catalog host. This is the host where you installed the PostgreSQL database.

In most cases this will be your control node.

14. Type port number 5558 as the archive catalog database port.

15. After the installation summary is displayed, continue installing.


17. Confirm that you are ready to continue installing.

After the install program finishes, transport node services are ready for use.

Repeat this procedure on each transport node.

Installing transport node services 83


Choosing a library in NetWorker

If your tape backup server is running with NetWorker, and if it is connected to multiple libraries, you need to identify the library you want ADT to use for transport and recovery jobs. To do this you need to uncomment and set the library.name= line in the 3rdpartybackup.properties file found in the /opt/EMC/TransportNodeService/config directory.

The most straightforward way to determine the names of the libraries that NetWorker is attached to is to use the nsradmin command. For example, if you wanted to tell ADT to use the ADIC library which is connect to the NetWorker server running on lava4148, you would use the following process:

1. Log in a root to an ADT transport node that has the NetWorker client installed on it.


nsradmin -s lava4148

3. From the nsradmin> prompt type:

visual

4. While in visual mode use the arrows keys to choose Select



5. Use the arrow keys to choose NSR jukebox

6. Use the Next and Prev options to see all the libraries connected to NetWorker.

7. After determining the name of the library you want to use, in this case “ADIC@sg3,” type q and then q.

8. Change to the /opt/EMC/TransportNodeService/config directory

9. Edit the 3rdpartybackup.properties file, and then uncomment and set the library.name= line to “ADIC@sg3”.

# which library, in a multiple attached library solution, should ADT query for# media present. By default if more than one library is attached and managed# by the archive server, the query will hang. This resource allows the end-user# to override that behavior.library.name=ADIC@sg3

ADT is now configured to the use the specified library.

Installing transport node services 85


Configuring SSH keys

Even if you do not want to configure your system to communicate with SSH keys, you are still required to have an SSH server running on your tape backup server.

In order to allow the Avamar Data Transport transport node to communicate with a tape backup server using SSH keys, you will need to have a public key and private key pair. You can create your own key pairs or you can use the following keys included with Avamar Data Transport:

◆ Private Key: adt_node◆ Public Key: adt_node.pub

These file are located in the config directory where transport node services was installed, usually /opt/EMC/TransportNodeServices/config.

On a Solaris or Linux tape backup server, the public key should be placed in the directory ~/.ssh. This is the .ssh directory under the root home directory on the tape backup server.

The generation and placement of the public key on Windows varies according to the SSH server that is running. Consult the documentation for your SSH server for specific steps for SSH key configuration.

To configure the public key on a Solaris or Linux tape backup server:

1. Login in the tape backup server as root.

2. Change to the ~/.ssh directory.

3. Use the cat command to append the contents of the public key to the authorized_keys2 file. For example, if you were using the Avamar Data Transport public key you would enter:

cat adt_node.pub >> authorized_keys2

4. Type chmod 400 authorized_keys2

The Avamar Data Transport transport node is now configured to communicate with the tape backup server using SSH keys.

Using a Different Private KeyBy default, Avamar Data Transport uses the adt_node private key found in the /opt/EMC/TransportNodeService/config directory. If you want to use a different private key or put the private key in a different location, perform the following steps:

1. Log in to the Avamar Data Transport transport node you are configuring as root.

2. Change to the config directory for transport node services, usually /opt/EMC/TransportNodeService/config



3. If you want to use a private key other than adt_node or want to put the private key in a different location, uncomment the following line in the identity.properties file:

# identity=

Then enter the path and file name of the private key as the value of identity=


service nodeservice restart

Avamar Data Transport is now configured to use the private key specified.

Changing the tape backup server userIf the root user on the tape backup server changes after you install transport node services, you will need to update the user in the lockbox on each transport node. You can modify the tape backup server user on the transport using the changeUser.sh script.

To change the tape backup server user in the lockbox of the transport node:

1. Log in to the transport as root.

2. Change to the /opt/EMC/TransportNodeService/bin directory.


./changeUser.sh <newBackupServerUser>

where newBackupServerUser is the root user of the tape backup server.

For example, if the root user on the tape backup server had been changed to “ExampleUser” you would type the following command and see the following results:

root@lava4032:/opt/EMC/TransportNodeService/bin/#: ./changeUser.sh ExampleUserItem DB_User is set to "ExampleUser".root@lava4032:/opt/EMC/TransportNodeService/bin/#:

The new root user of the tape backup server is now stored in the lockbox of the transport node. Repeat this procedure on each transport node that is using the tape backup server.

Changing the tape backup server passwordIf the root password on the tape backup server changes after you install transport node services, you will need to update the password in the lockbox on each transport node. You can modify the tape backup server password on the transport using the changePass.sh script.

To change the tape backup server password in the lockbox of the transport node:

1. Log in to the transport as root.

2. Change to the /opt/EMC/TransportNodeService/bin directory.


./changePass.sh <newBackupServerPasswd>

where newBackupServerPasswd is the root password of the tape backup server.

Changing the tape backup server user 87


For example, if the root password on the tape backup server had been changed to “brt76iklm!” you would type the following command and see the following results:

root@lava4032:/opt/EMC/TransportNodeService/bin/#: ./changePass.sh brt76iklm!Item DB_UserPassword is set to "brt76iklm!".root@lava4032:/opt/EMC/TransportNodeService/bin/#:

The new root password of the tape backup server is now stored in the lockbox of the transport node. Repeat this procedure on each transport node that is using the tape backup server.

Changing database communication settingsBy default, the transport node will communicate “over the wire” with the Avamar Data Transport database (or catalog) in an encrypted manner using ssh tunneling. However, you can modify the default behavior by inserting the entries listed next into the Catalog.properties file found in the following directory on the transport node:

/opt/EMC/TransportNodeService/config

In most cases the entries identified next will not be present in the Catalog.properties file, so you will need to insert them.

◆ tunnel — This value can be set or not set according to the table below

◆ tunnelPort — By default, the ssh tunneling port is set to the same port used by the Avamar Data Transport database, which by default is 5558. You might need to change the tunnel port if the default port is being used by another process on the transport node. If you want to use a different ssh tunneling port, type a new value for this entry.

◆ tunnelUser — By default, the ssh tunnel will be created using the user who owns the Avamar Data Transport database. If the database was installed with an owner other than postgres, set this entry to the name of that user.

As an example, the following Catalog.Properties file is configured to use the host port 5080 for ssh tunneling using the user skerrit.

root@lava4033:/opt/EMC/TransportNodeService/config/#: cat Catalog.properties

serverName=localhostportNumber=5558databaseName=ada_cataloguser=ada_userssl=falsetunnel=truetunnelport=5080tunneluser=skerrit

Table 5 tunnel value descriptions

tunnel=true All communication with the database will be encrypted. If tunneling cannot be established, communications will fail.

tunnel=false All communication with the database will be unencrypted.

tunnel=or not present in file

If the “tunnel” entry is not in the Catalog.properties file or if the “tunnel” entry is not set to any value, Avamar Data Transport will attempt to establish encrypted communication with the database. If it fails to establish tunneling, then Avamar Data Transport will establish communication with the database in an unencrypted manner.


CHAPTER 9Verifying Avamar Data Transport Installation

The following topics describe how to verify the Avamar Data Transport installation.

◆ Verifying Avamar servers ......................................................................................... 90◆ Verifying transport nodes ........................................................................................ 91◆ Verifying the tape backup server ............................................................................. 91

Verifying Avamar Data Transport Installation 89

Verifying Avamar Data Transport Installation

Verifying Avamar serversAfter the installation has been completed, verify that the components of the Avamar Data Transport system are accessible and responding appropriately. To do this, use the Avamar Data Transport GUI.

To verify that the Avamar servers in your system are configured and functioning:

1. Log in to the Avamar Data Transport GUI.

2. Click WORKSPACES to expand it.

3. Click the ADT icon.

The ADT workspace appears.

4. Verify that the Avamar Servers springboard contains all the Avamar servers that you want to back up with Avamar Data Transport. If you do not see all the Avamar servers you expect, “Troubleshooting problems with Avamar servers” on page 100 provides some troubleshooting information.

There can be a delay of up to 10 minutes before correctly configured Avamar servers are displayed in the GUI.



Verifying transport nodesTo verify that the transport nodes in your system are functioning as expected:

1. Log in to the Avamar Data Transport GUI.

2. Click WORKSPACES to expand it.

3. Click the ADT icon.

The ADT workspace appears.

4. In the ADT Server springboard, click Launch ADT Server Viewer.

Verify that the ADT Server screen contains all the transport nodes that you configured to back up Avamar servers. If you do not see all the transport nodes you expect, “Troubleshooting problems with transport nodes” on page 102 provides some troubleshooting information.

There can be a delay of up to 10 minutes before correctly configured transport nodes are displayed in the GUI.

Verifying the tape backup serverThe test to verify the tape backup server was performed as part of the tape backup server installation procedure. “Testing the NetWorker configuration” on page 72 or “Testing the NetBackup configuration” on page 79 provide information on verifying the tape backup configuration.

Verifying transport nodes 91

CHAPTER 10Troubleshooting

After Avamar Data Transport has been installed and configured, it is possible that components in the Avamar Data Transport system may stop working or not be configured as expected. If this happens, the following troubleshooting topics provide some direction on how to identify and resolve some common problems.

◆ About logging ......................................................................................................... 94◆ About services ........................................................................................................ 94◆ Troubleshooting Avamar Data Transport GUI issues ................................................. 95◆ Troubleshooting problems with the control node..................................................... 99◆ Troubleshooting problems with Avamar servers..................................................... 100◆ Troubleshooting problems with transport nodes.................................................... 102◆ Troubleshooting tape backup server errors............................................................ 104

Troubleshooting 93

Troubleshooting

About loggingThe components of the Avamar Data Transport create log files that can be useful in analyzing the function of the system. The table below identifies the location and content of some of these log files.

About servicesThere are times when problems can be fixed by restarting Avamar Data Transport services. The next table identifies some of the services that can be restarted. The commands are issued as root on the specified host.

Table 6 Log file locations for Avamar Data Store components

Host and Component Log File

All Avamar Data Transport Hosts: Install

/tmp/bitrock_installer.log

Control Node: Framework /opt/EMC/IMF/apache-tomcat/logs/IMFTrace.log/opt/EMC/IMF/apache-tomcat/logs/catalina.out

Control Node: Security Logger

/opt/EMC/IMFSecurityLogger/logs/SecurityTrace.log

Transport Node /opt/EMC/TransportNodeService/log/AdaNodeService.log/opt/EMC/ TransportNodeService /log/jsvcerr.log/opt/EMC/ TransportNodeService /log/jsvcout.log

Avamar Server /opt/EMC/TransportSystemService/log/AdaGridTrace.log/opt/EMC/ TransportSystemService /log/jsvcerr.log/opt/EMC/ TransportSystemService/log/jsvcout.log

/usr/local/avamar/var/cron/replicate_adt_8ada*.log (latest)

Table 7 Avamar Data Store services that can be restarted

Host Restart Command

Control Node: Framework

service imf-server restartservice imf-messagebus restart

Control Node: Security Logger


Transport Node service nodeservice restart

Avamar Server service gridservice restart


Troubleshooting

Troubleshooting Avamar Data Transport GUI issuesSome system problems may manifest themselves on the Avamar Data Transport GUI. The following sections describe some possible conditions that may be encountered in the GUI.

Transport or recover tasks are failing

Each transport node pings the tape backup server every five minutes to ensure that the tape backup services are still available. If the services are unavailable (because the network connection is broken or the services are down) then the transport node will fail the job that is currently in process.

A situation, then, where all the transport jobs displayed in the GUI start failing is often the result of a lost network connection between the transport nodes and the backup server or a situation where the tape backup services are down or not responding.

To correct the problem, re-establish the network connection between the transport nodes and the tape backup server or restart the services on the tape backup server.

Transport tasks seem to hang

If a transport job starts and seems to hang, or if takes more than five minutes to reach 5% and start replication, the transport node may have become unlicensed. With unlicensed transport nodes, Avamar will wait 10 hours to start replication and then fail.

You can check to see if the transport node has become unlicensed by examining the gsan.log file in the /data01/cur/ directory on the transport node. The errors that indicate an unlicensed node are:

2012/04/17-15:19:02.05965 {0.0} [licensevalidator:111] ERROR: <0948> license grace period expired 1 days ago (Sun Apr 15 22:40:07 2012)

2012/04/17-15:19:02.05977 {0.0} [licensevalidator:111] FATAL ERROR: <0001> licensevalidator::body no valid license found

If the transport node is unlicensed, you will need to relicense it following directions contained in the “Obtain and Install a Server License” in the EMC Avamar Virtual Edition 5.0 System Installation Guide.

Replication to ADT is timing out

When an Avamar server begins replicating to an ADT transport node, a specific time period is specified for how long the replication will run. If the replication process takes longer than the time specified, the replication job times out, and ADT displays a red error message in the Queued Tasks springboard in the ADT GUI.

Detecting the time-out errorTo determine if the task failed because of a replication time-out, you will need to examine the AdaGridTrace.log which can be found on the Avamar server in the following directory:

/opt/EMC/TransportSystemService/log/

Troubleshooting Avamar Data Transport GUI issues 95

Troubleshooting

In the AdaGridTrace.log you will be looking for two entries:

◆ “validate.Status.FAILED”◆ “replicate finish endtime (without completed)”

An example of how these appear in the log is shown below:

2010-03-05 23:17:53,288 ERROR [BusListener]-model.AvamarADAReplicate: validate:Status.FAILED2010-03-05 23:17:53,288 ERROR [BusListener]-model.AvamarADAReplicate: replicate finish endtime (without completed) 2010/03/05-23:16:52

If you see these two entries in the AdaGridTrace.log file, you will need to look a little higher in the log to determine the replication ID of the replication job that timed out. In the example below, the replication ID is 8adaeb567da07a78:

2010-03-05 23:17:53,040 INFO [BusListener]-model.AvamarSystem: getReplicationStatus: wid [ 8adaeb567da07a78 ]2010-03-05 23:17:53,041 INFO [BusListener]-model.AvamarSystem: getReplicationInfo:[ from file ]2010-03-05 23:17:53,066 INFO [BusListener]-model.AvamarADAReplicate: replicate 6413 starttime 2010/03/05-15:16:442010-03-05 23:17:53,287 INFO [BusListener]-model.AvamarADAReplicate: replicate /TAP/tapfsr01.dsd.hksarg to DSDADT022010-03-05 23:17:53,288 ERROR [BusListener]-model.AvamarADAReplicate: validate:Status.FAILED

2010-03-05 23:17:53,288 ERROR [BusListener]-model.AvamarADAReplicate: replicate finish endtime (without completed) 2010/03/05-23:16:52

Using this ID you can then inspect the replication log of the job that failed. For ADT these logs can be found in:

/usr/local/avamar/var/cron

and they are named with the following convention

replicate_adt_<replicationID>.log

where replicationID is a 16-character ID.

In the example above, where the replication ID was 8adaeb567da07a78, the log file would be:

/usr/local/avamar/var/cron/replicate_adt_8adaeb567da07a78.log

In the log snippet provided below, you can see some key troubleshooting information:

1. Towards the middle of the example, you can see that the replication job was interrupted.

2. Below that you can see that the job was externally cancelled.

3. And, at the bottom of the example, there is an error message indicating that the replication has timed out.

2010/03/05-15:16:44 repl_cron [v2.0 11/13/06]: configfile = '/usr/local/avamar/etc/repl_cron_adt_8adaeb567da07a78.cfg'2010/03/05-15:16:44 ============================== Running adt_cron ==============2010/03/05-15:16:44 ps -efww2010/03/05-15:16:44 ======== starting replication (pid=6413) ========2010/03/05-15:16:44 mccli event publish --code=4600 --message='adt_cron - starting replication (pid=6413)'2010/03/05-15:16:45 0,23000,CLI command completed successfully.. . .


Troubleshooting

2010/03/05-15:16:47 avtar Info <5551>: Command Line: /usr/local/avamar/bin/avtar.bin --flagfile=/usr/local/avamar/etc/usersettings.cfg --password=********* --vardir=/usr/local/avamar/var --server=DSDBKP01 --id=root --bindir=/usr/local/avamar/bin --hfsport=27000 --vardir=/usr/local/avamar/var --bindir=/usr/local/avamar/bin --sysdir=/usr/local/avamar/etc -x --replicate --allbackups --before="2010-03-05 15:12:00" --after="2010-01-05 15:12:00" --allnodes --statistics --informationals=1 --account=/TAP/tapfsr01.dsd.hksarg --expires=365000 --workorderid=8adaeb567da07a782010/03/05-15:16:47 avtar Info <5552>: Connecting to Server (DSDBKP01). . .2010/03/05-15:16:48 avtar Info <6617>: Replicating backup 153, Label "Daily0800-Daily0800-1265371200056", 25.66 GB. . .2010/03/05-23:16:47 avtar Info <5100>: Status 2010-03-05 23:16:47, 12.24 GB (9.896 GB, 80.87% new) 146MB 1% CPU tapfsr01.dsd.hksarg#153::/F:/TPShare/TPSTW(Shift)/Share Folder/shift photos/Photo of 2008/Apr 2008/21Apr08/ - (target server)2010/03/05-23:16:50 *INTERRUPT*2010/03/05-23:16:51 avtar Info <5673>: PARTIAL Backup #1 timestamp 2010-03-05 23:19:46 HKT created. . . 2010/03/05-23:16:51 avtar Info <6149>: Error summary: 1 error: 66182010/03/05-23:16:51 avtar Info <6607>: Writing wrapup to alg file for agent to read2010/03/05-23:16:51 avtar Info <5314>: Command failed (1 error, exit code 10022: Externally cancelled by INT signal)2010/03/05-23:16:51 avtar Stats <6559>: 36.35 MB in 660,088 messages sent to server, 9.932 GB in 658,164 messages received from server.2010/03/05-23:16:51 alarm 287982010/03/05-23:16:51 kill(2) 6857 avtar -x --replicate --allsnapups --before=2010-03-05 15:12:00 --after=2010-01-05 15:12:00 --allnodes --allnodes:1 --stats --info=1 --hfsaddr:1=DSDADT02 --id:1=MCUser --ap:1=MCUser1 --path=/TAP/tapfsr01.dsd.hksarg --path:1=/REPLICATE/DSDBKP01/TAP/tapfsr01.dsd.hksarg --status:1=300 --throttle:1=3.0 --expires=365000 --wid=8adaeb567da07a782010/03/05-23:16:51 REPLICATE ERROR: Command returned 32512 (0x7f00): rununtil -28798 avtar -x --replicate --allsnapups --before='2010-03-05 15:12:00' --after='2010-01-05 15:12:00' --allnodes --allnodes:1 --stats --info=1 --hfsaddr:1=DSDADT02 --id:1=MCUser --ap:1=***** --path=/TAP/tapfsr01.dsd.hksarg --path:1=/REPLICATE/DSDBKP01/TAP/tapfsr01.dsd.hksarg --status:1=300 --throttle:1=3.0 --expires=365000 --wid="8adaeb567da07a78" 2010/03/05-23:16:51 dpncron.pm::docmdout got exit code 32512 from 'replicate_adt --flagfile=/usr/local/avamar/etc/repl_cron_adt_8adaeb567da07a78.cfg', returning 02010/03/05-23:16:51 ======== replication timed-out (pid=6413) ========2010/03/05-23:16:51 mccli event publish --code=4603 --message='adt_cron - replication timed-out (pid=6413)'2010/03/05-23:16:52 0,23000,CLI command completed successfully.2010/03/05-23:16:52 2010/03/05-23:16:52 avmaint infomessage --avamaronly --errcode=4603 'adt_cron - replication timed-out (pid=6413)'2010/03/05-23:16:52 ============================== Finished adt_cron =========

Fixing the replication time-out problemAfter you have determined that replication is failing because it exceeds the specified time-out window, there are two options:

1. If you believe the time-out was an isolated incident that is unlikely to recur, you can use the ADT GUI to “retry” the failed task. ADT still retains all the data that was replicated in the original time-out window, and, in some cases, by re-trying the failed job, ADT can get the rest of the remaining data within replication time-out window.

2. You can increase the replication time-out value. To do this, you would edit the "--timeout=" value in the /usr/local/avamar/etc/adt_cron.cfg file.

Troubleshooting Avamar Data Transport GUI issues 97

Troubleshooting

The configuration file snippet below shows and example of how to increase the replication time-out window to 24 hours:

# REQUIRED: Password of authorized user on destination DPN# --dstpassword=<password of replicate user>

# OPTIONAL: Maximum time replicate can run in one invocation (0=forever)# --timeout=<seconds># 1 hour: --timeout=3600# 2 hours: --timeout=7200# 3 hours: --timeout=10800# 4 hours: --timeout=14400# 5 hours: --timeout=18000# 6 hours: --timeout=21600# 7 hours: --timeout=25200# 8 hours: --timeout=28800# 12 hours: --timeout=43200# 16 hours: --timeout=57600# 20 hours: --timeout=72000# 24 hours: --timeout=86400--timeout=86400

If the /usr/local/avamar/etc/adt_cron.cfg file does not exist, create it by copying one of the two repl_cron.cfg files available on the Avamar server. The active file is /usr/local/avamar/etc/repl_cron.cfg and you will want to use this file first. For example you might type:

cp /usr/local/avamar/etc/repl_cron.cfg /usr/local/avamar/etc/adt_cron.cfg

If the /usr/local/avamar/etc/repl_cron.cfg does not exist, then copy the /usr/local/avamar/bin/repl_cron.cfg file instead. For example you might type:

cp /usr/local/avamar/bin/repl_cron.cfg /usr/local/avamar/etc/adt_cron.cfg

The replication time-out for ADT is now reconfigured.

User events and other messages seem to be getting lost

If user events, or any other type of message appears to be getting lost in the message bus, it is possible that the message bus used by the Avamar Data Transport applications has become unstable. This condition may also be manifested by errors similar to that shown next from the activemq.log found in the /opt/EMC/IMF/apache-activemq/data/ directory:

ERROR RecoveryListenerAdapter - Message id ID:lava3172.lss.emc.com-53045-1252438506221-0:1:1:1:10 could not be recovered from the data store - already dispatched

This condition can be remedied by resetting the message bus using the following procedure:

1. Log in to the Avamar Data Transport control node as root.

2. From the command line, type the following command:

/etc/init.d/imf-messagebus restart_clean

This command removes all the queues and topics (and any messages they may contain) from the message broker's data store. It essentially puts the message broker into the state it was in just after installation.


Troubleshooting

Springboards do not seem to be added to my workspace

In some cases clicking the Add Springboard to the “My Workspace” icon does not seem to work. If this situation occurs perform the following actions:

1. From the Avamar Data Transport GUI, click Workspaces and then click My Workspace.

2. Click Toolbar, and then ensure that the springboard you want to appear in My Workspace has a check mark by it.

3. Click Toolbar again to close it.

The springboards that you check marked will display on the My Workspace screen.

Troubleshooting problems with the control nodeSome system problems may manifest themselves while working on the Avamar Data Transport control node. The following sections describe some possible conditions that may be encountered on the control node.

Postgres user password does not work

The PostgreSQL install program doesn’t escape the “!” character correctly when it creates the password for the operating system user postgres. (There may also be problems with other shell-specific reserved characters.)

This potential problem is usually resolved in the steps outlined in “Post-Installation configuration” on page 38, where you are instructed to log in as root and set the postgres user password manually.

If you encounter problems on the control node trying to log in as user postgres, log in as the root user on the control node and reset the postgres user password.

Troubleshooting problems with the control node 99

Troubleshooting

Troubleshooting problems with Avamar serversTable 8 Avamar server troubleshooting

Symptom Possible Cause Troubleshooting

Avamar servers do not appear in Avamar Servers springboard in ADT workspace.

GSAN is not running Log in as root on the Avamar server and type the following command:dpnctl status

The output should look something like this:

root@lava4031:~/#: dpnctl statusIdentity added: /home/dpn/.ssh/dpnid (/home/dpn/.ssh/dpnid)dpnctl: INFO: gsan status: readydpnctl: INFO: MCS status: up.dpnctl: INFO: EMS status: up.dpnctl: INFO: Scheduler status: up.dpnctl: INFO: Maintenance operations status: enabled.dpnctl: INFO: Unattended startup status: enabled.

If the GSAN is not running, restart it.

Grid Service is not running.

Log in as root on the Avamar server and type the following command:

service gridservice restart

After the command completes, review the following log file:

/opt/EMC/TransportSystemService/log/jsvcerr.log

At the bottom of the log file, an entry similar to the following confirms that the grid service is running:

24/02/2009 10:46:08 13777 jsvc.exec debug: Daemon loaded successfully

24/02/2009 10:46:08 13777 jsvc.exec debug: Daemon started successfully

If the gridservice daemon did not start successfully, contact EMC technical support.


Troubleshooting

Avamar servers do not appear in Avamar Servers springboard in ADT workspace (continued).

NTP skew is too great. Log in as root on both the Avamar server and the control node. Type the following command on each host:ntpq -p

If the time service is not configured, configure it by using the instructions found in “Synchronize Avamar Data Transport hosts with NTP” on page 35 or by using the asktime utility on the Avamar server. Verify that all hosts in the Avamar Data Transport system use the same time server. If not, synchronize the Avamar server and the control node with the same NTP server.Determine the time difference between the Avamar server and the control node by opening a terminal window to both hosts and typing the following command on each host:watch --interval=1 date

If necessary, manually set the dates so they are within a few seconds of each other.

Network is down between control node and Avamar server

Log in as root on the control node and type the following command:ping SERVERNAME

where SERVERNAME is the Avamar server hostname.If the ping is unsuccessful check that entries for the Avamar server are in the DNS server or in the /etc/hosts file of the control node.Log in as root on the Avamar server and type the following command:ping UTILITYNODE

where UTILITYNODE is the utility node's hostname.If the ping is unsuccessful, check that entries for the control node are in the DNS server or in the /etc/hosts file of the Avamar server.

Table 8 Avamar server troubleshooting


Troubleshooting problems with Avamar servers 101

Troubleshooting

Troubleshooting problems with transport nodesTable 9 Troubleshooting transport nodes


Transport nodes are not displaying in the ADT Server springboard in Avamar Data Transport GUI.

Transport node service is not running.

Log in as root on the Avamar server and type the following command:service nodeservice restart

After the command completes, review the following log: /opt/EMC/TransportSystemService/log/jsvcerr.log

At the bottom of the log, an entry similar to this confirms that the grid service is running:24/02/2009 10:46:08 13777 jsvc.exec debug: Daemon loaded successfully

24/02/2009 10:46:08 13777 jsvc.exec debug: Daemon started successfully

If the gridservice daemon did not start successfully, contact EMC technical support.

NTP skew is too great.

Log in as root on both the Avamar server and the control node. Type the following command on each host:ntpq -p

If the time service is not configured, configure it by using the instructions found in “Synchronize Avamar Data Transport hosts with NTP” on page 35 or by using the asktime utility on the Avamar server. Verify that all hosts in the Avamar Data Transport system use the same time server. If not, synchronize the Avamar server and the control node with the same NTP server.Determine the time difference between the Avamar server and the control node by opening a terminal window to both hosts, and then typing the following command on each host:watch --interval=1 date

If necessary, manually set the dates so they are within a few seconds of each other.

Transport nodes are not displaying in the ADT Server springboard in Avamar Data Transport GUI (continued)

Network down between control node and Avamar Server.

Log in as root on the control node and type the following command:ping SERVERNAME

Where SERVERNAME is the Avamar server hostname.If the ping is unsuccessful, check that entries for the Avamar server are in the DNS server or in the /etc/hosts file of the control node.Log in as root on the Avamar server and type the following command:ping UTILITYNODE

Where UTILITYNODE is the utility node's hostname.If the ping is unsuccessful, check that entries for the control node are in the DNS server or in the /etc/hosts file of the Avamar server.


Troubleshooting

Transport node does not seem to be making progress or is stalled.

The transport node is waiting on itself to start. This condition is sometimes described as the “sleepy node” syndrome.

When transporting data to tape, you can monitor the progress of tasks in the GUI from the ADT Server screen which is displayed by clickingADT > Launch ADT Server ViewerWhen you run a task, typically you will see Task Type change in this way:1. Purging complete

2. Preparing for Replication

3. Replicating

4. Preparing to archive to tape

5. Archiving to Tape

6. Generating archive file catalog data

7. Purging

However, if the GUI reports that “Preparing to archive to tape” task has completed but the process does not proceed to “Generating archive file catalog data,” then you will need to stop the transport node, fail the task that has stalled, and re-issue the transport task.To reset the node and fail the task:1. Log in as root to the transport node.

2. Shut down the transport node service by typing the following command:

service nodeservice stop

3. Edit the following file

/opt/EMC/TransportNodeService/config/AdaNodeDetails.xml

The contents of this XML file look something like this:<NodeConfig>

<com.emc.imf.ada.service.node.AdaNodeDetails> <filename>/opt/EMC/TransportNodeService/config/AdaNodeDetails.xml</filename>

<nodeId>00:50:56:BD:59:59</nodeId> <currentActivity>PREPARE_FOR_BACKUPTOTAPE</currentActivity>

<currentNodeState>COMPLETED</currentNodeState>

<nodeServiceOnline>true</nodeServiceOnline> <bkMgrRententionPolling>3600000</bkMgrRententionPolling>

</com.emc.imf.ada.service.node.AdaNodeDetails>

</NodeConfig>

Transport node does not seem to be making progress or is stalled. (Continued)

Change the content of the currentNodeState element from COMPLETED to FAILED, and save the file.1. Restart the node service by typing the following command:

service nodeservice start

2. In the GUI, click the transport node that was stalled and then click the Unreserve and purge icon.

You can now re-run your transport task.

Table 9 Troubleshooting transport nodes


Troubleshooting problems with transport nodes 103

Troubleshooting

Troubleshooting tape backup server errorsErrors can be reported on the console of the tape backup server that may not generate events in the Avamar Data Transport GUI. The following sections describe possible error conditions that may arise on the tape backup server.

NetWorker Installed in non-standard location

Avamar Data Transport assumes that NetWorker is installed in the default location on the tape backup server. If you have installed NetWorker in a different directory than the default, you will need to enter the location in the 3rdpartybackup.properties file which is located on the transport node at:

opt/EMC/TransportNodeService/config/

The two entries that point Avamar Data Transport to the NetWorker installation on the tape backup server are installation.folder.server and networker.completion.status.file.

For example, if you were to install NetWorker to D:\Legato\nsr instead of the default C:\Legato\nsr, you would change the 3rdpartybackup.properties file as shown below:

### All folder formats are from the top level installation folder, for

example:# UNIX NetWorker: /nsr# UNIX Net Backup: /usr/openv/netbackup## Windows Networker: F:\\Program Files\\Legato\\nsr# Windows Net Backup: F:\\Program

Files\\Veritas\\NetBackup

# the third party backup installation folder on the server hostinstallation.folder.server=D:\\Legato\\nsrnetworker.completion.status.file=D:\\Legato\\nsr\\tmp\\sec\\sg\\{0}\\

Media not available for transporting data

With EMC NetWorker or Symantec NetBackup it is possible to get an error message similar to the following: “unable to allocate new media.” This condition error can be generated from the following conditions:

◆ There is no media available in the tape library’s freepool

◆ The available media is set to a different retention period than the Avamar Data Transport application is requesting.

When any data is written to tape, the entire tape is set to a specified retention period. However, even if there is available space on the tape, NetWorker and NetBackup will only write files to that tape if the specified retention period matches the period the tape was set to when the first files were written to the tape.

If you encounter this error, take either of the following actions:

◆ Add more media to your tape library’s freepool.

◆ Re-run your Avamar Data Transport job specifying a retention level for the job that matches the retention level of the available media in your library.


Troubleshooting

Media not in library for recovery

When recovering data from tape, the tape backup server may report that a required tape is not available. This error can be caused by the following conditions:

◆ The required media has been removed from the tape library◆ The required media was removed from the tape library but was reinserted using a

utility that was not part of the tape backup server product.

If you encounter this error take either of the following actions:

◆ Import the required media back into the tape library.◆ Re-inventory your tape library so the tape backup server can find the required media.

Failure to authenticate with tape backup server

A transport job, or a recover from tape job, may fail because the transport node is unable to authenticate with the tape backup server. This can occur if hosts in the Avamar Data Transport system have been renamed or have been given new IP addresses. This condition may show up in the logs as error messages that say something similar to “failure to authenticate” or “HostKey has been changed.”

If you encounter this error, take the following actions:

1. Log in to the transport node that failed as root and type:

su - admin

2. Edit the /home/admin/.ssh/known_hosts file.

3. Delete the line that refers to the hostname of your tape backup server.

4. Save the file.

5. If the tape backup server is running on Linux, type:

ssh root@TAPEBACKUPSERVER

Or, if the tape backup server is running on Windows, type:

ssh administrator@TAPEBACKUPSERVER

Where TAPEBACKUPSERVER is the name of the tape backup server. The server name format can either be the hostname or it can be the fully qualified domain name. Use the name format that is consistent with how you have set up your systems. For example, if the tape backup server were named magma124 on a domain named test.local, you might type one of the following commands:

ssh root@magma124ssh [email protected] administrator@magma124

6. At the passphrase prompt, press Enter.

7. When prompted, type the root password of the tape backup server.

8. To finish this procedure, type:

exitexit

The tape backup server is now correctly identified as a known host on the transport node.

Troubleshooting tape backup server errors 105

Troubleshooting


APPENDIX AChanging Communication Ports

The following topics describe how to change Avamar Data Transport communication ports.

◆ Avamar Data Transport communication ports ........................................................ 108◆ Changing the SSL port........................................................................................... 108◆ Changing the message bus port ............................................................................ 109◆ Changing the PostgreSQL database port................................................................ 111

Changing Communication Ports 107

Changing Communication Ports

Avamar Data Transport communication portsAvamar Data Transport communicates on the following ports.

The following sections describe how to change some of the default port values.

Changing the SSL portBy default, SSL communicates on port 443. To change the SSL port, perform the following steps:

1. Log in as root to the control node.

2. Assuming you installed Avamar Data Transport to the default location, edit the following file:

/opt/EMC/IMF/apache-tomcat/conf/server.xml

and change the following line:

<Connector port="443" maxHttpHeaderSize="8192"

replacing 443 with the new port number.

3. Save the file.


service imf-server restart

The Avamar Data Transport web server will now respond to the new port number.

Remember that after changing the default SSL port, you will need to append the port number to the URL in the browser. For example, if your control node were magma44, and you change the SSL communication port to be 665, then you would type the following in the your browser:

https://magma44:665

Table 10 Avamar Data Transport communication ports

Port Default Value

Apache Tomcat 8000

Apache Tomcat Secure Socket Layer (SSL) 443

ActiveMQ 1616

ActiveMQ Message Bus 61617

PostgreSQL Database 5558

SSHD 22



Changing the message bus portVarious Avamar Data Transport components communicate with each other on a message bus which uses port 61617 by default.

If you are going to change this value, you will need to change the port number in five different configuration files and restart all the services that use those files. The table below describes the changes that need to be made. The paths to the files that need to be changed are specified relative to the default install location.

To change the message bus port:



/opt/EMC/IMF/apache-tomcat/imf/WEB-INF/classes/messagebus.properties


broker.port=61617


3. Save the file.


/opt/EMC/IMF/apache-activemq/conf/activemq.xml

Table 11 Message bus port configuration file paths and service restart commands

Host File and Path Service to restart

Control Node

messagebus.properties

Path:/opt/EMC/IMF/apache-tomcat/imf/WEB-INF/classes/

service imf-messagebus restart

service imf-server restart


activemq.xml

Path:/opt/EMC/IMF/apache-activemq/conf

SecurityLog.config

Path:/opt/EMC/IMFSecurityLogger/config

Avamar server

AdaGridService.xml

Path:/opt/EMC/TransportSystemService/config


Transport node

AdaNodeService.xml

Path:/opt/EMC/TransportNodeService/config


Changing the message bus port 109



<transportConnector name="ssl" uri="ssl://localhost:61617?transport.socket.needClientAuth=true"/>

replacing 61617 with the new port number

5. Save the file.


/opt/EMC/IMFSecurityLogger/config/SecurityLog.config


<brokerport>61617</brokerport>


7. Save the file.

8. At the command prompt, type the following three commands:

service imf-messagebus restartservice imf-server restartservice securitylogger restart

9. Log out of the control node.

10. Log in to the Avamar server as root.


/opt/EMC/TransportSystemService/config/AdaGridService.xml

Change the following line:



12. Save the file.



14. Log out of the Avamar Server.

15. Repeat steps 10-14 for each Avamar server you are using.

16. Log in to the transport node.


/opt/EMC/TransportNodeService/config/AdaNodeService.xml






18. Save the file.



20. Log out of the transport node.

21. Repeat steps 16-20 for each transport node you are using.

The message bus communication port has now been changed.

Changing the PostgreSQL database portAvamar Data Transport components communicate with the PostgreSQL database on port 5558.

If you are going to change this value, you will need to change the port number in three configuration files and restart all the services that use those files. The table below describes the changes that need to be made. The paths to the files that need to be changed are specified relative to the default install location.

To change the PostgreSQL database port:



/opt/PostgreSQL/8.3/data/postgresql.conf


port=5558


3. Save the file.

Table 12 PostgreSQL database port configuration file locations and service restart commands

Host File and Path Service to restart

Control Node

postgresql.conf

Path:/opt/PostgreSQL/8.3/data/

/etc/init.d/postgresql-8.3 restart

service imf-server restartCatalog.properties

Path:/opt/EMC/IMF/apache-tomcat/imf/WEB-INF/imfcomponents/ADT/resources

Transport Node

Catalog.properties

Path:/opt/EMC/TransportNodeService/config


Changing the PostgreSQL database port 111



/opt/EMC/IMF/apache-tomcat/imf/WEB-INF/imfcomponents/ADT/resources/Catalog.properties


portNumber=5558


5. Save the file.

6. At the command prompt, type the following two commands:

/etc/init.d/postgresql-8.3 restartservice imf-server restart

7. Log out of the control node.

8. Log in to the transport node.


/opt/EMC/TransportNodeService/config/Catalog.properties


portNumber=5558


10. Save the file.



12. Log out of the transport node.

13. Repeat steps 8-12 for each transport node you are using.

The PostgreSQL database port has now been changed.


APPENDIX BUninstalling Avamar Data Transport

Avamar Data Transport components can be uninstalled individually from the various hosts where they were installed. The following topics describe how to uninstall each Avamar component.

◆ Uninstalling the Avamar Data Transport framework................................................ 114◆ Uninstalling the PostgreSQL database................................................................... 114◆ Uninstalling the Avamar Data Transport security logger ......................................... 115◆ Uninstalling the Avamar Server’s transport system service .................................... 115◆ Uninstalling the transport node service ................................................................. 115

Uninstalling Avamar Data Transport 113

Uninstalling Avamar Data Transport

Uninstalling the Avamar Data Transport frameworkTo uninstall the Avamar Data Transport framework:

1. Log in as root on the Avamar Data Transport control node.

2. On the control node console, type:

/opt/EMC/IMF/uninstall

3. Type:

ps -ef |grep Bootstrap

If any processes are running, type:

kill -9 <PID>

where PID is the process ID of any “Bootstrap” processes that are running.

4. Type:

rm -rf /opt/EMC/IMF

5. Type:

rm -f /tmp/bitrock*

The Avamar Data Transport framework has been uninstalled.

Uninstalling the PostgreSQL databaseTo uninstall the PostgreSQL database:



/opt/PostgreSQL/8.3/uninstall-postgresql

3. Type:

rm -rf /opt/Postgre*

4. Type:

rm /etc/postgres-reg.ini

The PostgreSQL database has been uninstalled.



Uninstalling the Avamar Data Transport security loggerTo uninstall the Avamar Data Transport security logger:



/opt/EMC/IMFSecurityLogger/uninstall

3. Type:

rm -rf /opt/EMC/IMFSecurityLogger

4. Type:

rm -f /tmp/bitrock*

The Avamar Data Transport security logger has been uninstalled.

Uninstalling the Avamar Server’s transport system serviceTo uninstall the Avamar Data Transport system service on the Avamar server:

1. Log in as root on the Avamar server.


/opt/EMC/TransportSystemService/uninstall

3. Type:

rm -rf /opt/EMC/TransportSystemService

4. Type:

rm -f /tmp/bitrock*

The Avamar Data Transport system service has been uninstalled.

Uninstalling the transport node serviceTo uninstall the transport node service on the transport node:

1. Log in as root on the transport node.


/opt/EMC/TransportNodeService/uninstall

3. Type:

rm -rf /opt/EMC/TransportNodeService

4. Type:

rm -f /tmp/bitrock*

The transport node service has been uninstalled.

Uninstalling the Avamar Data Transport security logger 115

APPENDIX CCreating SSL Certificates

Avamar Data Transport uses SSL to serve the application to client browsers. Consequently, when accessing Avamar Data Transport for the first time, the user will be notified that the certificate is not valid.

Microsoft and Mozilla browsers allow you to accept the certificate “as valid” and use the Avamar Data Transport application immediately. However, if you want to have Avamar Data Transport serve out a valid certificate, refer to directions on how to configure SSL on http://tomcat.apache.org/.

Creating SSL Certificates 117

http://tomcat.apache.org/

http://tomcat.apache.org/

Creating SSL Certificates


APPENDIX DBacking up PostgresSQL

For every file transported to tape, Avamar Data Transport creates an entry for this file in the PostgreSQL database. This is the database that Avamar Data Transport searches to determine which tapes are needed to recover specific files.

Consequently, it is important to create regular backups of the PostgreSQL database and move these backups to a location outside the Avamar Data Transport system.

The following topics describe how to back up the PostgreSQL database and how to restore it. They assume that the PostgreSQL database was installed on the control node in the default location.

◆ Backing up the database....................................................................................... 120◆ Restoring the database ......................................................................................... 122

Backing up PostgresSQL 119

Backing up PostgresSQL

Backing up the databaseTo back up the PostgreSQL database:

1. Log in as user postgres on the Avamar Data Transport control node.

2. Verify that there is a mount point for /export/backup by typing:

df -h

The output of the this command should show /export/backup is mounted similar to what is shown below in bold:


3. Type:

cd /opt/EMC/ADT/scripts

4. Type:

./adt_pg_backup.sh

5. Type the password for the postgreSQL super user role.

If the script reports “SUCCESS,” the postgreSQL database backed up successfully.

The backup script creates a directory that is named with a time stamp and puts the contents of the postgreSQL database into this directory. It also creates a symbolic link called current that always points to the most recent backup.

For example, a listing of /export/backup might look something like this:

root@lava4119:/export/backup/#: ls -altotal 44drwxr-xr-x 8 postgres postgres 4096 Apr 8 14:32 .drwxr-xr-x 3 root root 4096 Apr 7 10:36 ..drwxrwxr-x 2 postgres postgres 4096 Apr 7 13:57 ADT_04-07-2010_11:37:31drwxrwxr-x 2 postgres postgres 4096 Apr 7 16:36 ADT_04-07-2010_14:18:45drwxrwxr-x 2 postgres postgres 4096 Apr 7 19:19 ADT_04-07-2010_17:04:34drwxrwxr-x 2 postgres postgres 4096 Apr 8 12:39 ADT_04-08-2010_10:39:20drwxrwxr-x 2 postgres postgres 4096 Apr 8 14:32 ADT_04-08-2010_14:32:43lrwxrwxrwx 1 postgres postgres 38 Apr 8 14:32 current ->

/export/backup/ADT_04-08-2010_14:32:43drwx------ 2 root root 16384 Apr 7 10:30 lost+found

By default, the backup script will keep the four most recent backups.



Putting PostgreSQL backup in CRON (optional)

If you would like to create a regular backup of the PostgreSQL database, you can optionally add the catalog backup script to the control node’s crontab file.

To add the adt_pg_backup.sh script to crontab:

1. Log in to the ADT control node as root.

2. Type:

vi /opt/PostgreSQL/8.3/.bashrc

Include the following line in the .bashrc file.

export PG_PASSWORD=/opt/PostgreSQL/8.3/.pgpass

If the file already exists and contains data, put the line at the bottom of the file.

3. Edit the /opt/PostgreSQL/8.3/.pgpass file.

Include the following line in the .pgpass file.

localhost:5558:ada_catalog:postgres:<password>

where password is the PostgreSQL super user password.

4. Type the following:

chmod 600 /opt/PostgreSQL/8.3/.bashrcchown postgres:postgres /opt/PostgreSQL/8.3/.bashrcchmod 600 /opt/PostgreSQL/8.3/.pgpasschown postgres:postgres /opt/PostgreSQL/8.3/.pgpass

5. Type:

crontab -e

Add an entry to run the adt_pg_backup.sh script at the desired time. For example, to run the catalog backup script at 2:00 a.m. on Sunday morning, you would add the following line:

0 2 * * 0 su - postgres -c '/opt/EMC/ADT/scripts/adt_pg_backup.sh >/export/backup/adtPGCatalogBkp.log 2>&1; mv /export/backup/adtPGCatalogBkp.log /export/backup/current/'

The cron process is now configured to run the catalog backup script. Copy catalog backups to a secure location on a regular basis.

Backing up the database 121


Restoring the databaseTo restore the PostgreSQL database:

1. Open a browser window and connect to the ADT GUI.

2. From the ADT workspace, cancel all tasks displaying in the Queued Tasks springboard by clicking the icon on each task.

3. After all tasks have been cancelled, log in to the control node as root.

4. Type:

service imf-server stop

5. Type:

su postgres

6. Type:

cd /opt/EMC/ADT/scripts

7. To restore the most current backup, type:

./adt_pg_restore.sh

If you want to restore an older backup, supply the full path the to directory you want to restore. For example, you might type something like this:

./adt_pg_restore.sh /export/backup/ADT_04-14-2010_16:42:17

8. Type:

y

9. Enter the password for the PostgreSQL super user role.

10. Re-enter the password for the PostgreSQL super user role. If the script reports “SUCCESS,” the postgreSQL database restored successfully.

11. Type:

exit

12. Type:

service imf-server start

You can now use the ADT application with the restored PostgreSQL database.


APPENDIX EThe adtUtil.sh Script

The following topics describe how to use the adtUtil.sh script.

◆ About the adtUtil.sh script .................................................................................... 124◆ ClientArchiveData ................................................................................................. 124◆ TransportClientData .............................................................................................. 127◆ TransportMediaData.............................................................................................. 128◆ TransportMediaExpire ........................................................................................... 129◆ RemoteRestore...................................................................................................... 130

The adtUtil.sh Script 123

The adtUtil.sh Script

About the adtUtil.sh scriptThe adtUtil.sh script generates reports that relate information in the ADT transport catalog with information in the tape backup software database. The script takes the following parameters as input:

◆ “ClientArchiveData” on page 124—this parameter, along with a specified client (and optional date range) will generate an XML report of the transport jobs that contain Avamar backups of the specified client. This report identifies the media volume ids and Avamar backup information for these transport jobs (filtered by the date range if provided).

◆ “TransportClientData” on page 127—this parameter (and optional date range) will generate an XML report of all ADT transport jobs. This report identifies the media volume ids and Avamar backup information for these transport jobs (filtered by the date range if provided).

◆ “TransportMediaData” on page 128—this parameter generates a report of all tape media which the ADT system is using

◆ “TransportMediaExpire” on page 129—this parameter expires specified ADT transport archives on the tape backup server

◆ “RemoteRestore” on page 130—this parameter tells the script to use the output from “adtUtil.sh ClientArchiveData” to populate an ADT system’s transport catalog with information about tape media that has been exported from a remote ADT system.

The adtUtil.sh script is run on an ADT transport node as user Admin.

ClientArchiveData The ClientArchiveData option allows you to pass a client name and an optional date range for that client’s Avamar backups to the adtUtil.sh script. The resulting report allows you to determine the volume IDs of the media that contain the transport jobs for that particular client. The script also provides the media locator ID for the transport job.

The format for this option is:

adtUtil.sh ClientArchiveData <clientName> [ <startDate> <endDate> ]

where

clientName—is the name of Avamar client whose backups you are interested in.

startDate—is the beginning date range specified in the format “yyyy-MM-dd_HH:mm:ss”

endDate—is the ending date range specified in the format “ yyyy-MM-dd_HH:mm:ss”



Example of adtUtil.sh with ClientArchiveData

If you were interested, for example, in Avamar backups for the client lava5112.lab.local, you would take the following steps to find out which transport jobs contain these backups:

1. Log in as user admin on a local ADT transport node.

2. Type:

cd /opt/EMC/TransportNodeService/scripts

3. Type:

./adtUtil.sh ClientArchiveData lava5112.lab.local

admin@lava4103:/opt/EMC/TransportNodeService/scripts/#: ./adtUtil.sh ClientArchiveData lava5112.lab.localStarting ClientArchiveData dump

Xml spooled to [/opt/EMC/TransportNodeService/log/ClienArchiveData2010-02-01_153105.xml]

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><records><record client="lava5112.lab.local" archiveId="19" archiveDate="2010-01-25 15:33:40.0" checksum="0x5ED4F30C20C7189553A738614CDDB2D0" domain="/REPLICATE/lava3099/clients2"> <media_locator>NetBackup:lava5240:lava4103.dev.local:ADT_Remote:1264458771000</media_locator> <volumes> <volume label="804D01" /> </volumes> <backups> <backup label="COD-1264195051374" creation_date="2010-01-22 14:22:36.0" /> <backup label="COD-1264207355890" creation_date="2010-01-22 17:54:22.0" /> <backup label="COD-1264193305260" creation_date="2010-01-22 13:52:23.0" /> </backups></record><record client="lava5112.lab.local" archiveId="20" archiveDate="2010-01-25 21:57:50.0" checksum="0x5C7B5B73A80B67C9EA31F39466E70856" domain="/REPLICATE/lava3099/clients2"> <media_locator>NetBackup:lava5240:lava4103.dev.local:ADT_Remote:1264479596000</media_locator> <volumes> <volume label="804D01" /> <volume label="804D02" /> </volumes> <backups> <backup label="MOD-1248278557091" creation_date="2009-07-22 20:43:41.0" /> <backup label="MOD-1248278577928" creation_date="2009-07-23 02:05:03.0" /> <backup label="MOD-1247266777897" creation_date="2009-07-11 15:49:45.0" /> <backup label="MOD-1247266741865" creation_date="2009-07-11 04:57:44.0" /> <backup label="MOD-1247266788122" creation_date="2009-07-11 10:23:41.0" /> <backup label="MOD-1247597895276" creation_date="2009-07-14 18:20:18.0" /> <backup label="MOD-1247597968299" creation_date="2009-07-14 23:41:48.0" /> <backup label="MOD-1247597944257" creation_date="2009-07-15 05:03:33.0" /> <backup label="MOD-1247597925438" creation_date="2009-07-15 10:25:38.0" /> <backup label="MOD-1248278520562" creation_date="2009-07-22 15:22:55.0" /> </backups></record><record client="lava5112.lab.local" archiveId="21" archiveDate="2010-02-01 13:52:08.0" checksum="0x7107BFA474C61DF7F0E1B4A41D233062" domain="/REPLICATE/lava3099/clients2"> <media_locator>NetBackup:lava5240:lava4103.dev.local:ADT_Remote:1265057483000</media_locator> <volumes> <volume label="804D02" /> </volumes>

ClientArchiveData 125


<backups> <backup label="COD-1265043110040" creation_date="2010-02-01 09:52:53.0" /> <backup label="COD-1265047033162" creation_date="2010-02-01 10:57:41.0" /> </backups></record></records>

The output of the script lists the ADT transport jobs that contain backups for the client lava5112.lab.local. These transport jobs are identified by the XML element “record”.

Each “record” lists the ADT “media_locator” ID for the transport job as well as the “volume labels” of the media that contain the transport job data. In addition, a list of all the included client backups are listed.

The console output will also identify the file where adtUtil.sh has written the XML file.

You can inspect this output to see if the client backups you’re interested in exist in an ADT transport job. You can also limit the output of the script by specifying a date range. For example, if you were interested in lava5112.lab.local backups between July 11, 2009 and July 22, 2009, you could enter the following:

./adtUtil.sh ClientArchiveData lava5112.lab.local 2009-07-11_00:01:00 2009-07-22_23:59:00

admin@lava4103:/opt/EMC/TransportNodeService/scripts/#: ./adtUtil.sh ClientArchiveData lava5112.lab.local 2009-07-11_00:01:00 2009-07-22_23:59:00Starting ClientArchiveData dump

Xml spooled to [/opt/EMC/TransportNodeService/log/ClienArchiveData2010-02-01_162433.xml]

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><records><record client="lava5112.lab.local" archiveId="20" archiveDate="2010-01-25 21:57:50.0" checksum="0x5C7B5B73A80B67C9EA31F39466E70856" domain="/REPLICATE/lava3099/clients2"> <media_locator>NetBackup:lava5240:lava4103.dev.local:ADT_Remote:1264479596000</media_locator> <volumes> <volume label="804D01" /> <volume label="804D02" /> </volumes> <backups> <backup label="MOD-1247266741865" creation_date="2009-07-11 04:57:44.0" /> <backup label="MOD-1247266788122" creation_date="2009-07-11 10:23:41.0" /> <backup label="MOD-1247266777897" creation_date="2009-07-11 15:49:45.0" /> <backup label="MOD-1247597895276" creation_date="2009-07-14 18:20:18.0" /> <backup label="MOD-1247597968299" creation_date="2009-07-14 23:41:48.0" /> <backup label="MOD-1247597944257" creation_date="2009-07-15 05:03:33.0" /> <backup label="MOD-1247597925438" creation_date="2009-07-15 10:25:38.0" /> <backup label="MOD-1248278520562" creation_date="2009-07-22 15:22:55.0" /> <backup label="MOD-1248278557091" creation_date="2009-07-22 20:43:41.0" /> </backups></record></records>



TransportClientDataThe TransportClientData option generates a report of all ADT transport jobs. This report provides information on the volume IDs of the media that the transport jobs are stored on, and the output of this report can be filtered by providing an option date range.

The format for this option is:

adtUtil.sh TransportClientData [ <startDate> <endDate> ]

where

startDate—is the beginning date range specified in the format “yyyy-MM-dd_HH:mm:ss”

endDate—is the ending date range specified in the format “yyyy-MM-dd_HH:mm:ss”

Example of adtUtil.sh with TransportClientData

To generate this report, perform the following steps:

1. Log in as user admin on a local ADT transport node.

2. Type:


3. Type:

./adtUtil.sh TransportClientData

admin@LAVA4104:/opt/EMC/TransportNodeService/scripts/#: ./adtUtil.sh TransportClientDataStarting TransportClientData dump

Xml spooled to [/opt/EMC/TransportNodeService/log/TransportClientData2010-06-01_094341.xml]

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><records> <record archiveId="1" archiveDate="2010-05-25 00:10:41.0" checksum="0xE2F79DFFCA2F783C709D07B5426DB8B2"> <media_locator><keyword type="NetWorker" group="ADA_lava4104" date="1274767695000" client="lava4104.dev.local"> <entry sid="2818271645" fs="/data04" /> <entry sid="2784717213" fs="/data03" /> <entry sid="2851826077" fs="/data06" /> <entry sid="2835048861" fs="/data05" /> <entry sid="2801494429" fs="/data02" /> <entry sid="2767939997" fs="/data01" /> </keyword></media_locator> <no_volumes /> <backups> </backups> </record> <record archiveId="2" archiveDate="2010-05-25 15:30:42.0" checksum="0xFB7182458A90196CBCA56ACC6EA5CF36"> <media_locator><keyword type="NetWorker" group="ADA_lava4104" date="1274822993000" client="lava4104.dev.local"> <entry sid="2667331923" fs="/data04" /> <entry sid="2650554707" fs="/data03" /> <entry sid="2734440787" fs="/data06" /> <entry sid="2717663571" fs="/data05" /> <entry sid="2684109139" fs="/data02" /> <entry sid="2700886355" fs="/data01" /> </keyword></media_locator> <volumes> <volume label="000024" /> </volumes>

TransportClientData 127


<backups> <backup domain="/REPLICATE/lava3099/Domain1" client="lava4157.dev.local" label="COD-1238951488609" creation_date="2009-04-05 11:31:25.0" /> </backups> </record> <record archiveId="3" archiveDate="2010-05-27 13:25:50.0" checksum="0xCD047963B9ED0758CF4B2D2AF94AAECC"> <media_locator><keyword type="NetWorker" group="ADA_lava4104" date="1274988263000" client="lava4104.dev.local"> <entry sid="2566833975" fs="/data04" /> <entry sid="2550056759" fs="/data03" /> <entry sid="2617165623" fs="/data06" /> <entry sid="2600388407" fs="/data05" /> <entry sid="2583611191" fs="/data02" /> <entry sid="2533279543" fs="/data01" /> </keyword></media_locator> <volumes> <volume label="000024" /> </volumes> <backups> <backup domain="/REPLICATE/lava3099/clients2" client="lava5112.lab.local" label="COD-1274985790600" creation_date="2010-05-27 12:43:17.0" /> </backups> </record></records>

The output of the script lists the ADT transport jobs. These transport jobs are identified by the archiveID element within the “record” tags.

Each “record” lists the ADT “media_locator” ID for the transport job as well as the “volume labels” of the media that contain the transport job data. In addition, a list of all the included client backups are listed.

The console output will also identify the file where adtUtil.sh has written the XML file.

You can limit the output of the script by specifying a date range. For example, if you were interested in transport jobs between July 11, 2009 and July 22, 2009, you could enter the following:

./adtUtil.sh TransportClientData 2009-07-11_00:01:00 2009-07-22_23:59:00

admin@lava4103:/opt/EMC/TransportNodeService/scripts/#: ./adtUtil.sh TransportClientData 2009-07-11_00:01:00 2009-07-22_23:59:00Starting ClientArchiveData dump

TransportMediaDataThe TransportMediaData script generates a report of all tape media which the ADT system is using. The script is run on the command line of an ADT transport node using the following command:

./adtUtil.sh TransportMediaData

Output from the script looks something like this:

admin@LAVA4104:/opt/EMC/TransportNodeService/scripts/#: ./adtUtil.sh TransportMediaDataStarting TransportMediaData Util

Xml spooled to [/opt/EMC/TransportNodeService/log/TransportMediaData2010-06-01_101025.xml]

<?xml version="1.0" encoding="UTF-8" standalone="yes"?><records> <volume value="000001" \> <volume value="000024" \>

</records>



TransportMediaExpireThe TransportMediaExpire option expires a save set on the tape backup server for a specified ADT transport job. The transport job you want to delete is identified by its media locator.

Example of adtUtil.sh with TransportMediaExpire

Output from the script may identify a transport job as follows:

<record archiveId="3" archiveDate="2010-05-27 13:25:50.0" checksum="0xCD047963B9ED0758CF4B2D2AF94AAECC"> <media_locator>

<keyword type="NetWorker" group="ADA_lava4104" date="1274988263000" client="lava4104.dev.local">

<entry sid="2566833975" fs="/data04" /> <entry sid="2550056759" fs="/data03" /> <entry sid="2617165623" fs="/data06" /> <entry sid="2600388407" fs="/data05" /> <entry sid="2583611191" fs="/data02" /> <entry sid="2533279543" fs="/data01" /> </keyword> </media_locator> <volumes> <volume label="000024" /> </volumes> <backups> <backup domain="/REPLICATE/lava3099/clients2" client="lava5112.lab.local"

label="COD-1274985790600" creation_date="2010-05-27 12:43:17.0" /> </backups></record>

Using the data contain between the media_locator tags, you can create a file that can be used as input to the adtutil.sh TransportClientData script. Using the example above, for example, you could create a file called expiremedialocator that looks something like this:

<keyword type="NetWorker" group="ADA_lava4104" date="1274988263000" client="lava4104.dev.local">

<entry sid="2566833975" fs="/data04" /> <entry sid="2550056759" fs="/data03" /> <entry sid="2617165623" fs="/data06" /> <entry sid="2600388407" fs="/data05" /> <entry sid="2583611191" fs="/data02" /> <entry sid="2533279543" fs="/data01" /></keyword>

Then you would enter the following command on the command line of the ADT transport node:

./adtUtil.sh TransportMediaExpire expiremedialocator

TransportMediaExpire 129


RemoteRestoreThe RemoteRestore option allows you to import information about tape media that was exported from a remote ADT system. This allows you to recover client backups from the media and transport jobs of the remote ADT system.

This command is run after the media from the remote ADT system has been successfully imported into the local tape library using Networker or NetBackup. (As necessary, the library should be re-inventoried as well.

This command also assumes that, before the media at the remote ADT site was exported, the adtUtil.sh script was run to identify all the media that contains data from the desired ADT archives (e.g. the output from the adtUtil.sh ClientArchiveData command).

Example of adtUtil.sh with RemoteRestore

The following is an example of how a transport job containing the client backups from a remote ADT system can be restored to a local ADT node using:

1. Import the media into the remote library. This process should include updating the tape backup software applications with information about the media (e.g. using the bpimport command with NetBackup).

2. Log in to the local ADT transport node as user admin.

3. Type:


4. Create a file named MediaLocator.txt and paste all the media locators for the ADT archives in the file. For example, a line of the file may look something like this:

NetBackup:lava5240:lava4103.dev.local:ADT_Remote:1264479596000

5. Using the newly created file as input, type the following command:

adtUtil.sh RemoteRestore MediaLocator.txt

After the script finishes, the transport job created at the local site will now be available on the remote ADT node. You can access the information on the ADT node as you would an Avamar AVE or an Avamar server.


APPENDIX FConfiguring ADT for Media Groups

In early versions of ADT, transport nodes were configured as clients of EMC NetWorker or Symantec NetBackup. In NetWorker, each transport node was associated in a one-to-one relationship with a group that moved data to media assigned to that group. In NetBackup, all transport nodes were added (in a many-to-one relationship) to a single policy that moved data to media assigned to that policy.

However, starting with ADT 1.0 SP3, an ADT transport node can now move data to multiple NetWorker groups (where each group may be assigned a separate media pool). Similarly, ADT transport nodes can also move data to multiple NetBackup policies (where each policy may be assigned a separate media pool).

In the ADT GUI, a new field has been added to the ADT Transport Settings that allows ADT to move data to a specified “Media Group,” which is defined as either a NetWorker group or a NetBackup policy.

The following topics describe how to configure additional NetWorker groups or NetBackup policies so that ADT transport nodes can direct data to multiple media pool destinations.

◆ Configuring NetWorker for media groups ............................................................... 132◆ Configuring NetBackup for media groups............................................................... 140

Configuring ADT for Media Groups 131

Configuring ADT for Media Groups

Configuring NetWorker for media groupsThe following instructions describe how to create a pool and assign it to a new group which can then be used as a “Media Group” in ADT.

These instructions assume that the NetWorker server has been installed and is properly configured to back up to and restore from tape. It also assumes the NetWorker Management Console has been installed on a client that can connect with the NetWorker server.

To configure media groups for NetWorker:

1. Log in to the ADT GUI.

2. From the ADT Server springboard, click Launch ADT Server Viewer.

The ADT Server window appears with a list of all transport nodes.

3. Ensure that there is no activity on any of the transport nodes.

To ensure this, you may need to cancel tasks in the Queued Tasks springboard.

4. From the ADT Server window, click an idle transport node and click Toggle Online/Offline.

5. Repeat step 4 until all the transport nodes are off line.

6. Using an ssh client, log in to a transport node as root.



8. Repeat steps 6-7 until the nodeservice on all transport nodes has been shut down.

9. Log in to the NetWorker Management Console as a user who has rights to configure the server.









15. In the tree panel on the left of the NetWorker Administration screen, right-click Groups, and then click New.

Configuring NetWorker for media groups 133


16. In the Name field, type the name for the group.

17. On the Advanced tab, select full from the Level list and clear the Force incremental checkbox.

If you do not clear Force incremental, it is possible to lose access to the data that is written to tape permanently.



18. Click OK.

19. Repeat steps 15-18 until you have created all the ADT groups that you plan to use.

20. At the top of the NetWorker Administration window, click the Media icon.

21. In the tree panel on the left of the NetWorker Administration screen, right-click Media Pools, and then click New.

22. In the Name field, type the name you want for the media pool.

23. In the Groups field, click the group you created in steps 15-18.

24. From the Label template drop-down list, choose Default.



25. On the Configuration tab, select the Retention policy for the media pool.

26. Click OK.

27. Repeat steps 21-26 until you have created media pools for each of the ADT groups you created in steps 15-19.


29. In the tree panel on the left of the NetWorker Administration screen, right-click Clients, and then click New.



30. In the Name field, type the name of the transport node you want to back up.

This name should resolve through DNS or entries in the /etc/hosts file to the IP address of the transport node.

31. In the Browse policy field, select Day.

32. Ensure that the Scheduled backup option is selected.

33. In the Group field, click the checkbox by the all the ADT groups that you created in steps 15-19.

34. In the Save set field, type the first data mount point.

For full TB transport nodes, there are typically six mount points: /data01, /data02, /data03, /data04, /data05, and /data06.

For 2 TB transport nodes, there are typically twelve mount points: /data01, /data02, /data03, /data04, /data05, /data06, /data07, /data08, /data09, /data10, /data11, /data12.

You can also set Index Policy Retention on this page. However, be aware that tape-level retention is determined by the following precedence: • Pool Retention Policy • Overrides to Index Policy Retention (such as those coming from the Avamar Data Transport application) • Index Policy Retention (which is set on this screen)

For example, if you were to set the Index Policy Retention on this screen to one year, then any Avamar Data Transport overrides would take precedence as would any Pool Retention Policies set on media pools assigned to this client.

35. Click the Globals (2 of 2) tab.



36. In the Remote access text box, type:

*@*

This will allow data backed up from any transport node to be recovered to this transport node.

37. Click OK.

38. Repeat steps 29–37 for each transport node that you want to back up to tape.

39. Close the NetWorker Management Console.


41. Edit the following file:

/opt/EMC/TransportNodeService/config/3rdpartybackup.properties

42. If the following two lines do not exist at the bottom of file, add them:

# The default group/policy to use when no media group is provided.# default.media.group=

43. Uncomment the “# default.media.group=” line and type the default group name on that line.

For example, after you are finished the bottom of the file might look something like this:

# The default group/policy to use when no media group is provided.default.media.group=Customer1

If a user changes the Tape Backup Manager Retention value in the ADT GUI, it will change the retention for the group. Consequently, do not set as the default.media.group any group whose retention you need to stay unchanged.



44. Start the transport node service by typing the following command:


45. Repeat steps 40-44 until the nodeservice on all transport nodes has been started.





49. Repeat step 48 until all the transport nodes are on line.

NetWorker is now configured to use media groups with ADT. When creating or editing transport groups in the ADT GUI, provide the name of the NetWorker group that uses your media pools as the Media Group.



Configuring NetBackup for media groupsThe following instructions describe how to create a media volume pool and assign it to a new policy which can then be used as a “Media Group” in ADT.

These instructions assume that the NetBackup server has been installed and is properly configured to back up to and restore from tape. It also assumes that the NetBackup Administration console has been installed.

To configure media groups for NetBackup:




3. Ensure that there is no activity on any of the transport nodes.

To ensure this, you may need to cancel tasks in the Queued Tasks springboard.


5. Repeat step 4 until all the transport nodes are off line.




8. Repeat steps 6-7 until the nodeservice on all transport nodes has been shut down.

9. Start the NetBackup console by typing the following command:



10. Log in to the NetBackup Administration Console as a user who has privileges to configure NetBackup installation.

11. In the far left-hand pane, expand Media and Device Management, Media, and then Volume Pools.



12. Begin creating a new volume pool by right-clicking Volume Pools and selecting New Volume Pool.

13. In the Add a New Volume Pool dialog type a Pool name and optionally provide a description.

For example, you might type something like “Customer1_VolumePool.”

14. Click OK.

15. In the far left-hand pane, expand Volume Groups and then click the volume group that contains the media you want to assign to your newly created volume pool.

16. In the right-hand pane, select the media you want to assign to the volume pool, right-click your selection, and click Change.

Configuring NetBackup for media groups 141


17. In the Change Volumes dialog, click the New Pool radio button and from the drop down list choose the volume pool created in steps 12-14.

18. Click OK.

19. Begin creating a new policy by expanding NetBackup Management and clicking Policies.



20. In the All Policies pane, right-click a blank area of the pane, and then select New Policy.

21. Type a policy name in the Add a new Policy dialog box.

For example, you might type something like “Customer1_Policy_1TBADTTransportNode” as the policy name.

22. Click OK.

23. On the Attributes tab of the Change Policy dialog box, choose the Policy volume from the drop down menu.

This is the volume pool you created in steps 12-14.



24. Set whatever other attributes your environment requires.

Ensure that the “Cross mount points,” “Take checkpoint,” and “Bare Metal Restore” check boxes are not selected.

25. On the Schedules tab, click New.

26. In the Name field of the Attributes tab of the Add Schedule dialog box, type a name for the schedule.

27. Ensure that Type of Backup is set to Full Backup.

If, on the Add Schedule dialog box, you change Type of backup to any selection other than Full Backup, you may lose access to data that is written to tape permanently.

28. Click OK.

29. On the Clients tab, click New.

30. In the Client Name field, type the hostname of a transport node you want to back up.

The client name should be resolvable through DNS or through the /etc/hosts file on the tape backup server. In addition, the client name should be consistent with the hostname format used during the initial install. For example, if the hostname format that was used on all hosts during system install was fully qualified hostnames, then you would enter a hostname that looked something like this: myNBclient.corp.



31. From the Hardware and operating system list, select Linux, Redhat2.6, and then click Add.

When adding policies you can optionally set retention periods from the Schedules tab. Retention policies set in the Avamar Data Transport application override these values.

32. Repeat steps 29-31 until all the transport nodes have been added.

33. Click Close.

34. On the Backup Selections tab of the Change Policy dialog box, click New.

35. In the Add Backup Selection dialog box, type the first data mount point in the Pathname or directive field.

36. Click Add.

For full TB transport nodes, there are typically six mount points: /data01, /data02, /data03, /data04, /data05, and /data06.

For 2 TB transport nodes, there are typically twelve mount points: /data01,/data02, /data03, /data04, /data05, /data06, /data07, /data08, /data09, /data10, /data11, /data12.



37. Repeat steps 35-36 until the six (or twelve) mount points have been added.

38. Click OK, and then click Close.

39. Verify that the NetBackup clients are on the transport nodes by expanding Host Properties (under NetBackup Management) and clicking on Clients.

In the right-hand pane you should see your transport nodes listed and “Connected” should be displayed in the Status column.

40. Close the NetBackup Administration Console, by selecting File > Exit from the main menu.


42. Edit the following file:

/opt/EMC/TransportNodeService/config/3rdpartybackup.properties

43. If the following two lines do not exist at the bottom of file, add them:

# The default group/policy to use when no media group is provided.# default.media.group=

44. Uncomment the “# default.media.group=” line and type the default policy name on that line.

For example, after you are finished the bottom of the file might look something like this:

# The default group/policy to use when no media group is provided.default.media.group=Customer1_Policy_1TBADTTransportNode



If a user changes the Tape Backup Manager Retention value in the ADT GUI, it will change the retention for the policy. Consequently, do not set as the default.media.group any policy whose retention you need to stay unchanged.

45. Start the transport node service by typing the following command:


46. Repeat steps 41-45 until the nodeservice on all transport nodes has been started.





50. Repeat step 49 until all the transport nodes are on line.

NetBackup is now configured to use tape pools or volume pools with ADT. When creating or editing transport groups in the ADT GUI, provide the name of the NetBackup policy that uses your tape pool as the Media Group.


INDEX

Numerics3rdpartybackup.properties 84, 85, 138, 146

AAvamar Server

plug-in versions 55

CCatalog.properties 40, 88

Ddefault.media.group 146

EEMC Networker

retention overrides 70, 137

HHardware Requirements

ESX server 17transport node 24

Iidentity.properties 87Installation

ESX server requirements 24information required 22order of install 26

LLogs

location of 94

SSecurity

encrypted communication 40, 88location of log file 43updating lockbox password 56

Servicesnames of 94

Software Requirementstape backup server 18web browsers 44

TTape Backup Server

changing password 87changing user 87

Time Synchronization 24

Transport Nodesplug-in versions 60

Troubleshootingrecovering from "sleepy node" 103restarting the transport node 102resting the message bus 98synchronizing time 102

VVeritas NetBackup

retention overrides 77, 145

Index 149

Index


emc avamar data transport® avamar data transport 1.0 sp3 installation guide and reference manual...

Documents