NetBackup NAS Appliance Support Guide

Symantec TechNote 267773
NetBackupTM for NDMP:

NAS Appliance
Information
This TechNote 267773 provides up-to-date information on the Network
Attached Storage (NAS) appliances supported by NetBackup for NDMP. Also
included are configuration tips and restrictions for each supported NAS
appliance.
Supported operating systems

For an up-to-date list of supported operating systems, and for notes on
supported hardware platforms, refer to the following NetBackup OS
Compatibility List:
For NetBackup 6.x:
http://entsupport.symantec.com/docs/325328
For NetBackup 7.x:
Note that NDMP compatibility is listed as a column in the NetBackup Server
section for each OS platform in the above NetBackup 7.x Operating System
Compatibility List.
See also the NetBackup Release Notes.
Note: NetBackup for NDMP is installed on a master or media server, not on a

client.
2/17/10
2 NetBackupTM for NDMP: NAS Appliance Information Symantec Corporation
NAS appliance versions 2/17/10
NAS appliance versions

For a document listing the features and software releases for each NAS vendor,
and for the NetBackup versions that support these vendors, refer to the
following compatibility lists:
■ For versions of NetBackup through 6.0:
■ For NetBackup 6.5.x:
■ For NetBackup 7.x:
Authorizing NetBackup access to the NDMP host

■ For NetBackup 5.1 and earlier, use the following commands to authorize
NetBackup access to the NDMP host (NAS filer):
set_ndmp_attr -auth ndmp-server-host username password
set_ndmp_attr -verify ndmp-server-host
where ndmp_server_host identifies the NDMP host that NetBackup will
be backing up, and username is the username under which NetBackup will
access the NDMP host. If your NDMP host requires a particular username or
access level, see the section in this document on that NDMP host. For more
information on authorizing access for NetBackup, refer to the NetBackup
for NDMP Administrator’s Guide for your NetBackup release.
■ For NetBackup 6.0 or later, use the tpconfig and tpautoconf commands
as described under “Example Configuration Sequence” in each of the
following sections of this document for particular NDMP hosts.
Note on file restore to a different location

When restoring files from NetBackup backups of NAS filers that use older
versions of the NDMP protocol (V2 and V3), the destination path for the restore
must end with the original folder and file name, even if you are restoring the
files to a different location. (This restriction does not apply to NAS filers that
use the NDMP protocol V4.)
If the original backup path was /vol/vol1/mydir/myfile, the destination path for
restore to a different location must end with /mydir/myfile. Otherwise,
NetBackup appends /mydir/myfile to the end of the destination path.
For example, to restore /vol/vol1/mydir/myfile to a folder under /vol/vol2/,
specify /vol/vol2/mydir/myfile as the destination.
http://entsupport.symantec.com/docs/267773 Symantec TechNote

Symantec Corporation NetBackupTM for NDMP: NAS Appliance Information 3
2/17/10 Note on file restore to a different location
For NAS filers that use NDMP V4, you can specify a different subfolder or file
name. /vol/vol1/mydir/myfile can be restored, for example, to
/vol/vol2/mydir2/myfile_restored.
For any restrictions unique to a particular NAS filer, see the appropriate section
in this document for your filer.
Symantec TechNote http://entsupport.symantec.com/docs/267773

agámi systems 2/17/10
agámi systems
This information is provided to help you use NetBackup for NDMP with an
agámi Information Server (AIS) system. It is intended as a supplement to the
NetBackup for NDMP Administrator’s Guide.
For further details on the AIS system, please contact agámi Systems.
Known restrictions
The AIS supports three-way and remote NDMP backup, but does not support
local NDMP backup. NDMP backup types are described in the NetBackup for
NDMP Administrator's Guide.
AIS logs
To obtain diagnostic logs, use the AIS management console to access the
Support Diagnostic page. Select Create New File to create a new AIS diagnostic
log.
Tips for control and configuration

■ To monitor system status, access the AIS management console to sign into
the AIS. Go to System Status and select the Event Viewer.
■ To enable NDMP, use the AIS management console and select File System
Management > file system name > Protocols and Access > Add/Edit
Protocols. Select Enable NDMP backups and apply changes.
■ For the usage of set FILE_ID, see the following:
■ agámi Information Server Administrator's Guide (GUI)
■ agámi Information Server Administrator's Guide (CLI)
■ agámi Information Server Release Notes
Tips for robot and media discovery

Please refer to the chapter that describes remote NDMP in the NetBackup for
NDMP Administrator’s Guide.
Example configuration sequence

1 Enter the following to authorize NetBackup 6.0 or later to access the AIS.
(See “Authorizing NetBackup access to the NDMP host” for assistance with
earlier NetBackup releases.)
tpconfig -add -nh agami_host -user_id user_id -password password

2/17/10 agámi systems
tpautoconf -verify agami_host

Example output from the -verify option:
Connecting to host "agami_host" as user "admin"...
Waiting for connect notification message...
Opening session--attempting with NDMP protocol version 3...
Opening session--successful with NDMP protocol version 3
host supports TEXT authentication
Logging in using TEXT method...
Host info is:
host name "h-00d054623ef1.localdomain"
os type "GNU/Linux"
os version "2.6.7-aruba_1.2.41869"
host id "7f0100"
Login was successful
Host supports 3-way backup/restore
2 Using the Media and Device Management utility in the NetBackup
Administration Console, define robots, drives, and storage units, then create
a backup policy. These procedures are described in the NetBackup for NDMP
Administrator’s Guide.
Direct access recovery

DAR is supported by the AIS and by the following versions of NetBackup:
■ NetBackup Feature Pack 4.5_3_F and later 4.5 Feature Packs
■ NetBackup 5.0 and later versions
For NAS hosts that support DAR, NetBackup enables DAR by default.
Other
■ The following are example entries for the NetBackup policy’s Backup
Selections list (file list):
set HIST=y
set TYPE=atar
set UPDATE=y
/export/vol2
■ The AIS supports path-based history with NetBackup 4.5 or later.
Path-based history is enabled by means of the set HIST=y entry shown
above.

BlueArc titan 2/17/10
BlueArc titan
This information is provided to help you use NetBackup for NDMP with a
BlueArc Titan system. It is intended as a supplement to the NetBackup for NDMP
For further details, refer to the following BlueArc documentation or contact
BlueArc Corporation:
■ BlueArc Titan System Administration Guide
Known restrictions
The BlueArc supports only inode-based backup (Backup type = dump).
BlueArc titan logs

To display logs for the BlueArc Titan, use a web browser to log in to the System
Management Unit. Select Home > Status & Monitoring > Event Log.

For monitoring and configuration tasks, use a web browser to log in to the
System Management Unit and select the following.
■ To monitor system status, select Home > Status & Monitoring > System
Monitor.
■ To set the NDMP user and password, select Home > Data Protection > NDMP
Configuration. Set the NDMP version to 4.
■ To discover and allow access to tape devices, select Home > Data Protection
> Backup SAN Management.

To discover devices on a BlueArc Titan, you can use the tpautoconf -probe
command. For example (for local NDMP backup):
tpautoconf -probe bluearc_host
Example output:
Host "bluearc_host" SCSI device model "ATL P1000 6220052.0":
Device "/dev/mc_d0l0" attributes=0x0
Host "bluearc_host" tape device model "QUANTUM DLT7000
256qe":
Device "/dev/mt_d0l1" attributes=(0x4) RAW
Device "/dev/mt_d0l1r" attributes=(0x5) REWIND RAW
Host "bluearc_host" tape device model "QUANTUM DLT7000
256qe":

2/17/10 BlueArc titan
Device "/dev/mt_d0l2" attributes=(0x4) RAW

Device "/dev/mt_d0l2r" attributes=(0x5) REWIND RAW

1 Enter the following to authorize NetBackup 6.0 or later to access the
BlueArc Titan system and its robot. (See “Authorizing NetBackup access to
the NDMP host” for assistance with earlier NetBackup releases.)
tpconfig -add -nh bluearc_host -user_id ndmp -password ndmp
tpautoconf -verify bluearc_host
Connecting to host "bluearc_host" as user "ndmp"...
host supports MD5 authentication
Getting MD5 challenge from host...
Logging in using MD5 method...
Host info is:
host name "bluearc_host"
os type "BOS"
os version "3.3"
host id "b313425de63a:1"
Host supports LOCAL backup/restore
Direct access recovery (DAR)

DAR is supported by the BlueArc Titan and by the following versions of
NetBackup:
Other
■ Directory entry/inode-based history (file history) is supported with
NetBackup 4.5 or later.

BlueArc titan 2/17/10
To enable file-based history, enter the following as the first entry on the
NetBackup policy’s Backup Selections tab (file list):
SET HIST=y

2/17/10 DinoStor TapeServer
DinoStor TapeServer
This information is provided to help you use NetBackup for NDMP and one or
more NAS servers (NDMP hosts) with a DinoStor TapeServer. It is intended as a
supplement to the NetBackup for NDMP Administrator’s Guide.
For further details on the DinoStor TapeServer, refer to the DinoStor TapeServer
User Guide, or contact the DinoStor division of Global Automation, Inc.
DinoStor TapeServer enables NetBackup to send backups of any supported NAS
server to a tape device configured on the TapeServer. This is a form of three-way
backup; three-way backup is described in the NetBackup for NDMP
Known restrictions
None.
DinoStor TapeServer logs

To display logs, use a browser to log in to the DinoStor TapeServer web
interface. Select Monitor > Log.
On the DinoStor TapeServer

For configuration tasks on the DinoStor TapeServer, use a browser to log in to
the TapeServer web interface and select the following:
■ To set up a SCSI device, select Configure > SCSI (if the robot is SCSI
connected).
■ To set up a FC device, select Configure > FC (if robot is FC connected).
■ To set up DNS, interfaces, and gateway information, select Configure >
Network.
Note: To use a TapeServer with NetBackup, two IP addresses must be configured

in the Interfaces section of the TapeServer web interface: one IP address for the
backup data stream and the other for control management.
On NetBackup
Using the Media and Device Management utility in the NetBackup
Administration Console, define robots, drives, and storage units, then create (or
DinoStor TapeServer 2/17/10
modify) a backup policy. These procedures are described in the NetBackup for
NDMP Administrator’s Guide. Note the following when configuring NetBackup
for a DinoStor TapeServer.
■ When defining a robot in the Add a New Robot dialog, specify the device
name of the DinoStor TapeServer (not of the robot) in the Robot device path
field, and specify the DinoStor TapeServer host name in the NDMP host
name field. For example, referring to the output shown below for
tpautoconf -probe, the device name of the DinoStor TapeServer to
specify in the Robot device path field would be sgh2-0c0i1l1, and the
host name to specify in the NDMP host name field would be dinostor.
■ When defining a storage unit for DinoStor TapeServer in the New Storage
Unit dialog, specify the DinoStor TapeServer host name in the NDMP Host
field.
■ In the NetBackup policy, specify the storage unit that you created for the
DinoStor TapeServer.

To discover devices on a DinoStor TapeServer, you can use the tpautoconf
-probe command. For example:
tpautoconf -probe dinostor
Example output:
Host "dinostor" SCSI device model "Scalar 24 ":
Device "sgh2-0c0i1l1" attributes=0x0
Host "dinostor" tape device model "ULTRIUM-TD3 ":
Device "sth2-0c0i1l0" attributes=(0x5) REWIND RAW
EXECUTE_CDB=b
Device "nsth2-0c0i1l0" attributes=(0x4) RAW
EXECUTE_CDB=b

DinoStor TapeServer and its robot. (See “Authorizing NetBackup access to
tpconfig -add -nh dinostor_host -user_id ndmp -password ndmp
tpautoconf -verify dinostor_host
Connecting to host "dinostor_host" as user "ndmp"...

2/17/10 DinoStor TapeServer

Host info is:
host name "dinostor_host"
os type "DinoStor OS"
os version "4.0"
host id "50232"
2 See under “On NetBackup” on page 9 for NetBackup configuration
instructions.

DAR support depends on the NAS server (NDMP host) you are backing up. Refer
to the appropriate NAS server section of this document.
Other
None.

EMC celerra 2/17/10
EMC celerra
This information is provided to help you use NetBackup for NDMP with an EMC
Celerra Network Server. It is intended as a supplement to the NetBackup for
For more information on your Celerra Network Server, refer to the Celerra
Network Server Version 5.5 Documentation CD, which can be downloaded from
EMC's Powerlink web site.
Known restrictions
The username used with the tpconfig command must be defined as ndmp for
each data mover.
EMC celerra logs

The logs are located on each Data Mover. For example, to access the server_2
Data Mover log file, you would enter the following at the Celerra Network Server
Control Station:
server_log server_2

■ After logging on to the Celerra Network Server Control Station, you can use
the following commands:
nas_version
(Displays the Celerra version number)
server_devconfig
(Queries the device configuration of the specified Data Mover)
■ Make sure the backup is created from a snapshot. See the following:
“NDMP policy should specify snapshot-based backup” on page 16.

Check that each Data Mover is recognizing the robot/media devices by entering
the server_devconfig command from the Control Station.
For example:
server_devconfig server_2 -list -probe -scsi -nondisks
The above command queries the device configuration of the specified Data
Mover (server_2).
Example output:

2/17/10 EMC celerra
server_2 :
SCSI non-disk devices :
chain= 0, scsi-0
symm_id= 0 symm_type= 0
tid/lun= 15/15 type= disk val= -99 info= 52658653C310 diskerr=
-1
chain= 1, scsi-1
tid/lun= 15/15 type= disk val= -99 info= 52686043C320 diskerr=
-1
chain= 2, scsi-2 : no devices on chain
chain= 3, scsi-3
tid/lun= 0/0 type= jbox info= HP C5173-7000 3.04
tid/lun= 1/0 type= tape info= QUANTUM DLT7000 2560q`
tid/lun= 2/0 type= tape info= QUANTUM DLT7000 2560q`
Alternate means of finding robot and media device file names

NetBackup 4.5 and higher provides a new method of discovering devices
attached to a NAS host. This is the -probe option on the tpautoconf
command. The -probe option requires NDMP protocol version 3.
tpautoconf -probe celerra_host
Example output:
Host "celerra_host" SCSI device model "C5173-70":
Device "c3t0l0" attributes=0x0
Host "celerra_host" tape device model "DLT7000 ":
Device "c3t1l0" attributes=(0x0)
COMPRESSION=
Host "celerra_host" tape device model "DLT7000 ":
Device "c3t2l0" attributes=(0x0)
COMPRESSION=
Where celerra_host is the name of the Data Mover, c3t0l0 is the robot
device file, and c3t1l0 and c3t2l0 are the tape device file names.
Robot
Use the tpconfig command to set attributes for an NDMP-attached robot.
For example:
tpconfig -add -robot 8 -robtype tld -robpath c3t0l0 -nh celerra_host
-bus 3 -target 0 -lun 0
Where:
■ celerra_host is the name of the Data Mover. This is also the NDMP host
name to be specified on the Add Robot display in the NetBackup
Administration Console. For assistance, refer to “Adding a Robot Directly
Attached to an NDMP Host” in the NetBackup for NDMP Administrator’s
Guide.

EMC celerra 2/17/10
■ c3t0l0 is the device name for the robotic controller. This is also the Robotic
device to be specified on the Robot Control display. Refer to “Adding a Robot
Directly Attached to an NDMP Host” in the NetBackup for NDMP
■ 3 is the chain number (the bus number).
■ 0 is the target ID or tid of the robot control.
■ 0 is the LUN number.
Media devices
EMC Celerra Network Servers have only one device file per tape drive. Use this
device file when configuring the tape device files for use with NetBackup for
NDMP.
Following is an example of a device name (on UNIX, this is called the No Rewind
Device), to be entered on the Add Drive display in the NetBackup Administration
Console:
celerra:c3t2l0
Where celerra is the external Data Mover name and c3t2l0 is the tape device
file name. This example file name is for the second DLT tape drive listed in the
example output for server_devconfig command on the previous page.

1 Enter the following to authorize NetBackup 6.0 or later to access the Data
Mover and its robot. (See “Authorizing NetBackup access to the NDMP host”
for assistance with earlier NetBackup releases.)
tpconfig -add -nh celerra_host -user_id ndmp -password password
tpconfig -add -robot 8 -robtype tld -robpath c3t0l0 -nh
celerra_host -bus 3 -target 0 -lun 0
tpautoconf -verify celerra_host
Connecting to host "celerra_host" as user "ndmp"...
Host info is:
host name "celerra_host"
os type "DartOS"
os version "Symmetrix Network File Storage.T.2.2.53.310"
host id "abc5368"

2/17/10 EMC celerra
Opening SCSI device "c3t0l0"...

Setting SCSI target controller 3 id 0 lun 0...
Inquiry result is "HP C5173-7000 3.04.53."

DAR is supported by the EMC Celerra (contact EMC for the required OS level)
and by the following versions of NetBackup:
For celerra network server version 5.5 software and above

EMC Celerra Network Server version 5.5 and later software supports file and
directory exclude lists with wild cards, in the NetBackup policy’s Backup
Selections list (file list).
Celerra Network Server version 5.5 and later software also supports NDMP
Volume Backup.
File and directory exclusion statements

In the policy’s Backup Selections list, file and directory exclusion statements
can be used with the set directive. The statements are named
EMC_EFILE[01-05] for file exclusion, and EMC_EDIR[01-05] for directory
exclusion, in the following form (see examples below):
set EMC_EFILExx=file_exlusion_statement
set EMC_EDIRxx=/directory_exlusion_statement
where xx is a two-digit number.
For restrictions in the use of these statements and other details such as the use
of wild cards, refer to the Celerra Network Server Version 5.5 Documentation
CD.
Examples of file and directory exclude statements in a Netbackup Backup

selections list
set HIST=y
set TYPE=tar
set EMC_EDIR01=/fs2/l*
set EMC_EDIR02=/fs2/Ndmp*

EMC celerra 2/17/10
set EMC_EDIR03=/fs2/NAS*
set EMC_EDIR05=/fs2/j*
set EMC_EFILE01=*tar
set EMC_EFILE03=*dat
set EMC_EFILE02=*dat
set EMC_EDIR04=/fs2/Millions
set UPDATE=y
/fs2
In the above example, the backup of /fs2 will not include the files and
directories specified by the EMC_EDIR and EMC_EFILE statements.
NDMP policy should specify snapshot-based backup

To make sure that the backup is based on data that is transactionally consistent,
the following should be the first entry in the NetBackup policy Backup
Selections list:
set snapsure=yes
The Celerra Server creates a snapshot and the backup is created from the
snapshot. The snapshot is managed by the EMC Celerra, not by NetBackup.
NDMP volume backup (VBB)

The NetBackup policy’s Backup Selections list can specify that the backup is
performed using EMC’s NDMP Volume Backup.
Example of NDMP volume backup entries in the Backup Selections list:

set snapsure=yes
set type=vbb
/testfs
In the above example, /testfs will be backed up using NDMP Volume Backup.
For restrictions and other information on NDMP Volume Backup, refer to the
“Configuring NDMP Backups on Celerra” technical module on the Celerra
Network Server Version 5.5 Documentation CD. This CD is downloadable from
the EMC Powerlink web site.
Other
■ If you specify an incorrect path name in the NetBackup policy’s Backup
Selections list (file list), the entire backup fails with status code 99, “NDMP
backup failure.”
■ Path-based history is supported with NetBackup 4.5 or later.
To enable path-based history, enter the following as the first entry in the
NetBackup policy’s Backup Selections list:
set type=tar

2/17/10 EMC centera with centera backup and recovery Module (CBRM)
EMC centera with centera backup and recovery

Module (CBRM)
This information is provided to help you use NetBackup for NDMP with an EMC
CBRM system. This information is intended as a supplement to the NetBackup
for NDMP Administrator’s Guide.
For more information on your Centera and the CBRM, refer to the following
documentation or contact EMC Corporation:
■ EMC CBRM Installation and Administrator’s Guide
Known restrictions
■ Backup and restore times on the CBRM running with NetBackup are
noticeably longer than expected. EMC is working to resolve this issue.
■ The CBRM is currently limited to single-threaded backups and restores. EMC
is working to resolve this issue.
■ The CBRM cannot run on the same NetBackup master server where
NetBackup for NDMP is running, because both NetBackup Remote NDMP
and CBRM utilize the same port for internal communication.
■ The CBRM does not allow redirected restores to an alternate path. If you
attempt to restore to an alternate path (or to an invalid path), the CBRM
restores the data to the original path.
■ The CBRM does not allow cross platform restores. For example, if the backup
was made by means of a CBRM installed on Windows, the backup cannot be
restored using a CBRM installed on Solaris.
■ The CBRM supports full backups (Level=0) and cumulative/incremental
backups (Level=1) only.
■ Changing the CBRM .res profile file while a backup is running may cause the
backup job to hang or fail.
■ The CBRM currently does not support local NDMP.
■ The CBRM BEGIN_DATE and END_DATE in the .res profile are automatically
deleted when the current backup job is completed.
EMC CBRM logs

There are two kinds of EMC CBRM logs to examine: SDK logs and NDMP logs.

EMC centera with centera backup and recovery Module (CBRM) 2/17/10
To capture SDK logs:

Set the FPLIBRARY_LOG_FILE_DEBUG and export environment parameters
on the CBRM host, as follows.
UNIX
For example, on a Solaris CBRM machine:
setenv FPLIBRARY_LOG_FILE_DEBUG /temp/mylog.log
setenv export FPLIBRARY_LOG_FILE_DEBUG
Windows
Use the Control Panel > System > Advanced tab > Environment Variables,
System Variables area. Enter the following two system variables:
■ Click New. For Variable Name, enter FPLIBRARY_LOG_FILE_DEBUG
For Variable Value, enter the location of the log file, such as
C:\temp\mylog.log
■ Click New. For Variable Name, enter export
For Variable Value, enter /xpd
To capture NDMP logs:

1 Set the NDMPD_XARGS environment parameter on the CBRM host, as
follows.
UNIX
For example, on a Solaris CBRM machine, add the following (all on one line)
to the end of the inetd.conf file:
ndmp stream tcp nowait root /usr/EMC_CBRM/bin/ndmpd ndmpd -l -xpd
Windows
Use the Control Panel > System > Advanced tab > Environment Variables,
System Variables area to enter the NDMPD_XARGS system variable:
■ Click New. For Variable Name, enter NDMPD_XARGS
For Variable Value, enter /xpd
2 Set CENTERA_DEBUG=4 in the .res profile on the CBRM host.
3 For the changes to take effect, restart the NDMP services on the CBRM host.

To view the roles, software version, and state of each Centera node, log in to the
Centera by means of the Centera Viewer and select Commands > Diagnostics.
The Node Summary lists the roles, software version, and state of each node.
For additional information on the EMC CBRM, refer to the EMC CBRM
Installation and Administrator's Guide.

2/17/10 EMC centera with centera backup and recovery Module (CBRM)

Please refer to the chapter that describes Remote NDMP in the NetBackup for

Enter the following to authorize NetBackup 6.0 or later to access the EMC
Centera CBRM host. (See “Authorizing NetBackup access to the NDMP host” for
assistance with earlier NetBackup releases.) The NDMP user ID specified on the
following command must have root or administrator privilege on the host where
the CBRM is installed. Note that the CBRM host is separate from the EMC
Centera.
tpconfig -add -nh cbrm_host -user_id user_ID -password password
tpconfig -add -robot 8 -robtype tld -robpath c3t0l0 -nh
cbrm_host -bus 3 -target 0 -lun 0
tpautoconf -verify cbrm_host
Example output from tpautoconf -verify:
Connecting to host "cbrm_host" as user "root"...
Host info is:
host name "cbrm_host"
os type "SunOS"
os version "5.9"
host id "80b34ef5"

DAR is supported by the EMC Centera and by the following versions of
NetBackup:
Other
■ The following are required entries in the NetBackup policy’s Backup
Selections tab (file list). No other entries should be made in the NetBackup
Backup Selections tab.

EMC centera with centera backup and recovery Module (CBRM) 2/17/10
Except for the file name for the profile, these must be entered exactly as
shown below:
set profile=file_name
set type=centera
set hist=y
set fstype=ufs
/centera
where set profile=file_name specifies the name of the CBRM .res
profile.
Note: Make sure to include the IP address of the EMC Centera host in the CBRM
.res profile:
Centera_IP=xxx.xx.xx.xxx
■ Path-based history is supported with NetBackup 4.5 or later, and is enabled

by means of the set hist=y entry shown above.

2/17/10 Hitachi lightning NAS blade
Hitachi lightning NAS blade

This information is provided to help you use NetBackup for NDMP with the
Hitachi Lightning NAS Blade system. It is intended as a supplement to the
NetBackup for NDMP Administrator's Guide.
For further details on the Hitachi Lightning system, please contact Hitachi
Corporation.
Known restrictions
■ The Hitachi Lightning currently supports NetBackup remote NDMP backups
only. Remote NDMP backups are a form of three-way backup described in
the NetBackup for NDMP Administrator’s Guide.
■ The Hitachi Lightning allows only one NDMP connection for non-backup
operations.
For example, if a restore operation is running, you cannot perform another
restore operation on another file system on the same node of the Hitachi
Lightning at the same time.
■ The Hitachi Lightning does not allow multiple backup operations to occur
from the same file system.
For example, if you have a policy running a backup of /dir1, you cannot run
another policy that backs up /dir1/subdir1 at the same time.
Hitachi lightning logs

To display logs, use a web browser to log in to the Hitachi Network Attached
Storage interface on the Hitachi Lightning.
1 On the main menu, under Maintenance, click RAS Management.
2 For Info type, select List of other log files and click Display.
3 Select the desired file type and click Display.

To monitor system status, use a web browser to log in to the Hitachi Network
Attached Storage interface on the Hitachi Lightning.
◆ On the main menu, under Basics, click Cluster Management. The cluster
should be active and at least one of the nodes should be listed in the UP
state.

Hitachi lightning NAS blade 2/17/10

To discover robots and media for a configuration that utilizes the Hitachi
Lightning, use the NetBackup Device Configuration Wizard, or refer to the
NetBackup Administrator’s Guide, Volume I.

Enter the following to authorize NetBackup 6.0 or later to access the Hitachi
Lightning system and its robot. (See “Authorizing NetBackup access to the
NDMP host” for assistance with earlier NetBackup releases.)
tpconfig -add -nh hds_host -user_id root -password password
tpautoconf -verify hds_host
Connecting to host "hds_host" as user "root"...
Host info is:
host name "hds_host"
os type "Linux"
os version "2.4.17-enas0200-SI20K022"
host id "500c261a"

DAR is supported by the Hitachi Lightning NAS system version 02-02 or higher
Other
■ The Hitachi Lightning supports path-based history with NetBackup 4.5 or
later.
■ On the NetBackup Administration Console, in the Backup Selections tab of
the backup policy, you must use the set directive to specify the files or
directories to back up.

2/17/10 Hitachi lightning NAS blade
Note: You must use the set directive in exactly the format shown below,
otherwise the backup will fail.
Example entries in Backup Selections tab:
Explanation
set files=directory_to_back_up
Specifies the directory or file that you want to back up. For example:
set files=dir1
Note: This entry must NOT have a space or a slash after the equal sign (=).
The following entries are not allowed:
Set files=/dir1 (do not put a / after the = )
set files= dir1 (do not put a space after the = )
set type=tar
This is a required entry.
/mnt/file_system
Specifies the mounted file system on the Hitachi Lightning containing the
files to back up. For example, /mnt/hitachi05.

Hitachi lightning NAS blade 2/17/10
Note: This entry must start with a slash, and must NOT have a trailing slash if
the Hitachi Lightning NAS system version is earlier than 02-02 (version 02-02
supports a trailing slash).
mnt/hitachi01 (a leading slash is required)
/mnt/hitachi01/ (do not use a trailing slash if the Hitachi Lightning version
is prior to 02-02)

2/17/10 Hitachi TagmaStore
Hitachi TagmaStore
Hitachi TagmaStore AMS/WMS NAS Modular system and the TagmaStore
USP/NSC NAS Blade system. It is intended as a supplement to the NetBackup for
NDMP Administrator's Guide.
The following information applies to both the AMS/WMS and USP/NSC systems
unless otherwise noted. For further details on your Hitachi TagmaStore system,
please contact Hitachi Data Systems.
Known restrictions
■ The Hitachi TagmaStore currently supports NetBackup remote NDMP
backups only. Remote NDMP backups are a form of three-way backup
described in the NetBackup for NDMP Administrator's Guide.
■ NetBackup policy directives in the Backup Selections list cannot omit the
TYPE variable because NetBackup assumes TYPE=dump by default.
■ Only one backup job is allowed per file system when “set SNAPSHOT=Y” is
specified in the NetBackup policy’s Backup Selections list.
■ The Hitachi TagmaStore AMS 1000/500 and USP/NSC allow up to five
simultaneous jobs per NAS unit (the number of backup and restore jobs
together must not exceed five). The Hitachi TagmaStore AMS 200/WMS 100
allow up to two simultaneous jobs per NAS unit (the number of backup and
restore jobs together must not exceed two).
Hitachi TagmaStore system logs

To display logs, use the NetBackup Administration Console:
1 In the NetBackup Administration Console on the master server, open the
Activity Monitor and click on the NetBackup job for which you want to view
log details.
2 From the Actions menu, select Details, then click on the Detailed Status tab.
3 Search for messages with “KAQB” or “KAQS” in the prefix.

Use a browser to log in to the Hitachi Network Attached Storage interface on the
Hitachi TagmaStore system.

Hitachi TagmaStore 2/17/10
■ To monitor system status: on the main menu, select Cluster Management

and click Display. The cluster should be active and at least one of the nodes
should be listed in the UP state.
■ To enable NDMP: select Backup/Restore and click Display. Then select
NDMP Server Control and select the start/restart button.

None.

1 Enter the following to authorize NetBackup 6.0 or later to access the Hitachi
TagmaStore system and its robot. (See “Authorizing NetBackup access to
tpconfig -add -nh hds_host -user_id user_id -password password
Updated host "hds_host"
tpautoconf -verify hds_host
Connecting to host "hds_host" as user "<userid>"...
Host info is:
host name "hds_host"
os type "Linux"
os version "2.4.17-enas0400-SI40K011-1"
host id "500a436c"

DAR is supported by the Hitachi TagmaStore and by the following versions of
NetBackup:
2/17/10 Hitachi TagmaStore
Other
■ The Hitachi TagmaStore supports path-based history with NetBackup 4.5 or
later.
To enable path-based history, enter the following at the top of the list on the
set HIST=f
■ On the NetBackup Administration Console, in the NetBackup policy’s
Backup Selections tab, you must use the set directive to specify the files or
directories to back up.
Note: Use the set directive in exactly the format shown below, otherwise the
backup will fail.
Example entries in Backup Selections tab:
Explanation
set files=directory_to_back_up
Specifies the directory or file that you want to back up. For example,
set files=dir1
Note: This entry must NOT have a space or a slash after the equal sign (=).
set files=/dir1 (do not put a / after the = )
set files= dir1 (do not put a space after the = )
set type=tar

Hitachi TagmaStore 2/17/10
This is a required entry. Note that uppercase values such as TAR are not
supported.
/mnt/file_system
Specifies the mounted file system on the Hitachi TagmaStore system
containing the files to back up. For example, /mnt/hitachi05.
Note: This entry must start with a slash. The following entry is not allowed:
mnt/hitachi01 (a leading slash is required)

2/17/10 IBM system Storage nxxxx
IBM system Storage nxxxx

This information is provided to help you use NetBackup for NDMP with an IBM
System Storage Nxxxx filer. It is intended as a supplement to the NetBackup for
For further details, refer to the following documentation.
■ Data ONTAP Command Reference Guide
■ Data ONTAP System Administrator's Guide
Known restrictions
The username used with the tpconfig command must be defined as root for
each data mover. See “Example configuration sequence” on page 32.
IBM nxxxx logs

The logs on the IBM Nxxxx filer must be viewed through an NFS or CIFS mount
point. On the IBM filer, general messages appear in /etc/messages.

■ The NDMP service is controlled by means of the Data ONTAP administrative
interface or the following commands:
ndmpd on
(Starts the NDMP service)
ndmpd off
(Stops the NDMP service)
ndmpd status
(Displays the status of the NDMP service including any active NDMP
sessions)
ndmpd probe session-number
(Displays details about the specified session)
■ By default, the NDMP service is not started at boot time. To start it, add the
following line to the end of the /etc/rc file on the IBM system:
ndmpd on
■ To determine the number of objects in a volume, enter the following:
maxfiles
Tips for robot and drive discovery

The IBM administrative interface can be used to list the attached tape drives and
robotic devices.

IBM system Storage nxxxx 2/17/10
Robot
To display the robot device file, sign on to the IBM Nxxxx host and enter the
following command:
sysconfig -m
The names are of the format mcN, where N is 0 or higher.
For example:
Medium changer (6a.4) HP C6280-7000
mc0 - medium changer device
Media devices
To display tape device files, enter the following command:
sysconfig -t
Always use the drive names that begin with “nr” (such as nrst0a) because these
are the non-rewinding devices.
Example sysconfig output:
Tape drive (6a.5) Quantum DLT7000
rst0l - rewind device, format is: 81633 bpi 40 GB (w/comp)
nrst0l - no rewind device, format is: 81633 bpi 40 GB (w/comp)
urst0l - unload/reload device, format is: 81633 bpi 40 GB (w/comp)
rst0m - rewind device, format is: 85937 bpi 35 GB
nrst0m - no rewind device, format is: 85937 bpi 35 GB
urst0m - unload/reload device, format is: 85937 bpi 35 GB
rst0h - rewind device, format is: 85937 bpi 50 GB (w/comp)
nrst0h - no rewind device, format is: 85937 bpi 50 GB (w/comp)
urst0h - unload/reload device, format is: 85937 bpi 50 GB (w/comp)
rst0a - rewind device, format is: 85937 bpi 70 GB (w/comp)
nrst0a - no rewind device, format is: 85937 bpi 70 GB (w/comp)
urst0a - unload/reload device, format is: 85937 bpi 70 GB (w/comp)

NetBackup 4.5 and later provides a new method of discovering devices attached
to a NAS host. (Note: the IBM Nxxxx is supported by NetBackup 5.x or later.) The
discovery method is the -probe option on the tpautoconf command. The
-probe option requires NDMP protocol version 3.
For example:
tpautoconf -probe IBM_host
Example output (in this example, IBM_host is the name of the filer):
Host "IBM_host" SCSI device model "HP C6280-7000 ":
Device "mc0" attributes=0x0
ELECTRICAL_NAME=6a.4
SERIAL_NUMBER=
WORLD_WIDE_NAME=
ALIAS 0=mc6
Host "IBM_host" tape device model "Quantum DLT7000":
Device "rst0l" attributes=(0x1) REWIND
DENSITY=81633 bpi 40 GB (w/comp)

SERIAL_NUMBER=CX909S1735
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0l" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0l" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0m" attributes=(0x1) REWIND
DENSITY=85937 bpi 35 GB
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0m" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0m" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0h" attributes=(0x1) REWIND
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0h" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0h" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8

IBM system Storage nxxxx 2/17/10
Device "rst0a" attributes=(0x1) REWIND

WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0a" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0a" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Following is an example of a device name (on UNIX, it is called the No Rewind
Console:
IBM_host:nrst0a
where IBM_host is the name of the IBM filer, and nrst0a is the non-rewinding
device.

1 Enter the following to authorize NetBackup 6.0 or later to access the filer
and its robot. (See “Authorizing NetBackup access to the NDMP host” for
assistance with earlier NetBackup releases.)
tpconfig -add -nh IBM_host -user_id root -password password
tpconfig -add -robot 8 -robtype tld -robpath mc0 -nh IBM_host
tpautoconf -verify IBM_host
Connecting to host "IBM_host" as user "root"...
Host info is:
host name "IBM_host"
os type "IBM"
os version "Data ONTAP Release 7.1.0.1P2"
host id "0084248481"



DAR is supported by the IBM filer and by the following versions of NetBackup:
■ NetBackup Feature Pack 4.5_3_F and later 4.5 Feature Packs (the IBM Nxxxx
requires NetBackup 5.x or later)
Other
If you eject a tape from an IBM Nxxxx-attached drive and then try to open the
device, it will reload the tape. This happens when the device is still UP and the
NetBackup automatic-volume-recognition daemon (avrd) polls it.

Isilon IQ 2/17/10
Isilon IQ
This information is provided to help you use NetBackup for NDMP with an Isilon
IQ system. It is intended as a supplement to the NetBackup for NDMP
Administrator's Guide.
For further details on an Isilon IQ system, please contact Isilon Systems.
Known restrictions
None.
Isilon IQ logs
The NDMP logs can be found at /var/log/isi_ndmp_d on each node.

For the following tasks, access the management browser to sign in to the
system.
■ To monitor system status, go to Alerts to view alert activity.
■ To enable NDMP, select Backup > Configuration, select the username and
password, and enable the NDMP service state.

None.

1 Enter the following to authorize NetBackup 6.0 or later to access the Isilon
IQ system and its robot. (See “Authorizing NetBackup access to the NDMP
host” for assistance with earlier NetBackup releases.)
tpconfig -add -nh isilon_host -user_id username -password
password
tpautoconf -verify isilon_host
Connecting to host "isilon_host" as user "root"...
Host info is:

2/17/10 Isilon IQ
host name "isilon_host"

os type "Isilon OneFS"
os version "v3.0"
host id "10.43.92.110"

DAR is supported by the Isilon IQ system and by the following versions of
NetBackup:
Other
Path-based history is supported with NetBackup 4.5 or later.
set HIST=f

Mirapoint 2/17/10
Mirapoint
Mirapoint server. It is intended as a supplement to the NetBackup for NDMP
For more information on your Mirapoint host, refer to the following
documentation or contact Mirapoint Inc.
■ Mirapoint System Software Setup and Administration Guide
Known restrictions
■ Mirapoint 3.6 supports local, three-way, and remote-NDMP backup.
■ Mirapoint only supports one attached robot and one attached tape drive.
The tape drive can be standalone or in the robot.
■ Mirapoint does not allow concurrent backups or restores.
■ Mirapoint only allows backup or restore of the /usr/store directory, not
of subdirectories under /usr/store. Please refer to Mirapoint
documentation regarding selective backup and restore.
■ For backup, the /usr/store directory must be specified with no trailing
slash; /usr/store/ is not allowed.
■ Mirapoint supports type=image only.
■ The default Mirapoint user ID for ndmp is administrator. This ID is user
selectable.
■ Mirapoint does not allow redirection of a restore to a different path (the
restore will fail).
■ Mirapoint must be rebooted after a successful full restore to remount the file
system.
Mirapoint logs
Contact Mirapoint support for the collection of logs on the Mirapoint host.

Please refer to the Mirapoint documentation.

2/17/10 Mirapoint

After you telnet into the Mirapoint host using the appropriate port number, you
can use the following commands to discover more information about the robot
and tape drive. The quotation marks must be entered exactly as they appear
below.
diag tape inquiry ““ ““ ““
(Returns the tape inquiry string)
diag changer inquiry ““ ““ ““
(Returns the inquiry string for the changer/robot)
diag get tapeaddress
(Returns the controller, target, and LUN for the tape drive)
diag get changeraddress
(Returns the controller, target, and LUN for the changer/robot)
Tape
For either a tape drive in a robot or a standalone tape, the local NDMP drive path
is: /dev/nrsa0
Robot
Since Mirapoint supports only one robot device, the device name for the robot
controller will be /dev/ch0.
To discover the controller, target, and LUN for the robot device:
1 Telnet into the Mirapoint host with the appropriate port number (refer to
your Mirapoint documentation).
telnet mirapoint port_number
Example output
Trying 244.87.21.47...
Connected to mirapoint.mirapoint.com.
Escape character is '^]'.
OK mirapoint.mirapoint.com admind 3.0 server ready
User: administrator
Password:
OK User logged in
mirapoint.mirapoint.com>
2 To obtain the controller, target and LUN of the robot controller, enter the
following.
diag get changeraddress
Example output:
Controller 3, Target 3, Lun 0
OK Compelete
Enter quit to terminate the telnet session.

Mirapoint 2/17/10
3 For NetBackup 6.0 or later, use the tpconfig command to set attributes for
an NDMP-attached robot.
For example:
tpconfig -add -robot 8 -robtype tld -robpath /dev/ch0
-nh mirapoint_host -bus 3 -target 3 -lun 0

Mirapoint host and its robot. (See “Authorizing NetBackup access to the
tpconfig -add -nh mirapoint_host -user_id administrator
-password password
tpautoconf -verify mirapoint_host
Connecting to host "mirapoint_host" as user "administrator"...
Host info is:
host name "mirapoint_host"
os type "Mirapoint"
os version "3.0.0.29-EA"
host id "76b2b2d"
Opening SCSI device "/dev/ch0"...
Inquiry result is "HP C6280-7000 2.07"

Mirapoint does not currently support DAR.
Other
■ For incremental backups, the NetBackup policy file list (or Backup Selections
tab) must contain the following as the first entry in the list:
set UPDATE=y

2/17/10 Mirapoint
■ After doing a restore, the Mirapoint host must be rebooted by pressing its
reset button. Because of the reboot of the Mirapoint host, the NetBackup
automatic-volume-recognition daemon (avrd) sets the drive to the DOWN
state. You must set the drive to the UP state in order to run backups and
restores.
■ Path-based history (file history) is supported with NetBackup 4.5 or later.
To enable path-based history (needed for selective restore), enter the
following at the top of the list on the NetBackup policy’s Backup Selections
tab (file list):
set HIST=y
To turn off path-based history:
set HIST=n
For further details, refer to Mirapoint documentation.

NEC iStorage NV series 2/17/10
NEC iStorage NV series

This information is provided to help you use NetBackup for NDMP with an NEC
iStorage NV Series file server. It is intended as a supplement to the NetBackup
For more information on the NEC iStorage NV Series, refer to the following
documentation:
■ NEC iStorage NV Series Users Guide
■ NEC iStorage NV Series Maintenance Manual
For further details, please contact NEC Corporation.
Known restrictions
■ The NEC iStorage NV Series supports the NDMP protocol version V2 only.
■ The NEC iStorage NV Series can only back up file systems, not
sub-directories.
■ Only one backup or restore can be running per file system. For example, if a
backup job is currently backing up /export/sxfs/vol1, another attempt
to back up or restore /export/sxfs/vol1 at the same time will fail.
■ A second backup of the same file system could fail if started too soon after
the first backup of that file system. This is because a backup job needs time
to delete the snapshot after completion of the backup. Until the snapshot is
deleted, the second backup of the same file system cannot start. The same is
true for restores: a restore of a file system could fail if started too soon after
a previous restore of that file system.
NEC NV series logs

Sign in to the NEC iStorage NV Series through a telnet session and add the
following lines to the /etc/sysconfig/ndmpd file:
LOGFILE=/var/dumpfile/ndmpd
DEBUG=yes
LEVEL=65535
Debug logs are located in the /var/dumpfile/ndmpd directory.

Use a browser to sign in to the NEC iStorage Manager IP interface to do the
following:
■ Monitor system status.

2/17/10 NEC iStorage NV series
■ Enable NDMP service in the NEC iStorage: enter your NEC license key for the
NDMP option and then start NDMP in the Service section.

Robot
To find the robot device name, telnet into the NEC iStorage and enter:
dmesg | grep “scsi generic”
Example output:
Attached scsi generic sg0 at scsi0, channel 0, id 0, lun 0, type
8
The robot device is /dev/sg0.
Drives
To find the tape device names, telnet into the NEC iStorage and enter:
dmesg | grep “scsi tape”
Example output:
Attached scsi tape st0 at scsi0, channel 0, id 1, lun 0
Attached scsi tape st1 at scsi0, channel 0, id 2, lun 0
The tape device names, to be entered on the Add Drive display in the NetBackup
Administration Console, are /dev/nst0 for tape drive 1 and /dev/nst1 for
tape drive 2. Always use the drive names that begin with “n” because these are
the non-rewinding devices.

1 Enter the following to authorize NetBackup 6.0 or later to access the NEC
iStorage NV Series and its robot. (See “Authorizing NetBackup access to the
tpconfig -add -nh NEC_host -user_id root -password password
tpconfig -add -robot 8 -robtype tld -robpath /dev/sg0
-nh NEC_host -bus 0 -target 0 -lun 0
tpautoconf -verify NEC_host
Host info is:
host name "NEC_host"
os type "NEC iStorage"
os version "2.4.17-NEC1143smp"
host id "500c345b"

NEC iStorage NV series 2/17/10

Opening SCSI device "/dev/sg0"...
Inquiry result is "STK L40 0212"

The NEC iStorage NV Series does not currently support DAR.
Other
The following directive must be placed at the start of the NetBackup policy’s
Backup Selections tab (file list):
set XFS=yes
This directive must be specified for all NetBackup backups of the NEC iStorage
NV Series, otherwise the backup will fail. Note that the set XFS=yes directive
must be specified for both XFS and XFSFW file systems.

2/17/10 NetApp
NetApp
NetApp NAS (Network Attached Storage) filer. It is intended as a supplement to
For further details, refer to the following documentation or contact NetApp.
■ Data ONTAP Command Reference Guide
■ Data ONTAP System Administrator's Guide
Known restrictions
■ The username used with the tpconfig command must be defined as root
for each data mover. See “Example configuration sequence” on page 47.
■ When restoring files, if the NetApp filer does not use Direct access recovery
(DAR), the destination path that you specify for the restore must end with
the original folder and file name. If the original backup path was
/vol/vol1/mydir/myfile, the destination path for the restore must end with
/mydir/myfile. Otherwise, NetBackup appends /mydir/myfile to the end of
the destination path.
For more details on DAR, and to determine whether DAR has been disabled
in NetBackup, refer to the NetBackup for NDMP Administrator's Guide.
NetApp logs
The logs on the NetApp filer must be viewed through an NFS or CIFS mount
point. On the NetApp filer, general messages appear in /etc/messages.

■ For NDMP devices to share tape drives, tape reservation must be enabled in
the ONTAP software on the filer as well as in NetBackup. You can use either
SCSI persistent reservation or SCSI reservation. To share tape drives, note
that the drive itself must support one of these types of reservation.
To enable SCSI reservation in Data ONTAP, enter either of the following at

the ONTAP command line on the filer:
options tape.reservations scsi
options tape.reservations persistent
To enable SCSI reservation in the NetBackup Administration Console, go to

Host Properties > Media Servers > double click the media server >
Properties > Media. Make sure to select the same type of SCSI reservation as
you set on the filer.

NetApp 2/17/10
■ In ONTAP 8.0, both ONTAP 7 mode and ONTAP 10 mode are combined into a
single release. You cannot run both modes on the same filer concurrently.
■ The NDMP service is controlled by means of the Data ONTAP administrative
interface or the following commands:
ndmpd on
(Starts the NDMP service)
ndmpd off
(Stops the NDMP service)
ndmpd status
(Displays the status of the NDMP service including any active NDMP
sessions)
ndmpd probe session-number
(Displays details about the specified session)
■ By default the NDMP service is not started at boot time. To start it, add the
following line to the end of the /etc/rc file on the NetApp system:
ndmpd on
■ To determine the number of objects in a volume, enter the following:
maxfiles
Tips for robot and drive discovery

The NetApp administrative interface can be used to list the attached tape drives
and robotic devices.
Robot
To display the robot device file, sign on to the NetApp host and enter the
following command:
sysconfig -m
The names are of the format mcN, where N is 0 or higher.
For example:
Medium changer (6a.4) HP C6280-7000
mc0 - medium changer device
Media devices
To display tape device files, enter the following command:
sysconfig -t
Always use the drive names that begin with “nr” (such as nrst0a) because these
are the non-rewinding devices.
Example sysconfig output:
Tape drive (6a.5) Quantum DLT7000
rst0l - rewind device, format is: 81633 bpi 40 GB (w/comp)
nrst0l - no rewind device, format is: 81633 bpi 40 GB (w/comp)

2/17/10 NetApp
urst0l - unload/reload device, format is: 81633 bpi 40 GB (w/comp)

rst0m - rewind device, format is: 85937 bpi 35 GB
nrst0m - no rewind device, format is: 85937 bpi 35 GB
urst0m - unload/reload device, format is: 85937 bpi 35 GB
rst0h - rewind device, format is: 85937 bpi 50 GB (w/comp)
nrst0h - no rewind device, format is: 85937 bpi 50 GB (w/comp)
urst0h - unload/reload device, format is: 85937 bpi 50 GB (w/comp)
rst0a - rewind device, format is: 85937 bpi 70 GB (w/comp)
nrst0a - no rewind device, format is: 85937 bpi 70 GB (w/comp)
urst0a - unload/reload device, format is: 85937 bpi 70 GB (w/comp)

NetBackup 4.5 and higher provides a new method of discovering devices
attached to a NAS host. This is the -probe option on the tpautoconf
command. The -probe option requires NDMP protocol version 3.
For example:
tpautoconf -probe netapp
Example output (in this example, netapp is the name of the filer):
Host "netapp" SCSI device model "HP C6280-7000 ":
Device "mc0" attributes=0x0
SERIAL_NUMBER=
WORLD_WIDE_NAME=
ALIAS 0=mc6
Host "netapp" tape device model "Quantum DLT7000":
Device "rst0l" attributes=(0x1) REWIND
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0l" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0l" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0m" attributes=(0x1) REWIND
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0m" attributes=(0x0)

NetApp 2/17/10
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0m" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0h" attributes=(0x1) REWIND
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0h" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0h" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "rst0a" attributes=(0x1) REWIND
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "nrst0a" attributes=(0x0)
WORLD_WIDE_NAME=
ALIAS 0=st8
Device "urst0a" attributes=(0x2) UNLOAD
WORLD_WIDE_NAME=
ALIAS 0=st8
Console:
netapp:nrst0a

2/17/10 NetApp
where netapp is the name of the NetApp filer, and nrst0a is the
non-rewinding device.

tpconfig -add -nh netapp_host -user_id root -password password
tpconfig -add -robot 8 -robtype tld -robpath mc0 -nh netapp_host
tpautoconf -verify netapp_host

Connecting to host "netapp_host" as user "root"...
Opening session with NDMP protocol version 3...
Host info is:
host name "netapp_host"
os type "NetApp"
os version "NetApp Release 6.1.2R1"
host id "0019567533"
Opening SCSI device "mc0"...
Inquiry result is "SPECTRA 215 101400"

DAR is supported by the NetApp filer (contact NetApp for the required OS level)

NetApp 2/17/10
Other
Tape ejection
If you eject a tape from a NetApp-attached drive and then try to open the device,
it will reload the tape. This happens when the device is still UP and the
NetBackup automatic-volume-recognition daemon (avrd) polls it.
Image Backup (smtape)

Image Backup is a new Data ONTAP 8.0 feature (formerly referred to as
SnapMirror to Tape, or smtape). This feature backs up a volume as a single file.
Note: Only the entire volume can be restored; files within the volume cannot be
restored individually.
Image Backup is supported with the following NetBackup versions and later
maintenance packs (MP) of the same release:
■ NetBackup 4.5 MP8/FP8
■ NetBackup 5.0 MP4
■ NetBackup 5.1 MP2
■ NetBackup 6.x
■ NetBackup 7.x
NetApp filers running Data ONTAP 7.0.1 or higher support SnapMirror to Tape,
which provided the same functionality as Image Backup but required approval
through a NetApp Product Variance Request (PVR) form. For that reason, this
functionality has not been included in previous NetBackup documentation.
Environment variables needed in the NetBackup policy

The following environment variables should be entered in the NetBackup
policy's Backup Selections tab (file list):
SET type = smtape

SET SMTAPE_DELETE_SNAPSHOT = Y
/volume_to_back_up
Notes on the environment variables:

■ SET type = smtape
Specifies the image backup feature.
■ SET SMTAPE_DELETE_SNAPSHOT = Y

2/17/10 NetApp
Use this variable if you want the snapshot to be deleted after the backup
completes. A snapshot is taken of the volume before the backup is written to
tape. Deleting the snapshot saves storage space.
■ /volume_to_back_up
Specifies the volume you want backed up. For example: /vol/vol1

NetApp Data ONTAP GX 2/17/10
NetApp Data ONTAP GX

NetApp Data ONTAP GX NAS (Network Attached Storage) filer. It is intended as
a supplement to the NetBackup for NDMP Administrator's Guide.
For further details, refer to the following documentation or contact NetApp.
■ Data ONTAP 10.0 Administration Guide
Known Restrictions
■ Use of the tpautoconf -probe command for device discovery is not
supported in local NDMP configurations with the NetApp Data ONTAP GX.
■ Directory DAR is not supported with the NetApp Data ONTAP GX.
■ When restoring files, if the NetApp filer does not use Direct access recovery
(DAR), the destination path that you specify for the restore must end with
the original folder and file name. If the original backup path was
/vol/vol1/mydir/myfile, the destination path for the restore must end with
/mydir/myfile. Otherwise, NetBackup appends /mydir/myfile to the end of
the destination path.
For more details on DAR, and to determine whether DAR has been disabled
in NetBackup, refer to the NetBackup for NDMP Administrator's Guide.
NetApp Logs
The logs on the NetApp Data ONTAP GX filer must be viewed through a SSH
session. NDMP logs are located in /mroot/log/ndmpd.log.
Tips for Control and Configuration

■ For NDMP devices to share tape drives, tape reservation must be enabled in
the ONTAP software on the filer as well as in NetBackup. You can use either
SCSI persistent reservation or SCSI reservation. To share tape drives, note
that the drive itself must support one of these types of reservation.
To enable SCSI reservation in Data ONTAP, enter either of the following at

the ONTAP command line on the filer:
options tape.reservations scsi
options tape.reservations persistent
To enable SCSI reservation in the NetBackup Administration Console, go to

Host Properties > Media Servers > double click the media server >
Properties > Media. Make sure to select the same type of SCSI reservation as
you set on the filer.

2/17/10 NetApp Data ONTAP GX
■ In ONTAP 8.0, both ONTAP 7 mode and ONTAP 10 mode are combined into a
single release. You cannot run both modes on the same filer concurrently.
■ All volumes on the NetApp Data ONTAP GX filer are created within Virtual
Servers.
■ The path specified in the NetBackup policy’s Backup Selections list must
contain the Virtual Server. For example:
/vs1/vol1
Tips for Robot and Drive Discovery

The NetApp Data ONTAP GX Web interface can be used to list the attached tape
drives and robotic devices.
Robot
To display the robot device file, sign on to the NetApp host and go to SYSTEM >
hardware > tape > library.
The names are of the format:
/robot/switchname~switch_port_number.target
For example:
/robot/brocade18~23.126
Media Devices
The names are of the format:
/tape/nr.switchname~switch_port_number.targetLlun.a
where Llun indicates the LUN.
For example:
/tape/nr.brocade18~23.126L2.a
Example Configuration Sequence

tpconfig -add -nh netappGX_host -user_id root -password password
tpconfig -add -robot 8 -robtype tld -robpath
/robot/brocade18~23.126 -nh netappGX_host -bus 0
-target 0 -lun 0
tpautoconf -verify netapp_host
Connecting to host "netappGX_host" as user "root"...

NetApp Data ONTAP GX 2/17/10

Host info is:
host name "Data ONTAP GX series"
os type "NetApp"
os version "NetApp Release 10.0.3X9"
host id "1111111111"
Opening SCSI device "/robot/brocade18~23.126"...
Inquiry result is "EMC Disk Library 2.00"
Direct Access Recovery (DAR)

DAR is supported by the NetApp filer (contact NetApp for the required OS level)
Other
To back up a volume as a single file, see “Image Backup (smtape)” on page 48.

2/17/10 ONStor NAS gateway: SF4400 and bobcat 2200 series
ONStor NAS gateway: SF4400 and bobcat 2200

series
ONStor NAS Gateway. It is intended as a supplement to the NetBackup for NDMP
Administrator’s Guide. For other ONStor details, refer to your ONStor
documentation.
Known restrictions
None.
ONStor NAS gateway logs

To display logs for the ONStor NAS Gateway, log onto the NAS Gateway
Manager (NGM) and click Elogs > View Logs.

■ To monitor system status, use the NAS Gateway Manager (NGM) to sign into
the system. The IP node should be green.
■ To view volumes/shares, click on Volumes/Shares. A table of volumes with
their corresponding status should appear in the right pane, as shown below.

ONStor NAS gateway: SF4400 and bobcat 2200 series 2/17/10

To discover robots and media for a configuration that utilizes the ONStor NAS
Gateway, please refer to the NetBackup for NDMP Administrator’s Guide.

1 Enter the following to authorize NetBackup 6.0 or later to access the ONStor
NAS Gateway system and its robot. (See “Authorizing NetBackup access to
tpconfig –add -nh ONStor_host -user_id Admin -password password
tpautoconf –verify ONStor_host
Sample output:
Connecting to host "ONStor_host" as user "ndmp"...
Host info is:
host name "ONStor_host"
os type "ONStor EverON"
os version " R1.2.1.1-111804 "
host id "0402046578"

DAR is supported by ONStor NAS Gateway and by the following versions of
NetBackup:

2/17/10 ONStor NAS gateway: SF4400 and bobcat 2200 series
Other
■ The ONStor NAS Gateway supports path-based history with NetBackup 4.5
or later.
■ The ONStor NAS Gateway also supports the following environmental
parameters in the NetBackup policy’s Backup Selections tab (file list).
For more detail on these parameters, refer to your ONStor documentation.
■ RECURSIVE=(y, n) (default is y)
■ TYPE= (default is tar)
■ LEVEL= (default is 0)
■ UPDATE=(y, n) (default is y)
■ ONSTOR_OVERWRITE=(y, n) (default is y)
■ ONSTOR_EXTRACT_8.3=(y, n) (default is y)

Overland storage: NEO gigabit ethernet option (GEOn) 2/17/10
Overland storage: NEO gigabit ethernet option

(GEOn)
This information is provided to help you use NetBackup for NDMP using the
Overland Storage GEOn system. It is intended as a supplement to the NetBackup
for NDMP Administrator's Guide. For further details on an Overland system,
please contact Overland Storage.
Known restrictions
The GEOn system is designed for NDMP three-way backups only.
GEOn logs
To generate trace logs for the GEOn pertaining to a particular issue, do the
following.
1 Log into the GEOn by means of the Overland console, or from a remote host
through telnet.
2 At the Ready prompt, enter:
set tracelog enabled
3 Enter:
saveconfiguration
4 Reproduce the issue that you want to log.
5 To create a trace log and display it to the screen, enter:
dumptracelog
You can highlight portions of the output and copy them to a file. Or you can
enter the script file_name command prior to running dumptracelog,
and the dumptracelog output is written to the file specified on the
script command.
6 Continued logging can impact performance. To disable logging, enter:
set tracelog disabled
7 To save this configuration (with logging disabled), enter:
saveconfiguration

Log in to the Overland Storage web interface to do the following.

2/17/10 Overland storage: NEO gigabit ethernet option (GEOn)
To obtain the current status of the NDMP service in the GEOn

◆ Click Advanced and enter the NDMPStatus command in the CLI command
box and click Submit.
Or telnet to the GEOn and enter the NDMPStatus command.
To have NDMP devices automatically mapped

1 Select Mapping.
2 Click the Automap button.
3 Click the Submit button.

To discover devices on a GEOn system, you can use the NetBackup tpautoconf
-probe command. For example:
tpautoconf -probe testhost
Example output:
Host "testhost" SCSI device model "OVERLAND NEO Series ":
Device "/dev/sg/Mc0" attributes=0x4
EXECUTE_CDB=b
Host "testhost" tape device model "HP Ultrium 2-SCSI ":
Device "/dev/rmt/Tape0" attributes=(0x4) RAW
EXECUTE_CDB=b
Host "testhost" tape device model "HP Ultrium 2-SCSI ":
Device "/dev/rmt/Tape1" attributes=(0x4) RAW
EXECUTE_CDB=b

1 Enter the following to authorize NetBackup 6.0 or later to access the GEOn
system and its robot. (See “Authorizing NetBackup access to the NDMP
host” for assistance with earlier NetBackup releases.)
tpconfig -add -nh testhost -user_id User_ID -password password
tpconfig -verify testhost
Sample output:
Connecting to host "testhost" as user "User_ID"...
Host info is:
host name "Neo2"
os type "AEOS"
os version "1.0"

Overland storage: NEO gigabit ethernet option (GEOn) 2/17/10
host id "20000058493004?0"

DAR is supported by the GEOn and by the following versions of NetBackup:
Other
None.

2/17/10 Pillar data systems axiom
Pillar data systems axiom

Axiom system from Pillar Data Systems (Pillar). It is intended as a supplement to
For further details on the Axiom storage system, please consult the Pillar Data
Systems web site: www.pillardata.com.
Known restrictions
None.
Pillar logs
Do the following to access the logs.
1 Log on to the Axiom Storage Manager GUI.
2 Click the Support button and then select Collect System Information under
the Tools menu on the left.
3 From the Actions pull-down menu in the bottom-middle of the window,
select Collect System Information.
4 Select the desired items from the Collection Scope list.
Collecting system information can take several minutes depending on the
items selected.
5 After collection of system information completes, select Download
Information to Client from the Actions pull-down menu and select the
location to save the System Information (it will be a tar file).

NDMP settings should be checked on the Pillar Axiom system and verified to
correspond to the Veritas defined configuration. From the Axiom Storage
Manager GUI, navigate to Data Protection > NDMP Backup Settings > Modify
NDMP Backup Settings. This location also turns the NDMP port on and off on
the Axiom system.
For additional Axiom configuration information, refer to the Pillar Axiom

Pillar data systems axiom 2/17/10

To discover robot and media for a configuration that utilizes a Pillar Data Axiom
system, use the -probe option on the tpautoconf command. (The -probe
option requires NDMP protocol version 3.) For example:
tpautoconf -probe host_name
where host_name is the name of the Pillar Axiom system.
Example output:
Host "host_name" SCSI device model "Scalar 100 ":
Device "Robot-10" attributes=0x0
EXECUTE_CDB=n
Host "host_name" tape device model "ULTRIUM-TD2 ":
Device "Tape-30" attributes=(0x0)
EXECUTE_CDB=n
Host "host_name" tape device model "ULTRIUM-TD2 ":
Device "Tape-20" attributes=(0x0)
EXECUTE_CDB=n
To manually detect locally attached tape devices on the Axiom system, use the
Axiom Storage Manager GUI to navigate to Data Protection > Tape Devices, and
then select Check for Tape Devices from the Actions pull-down menu in the
middle of the window.

1 Enter the following to authorize NetBackup 6.0 or later to access the Pillar
Axiom system and its robot. (See “Authorizing NetBackup access to the
tpconfig -add -nh Axiom_host -user_id user_ID -password password
tpconfig -add -robot 7 -robtype tld -robpath spt0 -nh Axiom_host
tpautoconf -verify Axiom_host
Connecting to host "Axiom_host" as user "ndmp"...
Host info is:
host name "Axiom_host"
os type "Linux"
os version "2.4.20-30.8.legacy"
host id "514486433"

2/17/10 Pillar data systems axiom
Opening SCSI device "Robot-10"...

Inquiry result is "ADIC Scalar 100 3.223.22.0003 "

DAR is supported by the Pillar Axiom and by the following versions of
NetBackup:
Other
None.

Quantum 2/17/10
Quantum
Quantum Network-Attached Storage (NAS) backup solution controlled by a
Prism Management Card (PMC). It is intended as a supplement to the NetBackup
For further details, contact Quantum Corporation.
Known restrictions
The Quantum PMC-controlled robotic library only supports three-way backups.
ATL logs
To display any logs for Quantum PMC-controlled robotic library, contact
Quantum Corporation for assistance.

Note that each robot and each tape drive has its own IP address.
1 Use a browser to connect to the IP address of the robot.
2 Select Drive Configuration under “NDMP”
■ Under “View/Edit NDMP Drive Configuration,” enter the drive you
want to configure.
■ Change the IP and Password information.
■ Select Apply.
■ Select “Reboot Prism Management Card” in the “Utilities” Section.
3 Once the PMC reboots, power cycle the robot.
4 When the robot comes “Online,” check the drives.
■ Select “Drive Status” under NDMP.
■ If the configured drives show up with “Running,” ping the configured
drives.
Robot
The robot name is spt0. The robot has its own IP address.
Use the tpconfig command to set attributes for the robot.

2/17/10 Quantum
For example:
tpconfig -add -robot 8 -robtype tld -robpath spt0 -nh 101.111.222.33
Where:
■ 101.111.222.33 is the IP address for the PMC.
■ spt0 is the device name for the robotic control.
■ 0 is the SCSI controller number.
■ 0 is the target ID.
■ 0 is the LUN number.
Media device
Although each tape drive has the same device name (/dev/nst0), each drive
has a unique IP address. As a result, you must authorize access to each drive.
The following example is for two tape drives in the same robot.
tpconfig -add -nh 101.111.222.34 -user_id root
tpconfig -add -nh 101.111.222.35 -user_id root
(enter password at prompt)
Console:
101.111.222.34:/dev/nst0
Where 101.111.222.34 is the IP address for the tape drive and /dev/nst0
is the tape device name.

Quantum PMC-controlled robotic library. (See “Authorizing NetBackup
access to the NDMP host” for assistance with earlier NetBackup releases.)
tpconfig -add -nh 101.111.222.33 -user_id root -password
password
tpconfig -add -robot 8 -robtype tld -robpath spt0
-nh 101.111.222.33 -bus 0 -target 0 -lun 0
tpautoconf -verify 101.111.222.33
Verify Host name: 101.111.222.33
Connecting to host “101.111.222.33” as user “root”..
Host info is:
host name “101.111.222.33”
os type “Linux”

Quantum 2/17/10
os version “2.2.5-22”
host id “0”
host supports TEXT Authorization
Opening SCSI device “spt0”
Setting SSI target controller 0 id 0 lun 0...
Inquiry result is ATL P3000 63100501.42
2 Enter the following to authorize NetBackup 6.0 or later to access a tape drive
in the Quantum PMC-controlled robotic library. (See “Authorizing
NetBackup access to the NDMP host” for assistance with earlier NetBackup
releases.) This command must be repeated for each tape drive in the robot.
tpconfig -add -nh 101.111.222.34 -user_id root -password
password
tpautoconf -verify 101.111.222.34
Verify Host name: 101.111.222.34
Connecting to host “101.111.222.34” as user “root”..
Host info is:
host name “101.111.222.34”
os type “Linux”
os version “2.2.5-22”
host id “0”
host supports TEXT Authorization

DAR is supported by the Quantum robotic library (contact Quantum for the
required OS level) and by the following versions of NetBackup:
Other
None.

2/17/10 Spectra logic
Spectra logic
Spectra Logic NDMP enabled by TAOS robotic library. It is intended as a
supplement to the NetBackup for NDMP Administrator’s Guide.
For further details, refer to the following Spectra Logic documentation or
contact Spectra Logic Corporation.
■ Spectra 2000 TAOS enabled Manual
Known restrictions
The Spectra Logic NDMP enabled by TAOS robotic library only supports
three-way backups.
Spectra logic logs

To display any logs for Spectra Logic NDMP robotic library, you must make a
serial connection to the library. Contact Spectra Logic for assistance.

To make sure TAOS NDMP is enabled:
1 Use a browser to sign in to the Spectra Logic NDMP robotic library. Click
“Configure” and enter your password.
2 On the Administration and Configuration menu, select “Options
Enablement.” Under “Enabled Protocol,” make sure TAOS NDMP is enabled.
3 If TAOS NDMP is not enabled, click its button to enable it, then return to the
Administration and Configuration menu and select “Restart Device.”
To change the TAOS NDMP password:

1 Use a browser to sign in to the Spectra Logic NDMP robotic library. Click
“Configure” and enter your password.
2 On the Administration and Configuration menu, click “TAOS NDMP Access
Control” and enter the required information.
3 Re-run tpconfig on your NetBackup for NDMP server.

The Spectra Logic Administration and Configuration menu does not display the
robot or tape device file names. The device file names are in this format:

Spectra logic 2/17/10
devicetargetnumber_LUN
Robot
For example:
Library0_0
where Library is the device, the target number is 0, and the LUN is 0.
Media device
For example:
Tape1_0
where Tape is the device, the target number is 1, and the LUN is 0.
Console:
treefrog:Tape1_0
where treefrog is the name of the Spectra Logic NDMP enabled by TAOS robotic
library.

1 Enter the following to authorize NetBackup 6.0 or later to access the Spectra
Logic library. (See “Authorizing NetBackup access to the NDMP host” for
tpconfig -add -nh Spectra_host -user_id root -password password
tpconfig -add -robot 8 -robtype tld -robpath Library0_0
-nh Spectra_host -bus 0 -target 0 -lun 0
tpautoconf -verify Spectra_host
Connecting to host "Spectra_host" as user "root"...
Host info is:
host name "Spectra_host"
os type "UCOS"
os version "4.1.28.0"
host id "1234"
Opening SCSI device "Library0_0"...
Inquiry result is "SPECTRA 215 X010h1"

2/17/10 Spectra logic


DAR is supported by the Spectra Logic robotic library (contact Spectra Logic for
the required OS level) and by the following versions of NetBackup:
Other
None.

Stratus V Series 2/17/10
Stratus V Series
Stratus V Series system. It is intended as a supplement to the NetBackup for
The Stratus V Series is supported by NetBackup 6.0 and later.
For further details on the Stratus V Series system, please contact Stratus
Technologies.
Known restrictions
■ The Stratus V Series system supports NetBackup remote NDMP backups
only. Remote NDMP backups are a form of three-way backup described in
the NetBackup for NDMP Administrator's Guide.
■ The Stratus V Series does not support directory names greater than 32
characters. The limitation for files names is 255 characters.
■ The Stratus V Series does not support CIFS or NFS for file system access. To
access the Stratus file system, you must use SAMBA.
To learn more about file system access to the Stratus V Series, please refer
to your Stratus documentation.
■ The Stratus V Series uses its own operating system called VOS. To access the
VOS operating system directly, you must use a terminal emulator such as
TTWIN 3.
■ The Stratus V Series supports the NDMP version 3 protocol only.
Stratus V Series logs

The Stratus VOS Enterprise Backup Agent creates the following log files. All are
stored on the Status system in the >system>ndmpd>log directory:
■ ndmpd_log.YY_MM_DD.out
■ save.YY_MM_DD.hh_mm_ss.process_id
■ macro.YY_MM_DD.hh_mm_ss.process_id
For more information about these files, refer to “Log Files” in the VOS
Enterprise Backup Agent online documentation.

See “Tips for robot and media discovery.”

2/17/10 Stratus V Series

The Stratus V Series is supported for remote NDMP backup only. The devices
are controlled by the NetBackup media server rather than locally by the Stratus
system. To learn more about remote NDMP, refer to the NetBackup for NDMP
Example Configuration Sequence

1 To add the Stratus V Series to the NDMP credential list, enter the following
on the NetBackup media server:
tpconfig -add -nh Stratus_hostname -user_id ndmp_username
-password password
2 To verify that the Stratus V Series has been added to the NetBackup EMM
database, enter the following:
tpconfig -dnh
Example output:
Media Server: media_server_hostname
NDMP Host Name: Stratus_hostname
User Id: ndmp_username
3 To verify that the NetBackup media server can communicate with the
Stratus V Series, enter:
tpautoconf -verify stratusv34a
where stratusv34a is an example Stratus host name.
Example output:
Connecting to host "stratusv34" as user "root"...
Host info is:
host name "stratusv34"
os type "VOS"
os version "OpenVOS Release 17.0.1"
host id "0"

Stratus V Series 2/17/10
Direct Access Recovery (DAR)

The Stratus V Series supports DAR.
Other
The following directives must be placed at the start of the NetBackup policy's
Backup Selections tab (file list):
SET TYPE=save
SET SAVE_OPTIONS='-backup'
To learn more about the additional directives available for the Stratus V Series,
see the Stratus V Series documentation.

2/17/10 Sun StorEdge 5xxx NAS
Sun StorEdge 5xxx NAS

This information is provided to help you use NetBackup for NDMP with the Sun
StorEdge 5xxx NAS system. It is intended as a supplement to the NetBackup for
NDMP Administrator’s Guide. For further details on the Sun StorEdge 5xxx NAS,
please contact Sun Microsystems, Inc.
Known restrictions
■ Sun StorEdge NAS systems running OS version 4.02.45 or earlier support
remote NDMP backup and restore only. Sun StorEdge 52xx and 53xx NAS
systems running OS version 4.20 or later support local and three-way
backup and restore (including remote NDMP).
■ Set TYPE=tar is not supported for the Sun StorEdge 5xxx NAS OS version
4.02.45 or earlier. Since the path name does not start with the path
separator (/), the restores will fail. This restriction does not apply to NAS OS
version 4.20 or later.
■ Files containing hard links may not be restored with the correct number of
hard links.
Sun StorEdge 5xxx NAS logs

To display logs, log onto the Sun StorEdge 5xxx NAS Web Admin console and go
to Monitoring and Notification > View System Events > Display System Log.

Sun StorEdge 5xxx NAS 2/17/10

To monitor system activity, access the Sun StorEdge 5xxx NAS Web Admin
console and go to System Activity > View System Activity.

The Sun StorEdge 5xxx NAS supports remote NDMP backup and restore only.
For assistance configuring devices, use the NetBackup Device Configuration
wizard, or refer to the NetBackup Administrator’s Guide, Volume I.

Enter the following to authorize NetBackup 6.0 or later to access the Sun
StorEdge 5xxx NAS. (See “Authorizing NetBackup access to the NDMP host” for
tpconfig -add -nh Sun_host -user_id ndmp -password password
tpautoconf -verify Sun_host
Connecting to host "Sun_host" as user "administrator"...
Opening session--attempting with NDMP protocol version 3..

2/17/10 Sun StorEdge 5xxx NAS

Host info is:
host name "Sun_host"
os type "StorEdge"
os version "Version 4.02 M42 (Build 160) "
host id "FG42499997"

DAR is supported by the Sun StorEdge 5xxx NAS and by the following versions
of NetBackup:
To verify that DAR is enabled, telnet into the Sun StorEdge 5xxx NAS and enter
the following:
ndmp set dar=yes
ndmp save
ndmp show dar
If DAR is enabled, the Sun StorEdge 5xxx NAS responds “yes.”
Other
The Sun StorEdge 5xxx NAS supports path-based history with NetBackup 4.5 or
later.
set HIST=y

Veritas remote NDMP 2/17/10
Veritas remote NDMP

Note: This section applies only to NetBackup releases prior to 6.0. In 6.0 and
later, tape devices used for remote NDMP are configured as ordinary Media
Manager devices.
This information is provided to help you use Veritas Remote NDMP. It is

intended as a supplement to the NetBackup 4.5/5.x for NDMP System
Known restrictions
Remote NDMP only supports three-way backups.
Remote logs
For troubleshooting, look at the following log on the server where you installed
remote NDMP: /usr/openv/netbackup/logs/ndmpmoveragent

This subsection applies to NetBackup 4.5 only.
To install the agent required for remote NDMP on Windows NT/2000

1 Use the InstallNdmpMoverAgent command:
For example (to be entered all on one line):
C:\Program Files\Veritas\volmgr\bin\InstallNdmpMoverAgent
“C:\Program Files\Veritas\volmgr\bin” administrator password1
where administrator is the username for authentication to the NDMP
host, and password1 is the password.
2 To confirm that the agent is running, do one of the following:
■ Start the NetBackup Administration Console and click on the Activity
Monitor. Click the Processes tab and look for “ndmpmoverlisten.”
■ In the Windows Services display, make sure that the NDMP Mover
Agent is listed as Started.
To install the agent required for remote NDMP on Solaris

1 Use the ndmpmoveragent command:
For example:
/usr/openv/volmgr/bin/ndmpmoveragent.start -install
2 To confirm that the agent is running, enter the following:

2/17/10 Veritas remote NDMP
ps -e | grep ndmpmove
Example output:
1346 ? 0:00 ndmpmove
For details on these commands, refer to the commands appendix of the
NetBackup 4.5 for NDMP System Administrator’s Guide.

Robot
Since the robot is directly attached to the NetBackup media server, it is not
configured as an NDMP robotic device. Refer to the NetBackup Administrator’s
Guide, Volume I for configuration instructions.
Media device
Unlike the robot, the tape device must be configured as an NDMP device.
Console:
Solaris example:
patch:/dev/rmt/0cbn
where patch is the name of the Solaris NetBackup media server, 0 specifies unit
0, c means compressed, and bn is the Berkeley no-rewind device. You must use
the Berkeley no-rewind device.
Windows NT/2000 example:
patch:Tape0
where patch is the name of the Windows NT/2000 NetBackup media server and
Tape0 is the device name.

1 Enter the following to authorize access to the remote NDMP host:
set_ndmp_attr -auth remoteNDMP_host username password
set_ndmp_attr -verify remoteNDMP_host
Example output from the -verify option on a Solaris media server:
Connecting to host "remoteNDMP_host" as user "root"...
Host info is:
host name "remoteNDMP_host"
os type "SunOS"
os version "5.8"

Veritas remote NDMP 2/17/10
host id "80cc45cd"
a backup policy. These procedures are described for remote NDMP in the
NetBackup 5.x for NDMP System Administrator’s Guide.

DAR is supported by Remote NDMP and by the following versions of NetBackup:
Other
None.

NetBackup NAS Appliance Support Guide

Cargado por

Información del documento

Descripción original:

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

NetBackup NAS Appliance Support Guide

Cargado por

Copyright:

Formatos disponibles

Symantec TechNote 267773

NetBackupTM for NDMP:

Supported operating systems

Note: NetBackup for NDMP is installed on a master or media server, not on a

NAS appliance versions

Authorizing NetBackup access to the NDMP host

Note on file restore to a different location

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

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

Tips for control and configuration

Tips for robot and media discovery

Example configuration sequence

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

tpautoconf -verify agami_host

Direct access recovery

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

BlueArc titan logs

Tips for control and configuration

Tips for robot and media discovery

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

Device "/dev/mt_d0l2" attributes=(0x4) RAW

Example configuration sequence

Direct access recovery (DAR)

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

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

DinoStor TapeServer logs

Tips for control and configuration

On the DinoStor TapeServer

Note: To use a TapeServer with NetBackup, two IP addresses must be configured

Tips for robot and media discovery

Example configuration sequence

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

Getting MD5 challenge from host...

Direct access recovery (DAR)

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

EMC celerra logs

Tips for control and configuration

Tips for robot and media discovery

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

Alternate means of finding robot and media device file names

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

Example configuration sequence

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

Opening SCSI device "c3t0l0"...

Direct access recovery (DAR)

For celerra network server version 5.5 software and above

File and directory exclusion statements

Examples of file and directory exclude statements in a Netbackup Backup

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

NDMP policy should specify snapshot-based backup

NDMP volume backup (VBB)

Example of NDMP volume backup entries in the Backup Selections list:

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

EMC centera with centera backup and recovery

EMC CBRM logs

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

To capture SDK logs:

To capture NDMP logs:

Tips for control and configuration

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

Tips for robot and media discovery

Example configuration sequence