Download - Symantec NetBackup for NDMPAdministrator'sGuide 3 Configuring NDMP backup to NDMP-attached devices 39 About configuring NDMP-attached devices 39 Authorizing access to the NDMP host

Symantec NetBackup™ forNDMP Administrator's Guide

UNIX, Windows, and Linux

Release 7.0.1

Symantec NetBackup™ for NDMP Administrator's GuideThe software described in this book is furnished under a license agreement and may be usedonly in accordance with the terms of the agreement.

Documentation version: 7.0.1

Legal NoticeCopyright © 2010 Symantec Corporation. All rights reserved.

Symantec, the Symantec Logo, and NetBackup are trademarks or registered trademarks ofSymantec Corporation or its affiliates in the U.S. and other countries. Other names may betrademarks of their respective owners.

Portions of this software are derived from the RSA Data Security, Inc. MD5 Message-DigestAlgorithm. Copyright 1991-92, RSA Data Security, Inc. Created 1991. All rights reserved.

This Symantec product may contain third party software for which Symantec is requiredto provide attribution to the third party (“Third Party Programs”). Some of the Third PartyPrograms are available under open source or free software licenses. The License Agreementaccompanying the Software does not alter any rights or obligations you may have underthose open source or free software licenses. Please see the Third Party Legal Notice Appendixto this Documentation or TPIP ReadMe File accompanying this Symantec product for moreinformation on the Third Party Programs.

The product described in this document is distributed under licenses restricting its use,copying, distribution, and decompilation/reverse engineering. No part of this documentmay be reproduced in any form by any means without prior written authorization ofSymantec Corporation and its licensors, if any.

THE DOCUMENTATION IS PROVIDED "AS IS" AND ALL EXPRESS OR IMPLIED CONDITIONS,REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE OR NON-INFRINGEMENT,ARE DISCLAIMED, EXCEPT TO THE EXTENT THAT SUCH DISCLAIMERS ARE HELD TOBE LEGALLY INVALID. SYMANTEC CORPORATION SHALL NOT BE LIABLE FOR INCIDENTALOR CONSEQUENTIAL DAMAGES IN CONNECTION WITH THE FURNISHING,PERFORMANCE, OR USE OF THIS DOCUMENTATION. THE INFORMATION CONTAINEDIN THIS DOCUMENTATION IS SUBJECT TO CHANGE WITHOUT NOTICE.

The Licensed Software and Documentation are deemed to be commercial computer softwareas defined in FAR 12.212 and subject to restricted rights as defined in FAR Section 52.227-19"Commercial Computer Software - Restricted Rights" and DFARS 227.7202, "Rights inCommercial Computer Software or Commercial Computer Software Documentation", asapplicable, and any successor regulations. Any use, modification, reproduction release,performance, display or disclosure of the Licensed Software and Documentation by the U.S.Government shall be solely in accordance with the terms of this Agreement.

Symantec Corporation350 Ellis StreetMountain View, CA 94043

http://www.symantec.com

http://www.symantec.com

Technical SupportSymantec Technical Support maintains support centers globally. TechnicalSupport’s primary role is to respond to specific queries about product featuresand functionality. The Technical Support group also creates content for our onlineKnowledge Base. The Technical Support group works collaboratively with theother functional areas within Symantec to answer your questions in a timelyfashion. For example, the Technical Support group works with Product Engineeringand Symantec Security Response to provide alerting services and virus definitionupdates.

Symantec’s support offerings include the following:

■ A range of support options that give you the flexibility to select the rightamount of service for any size organization

■ Telephone and/or web-based support that provides rapid response andup-to-the-minute information

■ Upgrade assurance that delivers automatic software upgrades protection

■ Global support purchased on a regional business hours or 24 hours a day, 7days a week basis

■ Premium service offerings that include Account Management Services

For information about Symantec’s support offerings, you can visit our web siteat the following URL:

www.symantec.com/business/support/

All support services will be delivered in accordance with your support agreementand the then-current enterprise technical support policy.

Contacting Technical SupportCustomers with a current support agreement may access Technical Supportinformation at the following URL:


Before contacting Technical Support, make sure you have satisfied the systemrequirements that are listed in your product documentation. Also, you should beat the computer on which the problem occurred, in case it is necessary to replicatethe problem.

When you contact Technical Support, please have the following informationavailable:

■ Product release level



■ Hardware information

■ Available memory, disk space, and NIC information

■ Operating system

■ Version and patch level

■ Network topology

■ Router, gateway, and IP address information

■ Problem description:

■ Error messages and log files

■ Troubleshooting that was performed before contacting Symantec

■ Recent software configuration changes and network changes

Licensing and registrationIf your Symantec product requires registration or a license key, access our technicalsupport web page at the following URL:


Customer serviceCustomer service information is available at the following URL:


Customer Service is available to assist with non-technical questions, such as thefollowing types of issues:

■ Questions regarding product licensing or serialization

■ Product registration updates, such as address or name changes

■ General product information (features, language availability, local dealers)

■ Latest information about product updates and upgrades

■ Information about upgrade assurance and support contracts

■ Information about the Symantec Buying Programs

■ Advice about Symantec's technical support options

■ Nontechnical presales questions

■ Issues that are related to CD-ROMs or manuals



Support agreement resourcesIf you want to contact Symantec regarding an existing support agreement, pleasecontact the support agreement administration team for your region as follows:

[email protected] and Japan

[email protected], Middle-East, and Africa

[email protected] America and Latin America

Additional enterprise servicesSymantec offers a comprehensive set of services that allow you to maximize yourinvestment in Symantec products and to develop your knowledge, expertise, andglobal insight, which enable you to manage your business risks proactively.

Enterprise services that are available include the following:

Managed Services remove the burden of managing and monitoring securitydevices and events, ensuring rapid response to real threats.

Managed Services

Symantec Consulting Services provide on-site technical expertise fromSymantec and its trusted partners. Symantec Consulting Services offer a varietyof prepackaged and customizable options that include assessment, design,implementation, monitoring, and management capabilities. Each is focused onestablishing and maintaining the integrity and availability of your IT resources.

Consulting Services

Education Services provide a full array of technical training, security education,security certification, and awareness communication programs.

Education Services

To access more information about enterprise services, please visit our web siteat the following URL:

www.symantec.com/business/services/

Select your country or language from the site index.

mailto:[email protected]



www.symantec.com/business/services/

Technical Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4

Chapter 1 Introduction to NetBackup for NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

About NetBackup for NDMP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12NetBackup for NDMP features ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12NetBackup for NDMP terminology .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Network data management protocol (NDMP) .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Types of NDMP backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

NDMP local backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17NDMP three-way backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Backup to Media Manager storage units (remote NDMP) .... . . . . . . . . . . . . 19

NDMP policies ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Storage units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

NDMP Storage units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Media Manager storage units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Assigning tape drives to different hosts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

NDMP backup process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24NDMP restore process ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Direct access recovery (DAR) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27NDMP direct copy with VTL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

NDMP direct copy without VTL .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30NDMP direct copy: notes and limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

NDMP information on the Web .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Snapshot Client Assistance .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32NDMP multiplexing .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

About NDMP multiplexing general considerations .... . . . . . . . . . . . . . . . . . . . 33

Chapter 2 Installing NetBackup for NDMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Installation prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Installing on UNIX servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36Installing on Windows servers ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Uninstalling NetBackup for NDMP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Contents

Chapter 3 Configuring NDMP backup to NDMP-attacheddevices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

About configuring NDMP-attached devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Authorizing access to the NDMP host ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Access for three-way backups and remote NDMP .... . . . . . . . . . . . . . . . . . . . . . 41Media and Device Management configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Adding a robot directly attached to an NDMP host ... . . . . . . . . . . . . . . . . . . . . 42Adding a drive ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Checking the device configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46About adding volumes .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Verifying NDMP password and robot connection .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Adding NDMP storage units ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47About creating an NDMP policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Attributes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Clients ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Files (Backup Selections) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Schedules ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

About enabling or disabling DAR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Disabling DAR for file and directory restores ... . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Disabling DAR for directory restores only ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

Setting up clustering .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Post-installation changes ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Testing an NDMP configuration .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 4 Configuring NDMP backup to NetBackup mediaservers (remote NDMP) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55

About remote NDMP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Configuring NDMP backup to Media Manager storage units ... . . . . . . . . . . . . . . 56

Chapter 5 Configuring NDMP direct copy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

About NDMP direct copy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Notes and limitations .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Prerequisites ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

How to configure NDMP direct copy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Using NDMP direct copy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Requirements ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Initiate NDMP direct copy with the Administration Console ... . . . . . . . . 62

Contents8

Chapter 6 Remote NDMP and disk devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

About remote NDMP and disk devices ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Configuring remote NDMP .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Chapter 7 Using the Shared Storage Option (SSO) . . . . . . . . . . . . . . . . . . . . . . . . . 67

About the Shared Storage Option (SSO) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Setting up SSO: overview .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68Using the Device Configuration Wizard .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Chapter 8 Backup and restore procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

About NDMP backup .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Automatic backup of an NDMP policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Performing a manual backup of an NDMP policy ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Performing a restore from the server ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Chapter 9 Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Sources of information .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77NDMP operating notes and restrictions ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Notes on DAR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Types of logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Using logs ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Troubleshooting suggestions .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

NDMP backup levels ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Troubleshooting media and devices on Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Troubleshooting media and devices on UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Troubleshooting NDMP direct copy .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Troubleshooting DAR .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Testing a robot ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

TL8 example for Windows .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85TLD example for UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86TLH example for UNIX .... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86

Chapter 10 Using scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

About scripts ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89ndmp_start_notify (UNIX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90ndmp_start_notify.cmd (Microsoft Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92ndmp_end_notify (UNIX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94ndmp_end_notify.cmd (Microsoft Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96ndmp_start_path_notify (UNIX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98ndmp_start_path_notify.cmd (Microsoft Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . 101

9Contents

ndmp_end_path_notify (UNIX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103ndmp_end_path_notify.cmd (Microsoft Windows) ... . . . . . . . . . . . . . . . . . . . . . . . . . 105ndmp_moving_path_notify (UNIX) ... . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107ndmp_moving_path_notify.cmd (Microsoft Windows) ... . . . . . . . . . . . . . . . . . . . . 109

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Contents10

Introduction to NetBackupfor NDMP

This chapter includes the following topics:

■ About NetBackup for NDMP

■ NetBackup for NDMP features

■ NetBackup for NDMP terminology

■ Network data management protocol (NDMP)

■ Types of NDMP backup

■ NDMP policies

■ Storage units

■ NDMP backup process

■ NDMP restore process

■ Direct access recovery (DAR)

■ NDMP direct copy with VTL

■ NDMP information on the Web

■ Snapshot Client Assistance

■ NDMP multiplexing

1Chapter

About NetBackup for NDMPNetBackup for NDMP is an optional NetBackup application. It enables NetBackupto use the Network Data Management Protocol (NDMP) to initiate and controlbackups and restores of Network Attached Storage (NAS) systems.

NetBackup for NDMP featuresNetBackup for NDMP includes the following features:

■ Support for NDMP protocol versions V2, V3, and V4.

■ Centralized backup-policy managementScheduling, catalog management, and other backup tasks are managed froma NetBackup master server. NetBackup for NDMP can be installed on aNetBackup master or media server.

■ Device and media managementNetBackup software provides complete management and control of the devicesand media that are used for backups and restores of NDMP hosts. TheNetBackup Device Configuration wizard discovers and configures the storagedevices that are attached to an NDMP host (requires NDMP protocol versionsV3 or V4). Note that wizard-based discovery depends upon a number ofdevice-specific features, such as SCSI inquiry and serialization, which someNAS vendors may not support.

■ High speed local backup of NDMP hostsBackup data travels between the disk and tape drives that are directly attachedto the same NDMP host. This transfer provides high-speed backup withoutimpairing network throughput.

■ Backup of network-attached NDMP hosts to a tape device on another NDMPhost or to advanced tape libraries with an embedded NDMP server.Backup data travels across the network, from a disk on an NDMP host to tapeon another NDMP host. This backup is referred to as three-way backup. Thisdata movement option requires support from the NAS/NDMP host.

■ Backup of a network-attached NDMP host to a tape device on a NetBackupmedia server. This backup is a form of three-way backup also known as remoteNDMP. This feature supports NDMP versions V2, V3, and V4 on the NDMPhosts.

■ Shared tape librariesTape libraries can be shared between NDMP hosts and NetBackup servers, orbetween multiple NDMP hosts. Robotic control can be on an NDMP host or ona NetBackup server.

Introduction to NetBackup for NDMPAbout NetBackup for NDMP

12

■ Shared tape drives with the Shared Storage OptionTape drives can be shared between servers (both NetBackup servers and NDMPhosts). This setup requires the Shared Storage Option (SSO) license.See “NDMP information on the Web” on page 32.

■ Snapshots of data on NDMP hostsNetBackup can make point-in-time data snapshots on an NDMP (NAS) hostwithout interrupting client access to data, using the NDMP V4 snapshotextension. The snapshot is stored on the same device that contains the NDMPclient data. From the snapshot, you can restore individual files or roll back afile system or volume by means of Snapshot Client Instant Recovery. ANetBackup Snapshot Client license is required, in addition to the NetBackupfor NDMP license. This Snapshot Client feature uses the NAS_Snapshot method.Refer to the NetBackup Snapshot Client Administrator’s Guide for details.

■ NDMP direct copyNetBackup can copy virtual tape library (VTL) images directly from the VTLto physical tape or to another VTL, without using media server I/O resourcesor network bandwidth. NetBackup can directly copy NDMP backup imagesfrom one NDMP-attached tape drive to another NDMP tape drive that isattached to the same NDMP host. Note that the operation does not use mediaserver I/O.

Note: The VTL must have an embedded NDMP tape server.

■ NetBackup can also create a SnapVault disk copy from a NAS snapshot.Configuration details are contained in the NetBackup Snapshot ClientAdministrator’s Guide.For a list of NAS vendors that NetBackup currently supports for SnapVaultand NAS_Snapshot, refer to the Symantec NetBackup Snapshot ClientConfiguration online document. Information on how to access that documentis available.See “Snapshot Client Assistance” on page 32.

■ Direct Access Recovery (DAR)For NDMP hosts that support DAR, this feature greatly reduces the time thatis needed to restore a directory, a single file, or a small number of files.

■ Path-based file historyThe NDMP server can send catalog information consisting of complete pathnames to NetBackup. Some vendors do not support this feature. Up-to-dateinformation is available on the vendors that support path-based history.See “NDMP information on the Web” on page 32.

13Introduction to NetBackup for NDMPNetBackup for NDMP features

■ NetBackup for NDMP servers are supported in a NetBackup-clusteredenvironment.

■ The enhanced ability to run customized scripts during a backup, especiallyfor relational databases residing on NAS devices.

■ NDMP multiplexingNDMP multiplexing enables NDMP backups to be multiplexed to Media ManagerStorage Units. Only remote NDMP multiplexing is supported.

■ NDMP to diskNetBackup can write NDMP backups to disk storage units.

NetBackup for NDMP terminologyTable 1-1 describes NetBackup for NDMP terminology. For explanations of otherNetBackup terms, consult the NetBackup online glossary in NetBackup help.

Table 1-1 Terminology

DefinitionTerm

The NDMP host positions the tape to the exact location ofthe requested file(s), reading only the data that is neededfor those files. Restore times can be reduced from hours tominutes.

DAR (Direct AccessRecovery)

NDMP is a widely used protocol through which anNDMP-conformant backup application can control thebackups and restores for an NDMP host.

NDMP (Network DataManagement Protocol)

A form of three-way backup and restore also known asRemote NDMP. Data travels from an NDMP host to a tapedrive that is attached to a NetBackup media server.

NDMP backup to MediaManager storage units

An NDMP client is an NDMP-compliant backup application(also known as a Data Management Application or DMA)that is an NDMP server application client. An NDMP clientsends commands to the NDMP server application to controlthe backups and restores on an NDMP host.

NetBackup for NDMP allows NetBackup to act as an NDMPclient.

NDMP client

A NetBackup for NDMP server is a NetBackup master ormedia server on which NetBackup for NDMP software isinstalled.

NetBackup for NDMP server

Introduction to NetBackup for NDMPNetBackup for NDMP terminology

14

Table 1-1 Terminology (continued)

DefinitionTerm

A NAS system that serves files to clients using HTTP, FTP,CIFS, or NFS protocols. It also runs an NDMP serverapplication that communicates with NDMP client backupsoftware to configure and perform backup and restore tasks.NAS systems provide fast, multi-protocol file access andcost effective data storage to workstations and servers inthe network or across the Internet.

In a NetBackup configuration, the NDMP host is considereda client of NetBackup. However, NetBackup client softwareis never installed on an NDMP host.

NDMP host

NDMP multiplexing concurrently writes multiple backupstreams to the same Media Manager tape storage devicefrom the same client or different clients. NDMP multiplexingimproves overall NetBackup performance by more efficientuse of the Storage Unit drives. State of the art storagedevices can typically stream data faster than client agentscan create backup streams. Therefore multiple data streamscan be sent to and effectively processed by a given storageunit. Remote NDMP multiplexing only is supported.

NDMP multiplexing

An NDMP server application runs on an NDMP host andruns backup, restore, and device control commands that itreceives from an NDMP-conformant backup application.The backup application (NetBackup) is considered an NDMPclient. A separate instance of an NDMP server process existsfor each connection to an NDMP client. That is, if twobackups are in progress, an NDMP server process exists foreach backup.

NDMP server application

An NDMP storage unit stores the backup data for an NDMPhost. The tape drives in this storage unit attach directly tothe NDMP host or can be configured on a SAN. Note thatNDMP storage units cannot be used to store data fornon-NDMP hosts, and NetBackup disk storage units cannotbe used for NDMP tasks.

NDMP storage unit

In a redirected restore, files are restored to a client otherthan the one from which they were originally backed up. InNetBackup for NDMP, the following occurs: the restore datatravels from an NDMP host (or NetBackup media server)with a locally attached storage device to another NDMP hoston the network.

Redirected restore (to adifferent client)

15Introduction to NetBackup for NDMPNetBackup for NDMP terminology

Table 1-1 Terminology (continued)

DefinitionTerm

See “Configuring NDMP backup to Media Manager storageunits” on page 56.

Remote NDMP

In a three-way backup or restore, data travels in thefollowing manner: between an NDMP host and a storagedevice that is attached to another NDMP host or to aNetBackup media server. This backup contrasts with localNDMP backup or restore where the data travels as follows:between an NDMP host’s disk and a storage device directlyattached to the same NDMP host.

Three-way backup/restore

A virtual tape library is a storage system that usesdisk-based technology to emulate a tape library and tapedrives. For secondary storage, NetBackup can copy VTLimages directly to a physical tape or to another VTL, bymeans of NDMP direct copy.

Virtual Tape Library (VTL)

Network data management protocol (NDMP)NDMP is a widely used protocol. through which an NDMP-conformant backupapplication controls the backups and restores of any NDMP host that runs anNDMP server application.

NDMP architecture follows the client/server model:

■ The NetBackup master or media server where NetBackup for NDMP is installedis called a NetBackup for NDMP server.

■ The host where the NDMP server application resides is called an NDMP host.

■ The NetBackup software is a client of the NDMP server application. NetBackupfor NDMP lets NetBackup act as an NDMP client. The NDMP hosts, on theother hand, act as NetBackup clients.

Introduction to NetBackup for NDMPNetwork data management protocol (NDMP)

16

Figure 1-1 NDMP and NetBackup hosts as clients of each other

NDMP Host NDMP Host

NDMP hosts act as NetBackup clients ...

NOTE: NetBackup software is NOT installedon NDMP hosts.

Network

NetBackup for NDMP server

A NetBackup master or media serverwhere NetBackup for NDMP isinstalled.

The NetBackup for NDMP server acts asan NDMP client.

Types of NDMP backupThe NDMP server application on the NDMP host performs backups and restoresof the NDMP host, directed by commands from an NDMP client (NetBackup).Backups can be conducted in any of the following ways:

■ NDMP local backup

■ NDMP three-way backup

■ Backup to a Media Manager storage unit on the NetBackup server

NDMP local backupThe NetBackup for NDMP server initiates the backup. The data travels from theNDMP host’s disk to a storage device that is attached to the same host. Or thestorage device is available on a SAN.

17Introduction to NetBackup for NDMPTypes of NDMP backup

Figure 1-2 NDMP local backup/restore

NDMPhost

LAN/WAN

NetBackup forNDMP server

Tape libraryDisks

Local NDMP backup

Data travels from disk to tape on same NDMP host, or from disk totape device on SAN. Backup data is NOT sent over local network.

The tape drives must be in NDMP-type storage units.

Storage devices on SAN

FC/SAN

NDMP three-way backupThe NetBackup for NDMP server initiates the backup. Data travels over the networkin the following manner: from an NDMP host to a storage device that is attachedto another NDMP host on the local network or available on a SAN.

Introduction to NetBackup for NDMPTypes of NDMP backup

18

Figure 1-3 NDMP three-way backup/restore

NDMPhost

LAN/WAN


Tape libraryDisks

Three-Way NDMP backup

Data travels from disk on an NDMP host to tape device on anotherNDMP host. Backup data is sent over the local network.

The tape drives must be in NDMP-type storage units.

NDMPHost

Backup to Media Manager storage units (remote NDMP)The data travels over the network in the following manner: from an NDMP hostto a Media Manager-type storage device that is attached to a NetBackup mediaserver or available on the SAN. The NetBackup drive(s) must be in Media Managerstorage units (not NDMP storage units).

19Introduction to NetBackup for NDMPTypes of NDMP backup

Figure 1-4 NDMP backup to a media manager device (remote NDMP)

LAN / WAN


To NetBackup Server-Attached Media Manager Storage Units

Data travels from NDMP host to a drive on a NetBackup media server or on a SAN. Backupdata is sent over the local network.

NOTE: The NetBackup drive(s) must be in Media Manager type storage units.

Storage Devices on SAN

FC/SAN

NDMPhost

DisksTape library

NDMP policiesAfter you install and configure NetBackup for NDMP, you can schedule backupsby creating an NDMP policy in NetBackup.

An NDMP policy can have one or more NetBackup clients. Each NetBackup clientmust be an NDMP host.

See Figure 1-1 on page 17.

Note that you do not install any NetBackup software on the NDMP hosts.

The allowable backup types for schedules in an NDMP policy are: Full, CumulativeIncremental, or Differential Incremental. User-initiated backups and archives arenot allowed because the NDMP protocol does not permit these tasks.

Restores of NDMP host backups can be initiated from any NetBackup media serverthat meets the following criteria:

■ Is within the same overall NetBackup storage domain

■ Uses the same NetBackup master server that the media server uses thatperformed the backup

Introduction to NetBackup for NDMPNDMP policies

20

The data can be restored to the NDMP host where it was backed up, or to anotherNDMP host.

NDMP policies can use either NDMP storage units or Media Manager storage units.

Storage unitsNetBackup uses either of the following storage units:

■ NDMP-type storage units (for local or three-way backup)

■ Media Manager storage units (for backup to devices that are attached to aNetBackup media server)

NDMP Storage unitsNetBackup requires NDMP-type storage units when you back up NDMP host datato the devices that are as follows:

■ Attached to an NDMP host

■ Available to the NDMP host on a SAN

An NDMP storage unit can contain stand-alone or robotic drives. Robotic controlscan be in a TLD (Tape Library DLT), TL8 (Tape Library 8MM), TLH (Tape LibraryHalf Inch), or ACS robot type.

Media Manager storage unitsYou can use drives that were configured in Media Manager-type storage unitswhen you back up NDMP host data to devices that are as follows:

■ Attached to a NetBackup for NDMP server

■ Available to the server on a SAN

For NDMP backup, drives in Media Manager-type storage units do not have to bededicated to NDMP data. They can store backups of regular (non-NDMP) NetBackupclients as well as of NDMP clients.

Assigning tape drives to different hostsRobotic tape drives can be divided up among NDMP hosts and NetBackup servers.

Figure 1-5 shows the following:

■ Tape drives 1, 3, and 5 are attached to NDMP hosts. They are in NDMP storageunits that can be used for NDMP backup (local or three-way).

21Introduction to NetBackup for NDMPStorage units

The commands that control these drives originate on the NetBackup for NDMPserver and are sent through the NDMP connection on the network. The NDMPserver application on each NDMP host translates the NDMP commands intoSCSI commands for the local drives.

■ Tape drives 2 and 4 are attached to a NetBackup server. They are in non-NDMPstorage units and are controlled in the same way as other drives on NetBackupservers. Depending on the type of storage unit, these drives can be used forthe following:

■ For non-NDMP clients of NetBackup

■ In the case of tape drives in Media Manager storage units, they can be usedfor both NDMP (local or three-way) and non-NDMP backup.

In this diagram, all tape drives except drive 4 can be used for NDMP backup.

Figure 1-5 NDMP and non-NDMP storage units

Drive 1*

TLDRobot

NDMPhost

LAN/WAN

Drive 2†Drive 3*

Drive 5*

*

Drive-control commands for NDMP

NB forNDMPmediaserver

NDMPhost

NDMPhost

†In NDMP storage unit

In NetBackup MediaManager storage unit

In another type ofNetBackup storageunit (not NDMP orMedia Manager)

‡

Drive 4‡

Drive 2 (in Media Manager storage unit) canbe used for NDMP or non-NDMP backup.

Drives 1, 3, and 5 (in NDMP storageunits) can be used for NDMP backups.

Drive 4 (in different type of NetBackup storageunit) cannot be used for NDMP backup.

Introduction to NetBackup for NDMPStorage units

22

NDMP hostRobotics control can be attached to an NDMP host or to a NetBackup server.

Figure 1-6 shows how NetBackup sends commands over the network to the NDMPhost, which in turn sends them to the robot.

Figure 1-6 Robotics control that is attached to an NDMP host

Commands to controlrobot

Robot

NetBackupFor

NDMPserver

NDMPhost

Roboticcontrol

NetBackup serverFigure 1-7 shows how the robot is controlled in the same way as other robots onNetBackup servers.

Figure 1-7 Robotics control that is attached to a NetBackup server

Commands to controlrobot

Roboticcontrol

Robot

NDMPhost

NetBackupserver

23Introduction to NetBackup for NDMPStorage units

NDMP backup processDuring a backup, the following events occur in this order:

■ From the EMM database, NetBackup obtains a media ID for the tape that isused for the backup and sends a tape-mount request to ltid.

■ ltid on the NetBackup for NDMP server sends the necessary NDMP (SCSIrobotic) commands to mount the requested tape on the storage device.

■ NetBackup sends the NDMP commands that are necessary to have the NDMPserver application perform a backup to the tape. The backup data travels inone of two ways:

■ Between the local disk and tape drives on an NDMP host.

■ Over the network, data travels in the following manner: from an NDMPhost without its own storage device to an NDMP host (or NetBackup mediaserver) with a locally attached storage device (three-way backup).

■ The NDMP server application sends information to the NetBackup for NDMPserver about the files that were backed up. This information is stored in theNetBackup file database.

■ The NDMP server application sends status about the backup operation to theNetBackup for NDMP server.

Figure 1-8 shows the NetBackup processes that are involved in NDMP backups.

Introduction to NetBackup for NDMPNDMP backup process

24

Figure 1-8 NetBackup backup processes

NetBackup Master Server

bprd

NetBackupAdministration

Console

bpdbm

bpcd

bpbrm

bptm

ltid

ConfigurationDatabase

FileDatabase

Catalog information

TapeRequest

NetworkConnection

NDMP Host

Tape

OS

NDMP Server

NDMP Host

OS

Disk

“3-way”

Local

NetBackup Master orMedia Server

This server hasNetBackup for NDMP

ndmpagent

NDMP Server

nbpem

EMMdatabase nbjm

nbrb

nbproxy

nbproxy

nbemm

Disk

NDMP restore processBecause of the design of the NDMP protocol, only an administrator on a NetBackupserver (master or media) can restore files from NDMP backups. During a restore,

25Introduction to NetBackup for NDMPNDMP restore process

the administrator browses the file catalog and selects files from NDMP images inthe same manner as for standard backup images.

The following events occur during a restore, in this order:

■ The NetBackup for NDMP server looks in its EMM database for the tape thatcontains the backup, and asks ltid to mount that tape.

■ ltidon the NetBackup for NDMP server sends the necessary NDMP commandsto load the requested tape on the storage device.

■ NetBackup sends the NDMP commands that are necessary to have the NDMPserver application perform a restore operation to the disk. The restore datatravels in one of two ways:

■ From a tape drive to a local disk (tape drive and disk are on the same NDMPhost)

■ Over the network, from an NDMP host (or NetBackup media server) witha locally attached storage device to another NDMP host (three-waybackup/restore)

■ The NDMP server application sends status about the restore operation to theNetBackup for NDMP server.

Figure 1-9 shows the NetBackup processes involved in NDMP restores.

Introduction to NetBackup for NDMPNDMP restore process

26

Figure 1-9 NetBackup restore processes

bptm

NetworkConnectionEMM

database

bpcd

bpbrm

ltid

NetBackup Media ID

Tape Request

NetBackup Master Server Backup, Archive, and Restore (onmaster or media server)

bprdbprd is on themaster server

NDMP Host

Tape

OS

Disk

NDMP Host

OS

Local

NetBackup Master orMedia Server

This server hasNetBackup for NDMP.

ndmpagent

NDMP Server NDMP Server

“3-way”

Disk

Direct access recovery (DAR)NetBackup uses Direct Access Recovery (DAR) to restore a directory or individualfiles from a backup image. DAR can greatly reduce the time it takes to restorefiles and directories. DAR is enabled by default (no configuration is required).

DAR enables the NDMP host to position the tape to the exact location of therequested file(s). It reads only the data that is needed for those files. For individualfile restore, NetBackup automatically determines whether DAR shortens the

27Introduction to NetBackup for NDMPDirect access recovery (DAR)

duration of the restore. It activates DAR only when it results in a faster restore.Further details are available as to when DAR is used and how to disable it.

See “About enabling or disabling DAR” on page 52.

The following two prerequisites are necessary for using DAR with NetBackup forNDMP:

■ The NDMP host must support DAR where the NDMP server application resides.

■ NetBackup 4.5 GA or later, with the catalog in binary format (binary formatis the default).

NDMP direct copy with VTLNetBackup supports virtual tape libraries (VTLs). A virtual tape library usesdisk-based technology to emulate a tape library (robot) and drives. The backupimage is written to one or more disks in the VTL. The VTL allows the image to betreated as though it resides on tape, but with the access speed of a disk.

For additional storage (such as for disaster recovery), NetBackup copies backupimages from the VTL disk to a physical tape in an NDMP storage unit. It copieswithout using media server I/O or network bandwidth. NetBackup can also copyNDMP images directly between NDMP tape drives attached to an NDMP host. Inboth cases, this feature is called NDMP direct copy. This feature also enablesNetBackup to restore data directly from either the image in the VTL or from thephysical NDMP tape.

To initiate the NDMP direct copy, you can use the NetBackup duplication featurein the Administration Console, or the bpduplicate command, or NetBackup Vault.

Figure 1-10 represents a VTL from two perspectives: it shows the actual hardwarepresent in a VTL configuration and the configuration from the perspective ofNetBackup.

Introduction to NetBackup for NDMPNDMP direct copy with VTL

28

Figure 1-10 Overview of NDMP direct copy with VTL

LAN/WAN

NetBackup media server

Tape libraryfor tertiarystorage

SCSIorSAN

Actual hardware in VTL configurationHardware from NetBackup perspective

VTL is a disk storage systemthat emulates both a tapelibrary and an NDMP tapeserver

VTL(disk array)

SCSI or SAN

LAN/WAN

NetBackup media server

SCSIorSAN

On NetBackup, the VTL isconfigured as a tape library withtape drives.

SCSI or SAN

Tape libraryfor tertiarystorage

VTLappears tobe a robot

The NDMP direct copy feature uses a VTL that has an embedded NDMP tape serverusing the NDMP protocol. The embedded NDMP tape server moves the imagefrom the VTL disk directly to a physical tape. The image does not pass throughthe NetBackup media server or travel over the network.

Figure 1-11 shows the data flow and control for a VTL.

29Introduction to NetBackup for NDMPNDMP direct copy with VTL

Figure 1-11 NDMP direct copy with VTL: data flow and control

LAN/WAN

NBmediaserver

VTL

physical tape library

SCSIorSAN

SCSI or SAN

1. NetBackup media server sends the backup over a direct device path (SCSI or SAN) to the VTL.

2. NetBackup selects an NDMP device path to the VTL and creates an NDMP control session for the device.

3. NetBackup selects a tape volume from the physical tape library. It then selects an NDMP device path fromthe library and creates a second NDMP control session for the device.

4. By means of the NDMP protocol, the backup image in the VTL is copied directly to the physical tape library(not sent over the network).

5. The image can be restored directly to the media server from either the VTL or the physical tape.

NDMPsessionin VTL

NDMPsessionin VTL

NDMP direct copy without VTLBy means of the NetBackup duplication feature, NetBackup can copy NDMP imagesbetween tape drives attached to an NDMP host. A typical usage is to copy imagesbetween tape drives within the same tape library. (Images can also be copiedbetween tape libraries.) Like NDMP direct copy with a VTL, the copied data doesnot pass through the NetBackup media server or travel over the network.

Introduction to NetBackup for NDMPNDMP direct copy with VTL

30

Figure 1-12 NDMP direct copy between tape drives accessible to an NDMP host

NDMPhost

NetBackup forNDMP server SCSI or SAN

NDMP directcopy

LAN/WAN

NDMP direct copy: notes and limitationsNote the following:

■ Supports backup to tape and restore from tape, for NDMP data as well asnon-NDMP data.

■ Does not support synthetic backup or multiple copies.

■ Does not support multiplexed backup.[**fr Don Peterson's original statement, which may not be needed (waiting forreply fr Don): Cannot be used to duplicate multiplexed backup jobs or anybackup images that are part of a multiplexed backup job.]

■ Does not support storage unit groups for the destination device. If you selecta storage unit group, NDMP direct copy is disabled. The data transfer takesplace over the network by means of the NetBackup server.

■ In a VTL environment, a NAS appliance is not required: the VTL emulates aNAS (NDMP) host. The VTL requires NDMP tape server functionality.

■ NetBackup for NDMP software must be installed. NetBackup for NDMP isenabled by the Virtual Tape Option license. Requires the NDMP protocol versionV4 or higher.

■ NetBackup servers (master and media) must be at NetBackup 6.5 or later.**Phil G thinks this ref to 6.5 is OK, because support for NDMP direct copystarted then.

31Introduction to NetBackup for NDMPNDMP direct copy with VTL

■ The NetBackup 7.x Hardware Compatibility List (HCL) indicates which VTLsoftware supports this functionality:http://entsupport.symantec.com/docs/336875.htm

NDMP information on the WebThe Symantec support web site has a PDF document on supported NDMP operatingsystems and NAS vendors. The document is titled NetBackup for NDMP: NASAppliance Information. It also contains configuration and troubleshooting helpfor particular NAS systems:

http://entsupport.symantec.com/docs/267773

For the features and software releases for each NAS vendor, for SSO support, andfor the NetBackup versions that support these vendors, refer to the NetBackup7.x Hardware Compatibility List (HCL):

http://entsupport.symantec.com/docs/336875.htm

Snapshot Client AssistanceFor Snapshot Client assistance, see theNetBackupSnapshotClientAdministrator’sGuide. For additional information, see the Snapshot Client Configurationdocument:

http://entsupport.symantec.com/docs/288300

Document 288300 includes the following:

■ An up-to-date list of supported operating systems and peripherals

■ A list of NAS vendors that are supported for the NAS_Snapshot method.

■ Sections on SAN device configuration and on setting up NetBackup for off-hostdata mover backups (including instructions on creating 3pc.conf andmover.conf files)

NDMP multiplexingNDMP multiplexing concurrently writes multiple backup streams to the sametape storage device from the same client or different clients. NDMP multiplexingonly supports remote NDMP and improves overall NetBackup performance bybetter using tape storage devices. State of the art tape storage devices can typicallystream data faster than client agents can create backup streams. Thereforemultiple data streams can be sent to and effectively processed by a given tapestorage unit.

Introduction to NetBackup for NDMPNDMP information on the Web

32

A Network Attached Storage (NAS) device with an NDMP server is an agent thatproduces a backup stream that is similar to a NetBackup client. Multiplexing isdesired for NDMP backups because NAS devices are limited in the rate at whichthey create backup streams. These backup streams are often much slower thanthe tape storage device consuming and writing the stream.

NDMP multiplexing provides the following features:

■ Several backups can be run at the same time writing to the same tape. Thisprocess can reduce the need for many tape devices.

■ Backup time is reduced by writing concurrent backups to a single tape storagedevice.

■ Many tape storage devices require that data is streamed to them at hightransfer rates. When data is not streamed fast enough, they do not workefficiently and are subject to possible excessive wear.

About NDMP multiplexing general considerationsConsider the following general items when implementing NDMP multiplexing.

■ Only media manager tape storage units can be used for NDMP multiplexing.

■ Multiplexing of NDMP backups and restores only supports remote NDMP. Theremote NDMP processes backup streams by going through the media server.

■ NDMP local and NDMP three-way backups and restores are not supported forNDMP multiplexing. Each of these methods process backup streams withoutgoing through the media server.

■ Synthetic backups are not supported.

■ Only tape devices are supported.

■ Disk storage devices are not supported.

■ A mix of NDMP and non-NDMP backups can be present in the same MPXbackup group.

■ File and directory DAR are allowed.

■ NDMP multiplexing works with both VTL and PTL. However, VTL userstypically do not use NDMP multiplexing because they can add more virtualtape devices to accommodate additional streams.

■ For NDMP multiplexed backups the storage unit and policy schedule multiplexvalue must be set to a value greater than one.

33Introduction to NetBackup for NDMPNDMP multiplexing

Introduction to NetBackup for NDMPNDMP multiplexing

34

Installing NetBackup forNDMP


■ Installation prerequisites

■ Installing on UNIX servers

■ Installing on Windows servers

■ Uninstalling NetBackup for NDMP

Installation prerequisitesNote the following items:

■ The NetBackup for NDMP master or media server must run NetBackup 7.0 orlater.

■ For a list of operating systems that NetBackup 7.0 for NDMP supports, referto the NetBackup 7.x Operating System Compatibility List.http://seer.entsupport.symantec.com/docs/337048.htm

■ For a detailed list of NAS platforms that NetBackup for NDMP supports, referto the following document:http://seer.entsupport.symantec.com/docs/267773.htm

■ For making snapshots of NDMP (NAS) hosts, NetBackup Snapshot Clientsoftware must be installed on the following: The NetBackup master server andthe NetBackup clients that are used to perform backups.For more information, refer to theNetBackupSnapshot ClientAdministrator’sGuide.

2Chapter

■ The drives and robots that are attached to the NDMP host must be the typesthat the NDMP host and NetBackup support. A list of supported robot typesis available.See “NDMP Storage units” on page 21.For more information on storage devices, see the NetBackup Administrator’sGuide, Volume I.

■ Notes and tips on your particular NDMP host are available.See “NDMP information on the Web” on page 32.

Installing on UNIX serversNetBackup for NDMP installs on a UNIX or Linux system when the NetBackupserver software is installed. No separate installation procedure is required.However, you must enter a valid license key to use NDMP. On the UNIX host thatyou want to be the NetBackup for NDMP server, perform the following procedure.

Note: If you install in a cluster environment, first freeze the active node so thatmigrations do not occur during installation. For information about freezing aservice group, see the clustering section in the NetBackup High AvailabilityAdministrator’s Guide for the cluster software you are running.

To install NetBackup for NDMP

1 Log on as root.

2 Install NetBackup server and client software as explained in the NetBackupInstallation Guide for UNIX and Linux.

3 To make sure a valid license key for NetBackup for NDMP is registered, enterthe following command to list and add keys:

/usr/openv/netbackup/bin/admincmd/get_license_key

4 If this NetBackup for NDMP server is not your master server, install yourNDMP license key on the master.

5 In a clustered environment, perform these steps on each node in the cluster.

6 If you install in a cluster environment, unfreeze the active node after theinstallation completes.

For information about unfreezing a service group, see the clustering sectionin the NetBackup High Availability Administrator’s Guide for the clustersoftware you are running.

Installing NetBackup for NDMPInstalling on UNIX servers

36

Installing on Windows serversUse this procedure on the Windows host that you want to be the NetBackup forNDMP server.

Note: If you install in a cluster environment, first freeze the active node so thatmigrations do not occur during installation. For information about freezing aservice group, see the clustering section in the NetBackup High AvailabilityAdministrator’s Guide for the cluster software you are running.

To install NetBackup for NDMP

1 Log on.

2 Install NetBackup server and client software as explained in the NetBackupInstallation Guide for Windows.

3 NetBackup for NDMP is part of the core NetBackup product. To make sure avalid license key for NetBackup for NDMP is registered, do the following tolist and add keys:

■ In the NetBackup Administration Console, select Help.

■ On the Help menu, select License Keys.

■ Existing keys are listed in the lower part of the window.

■ To register a new key, click the star icon to open the Add a new LicenseKey dialog box. Type the new license key in the Newlicensekey field andclick Add.

The new license key appears in the lower part of the dialog box.

4 If this NetBackup for NDMP server is not your master server, install yourNDMP license key on the master.

5 In a clustered environment, perform these steps on each node in the cluster.

6 If you install in a cluster environment, unfreeze the active node after theinstallation completes.

For information about unfreezing a service group, see the clustering sectionin the NetBackup High Availability Administrator’s Guide for the clustersoftware you are running.

Uninstalling NetBackup for NDMPThis procedure uninstalls NetBackup for NDMP (and all of NetBackup).

37Installing NetBackup for NDMPInstalling on Windows servers

To uninstall NetBackup

1 On the master server, check the Activity Monitor in the NetBackupAdministration Console. Make sure no NetBackup for NDMP backups areactive or running for the client (the Job State field should read Done).

2 Perform the uninstall procedure that is described in theNetBackupInstallationGuide. Note: that procedure uninstalls all of NetBackup.

Installing NetBackup for NDMPUninstalling NetBackup for NDMP

38

Configuring NDMP backupto NDMP-attached devices


■ About configuring NDMP-attached devices

■ Authorizing access to the NDMP host

■ Media and Device Management configuration

■ Verifying NDMP password and robot connection

■ Adding NDMP storage units

■ About creating an NDMP policy

■ About enabling or disabling DAR

■ Setting up clustering

■ Testing an NDMP configuration

About configuring NDMP-attached devicesThis topic explains how to configure backups on the storage devices that areattached to NDMP hosts. Only NDMP-specific steps are described.

You can also use the NetBackup Device Configuration wizard to discover andconfigure the robots and drives that are attached to an NDMP host. The wizardrequires NDMP protocol versions V3 or V4.

To configure and use the NAS_Snapshot method, see the NetBackup SnapshotClient Administrator’s Guide.

3Chapter

Authorizing access to the NDMP hostBefore NetBackup can carry out backups, it must have access to the NDMP host.

Note:Do the following on the master server (not media server) if you plan to createsnapshots using the Snapshot Client NAS_Snapshot method.

To authorize NetBackup access to the NDMP host

1 On the NetBackup server, from the Administration Console: under Mediaand Device Management > Credentials, click NDMP Hosts.

2 Under Actions, select New > NDMP Host.

3 In the NDMP host name dialog box, enter the name of the NDMP server forNetBackup to back up.

The NDMP host name is case sensitive. Whenever this host name is used, thename must be identical to the name entered here. (For example, when youconfigure tape drives and storage units for this host.)

4 Click OK.

5 In the New NDMP Host dialog box, specify the following:

(The term credentials refers to the user name and password that NetBackupuses to access the NDMP host.)

Select this option to enable all NetBackup mediaservers under the master server to access this NDMPhost using a pre-defined global NDMP login.

To create this login, click Host Properties > MasterServer > Properties > NDMP in the NDMP GlobalCredentials dialog box.

Use global NDMPcredentials for this NDMPhost

This option enables all NetBackup media servers thatare connected to the NDMP host to access the NDMPhost using the login you specify:

■ Username: the user name under which NetBackupaccesses the NDMP server. This user must havepermission to run NDMP commands.

You can find out whether your NDMP host vendorrequires a particular user name or access level.

See “NDMP information on the Web” on page 32.

■ Password and Confirm Password: enter thepassword for this user.

Use the followingcredentials for this NDMPhost on all media servers

Configuring NDMP backup to NDMP-attached devicesAuthorizing access to the NDMP host

40

Select this option to specify NDMP logins for particularNetBackup servers. Then click AdvancedConfiguration.

■ In the Advanced NDMP Credentials dialog box, clickAdd.

■ In the Add Credentials dialog box, select aNetBackup server and specify the user name andpassword it uses to access the NDMP host.

■ Click OK. NetBackup validates the user name andpassword.

■ The NetBackup server and user name appear in theAdvanced NDMP Credentials dialog box.

■ If necessary, click Add again to specify otherservers and user

Usedifferentcredentialsforthis NDMP host on eachmedia server

6 Repeat this procedure for each NDMP host that NetBackup backs up.

Access for three-way backups and remote NDMPTo perform three-way backups, you must authorize access to the NDMP host asdescribed in the previous section.

Note the following points:

■ Three-way backups: for the NDMP host name, specify the NDMP host thathas no attached tape drive.

■ NDMP to Media Manager storage units (remote NDMP): for the NDMP hostname, specify the NDMP host to back up to the Media Manager storage unitthat is defined on the NetBackup server.See the topic on remote NDMP.

Media and Device Management configurationOn the NetBackup for NDMP server, use Media and Device Management in theAdministration Console to add drives and robots. As an alternative, you can usethe NetBackup Device Configuration wizard.

The following procedures and examples treat NDMP configuration issues only.

See the NetBackup Administrator’s Guide, Volume I, for general information onconfiguring NetBackup media.

More information on configuring storage devices for specific NDMP hosts isavailable.

41Configuring NDMP backup to NDMP-attached devicesMedia and Device Management configuration


These procedures do not apply to setting up the devices that are attached to theNetBackup media server. To back up NDMP data to media servers, you mustconfigure storage units in the same way as ordinary NetBackup (non-NDMP)devices.

See “About remote NDMP” on page 55.

See also the NetBackup Administrator’s Guide, Volume I.

Adding a robot directly attached to an NDMP hostThis procedure describes how to configure a robot that is attached to an NDMPhost.

To add a robot directly attached to an NDMP host

1 Start the NetBackup Administration Console on the NetBackup for NDMPserver as follows:

In the Windows Start menu, click Programs > SymantecNetBackup > NetBackup Administration Console.

Windows

Enter the following:

/usr/openv/netbackup/bin/jnbSA &

UNIX

2 Select Media and Device Management > Devices in the left pane.

3 On the Actions menu, select New. Then select Robot. from the popup.

Configuring NDMP backup to NDMP-attached devicesMedia and Device Management configuration

42

4 In the Add Robot dialog box, select the following:

Specify the host that manages the EMM database (by default,this host is the NetBackup master server).

Media Manager host

Use the pull-down to select the NetBackup media server.Device host

Specify type.Robot type

Specify number.Robot number

Click Robot control is attached to an NDMP host.Robot control

Enter the device name of the robot. You do not need to includethe NDMP host name as part of the device path.

Robot device path

You can determine the device name of the robot. Moreinformation on your NDMP host is available.


Enter the name of the NDMP host to which the robot isattached

NDMP host name

Specify these values if the NDMP host requires them. Bydefault, the bus, target, and lun values are 0.

Bus, Target, and LUNvalues

More information on your NDMP host is available.



Explained in online helpor in the NetBackupAdministrator’s Guide,Volume I.

Explained in thefollowing steps.

For further assistance with the Add Robot dialog box, refer to the online help.The following steps explain the portions that are unique to configuringNetBackup for NDMP.

5 Click OK.

6 In the popup message that asks if you want to stop and restart the devicemanager service (or daemon), click Yes.

Adding a driveThis procedure describes how to configure a tape drive.


44

To add a drive

1 In the NetBackup administration console, select Media and DeviceManagement > Devices in the left pane.

2 On the Actions menu, select New.

3 In the popup, select New Drive (on UNIX, Tape Drive).

4 In the Add a New Drive dialog box, in the Drive Name box, enter the nameof the drive.

5 Click Add to specify a drive path.


6 In the Add Path dialog box, select the host and the path information as follows:

Select the name of the NetBackup media server. Use thepull-down to select media servers already defined, or click Addto enter a new one.

Device host

Enter the device file name of the tape drive, such as nrst2a. Referto the NAS vendor documentation for your drive for the correctformat of the device file name.

Alternate method: use the following command to find the devicefile name for the drive, if the NDMP host is running NDMPprotocol V3 or later:

tpautoconf -probe ndmp_host_name

Path

7 Click This path is for a Network Attached Storage device.

8 In the NDMP Host drop-down list, select the name of the NAS filer to whichthe drive is attached.

9 Click OK.

10 Return to the Add a New Drive dialog box and enter the drive information asrequired. Repeat this procedure for each drive that must be added.

When you are prompted to restart the Media Manager device daemon and allrobotic daemons, click Yes.

Checking the device configurationOn the NetBackup for NDMP server, use the following procedure.

To check the device configuration

1 On UNIX, execute /usr/openv/volmgr/bin/vmps

Verify that ltid, vmd, avrd, and any required robotic daemons are active.

2 On Windows, go to the NetBackup Administration Console

Use the Activity Monitor (Processes tab) to verify that ltid, vmd, avrd, andany required robotic daemons processes are active.

3 From the NetBackup Administration Console, use the Device Monitor toensure that the drive is in the UP state.


46

About adding volumesUse the NetBackup Media and Device Management utility to add the volumesthat you plan to use for the NDMP host backups.

See the NetBackup Administrator’s Guide, Volume I, for instructions.

When you specify the Robot Control Host for a volume that is in a robot, specifythe host name for the NetBackup for NDMP server. Do not specify the NDMP host.

Verifying NDMP password and robot connectionWhen you authorize NetBackup access to the NDMP host and configure robotsusing the Administration Console, NetBackup automatically verifies NDMPcredentials and the robotic configuration. If you want, you can re-verify them.For example:

tpautoconf -verify ndmp_host_name

A successful verification looks like the following:

Connecting to host "stripes" as user "root"...

Waiting for connect notification message...

Opening session--attempting with NDMP protocol version 4...

Opening session--successful with NDMP protocol version 4

host supports MD5 authentication

Getting MD5 challenge from host...

Logging in using MD5 method...

Host info is:

host name "stripes"

os type "NetApp"

os version "NetApp Release 7.0.0.1"

host id "0033625811"

Login was successful

Host supports LOCAL backup/restore

Host supports 3-way backup/restore

Adding NDMP storage unitsOn the NetBackup master server, add an NDMP-type storage unit for the devicesthat contain the backup data. Most of the requirements are the same as for addinga Media Manager storage unit. The following explains how to add an NDMP storageunit.

47Configuring NDMP backup to NDMP-attached devicesVerifying NDMP password and robot connection

See the NetBackup Administrator’s Guide, Volume I, for more information onstorage units.

NDMP-type storage units are not used for backups to devices that are attachedto NetBackup media servers. Use a non-NDMP storage unit instead.

See the topic on remote NDMP.

To add NDMP storage units

1 In the NetBackup Administration Console, select NetBackup Management> Storage.

2 On the Actions menu, select New > Storage Unit.

3 In the New Storage Unit dialog box, enter the following:

Enter a unique name for the storage unit.Storage unit name

Select NDMP.Storage unit type

This option specifies whether the storage unit is availableonly when a policy or schedule specifically requests it. If thisoption is not used, the storage unit is available to any NDMPpolicy or schedule.

On demand only

Select the type of device for this storage unit.Storage Device

Select the media server associated with this storage unit.Media server

Select the maximum number of drives for concurrentwritting.

Maximumconcurrentwrite drives

Enter the minimum fragment size for this storage unit.Reduce fragment sizeto

Select this item to enable NDMP multiplexing.Enable multiplexing

Select the maximum number of data streams to use withNDMP multiplexing.

Note: You must select at least two data streams.

Maximumstreamsperdrive

The remaining fields are described in the NetBackup Administrator’s Guide,Volume I.

About creating an NDMP policyOn the NetBackup master server, you must create an NDMP policy to configurebackups of the NDMP host.

Configuring NDMP backup to NDMP-attached devicesAbout creating an NDMP policy

48

Note:You can use the Backup Policy Configuration wizard to create NDMP policies.

Creating an NDMP policy is very similar to creating other NetBackup policy types.The following topics explain the differences when creating NDMP policies.

See the NetBackup Administrator’s Guide, Volume I, for more information onNetBackup policies and the Policy utility.

To configure a policy for the NAS_Snapshot method, see theNetBackup SnapshotClient Administrator’s Guide.

AttributesThe following policy attributes are required:

Do not select any other policy type.Policy Type: NDMP

■ To direct backups for this policy to a specific storage unit ifthe NDMP host has multiple storage units, specify that storageunit name.

■ For a three-way backup, specify a storage unit that was definedfor the target NDMP host with attached tape.

■ For NDMP backup to Media Manager storage units: specify aMedia Manager storage unit that is defined for a device thatis connected to a NetBackup media server.

See the topic on remote NDMP.

Policy Storage Unit

SchedulesIn the schedules list under the attributes tab, the following is optional for eachschedule in an NDMP policy but is required for NDMP multiplexing:

This value must be set to a number greater than one.Media multiplexing

ClientsIn the client list, the following are required for each client in an NDMP policy:

Name of the NDMP hostHostname

NDMP NDMPHardware andoperating system

49Configuring NDMP backup to NDMP-attached devicesAbout creating an NDMP policy

Files (Backup Selections)The Backup Selections list must specify directories from the perspective of theNDMP host.

Two examples:

/home/dir1/

/vol1

The following Backup Selections capabilities are NOT supported for an NDMPpolicy:

■ Wildcards in pathnames. For example, /home/* is an invalid entry.

■ Individual file names. Only directory or volume names are allowed.

■ Exclude list (because client software is not installed on the NDMP host). Youcan, however, exclude files by using the SET keyword.

See “About environment variables in the Backup Selections list” on page 50.The SET option allows you to exclude files on a backup. The format is vendordependent; refer to the vendor’s documentation for more details on whichvariable can be passed and in what format.

About environment variables in the Backup Selections listNDMP allows you to use environment variables to pass configuration parametersto an NDMP host with each backup. NDMP environment variables can be one ofthe following types:

■ Defined as optional by the NDMP protocol specification.You can set these variables.

■ Specific to an NDMP host vendor.You can set these variables.

■ Reserved for use by NetBackup:FILESYSTEMLEVELDIRECTEXTRACTACL_START

In NetBackup, environment variables can be set within the Backup Selections listby specifying one or more SET directives.

Configuring NDMP backup to NDMP-attached devicesAbout creating an NDMP policy

50

Note: In the Backup Selections list, the SET directive must be the first in the list,followed by the file systems or volumes to back up.

To obtain up-to-date information on environment variables relating to particularNAS vendors, refer to the following:


In general, the syntax of a SET directive is as follows:

SET variable = value

Where variable is the name of the environment variable and value is the valuethat is assigned to it. The value can be enclosed in single or double quotes, andmust be enclosed in quotes if it contains a space character. For example:

SET ABC = 22

SET DEF = "hello there"

SET type = tar

Setting a variable equal to no value unsets that variable. For example:

SET ABC =

Variables accumulate as the Backup Selections list is processed. For example, ifBackup Selections contains the following entries:

/vol/vol1

SET HIST = N

/vol/vol2

SET DEF = 20

SET SAMPLE = all

/vol/vol3

Directory/vol/vol1 is backed up without any user-specified environment variables.The second directory (/vol/vol2) is backed up with the variable HIST set to N. Thethird directory (/vol/vol3) is backed up with all three of the environment variablesset.

If an environment variable appears again later in the list, the value of this variableoverrides the previous value of the variable.

The values that each backup uses are saved and provided to subsequent restoresof the directory. The NDMP host may have some environment variables that areset internally and these are also saved for restores.

51Configuring NDMP backup to NDMP-attached devicesAbout creating an NDMP policy

SchedulesYou can specify any of the following backup types in a schedule for an NDMPpolicy:

■ Full

■ Cumulative Incremental

■ Differential Incremental

Specify Override policy storage unit only in the following situation: this clientof NetBackup (the NDMP host) has more than one storage unit and you want touse a specific storage unit for this schedule. In this case, the client must be theonly client in this NDMP policy.

About enabling or disabling DARBy default, NetBackup for NDMP is configured to use Direct Access Recovery(DAR) when restoring files or directories. DAR is used somewhat differently forfile restore than for directory restore, as follows:

■ For each restore of files (not of directories), NetBackup automaticallydetermines if the use of DAR speeds up the restore. NetBackup uses DAR onlywhen it results in a faster restore.

■ For restore of directories, by default DAR is always used when restoring asubdirectory but never used when restoring the directory containing an entireimage. For example, if /vol/vol0 contains the entire image, and/vol/vol0/dir1 is a subdirectory, DAR is used by default when restoring/vol/vol0/dir1. But it is not used when restoring /vol/vol0.

For restore of subdirectories, NetBackup does not attempt to gauge theeffectiveness of using DAR. Unless DAR is manually disabled, NetBackupalways uses DAR when restoring subdirectories.See “Disabling DAR for file and directory restores” on page 52.

It may be necessary to disable DAR in the following situation: you have problemswith DAR and your NDMP host is an older machine or is not running the latestNAS OS version.

Disabling DAR for file and directory restoresThis procedure disables DAR for both file and directory restores, for all NDMPpolicies.

Configuring NDMP backup to NDMP-attached devicesAbout enabling or disabling DAR

52

To disable DAR

1 In the NetBackup Administration Console, expand HostProperties and clickMaster Servers or Media Servers.

2 Right-click the name of the server and select Properties.

3 Click General Server.

4 Uncheck the Use direct access recovery for NDMP restores box and clickApply.

This action disables DAR on all NDMP restores.

Disabling DAR for directory restores onlyThis procedure disables DAR for directory restores only. It leaves DAR enabledfor individual file restore.

To disable DAR on restores of directories only, for all NDMP policies

1 Enter the string NDMP_DAR_DIRECTORY_DISABLED in the following file:

/usr/openv/netbackup/db/config/ndmp.cfg

2 To re-enable directory DAR, remove (or comment out) theNDMP_DAR_DIRECTORY_DISABLED string from the ndmp.cfg file.

Setting up clusteringBefore configuring NetBackup for NDMP for clustering, the following must beinstalled on each node of the cluster:

■ The NetBackup serverSee the NetBackup Installation Guide.

■ NetBackup for NDMP software.See “ Installation prerequisites” on page 35.For Windows servers, only the NetBackup for NDMP licence key has to beinstalled.

To set up clustering

1 Configure NDMP-attached robots and drives. Then configure storage unitsand policies as in a normal, non-clustered environment:

■ You can use the Device Configuration wizard, or configure devicesmanually.See “Authorizing access to the NDMP host” on page 40.

53Configuring NDMP backup to NDMP-attached devicesSetting up clustering

■ To use the same robotic libraries throughout a cluster, robot numbersmust be consistent. The Device Configuration wizard attempts to ensurethis configuration. If you configure robots manually, be sure to use thesame robot number for a given robot, from one host to another in thecluster.

2 When you finish configuring devices and policies for NetBackup for NDMP,fail-over to the next node in the cluster and configure the drives and robots.

Select the same robot number that you used when configuring the robot forthe first node.

Post-installation changesAfter NetBackup is configured in a clustered environment, most configurationinformation is available to all nodes in the cluster. The information is availableby means of a shared hard drive. However, if you make changes in the HostProperties area of the Administration Console, they are not available on the shareddrive. Such changes apply only to the active node. You must manually duplicateon each node any Host Properties changes that are made on the active node. Thisaction lets NetBackup perform exactly the same way in case of failover to anothernode.

Refer to the NetBackup High Availability Guide for assistance.

Testing an NDMP configurationTo test the configuration, run the backup and then restore some files. See thefollowing topics:

■ See “Performing a manual backup of an NDMP policy” on page 73.

■ See “Performing a restore from the server” on page 74.

■ See “Sources of information” on page 77.

Configuring NDMP backup to NDMP-attached devicesTesting an NDMP configuration

54

Configuring NDMP backupto NetBackup media servers(remote NDMP)


■ About remote NDMP

■ Configuring NDMP backup to Media Manager storage units

About remote NDMPThis chapter describes how to configure NetBackup for NDMP to make backupsto Media Manager storage units (remote NDMP). Only NDMP-specific steps aredescribed.

Using remote NDMP, you can back up NDMP data to a configured drive in a MediaManager storage unit on a NetBackup media server. The drive can be used forboth NDMP backups and for non-NDMP backups.

An added feature to remote NDMP is NDMP multiplexing. NDMP multiplexingworks with remote NDMP. It concurrently writes multiple backup streams to thesame storage device from the same client or different clients.

4Chapter

Figure 4-1 NDMP backup to a Media Manager storage unit

LAN / WAN

NDMP hosts (NAS filers). . .


Data travels between NDMP hosts and a drive on aNetBackup media server.

NOTE: The NetBackup drive(s) need not be dedicated toNDMP backups: they can be used for non-NDMP backups aswell.

NetBackupdrives inMediaManagerstorageunit(s).

ConfiguringNDMPbackup toMediaManager storageunits

This section describes how to configure NDMP backups to Media Manager storageunits.

To configure NDMP backups to Media Manager storage units

1 Authorize the NetBackup server to access the NDMP hosts you want to backup.

Do the following on the master server (not media server) if you plan to createsnapshots using the Snapshot Client NAS_Snapshot method:

■ Under Media and Device Management > Credentials, click on NDMPHosts. Under Actions, choose New > NDMP Host to display the NDMPHost dialog box.

■ Fill in the values.See “Authorizing access to the NDMP host” on page 40.

■ Repeat the above for each NDMP host that the NetBackup server backsup.

2 Use the NetBackup Device Configuration wizard to configure the drive(s) androbot(s).

Note the following:

Configuring NDMP backup to NetBackup media servers (remote NDMP)Configuring NDMP backup to Media Manager storage units

56

■ Do not use the "Configuring NDMP backup to NDMP-attached devices"topic in this guide. Configure the robots and drives as ordinary NetBackupdevices, not as NDMP-attached devices.See the NetBackup Administrator’s Guide, Volume I.

■ Drives can be shared using the Shared Storage Option (SSO) of NetBackup.The drives can be shared as both NDMP drives and non NDMP drives.See “About the Shared Storage Option (SSO)” on page 67.

3 Create a Media Manager storage unit for the drive(s). The storage unit typemust be Media Manager, not NDMP.

Note the following for NDMP multiplexing:

■ Select the Enable Multiplexing item on the New Storage Unit menu.

■ Set the Maximum streams per drive entry to a value greater than one.

For details on storage units, refer to the NetBackup Administrator’s Guide,Volume I.

4 Create an NDMP-type policy. On the New/Change Policy display, be sure tospecify the storage unit that was created in the previous step.

Note the following for NDMP multiplexing:

■ Set the Media multiplexing attribute on the Add New Schedule menu toa value greater than one.

57Configuring NDMP backup to NetBackup media servers (remote NDMP)Configuring NDMP backup to Media Manager storage units

Configuring NDMP backup to NetBackup media servers (remote NDMP)Configuring NDMP backup to Media Manager storage units

58

Configuring NDMP directcopy


■ About NDMP direct copy

■ How to configure NDMP direct copy

■ Using NDMP direct copy

About NDMP direct copyNDMP direct copy can operate in the following environments:

■ A NetBackup media server that is connected to a VTL that has access to aphysical tape library. The steps for configuring NDMP direct copy are describedin this chapter.

■ A NetBackup for NDMP server that is connected to an NDMP host that hasaccess to a tape library (no VTL). This NDMP backup environment is describedin other chapters of this guide. In this environment, no additional configurationis required for NDMP direct copy.If your NDMP host and storage devices are correctly configured, NetBackupuses NDMP direct copy when you duplicate an NDMP backup that NetBackuphad created.

Notes and limitationsSee “NDMP direct copy: notes and limitations” on page 31.

5Chapter

PrerequisitesNote the following prerequisites:

■ If your environment includes a VTL, the VTL must be installed and set upaccording to the vendor’s instructions. The NetBackup Virtual Tape Optionlicense(s) are required. The Virtual Tape Option license enables NDMP directcopy functionality.

■ The VTL must have the NDMP capabilities needed to support NDMP directcopy.

■ To make direct copies from one NDMP tape drive to another (no VTL), theNetBackup for NDMP license is required.

How to configure NDMP direct copyUse the following procedure.

To configure NDMP direct copy from backups that were made to a VTL

1 Configure the VTL as an NDMP host. You can use the Device ConfigurationWizard, as follows.

■ On the Device Hosts dialog box of the wizard, choose the device host, thenclick Change.

■ In the Change Device Host dialog box, select NDMP server and click OK.

■ Click Next. The VTL appears in the NDMP Host column of the NDMP Hostsdialog.See “Using the Device Configuration Wizard” on page 69.

2 Authorize NetBackup access to the VTL. Note that the VTL emulates an NDMPhost.

See “Authorizing access to the NDMP host” on page 40.

3 Configure the VTL as a robot, then configure one or more tape drives in aMedia Manager storage unit.

You can use the NetBackup Device Configuration wizard. Additional helpconfiguring devices and Media Manager storage units is also available.

See the NetBackup Administrator’s Guide Volume I.

Configuring NDMP direct copyHow to configure NDMP direct copy

60

4 Configure one or more tape drives in the VTL as Network Attached Storagedevices, and create one or more NDMP storage units for the drives.

See “Adding a drive” on page 44.

See “Adding NDMP storage units” on page 47.

The drives can be the same as those that were selected in the previous step.NetBackup supports sharing of drives among media servers and NDMP hosts.

5 Configure one or more NDMP tape drives in the physical tape library, andadd the drives to NDMP storage units. Use the same procedures as thosementioned in the previous step.

You can also use these drives in Media Manager storage units, if they areshared on a SAN.

Using NDMP direct copyNetBackup uses NDMP direct copy when you duplicate a backup image. To run aduplication, you can use any of the following:

■ The Duplicate option in the Catalog node of the NetBackup AdministrationConsole.See “Initiate NDMP direct copy with the Administration Console” on page 62.

■ NetBackup Vault.Refer to the NetBackup Vault Administrator’s Guide.

■ The bpduplicate command.Refer to the NetBackup Commands Guide.

RequirementsFor NetBackup to use NDMP direct copy when you duplicate an image, note thefollowing:

■ For the destination for the duplication, you must designate an NDMP storageunit in a VTL or in a physical tape library.

■ An NDMP tape drive must be available to mount the source image. The NDMPtape drive can be one that was defined in the VTL, or it can be a physical tapedrive in a tape library.

Setup instructions are available.

See “About NDMP direct copy” on page 59.

61Configuring NDMP direct copyUsing NDMP direct copy

If these two requirements are met, NDMP direct copy is enabled. NetBackup copiesthe image directly to the designated storage unit without using media server I/Oor network bandwidth.

NetBackup policy typeYou can duplicate an image that any NetBackup policy created; the policy neednot be an NDMP policy.

See “NDMP direct copy: notes and limitations” on page 31.

The backup can be made to a storage unit in the VTL or to a storage device thatis attached to an NDMP host. You can then copy the backup directly to a tape driveusing the NetBackup Duplicate feature, as follows.

Initiate NDMP direct copy with the Administration ConsoleUse the following procedure.

To initiate NDMP direct copy

1 In the NetBackup Administration Console, expand NetBackupManagement> Catalog.

2 Set up the search criteria for the image you want to duplicate. Click SearchNow.

3 Right-click the image(s) you want to duplicate and select Duplicate from theshortcut menu.

You must designate an NDMP storage unit as the destination for theduplication. Use the Storage unit field in the Setup Duplication Variablesdialog box.

See "Duplicating backup images" in the NetBackup Administrator’s Guide,Volume I.

Configuring NDMP direct copyUsing NDMP direct copy

62

Remote NDMP and diskdevices


■ About remote NDMP and disk devices

■ Configuring remote NDMP

About remote NDMP and disk devicesThe remote NDMP feature of NetBackup involves backing up NAS data (NetworkAttached Storage) to a storage device configured on a NetBackup media server.The NetBackup 6.5.2 release added support for disk devices on the media server.

Figure 6-1 shows the main components for NDMP backup to disk storage.

6Chapter

Figure 6-1 NDMP backup to a storage unit on media server (remote NDMP)

NDMP hosts (NAS filers) ...

Backup data travels from NDMP hosts to a disk ortape drive attached to a NetBackup media server oron a SAN.

NOTE: The NetBackup drive(s) need not be dedicatedto NDMP backups: they can be used for non-NDMPbackups as well.

NetBackup drivesin disk storageunits or MediaManager storageunits (tape).

NetBackup forNDMP media server

LAN / WAN

Configuring remote NDMPThis topic describes how to configure NetBackup to make backups to either diskor tape storage units attached to a NetBackup media server. Only NDMP-specificsteps are described.

To configure NDMP backups to disk or tape storage units

1 Authorize the NetBackup server to access the NDMP hosts you want to backup.

Do the following on the NetBackup media server:

■ Under Media and Device Management > Credentials, click on NDMPHosts. Under Actions, choose New > NDMP Host to display the NDMPHost dialog box.

■ Enter the name of the NDMP server (NAS filer) to back up. This NDMPhost name is case sensitive.

Remote NDMP and disk devicesConfiguring remote NDMP

64

■ Repeat the above for each NDMP host that the NetBackup server backsup.

■ If you plan to create snapshots using the Snapshot Client NAS_Snapshotmethod, do the above on the master server (not on the media server).

2 Use the NetBackup Device Configuration wizard to configure devices forremote NDMP (disks, or tape drives and robots, on the media server).

Note the following:

■ Do not use the device configuration procedure in the “Configuring NDMPbackup to NDMP-attached devices” section of the NetBackup for NDMPGuide. Rather, configure the disk, or robots and drives, in the same wayas ordinary NetBackup devices.See the NetBackup Administrator’s Guide, Volume I.

■ Tape drives can be shared using the Shared Storage Option (SSO) ofNetBackup. The drives can be shared as both NDMP drives and non NDMPdrives.See “Using the Shared Storage Option (SSO)” chapter of the NetBackupfor NDMP Guide.

3 Create a disk or Media Manager storage unit for the drive(s). The storage unittype must be Disk or Media Manager, not NDMP.

For details on storage units, refer to the NetBackup Administrator’s Guide,Volume I.

4 Create an NDMP-type policy. On the New/Change Policy display, be sure tospecify the storage unit that was created at

See “Creating an NDMP policy” in the NetBackup for NDMP Guide.

65Remote NDMP and disk devicesConfiguring remote NDMP

Remote NDMP and disk devicesConfiguring remote NDMP

66

Using the Shared StorageOption (SSO)


■ About the Shared Storage Option (SSO)

■ Setting up SSO: overview

■ Using the Device Configuration Wizard

About the Shared Storage Option (SSO)Figure 7-1 shows a robotic library on a SAN that can share its drives between twoNetBackup for NDMP servers and two NDMP hosts. Drive sharing requires alicense for the Shared Storage Option. A SAN is not required.

7Chapter

Figure 7-1 NDMP backup using Shared Storage Option

NetBackupfor NDMPserver 1

LAN

NetBackupfor NDMPserver 2

NetBackup servers 1 and 2 shared drives in thetape library for backing up NDMP hosts.

Drives can be in Media Manager storage unitsor NDMP storage units, or both.

Fibre Channel SAN(optional)

NDMPhost

NDMPhost

For each robot, either a NetBackup media sever or an NDMP server (not both) canhandle robotic control.

Setting up SSO: overviewThis overview includes an outline of the steps for setting up access to a drive thatis shared between NDMP and NetBackup servers.

For a more complete discussion of SSO, refer to the NetBackup Shared StorageGuide.

This procedure assumes the following:

■ That the prerequisites for SSO have been met, as described in the NetBackupShared Storage Guide.

■ That all physical devices, including the NDMP host, are correctly connectedto the network.

■ That NetBackup for NDMP supports the NDMP host.A document that lists supported NAS systems is available.See “NDMP information on the Web” on page 32.The NetBackup NDMP Compatibility List indicates which versions of vendorsoftware support SSO for NDMP. The NAS systems (hardware) do not providethe support; the proper software version provides it.

Using the Shared Storage Option (SSO)Setting up SSO: overview

68

To set up an SSO

1 Configure NetBackup access to the NDMP host.

See “Authorizing access to the NDMP host” on page 40.

2 Verify that the NDMP host can access the required robots and drives.

To verify NDMP host access to the required devices, run the followingcommands on a NetBackup media server that is authorized to access the host:

tpautoconf -verify ndmp_host_name

tpautoconf -probe ndmp_host_name

The -verify option verifies that the NetBackup server can access the NDMPhost. The -probe option lists the devices that are visible to the NDMP host.

3 From the NetBackup Administration Console, use the Device ConfigurationWizard to configure the devices and storage units.

See “Using the Device Configuration Wizard” on page 69.

An NDMP storage unit must be defined for each NDMP host that shares adrive. If all hosts have access to the shared drive(s), the Device ConfigurationWizard can create these storage units automatically.

Using the Device Configuration WizardThe most convenient way to configure devices and storage units for NDMP hosts(with or without SSO) is to use the Device Configuration Wizard.

69Using the Shared Storage Option (SSO)Using the Device Configuration Wizard

To use the Device Configuration wizard

1 In the NetBackup Administration Console, click Configure Storage Devicesto launch the Device Configuration Wizard.

2 Click Next on the Welcome screen. The Device Hosts screen appears.

3 Under Device Hosts, place a check beside the NetBackup media server thataccesses the NDMP host.

4 Click the server name to select it and click Change.

Using the Shared Storage Option (SSO)Using the Device Configuration Wizard

70

5 In the Change Device Host screen, place a check beside NDMP server.

6 Click OK.

7 In the Device Hosts screen, "NDMP" is now listed in the Optional Devices tobe Scanned column for the media server.

8 Click Next to continue.

71Using the Shared Storage Option (SSO)Using the Device Configuration Wizard

9 In the NDMP Hosts screen that shows the NDMP host(s) where you canconfigure devices, click Next to configure the NDMP-attached devices.

10 Follow the screens in the wizard to complete the configuration.

Using the Shared Storage Option (SSO)Using the Device Configuration Wizard

72

Backup and restoreprocedures


■ About NDMP backup

■ Automatic backup of an NDMP policy

■ Performing a manual backup of an NDMP policy

■ Performing a restore from the server

About NDMP backupOnly the administrator can perform NDMP backups and restores on the NetBackupserver (master or media). The NDMP protocol does not allow users to initiate abackup or restore; no NetBackup client software is installed on an NDMP host.

Automatic backup of an NDMP policyInformation is available to help you configure an NDMP policy and set up schedulesfor automatic, unattended backups.

See the NetBackup Administrator’s Guide, Volume I.

Performing a manual backup of an NDMP policyOnly a NetBackup administrator can initiate an NDMP backup. The followingprocedure explains how to perform the backup using the NetBackup AdministrationConsole.

8Chapter

For further information on the NetBackup Administration Console, see theNetBackup Administrator’s Guide, Volume I.

To back up an NDMP policy manually

1 As administrator, start the NetBackup Administration Console on theNetBackup server in the following way:

On Windows: on the Windows Start menu, click Programs > SymantecNetBackup > NetBackup Administration Console.

On UNIX, enter the following:

/usr/openv/netbackup/bin/jnbSA &

2 Click Policies.

3 Right-click the NDMP policy name and select ManualBackup from the pop-upmenu.

4 In the Manual Backup dialog box, select a schedule and then select the clients(NDMP hosts) that you want to back up.

If you do not select any schedules, NetBackup uses the schedule with thehighest retention level. If you do not select any clients, NetBackup backs upall configured NDMP hosts.

5 Click OK to start the backup.

Performing a restore from the serverUser-directed restores of files are not allowed, because no NetBackup clientsoftware is installed on an NDMP host.

The administrator can use the Backup, Archive, and Restore interface on aNetBackup server (master or media server) to restore files to the following: theNDMP host from which they were backed up or to a different NDMP host.

For help with the restore procedure, see the NetBackup online help in theAdministration Console or the NetBackup Backup, Archive, and Restore GettingStarted Guide.

Backup and restore proceduresPerforming a restore from the server

74

To set up the Specify NetBackup Machines and Policy Type dialog for a restore

1 In the Backup, Archive, and Restore interface on a NetBackup server, clickActions > Specify NetBackup Machines and Policy Type.

2 For the server, select the NetBackup master server.

If your configuration has multiple master servers, specify the master serverthat has the policy for the NDMP host that you plan to restore. If the servername is not in the pull-down list, use Edit Server List to add it.

3 For the source and destination clients, select the appropriate NDMP (NAS)hosts.

The destination host must be an NDMP host compatible with the data formatof the source. (The source and destination must be of the same NAS vendortype.)

Warning: An NDMP restore always overwrites existing files.

If the hosts you want are not available in the pull-down, use Edit Client Listto add the client.

4 In the policy type field, select NDMP.

75Backup and restore proceduresPerforming a restore from the server

Backup and restore proceduresPerforming a restore from the server

76

Troubleshooting


■ Sources of information

■ NDMP operating notes and restrictions

■ Notes on DAR

■ Types of logs

■ Using logs

■ Troubleshooting suggestions

■ Troubleshooting media and devices on Windows

■ Troubleshooting media and devices on UNIX

■ Troubleshooting NDMP direct copy

■ Troubleshooting DAR

■ Testing a robot

Sources of informationFor explanations of NetBackup status codes, refer to the NetBackupTroubleshooting Guide.

Troubleshooting information is also available about particular NAS vendors.


9Chapter

NDMP operating notes and restrictionsBefore you try to troubleshoot a suspected problem, review the following operatingnotes:

■ A tape that was created on an NDMP storage unit is in backup format. It cannotbe restored from a non-NDMP storage unit. If you duplicate an NDMP backupimage, the new copy is still in backup format. It cannot be used for restoreson a non-NDMP storage unit.

■ In the Backup Selections list for an NDMP policy, you can include only directorypaths. Wildcards and individual file names are not allowed.

■ You cannot back up files where the path length is greater than 1024 characters.

■ The NDMP protocol uses port 10000 for communication.

■ On UNIX systems, the NetBackup avrd process uses ICMP (Internet ControlMessage Protocol) to ping NDMP hosts to verify network connectivity. Thisprotocol is required for the NetBackup for NDMP product.

■ If backup or restore jobs are running slowly, verify that the network interfacecards (NIC) are set to full duplex. Half duplex often causes poor performance.For assistance viewing and resetting duplex mode for a particular NAS host,consult the documentation that the manufacturer provides. You may be ableto use the ifconfig (or ipconfig) command, as explained in the NetBackupTroubleshooting Guide.

■ Do not perform incremental backups of the same NDMP data from two differentpolicies. Incremental backups performed by one of the policies may beincomplete, because NDMP filers perform level-based incrementals insteadof time-based incrementals. Consider the following example:**from ET 541829

Policy A does a full backup of /vol/vol1 (level 0).

Policy B then does a full backup of /vol/vol1 (level 0). The filer now considers the policyB backup to be the last full (level 0) backup of /vol/vol1.

Policy A does an incremental backup of /vol/vol1 (level 1). The policy A incrementalbackup captures only the data that changed since the full backup that was done bypolicy B. The incremental backup misses any changes that occurred between the policyA full backup and the policy B full backup.

TroubleshootingNDMP operating notes and restrictions

78

Notes on DARNote the following points:

■ DAR can be used when restoring NetBackup 4.5GA or later backups. Startingwith NetBackup 4.5GA, NetBackup stores the required DAR offset informationon each backup.

■ Backups must have been performed with the NetBackup catalog set to binarymode. If backups were made with the catalog set to ASCII mode, the restorescannot use DAR. ASCII mode did not store the required DAR offset informationon each backup. Note that all backups that were made before NetBackup 4.5used ASCII catalog mode.

Note: Starting with NetBackup 6.0, all backups are in binary mode.

■ To use DAR with NetBackup, the NDMP host you want to restore must supportDAR. Some NDMP host vendors do not currently support DAR.

Types of logsNetBackup uses two types of logging: unified logging and legacy logging. Both aredescribed in the "Using Logs and Reports" chapter in the NetBackupTroubleshooting Guide.

Note the following:

■ All unified logs are written to /usr/openv/logs (UNIX) or install_path\logs(Windows). Unlike legacy logging, you do not need to create logging directories.

■ Use the vxlogview command to examine unified logs (see examples in the nextsection):On UNIX: /usr/openv/netbackup/bin/vxlogview

On Windows: install_path\NetBackup\bin\vxlogview

Refer to the NetBackup Troubleshooting Guide for assistance in using thevxlogview command.

See also the vxlogview man page or the NetBackup Commands Guide.

Using logsThe following procedure describes how to use NetBackup logs.

79TroubleshootingNotes on DAR

Note: The legacy and unified logging files can consume a lot of disk space. Deletethe log files when you are finished and set logging to a lower level of detail.

To use the NetBackup logs

1 In the NetBackup Administration Console: expand Host Properties in theleft pane, click on Media Server, and right click on the server name in theright pane.

2 From the pop-up, select Properties, then click Logging and set the Globallogging level to 5.

This increases logging detail to the highest level, for both unified logging andlegacy logging.

3 View the unified logging information in /usr/openv/logs (UNIX) orinstall_path\logs (Windows) for the following processes:

ndmpagent (originator ID 134)

ndmp (originator ID 151)

nbpem (originator ID 116)

nbjm (originator ID 117)

nbrb (originator ID 118)

4 For ndmpagent logs, try the vxlogview command as follows:

/usr/openv/netbackup/bin/vxlogview -I ndmpagent -d T,s,x,p

5 For ndmp logs, try the vxlogview command as follows:

/usr/openv/netbackup/bin/vxlogview -I ndmp -d T,s,x,p

6 On the NetBackup for NDMP server, create bptm, bpbrm, and ndmpagentlegacy debug log folders in the /usr/openv/netbackup/logsdirectory (UNIX)or install_path\NetBackup\logs folder (Windows).

NetBackup writes legacy log files in these directories, if the directories exist.

Troubleshooting suggestionsTry the following:

■ Check the NetBackup All Log Entries report for information about the failedjob.

TroubleshootingTroubleshooting suggestions

80

■ To verify that the appropriate services are running, use one of the following:the NetBackup Activity Monitor, the Windows control panel (on Windowssystems), or the bpps command (UNIX systems).

■ If NDMP host backups terminate with a status code of 154 (storage unitcharacteristics mismatch requests), the problem may be one of the following:

■ Verify that the NetBackup configuration is correct.

■ There may be a conflict between the policy type and storage unit type. (Forexample, if the policy type is Standard and the storage unit is of type NDMP.)

■ If your NDMP backup fails with a status code of 99 (NDMP backup failure), nopaths in your NDMP policy Backup Selections list were backed up. Check theNetBackup All Log Entries report for more information. A possible cause ofthis status is that none of the backup paths exist on the NDMP host.

NDMP backup levelsAt the start of a debug log, you may see an entry titled LEVEL. This entry refersto an environment variable that NetBackup set based on the type of backup. Hereis an example from a bptm log:

08:48:38.816 [22923] <2> write_data_ndmp: backup environment

values:

08:48:38.816 [22923] <2> write_data_ndmp: Environment 1:

TYPE=dump


FILESYSTEM=/vol/vol0/2million


PREFIX=/vol/vol0/2million

08:48:38.817 [22923] <2> write_data_ndmp: Environment 4: LEVEL=0

The NDMP backup level is modeled after UNIX dump levels. The backup level isa number in the range of 0 to 9.

An NDMP backup level of 0 is a full backup. A backup level greater than 0 is anincremental backup of all objects that were modified since the last backup of alower level. For example, level 1 is a backup of all objects that were modified sincethe full backup (level 0). Level 3 is a backup of all objects that were modified sincethe last level 2 incremental.

Table 9-1 NetBackup backup types and corresponding NDMP backup levels

NDMP backup levelsNetBackup backup types

NDMP level 0NetBackup Full

81TroubleshootingTroubleshooting suggestions

Table 9-1 NetBackup backup types and corresponding NDMP backup levels(continued)

NDMP backup levelsNetBackup backup types

NDMP level 1NetBackup Cumulative Incremental

NDMP level (last level + 1, up to 9)

never goes higher than 9

NetBackup Differential Incremental

More information is available on environment variables.

See “About environment variables in the Backup Selections list” on page 50.

Troubleshooting media and devices on WindowsTry the following:

■ For legacy logging, enable debug logging by creating reqlib and daemon

directories in the install_path\Volmgr\debug directory on the NetBackupfor NDMP server.

■ Check the Windows Event Viewer Application log for troubleshooting clues.For more information on the Event Viewer logging option, refer to theNetBackup Troubleshooting Guide.

■ Use the Activity Monitor interface or the Windows control panel to verify thatthe Media and Device Management services are running.

■ Drives can be unexpectedly set to the DOWN state.

This action is due to communication problems between avrd on the NetBackupfor NDMP server and the NDMP server application on the NDMP host. Somepossible causes for the communication problems are:

■ Network cable on the NDMP host was unplugged.

■ NIS (Network Information System) problems on the NetBackup for NDMPserver (NDMP client).

■ The NDMP host was halted for too long.

Note:Whatever the cause, if the avrd connection to the NDMP host fails, the driveis set to DOWN. It is not automatically set to UP when the communication problemis corrected.

TroubleshootingTroubleshooting media and devices on Windows

82

Troubleshooting media and devices on UNIXTry the following:

■ Ensure that syslogd logs debug messages relating to ltid and other deviceprocesses.For more information on syslogd, refer to the NetBackup TroubleshootingGuide.

■ Start ltid with the -v option. Check the system’s syslog for troubleshootingclues.

■ Use vmps to make sure that the appropriate daemons are running.

■ Drives can be unexpectedly set to the DOWN state. This action is due tocommunication problems between avrd on the NetBackup for NDMP serverand the NDMP server application on the NDMP host.Further details are available.See “Troubleshooting media and devices on Windows” on page 82.

Troubleshooting NDMP direct copyWhen NetBackup enables NDMP direct copy for a backup image duplication, theNetBackup progress log includes the message "NDMP Direct Copy will be used."If NDMP direct copy was not enabled for the duplication, no specific messagesabout NDMP direct copy are listed in the progress log. For detailed messages (suchas why NDMP direct copy was not used), consult the legacy debug logs for theadmin log or the bptm log.

Refer to theNetBackupTroubleshootingGuide for information on legacy NetBackuplogs.

Troubleshooting DARTable 9-2 lists messages that may appear in the unified logs for ndmpagent(originator ID 134) on the NetBackup media server. These messages are alsowritten to the progress log.

83TroubleshootingTroubleshooting media and devices on UNIX

Table 9-2 DAR log messages

ExplanationMessage

The number of files being restored is greater thanthe maximum that is allowed (default is 1024).You can either select fewer files for the restore,or increase the DAR maximum Backup Selectionslist count. (Some NDMP host vendors do notsupport increasing the maximum.)

To increase the DAR maximum Backup Selectionslist count, place a "DAR_MAXIMUM_FILE_LIST_COUNT x" entry in the following file. Specifyx as a number greater than 1024.

On UNIX:


On Windows:

install_path\NetBackup\db\config\ndmp.cfg

DAR disabled - number of files n >DAR_MAXIMUM_FILE_LIST_COUNTx

The current NDMP host does not support DAR.data host does not support DARrecovery

DAR information is not available for the file.DAR disabled—continuing restorewithout DAR

The DAR feature can be used when restoring thebackups that NetBackup 4.5GA or later made.Starting with NetBackup 4.5GA, NetBackup storesthe required DAR offset information on eachbackup. For pre-4.5GA NetBackup backups,restores cannot use DAR because the pre-4.5versions did not store DAR offset information.

DAR disabled—backup was performedbefore NB 4.5

The backup was performed with an NDMP hostversion that does not support DAR. Ask the NDMPhost vendor if a later NAS software version isavailable that supports DAR.

DAR disabled—NDMP host did notprovide DAR info during backup

NetBackup determined that the restore wouldtake longer with DAR than without it.

DAR disabled—Exceeded optimal DARparameters for this image size

DAR is automatically disabled when a restore jobspecifies a directory to restore. DAR can be usedwhen restoring files, but not when restoringdirectories.

DAR disabled—Directory DAR notsupported

TroubleshootingTroubleshooting DAR

84

Table 9-2 DAR log messages (continued)

ExplanationMessage

**Not needed, acc to Phil G.

DAR was disabled by adding the entryNDMP_DAR_DISABLED to the following file:

On UNIX:


On Windows:

install_path\NetBackup\db\config\ndmp.cfg

This method of disabling DAR is obsolete. Use theHost Properties dialog box.

See “About enabling or disabling DAR”on page 52.

DAR disabled by DAR config file

DAR was disabled on the Master or Media ServerProperties dialog box.

See “About enabling or disabling DAR”on page 52.

DAR disabled by host parameters

Testing a robotDepending on the type of robot, use the tests in Table 9-3 to exercise the robot.

Table 9-3 Robot types and tests

TestRobot type

tldtestTLD

tl8testTL8

tlhtestTLH

acstestACS

TL8 example for WindowsTo exercise the TL8 robot c2t3l0 that the NDMP host stripes controls, use thefollowing test and commands on Windows:

85TroubleshootingTesting a robot

Note:The drive must be down before you perform this test, or avrdmay interfere.

install_path\Volmgr\bin\tl8test -r stripes:c2t3l0 -d1 stripes:/dev/RMT/0cbn

At the prompt, enter ? for help information.

inquiry (Displays the vendor and product ID. If you get a UNIT ATTENTIONmessage, try the mode command and then continue your testing.)

s s (Checks slot status.)

s d (Checks drive status.)

m s3 d1 (Moves a tape from slot 3 to drive 1.)

m d1 s3 (Moves the tape back to slot 3.)

TLD example for UNIXTo exercise drive 1 in the TLD robot c2t3l0 the NDMP host stripes controls, usethe following commands on UNIX:

/usr/openv/volmgr/bin/tldtest -r stripes:c2t3l0 -d1 stripes:/dev/RMT/Ocbn


inquiry (Displays the Vendor and Product ID. If you get a UNIT ATTENTIONmessage, try the mode command and then continue your testing.)

s s (Checks slot status.)

s d (Checks drive status.)

m s3 d1 (Moves a tape from slot 3 to drive 1.)

unload d1 (Unloads the tape.)

m d1 s3 (Moves the tape back to slot 3.)

TLH example for UNIXTo exercise drive 1 in a TLH robot, use the following command on UNIX:

/usr/openv/volmgr/bin/tlhtest -r /dev/lmcpo -d1 stripes:/dev/RMT/Ocbn

Note that a TLH robot cannot attach directly to the NDMP host; only a TLH drivecan directly attach to the NDMP host.


inv (Inventories the robot.)

TroubleshootingTesting a robot

86

drstat (Shows drive status.)

m media_id drive_name (Moves specified media to the specified drive.)

dm drive_name (Dismounts the tape.)

unload drive_name (Unloads the tape.)

87TroubleshootingTesting a robot

TroubleshootingTesting a robot

88

Using scripts


■ About scripts

■ ndmp_start_notify (UNIX)

■ ndmp_start_notify.cmd (Microsoft Windows)

■ ndmp_end_notify (UNIX)

■ ndmp_end_notify.cmd (Microsoft Windows)

■ ndmp_start_path_notify (UNIX)

■ ndmp_start_path_notify.cmd (Microsoft Windows)

■ ndmp_end_path_notify (UNIX)

■ ndmp_end_path_notify.cmd (Microsoft Windows)

■ ndmp_moving_path_notify (UNIX)

■ ndmp_moving_path_notify.cmd (Microsoft Windows)

About scriptsThis topic explains how to customize the NDMP-specific notify scripts.

NetBackup for NDMP provides the following scripts (commands on Windows) forcollecting information and providing notification of events.

Table 10-1 Scripts to run on the NetBackup for NDMP server

Scripts for WindowsScripts for UNIX

ndmp_start_notify.cmdndmp_start_notify

10Chapter

Table 10-1 Scripts to run on the NetBackup for NDMP server (continued)

Scripts for WindowsScripts for UNIX

ndmp_end_notify.cmdndmp_end_notify

ndmp_start_path_notify.cmdndmp_start_path_notify

ndmp_end_path_notify.cmdndmp_end_path_notify

ndmp_moving_path_notify.cmdndmp_moving_path_notify

The scripts are similar to those already included in your NetBackup serverinstallation. To create the scripts on UNIX, copy the bpstart_notify andbpend_notify scripts from

/usr/openv/netbackup/bin/goodies (UNIX)

to

/usr/openv/netbackup/bin

on the NetBackup for NDMP server. Then rename the copied scripts and modifyas needed.

On Windows, you must create the scripts from scratch.

ndmp_start_notify (UNIX)The UNIX scripts are provided as examples only. You must customize the scriptsbefore using them. For example, the -ne value in the first if statement must bemodified to reflect the number of passed parameters. For the ndmp_start_notifyscript, the -ne value must be set to 5.

On the UNIX media server, NetBackup calls the ndmp_start_notify script eachtime the client starts a backup operation. To use this script, create a script similarto

/usr/openv/netbackup/bin/goodies/bpstart_notify

on the server, and copy it to

/usr/openv/netbackup/bin/ndmp_start_notify

on the UNIX NetBackup for NDMP server. Then, modify the script and ensurethat you have permission to run it.

Using scriptsndmp_start_notify (UNIX)

90

Note: Before you use this script, make sure that you can run it by using other onthe media server. Run chmod 755 script_name, where script_name is the nameof the script.

The ndmp_start_notify script runs each time a backup starts and after the tapehas been positioned. This script must exit with a status of 0 for the calling programto continue and for the backup to proceed. A nonzero status causes the clientbackup to exit with a status of ndmp_start_notify failed.

If the /usr/openv/netbackup/bin/ndmp_start_notify script exists, it runs inthe foreground. The bptmprocess that is on the NetBackup for NDMP server waitsfor it to complete before continuing. Any commands in the script that do not endwith an & character run serially.

The server expects the client to respond with a continue message within theperiod of time that the NetBackup CLIENT_READ_TIMEOUT option on the serverspecifies.

The default for CLIENT_READ_TIMEOUT is 300. If the script needs more time than300 seconds, increase the value to allow more time.

NetBackup passes the following parameters to the script:

Table 10-2 Script parameters: ndmp_start_notify (UNIX)

DescriptionParameter

Name of the NDMP host.$1

Policy name from the NetBackup catalog.$2

Schedule name from the NetBackup catalog.$3

One of the following:

FULL

INCR (differential incremental)

CINC (cumulative incremental)

$4

The NetBackup status code for the operation.$5

For example:

ndmp_start_notify freddie cd4000s fulls FULL 0

ndmp_start_notify danr cd4000s incrementals INCR 0

ndmp_start_notify hare cd4000s fulls FULL 0

91Using scriptsndmp_start_notify (UNIX)

To create an ndmp_start_notify script for a specific policy or policy and schedulecombination, create script files with a.policynameor.policyname.schedulenamesuffix. In the following two examples of script names, the policy is namedproduction and the schedule is named fulls:

/usr/openv/netbackup/bin/ndmp_start_notify.production

/usr/openv/netbackup/bin/ndmp_start_notify.production.fulls

The first script affects all scheduled backups in the policy that is namedproduction. The second script affects scheduled backups in the policy that isnamed production only when the schedule is named fulls.

Note: For a given backup, NetBackup uses only one ndmp_start_notify scriptand that is the one with the most specific name. For example, if there are bothndmp_start_notify.production and ndmp_start_notify.production.fulls

scripts, NetBackup uses only ndmp_start_notify.production.fulls.

The ndmp_start_notify script can use the following environment variables:

BACKUPID

UNIXBACKUPTIME

BACKUPTIME

The NetBackup bptm process creates these variables. The following are examplesof the strings that are available to the script for use in recording informationabout a backup:

BACKUPID=freddie_0857340526

UNIXBACKUPTIME=0857340526

BACKUPTIME=Sun Mar 2 16:08:46 1997

ndmp_start_notify.cmd (Microsoft Windows)For Windows NetBackup for NDMP media servers, you can create the batch scriptsthat provide notification whenever the client starts a backup. These scripts mustreside on the media server in the following directory:

install_path\NetBackup\bin

Where install_path is the directory where NetBackup is installed.

You can createndmp_start_notify scripts that provide notification for all backupsor only for backups of a specific policy or schedule. The ndmp_start_notify scriptruns each time a backup starts and after the tape is positioned.

Using scriptsndmp_start_notify.cmd (Microsoft Windows)

92

To create a script that applies to all backups, name the script:

install_path\netbackup\bin\ndmp_start_notify.cmd

To create an ndmp_start_notify script that applies only to a specific policy orpolicy and schedule combination, add a .policyname or.policyname.schedulename suffix to the script name. The following are twoexamples:

■ The following script applies only to a policy named days:

install_path\netbackup\bin\ndmp_start_notify.days.cmd

■ The following script applies only to a schedule that is named fulls, which isin a policy named days:

install_path\netbackup\bin\ndmp_start_notify.days.fulls.cmd

The first script affects all scheduled backups in the policy named days. The secondscript affects scheduled backups in the policy named days only when the scheduleis named fulls.

For a given backup, NetBackup calls only one ndmp_start_notify script andchecks for them in the following order:

ndmp_start_notify.policy.schedule.cmd

ndmp_start_notify.policy.cmd

ndmp_start_notify.cmd

For example, if there are both ndmp_start_notify.policy.cmd andndmp_start_notify.policy.schedule.cmd scripts, NetBackup uses only thendmp_start_notify.policy.schedule.cmd script.

Note: If you also use ndmp_end_notify scripts, they can provide a different levelof notification than the ndmp_start_notify scripts. For example, if you had oneof each, they could be ndmp_start_notify.policy.cmd andndmp_end_notify.policy.schedule.cmd.

When the backup starts, NetBackup passes the following parameters to the script:

Table 10-3 Script parameters: ndmp_start_notify.cmd (Microsoft Windows)


Name of the client from the NetBackup catalog.%1

93Using scriptsndmp_start_notify.cmd (Microsoft Windows)

Table 10-3 Script parameters: ndmp_start_notify.cmd (Microsoft Windows)(continued)


Policy name from the NetBackup catalog.%2

Schedule name from the NetBackup catalog.%3


FULLINCRCINC

%4

Status of the operation is always 0 for bpstart_notify.%5

Results file that NetBackup checks for a return code from the script. NetBackup uses %6 to passthe file name and then expects the script to create the file in the same directory as the script.

If the script applies to a specific policy and schedule, the results file must be named

install_path\netbackup\bin\NDMP_START_NOTIFY_RES.policy.schedule

If the script applies to a specific policy, the results file must be named

install_path\netbackup\bin\NDMP_START_NOTIFY_RES.policy

If the script applies to all backups, the results file must be named

install_path\netbackup\bin\NDMP_START_NOTIFY_RES

An echo 0> %6 statement is one way for the script to create the file.

NetBackup deletes the existing results file before it calls the script. After the script runs,NetBackup checks the new results file for the status. The status must be 0 for the script to beconsidered successful. If the results file does not exist, NetBackup assumes that the script wassuccessful.

%6

The server expects the client to respond with a continue message within theperiod of time that the NetBackup CLIENT_READ_TIMEOUT option on the serverspecifies. The default is 300 seconds. If the script needs more than 300 seconds,increase the value to allow more time.

ndmp_end_notify (UNIX)The ndmp_end_notify script is run at the end of the backup. The backup does notwait for the script to complete.

Using scriptsndmp_end_notify (UNIX)

94

Note: Before you use this script, make sure you can run it by using other on themedia server. Run chmod 755 script_name, where script_name is the name ofthe script.

The UNIX scripts are provided as examples only. You must customize the scriptsbefore using them. For example, the -ne value in the first if statement must bemodified to reflect the number of passed parameters. For the ndmp_end_notifyscript, the -ne value must be set to 5.

For a UNIX media server, if you need notification whenever the NDMP hostcompletes a backup, copy

/usr/openv/netbackup/bin/goodies/bpend_notify

from the server, to

/usr/openv/netbackup/bin/ndmp_end_notify

on the UNIX NetBackup for NDMP host. Then, modify the script and ensure thatyou have permission to run it.

The ndmp_end_notify script runs each time a backup completes.

NetBackup passes the following parameters to the ndmp_end_notify script:

Table 10-4 Script parameters: ndmp_end_notify (UNIX)


Name of the client from the NetBackup catalog.$1




FULL



$4

Exit code from bptm.$5

For example:

ndmp_end_notify freddie cd4000s fulls FULL 0

ndmp_end_notify danr cd4000s incrementals INCR 73

95Using scriptsndmp_end_notify (UNIX)

To create an ndmp_end_notify script for a specific policy or policy and schedulecombination, create script files with a.policynameor.policyname.schedulenamesuffix. In the following two examples of script names, the policy is namedproduction and the schedule is named fulls:

/usr/openv/netbackup/bin/ndmp_end_notify.production

/usr/openv/netbackup/bin/ndmp_end_notify.production.fulls


Note: For a given backup, NetBackup uses only one ndmp_end_notify script andthat is the one with the most specific name. For example, if there are bothndmp_end_notify.production andndmp_end_notify.production.fulls scripts,NetBackup uses only ndmp_end_notify.production.fulls.

The ndmp_end_notify script can use the following environment variables:

BACKUPID

UNIXBACKUPTIME

BACKUPTIME





ndmp_end_notify.cmd (Microsoft Windows)For Windows media servers, you can create the batch scripts that providenotification whenever the client completes a backup. These scripts must resideon the media server in the same directory as the NetBackup binaries:



You can create ndmp_end_notify scripts that provide notification for all backupsor only for backups of a specific policy or schedule.

To create an ndmp_end_notify script that applies to all backups, name the script:

Using scriptsndmp_end_notify.cmd (Microsoft Windows)

96

install_path\netbackup\bin\ndmp_end_notify.cmd

To create a script that applies only to a specific policy or policy and schedulecombination, add a .policyname or .policyname.schedulename suffix to thescript name. The following are two examples:


install_path\netbackup\bin\ndmp_end_notify.days.cmd


install_path\netbackup\bin\ndmp_end_notify.days.fulls.cmd


For a given backup, NetBackup calls only one ndmp_end_notify script and checksfor them in the following order:

ndmp_end_notify.policy.schedule.cmd

ndmp_end_notify.policy.cmd

ndmp_end_notify.cmd

For example, if there are both ndmp_end_notify.policy.cmd andndmp_end_notify.policy.schedule.cmd scripts, NetBackup uses onlyndmp_end_notify.policy.schedule.cmd.

Note: If you also usendmp_start_notify scripts, they can provide a different levelof notification than the ndmp_end_notify scripts. For example, if you had one ofeach, they could be ndmp_start_notify.policy.cmd andndmp_end_notify.policy.schedule.cmd.

When the backup completes, NetBackup passes the following parameters to thescript:

Table 10-5 Script parameters: ndmp_end_notify.cmd (Microsoft Windows)




97Using scriptsndmp_end_notify.cmd (Microsoft Windows)

Table 10-5 Script parameters: ndmp_end_notify.cmd (Microsoft Windows)(continued)




FULLINCRCINC

%4

Status of the operation. It is the same as the status sent to the NetBackup server. This statusis 0 for successful backups and 1 for partially successful backups. If an error occurs, the statusis the value associated with that error.

%5

Note: The following file is not checked at the end of a backup.



install_path\netbackup\bin\NDMP_END_NOTIFY_RES.policy.schedule


install_path\netbackup\bin\NDMP_END_NOTIFY_RES.policy


install_path\netbackup\bin\NDMP_END_NOTIFY_RES



%6

ndmp_start_path_notify (UNIX)The UNIX scripts are provided as examples only. You must customize the scriptsbefore using them. For example, the -ne value in the first if statement must bemodified to reflect the number of passed parameters. For thendmp_start_path_notify script, the -ne value must be set to 7.

To use this script, create a script similar to


Using scriptsndmp_start_path_notify (UNIX)

98


/usr/openv/netbackup/bin/ndmp_start_path_notify


On the UNIX media server, the ndmp_start_path_notify script runs before thebackup process is issued to the NAS machine. This script must exit with a statusof 0 for the calling program to continue and for the backup to proceed. A nonzerostatus causes the client backup to exit with a status of 99 (NDMP backup failure).


If the /usr/openv/netbackup/bin/ndmp_start_path_notify script exists, it runsin the foreground. The bptm process on the NetBackup for NDMP server waits forit to complete before continuing. Any commands in the script that do not endwith an & character run serially.


The default for CLIENT_READ_TIMEOUT is 300. If the script needs more time than300 seconds, increase the value to allow more time.


Table 10-6 Script parameters: ndmp_start_path_notify (UNIX)






FULL



$4


99Using scriptsndmp_start_path_notify (UNIX)

Table 10-6 Script parameters: ndmp_start_path_notify (UNIX) (continued)


Not used.$6

The path being backed up.$7

For example:

ndmp_start_path_notify freddie cd4000s fulls FULL

ndmp_start_path_notify danr cd4000s incrementals INCR

ndmp_start_path_notify hare cd4000s fulls FULL

To create an ndmp_start_path_notify script for a specific policy or policy andschedule combination, create script files with a .policyname or.policyname.schedulename suffix. In the following two examples of script names,the policy is named production and the schedule is named fulls:

/usr/openv/netbackup/bin/ndmp_start_path_notify.production

/usr/openv/netbackup/bin/ndmp_start_path_notify.production.fulls


Note: For a given backup, NetBackup uses only one ndmp_start_path_notify

script and that is the one with the most specific name. For example, if there areboth ndmp_start_path_notify.production andndmp_start_path_notify.production.fulls scripts, NetBackup uses onlyndmp_start_path_notify.production.fulls.

The ndmp_start_path_notify script can use the following environment variables:

BACKUPID

UNIXBACKUPTIME

BACKUPTIME





Using scriptsndmp_start_path_notify (UNIX)

100

ndmp_start_path_notify.cmd (Microsoft Windows)For Windows media servers, you can create the batch scripts that providenotification before the backup process is issued to the NAS machine. These scriptsmust reside on the media server in the same directory as the NetBackup binaries:



You can create ndmp_start_path_notify scripts that provide notification for allbackups or only for backups of a specific policy or schedule.

To create an ndmp_start_path_notify script that applies to all backups, namethe script:

install_path\netbackup\bin\ndmp_start_path_notify.cmd



install_path\netbackup\bin\ndmp_start_path_notify.days.cmd

■ The following script applies only to a schedule that is named fulls, which ina policy named days:

install_path\netbackup\bin\ndmp_start_path_notify.days.fulls.cmd


For a given backup, NetBackup calls only one ndmp_start_path_notify scriptand checks for them in the following order:

ndmp_start_path_notify.policy.schedule.cmd

ndmp_start_path_notify.policy.cmd

ndmp_start_path_notify.cmd

For example, if there are both ndmp_start_path_notify.policy.cmd andndmp_start_path_notify.policy.schedule.cmd scripts, NetBackup uses onlyndmp_start_path_notify.policy.schedule.cmd.

101Using scriptsndmp_start_path_notify.cmd (Microsoft Windows)

Note: If you also use ndmp_start_notify scripts, they can provide a different levelof notification than the ndmp_start_path_notify scripts. For example, if you hadone of each, they could be ndmp_start_notify.policy.cmd andndmp_start_path_notify.policy.schedule.cmd.

When the backup starts, NetBackup passes the following parameters to the script:

Table 10-7 Script parameters: ndmp_start_path_notify.cmd (Microsoft Windows)






FULLINCRCINC

%4


%5



install_path\netbackup\bin\NDMP_START_PATH_NOTIFY_RES.policy.schedule


install_path\netbackup\bin\NDMP_START_PATH_NOTIFY_RES.policy


install_path\netbackup\bin\NDMP_START_PATH_NOTIFY_RES



%6

Pathname being backed up.%7

Using scriptsndmp_start_path_notify.cmd (Microsoft Windows)

102

ndmp_end_path_notify (UNIX)The UNIX scripts are provided as examples only. You must customize the scriptsbefore using them. For example, the -ne value in the first if statement must bemodified to reflect the number of passed parameters. For thendmp_end_path_notify script, the -ne value must be set to 7.


For a UNIX media server, if you need notification whenever the NDMP hostcompletes a backup, copy

/usr/openv/netbackup/bin/goodies/bpend_notify

from the server, to

/usr/openv/netbackup/bin/ndmp_end_path_notify

on the UNIX NetBackup for NDMP host. Then, modify the script and ensure thatyou have permission to run it.

The ndmp_end_path_notify script runs after the NAS machine has informedNetBackup that it has completed sending data.

NetBackup passes the following parameters to the ndmp_end_notify script:

Table 10-8 Script parameters: ndmp_end_path_notify (UNIX)


Name of the client from the NetBackup catalog.$1




FULL



$4

Exit code from bptm.$5

Not used.$6

103Using scriptsndmp_end_path_notify (UNIX)

Table 10-8 Script parameters: ndmp_end_path_notify (UNIX) (continued)



For example:

ndmp_end_path_notify freddie cd4000s fulls FULL 0

ndmp_end_path_notify danr cd4000s incrementals INCR 73

To create an ndmp_end_path_notify script for a specific policy or policy andschedule combination, create script files with a .policyname or.policyname.schedulename suffix. In the following two examples of script names,the policy is named production and the schedule is named fulls:

/usr/openv/netbackup/bin/ndmp_end_path_notify.production

/usr/openv/netbackup/bin/ndmp_end_path_notify.production.fulls


Note: For a given backup, NetBackup uses only one ndmp_end_path_notify scriptand that is the one with the most specific name. For example, if there are bothndmp_end_path_notify.production andndmp_end_path_notify.production.fulls scripts, NetBackup uses onlyndmp_end_path_notify.production.fulls.

The ndmp_end_path_notify script can use the following environment variables:

BACKUPID

UNIXBACKUPTIME

BACKUPTIME





Using scriptsndmp_end_path_notify (UNIX)

104

ndmp_end_path_notify.cmd (Microsoft Windows)For Windows media servers, you can create the batch scripts that providenotification whenever the client is finished writing to tape. These scripts mustreside on the media server in the same directory as the NetBackup binaries:



You can create ndmp_end_path_notify scripts that provide notification for allbackups or only for backups of a specific policy or schedule.

To create an ndmp_end_path_notify script that applies to all backups, name thescript:

install_path\netbackup\bin\ndmp_end_path_notify.cmd



install_path\netbackup\bin\ndmp_end_path_notify.days.cmd


install_path\netbackup\bin\ndmp_end_path_notify.days.fulls.

cmd


For a given backup, NetBackup calls only one ndmp_end_path_notify script andchecks for them in the following order:

ndmp_end_path_notify.policy.schedule.cmd

ndmp_end_path_notify.policy.cmd

ndmp_end_path_notify.cmd

For example, if there are both ndmp_end_path_notify.policy.cmd andndmp_end_path_notify.policy.schedule.cmd scripts, NetBackup uses onlyndmp_end_path_notify.policy.schedule.cmd.

105Using scriptsndmp_end_path_notify.cmd (Microsoft Windows)

Note: If you also use ndmp_end_notify scripts, they can provide a different levelof notification than the ndmp_end_path_notify scripts. For example, if you hadone of each, they could be ndmp_end_notify.policy.cmd andndmp_end_path_notify.policy.schedule.cmd.

When the backup completes, NetBackup passes the following parameters to thescript:

Table 10-9 Script parameters: ndmp_end_path_notify.cmd (Microsoft Windows)






FULLINCRCINC

%4


%5

Using scriptsndmp_end_path_notify.cmd (Microsoft Windows)

106

Table 10-9 Script parameters: ndmp_end_path_notify.cmd (Microsoft Windows)(continued)


Note: The following file is not checked when using ndmp_end_path_notify.



install_path\netbackup\bin\NDMP_END_PATH_NOTIFY_RES.policy.schedule


install_path\netbackup\bin\NDMP_END_PATH_NOTIFY_RES.policy


install_path\netbackup\bin\NDMP_END_PATH_NOTIFY_RES



%6


ndmp_moving_path_notify (UNIX)The UNIX scripts are provided as examples only. You must customize the scriptsbefore using them. For example, the -ne value in the first if statement must bemodified to reflect the number of passed parameters. For thendmp_moving_path_notify script, the -ne value must be set to 7.

To use this script, create a script similar to



/usr/openv/netbackup/bin/ndmp_moving_path_notify


On UNIX media servers, the ndmp_moving_path_notify script runs after thebackup process sends data to NetBackup.

107Using scriptsndmp_moving_path_notify (UNIX)

Note:Before you use this script, make sure you can run it using other on the mediaserver. Run chmod 755 script_name, where script_name is the name of the script.

If the /usr/openv/netbackup/bin/ndmp_moving_path_notify script exists, itruns in the foreground. The bptm process that is on the NetBackup for NDMPserver waits for it to complete before continuing. Any commands in the scriptthat do not end with an & character run serially.


The default for CLIENT_READ_TIMEOUT is 300 seconds. If the script needs morethan 300 seconds, increase the value to allow more time.


Table 10-10 Script parameters: ndmp_moving_path_notify (UNIX)




Schedule name from the NetBackup catalog$3


FULL



$4


Not used.$6


For example:

ndmp_moving_path_notify freddie cd4000s fulls FULL

ndmp_moving_path_notify danr cd4000s incrementals INCR

ndmp_moving_path_notify hare cd4000s fulls FULL

To create an ndmp_moving_path_notify script for a specific policy or policy andschedule combination, create script files with a .policyname or

Using scriptsndmp_moving_path_notify (UNIX)

108

.policyname.schedulename suffix. In the following two examples of script names,the policy is named production and the schedule is named fulls:

/usr/openv/netbackup/bin/ndmp_moving_path_notify.production

/usr/openv/netbackup/bin/ndmp_moving_path_notify.production.fulls


Note: For a given backup, NetBackup uses only one ndmp_moving_path_notify

script and that is the one with the most specific name. For example, if there areboth ndmp_moving_path_notify.production andndmp_moving_path_notify.production.fulls scripts, NetBackup uses onlyndmp_moving_path_notify.production.fulls.

Thendmp_moving_path_notify script can use the following environment variables:

BACKUPID

UNIXBACKUPTIME

BACKUPTIME





ndmp_moving_path_notify.cmd (MicrosoftWindows)For Windows media servers, you can create the batch scripts that providenotification whenever the NAS machine starts sending data. These scripts mustreside on the media server in the same directory as the NetBackup binaries:



You can create ndmp_moving_path_notify scripts that provide notification forall backups or only for backups of a specific policy or schedule.

To create an ndmp_moving_path_notify script that applies to all backups, namethe script:

109Using scriptsndmp_moving_path_notify.cmd (Microsoft Windows)

install_path\netbackup\bin\ndmp_moving_path_notify.cmd



install_path\netbackup\bin\ndmp_moving_path_notify.days.cmd


install_path\netbackup\bin\ndmp_moving_path_notify.days.ful

ls.cmd


For a given backup, NetBackup calls only one ndmp_moving_path_notify scriptand checks for them in the following order:

ndmp_moving_path_notify.policy.schedule.cmd

ndmp_moving_path_notify.policy.cmd

ndmp_moving_path_notify.cmd

For example, if there are both ndmp_moving_path_notify.policy.cmd andndmp_moving_path_notify.policy.schedule.cmd scripts, NetBackup uses onlyndmp_moving_path_notify.policy.schedule.cmd.

Note: If you also use ndmp_start_notify scripts, they can provide a different levelof notification than the ndmp_moving_path_notify scripts. For example, if youhad one of each, they could be ndmp_start_notify.policy.cmd andndmp_moving_path_notify.policy.schedule.cmd.

When the backup starts, NetBackup passes the following parameters to the script.

Table 10-11 Script parameters: ndmp_moving_path_notify.cmd (MicrosoftWindows)



Using scriptsndmp_moving_path_notify.cmd (Microsoft Windows)

110

Table 10-11 Script parameters: ndmp_moving_path_notify.cmd (MicrosoftWindows) (continued)





FULLINCRCINC

%4


%5

Note: The following is not checked when using ndmp_moving_path_notify.



install_path\netbackup\bin\NDMP_END_NOTIFY_RES.policy.schedule


install_path\netbackup\bin\NDMP_END_NOTIFY_RES.policy


install_path\netbackup\bin\NDMP_END_NOTIFY_RES



%6


111Using scriptsndmp_moving_path_notify.cmd (Microsoft Windows)

Using scriptsndmp_moving_path_notify.cmd (Microsoft Windows)

112

Symbols10000

port (used by NDMP) 783pc.conf file 32

Aacstest 85Activity Monitor interface 82Add Drive dialog 45, 48Add Robot dialog 44adding

drives 45Media Manager storage unit 57NDMP storage units 47robots 41volumes 47

authorizationNDMP user and password 40

auto discovery of devices 12, 39, 69avrd 78

Bbackup

automatic 73format 78level (NDMP vs. NetBackup) 81local vs. three-way 12, 16, 18, 24manual

of NDMP policy 73ndmp_end_notify script

UNIX 95Windows 96

ndmp_end_path_notify scriptUNIX 103Windows 105

ndmp_moving_path_notify scriptUNIX 107Windows 109

ndmp_start_notify scriptWindows 92

backup (continued)ndmp_start_path_notify script

UNIX 99Windows 101

overview 24procedure 73three-way

configuring for 41types allowed 52

Backup Selections list 50

Cclient list 49clustering 14, 53compatibility list

for NDMP 32configuration

add Media Manager storage unit 57add NDMP storage unit 47add volumes 47adding drives/robots 41Backup Selections list 50check devices 46client list 49drive

for NDMP-attached host 45for clustering 53general policy attributes 49NDMP policy 48policy storage unit 49policy type 49robot 42schedules 49, 52testing 54

control panelWindows 82

DDAR 13, 27

defined 14how to turn on/off 52

Index

data mover 32debug logs 80deinstallation

server 38Device Configuration Wizard 12, 39, 69Device Monitor 46devices

troubleshooting 82–83different client restore 15Direct Access Recovery (see DAR) 13direct copy

NDMP 28, 59, 83drives

addingfor NDMP-attached host 45

configuring 41duplex mode and performance 78

Eenvironment variables

in Backup Selections list 50exclude

filesusing SET directive 50

listusing 50

Ffail over 53file list 50file names (not allowed in Backup Selections list) 50,

78

HHardware Compatibility List 32High Availability 14, 53

IICMP protocol 78installation 35

deinstallation 38prerequisites 35

instant recovery 13

JjnbSA 74

LLEVEL (NDMP backup) 81log directories 80, 82–83ltid

restarting 46

Mmover.conf file 32

NNAS snapshot 13, 39–40, 56nbjm 80nbpem 80nbrb 80NDMP

access web info 32backup

manual 73client

definition of 14client type 49direct copy 13, 28, 59, 83

how to configure 60licensing 60VTL license 31

hostdefinition of 15

LEVELrelated to NetBackup backups 81

Multiplexing 33multiplexing

definition of 15policy

adding 48attributes 49clients 49files 50schedules 49, 52

policy storage unit attributeconfiguration 49

policy typeconfiguration 49overview 20

protocol 14, 16, 78restore 74restrictions 78schedule 49

Index114

NDMP (continued)server application

definition of 15storage unit

adding 47definition of 15

to media server 14, 41, 49, 55how to configure 56

ndmp logging 80NDMP Multiplexing 33NDMP to media server 12, 19ndmp_end_notify script

UNIX 95Windows 96

ndmp_end_path_notify scriptUNIX 103Windows 105

ndmp_moving_path_notify scriptUNIX 107Windows 109

ndmp_start_notify scriptWindows 92

ndmp_start_path_notify scriptUNIX 99Windows 101

ndmpagentlegacy debug log 80unified logging 80

NetBackup Administration Console 74NetBackup for NDMP

configuration 39definition 12features 12installation 35server

definition 14troubleshooting 80

network interface cards 78NIC cards and full duplex 78notification scripts 89

Ooff-host backup

with data mover 32on demand storage unit 48operating notes and restrictions 78Override policy storage unit

setting 52overwriting files 75

Ppassword

verifying 41, 47path length limit 78path-based history 13peripherals (latest info on web) 32ping 78point-in-time snapshots 13policy

attributes 49port 10000 (used by NDMP) 78protocol supported (NDMP) 12, 39

Rremote NDMP 55reserved environment variables 50restart

device manager 44Media Manager device daemon 46

restorelocal vs. three-way 16, 18, 24overview 26overwriting files 75procedure 74three-way 26to different client 15, 20

restrictionsNetBackup for NDMP 78

robotadding 41supported types 21test device configuration 85

robot connectionverifying 47

Robot Control Hostfor volume 47

robotsconfiguring 41

Sschedules 49, 52scripts

notification 89SET directive 50–51Shared Storage Option (see SSO) 68Snapshot Client 13

access web info 32snapshots 13

115Index

SSO 13configuration overview 68

storage devicesauto discovery 12, 39

storage unitadding 47media manager type 55NDMP type

overview 21specify for NDMP policy 49

support web site 32supported robots 21

Ttape libraries supported 21tape server 18terminology

NetBackup for NDMP 14testing configuration 54third-party copy device 32three-way backup 16

configuring for 41tl8test 85tldtest 85tlhtest 85–86tpautoconf 47, 69type

of backup allowed 52of policy 49

Uunified logging 80uninstalling NetBackup 38user-directed

backups and archives 20not allowed 73

restoresnot allowed 74

Vvariables

environment 50vendors (latest info on) 32verifying NDMP password 41version supported (NDMP) 12, 39Virtual tape Library

see VTL 13Virtual Tape Option license 31

volumesadding 47

VTL 13, 28, 59, 83license 31licensing 60

vxlogview 79

Wweb access

to NDMP info 32to Snapshot Client info 32

wildcardsin Backup Selections list 50, 78

Windows control panel 82

Index116

Download - Symantec NetBackup for NDMPAdministrator'sGuide 3 Configuring NDMP backup to NDMP-attached devices 39 About configuring NDMP-attached devices 39 Authorizing access to the NDMP host

Top Related