Veritas NetBackup™ for NDMP

Administrator’s Guide

UNIX, Windows, Linux

Release 6.5

12308312
Veritas NetBackup
Administrator’s Guide
Copyright © 2002 - 2007 Symantec Corporation. All rights reserved.

NetBackup 6.5

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

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

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

THIS DOCUMENTATION IS PROVIDED “AS IS” AND ALL EXPRESS OR IMPLIED

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

The Licensed Software and Documentation are deemed to be “commercial computer

software” and “commercial computer software documentation” as defined in FAR
Sections 12.212 and DFARS Section 227.7202.

Symantec Corporation

20330 Stevens Creek Blvd.

Cupertino, CA 95014

www.symantec.com

Printed in the United States of America.

Third-party legal notices

Third-party software may be recommended, distributed, embedded, or bundled

with this Symantec product. Such third-party software is licensed separately by
its copyright holder. All third-party copyrights associated with this product are
listed in the accompanying release notes.

Licensing and registration

Veritas NetBackup is a licensed product. See the NetBackup Installation Guide
for license installation instructions.

Technical support
For technical assistance, visit http://entsupport.symantec.com and select phone
or email support. Use the Knowledge Base search feature to access resources
such as TechNotes, product alerts, software downloads, hardware compatibility
lists, and our customer email notification service.
 Contents

Chapter 1 Introduction to NetBackup for NDMP

NetBackup for NDMP features ...........................................................................10

NetBackup for NDMP terminology ...................................................................12

Network data management protocol (NDMP) .................................................14

Types of NDMP backup .......................................................................................15

NDMP local backup ......................................................................................15

NDMP three-way backup ............................................................................16

Backup to Media Manager storage units (remote NDMP) .....................17

NDMP policies ......................................................................................................18

Storage units .........................................................................................................19

NDMP Storage units ....................................................................................19

Media Manager storage units .....................................................................19

Assigning tape drives to different hosts ..................................................19

NDMP backup process .........................................................................................22

NDMP restore process .........................................................................................24

Direct access recovery (DAR) .............................................................................26

NDMP direct copy with VTL ...............................................................................26

NDMP direct copy without VTL .................................................................28

NDMP direct copy: notes and limitations ................................................29

NDMP information on the Web .........................................................................29

Snapshot Client Assistance ................................................................................30

Chapter 2 Installing NetBackup for NDMP

Installation notes .................................................................................................31

Installing on UNIX servers .................................................................................32

Installing on Windows servers ..........................................................................33

Uninstalling NetBackup for NDMP ...................................................................34

Chapter 3 Configuring NDMP backup to NDMP-attached devices

Authorizing access to the NDMP host ..............................................................36

Access for three-way backups and remote NDMP ..................................37

Media and Device Management configuration ...............................................38

Adding a robot directly attached to an NDMP host ................................38

Adding a drive ..............................................................................................41

Verifying NDMP password and robot connection ..........................................43

6 Contents

Adding NDMP storage units .............................................................................. 44

Creating an NDMP policy ................................................................................... 46

Enabling or disabling DAR ................................................................................. 49

Disabling DAR for file and directory restores ......................................... 49

Disabling DAR for directory restores only .............................................. 49

Setting up clustering ........................................................................................... 50

Post-installation changes ........................................................................... 50

Testing an NDMP configuration ....................................................................... 51

Chapter 4 Configuring NDMP backup to NetBackup media servers

(remote NDMP)
Overview ............................................................................................................... 54

Configuring NDMP backup to Media Manager storage units ....................... 54

Chapter 5 Configuring NDMP direct copy

NDMP direct copy ................................................................................................ 58

Prerequisites ................................................................................................. 58

How to configure NDMP direct copy ........................................................ 58

Using NDMP direct copy .................................................................................... 59

Requirements ............................................................................................... 59

Initiate NDMP direct copy with the Administration Console ............... 60

Chapter 6 Using the Shared Storage Option (SSO)

Shared Storage Option (SSO): diagram ............................................................ 62

Setting up SSO: overview ................................................................................... 63

Using the Device Configuration Wizard .......................................................... 64

Chapter 7 Backup and restore procedures

Performing an NDMP backup ............................................................................ 68

Automatic backup of an NDMP policy ...................................................... 68

Manual backup of an NDMP policy ........................................................... 68

Performing a restore from the server .............................................................. 69

Chapter 8 Troubleshooting
NDMP operating notes and restrictions .......................................................... 72

Troubleshooting NetBackup .............................................................................. 73

Types of logs ................................................................................................. 73

Troubleshooting steps ................................................................................ 73

Troubleshooting media and devices on Windows .......................................... 75

Troubleshooting media and devices on UNIX ................................................. 76

Troubleshooting NDMP direct copy ................................................................. 76

 Contents 7

Troubleshooting DAR ..........................................................................................76

Testing a robot .....................................................................................................78

Chapter 9 Using scripts

ndmp_start_notify (UNIX) ..........................................................................82

ndmp_start_notify.cmd (Microsoft Windows) ........................................84

ndmp_end_notify (UNIX) ............................................................................86

ndmp_end_notify.cmd (Microsoft Windows) ..........................................88

ndmp_start_path_notify (UNIX) ................................................................90

ndmp_start_path_notify.cmd (Microsoft Windows) ..............................92

ndmp_end_path_notify (UNIX) ..................................................................94

ndmp_end_path_notify.cmd (Microsoft Windows) ................................96

ndmp_moving_path_notify (UNIX) ...........................................................98

ndmp_moving_path_notify.cmd (Microsoft Windows) .......................100

Index 103

8
Contents
 Chapter 1
Introduction to NetBackup
for NDMP
NetBackup for NDMP is an optional NetBackup application. It enables
NetBackup to use the Network Data Management Protocol (NDMP) to initiate
and control backups and restores of Network Attached Storage (NAS) systems.
This chapter contains the following topics.
■ 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
10 Introduction to NetBackup for NDMP
NetBackup for NDMP features

NetBackup for NDMP features

NetBackup for NDMP includes the following features:

■ Support for NDMP protocol versions V2, V3, and V4.
■ Centralized backup-policy management
Scheduling, catalog management, and other backup tasks are managed
from a NetBackup master server. NetBackup for NDMP can be installed on a
NetBackup master or media server.
■ Device and media management
NetBackup software provides complete management and control of the
devices and media that are used for backups and restores of NDMP hosts.
The NetBackup Device Configuration wizard discovers and configures the
storage devices that are attached to an NDMP host (requires NDMP protocol
versions V3 or V4). Note that wizard-based discovery depends upon a
number of device-specific features, such as SCSI inquiry and serialization,
which some NAS vendors may not support.
■ High speed local backup of NDMP hosts
Backup data travels between the disk and tape drives that are directly
attached to the same NDMP host. This transfer provides high-speed backup
without impairing network throughput.
■ Backup of network-attached NDMP hosts to a tape device on another NDMP
host or to advanced tape libraries with an embedded NDMP server.
Backup data travels across the network, from a disk on an NDMP host to
tape on another NDMP host. This backup is referred to as three-way backup.
This data movement option requires support from the NAS/NDMP host.
■ Backup of a network-attached NDMP host to a tape device on a NetBackup
media server. This backup is a form of three-way backup also known as
remote NDMP. This feature supports NDMP versions V2, V3, and V4 on the
NDMP hosts.
■ Shared tape libraries
Tape libraries can be shared between NDMP hosts and NetBackup servers,
or between multiple NDMP hosts. Robotic control can be on an NDMP host
or on a NetBackup server.
■ Shared tape drives with the Shared Storage Option
Tape drives can be shared between servers (both NetBackup servers and
NDMP hosts). This setup requires the Shared Storage Option (SSO) license.
To see if your NAS vendor supports SSO, refer to “NDMP information on the
Web” on page 29.
■ Snapshots of data on NDMP hosts
 Introduction to NetBackup for NDMP 11
NetBackup for NDMP features

NetBackup can make point-in-time data snapshots on an NDMP (NAS) host

without interrupting client access to data, using the NDMP V4 snapshot
extension. The snapshot is stored on the same device that contains the
NDMP client data. From the snapshot, you can restore individual files or
roll back a file system or volume by means of Snapshot Client Instant
Recovery. A NetBackup Snapshot Client license is required, in addition to
the NetBackup for NDMP license. This Snapshot Client feature uses the
NAS_Snapshot method.
Refer to the NetBackup Snapshot Client Administrator’s Guide for details.
■ NDMP direct copy
NetBackup can copy virtual tape library (VTL) images directly from the VTL
to physical tape or to another VTL, without using media server I/O
resources or network bandwidth. NetBackup can directly copy NDMP
backup images from one NDMP-attached tape drive to another NDMP tape
drive that is attached to the same NDMP host. Note that the operation does
not use media server 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 Client
Administrator’s Guide.
For a list of NAS vendors that NetBackup currently supports for SnapVault
and NAS_Snapshot, refer to the Veritas NetBackup Snapshot Client
Configuration online document.
See “Snapshot Client Assistance” on page 30 for help accessing that
document.
■ Direct Access Recovery (DAR)
For NDMP hosts that support DAR, this feature greatly reduces the time
that is needed to restore a directory, a single file, or a small number of files.
■ Path-based file history
The NDMP server can send catalog information consisting of complete path
names to NetBackup. Some vendors do not support this feature.
For up-to-date information on the vendors that support path-based history,
refer to “NDMP information on the Web” on page 29.
■ NetBackup for NDMP servers are supported in a NetBackup-clustered
environment.
■ The enhanced ability to run customized scripts during a backup, especially
for relational databases residing on NAS devices.
12 Introduction to NetBackup for NDMP
NetBackup for NDMP terminology

NetBackup for NDMP terminology

This section introduces NetBackup for NDMP terminology. For explanations of

other NetBackup terms, consult the NetBackup online glossary in NetBackup
help.
DAR (Direct Access Recovery)
The NDMP host positions the tape to the exact location of the requested file(s),
reading only the data that is needed for those files. Restore times can be reduced
from hours to minutes.
NDMP (Network Data Management Protocol)
NDMP is a widely used protocol through which an NDMP-conformant backup
application can control the backups and restores for an NDMP host.
NDMP backup to Media Manager storage units
A form of three-way backup and restore also known as Remote NDMP. Data
travels from an NDMP host to a tape drive that is attached to a NetBackup media
server.
NDMP client
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 client sends commands to the NDMP server application to
control the backups and restores on an NDMP host.
NetBackup for NDMP allows NetBackup to act as an NDMP client.
NetBackup for NDMP server
A NetBackup for NDMP server is a NetBackup master or media server on which
NetBackup for NDMP software is installed.
NDMP host
A NAS system that serves files to clients using HTTP, FTP, CIFS, or NFS
protocols. It also runs an NDMP server application that communicates with
NDMP client backup software to configure and perform backup and restore
tasks.
NAS systems provide fast, multi-protocol file access and cost effective data
storage to workstations and servers in the network or across the Internet.
In a NetBackup configuration, the NDMP host is considered a client of
NetBackup. However, NetBackup client software is never installed on an NDMP
host.
NDMP server application
An NDMP server application runs on an NDMP host and runs backup, restore,
and device control commands that it receives from an NDMP-conformant
backup application. The backup application (NetBackup) is considered an NDMP
client.
 Introduction to NetBackup for NDMP 13
NetBackup for NDMP terminology

A separate instance of an NDMP server process exists for each connection to an

NDMP client. That is, if two backups are in progress, an NDMP server process
exists for each backup.
NDMP storage unit
An NDMP storage unit stores the backup data for an NDMP host. The tape drives
in this storage unit attach directly to the NDMP host or can be configured on a
SAN.
Note that NDMP storage units cannot be used to store data for non-NDMP hosts,
and NetBackup disk storage units cannot be used for NDMP tasks.
Redirected restore (to a different client)
In a redirected restore, files are restored to a client other than the one from
which they were originally backed up. In NetBackup for NDMP, the following
occurs: the restore data travels from an NDMP host (or NetBackup media server)
with a locally attached storage device to another NDMP host on the network.
Remote NDMP
See “NDMP backup to Media Manager storage units” on page 12.
Three-way backup/restore
In a three-way backup or restore, data travels in the following manner: between
an NDMP host and a storage device that is attached to another NDMP host or to
a NetBackup media server. This backup contrasts with local NDMP backup or
restore where the data travels as follows: between an NDMP host’s disk and a
storage device directly attached to the same NDMP host.
Virtual Tape Library (VTL)
A virtual tape library is a storage system that uses disk-based technology to
emulate a tape library and tape drives. For secondary storage, NetBackup can
copy VTL images directly to a physical tape or to another VTL, by means of
NDMP direct copy.
14 Introduction to NetBackup for NDMP
Network data management protocol (NDMP)

Network data management protocol (NDMP)

NDMP is a widely used protocol. through which an NDMP-conformant backup

application controls the backups and restores of any NDMP host that runs an
NDMP server application.
NDMP architecture follows the client/server model:
■ The NetBackup master or media server where NetBackup for NDMP is
installed is 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.
NetBackup for NDMP lets NetBackup act as an NDMP client. The NDMP
hosts, on the other hand, act as NetBackup clients.

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

Network

NetBackup for NDMP server NDMP Host NDMP Host

A NetBackup master or media server
where NetBackup for NDMP is NDMP hosts act as NetBackup clients ...
installed.

The NetBackup for NDMP server acts as NOTE: NetBackup software is NOT installed
an NDMP client. on NDMP hosts.
 Introduction to NetBackup for NDMP 15
Types of NDMP backup

Types of NDMP backup

The NDMP server application on the NDMP host performs backups and restores
of 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 backup

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

Figure 1-2 NDMP local backup/restore

LAN/WAN

NDMP

host

NetBackup for

NDMP server

FC/SAN

Disks Tape library Storage devices on SAN

Local NDMP backup

Data travels from disk to tape on same NDMP host, or from disk to
tape device on SAN. Backup data is NOT sent over local network.
The tape drives must be in NDMP-type storage units.
16 Introduction to NetBackup for NDMP
Types of NDMP backup

NDMP three-way backup

The NetBackup for NDMP server initiates the backup. Data travels over the
network in the following manner: from an NDMP host to a storage device that is
attached to another NDMP host on the local network or available on a SAN.

Figure 1-3 NDMP three-way backup/restore

LAN/WAN

NDMP NDMP
host Host

NetBackup for
NDMP server

Disks Tape library

Three-Way NDMP backup

Data travels from disk on an NDMP host to tape device on another

NDMP host. Backup data is sent over the local network.

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

 Introduction to NetBackup for NDMP 17

Types of NDMP backup

Backup to Media Manager storage units (remote NDMP)

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

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

LAN / WAN

NetBackup for NDMP

NDMP server host

FC/SAN

Storage Devices on SAN Tape library Disks

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. Backup
data is sent over the local network.
NOTE: The NetBackup drive(s) must be in Media Manager type storage units.
18 Introduction to NetBackup for NDMP
NDMP policies

NDMP policies

After you install and configure NetBackup for NDMP, you can schedule backups

by creating an NDMP policy in NetBackup.

An NDMP policy can have one or more NetBackup clients. Each NetBackup

client must be an NDMP host.

See Figure 1-1, “NDMP and NetBackup hosts as clients of each other” on

page 14.

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,

Cumulative Incremental, or Differential Incremental. User-initiated backups

and archives are not allowed because the NDMP protocol does not permit these

tasks.

Restores of NDMP host backups can be initiated from any NetBackup media

server that

■ Is within the same overall NetBackup storage domain

■ Uses the same NetBackup master server that the media server uses that
performed the backup
The data can be restored to the NDMP host where it was backed up, or to another
NDMP host.
NDMP policies can use either NDMP storage units or Media Manager storage
units.
 Introduction to NetBackup for NDMP 19
Storage units

Storage units

NetBackup 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 a
NetBackup media server)

NDMP Storage units

NetBackup requires NDMP-type storage units when you back up NDMP host
data to 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
controls can be in a TLD (Tape Library DLT), TL8 (Tape Library 8MM), TLH (Tape
Library Half Inch), or ACS robot type.

Media Manager storage units

You can use drives that were configured in Media Manager-type storage units
when 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 be
dedicated to NDMP data. They can store backups of regular (non-NDMP)

NetBackup clients as well as of NDMP clients.

Refer to the “Configuring NDMP backup to NetBackup media servers (remote

NDMP)” chapter for configuration help.

Assigning tape drives to different hosts

Robotic tape drives can be divided up among NDMP hosts and NetBackup

servers.

For example, referring to Figure 1-5, “NDMP and non-NDMP storage units”:

■ Tape drives 1, 3, and 5 are attached to NDMP hosts. They are in NDMP
storage units that can be used for NDMP backup (local or three-way).
The commands that control these drives originate on the NetBackup for
NDMP server and are sent through the NDMP connection on the network.
20 Introduction to NetBackup for NDMP

Storage units

The NDMP server application on each NDMP host translates the NDMP
commands into SCSI commands for the local drives.
■ Tape drives 2 and 4 are attached to a NetBackup server. They are in
non-NDMP storage units and are controlled in the same way as other drives
on NetBackup servers. Depending on the type of storage unit, these drives
can be used for the following:
■ For non-NDMP clients of NetBackup
■ In the case of tape drives in Media Manager storage units, they can be
used for 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

LAN/WAN Drive-control commands for NDMP

NB for NDMP NDMP NDMP

NDMP host host host
media
server

Drive 1*

Drive 5*
Drive 2†
Drive 3*

Drive 4‡
TLD
Robot

* In NDMP storage unit

Drives 1, 3, and 5 (in NDMP storage units) can be used for NDMP backups.
† In NetBackup Media
Manager storage unit Drive 2 (in Media Manager storage unit) can be used for NDMP or
non-NDMP backup.
‡ In another type of
NetBackup storage Drive 4 (in different type of NetBackup storage unit) cannot be used for
unit (not NDMP or NDMP backup.
Media Manager)
 Introduction to NetBackup for NDMP 21
Storage units

Robotics control can be attached to an NDMP host or to a NetBackup server, as

follows.

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

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

Commands to control
robot
NetBackup NDMP
for Host
NDMP
Server

Robotic
Control

Robot

NetBackup server
Figure 1-7 shows how the robot is controlled in the same way as other robots on
NetBackup servers.

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

NetBackup NDMP
Server Host

Commands to control
robot
Robotic

Control

Robot

22 Introduction to NetBackup for NDMP

NDMP backup process

NDMP backup process

Figure 1-8, “NetBackup backup processes” shows the NetBackup processes that
are involved in NDMP backups. During a backup, the following events occur:
1 From the EMM database, NetBackup obtains a media ID for the tape that is
used for the backup and sends a tape-mount request to ltid.
2 ltid on the NetBackup for NDMP server sends the necessary NDMP (SCSI
robotic) commands to mount the requested tape on the storage device.
3 NetBackup sends the NDMP commands that are necessary to have the
NDMP server application perform a backup to the tape. The backup data
travels in one 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 NDMP
host without its own storage device to an NDMP host (or NetBackup
media server) with a locally attached storage device (three-way
backup).
4 The NDMP server application sends information to the NetBackup for
NDMP server about the files that were backed up. This information is stored
in the NetBackup file database.
5 The NDMP server application sends status about the backup operation to
the NetBackup for NDMP server.
 Introduction to NetBackup for NDMP 23
NDMP backup process

Figure 1-8 NetBackup backup processes

NetBackup Master Server NetBackup

Administration
Console
Configuration File
Database Database
bprd

bpdbm nbproxy nbpem

nbproxy
EMM
database nbjm

nbemm nbrb

NetBackup Master or bpcd

Ca

Media Server
ta
l
og

This server has

in
fo

NetBackup for NDMP

rm
at

bpbrm
io
n

Network
Connection
bptm ndmpagent
st
ue
eq
eR
Tap “3-way”

ltid NDMP Host NDMP Host

NDMP Server NDMP Server

OS OS

Tape

Disk Disk

Local
24 Introduction to NetBackup for NDMP
NDMP restore process

NDMP restore process

Because of the design of the NDMP protocol, only an administrator on a
NetBackup server (master or media) can restore files from NDMP backups.
During a restore, the administrator browses the file catalog and selects files
from NDMP images in the same manner as for standard backup images.
Figure 1-9, “NetBackup restore processes” shows the NetBackup processes
involved in NDMP restores. The following events occur during a restore:
1 The NetBackup for NDMP server looks in its EMM database for the tape that
contains the backup, and asks ltid to mount that tape.
2 ltid on the NetBackup for NDMP server sends the necessary NDMP
commands to load the requested tape on the storage device.
3 NetBackup sends the NDMP commands that are necessary to have the
NDMP server application perform a restore operation to the disk. The
restore data travels in one of two ways:
■ From a tape drive to a local disk (tape drive and disk are on the same
NDMP host)
■ Over the network, from an NDMP host (or NetBackup media server)
with a locally attached storage device to another NDMP host (three-way
backup/restore)
4 The NDMP server application sends status about the restore operation to
the NetBackup for NDMP server.
 Introduction to NetBackup for NDMP 25
NDMP restore process

Figure 1-9 NetBackup restore processes

NetBackup Master Server Backup, Archive, and Restore (on

master or media server)

bprd is on the
master server bprd

NetBackup Master or
Media Server bpcd
This server has
NetBackup for NDMP.

bpbrm

Network
EMM NetBackup Media ID Connection
database bptm ndmpagent

t
ues
e Re q
Tap
“3-way”
ltid
NDMP Host NDMP Host

NDMP Server NDMP Server

OS OS

Disk Disk

Tape

Local
26 Introduction to NetBackup for NDMP
Direct access recovery (DAR)

Direct access recovery (DAR)

NetBackup uses Direct Access Recovery (DAR) to restore a directory or

individual files from a backup image. DAR can greatly reduce the time it takes to

restore files 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 the

requested file(s). It reads only the data that is needed for those files. For

individual file restore, NetBackup automatically determines whether DAR

shortens the duration of the restore. It activates DAR only when it results in a

faster restore.

See “Enabling or disabling DAR” on page 49 for details on when DAR is used and

on how to disable it.

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

NDMP:

■ 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 format
is the default).

NDMP direct copy with VTL

NetBackup supports virtual tape libraries (VTLs). A virtual tape library uses
disk-based technology to emulate a tape library (robot) and drives. The backup
image is written to one or more disks in the VTL. The VTL allows the image to be
treated as though it resides on tape, but with the access speed of a disk.
For additional storage (such as for disaster recovery), NetBackup copies backup
images from the VTL disk to a physical tape in an NDMP storage unit. It copies
without using media server I/O or network bandwidth. NetBackup can also copy
NDMP images directly between NDMP tape drives attached to an NDMP host. In
both cases, this feature is called NDMP direct copy. This feature also enables
NetBackup to restore data directly from either the image in the VTL or from the
physical NDMP tape.
To initiate the NDMP direct copy, you can use the NetBackup duplication feature
in the Administration Console, or the bpduplicate command, or NetBackup
Vault.
Figure 1-10, “Overview of NDMP direct copy with VTL” on page 27 represents a
VTL from two perspectives: it shows the actual hardware present in a VTL
configuration and the configuration from the perspective of NetBackup.
 Introduction to NetBackup for NDMP 27
NDMP direct copy with VTL

Figure 1-10 Overview of NDMP direct copy with VTL

Actual hardware in VTL

Hardware from NetBackup
configuration
perspective
LAN/WAN
LAN/WAN

NetBackup media server

NetBackup media server

SCSI

SCSI
or

or
SAN

SAN

VTL VTL
SCSI or SAN
(disk array) appears to SCSI or SAN
be a robot

VTL is a disk storage system Tape library

that emulates both a tape for tertiary On NetBackup, the VTL is Tape library
library and an NDMP tape storage configured as a tape library with for tertiary
server tape drives. storage

The NDMP direct copy feature uses a VTL that has an embedded NDMP tape
server using the NDMP protocol. The embedded NDMP tape server moves the
image from the VTL disk directly to a physical tape. The image does not pass
through the NetBackup media server or travel over the network.
See Figure 1-11, “NDMP direct copy with VTL: data flow and control” on page 28.
28 Introduction to NetBackup for NDMP
NDMP direct copy with VTL

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

LAN/WAN

NB
media
server

SCSI
1 or
SAN

VTL 5

SCSI or SAN

4
2
NDMP NDMP
session session physical tape library
in VTL 3 in VTL

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 from
the 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.

Note: For configuration instructions, see the “Configuring NDMP direct copy”
chapter.

NDMP direct copy without VTL

Using the NetBackup duplication feature, NetBackup can copy NDMP images
between tape drives attached to an NDMP host, by means of NDMP direct copy.
A typical usage is to copy images between tape drives within the same tape
library. (Images can also be copied between tape libraries.) Like NDMP direct
copy with a VTL, the copied data does not pass through the NetBackup media
server or travel over the network. See Figure 1-12 on page 29.
 Introduction to NetBackup for NDMP 29
NDMP information on the Web

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

LAN/WAN

NDMP
host

NetBackup for

NDMP server
SCSI or SAN

NDMP direct
copy

NDMP direct copy: notes and limitations

Note the following:
■ Supports backup to tape and restore from tape, for NDMP data as well as
non-NDMP data.
■ Does not support synthetic backup or multiple copies.
■ Does not support storage unit groups for the destination device. If you select
a storage unit group, NDMP direct copy is disabled. The data transfer takes
place over the network by means of the NetBackup server.
■ In a VTL environment, a NAS appliance is not required: the VTL emulates a
NAS (NDMP) host. The VTL requires NDMP tape server functionality.
■ NetBackup for NDMP software must be installed. NetBackup for NDMP is
enabled by the Virtual Tape Option license. Requires the NDMP protocol
version V4 or higher.
■ NetBackup servers (master and media) must be at NetBackup 6.5 or later.
■ The “Virtual Tape Libraries/Drives” section of the NetBackup 6.5 Hardware
Compatibility List (HCL) indicates which VTL software supports this
functionality. See “NDMP information on the Web.”

NDMP information on the Web

The Symantec support Web site has a PDF document on supported NDMP
operating systems and NAS vendors. The document is titled Veritas NetBackup
for NDMP: Supported OS and NAS Appliance Information. It also contains
configuration and troubleshooting help for particular NAS systems:
30 Introduction to NetBackup for NDMP

Snapshot Client Assistance

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

For the features and software releases for each NAS vendor, for SSO support,
and for the NetBackup versions that support these vendors, refer to either of the
following, available at entsupport.symantec.com:
■ The NetBackup NDMP Compatibility List (titled Veritas NetBackup for
Network Data Management Protocol (NDMP) Support), document ID 251713.
■ The “NDMP Devices” section and the “Virtual Tape Libraries/Drives”
section of the Veritas NetBackup Enterprise Server 6.5 Hardware
Compatibility List, document ID 284599.

Snapshot Client Assistance

For Snapshot Client assistance, see the NetBackup Snapshot Client
Administrator’s Guide. For additional information, see the following document:
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 and
for SnapVault
■ Sections on SAN device configuration and on setting up NetBackup for
off-host data mover backups (including instructions on creating 3pc.conf
and mover.conf files)
 Chapter 2
Installing NetBackup for
NDMP
This chapter explains how to install the NetBackup for NDMP application on
NetBackup servers.

Installation notes
■ The NetBackup for NDMP master/media server must be running NetBackup
6.5 or later.
■ The NetBackup for NDMP 6.5 software supports Solaris (SPARC only),
HP-UX (PA-RISC only), Red Hat Linux (x86 only), AIX, and Windows
2000/2003 (including 64-bit) master or media servers.
For a detailed list of NAS platforms that NetBackup for NDMP supports,
refer to “NDMP information on the Web” on page 29.
■ For making snapshots of NDMP (NAS) hosts, NetBackup Snapshot Client
software must be installed on the following: the NetBackup master server
and the NetBackup clients that are used to perform backups.
For more information, refer to the NetBackup Snapshot Client
Administrator’s Guide.
■ The drives and robots that are attached to the NDMP host must be the types
that the NDMP host and NetBackup support.
See “NDMP Storage units” on page 19 for a list of supported robot types.
For more information on storage devices, see the NetBackup
Administrator’s Guide, Volume I.
■ For notes and tips on your particular NDMP host, refer to “NDMP
information on the Web” on page 29.
32 Installing NetBackup for NDMP
Installing on UNIX servers

Installing on UNIX servers

Note: If you install in a cluster environment, freeze the active node before you
begin the installation process so that migrations do not occur during
installation. For information about freezing a service group, see the clustering
section in the NetBackup High Availability Administrator’s Guide for the cluster
software you are running.

On the UNIX host that you want to be the NetBackup for NDMP server, do the
following:
1 Log in as root.
2 Install NetBackup server and client software as explained in the NetBackup
Installation Guide for UNIX and Linux.
3 To make sure a valid license key for NetBackup for NDMP is registered,
enter the following command to list and add keys:
/usr/openv/netbackup/bin/admincmd/get_license_key

4 Insert the CD-ROM containing NetBackup for NDMP software in the drive.
5 Change your working directory to the CD-ROM directory:
cd /cd_rom_directory
Where cd_rom_directory is the path to the directory where you can access
the CD-ROM. On some platforms, it may be necessary to mount this
directory.
6 To install NetBackup for NDMP, execute the following:
./install

Since other NetBackup products are included on the CD-ROM, a menu

appears.
7 Select NetBackup Add-On Product Software.
a Select the NetBackup for NDMP option.
b Enter q to quit the menu.
c In the prompt that asks if the list is correct, enter y.
8 If this NetBackup for NDMP server is not your master server, also install
your NDMP license key on the master.
9 In a clustered environment, perform these steps on each node in the cluster.
 Installing NetBackup for NDMP 33
Installing on Windows servers

Note: If you install in a cluster environment, unfreeze the active node after the
installation completes. For information about unfreezing a service group, see
the clustering section in the NetBackup High Availability Administrator’s Guide
for the cluster software you are running.

Installing on Windows servers

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

On the Windows host that you want to be the NetBackup for NDMP server,
perform the following:
1 Log in.
2 Install NetBackup server and client software as explained in the NetBackup
Installation Guide for Windows.
3 NetBackup for NDMP is part of the core NetBackup product. To make sure a
valid license key for NetBackup for NDMP is registered, do the following to
list and add keys:
a In the NetBackup Administration Console, select Help.

b On the Help menu, select License Keys ....

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

c To register a new key, click the star icon to open the Add a new
License Key dialog box. Type the new license key in the New license key

field and click 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 your
NDMP license key on the master.
5 In a clustered environment, perform these steps on each node in the cluster.

Note: If you install in a cluster environment, unfreeze the active node after the
installation completes. For information about unfreezing a service group, see
the clustering section in the NetBackup High Availability Administrator’s Guide
for the cluster software you are running.
34 Installing NetBackup for NDMP
Uninstalling NetBackup for NDMP

Uninstalling NetBackup for NDMP

On the server where you initially loaded the NetBackup for NDMP software, do
the following. This procedure results in total removal of the NetBackup for
NDMP software.

Note: In a cluster environment, you must first freeze the active node so that
migrations do not occur. For help freezing a service group, see the clustering
section in the NetBackup High Availability Administrator’s Guide for the cluster
software you are running.

1 Check the Activity Monitor in the Administration Console to make sure no

NetBackup for NDMP backups are active or running (State field reads
Done).
2 If ltid is running, stop it (use the Activity Monitor > Daemons tab).
3 Pre-6.0 NetBackup on Solaris only: if ndmpmoveragent is running (check
the Activity Monitor > Processes tab), stop it by entering the following:
cd /usr/openv/volmgr/bin

./ndmpmoveragent.stop

4 To remove the NetBackup for NDMP package, enter the following:

On Solaris (SPARC only):
■ For any version before NetBackup 6.5, enter the following:
pkgrm VRTSnbdmp

■ For NetBackup 6.5, enter the following:

pkgrm SYMCnbdmp

On other UNIX platforms:

rm -f /usr/openv/lib/libndmpclient.s?

rm -f /usr/openv/volmgr/bin/set_ndmp_attr

rm -f /usr/openv/share/version_ndmp

rm -f /usr/openv/netbackup/bin/ndmpagent

where ? is a wildcard.
5 Restart ltid.

Note: If you install in a cluster environment, unfreeze the active node after the
de-installation completes. For information about unfreezing a service group, see
the clustering section in the NetBackup High Availability Administrator’s Guide
for the cluster software you are running.
 Chapter 3
Configuring NDMP backup

to NDMP-attached devices

This chapter explains how to configure backups on the storage devices that are
attached to NDMP hosts. Only NDMP-specific steps are described.

Note: You also can use the NetBackup Device Configuration wizard to discover
and configure the robots and drives that are attached to an NDMP host. (The
wizard requires NDMP protocol versions V3 or V4.)

To configure and use the NAS_Snapshot method when backing up NDMP host

data, see the NetBackup Snapshot Client Administrator’s Guide.

The following topics are covered in this chapter:

■ Authorizing access to the NDMP host

■ Media and Device Management configuration
■ Verifying NDMP password and robot connection
■ Adding NDMP storage units
■ Creating an NDMP policy
■ Enabling or disabling DAR
■ Setting up clustering
■ Testing an NDMP configuration
36 Configuring NDMP backup to NDMP-attached devices
Authorizing access to the NDMP host

Authorizing access to the NDMP host

Before NetBackup can carry out backups, it must have access to the NDMP host.
To authorize this access, use the following dialog box from the NetBackup
Administration Console on your NetBackup for NDMP master server. You can
also use the NetBackup Device Configuration wizard to create this
authorization.

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

To authorize NetBackup access to the NDMP host (from the Administration

Console)
1 On the NetBackup server: under Media and Device Management >
Credentials, click NDMP Hosts. Under Actions, select New > NDMP Host.
2 In the NDMP host name dialog box, enter the name of the NDMP server for
NetBackup to back up.

Note: This NDMP host name is case sensitive. Whenever this host name is
used, the name must be identical to the name entered here. (For example,
when you configure tape drives and storage units for this host.)

3 Click OK.
4 In the New NDMP Host dialog box, specify the following:
(The term credentials refers to the user name and password that NetBackup
uses to access the NDMP host.)

Use global NDMP Select this option to enable all NetBackup media servers
credentials for this under the master server to access this NDMP host using a
NDMP host pre-defined global NDMP login.
To create this login, click Host Properties > Master Server
> Properties > NDMP in the NDMP Global Credentials
dialog box.
 Configuring NDMP backup to NDMP-attached devices 37
Authorizing access to the NDMP host

Use the following This option enables all NetBackup media servers that are
credentials for this connected to the NDMP host to access the NDMP host
NDMP host on all media using the login you specify:
servers ■ Username: the user name under which NetBackup
accesses the NDMP server. This user must have
permission to run NDMP commands.
To see if your NDMP host vendor requires a particular
user name or access level, refer to “NDMP
information on the Web” on page 29.
■ Password and Confirm Password: enter the password
for this user.

Use different Select this option to specify NDMP logins for particular
credentials for this NetBackup servers. Then click Advanced Configuration.
NDMP host on each ■ In the Advanced NDMP Credentials dialog box, click
media server Add.
■ In the Add Credentials dialog box, select a NetBackup
server and specify the user name and password it uses
to access the NDMP host.
■ Click OK. NetBackup validates the user name and
password.
■ The NetBackup server and user name appear in the
Advanced NDMP Credentials dialog box.
■ If necessary, click Add again to specify other servers
and user

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

Access for three-way backups and remote NDMP

To perform three-way backups, you must authorize access to the NDMP host as
described in the previous section.
■ Three-way backups: for the NDMP host name, specify the NDMP host that
has no attached tape drive.
■ NDMP to Media Manager storage units (remote NDMP): for the NDMP host
name, specify the NDMP host to back up to the Media Manager storage unit
that is defined on the NetBackup server.
See the “Configuring NDMP backup to NetBackup media servers (remote
NDMP)” chapter for more information.
38 Configuring NDMP backup to NDMP-attached devices
Media and Device Management configuration

Media and Device Management configuration

On the NetBackup for NDMP server, use Media and Device Management in the

Administration Console to add drives and robots. As an alternative, you can use

the 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 on

configuring NetBackup media.

For more information on configuring storage devices for specific NDMP hosts,

refer to “NDMP information on the Web” on page 29.

Note: These procedures do not apply to setting up the devices that are attached
to the NetBackup media server. To back up NDMP data to Media Manager
storage units (remote NDMP), storage units are configured in the same way as
ordinary NetBackup (non-NDMP) devices. For details, refer to “Configuring
NDMP backup to NetBackup media servers (remote NDMP)” on page 53 and to
the NetBackup Administrator’s Guide, Volume I.

Adding a robot directly attached to an NDMP host

To add a robot directly attached to an NDMP host
1 Start the NetBackup Administration Console on the NetBackup for NDMP
server as follows:

Windows In the Windows Start menu, click Programs, Veritas NetBackup,

NetBackup Administration Console.

UNIX Enter the following:

/usr/openv/netbackup/bin/jnbSA &

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 devices 39
Media and Device Management configuration

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

Explained in online help

or in the NetBackup
Administrator’s Guide,
Volume I.

Explained in the
following steps.

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

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

Robot type Specify type.

Robot number Specify number.

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

40 Configuring NDMP backup to NDMP-attached devices
Media and Device Management configuration

Robot device Enter the device name of the robot. You do not need to include the
path NDMP host name as part of the device path.
To determine the device name of the robot, refer to “NDMP
information on the Web” on page 29 for information pertaining to
your NDMP host.

NDMP host Enter the name of the NDMP host to which the robot is attached
name

Bus, Target, and Specify these values if the NDMP host requires them. By default,
LUN values the bus, target, and lun values are 0.
Refer to “NDMP information on the Web” on page 29 for
information pertaining to your NDMP host.

For assistance with the Add Robot dialog box, refer to the online help. The
following steps explain the portions that are unique to configuring
NetBackup for NDMP.
5 Click OK.
6 In the popup message that asks if you want to stop and restart the device
manager service (or daemon), click Yes.
 Configuring NDMP backup to NDMP-attached devices 41
Media and Device Management configuration

Adding a drive
To add a drive
1 In the NetBackup administration console, select Media and Device
Management > 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 name of
the drive.

5 Click Add to specify a drive path.

42 Configuring NDMP backup to NDMP-attached devices

Media and Device Management configuration

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

Device host Select the name of the NetBackup media server. Use the
pull-down to select media servers already defined, or click Add
to enter a new one.

Path Enter the device file name of the tape drive, such as nrst2a.
Refer to the NAS vendor documentation for your drive for the
correct format of the device file name.
Alternate method: use the following command to find the device
file name for the drive, if the NDMP host is running NDMP
protocol V3 or later:
tpautoconf -probe ndmp_host_name

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 which
the drive is attached.
9 Click OK.
Return to the Add a New Drive dialog box and enter the Drive information as
required. Repeat this procedure for each drive that must be added.
When you are prompted to restart the Media Manager device daemon and all
robotic daemons, click Yes.

Checking the device configuration

On the NetBackup for NDMP server, do the following:
■ On UNIX, execute /usr/openv/volmgr/bin/vmps and verify that ltid,
vmd, avrd, and any required robotic daemons are active. On Windows, go to
the NetBackup Administration Console and use the Activity Monitor
(Processes tab) to verify that the these processes are active.
■ From the NetBackup Administration Console, use the Device Monitor to
ensure that the drive is in the UP state.

Adding volumes
Use the NetBackup Media and Device Management utility to add the volumes

that you plan to use for the NDMP host backups.

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

 Configuring NDMP backup to NDMP-attached devices 43

Verifying NDMP password and robot connection

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

Verifying NDMP password and robot connection

When you authorize NetBackup access to the NDMP host and configure robots
using the Administration Console, NetBackup automatically verifies NDMP
credentials 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

44 Configuring NDMP backup to NDMP-attached devices

Adding NDMP storage units

Adding NDMP storage units

On the NetBackup master server, add an NDMP-type storage unit for the devices
that contain the backup data. Most of the requirements are the same as for
adding a Media Manager storage unit. The following explains how to add an
NDMP storage unit.
See the NetBackup Administrator’s Guide, Volume I, for more information on
storage units.

Note: NDMP-type storage units are not used for backups to media
server-attached devices. Use Media Manager storage units instead.
See the “Configuring NDMP backup to NetBackup media servers (remote
NDMP)” chapter for details.

1 In the NetBackup Administration Console, select NetBackup Management >

Storage.
2 On the Actions menu, select New > Storage Unit.
 Configuring NDMP backup to NDMP-attached devices 45
Adding NDMP storage units

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

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

Storage unit type Select NDMP.

On demand only This option specifies whether the storage unit is available only
when a policy or schedule specifically requests it. If this option
is not used, the storage unit is available to any NDMP policy or
schedule.

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

NDMP host Specify the NDMP host where the tape drive is physically
attached.

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

Volume I.
46 Configuring NDMP backup to NDMP-attached devices
Creating an NDMP policy

Creating an NDMP policy

On the NetBackup master server, create an NDMP policy to configure backups of
the NDMP host.

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 on
NetBackup policies and the Policy utility.

Note: To configure a policy for the NAS_Snapshot method and SnapVault, see
the NetBackup Snapshot Client Administrator’s Guide.

Attributes
Specify the following policy attributes:
■ Policy Type: NDMP
■ Policy Storage Unit:
■ To direct backups for this policy to a specific storage unit if the NDMP
host has multiple storage units, specify that storage unit name.
■ For a three-way backup, specify a storage unit that was defined for the
target NDMP host with attached tape.
■ For NDMP backup to Media Manager storage units: specify a Media
Manager storage unit that is defined for a device that is connected to a
NetBackup media server.
See the “Configuring NDMP backup to NetBackup media servers
(remote NDMP)” chapter.

Clients
In the client list, specify the following for each client in an NDMP policy:
■ Hostname
Name of the NDMP host
■ Hardware and operating system
NDMP NDMP
 Configuring NDMP backup to NDMP-attached devices 47
Creating an NDMP policy

Files
The Backup Selections list must specify directories from the perspective of the

NDMP host.

Two examples:

/home/dir1/

/vol1

The following Backup Selections capabilities are NOT supported for an NDMP
policy:
■ 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). You
can, however, exclude files by using the SET keyword as shown under “Using
environment variables in backup selections list.” The SET option allows you
to exclude files on a backup. The format is vendor dependent; refer to the
vendor’s documentation for more details on which variable can be passed
and in what format.

Schedules
You can specify any of the following backup types in a schedule for an NDMP
policy:
■ Full
■ Cumulative Incremental
■ Differential Incremental
Specify Override policy storage unit only in the following situation: this client of
NetBackup (the NDMP host) has more than one storage unit and you want to use
a specific storage unit for this schedule. In this case, the client must be the only
client in this NDMP policy.

Using environment variables in backup selections list

NDMP allows you to use environment variables to pass configuration
parameters to an NDMP host with each backup. NDMP environment variables
can be one of the 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:
48 Configuring NDMP backup to NDMP-attached devices
Creating an NDMP policy

FILESYSTEM

LEVEL

DIRECT

EXTRACT

ACL_START

In NetBackup, environment variables can be set within the Backup Selections

list by specifying one or more SET directives.

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 particular NAS vendors, refer
to “NDMP information on the Web” on page 29.

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 value
that is assigned to it. The value can be enclosed in single or double quotes, and
must 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, if

Backup 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. The third directory (/vol/vol3) is backed up with all three of the

environment variables set.

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

variable overrides the previous value of the variable.

The values that each backup uses are saved and provided to subsequent restores

of the directory. The NDMP host may have some environment variables that are

set internally and these are also saved for restores.

 Configuring NDMP backup to NDMP-attached devices 49

Enabling or disabling DAR

Enabling or disabling DAR

By default, NetBackup for NDMP is configured to use Direct Access Recovery

(DAR) when restoring files or directories. DAR is used somewhat differently for
file restore than for directory restore, as follows:
■ For each restore of files (not of directories), NetBackup automatically
determines if the use of DAR speeds up the restore. NetBackup uses DAR
only when it results in a faster restore.
■ For restore of directories, by default DAR is always used when restoring a
subdirectory but never used when restoring the directory containing an
entire image. 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 the
effectiveness of using DAR. Unless DAR is manually disabled, NetBackup
always uses DAR when restoring subdirectories.
See “Disabling DAR for file and directory restores.”
It may be necessary to disable DAR in the following situation: you have
problems with DAR and your NDMP host is an older machine or is not running
the latest NAS OS version.

Disabling DAR for file and directory restores

This procedure disables DAR for both file and directory restores, for all NDMP
policies.
1 In the NetBackup Administration Console, expand Host Properties and click
Master 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 click
Apply.
This action disables DAR on all NDMP restores.

Disabling DAR for directory restores only

To disable DAR on restores of directories only (leave DAR enabled for individual

file restore), for all NDMP policies, do the following.

Enter the string NDMP_DAR_DIRECTORY_DISABLED in the following file:

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

50 Configuring NDMP backup to NDMP-attached devices

Setting up clustering

To re-enable directory DAR, remove (or comment out) the

NDMP_DAR_DIRECTORY_DISABLED string from the ndmp.cfg file.

Setting up clustering
Before configuring NetBackup for NDMP for clustering, the following must be
installed on each node of the cluster:
■ NetBackup server (see the NetBackup Installation Guide).
■ NetBackup for NDMP software (see “Installing NetBackup for NDMP” on
page 31 of this manual). Note that for Windows servers, only the NetBackup
for NDMP licence key has to be installed.
1 Configure NDMP-attached robots and drives. Then configure storage units
and policies as in a normal, non-clustered environment:
■ You can use the Device Configuration wizard, or configure devices
manually as described under “Authorizing access to the NDMP host” on
page 36 and following.
■ To use the same robotic libraries throughout a cluster, robot numbers
must be consistent. The Device Configuration wizard attempts to
ensure this configuration. If you configure robots manually, be sure to
use the same robot number for a given robot, from one host to another
in the cluster.
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 for the first node.

Post-installation changes
After NetBackup is configured in a clustered environment, most configuration
information is available to all nodes in the cluster. The information is available
by means of a shared hard drive. However, if you make changes in the Host
Properties area of the Administration Console, they are not available on the
shared drive. Such changes apply only to the active node. You must manually
duplicate on each node any Host Properties changes that are made on the active
node. This action lets NetBackup perform exactly the same way in case of
failover to another node.
Refer to the NetBackup High Availability Guide for assistance.
 Configuring NDMP backup to NDMP-attached devices 51
Testing an NDMP configuration

Testing an NDMP configuration

To test the configuration, run the backup and then restore some files. For
instructions, see the following topics:
■ “Performing an NDMP backup” on page 68.
■ “Performing a restore from the server” on page 69.
If you encounter problems, see “Troubleshooting” on page 71.
52 Configuring NDMP backup to NDMP-attached devices
Testing an NDMP configuration
 Chapter 4
Configuring NDMP backup
to NetBackup media
servers (remote NDMP)
This chapter describes how to configure NetBackup for NDMP to make backups
to Media Manager storage units (remote NDMP). Only NDMP-specific steps are
described.
The following topics are covered in this chapter:
■ Overview
■ Configuring NDMP backup to Media Manager storage units
54 Configuring NDMP backup to NetBackup media servers (remote NDMP)
Overview

Overview
Using remote NDMP, you can back up NDMP data to a configured drive in a
Media Manager storage unit on a NetBackup media server. The drive can be used
for both NDMP backups and for non-NDMP backups. See Figure 4-1.

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

LAN / WAN

NetBackup for

NDMP server

NDMP hosts (NAS filers). . .

NetBackup

drives in

Media

Manager

storage Data travels between NDMP hosts and a drive on a

unit(s). NetBackup media server.
NOTE: The NetBackup drive(s) need not be dedicated to
NDMP backups: they can be used for non-NDMP backups as
well.

Configuring NDMP backup to Media Manager

storage units
Follow these steps to configure NDMP backups to Media Manager storage units.
1 Authorize the NetBackup server to access the NDMP hosts you want to back
up.

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

a Under Media and Device Management > Credentials, click on NDMP

Hosts. Under Actions, choose New > NDMP Host to display the NDMP
Host dialog box.
b Fill in the values as described under “Authorizing access to the NDMP
host” on page 36.
 Configuring NDMP backup to NetBackup media servers (remote NDMP) 55
Configuring NDMP backup to Media Manager storage units

c Repeat the above for each NDMP host that the NetBackup server backs
up.
2 Use the NetBackup Device Configuration wizard to configure the drive(s)
and robot(s).

Note: Do not use the device configuration procedure in the “Configuring NDMP
backup to NDMP-attached devices” chapter in this guide. Rather, configure the
robots and drives in the same way as ordinary NetBackup devices, described in
the NetBackup Administrator’s Guide, Volume I.

Note: Drives can be shared using the Shared Storage Option (SSO) of NetBackup.
For an overview of the setup procedure, see “Using the Shared Storage Option
(SSO)” on page 61. The drives can be shared as both NDMP drives and non
NDMP drives.

3 Create a Media Manager storage unit for the drive(s).

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

Volume I.

Note: The storage unit type must be Media Manager, not NDMP.

4 Create an NDMP-type policy. On the New/Change Policy display, be sure to

specify the storage unit that was created at step 3.

See “Creating an NDMP policy” on page 46.

56 Configuring NDMP backup to NetBackup media servers (remote NDMP)

Configuring NDMP backup to Media Manager storage units
 Chapter 5
Configuring NDMP direct
copy
This chapter explains how to configure NDMP direct copy.
The following topics are covered in this chapter:
■ NDMP direct copy
■ Using NDMP direct copy
58 Configuring NDMP direct copy
NDMP direct copy

NDMP direct copy

NDMP direct copy can operate in two different environments:

■ A NetBackup media server that is connected to a VTL that has access to a
physical tape library. The steps for configuring NDMP direct copy are
described in this chapter.
■ A NetBackup for NDMP server that is connected to an NDMP host that has
access to a tape library (no VTL). This NDMP backup environment is
described in other chapters of this guide. In this environment, no additional
configuration is required for NDMP direct copy.
If your NDMP host and storage devices are correctly configured, NetBackup
uses NDMP direct copy when you duplicate an NDMP backup that
NetBackup had created. To configure NetBackup for NDMP, refer to
“Authorizing access to the NDMP host” on page 36 through “Creating an
NDMP policy” on page 46.

Prerequisites
■ If your environment includes a VTL, the VTL must be installed and set up
according to the vendor’s instructions. The NetBackup Virtual Tape Option
license(s) are required. The Virtual Tape Option license enables NDMP
direct copy functionality.
■ The VTL must have the NDMP capabilities needed to support NDMP direct
copy.
■ To make direct copies from one NDMP tape drive to another (no VTL), the
NetBackup for NDMP license is required.

How to configure NDMP direct copy

These are the steps for configuring NDMP direct copy from backups that were
made to a VTL.
1 Configure the VTL as an NDMP host. You can use the Device Configuration
Wizard, as follows.
■ On the Device Hosts dialog box of the wizard, choose the device host,
then click 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
Hosts dialog.
See “Using the Device Configuration Wizard” on page 64 for assistance.
 Configuring NDMP direct copy 59
Using NDMP direct copy

2 Authorize NetBackup access to the VTL. See “Authorizing access to the

NDMP host” on page 36. Note that the VTL emulates an NDMP host.
3 Configure the VTL as a robot, then configure one or more tape drives in a
Media Manager storage unit.
You can use the NetBackup Device Configuration wizard. Or, refer to the
NetBackup Administrator’s Guide Volume I for help configuring devices and
Media Manager storage units.
4 Configure one or more tape drives in the VTL as Network Attached Storage
devices, and create one or more NDMP storage units for the drives.
Refer to “Adding a drive” on page 41 and “Adding NDMP storage units” on
page 44 for procedures.
The drives may be the same as those that were selected for step 3.
NetBackup supports sharing of drives among media servers and NDMP
hosts.
5 Configure one or more NDMP tape drives in the physical tape library, and
add the drives to NDMP storage units. Use the same procedures as those
mentioned in step 4.
You may also use these drives in Media Manager storage units, if they are
shared on a SAN.

Using NDMP direct copy

NetBackup uses NDMP direct copy when you duplicate a backup image. Certain
conditions apply to the duplication, explained under “Requirements.” To run a
duplication, you can use any of the following:
■ The Duplicate option in the Catalog node of the NetBackup Administration
Console.
See “Initiate NDMP direct copy with the Administration Console” on
page 60.
■ NetBackup Vault.
Refer to the NetBackup Vault Administrator’s Guide.
■ The bpduplicate command.
Refer to the NetBackup Commands Guide.

Requirements
For NetBackup to use NDMP direct copy when you duplicate an image, note the
following:
60 Configuring NDMP direct copy

Using NDMP direct copy

■ For the destination for the duplication, you must designate an NDMP
storage unit in a VTL or in a physical tape library.
■ An NDMP tape drive must be available to mount the source image. The
NDMP tape drive can be one that was defined in the VTL, or it can be a
physical tape drive in a tape library.
For setup instructions, refer to “NDMP direct copy” on page 58.

If these two requirements are met, NDMP direct copy is enabled. NetBackup

copies the image directly to the designated storage unit without using media

server I/O or network bandwidth.

Note on the NetBackup policy

You can duplicate an image that any NetBackup policy created; the policy need
not be an NDMP policy. See “NDMP direct copy: notes and limitations” on
page 29. The backup can be made to a storage unit in the VTL or to a storage
device that is attached to an NDMP host. You can then copy the backup directly
to a tape drive using the NetBackup Duplicate feature, as follows.

Initiate NDMP direct copy with the Administration Console

1 In the NetBackup Administration Console, expand NetBackup Management
> Catalog.
2 Set up the search criteria for the image you want to duplicate. Click Search
Now.
3 Right-click the image(s) you want to duplicate and select Duplicate from the
shortcut menu.

Note: You must designate an NDMP storage unit as the destination for the
duplication. Use the Storage unit field in the Setup Duplication Variables
dialog box.

For more details on running duplication, refer to “Duplicating backup

images” in the The NetBackup Administrator’s Guide, Volume I.
 Chapter 6
Using the Shared Storage
Option (SSO)
This chapter describes the steps for setting up the Shared Storage Option with

NetBackup for NDMP.

The following topics are covered in this chapter:

■ Shared Storage Option (SSO): diagram

■ Setting up SSO: overview
■ Using the Device Configuration Wizard
62 Using the Shared Storage Option (SSO)
Shared Storage Option (SSO): diagram

Shared Storage Option (SSO): diagram

Figure 6-1 shows a robotic library on a SAN that can share its drives between
two NetBackup for NDMP servers and two NDMP hosts. Drive sharing requires a
license for the Shared Storage Option. A SAN is not required.

Figure 6-1 NDMP backup using Shared Storage Option

LAN

NetBackup NetBackup NDMP NDMP

for NDMP for NDMP host host
server 1 server 2

Fibre Channel SAN

(optional)

NetBackup servers 1 and 2 shared drives in the

tape library for backing up NDMP hosts.
Drives can be in Media Manager storage units
or NDMP storage units, or both.

■ For each robot, either a NetBackup media sever or an NDMP server (not
both) can handle robotic control.
 Using the Shared Storage Option (SSO) 63
Setting up SSO: overview

Setting up SSO: overview

This overview includes an outline of the steps for setting up access to a drive

that is shared between NDMP and NetBackup servers.

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

Guide.

This procedure assumes the following:

■ That the prerequisites for SSO have been met, as described in the
NetBackup Shared Storage Guide.
■ That all physical devices, including the NDMP host, are correctly connected
to the network.
■ That NetBackup for NDMP supports the NDMP host.
For a document that lists supported NAS systems, see “NDMP information
on the Web” on page 29. The NetBackup NDMP Compatibility List indicates
which versions of vendor software support SSO for NDMP. The NAS
systems (hardware) do not provide the support; the proper software version
provides it.

To set up an SSO
1 Configure NetBackup access to the NDMP host.
For details, see “Authorizing access to the NDMP host” on page 36.
2 Verify that the NDMP host can access the required robots and drives.
To verify NDMP host access to the required devices, run the following
commands 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
NDMP host. The -probe option lists the devices that are visible to the
NDMP host.
3 From the NetBackup Administration Console, use the Device Configuration
Wizard to configure the devices and storage units. See “Using the Device
Configuration Wizard” on page 64.

Note: An NDMP storage unit must be defined for each NDMP host that
shares a drive. If all hosts have access to the shared drive(s), the Device
Configuration Wizard can create these storage units automatically.
64 Using the Shared Storage Option (SSO)
Using the Device Configuration Wizard

Using the Device Configuration Wizard

The most convenient way to configure devices and storage units for NDMP hosts
(with or without SSO) is to use the Device Configuration Wizard.
1 In the NetBackup Administration Console, click Configure Storage Devices
to 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 that
accesses the NDMP host.
4 Click the server name to select it and click Change.
 Using the Shared Storage Option (SSO) 65
Using the Device Configuration Wizard

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 to
be Scanned column for the media server.

8 Click Next to continue.

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

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

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

 Chapter 7
Backup and restore
procedures
This chapter describes the procedures for backing up and restoring NDMP-type
policies.
■ Performing an NDMP backup
■ Performing a restore from the server
For backup and restore of a NAS snapshot, refer to the NetBackup Snapshot
Client Administrator’s Guide.
68 Backup and restore procedures
Performing an NDMP backup

Performing an NDMP backup

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

Automatic backup of an NDMP policy

To configure an NDMP policy and set up schedules for automatic, unattended
backups, see the following: “Creating an NDMP policy” on page 46 and the
NetBackup Administrator’s Guide, Volume I.

Manual backup of an NDMP policy

Only a NetBackup administrator can initiate an NDMP backup. The following
procedure explains how to perform the backup using the NetBackup
Administration Console.
For further information on the NetBackup Administration Console, see the
NetBackup Administrator’s Guide, Volume I.

To back up an NDMP policy manually

1 As administrator, start the NetBackup Administration Console on the
NetBackup server in the following way:
On Windows: on the Windows Start menu, click Programs, Veritas
NetBackup, 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 Manual Backup from the
pop-up menu.
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 the
highest retention level. If you do not select any clients, NetBackup backs up
all configured NDMP hosts.
5 Click OK to start the backup.
 Backup and restore procedures 69
Performing a restore from the server

Performing a restore from the server

User-directed restores of files are not allowed, since no NetBackup client

software is installed on an NDMP host.

The administrator can use the Backup, Archive, and Restore interface on a

NetBackup server (master or media server) to restore files to the following: the

NDMP host from which they were backed up or to a different NDMP host.

For help with restoring, see the NetBackup online help in the Administration

Console or the NetBackup Backup, Archive, and Restore Getting Started Guide.

Note the following:

In the Actions > Specify NetBackup Machines and Policy Type dialog box,

specify the following:

■ For the server, select the NetBackup master server. If your configuration has
multiple master servers, specify the master server that has the policy for
the NDMP host that you plan to restore. If the server name is not in the
pull-down list, use Edit Server List to add it.
■ For the source and destination clients, select the appropriate NDMP (NAS)
hosts.

Note: The destination host must be an NDMP host compatible with the data
format of the source. (The source and destination must be of the same NAS
vendor type.)

Caution: An NDMP restore always overwrites existing files.

If the hosts you want are not available in the pull-down, use Edit Client List
to add the client.
■ In the policy type field, select NDMP.
70 Backup and restore procedures
Performing a restore from the server
 Chapter 8
Troubleshooting
The following information may be useful in troubleshooting NetBackup.
■ NDMP operating notes and restrictions
■ Troubleshooting NetBackup
■ Troubleshooting media and devices on Windows
■ Troubleshooting media and devices on UNIX
■ Troubleshooting NDMP direct copy
■ Troubleshooting DAR
■ Testing a robot

Note: For explanations of NetBackup status codes, refer to the “NetBackup

Status Codes and Messages” chapter in the NetBackup Troubleshooting Guide.
72 Troubleshooting
NDMP operating notes and restrictions

NDMP operating notes and restrictions

Before you try to troubleshoot a suspected problem, review the following

operating notes.

To obtain the troubleshooting information that may apply to particular NDMP

hosts, refer to “NDMP information on the Web” on page 29.

■ A tape that was created on an NDMP storage unit is in backup format. It

cannot be restored from a non-NDMP storage unit. If you duplicate an
NDMP backup image, the new copy is still in backup format. It cannot be
used for restores on a non-NDMP storage unit.
■ In the Backup Selections list for an NDMP policy, you can include only
directory paths. 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 Control
Message Protocol) to ping NDMP hosts to verify network connectivity. This
protocol is required for the NetBackup for NDMP product.
■ If backup or restore jobs are running slowly, verify that the network
interface cards (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 able to use the ifconfig (or ipconfig) command, as
explained in the NetBackup Troubleshooting Guide.

Notes on DAR
■ DAR can be used when restoring NetBackup 4.5GA or later backups.
Starting with NetBackup 4.5GA, NetBackup stores the required DAR offset
information on each backup.
■ Backups must have been performed with the NetBackup catalog set to
binary mode. If backups were made with the catalog set to ASCII mode, the
restores cannot use DAR. ASCII mode did not store the required DAR offset
information on each backup. Note that all backups that were made before
NetBackup 4.5 used 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
support DAR. Some NDMP host vendors do not currently support DAR.
 Troubleshooting 73
Troubleshooting NetBackup

Troubleshooting NetBackup
Types of logs
NetBackup uses two types of logging: unified logging and legacy logging. Both
are described in the “Using Logs and Reports” chapter in the NetBackup
Troubleshooting Guide.
Note:
■ 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
next section):
On UNIX: /usr/openv/netbackup/bin/vxlogview
On Windows: install_path\NetBackup\bin\vxlogview
Refer to the NetBackup Troubleshooting Guide for assistance in using the

vxlogview command.

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

Troubleshooting steps
■ Check the NetBackup All Log Entries report for information about the failed
job.
■ To get more information about a problem, do the following:
■ In the NetBackup Administration Console: expand Host Properties in
the left pane, click on Media Server, and right click on the server name
in the right pane. From the pop-up, select Properties, then click
Logging and set the Global logging level to 5. This increases logging
detail to the highest level, for both unified logging and legacy logging.
■ View the unified logging information in /usr/openv/logs (UNIX) or
install_path\logs (Windows) for the following processes:
ndmpagent (originator ID 134), ndmp (originator ID 151), nbpem
(originator ID 116), nbjm (originator ID 117), and nbrb (originator ID
118).
For ndmpagent logs, try the vxlogview command as follows:
/usr/openv/netbackup/bin/vxlogview -i ndmpagent -d T,s,x,p
For ndmp logs, try the vxlogview command as follows:
/usr/openv/netbackup/bin/vxlogview -i ndmp -d T,s,x,p
■ On the NetBackup for NDMP server, create bptm, bpbrm, and
ndmpagent legacy debug log folders in the
74 Troubleshooting

Troubleshooting NetBackup

/usr/openv/netbackup/logs directory (UNIX) or

install_path\NetBackup\logs folder (Windows). NetBackup writes
legacy log files in these directories, if the directories exist.

Note: The legacy and unified logging files can consume a lot of disk space. Delete
the log files when you finish troubleshooting and set logging to a lower level of
detail.

■ To verify that the appropriate services are running, use one of the
following: the NetBackup Activity Monitor, the Windows control panel (on
Windows systems), or the bpps command (UNIX systems).
■ If NDMP host backups terminate with a status code of 154 (storage unit
characteristics 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.
(For example, 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),
no paths in your NDMP policy Backup Selections list backed up. Check the
NetBackup All Log Entries report for more information. A possible cause of
this status is that none of the backup paths exist on the NDMP host.

NDMP backup levels

At the start of a debug log, you may see an entry titled LEVEL. This entry refers
to an environment variable that NetBackup set based on the type of backup. See
the following example from a bptm log.
For more information on environment variables, refer to “Using environment
variables in backup selections list” on page 47.
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

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

FILESYSTEM=/vol/vol0/2million

08:48:38.817 [22923] <2> write_data_ndmp: Environment 3:

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
is a number in the range of 0 to 9.
 Troubleshooting 75
Troubleshooting media and devices on Windows

An NDMP backup level of 0 is a full backup. A backup level greater than 0 is an

incremental backup of all objects that were modified since the last backup of a
lower level. For example, level 1 is a backup of all objects that were modified
since the full backup (level 0). Level 3 is a backup of all objects that were
modified since the last level 2 incremental.

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

NetBackup backup types NDMP backup levels

NetBackup Full NDMP level 0

NetBackup Cumulative Incremental NDMP level 1

NetBackup Differential Incremental NDMP level (last level + 1, up to 9)

never goes higher than 9

Troubleshooting media and devices on Windows

■ For legacy logging, enable debug logging by creating reqlib and daemon
directories in the install_path\Volmgr\debug directory on the NetBackup
for NDMP server.
■ Check the Windows Event Viewer Application log for troubleshooting clues.
For more information on the Event Viewer logging option, refer to the
NetBackup Troubleshooting Guide.
■ Use the Activity Monitor interface or the Windows control panel to verify
that the 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 NetBackup for NDMP server
and the NDMP server application on the NDMP host. Some possible causes
for the communication problems are:
■ Network cable on the NDMP host was unplugged.
■ NIS (Network Information System) problems on the NetBackup for
NDMP server (NDMP client).
■ The NDMP host was halted for too long.

Note: Whatever the cause, if the avrd connection to the NDMP host fails, the
drive is set to DOWN. It is not automatically set to UP when the communication
problem is corrected.
76 Troubleshooting
Troubleshooting media and devices on UNIX

Troubleshooting media and devices on UNIX

■ Ensure that syslogd logs debug messages relating to ltid and other device
processes.
For more information on syslogd, refer to the NetBackup Troubleshooting
Guide.
■ Start ltid with the -v option. Check the system’s syslog for
troubleshooting clues.
■ Use vmps to make sure that the appropriate daemons are running.
■ Drives can be unexpectedly set to the DOWN state. This action is due to
communication problems between avrd on the NetBackup for NDMP server
and the NDMP server application on the NDMP host.
For details, refer to the last main bullet and note under the
“Troubleshooting media and devices on Windows” section.

Troubleshooting NDMP direct copy

When NetBackup enables NDMP direct copy for a backup image duplication, the
NetBackup progress log includes the message “NDMP Direct Copy will be used.”
If NDMP direct copy was not enabled for the duplication, no specific messages
about NDMP direct copy are listed in the progress log. For detailed messages
(such as why NDMP direct copy was not used), consult the legacy debug logs for
the admin log or the bptm log.
Refer to the “Using Logs and Reports” chapter in the NetBackup
Troubleshooting Guide for information on legacy NetBackup logs.

Troubleshooting DAR
In certain situations, one of the following messages may appear in the unified
logs for ndmpagent (originator ID 134) on the NetBackup media server. These
are also written to the progress log.

Message:
DAR disabled - number of files n > DAR_MAXIMUM_FILE_LIST_COUNT x
Explanation:
The number of files being restored is greater than the maximum that is allowed
(default is 1024). You can either select fewer files for the restore, or increase the
DAR maximum Backup Selections list count. (Some NDMP host vendors do not
support increasing the maximum.)
 Troubleshooting 77
Troubleshooting DAR

To increase the DAR maximum Backup Selections list count, place a

“DAR_MAXIMUM_FILE_ LIST_COUNT x” entry in the following file. Specify x as
a number greater than 1024.
On UNIX:
/usr/openv/netbackup/db/config/ndmp.cfg

On Windows:
install_path\NetBackup\db\config\ndmp.cfg

Message:
data host does not support DAR recover

Explanation:

The current NDMP host does not support DAR.

Message:
DAR disabled—continuing restore without DAR

Explanation:

DAR information is not available for the file.

Message:
DAR disabled—backup was performed before NB 4.5
Explanation:
The DAR feature can be used when restoring the backups that NetBackup 4.5GA
or later made. Starting with NetBackup 4.5GA, NetBackup stores the required
DAR offset information on each backup. For pre-4.5GA NetBackup backups,
restores cannot use DAR because the pre-4.5 versions did not store DAR offset
information.

Message:
DAR disabled—NDMP host did not provide DAR info during backup
Explanation:
The backup was performed with an NDMP host version that does not support
DAR. Ask the NDMP host vendor if a later NAS software version is available that
supports DAR.

Message:
DAR disabled—Exceeded optimal DAR parameters for this image size
Explanation:
NetBackup determined that the restore would take longer with DAR than
without it.
78 Troubleshooting

Testing a robot

Message:
DAR disabled—Directory DAR not supported

Explanation:

DAR is automatically disabled when a restore job specifies a directory to restore.

DAR can be used when restoring files, but not when restoring directories.

Message:
DAR disabled by DAR config file
Explanation:
DAR was disabled by adding the entry NDMP_DAR_DISABLED to the following
file:

On UNIX:

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

On Windows:
install_path\NetBackup\db\config\ndmp.cfg

This method of disabling DAR is obsolete.

Use the Host Properties dialog box as explained under “Enabling or disabling

DAR” on page 49.

Message:
DAR disabled by host parameters

Explanation:

DAR was disabled on the Master or Media Server Properties dialog box.

To re-enable DAR, see “Enabling or disabling DAR” on page 49.

Testing a robot
Depending on the type of robot, use the tests in Table 8-2 to exercise the robot:

Table 8-2 Robot types and tests

Robot type Test

TLD tldtest

TL8 tl8test

TLH tlhtest

ACS acstest
 Troubleshooting 79
Testing a robot

TL8 example for Windows

To exercise the TL8 robot c2t3l0 that the NDMP host stripes controls, use
the following test and commands on Windows:

Note: The drive must be down before you perform this test, or avrd may
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 ATTENTION

message, 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 UNIX

To exercise drive 1 in the TLD robot c2t3l0 the NDMP host stripes controls,
use the following commands on UNIX:
/usr/openv/volmgr/bin/tldtest -r stripes:c2t3l0 -d1 stripes:/dev/rmt/Ocbn

At the prompt, enter ? for help information.

inquiry (Displays the Vendor and Product ID. If you get a UNIT ATTENTION

message, 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 UNIX

To 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 drive

can directly attach to the NDMP host.

at the prompt, enter ? for help information.

inv (Inventories the robot.)

drstat (Shows drive status.)

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

80 Troubleshooting
Testing a robot

dm drive_name (Dismounts the tape.)

unload drive_name (Unloads the tape.)
 Chapter 9
Using scripts
This chapter explains how to customize the NDMP-specific notify scripts.

Note: Before you use the notify scripts on UNIX, make sure they are executable
by other. Run chmod 755 script_name, where script_name is the name of the
script.

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

NetBackup for NDMP provides the following scripts (commands on Windows)

for collecting information and providing notification of events.

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

Scripts for UNIX Scripts for Windows

ndmp_start_notify ndmp_start_notify.cmd

ndmp_end_notify ndmp_end_notify.cmd

ndmp_start_path_notify ndmp_start_path_notify.cmd

ndmp_end_path_notify ndmp_end_path_notify.cmd

ndmp_moving_path_notify ndmp_moving_path_notify.cmd

The scripts are similar to those already included in your NetBackup server
installation. To create the scripts on UNIX, copy the bpstart_notify and
bpend_notify scripts from
/usr/openv/netbackup/bin/goodies (UNIX)

to
/usr/openv/netbackup/bin

82 Using scripts

on the NetBackup for NDMP server. Then rename the copied scripts and modify
as needed. You must customize the scripts before using them; see the preceding
note.
On Windows, you must create the scripts from scratch.

ndmp_start_notify (UNIX)

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

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

On the UNIX media server, NetBackup calls the ndmp_start_notify script

each time the client starts a backup operation. To use this script, create a script
similar to
/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 ensure

that you have permission to run it.

The ndmp_start_notify script runs each time a backup starts and after the

tape has been positioned. This script must exit with a status of 0 for the calling

program to continue and for the backup to proceed. A nonzero status causes the

client backup to exit with a status of ndmp_start_notify failed.

If the /usr/openv/netbackup/bin/ndmp_start_notify script exists, it

runs in the foreground. The bptm process that is on the NetBackup for NDMP

server waits for it to complete before continuing. Any commands in the script

that do not end with an & character run serially.

The server expects the client to respond with a continue message within the

period of time that the NetBackup CLIENT_READ_TIMEOUT option on the server

specifies.

The default for CLIENT_READ_TIMEOUT is 300. If the script needs more time

than 300 seconds, increase the value to allow more time.

NetBackup passes the following parameters to the script:

 Using scripts 83

Table 9-2 Script parameters: ndmp_start_notify (UNIX)

Parameter Description

$1 Name of the NDMP host.

$2 Policy name from the NetBackup catalog.

$3 Schedule name from the NetBackup catalog.

$4 One of the following:

FULL
INCR (differential incremental)
CINC (cumulative incremental)

$5 The NetBackup status code for the operation.

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

To create an ndmp_start_notify script for a specific policy or policy and

schedule 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_notify.production

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

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

Note: For a given backup, NetBackup uses only one ndmp_start_notify script
and that is the one with the most specific name. For example, if there are both
ndmp_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
examples of the strings that are available to the script for use in recording
information about a backup:
84 Using scripts

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
scripts that provide notification whenever the client starts a backup. These
scripts must reside on the media server in the following directory:
install_path\NetBackup\bin
Where install_path is the directory where NetBackup is installed.
You can create ndmp_start_notify scripts that provide notification for all
backups or only for backups of a specific policy or schedule. The
ndmp_start_notify script runs each time a backup starts and after the tape is
positioned.
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
or policy and schedule combination, add a .policyname or
.policyname.schedulename suffix to the script name.
■ 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 is
in 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
second script affects scheduled backups in the policy named days only when the
schedule is named fulls.
For a given backup, NetBackup calls only one ndmp_start_notify script and
checks 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 and
ndmp_start_notify.policy.schedule.cmd scripts, NetBackup uses only
the ndmp_start_notify.policy.schedule.cmd script.
 Using scripts 85

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

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

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

Parameter Description

%1 Name of the client from the NetBackup catalog.

%2 Policy name from the NetBackup catalog.

%3 Schedule name from the NetBackup catalog.

%4 One of the following:

FULL
INCR
CINC

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

%6 Results file that NetBackup checks for a return code from the script.
NetBackup uses %6 to pass the 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.sched
ule
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 be considered successful. If the results file
does not exist, NetBackup assumes that the script was successful.
86 Using scripts

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

ndmp_end_notify (UNIX)

Caution: The ndmp_end_notify script is ran at the end of the backup. The
backup does not wait for the script to complete.

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

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

For a UNIX media server, if you need notification whenever the NDMP host
completes 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 that

you 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 9-4 Script parameters: ndmp_end_notify (UNIX)

Parameter Description

$1 Name of the client from the NetBackup catalog.

$2 Policy name from the NetBackup catalog.

$3 Schedule name from the NetBackup catalog.

 Using scripts 87

Parameter Description

$4 One of the following:

FULL
INCR (differential incremental)
CINC (cumulative incremental)

$5 Exit code from bptm.

For example:
ndmp_end_notify freddie cd4000s fulls FULL 0
ndmp_end_notify danr cd4000s incrementals INCR 73
To create an ndmp_end_notify script for a specific policy or policy and
schedule 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_notify.production

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

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

Note: For a given backup, NetBackup uses only one ndmp_end_notify script
and that is the one with the most specific name. For example, if there are both
ndmp_end_notify.production and
ndmp_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
The NetBackup bptm process creates these variables. The following are
examples of the strings that are available to the script for use in recording
information about a backup:
BACKUPID=freddie_0857340526

UNIXBACKUPTIME=0857340526

BACKUPTIME=Sun Mar 2 16:08:46 1997

88 Using scripts

ndmp_end_notify.cmd (Microsoft Windows)

For Windows media servers, you can create the batch scripts that provide
notification whenever the client completes a backup. These scripts must reside
on the media server in the same directory as the NetBackup binaries:
install_path\NetBackup\bin
Where install_path is the directory where NetBackup is installed.

You can create ndmp_end_notify scripts that provide notification for all

backups or only for backups of a specific policy or schedule.

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

script:

install_path\netbackup\bin\ndmp_end_notify.cmd
To create a script that applies only to a specific policy or policy and schedule
combination, add a .policyname or .policyname.schedulename suffix to the script
name.
■ The following script applies only to a policy named days:
install_path\netbackup\bin\ndmp_end_notify.days.cmd
■ The following script applies only to a schedule that is named fulls, which is
in a policy named days:
install_path\netbackup\bin\ndmp_end_notify.days.fulls.cmd
The first script affects all scheduled backups in the policy named days. The
second script affects scheduled backups in the policy named days only when the
schedule is named fulls.
For a given backup, NetBackup calls only one ndmp_end_notify script and
checks for 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 and
ndmp_end_notify.policy.schedule.cmd scripts, NetBackup uses only
ndmp_end_notify.policy.schedule.cmd.

Note: If you also usendmp_start_notify scripts, they can provide a different

level of notification than the ndmp_end_notify scripts. For example, if you
had one of each, they could be ndmp_start_notify.policy.cmd and
ndmp_end_notify.policy.schedule.cmd.

When the backup completes, NetBackup passes the following parameters to the
script:
 Using scripts 89

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

Parameter Description

%1 Name of the client from the NetBackup catalog.

%2 Policy name from the NetBackup catalog.

%3 Schedule name from the NetBackup catalog.

%4 One of the following:

FULL
INCR
CINC

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

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

%6 Results file that NetBackup checks for a return code from the script.
NetBackup uses %6 to pass the 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_END_NOTIFY_RES.policy.schedule
If the script applies to a specific policy, the results file must be named
install_path\netbackup\bin\NDMP_END_NOTIFY_RES.policy
If the script applies to all backups, the results file must be named
install_path\netbackup\bin\NDMP_END_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 be considered successful. If the results file
does not exist, NetBackup assumes that the script was successful.
90 Using scripts

ndmp_start_path_notify (UNIX)

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

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

To use this script, create a script similar to

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

on the server, and copy it to

/usr/openv/netbackup/bin/ndmp_start_path_notify

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

On the UNIX media server, the ndmp_start_path_notify script runs before

the backup process is issued to the NAS machine. This script must exit with a

status of 0 for the calling program to continue and for the backup to proceed. A

nonzero status 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 runs in the foreground. The bptm process on the NetBackup for NDMP

server waits for it to complete before continuing. Any commands in the script

that do not end with an & character run serially.

The server expects the client to respond with a continue message within the

period of time that the NetBackup CLIENT_READ_TIMEOUT option on the server

specifies.

The default for CLIENT_READ_TIMEOUT is 300. If the script needs more time

than 300 seconds, increase the value to allow more time.

NetBackup passes the following parameters to the script:

Table 9-6 Script parameters: ndmp_start_path_notify (UNIX)

Parameter Description

$1 Name of the NDMP host.

$2 Policy name from the NetBackup catalog.

$3 Schedule name from the NetBackup catalog.

 Using scripts 91

Parameter Description

$4 One of the following:

FULL
INCR (differential incremental)
CINC (cumulative incremental)

$5 The NetBackup status code for the operation.

$6 Not used.

$7 The path being backed up.

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

and schedule 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

The first script affects all scheduled backups in the policy that is named
production. The second script affects scheduled backups in the policy that is
named production only when the schedule is named 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 are
both ndmp_start_path_notify.production and
ndmp_start_path_notify.production.fulls scripts, NetBackup uses
only ndmp_start_path_notify.production.fulls.

The ndmp_start_path_notify script can use the following environment

variables:
BACKUPID

UNIXBACKUPTIME

BACKUPTIME

The NetBackup bptm process creates these variables. The following are
examples of the strings that are available to the script for use in recording
information about a backup:
BACKUPID=freddie_0857340526

UNIXBACKUPTIME=0857340526

92 Using scripts

BACKUPTIME=Sun Mar 2 16:08:46 1997

ndmp_start_path_notify.cmd (Microsoft Windows)

For Windows media servers, you can create the batch scripts that provide
notification before the backup process is issued to the NAS machine. These
scripts must reside on the media server in the same directory as the NetBackup
binaries:
install_path\NetBackup\bin
Where install_path is the directory where NetBackup is installed.
You can create ndmp_start_path_notify scripts that provide notification
for all backups or only for backups of a specific policy or schedule.
To create an ndmp_start_path_notify script that applies to all backups,
name the script:
install_path\netbackup\bin\ndmp_start_path_notify.cmd
To create a script that applies only to a specific policy or policy and schedule
combination, add a .policyname or .policyname.schedulename suffix to the script
name.
■ The following script applies only to a policy named days:
install_path\netbackup\bin\ndmp_start_path_notify.days.cmd
■ The following script applies only to a schedule that is named fulls, which in
a policy named days:
install_path\netbackup\bin\ndmp_start_path_notify.days.full
s.cmd
The first script affects all scheduled backups in the policy named days. The
second script affects scheduled backups in the policy named days only when the
schedule is named fulls.
For a given backup, NetBackup calls only one ndmp_start_path_notify
script and 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 and
ndmp_start_path_notify.policy.schedule.cmd scripts, NetBackup uses
only ndmp_start_path_notify.policy.schedule.cmd.
 Using scripts 93

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

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

Table 9-7 Script parameters: ndmp_start_path_notify.cmd (Microsoft

Windows)

Parameter Description

%1 Name of the client from the NetBackup catalog.

%2 Policy name from the NetBackup catalog.

%3 Schedule name from the NetBackup catalog.

%4 One of the following:

FULL
INCR
CINC

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

Parameter Description

%6 Results file that NetBackup checks for a return code from the script.
NetBackup uses %6 to pass the 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_PATH_NOTIFY_RES.policy
.schedule
If the script applies to a specific policy, the results file must be named
install_path\netbackup\bin\NDMP_START_PATH_NOTIFY_RES.policy
If the script applies to all backups, the results file must be named
install_path\netbackup\bin\NDMP_START_PATH_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 be considered successful. If the results
file does not exist, NetBackup assumes that the script was successful.

%7 Pathname being backed up.

ndmp_end_path_notify (UNIX)

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

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

For a UNIX media server, if you need notification whenever the NDMP host
completes 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 that
you have permission to run it.
 Using scripts 95

The ndmp_end_path_notify script runs after the NAS machine has informed

NetBackup that it has completed sending data.

NetBackup passes the following parameters to the ndmp_end_notify script:

Table 9-8 Script parameters: ndmp_end_path_notify (UNIX)

Parameter Description

$1 Name of the client from the NetBackup catalog.

$2 Policy name from the NetBackup catalog.

$3 Schedule name from the NetBackup catalog.

$4 One of the following:

FULL
INCR (differential incremental)
CINC (cumulative incremental)

$5 Exit code from bptm.

$6 Not used.

$7 The path being backed up.

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 and
schedule 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

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

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

script and that is the one with the most specific name. For example, if there are
both ndmp_end_path_notify.production and
ndmp_end_path_notify.production.fulls scripts, NetBackup uses only
ndmp_end_path_notify.production.fulls.
96 Using scripts

The ndmp_end_path_notify script can use the following environment

variables:
BACKUPID

UNIXBACKUPTIME

BACKUPTIME

The NetBackup bptm process creates these variables. The following are
examples of the strings that are available to the script for use in recording
information about a backup:
BACKUPID=freddie_0857340526

UNIXBACKUPTIME=0857340526

BACKUPTIME=Sun Mar 2 16:08:46 1997

ndmp_end_path_notify.cmd (Microsoft Windows)

For Windows media servers, you can create the batch scripts that provide
notification whenever the client is finished writing to tape. These scripts must
reside on the media server in the same directory as the NetBackup binaries:
install_path\NetBackup\bin
Where install_path is the directory where NetBackup is installed.

You can create ndmp_end_path_notify scripts that provide notification for

all backups or only for backups of a specific policy or schedule.

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

the script:

install_path\netbackup\bin\ndmp_end_path_notify.cmd
To create a script that applies only to a specific policy or policy and schedule
combination, add a .policyname or .policyname.schedulename suffix to the script
name.
■ The following script applies only to a policy named days:
install_path\netbackup\bin\ndmp_end_path_notify.days.cmd
■ The following script applies only to a schedule that is named fulls, which is
in a policy named days:
install_path\netbackup\bin\ndmp_end_path_notify.days.fulls.
cmd
The first script affects all scheduled backups in the policy named days. The
second script affects scheduled backups in the policy named days only when the
schedule is named fulls.
For a given backup, NetBackup calls only one ndmp_end_path_notify script
and checks for them in the following order:
ndmp_end_path_notify.policy.schedule.cmd
ndmp_end_path_notify.policy.cmd
 Using scripts 97

ndmp_end_path_notify.cmd
For example, if there are both ndmp_end_path_notify.policy.cmd and
ndmp_end_path_notify.policy.schedule.cmd scripts, NetBackup uses
only ndmp_end_path_notify.policy.schedule.cmd.

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

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

Table 9-9 Script parameters: ndmp_end_path_notify.cmd (Microsoft

Windows)

Parameter Description

%1 Name of the client from the NetBackup catalog.

%2 Policy name from the NetBackup catalog.

%3 Schedule name from the NetBackup catalog.

%4 One of the following:

FULL
INCR
CINC

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

Parameter Description

Note: The following file is not checked when using

%6 ndmp_end_path_notify.
Results file that NetBackup checks for a return code from the script.
NetBackup uses %6 to pass the 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_END_PATH_NOTIFY_RES.policy.sc
hedule
If the script applies to a specific policy, the results file must be named
install_path\netbackup\bin\NDMP_END_PATH_NOTIFY_RES.policy
If the script applies to all backups, the results file must be named
install_path\netbackup\bin\NDMP_END_PATH_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 be considered successful. If the results file does
not exist, NetBackup assumes that the script was successful.

%7 Pathname being backed up.

ndmp_moving_path_notify (UNIX)

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

The UNIX scripts are provided as examples only. You must customize the scripts
before using them. For example, the -ne value in the first if statement must be
modified to reflect the number of passed parameters. For the
ndmp_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/goodies/bpstart_notify

on the server, and copy it to

/usr/openv/netbackup/bin/ndmp_moving_path_notify

on the UNIX NetBackup for NDMP server. Then, modify the script and ensure
that you have permission to run it.
 Using scripts 99

On UNIX media servers, the ndmp_moving_path_notify script runs after the

backup process sends data to NetBackup.

If the /usr/openv/netbackup/bin/ndmp_moving_path_notify script

exists, it runs in the foreground. The bptm process that is on the NetBackup for

NDMP server waits for it to complete before continuing. Any commands in the

script that do not end with an & character run serially.

The server expects the client to respond with a continue message within the

period of time that the NetBackup CLIENT_READ_TIMEOUT option on the

server specifies.

The default for CLIENT_READ_TIMEOUT is 300 seconds. If the script needs

more than 300 seconds, increase the value to allow more time.

NetBackup passes the following parameters to the script:

Table 9-10 Script parameters: ndmp_moving_path_notify (UNIX)

Parameter Description

$1 Name of the NDMP host.

$2 Policy name from the NetBackup catalog.

$3 Schedule name from the NetBackup catalog

$4 One of the following:

FULL
INCR (differential incremental)
CINC (cumulative incremental)

$5 The NetBackup status code for the operation.

$6 Not used.

$7 The path being backed up.

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

and schedule 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_moving_path_notify.production

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

100 Using scripts

The first script affects all scheduled backups in the policy that is named
production. The second script affects scheduled backups in the policy that is
named production only when the schedule is named 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 are both
ndmp_moving_path_notify.production and
ndmp_moving_path_notify.production.fulls scripts, NetBackup uses
only ndmp_moving_path_notify.production.fulls.

The ndmp_moving_path_notify script can use the following environment

variables:
BACKUPID

UNIXBACKUPTIME

BACKUPTIME

The NetBackup bptm process creates these variables. The following are
examples of the strings that are available to the script for use in recording
information about a backup:
BACKUPID=freddie_0857340526

UNIXBACKUPTIME=0857340526

BACKUPTIME=Sun Mar 2 16:08:46 1997

ndmp_moving_path_notify.cmd (Microsoft Windows)

For Windows media servers, you can create the batch scripts that provide
notification whenever the NAS machine starts sending data. These scripts must
reside on the media server in the same directory as the NetBackup binaries:
install_path\NetBackup\bin
Where install_path is the directory where NetBackup is installed.

You can create ndmp_moving_path_notify scripts that provide notification

for all backups or only for backups of a specific policy or schedule.

To create an ndmp_moving_path_notify script that applies to all backups,

name the script:

install_path\netbackup\bin\ndmp_moving_path_notify.cmd
To create a script that applies only to a specific policy or policy and schedule
combination, add a .policyname or .policyname.schedulename suffix to the script
name.
■ The following script applies only to a policy named days:
install_path\netbackup\bin\ndmp_moving_path_notify.days.cmd
 Using scripts 101

■ The following script applies only to a schedule that is named fulls, which is
in a policy named days:
install_path\netbackup\bin\ndmp_moving_path_notify.days.ful
ls.cmd
The first script affects all scheduled backups in the policy named days. The
second script affects scheduled backups in the policy named days only when the
schedule is named fulls.
For a given backup, NetBackup calls only one ndmp_moving_path_notify
script and 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 and

ndmp_moving_path_notify.policy.schedule.cmd scripts, NetBackup
uses only ndmp_moving_path_notify.policy.schedule.cmd.

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

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

Table 9-11 Script parameters: ndmp_moving_path_notify.cmd (Microsoft

Windows)

Parameter Description

%1 Name of the client from the NetBackup catalog.

%2 Policy name from the NetBackup catalog.

%3 Schedule name from the NetBackup catalog.

%4 One of the following:

FULL
INCR
CINC
102 Using scripts

Parameter Description

%5 Status of the operation. It is the same as the status sent to the

NetBackup server. This status is 0 for successful backups and 1 for
partially successful backups. If an error occurs, the status is the value
associated with that error.

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

%6 Results file that NetBackup checks for a return code from the script.
NetBackup uses %6 to pass the 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_END_NOTIFY_RES.policy.sch
edule
If the script applies to a specific policy, the results file must be named
install_path\netbackup\bin\NDMP_END_NOTIFY_RES.policy
If the script applies to all backups, the results file must be named
install_path\netbackup\bin\NDMP_END_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 be considered successful.
If the results file does not exist, NetBackup assumes that the script
was successful.

%7 Pathname being backed up.

 Index

Numerics UNIX 90

Windows 92

10000, port (used by NDMP) 72

overview 22

3pc.conf file 30

procedure 68

three-way, configuring for 37

A types allowed 47

acstest 78
Backup Selections list 47

Activity Monitor interface 75

Add Drive dialog 41, 44

C
Add Robot dialog 40

client list 46

adding

clustering 11, 50

drives 41

Compatibility List, for NDMP 30

Media Manager storage unit 55

configuration

NDMP storage units 44

add Media Manager storage unit 55

robots 38

add NDMP storage unit 44

volumes 42

add volumes 42

authorization

adding drives/robots 38

NDMP user and password 36

Backup Selections list 47

auto discovery of devices 10, 35, 64

check devices 42

avrd 72

client list 46

drive, for NDMP-attached host 41

B for clustering 50

backup
general policy attributes 46

automatic 68
NDMP policy 46

format 72
policy storage unit 46

level (NDMP vs. NetBackup) 74

policy type 46

local vs. three-way 10, 13, 16, 22

robot 38

manual, of NDMP policy 68

schedules 47

ndmp_end_notify script
testing 51

UNIX 86
control panel, Windows 75

Windows 88

ndmp_end_path_notify script
D
UNIX 95

DAR 11, 26

Windows 96

defined 12

ndmp_moving_path_notify script

how to turn on/off 49

UNIX 99

data mover 30

Windows 100

debug logs 73

ndmp_start_notify script

deinstallation

UNIX 82

server 34

Windows 84

Device Configuration Wizard 10, 35, 64

ndmp_start_path_notify script

104 Index

Device Monitor 42
M
devices

mover.conf file 30

troubleshooting 75, 76

different client restore 13

Direct Access Recovery (see DAR)

N
direct copy, NDMP 26, 58, 76
NAS snapshot 11, 35, 36, 46, 54, 67

drives
nbjm 73

adding, for NDMP-attached host 41

nbpem 73

configuring 38
nbrb 73

duplex mode and performance 72

NDMP

access web info 29

E backup, manual 68

client type 46

environment variables, in Backup Selections list 47

client, definition of 12

exclude

Compatibility List 30

files, using SET directive 47

direct copy 11, 26, 58, 76

list, using 47

how to configure 58

licensing 58

F VTL license 29

fail over 50
host, definition of 12

file list 47
LEVEL, related to NetBackup backups 74

file names (not allowed in Backup Selections

policy

list) 47, 72
adding 46

attributes 46

clients 46

H files 47

Hardware Compatibility List 30

schedules 47

High Availability 11, 50

policy storage unit attribute

configuration 46

I
policy type

configuration 46

ICMP protocol 72

overview 18

installation 31

protocol 12, 14, 72

deinstallation 34

restore 69

load from media 32

restrictions 72

prerequisites 31

server application, definition of 12

instant recovery 11

storage unit, adding 44

storage unit, definition of 13

J to media server 12, 37, 46, 54

jnbSA 68
how to configure 54

ndmp logging 73

NDMP to media server 10, 17

L ndmp_end_notify script

LEVEL (NDMP backup) 74

UNIX 86

log directories 73, 75, 76

Windows 88

ltid
ndmp_end_path_notify script

restarting 42
UNIX 95

Windows 96

ndmp_moving_path_notify script
 Index 105

UNIX 99
restart

Windows 100
device manager 40

ndmp_start_notify script
Media Manager device daemon 42

UNIX 82
restore

Windows 84
local vs. three-way 13, 16, 22

ndmp_start_path_notify script
overview 24

UNIX 90
overwriting files 69

Windows 92
procedure 69

ndmpagent
three-way 24

legacy debug log 73

to different client 13, 18

unified logging 73
restrictions

NetBackup Administration Console 68

NetBackup for NDMP 72

NetBackup for NDMP

robot

configuration 35, 57
adding 38

definition 9
supported types 19

features 10
test device configuration 78

installation 31
robot connection
server, definition 12
verifying 43

troubleshooting 73
Robot Control Host, for volume 43

network interface cards 72

robots

NIC cards and full duplex 72

configuring 38

notification scripts 81

S
O schedules 47

off-host backup scripts

with data mover 30

notification 81

on demand storage unit 45

SET directive 48

operating notes and restrictions 72

Shared Storage Option (see SSO)

Override policy storage unit, setting 47

Snapshot Client 11

overwriting files 69
access web info 30

snapshots 11

SnapVault 11, 46

P SSO 10

password configuration overview 63

verifying 37, 43
storage devices

path length limit 72

auto discovery 10, 35

path-based history 11
storage unit

peripherals (latest info on web) 29, 30

adding 44

ping 72
media manager type 54

point-in-time snapshots 11
NDMP type, overview 19

policy
specify for NDMP policy 46

attributes 46
support web site 29, 30

port 10000 (used by NDMP) 72

supported robots 19

protocol supported (NDMP) 10, 35

T
R tape libraries supported 19

remote NDMP 54
tape server 16

reserved environment variables 47

terminology, NetBackup for NDMP 12

106 Index

testing configuration 51
third-party copy device 30
three-way backup 13
configuring for 37
tl8test 78
tldtest 78
tlhtest 78, 79
tpautoconf 43, 63
troubleshooting 71
type
of backup allowed 47

of policy 46

U
unified logging 73
uninstalling NetBackup 34
user-directed
backups and archives 18
backups and archives, not allowed 68
restores, not allowed 69

V
variables, environment 47
vendors (latest info on) 29
verifying NDMP password 37
version supported (NDMP) 10, 35
Virtual tape Library
see VTL
Virtual Tape Option license 29
volumes, adding 42
VTL 11, 26, 58, 76
license 29
licensing 58
vxlogview 73

W
web access
to NDMP info 30
to Snapshot Client info 30
wildcards, in Backup Selections list 47, 72
Windows control panel 75