NDMP Backups With Celerra

Configuring NDMP Backups with Celerra
and BakBone NetVault

P/N 300-001-623
Rev A01
Version 5.3
August 2004
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2
Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4
Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5
NDMP Backup Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
NDMP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6
Restoring File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10
Dynamic Drive Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
EMC NAS Interoperability Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . .12
Planning Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13
Data Mover-to-TLU Cabling Examples . . . . . . . . . . . . . . . . . . . . . . . .13
Implementing International Character Support with NDMP . . . . . . .14
Multithreaded Backup and Restore Design . . . . . . . . . . . . . . . . . . . .16
User Interface Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18
Configuring NDMP Backups with Celerra and BakBone NetVault
Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19
Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20
Configuring Data Movers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21
Setting Up the TLU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29
Assigning Data Movers a Username and Password . . . . . . . . . . . . . . . .32
Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34
Configuring Your Backup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37
Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38
Backing Up a VDM File System with NDMP . . . . . . . . . . . . . . . . . . . . . . .42
Managing NDMP Backups on Celerra . . . . . . . . . . . . . . . . . . . . . . . . . . . .43
Viewing and Modifying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .43
Viewing Backup Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52
Command Syntax Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56
Troubleshooting NDMP Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Troubleshooting Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59
Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Want to Know More? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75
1 of 78
Introduction
The Network Data Management Protocol (NDMP) allows you to control the backup
and recovery of an NDMP server through a network backup application, without
installing third-party software on the server. In a Celerra® Network Server, the Data
Mover functions as the NDMP server.
This technical module is part of the Celerra Network Server information set and is
intended for the System Administrator implementing a backup strategy with one or
more Celerra Network Servers. The System Administrator should be familiar with
backup and restore operations and with the basic administration of a Celerra
Network Server.
This technical module explains how to perform Network Data Management Protocol
(NDMP) backups with the Celerra Network Server and your backup software. It also
contains the information you need to cable and configure the Celerra Network
Server. Use this and other Celerra Network Server documentation in conjunction
with the documentation for your specific backup vendor.
Terminology
This section defines terms that are important to understanding NDMP backup
capabilities on the Celerra Network Server. Refer to the Celerra Network Server
User Information Glossary for a complete list of Celerra terminology.
automated backup and restore: A procedure in which a remote backup server
running NDMP-compliant backup software backs up data to a TLU.
backup and restore: A technique for ensuring file-system integrity and security by
backing up to tape or disk a file system or incremental changes to a file system; this
data can then be restored at a later time.
cumulative incremental backup: A backup that copies all data objects modified
since the last full backup. To restore data when cumulative incremental backups are
in use, you need only the latest full backup and the latest cumulative incremental
backup. See also differential incremental backup, full backup, incremental backup.
DAR: Direct access restore. An optimized data recovery operation that allows the
NDMP client to directly access backed-up data in the middle of a tape set without
having to traverse the tape set sequentially.
differential incremental backup: A backup that copies data objects modified since
the last full backup or incremental backup. To restore data when differential
incremental backups are in use, the newest full backup and all subsequent
differential backups are required. See also cumulative incremental backup, full
backup, incremental backup.
dynamic drive sharing (DDS): A feature of NDMP-compliant backup software that
allows NDMP servers to share tape drives.
full backup: A backup that copies all of a defined set of data objects, regardless of
whether they have changed since the last backup. A full backup is the basis from
which incremental backups are taken. See also cumulative incremental backup,
differential incremental backup, incremental backup.
2 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

NetVault
heterogeneous three-way backup: A three-way NDMP backup involving a Data
Mover, which serves as the interface to the file system or primary storage system,
and a qualified third-party NDMP server, which serves as the interface to the tape
devices or other secondary storage. See also three-way backup.
incremental backup: A term that encompasses both cumulative incremental
backups and differential incremental backups. Any backup that copies only data
objects modified since the time of some previous backup. See also cumulative
incremental backup, differential incremental backup, full backup.
local backup: A procedure that backs up a copy of a file system or incremental
changes to a file system from a Data Mover to a locally attached TLU. See also
automated backup and restore, manual local backup.
NDMP: Network Data Management Protocol. An open standard network protocol
designed for enterprise-wide backup and recovery of heterogeneous network-
attached storage.
NDMP client: The application that controls the NDMP session. The NDMP client
runs an NDMP-compliant backup application, such as LEGATO® NetWorker.
NDMP Host: The host system (Data Mover) that executes the NDMP server
application. Data is backed up from the NDMP Host to either a local tape drive or to
a backup device on a remote NDMP Host.
NDMP server: The NDMP process that runs on an NDMP Host, which is a Data
Mover in a Celerra Network Server environment.
PAX: Portable Archive Interchange. A Celerra Network Server archive protocol that
works with standard UNIX tape formats.
remote backup: A remotely initiated procedure that backs up data to a TLU that can
be attached to a target server different from the source Data Mover. Your
configuration determines whether data traverses the network. See also automated
backup and restore, three-way backup.
tape library unit (TLU): A physical device that contains and manages multiple
magnetic tape units accessible as a single unit.
three-way backup: An NDMP-protocol backup that directs data from one Data
Mover through a network connection to a remote Data Mover to its attached tape
library backup device. See also heterogeneous three-way backup.
Terminology Differences
The following terminology differences exist between this guide and the third-party
documentation.
Table 1 Terminology Differences
EMC Term Equivalent Third-Party Terms
Tape library unit (TLU), jukebox, tape drive Library (refers to any backup storage device),
autochanger handle, autochanger
TLU robot Robotic arm, arm changer
NDMP-Host Data Mover Celerra filer, NAS filer, application server
Configuring NDMP Backups with Celerra and BakBone Version 5.3 3 of 78

NetVault
Table 1 Terminology Differences (Continued)
EMC Term Equivalent Third-Party Terms
Celerra Network Server Client computer, Celerra filer
Restrictions
When configuring your Celerra Network Server, note the following restrictions:
◆ EMC supports three-way NDMP backups in the following circumstances:
• Celerra Data Mover to Data Mover. The Data Movers can reside on the same
Celerra Network Server or on different Celerra Network Servers. This
includes the NS-Series Celerra Network Servers, which can provide one or
both Data Movers in a three-way configuration.
• Data Mover to NDMP server in a heterogeneous three-way configuration.
Refer to EMC NAS Interoperability Matrix on page 12 to locate the most up-
to-date information on heterogeneous three-way backup support.
◆ EMC supports NDMP drive sharing through a storage area network (SAN) only.
Refer to the EMC NAS Interoperability Matrix on page 12 and check with your
vendor for information on dynamic drive sharing support.
◆ On an NS-Series Celerra Network Server, the AUX port used for backup
defaults to Fibre Channel Arbitrated Loop (FC-AL) and 1 Gb. To use the AUX
port in a switched fabric environment or to change the speed, you must edit the
parameter file for the Data Mover to which you are connecting the tape drive.
Refer to Configuring Data Movers on page 21.
◆ NDMP does not support the Archive Bit method, only the Date/Time stamp
method is supported. The special wildcard characters, as well as the include/
exclude options, are not supported. To back up multiple directories, include all
directories in the file/directory list when creating the backup job.
◆ When you restore a Data Mover’s root partition, you must specify a restore path
that is different from the original location. You cannot restore to the original
location.
◆ NDMP does not follow symbolic links among file systems. Therefore, an NDMP
backup does not include a symbolic link's target file system. For more
information on symbolic links, refer to Configuring CIFS on Celerra for the
Windows Environment.
◆ Stripe size on your storage system can affect backup performance. For optimal
backup stripe size settings on Symmetrix® and CLARiiON® systems, refer to the
EMC NAS Interoperability Matrix on page 12.
◆ Currently, only full backups are supported with BakBone NetVault and Celerra.

NetVault
Cautions
This section lists cautions for configuring your Celerra Network Server for NDMP
backups.
! !
CAUTIONS
◆ You must configure Data Movers attached to tape drives for any NS Series
Celerra Network Server. For more information, refer to Configuring Data Movers
on page 21.
◆ If a failover occurs during a backup, you must directly connect the tape drive to
the new Data Mover and restart the backup. You may also need to reconfigure
your backup software.
◆ Do not connect a standby Data Mover to the TLU by means of a SCSI connection.
This will cause the backup to fail and could cause tape contention.
Important: If you change your network zoning configuration, where relevant:

— Propagate changes to the consistent binding table.
— Adjust the backup software to reflect the new zoning configuration.

NetVault
NDMP Backup Concepts
The Network Data Management Protocol (NDMP) allows you to control the backup
and recovery of an NDMP server through a network backup application, without
installing third-party software on the server. In a Celerra Network Server, the Data
Mover functions as the NDMP server.
NDMP-based backups are used for high-capacity backups and in environments
where true multiprotocol (both CIFS and NFS) support is required. The NDMP
protocol separates the control and data transfer components of a backup or restore.
The actual backups are handled by the Data Mover, which minimizes network
traffic.
NDMP Configurations
The procedures in this technical module assume that the TLU connects directly to
the Celerra Network Server Data Mover. Refer to your backup software vendor’s
documentation for information on configuring a TLU attached to a backup host. This
section covers:
◆ Basic NDMP configuration
◆ Single and dual-TLU configurations
◆ Three-way backups
Simple NDMP Backup Configuration
The NDMP architecture uses a client/server model in which the backup software is
the NDMP client to the NDMP-Host Data Mover, as shown in Figure 1. Backup data
flows from the storage system to the Data Mover to an attached tape library backup
device, without traversing the network. Only the backup software’s control data
(scheduling, cataloging, and TLU commands) travels across the network.

NetVault
The Data Mover maintains a state machine for each NDMP client connection that
executes and maintains the backup and restore processes. A maximum of four
simultaneous backups are supported on each NDMP-Host Data Mover.
Network Boundary
Celerra
NDMP
NDMP Client Control Data NDMP-Host
with Backup Data Mover
Software
Robotic
Backup Control
Data
SB14
SB15
SB12
SB13
SB10
SB11
SB8
SB9
SB6
SB7
SB4
SB5
SB2
SB3
SB0
SB1
PS0 PS1 PS2 PS3 PS4 SMB0 SMB1
Storage Tape Library

System Backup Device
CNS-000349
Figure 1 Simple NDMP Backup
Single TLU Configuration

Figure 2 on page 8 demonstrates the first and most common TLU configuration.
When a TLU configuration consists of several Data Movers sharing one robot, only
one Data Mover needs to be connected to the robot. One Data Mover can execute
both backups and robot operations, as shown in Figure 2 on page 8. Robotic
commands are executed from the backup software.

NetVault
Note: Your backup software and TLU manufacturer determine which configuration options
are available to you.
Backup Host
NDMP Client with

Backup Software
Network Boundary
Celerra
NDMP Control Data NDMP Control Data
NDMP-Host NDMP-Host
Data Mover Data Mover
Backup Backup Data and

Data Robotic Control
Backup
SB14
SB15
Data
SB12
SB13
SB10
SB11
SB8
SB9
SB6
SB7
SB4
SB5
SB2
SB3
SB0
SB1

CNS-000348
Figure 2 Single-TLU NDMP Backup
Dual-TLU Configuration
Figure 3 shows two Data Movers connected to two separate storage-system
volumes and two separate tape library backup devices. The NDMP client controls

NetVault
and launches the backup. The Data Mover processes the data and sends it to the
tape device.
NDMP Client
with Backup
Software
Network Boundary
Celerra
NDMP Connection NDMP Connection
NDMP-Host NDMP-Host
Data Mover Data Mover
Robotic Control Robotic Control

Backup Backup
Data Data
SB14
SB15
51BS
41BS
SB12
SB13
31BS
21BS
SB10
SB11
11BS
01BS
SB8
SB9
9BS
8BS
SB6
SB7
7BS
6BS
SB4
SB5
5BS
4BS
SB2
SB3
3BS
2BS
SB0
SB1
1BS
0BS
PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 1BMS 0BMS 4SP 3SP 2SP 1SP 0SP
Tape Library Tape Library

Backup Device Storage Systems Backup Device
CNS-000350
Figure 3 Dual-TLU NDMP Backup
Three-Way Backup Configuration

Some third-party vendor backup software is not qualified with the Celerra Network
Server for three-way backup configurations.
With NDMP Version 2.0 and higher and some backup software vendors, you can
direct backup data from one Data Mover (NDMP backup host) through a network
connection to a remote NDMP tape server to its attached tape backup device. The
NDMP tape server can be a Data Mover or another qualified server. This
configuration is known as a three-way backup.
A three-way backup involves the following three hosts:
◆ NDMP backup client running qualified NDMP backup software
◆ Data Mover (NDMP data server) containing the data to be backed up (reads
from the storage system and produces a data stream for backup)
◆ Data Mover or qualified server running the tape service (reads the data stream
and writes it to tape)

NetVault
Note: The Celerra Network Server supports heterogeneous three-way backups with some
backup software vendors.
In a three-way backup, both file system and control data travel across the network.
This connection can be a dedicated network to avoid network traffic. Figure 4
illustrates a Data Mover-to-Data Mover three-way backup.
NDMP Client
with Backup
Software
Storage Celerra Celerra Tape Library

NDMP NDMP
Control Control
SB14
SB15
Data Data
SB12
SB13
SB10
SB11
SB8
SB9
Backup Backup
SB6
SB7
SB4
SB5
Data Data
SB2
SB3
SB0
SB1
Backup Data Only Robotic

Control
NDMP-Host NDMP-Host
Data Server Tape Server
Network Boundary CNS-000351
Figure 4 Three-Way NDMP Backup
Restoring File Systems

A restore reverses the backup process shown in Figure 1 on page 7. This
operation, initiated by the backup software, retrieves the file system from the
backup device, sends it to the Data Mover, and then restores the file system on the
storage system. The benefit of the NDMP backup and restore is that it does not
impact the network with data traffic.
Note: It is unnecessary to back up the Celerra Network Server root file system. You are not
allowed to restore to this file system.
The NDMP feature direct access restore (DAR) allows you to perform file-level
restores. During a direct access restore, the NDMP client moves directly to the
location of the file you want to restore, without reading through the entire backup to
find the file. DAR requires that you enable the file history feature on the Celerra
Network Server, which tells the Celerra Network Server to send the NDMP client
the file history information for the backup. The down side to this feature is that the
file history information adds network traffic.

NetVault
Dynamic Drive Sharing
Several backup software vendors are developing the ability to allow more than one
NDMP-Host Data Mover to share a single or multiple tape drives. The backup
software controls the ability of the NDMP-Host Data Movers to share the tape
drives and mediates the negotiation for tape drive access during simultaneous
backups. EMC supports sharing tape drives over a SAN as shown in Figure 5.
Celerra
NDMP-Host
Data Mover
NDMP Client
with Backup
Software Celerra SAN
Tape Drive
Network NDMP-Host
Boundary Data Mover CNS-000356
Figure 5 Dynamic Drive Sharing

A Celerra Data Mover supports up to eight attached tape drives per Data Mover. By
default, a Data Mover is configured to accommodate four attached tape drives. To
attach more than four tape drives, you must edit the ntape parameter. However, a
Data Mover supports only four concurrent backups per Data Mover.
Refer to EMC NAS Interoperability Matrix on page 12 and to your backup software
vendor’s documentation for information on:
◆ Backup software-vendor support for three-way backups
◆ Supported NDMP configurations
◆ Dynamic-drive sharing support

NetVault
System Requirements
This section describes the Celerra Network Server software, hardware, network,
and storage configurations required for performing NDMP backups as described in
this technical module.
Note: The Celerra Network Server supports NDMP Version 4.0.
Table 2 System Requirements for NDMP Backups
Celerra Network Server Version 5.3.

Software
NDMP- and Celerra-compatible backup software running on the NDMP client.
Hardware Celerra Network Server.
Network Dedicated network (optional).
Storage Compatible tape device or tape library unit.
EMC NAS Interoperability Matrix

Refer to the EMC NAS Interoperability Matrix for definitive information on supported
software and hardware, such as backup software, Fibre Channel switches, and
application support for Celerra network-attached storage (NAS) products.
To view the EMC NAS Interoperability Matrix:
1. Go to http://powerlink.emc.com.
2. Search for NAS Interoperability Matrix.
3. In the Sort Search Results by box, select Score.
The EMC NAS Interoperability Matrix appears in the list.

NetVault
Planning Considerations
This section includes:
◆ Cabling examples for SCSI- and Fibre Channel–connected TLUs.
◆ An overview of how the Celerra Network Server handles international character
sets.
Data Mover-to-TLU Cabling Examples

This section includes examples of both SCSI and Fibre Channel cabling from the
Data Mover to the TLU. For information on cabling a TLU to a backup host, refer to
your backup software vendor’s documentation. For instructions on setting up the
TLU and identifying device names, refer to Setting Up the TLU on page 29.
SCSI Cabling Configuration
In Figure 6, two SCSI connections go from the NDMP-Host Data Movers to the
TLU. One SCSI connection is daisy chained to two tape drives, and the other one is
daisy chained to two tape drives and a robot. All the Data Movers in Figure 6 have
two direct SCSI connections to the storage system.
Storage
Celerra System
Tape Library Unit

SB14
SB15
SB14
SB15
SB12
SB13
SB12
SB13
SB10
SB11
SB10
SB11
SB8
SB9
SB8
SB9
SB6
SB7
SB6
SB7
SB4
SB5
SB4
SB5
SB2
SB3
SB2
SB3
SB0
SB1
SB0
SB1

CNS-000353
Figure 6 Sample SCSI Cabling Configuration
Robot Connectivity
If a configuration consists of several Data Movers sharing one TLU robot, you need
to connect only one of these Data Movers to the robot. Robotic control is configured
in the backup software. For more information on robotic control, refer to the
appropriate vendor’s documentation.
Fibre Channel Configuration
Figure 7 shows the Fibre Channel connection from the storage system to a switch
and from the switch to the top port of each Data Mover. The bottom port of each
Data Mover connects to another switch through Fibre Channel, and then from that
switch to the TLU through Fibre Channel.

NetVault
In a configuration where SCSI is used to connect to a TLU, the SCSI connection is
achieved by connecting the second switch to a bridge through Fibre Channel, and
then the SCSI cable connects the bridge to the TLU.
Note: You can use one switch by connecting the storage system and the TLU to the same
switch.Figure 7 illustrates a two-switch configuration.
Tape Library
Backup Device
Celerra
Storage
System
SB14
SB15
SB12
SB13
FC FC
SB10
SCSI DM 1
SB8
FC FC
SB14
SB15
DM 2
SB6
SB12
SB13
FC
SB4
SB5
SB10
SB11
Bridge
SB2
SB3
SB8
SB9
FC
SB0
SB1
SB6
SB7
FC Switch Switch
SB4
SB5
SB2
SB3
SB0
SB1
FC PS0 PS1 PS2 PS3 PS4 SMB0 SMB1
Tape Library
Backup Device
CNS-000352
Figure 7 Sample Fibre Channel Configuration
Implementing International Character Support with NDMP

The Celerra Network Server supports international character sets if you have
Unicode enabled. Celerra Network Server supports the architecture-independent
UTF-8 Unicode format. When performing NDMP backups with Unicode enabled,
verify that the EMC-qualified NDMP backup vendor you choose supports
international character sets.
If your vendor does not support international character sets, refer to the Using
International Character Sets with Celerra technical module for information about
choosing the best translation configuration file for your environment.
Verify Vendor Support for International Character Sets
Verify that the EMC-qualified NDMP backup vendor you choose supports
international character sets. The backup vendor’s software support for international
characters with NDMP will determine which of the following two Celerra
implementations you need to follow.

NetVault
Vendor Supports International Characters
If your vendor supports international character sets, follow the vendor instructions
for implementation and follow up with your backup software vendor regarding any
issues you encounter.The Celerra Network Server’s default translation dialect is
UTF-8.
For more information about setting parameters, refer to Configuring Data Movers
on page 21. For more information on how to use international character sets with
the Celerra Network Server, refer to the Using International Character Sets with
Celerra technical module.
Note: Refer to EMC NAS Interoperability Matrix on page 12 and your vendor’s
documentation to determine whether the vendor is qualified and supports the use of
international character sets.
Vendor Does Not Support International Characters

If Unicode is enabled on your Celerra Network Server, but your backup vendor
does not support international character sets, you may set up your environment to
work with the best translation configuration file for your environment. The default
translation dialect is UTF-8. Refer to the technical module Using International
Character Sets with Celerra for details about translation files and choosing the
appropriate file for your configuration. You must also set the Celerra Network
Server parameters as specified in Configuring Data Movers for NDMP Backups on
page 22.
Data Backup Type Behavior with International Character Sets
Data is backed up onto tape using either the tar or dump NDMP backup type. If
you have chosen a translation configuration file, the filename is converted to the
client encoding and sent to the client as the file history. These backup types are
processed differently when difficulties with the translation are encountered.
NDMP tar/dump Backups
During an NDMP tar or dump backup, if a file is found that the translation
configuration file cannot translate, the catalog information for that file will not be
sent to the backup client. An error log is created, the data is backed up without the
catalog information, and the rest of the NDMP backup continues normally. The file
with the catalog information that could not be backed up can only be recovered
through a full restore of the directory.

NetVault
Multithreaded Backup and Restore Design
The Celerra Network Server uses a multithreaded backup and restore design that
improves the Celerra NDMP backup and restore performance in most
environments. The design involves three main thread groups, referred to as NASA,
NASS, and NASW. These thread groups process and deliver backup and restore
data and metadata. Table 3 describes each thread group’s function. Parameters
related to the multithreaded backup design are described in more detail in
Managing NDMP Backups on Celerra on page 43. The server_pax command,
which is covered in Viewing Backup Statistics on page 52, displays backup
statistics for each thread group.
Table 3 Backup Thread Groups
Thread Function
NASA • Sends metadata to the NDMP backup software

• Reads file data
• Writes data to the buffer pool
NASS • Traverses the file system

• Provides metadata for each file and/or directory
NASW • Gets data from the data buffer pool

• Writes data to tape or sends it to a remote Data Mover or NDMP server

NetVault
Multithreaded Backup Process
When you initiate an NDMP backup, the NASA thread group activates multiple
backup threads and puts metadata buffers in the stat buffer pool, which is shared by
NASA and NASS. Figure 8 shows the components of the multithreaded backup
and restore design.
Client with
NDMP-compliant
backup software
Network Boundary
Data Mover
NASA
Backup and
Restore
Threads
SB14
SB15
SB12
SB13
Stat Buffer Data Buffer

SB10
SB11
Pool Pool
SB8
SB9
SB6
SB7
SB4
SB5
SB2
SB3
SB0
SB1
NASS NASW
System Unit
FTS Threads
Celerra CNS-000441
Figure 8 Multithreaded Backup and Restore

The stat buffer pool contains a user-definable number of buffers (determined by the
paxStatBuff parameter), which transfer file-system metadata. Upon receiving
metadata buffers, NASS traverses the backup file system or directory and returns
metadata to the stat buffer pool. When a metadata buffer is available, a backup
thread backs up one directory or file per thread, in sequential order. When a thread
completes its portion of the backup, it waits for subsequent threads to complete
their backup portions before starting a new one. The number of backup threads is
determined by the nThread parameter, which is described in more detail in Table 9
on page 49.
Multithreaded Restore Process
The multithreaded restore process involves the NASA and NASW thread groups.
You can define the number of restore threads through the nRestore parameter,
which is described in more detail on Table 9 on page 49. Each restore thread is
responsible for a single small file or part of a bigger file. When the backup software
begins the restore process, the NASA thread activates the restore threads and
waits for NASW to deliver data to the data buffer pool. The user-definable
ReadBuff parameter determines the number of buffers between the NASA and
NASW thread groups.

NetVault
User Interface Choices
The Celerra Network Server offers flexibility in managing networked storage based
on your support environment and interface preferences. This technical module
describes how to configure NDMP backups using the command line interface (CLI).
You can also perform some of these tasks using Celerra Manager. For more
information about Celerra Manager, refer to Getting Started with Celerra
Management in the documentation kit.

NetVault
Configuring NDMP Backups with Celerra and
BakBone NetVault Roadmap
This roadmap shows the process for configuring NDMP backups with Celerra and
your backup software vendor. This process contains components that represent the
sequential phases of the roadmap. In addition, any nonsequential phases are
represented in the blocks at the base of the roadmap. Each phase contains the
tasks required to complete the process.
Note: When viewing online, click the text in the roadmap to access that phase. To return to
this roadmap from other pages, click the roadmap symbol at the center bottom of the page.
Configuring Data Movers
Setting Up the TLU
Assigning Data Movers a

Username and Password
Setting Environment
Variables
Configuring Your Backup

Software
Backing Up a VDM File

System with NDMP
Managing
ManagingNDMP
NDMPBackups
Backupson
on
Celerra
Celerra

NetVault
Configuration Guidelines
◆ The Celerra Network Server supports a maximum of four concurrent backups
per NDMP-Host Data Mover.
◆ You can connect multiple Data Movers to the same TLU.
◆ The TLU may have multiple SCSI host connections (refer to the TLU
documentation for installation and configuration information). The TLU may also
have Fibre Channel connections.
◆ Do not connect the Celerra Network Server Control Station to the TLU.
◆ For each TLU SCSI connection, EMC recommends attaching no more than two
tape drives.
◆ You cannot daisy chain any of the Data Mover’s storage-system SCSI
connections to the TLU.
◆ If an NDMP-Host Data Mover fails over to its standby, you must physically
connect the Data Mover’s TLU cable to the standby, and restart the backup. You
may also need to reconfigure the backup software with the appropriate address.
◆ The ability to connect a Data Mover to a TLU is dependent on the number of
SCSI ports on a Data Mover. Some older models of a Data Mover may have
only two SCSI ports, which are required for storage-system connectivity and
redundancy. It is advised that these storage-system SCSI ports not be used for
TLU connections.
◆ If you plan to turn on Internationalization, you should do so before, not after, you
create your file systems.
◆ An NS Series Celerra Network Server requires a media interface adapter (MIA)
for device connection to the AUX-0 port. Instructions on how to install a MIA in a
NS series Celerra are documented in individual setup instructions provided with
each system.
◆ In Celerra Network Server Version 5.3 or later, you do not need to configure the
ntape or nbuf parameters. The default ntape value is now set to 4, which is
sufficient for performing backups with one through four attached tape drives.
The nbuf parameter has been removed altogether.

NetVault
Configuring Data Movers
This section includes the following procedures.
Action Procedure
Configuring Data
Movers
Define parameters for NDMP-Host Data Configuring Data Movers for NDMP Backups on
Movers. page 22
Setting Up the TLU
Note: This procedure is required for NS series
Celerra Network Servers.
Assigning Data
Movers a Username Configure parameters for Internationalization. Configuring Data Movers for International
and Password Character Sets on page 25
Setting Environment Override the NDMP version used by the Celerra Overriding the NDMP Version on page 27
Variables Network Server.
Configuring Your For a summary of parameter file formats, refer to Parameter File Format, which
Backup Software
follows.
Parameter Files
Parameters are stored in text files, /nas/site/slot_param (system) and /nas/
server/slot_<x>/param (server). Because these files might already contain
parameter settings, it is recommended that you search the file for all occurrences of
Backing Up a VDM File the parameters, and if found, modify one and remove any duplicates. However, if
System with NDMP the file does contain duplicates, the last one in the file takes precedence.
To allow you to modify parameters for individual Data Movers, the values in the
Managing NDMP server file, /nas/server/slot_<x>/param, overwrite the values in the system
Backups on Celerra
file, /nas/site/slot_param. For example, if you want 32-bit GIDs (group IDs)
turned on for all Data Movers except server_3, the parameter value for gid32
must be set up as follows:
In the system parameter file, /nas/site/slot_param, type:
param ufs gid32=1
In the server parameter file, /nas/server/slot_3/param, type:
param ufs gid32=0
Note: After editing the system or server file, you must reboot the Data Mover for the
parameters to take effect.

NetVault
Parameter File Format
Parameters are formatted as follows:
param <module> <parameter> = <paramvalue>
Where:
<module> = name of module
<parameter> = name of parameter
<paramvalue> = value associated with the parameter
Configuring Data Movers for NDMP Backups
Table 4 describes the bufsz, enable_fabric_aux0, and linx_speed_aux0
parameters, which you will configure in this section. For information on optional
Configuring Data
performance-related parameters, refer to Managing NDMP Backups on Celerra on
Movers page 43. For more information on other Celerra Network Server parameters, refer
to the Celerra Network Server Parameters Guide.
Setting Up the TLU Note: Configuring the enable_fabric_aux0, and linx_speed_aux0 parameters is
required for NS series Celerra Network Servers.
Assigning Data Table 4 Summary of Required Parameters

Movers a Username
and Password Module Parameter Value Comment/Description
Setting Environment
NDMP bufsz buffer size in Specifies the size of the buffer allocated for
Variables
kilobytes reading and writing on the tape. The NDMP
default=128 client determines this value through the
TAPE_READ/TAPE_WRITE request.
Configuring Your
Backup Software Example:
param NDMP bufsz=256
fcTach enable_fa 0 (default) or 1 Note: This parameter applies only to the NS

bric_aux0 series Celerra Network Servers.
param fcTach enable_fabric_aux0=0

on a Celerra NS-Series system, configures the
System with NDMP tape backup port for an FC-AL environment.
on a Celerra NS-Series system, configures the
Managing NDMP
tape backup port for a Fibre Channel switched
Backups on Celerra
fabric environment.
fcTach linx_spee 0x4000 (default) or Note: This parameter applies only to the NS
d_aux0 0x2000 series Celerra Network Servers.
param fcTach linx_speed_aux0=0x4000

sets the tape backup link speed to
accommodate an LC optical 1 Gb interface.
sets the tape backup link speed to
accommodate a 2 Gb FC-AL interface.

NetVault
! !
CAUTION
Do not change other lines in the parameter file without a thorough knowledge of the
potential effects on the system. Contact EMC Customer Support for more
information.
Notes:
• The procedure that follows is required for NS series Celerra Network Servers.
• In Celerra Network Server Version 5.3 or later, you do not need to configure the ntape or
nbuf parameters. The default ntape value is now set to 4, which is sufficient for
performing backups with one through four attached tape drives. The nbuf parameter has
been removed altogether.
Use this procedure to define parameters for NDMP-Host Data Movers.
Step Action
1. Log in to the Control Station.
2. Open the file /nas/server/slot_<x>/param with a text editor.

Where:
<x> = slot number of the Data Mover attached to the tape device
Note: In a Data Mover-to-Data Mover three-way configuration, you also need to set
required parameters (step 3) for the Data Mover without an attached tape drive.
Example:
/nas/server/slot_2/param contains the server_2 configuration parameters.
3. To configure the bufsz parameter, use the following format.

param NDMP bufsz=<paramvalue>
Where:
<paramvalue> = buffer size in kilobytes (default = 128)
Note: This parameter value is configured for the Data Mover attached to the tape drive or
TLU.
Example:
To set the buffer size on server_2 to 256, type:

NetVault
Step Action
4. This step is required only if you are configuring an NS series Celerra Network Server. For
more information on these parameters, refer to Table 4 on page 22.
In addition to the bufsz parameter, add these parameters:
param fcTach enable_fabric_aux0=<paramvalue>
Where:
<paramvalue> = type of Fibre Channel environment (0=FC-AL; 1=FC switched fabric)
param fcTach linx_speed_aux0=<paramvalue>
Where:
<paramvalue> = AUX-0 port link speed (0x4000 or 0x2000)
Example:
To configure a Celerra NS700 Data Mover where server_2 has six attached tape drives,
the buffer size is 256, the environment is switched fabric, and the link speed is LC optical
1 Gb:
5. Optional. Configure the Data Mover for international character sets. The default dialect is
UTF-8. To change the dialect, refer to Configuring Data Movers for International
Character Sets on page 25.
6. Close and save the file.
7. If you are performing a Data Mover-to-Data Mover three-way backup, reboot the Data
Mover without an attached tape drive using this command syntax:
$ server_cpu <movername> -reboot -monitor now
Where:
<movername> = name of the Data Mover controlled by the slot_<x>/param file. For
example, slot_2/param affects server_2.
Example:
To reboot server_2, type:
$ server_cpu server_2 -reboot -monitor now
8. Proceed to Setting Up the TLU on page 29.
Note: You do not need to reboot the Data Mover that attaches to tape drives. You will
reboot the Data Mover as part of the next procedure, Setting Up the TLU on page 29.

NetVault
Configuring Data Movers for International Character Sets
Table 5 shows the NDMP convDialect and dialect parameters and their
values. For more information on other Celerra parameters, refer to the Celerra
Configuring Data
Network Server Parameters Guide.
Movers
Table 5 dialect and convDialect Parameters
Setting Up the TLU Module Parameter Value Comment/Description
NDMP convDialect dialect string You must set the conversion dialect when you
default=8859-1 restore an ASCII-mode Data Mover image to a
Assigning Data Data Mover that has Internationalization turned
Movers a Username on. This applies only when the conversion
and Password dialect you want to use is a non-Latin1 dialect,
such as big5.
Setting Environment
Variables Example:
param NDMP convDialect=big5
Configuring Your NDMP dialect dialect string Sets the dialect on the Data Mover to match
Backup Software default=“ ” the dialect of the Data Mover clients. This
applies when Celerra operates in
(UTF-8)
Internationalization mode.
Note: The default value (null) means that UTF-

8 is used.
Example:
Backing Up a VDM File param NDMP dialect=big5
System with NDMP
Managing NDMP This section explains how to specify a dialect in the Celerra Network Server. You
Backups on Celerra may need to specify a dialect when:
◆ Your backup software does not support Unicode, and a backup is done with
Unicode enabled on the Celerra Network Server. The filename must then be
converted.
◆ The Celerra Network Server is in internationalization mode and you are
restoring a backup image of an ASCII mode Data Mover where a non-Latin1
dialect was used.
For more information on support and behavior of international character sets with
the Celerra Network Server, refer to Implementing International Character Support
with NDMP on page 14 and to the Using International Character Sets with Celerra
technical module.
Note: During a backup, if a file is found that the translation configuration file cannot
translate, an entry in the server log is created. For example, if a file was created using a
character that does not appear in the code page’s character set, or if an NDMP dialect does
not match the dialect used to create the file, then an entry in the server log is created. When
restoring, you cannot perform a single-file restore on a file that contains an invalid
(inode_<number>) filename. To restore the file, you must restore the entire directory in
which the file resides.

NetVault
! !
CAUTION
information.
Use this procedure to set the dialect.
Step Action

Where:
<x> = slot number of the Data Mover
Example:
/nas/server/slot_2/param contains the server_2 configuration parameters.
2. Edit the file and add the following line:

param NDMP dialect=<paramvalue>
Where:
• If Unicode was enabled during the backup and your backup software does not support
Unicode:
<paramvalue> = the same dialect as the Data Mover client
• If you are restoring a backup image of an ASCII mode Data Mover where a non-Latin1
dialect was used, and the Celerra Network Server is in internationalization mode:
<paramvalue> = the dialect used on the ASCII mode Data Mover
3. Close and save the file.
4. After setting all parameters, reboot the Data Mover. Use this command syntax:
Where:
<movername> = the name of the Data Mover controlled by the slot_<x>/param file.
For more information about implementing international character sets, refer to the
Using International Character Sets with Celerra technical module, and your backup
software vendor’s documentation on this subject.

NetVault
Overriding the NDMP Version
Table 6 shows the NDMP maxProtocolVersion parameter and its values. For
more information on other Celerra parameters, refer to Celerra Network Server
Configuring Data
Parameters Guide.
Movers
Table 6 maxProtocolVersion Parameter
Setting Up the TLU Module Parameter Value Comment/Description
NDMP maxProtoc 1–4 Sets the maximum NDMP version that can be
olVersion default=4 used. Autonegotiation between Celerra and the
Assigning Data NDMP client determines the highest NDMP
Movers a Username version used. This parameter setting overrides
and Password the autonegotiation.
Example:
Setting Environment
Variables param NDMP maxProtocolVersion=3
Configuring Your
Backup Software ! !
CAUTION
information.
By default, some servers and NDMP devices autonegotiate to use the latest NDMP
version supported by both the server and NDMP devices. EMC recommends using
System with NDMP this default setting. However, you can override the automatic NDMP-version
selection by specifying the latest NDMP version that can be used.
Managing NDMP Overriding the NDMP version can be a useful troubleshooting tool, for example, to
Backups on Celerra
isolate NDMP issues by determining whether they occur with different versions.
Use this procedure to override the NDMP version.
Step Action
1. Log in to the Control Station.

Where:
<x> = slot number of the Data Mover
3. Add the following line if it does not appear:

param NDMP maxProtocolVersion=<x>
Where:
<x> = maximum NDMP version that the NDMP-host Data Mover and the NDMP client
can use. The default value is 4.
Example:
To set the maximum NDMP version to 3, type:
param NDMP maxProtocolVersion=3
Note: If the line appears and indicates a different NDMP version, edit the line and add the
NDMP version you want to specify.

NetVault
Step Action
4. Close and save the files.
5. After setting all parameters, reboot the Data Mover. Use this command syntax:
Where:
<movername> = name of the specified Data Mover
Example:
To reboot server_2, type:

NetVault
Setting Up the TLU
This section includes the steps for retrieving and recording device names, which
you need when configuring your backup software.
Configuring Data
Movers Recording TLU Information
The Celerra Network Server addresses a TLU device component as follows:
Setting Up the TLU <SCSI_controller> <SCSI_ID> <SCSI_LUN>
Where:
Assigning Data <SCSI_controller> = chain number of the controller

Movers a Username <SCSI_ID> = SCSI ID (target) of the controller
and Password <SCSI_LUN> = logical unit number (LUN) of the controller
Setting Environment Note: For backups with a NS-Series Celerra Network Server, a media interface adapter
Variables
(MIA) adapts the Fibre Channel AUX-0 port from an HSSDC copper interface to an LC
optical (1 Gb) interface. Instructions on how to install a MIA in an NS series Celerra are
Configuring Your
documented in individual setup instructions provided with each system.
Backup Software
Use this procedure to connect the Data Movers to the TLU via SCSI, and to record
device names.
Step Action
1. From the Control Station, halt each Data Mover to be connected to the TLU and confirm
Backing Up a VDM File that it has been halted. Use this command syntax:
System with NDMP $ server_cpu <movername> -halt -monitor now
Where:
Managing NDMP <movername> = name of the specified Data Mover
Backups on Celerra Example:
To halt the Data Mover running on server_2, type:
$ server_cpu server_2 -halt -monitor now
2. Run /nas/sbin/getreason and make sure the status is powered off.
3. Cable each Data Mover to the TLU. Refer to Data Mover-to-TLU Cabling Examples on
page 13 for more information.
4. Turn on the TLU and verify that it is online.
5. Restart each Data Mover connected to the TLU and confirm that it has restarted using this
command syntax:
Where:
Example:
To restart server_2, type:
The output is similar to the following:
server_2: reboot in progress 0.0.3.4 done

NetVault
Step Action
6. After the Data Mover has restarted, verify that the Data Mover can recognize its TLU
device. Use this command syntax:
$ server_devconfig <movername> -probe -scsi -nondisks
Where:
For example, to confirm that server_2 can recognize its TLU devices, type:
$ server_devconfig server_2 -probe -scsi -nondisks
7. Save the Data Mover’s TLU devices to the Celerra Network Server database. Use this
command syntax:
$ server_devconfig <movername> -create -scsi -nondisks
Where:
<movername> = name of the specified Data Mover.
Example:
$ server_devconfig server_2 -create -scsi -nondisks
8. List the device addresses. You will need to record this information in step 8. To list the
devices and their addresses, use this command syntax:
$ server_devconfig <movername> -list -scsi -nondisks
Where:
For example, to list the devices for server_2, type:
$ server_devconfig server_2 -list -scsi -nondisks
The output will look similar to the following:
server_2 :
scsi device table
name addr type info
jbox1 c1t0l0 jbox ATL P1000 62200501.21
tape2 c1t4l0 tape QUANTUM DLT7000 245Fq_
tape3 c1t5l0 tape QUANTUM DLT7000 245Fq_
9. Record the device name information as shown in Table 7, which follows this procedure.
You will need the device names when you configure your backup software.
10. Perform this procedure for each Data Mover attached to the TLU.

NetVault
Table 7 shows an example of the configuration information you should record. You
will need this information when you configure your backup software.
When you configure a stand-alone tape drive in your backup software, you can add
a c or u prefix to the Celerra Network Server device name to specify whether tape
compression is used. To turn on tape compression, prefix the device name with c;
to turn off compression, prefix the device name with u. When no prefix is specified,
the default compression setting for the tape drive is used.
Note: When configuring stand-alone tape drives, EMC recommends prefixing the Celerra
Network Server device name with c in your backup software. This ensures that tape
compression is used during a backup. For example, to use tape compression for the device
C1T0L0, enter cC1T0L0 as the device name.
Table 7 Sample Device Name Information
Resulting
Data Mover TLU SCSI Port Device Component
Device Name
server_x chain 1, target 0, LUN 0 C1T0L0 Robot
server_y chain 1, target 4, LUN 0 C1T4L0 Tape Drive 1
server_z chain 1, target 5, LUN 0 C1T5L0 Tape Drive 2

NetVault
Assigning Data Movers a Username and Password
NDMP configuration for your backup software and Celerra Network Server requires
that you set a trusted username and password for each NDMP-Host Data Mover.
Configuring Data
Movers Note: The only username recognized by the Celerra Network Server is ndmp. Therefore,
enter ndmp as the username for each NDMP-Host Data Mover and when configuring your
backup software.The password must match the password you enter in Setting Environment
Setting Up the TLU Variables on page 34.
With NIS
Assigning Data
Movers a Username For Network Information Service (NIS) installations, the username and password
and Password must match the username and password in the NIS database. If you are using NIS,
enter the following into the NIS database:
Setting Environment
Variables ◆ ndmp as the user ID
◆ Same password to be entered when you configure your backup software
Configuring Your
Backup Software Note: NIS must be enabled on every NDMP-Host Data Mover.
Without NIS
If you do not have NIS, use this procedure to assign a user account name and
password to the NDMP-Host Data Movers.
Backing Up a VDM File Step Action

System with NDMP
1. To assign a user account name and password to one or more Data Movers, log in to the
Managing NDMP Celerra Network Server Control Station as nasadmin and switch user to root by typing:
Backups on Celerra $ su
Note: The su- command will fail. You must use the su command.
2. Type the root password when prompted.

NetVault
Step Action
3. From /nas/sbin/, use the appropriate command syntax, as follows:

Text method:
# server_user <movername> -add -password <password>
MD5 password encryption method:
# server_user <movername> -add -md5 -password <password>
Where:
<password> = password you want to assign to the Data Mover; passwords have a six-
character minimum and an eight-character maximum
Output:
Creating new user ndmp
User ID: mandatory field
Group ID: mandatory field
Comment: optional field
Home directory: optional field
Shell: optional field
Changing password for user ndmp
New password: same password to be configured in NDMP backup
software (minimum 6 characters, maximum 8)
Retype new password:
server_2 : done
In the output, the two mandatory fields, User ID (UID) and Group ID (GID), are integers.
Note: The Celerra Network Server accesses a Data Mover by its internal name
(movername), which is server_2 in the sample output.
Text method example:

# server_user server_2 -add -password ndmp
MD5 encryption method example:
# server_user server_2 -add -md5 -password ndmp
4. Repeat steps 1, 2, and 3 for each NDMP-Host Data Mover.

To assign the same user account and password to all Data Movers in the Celerra Network
Server cabinet, from /nas/sbin/, use the appropriate command syntax, as follows:
Text method:
# server_user ALL -add -password <password>
MD5 password encryption method:
# server_user ALL -add -md5 -password <password>
Where:
<password> = password you want to assign to the Data Mover; passwords have a six-
character minimum and an eight-character maximum
Example:
# server_user ALL -add -password ndmp
To use the MD5 password encryption method, from nas/sbin/, type:
# server_user ALL -add -md5 -password ndmp

NetVault
Setting Environment Variables
Table 8 shows environment variables supported by the Celerra Network Server.
Check your backup vendor’s documentation for more information about
Configuring Data environment variable requirements, as backup vendors use and implement
Movers variables differently.
Note: If you are backing up NT attributes, be sure that HIST=y and OPTIONS=NT.
Setting Up the TLU
Assigning Data
Table 8 Environment Variables
Movers a Username
and Password Possible Default
Variable Description
Values Value
Setting
Environment BASE_DATE Obtained from N/A Incremental count and date/time of
Variables the NDMP data previous backup operation.
server for the
Configuring Your previous backup Note: This variable works in conjunction
Backup Software operation or set with DUMP_DATE.
to 0 (zero) for a
full backup. When BASE_DATE is specified, LEVEL is
ignored. For more information, refer to
Backup Levels with Celerra and NDMP on
page 35.
Backing Up a VDM File DIRECT y/n n This value (along with the HIST variable)
System with NDMP must be set to y before you perform a
backup if you want to use DAR when
recovering files.
Managing NDMP
Backups on Celerra
DUMP_DATE Obtained from N/A Incremental count and date/time of current
the NDMP data backup operation.
server for the
current backup Note: This variable works in conjunction
operation only if with BASE_DATE.
BASE_DATE is
specified by the For more information, refer to Backup
backup client as Levels with Celerra and NDMP on page 35.
part of the
environment.
EMC_OFFLINE y/n n By default, the Celerra backs up only offline

DATA attributes.
Yes specifies that Celerra back up data, as
well as attributes.
This variable applies only when using
Distributed HSM. Refer to the Configuring
DHSM on Celerra technical module for
more information.
FILESYSTEM <pathname> N/A The device or file system to be backed up.

NetVault
Table 8 Environment Variables (Continued)
Possible Default
Variable Description
Values Value
HIST y/n n Determines whether a file history is

created. This must be set to y before you
perform a backup to use direct access
restore (DAR) when recovering files.
LEVEL 0–10 0 Dump level.

For more information on backup levels,
refer to Backup Levels with Celerra and
NDMP on page 35.
OPTION NT NT Saves NT attributes.

LK for tar and Follows symbolic links.
AT dump Preserves access time in archive mode.
MI/MD/MM Restores collision policy for localization.
PREFIX <pathname> N/A PREFIX can be used in place of

FILESYSTEM for backward compatibility.
TYPE tar or dump N/A The data type.
Note: Dump format does not cross file

system boundaries.
VLC y/ n n Specifies an NDMP volume-level copy to

tape.
Note: You must use a read-only file system

for a volume-level copy.
For information on replicating data, refer to

the Using Celerra Replicator technical
module.
Backup Levels with Celerra and NDMP

A token-based incremental backup uses the BASE_DATE and DUMP_DATE
environment variables to invoke full and incremental backups. In a token-based
backup, the NDMP client, rather than the data server (Data Mover), maintains the
database of backup time stamps, which are used to identify files that should be
included in incremental backups.
The BASE_DATE environment variable specifies the incremental count field and the
date/time of a previous backup to be used as the base for a current incremental
backup. The NDMP client never computes the value of BASE_DATE. Either
DUMP_DATE obtains it from the NDMP data server or the NDMP client sets it to zero
to request a full backup.
The DUMP_DATE environment variable specifies the dump-date token for the
current backup operation. At the end of a successful backup operation, the NDMP
client should retrieve the DUMP_DATE environment variable. It retrieves this variable

NetVault
by issuing an NDMP_DATA_GET_ENV request while the NDMP data server is in a
halted state. DUMP_DATE is returned only if BASE_DATE was previously specified
by the NDMP client as part of the backup environment. When BASE_DATE is
specified, the LEVEL environment is ignored.
NDMP defines 0–9 for dump levels, with level 0 being a full backup. For
incremental-backup levels 1–9, only changes since the next available lower-level
incremental backup or since a full backup are copied. Celerra NDMP supports level
10, which allows any number of incremental backups. It backs up all files modified
since the most recent backup, which can be a level 10 or lower, if no level 10
backup was run previously.

NetVault
Configuring Your Backup Software
Perform the steps in this section from your backup software. These procedures
provide guidelines for configuring your backup software with the Celerra Network
Configuring Data Server. Refer to your backup software vendor’s documentation for more
Movers information. A list of documents appears in Related Information on page 74.
Setting Up the TLU Guidelines

The following guidelines apply to your backup software configuration:
◆ You must configure Data Mover access from your backup software before you
Assigning Data
Movers a Username
can carry out any operations. You enable access to the NDMP-Host Data Mover
and Password by entering a trusted user account name and password in your backup software
that match those assigned to each NDMP-Host Data Mover.
Setting Environment
Variables
In your backup software, you must use ndmp as the username and the same
password that you used in Assigning Data Movers a Username and Password
on page 32.
Configuring Your
Backup Software ◆ When configuring stand-alone tape drives in your backup software, EMC
recommends prefixing the Celerra Network Server device name with c. This
ensures that tape compression is used during a backup. For example, to use
tape compression for the device C1T0L0, enter cC1T0L0 as the device name.
Without a prefix, the default compression setting for the tape device is used.
Refer to Setting Up the TLU on page 29 for information on determining Celerra
Network Server device names.
System with NDMP ◆ Currently, only full backups are supported with BakBone NetVault and Celerra.
For more information on your third-party software, refer to the documents listed in
Managing NDMP Related Information on page 74.
Backups on Celerra

NetVault
Configuration Steps
The steps in this section assume that the robot device is directly attached to the
NDMP-Host Data Mover. To perform the configuration steps in this section, you
Configuring Data must know the cabling configurations between the NDMP-Host Data Movers and
Movers the tape drives. You perform these steps at the backup host.
Note: For drive index information, refer to the TLU manufacturer’s documentation.
Setting Up the TLU
This section describes how to configure your BakBone NetVault software for NDMP
backups with the Celerra Network Server. The procedures in this section are based
Assigning Data on NetVault Version 7.0, which was qualified with the Celerra Network Server. To
Movers a Username access the most up-to-date patch and qualification information, refer to EMC NAS
and Password
Interoperability Matrix on page 12.
Setting Environment Task 1: Add an NDMP Server
Variables
Use this procedure to add an NDMP Server.
Configuring Your
Backup Software Step Action
1. Ensure that version 5.3 or higher of the NDMP APM is installed on your client running the
NetVault backup software.
For a list of qualified APM versions, refer to the EMC NAS Interoperability Matrix. Refer to
the NetVault documentation for information on installing the NDMP APM.
Backing Up a VDM File 2. If you are running NDMP APM Version 5.4 or higher, skip to step 3.
System with NDMP If you are running NDMP APM Version 5.3, you must install the following files on your
NDMP client:
Managing NDMP • The NDMP configuration file ndmpversions.cfg
Backups on Celerra • A new emc-celerra-dump-backup.srn file
For information on installing these files, refer to your NetVault documentation.
3. Add an NDMP Server. Open the Backup window by clicking the Backup button on the
toolbar or by selecting the Operations Backup command.
4. Right-click the NDMP APM and select Add Server to open the initial NDMP Server dialog
box.
5. Enter the required information as follows:

Name — The name of the NDMP-Host Data Mover.
Address(es) — One or more IP addresses to the NDMP-Host Data Mover, separated by
commas.
Port — NDMP server port number, which you must set as 10000.
Account — The username, which should be ndmp. This is the only username recognized
by the Celerra NDMP-Host Data Mover.
Password — Password for the username account. This string should not exceed eight
characters and must match the password you set for the NDMP-Host Data Mover.
6. Click OK. A second dialog box appears.

NetVault
Step Action
7. Enter the required information as follows:

Name — The name you entered in the previous window. You cannot edit this value.
Address(es) — The addresses you entered in the previous window appears. Edit this
value as necessary.
Port — NDMP server port number, which should be set to 10000.
Account — The username, which should be ndmp. This is the only username recognized
by the Celerra NDMP-Host Data Mover.
Password — Password for the username account. This string should not exceed eight
characters and must match the password you set in Assigning Data Movers a Username
and Password on page 32.
Arm(s) — The exact path to the device node for any locally attached tape drive. Separate
multiple paths for multiple nodes with commas. This should include chain, target, LUN
numbers. For example, C1T0L0.
Refer to Table 7 on page 31 and Setting Up the TLU on page 29 for more information.
Tape Drive(s) — The exact path to the device for any locally attached tape drive.
Separate multiple paths for multiple nodes with commas. This should include chain,
target, LUN numbers. For example, C1T0L0.
Refer to Table 7 on page 31 and Setting Up the TLU on page 29 for more information.
8. Click OK.

NetVault
Task 2: Using the Automatic Device Configuration
NetVault 7.0 will automatically locate devices on the network. After you add the
NDMP Server, complete the procedure in this section, which describes how to
Configuring Data recognize and configure a device through the NetVault wizard.
Movers
Note: To manually recognize and configure devices, refer to your BakBone NetVault
documentation.
Setting Up the TLU
Use this procedure to recognize and configure a device through the NetVault
wizard.
Assigning Data
Movers a Username
Step Action
and Password
1. Recognize a device. Launch NetVault and click the Device Management button (or
Setting Environment
select Device Management from the Administration menu. NetVault automatically
Variables
scans the SCSI bus on all NetVault clients and the server.
Configuring Your 2. NetVault searches for a library with serialization capability. If it finds one, a Device
Backup Software Configuration Wizard launches.
3. To autoconfigure the device, select Yes.
4. On the Add Library window, the Name field displays the library name and path, which
you can edit, if desired.
Backing Up a VDM File 5. To set default performance options, select the Configure Performance Options
System with NDMP checkbox. This launches another window after you click Next.
To add a library in a SAN environment where the drives can be seen by many clients,
Managing NDMP select the Scan clients for remote/shared drives checkbox. This launches another
Backups on Celerra window after you click Next.
6. Optional. Configure performance options as follows:

Amount of memory to assign to transfer buffers (Kb)— The default, 257, is equal to
eight buffers of 32 Kb plus 1 Kb. Increasing this value will optimize performance, if
memory permits.
Media Block Size — Increasing the Media Block Size may increase the backup
performance on various device types.
Notes:
If you increase the Media block size, you must also increase the shared memory setting.
The shared memory value must be equal to at least four times the Media Block Size plus
1 Kb.
Use caution when setting block and shared memory size. Total shared memory size also
depends on the operating system you are running.
7. Click Next.

NetVault
Step Action
8. Optional. Rescan for devices. If you do not rescan, the devices previously detected and
stored in cache are used.
a. In the Automatic Device Configuration window, select Scan clients for remote/
shared devices to rescan the bus for devices.
b. From the Add Library window, complete the following:
Re-scan clients for devices — Select to force a rescan for devices.
Select Clients Window — Select any or all clients that may have a device attached.
NetVault scans the selected clients and automatically adds any devices it finds.
9. Click Next.
Once NetVault has scanned and added the devices, you see a window with the following
text:
Devices added successfully.
10. Click Next, and then click Finish.

NetVault
Backing Up a VDM File System with NDMP
A Virtual Data Mover (VDM) is a Celerra Network Server software feature that
enables you to administratively separate CIFS servers and their associated
Configuring Data resources, like file systems, into virtual containers. These virtual containers allow
Movers administrative separation between groups of CIFS servers, enable replication of
CIFS environments, and allow the movement of CIFS servers from Data Mover to
Data Mover. The procedure in this section explains only the NDMP-specific
Setting Up the TLU
guideline for VDM. For more information on VDM, refer to the Configuring Virtual
Data Movers for Celerra technical module.
In a CIFS environment, when you use NDMP to back up a VDM-configured file
Assigning Data
Movers a Username system, you must specify the full mount path of the file system. To retrieve the full
and Password path, use the server_mount command.
Setting Environment
Variables
Step Action
1. To retrieve the full mount path of a file system, use this command syntax:
Configuring Your $ server_mount <movername> | grep <fs_name>
Backup Software Where:
<movername> = name of the Data Mover
<fs_name> = name of the file system for which you want the full path
Example:
$ server_mount server_2 | grep ufs1
Output:
Backing Up a VDM File ufs1 on /root_vdm_1/ufs1
uxfs,perm,rw
System with NDMP
Note: /root_vdm_1 in this example indicates that the file system is a VDM-configured
Managing NDMP file system. When using NDMP to back up this file system, you would enter in your backup
Backups on Celerra software /root_vdm_1/ufs1 as the full path.
2. In your NDMP backup software, enter the pathname that was revealed in step 1. For
example:
/root_vdm_1/ufs1
Note: Refer to your backup software vendor’s documentation for more information on
specifying file-system pathnames in your NDMP backup software.

NetVault
Managing NDMP Backups on Celerra
This section describes how to view and dynamically modify NDMP backup
parameters, and how to monitor backup performance statistics. It includes:
Configuring Data
Movers
◆ Viewing and Modifying Parameters, which describes the commands you use to
view details on and dynamically modify parameters that affect backup
performance.
Setting Up the TLU
◆ Viewing Backup Statistics on page 52, which describes the commands you use
to view detailed backup and restore performance statistics.
Assigning Data
Movers a Username
Viewing and Modifying Parameters
and Password
You can view and dynamically modify performance-related backup parameters
using the server_param command or through Celerra Manager. This technical
Setting Environment
Variables
module describes only the command-line procedures. Refer to the online help for
information on using Celerra Manager to modify parameter values. For more
information on all Celerra Network Server parameters, refer to Celerra Network
Configuring Your Server Parameters Guide.
Backup Software
This section includes the following tasks.
Action Procedure
For a particular Data Mover, view the tunable Viewing Backup Parameters on page 44
backup parameters and their values.
System with NDMP View information on a specified parameter or Viewing Parameter Information on page 45
view information on all tunable backup
parameters for a specified Data Mover.
Managing NDMP
Backups on Celerra
Modify the value of a tunable backup parameter. Modifying Parameters on page 48

NetVault
Viewing Backup Parameters
Use this command to view tunable backup parameters and their values.
Configuring Data Action

Movers
To view parameters and their values, use this command syntax:
$ server_param <movername> -facility <facility_name> -list
Setting Up the TLU
Where:
<facility_name> = name of the facility to which the parameter belongs
Assigning Data Example:
Movers a Username For example, to view a list of PAX parameters on server_2, type:
and Password $ server_param server_2 -facility PAX -list
Setting Environment Output

Variables
name facility default current configured
paxWriteBuff PAX 64 128 30
Configuring Your paxStatBuff PAX 128 128
Backup Software nFTSThreads PAX 8 8
nThread PAX 64 16
nPrefetch PAX 8 8
nRestore PAX 16 16
Notes
Backing Up a VDM File Note: Parameter and facility names are case-sensitive.
System with NDMP
Where:
Managing NDMP name = name of the parameter
Backups on Celerra facility = facility to which the parameter belongs
default = default value for the parameter
current = value set on the Data Mover
configured = value set through the server_param command
Note: The configured and current values can differ when:

— you use the server_param command to configure the value of a parameter (different from the
default), and
— to take effect, the parameter change requires user action, which you have not yet taken.

NetVault
Viewing Parameter Information
Use this procedure to view details on a specific parameter, including current,
default, and possible values. Refer to Parameter Summary on page 49 for
Configuring Data parameter descriptions.
Movers
Action
Setting Up the TLU To view detailed information on a specific parameter, use the following command syntax:
$ server_param <movername> -facility <facility_name> -info <param_name>
Where:
Assigning Data <movername> = name of the specified Data Mover
Movers a Username <facility_name> = name of the facility to which the parameter belongs
and Password <param_name> = name of the parameter you want to view
Example:
Setting Environment For server_2, to view detailed information on the paxWriteBuff parameter, type:
Variables
$ server_param server_2 -facility PAX -info paxWriteBuff
Configuring Your Output

Backup Software
name = paxWriteBuff
facility_name = PAX
default_value = 64
current_value = 128
configured_value = 128
user_action = none
change_effective = immediate
range = (1,2048)
System with NDMP
description = Number of buffers in tape write queue per
backup session
Managing NDMP
Backups on Celerra Notes
Note: Parameter and facility names are case-sensitive.
The output in this example shows that the paxWriteBuff parameter value has been increased
from the default value to 128.
Where:
facility_name = facility to which the parameter belongs
default_value = value set as the default
current_value = value set on the Data Mover
configured_value = value configured with the server_param command
user_action = action necessary for the parameter change to take effect
change_effective = when the parameter change takes effect
range = range of possible values
description = refer to Parameter Summary on page 49 for parameter descriptions

NetVault
To view information on all parameters for a particular Data Mover or all Data
Movers, use this command syntax.
Action
To view all parameters for a particular Data Mover, use this command syntax:
$ server_param <movername> -facility <facility_name> -info -all
Where:
<movername> = name of the Data Mover
Example:
$ server_param server_2 -facility PAX -info -all
Output
Note: For an explanation of the categories displayed in this output, refer to the previous example.
server_2 :
name = paxWriteBuff
facility_name = PAX
default_value = 64
current_value = 64
user_action = none
range = (1,1024)
description = Number of buffers in tape write queue per
backup session
name = paxStatBuff
facility_name = PAX
default_value = 128
current_value = 128
configured_value =
user_action = none
range = (1,2048)
description = Number of buffers in stat queue per backup
session
name = nRestore
facility_name = PAX
default_value = 16
current_value = 30
user_action = none
range = (1,64)
description = Number of worker threads per restore session

NetVault
Output
name = nFTSThreads
facility_name = PAX
default_value = 8
current_value = 8
user_action = none
range = (1,256)
description = Number of FTS threads per backup session
name = nThread
facility_name = PAX
default_value = 64
current_value = 32
user_action = none
range = (1,128)
description = Number of worker threads per backup session
name = nPrefetch
facility_name = PAX
default_value = 8
current_value = 8
user_action = none
range = (1,32)
description = Number of tape records prefetched per worker
thread

NetVault
Modifying Parameters
This section describes how to modify a parameter value. Refer to Parameter
Summary on page 49 for parameter descriptions.
Configuring Data
Movers
! !
CAUTIONS
◆ Parameters allow you to increase the number of threads and data blocks used
Setting Up the TLU during the backup and restore processes. However, more threads and data
blocks increase the amount of Data Mover memory dedicated to the backup and
restore processes, which can negatively impact other processes running on the
Data Mover.
Assigning Data
Movers a Username ◆ Parameter changes made while backups are running on a Data Mover take effect
and Password only after all backups on the Data Mover have ceased.
Setting Environment
Variables
Use this command to modify a parameter.
Configuring Your Action

Backup Software
To modify a parameter, use this command syntax:
$ server_param <movername> -facility <facility_name> -modify
<param_name> -value <new_value>
Where:
Backing Up a VDM File <param_name> = name of the parameter
System with NDMP
<new_value> = value you want to set for the specified parameter
Example:
Managing NDMP
Backups on Celerra
For example, to set the paxWriteBuff parameter to 128, type:
$ server_param server_2 -facility PAX -modify paxWriteBuff -value 128
Output
server_2 : done
Notes
Parameter and facility names are case-sensitive.

NetVault
Parameter Summary
Table 9 and Table 10 on page 51 describe performance-related parameters.
Table 9 includes the parameters you can modify with the server_param
Configuring Data command or through Celerra Manager. (Refer to the online help for information on
Movers using Celerra Manager). The nontunable parameters in Table 10 on page 51 must
be edited in the param file, as described in Configuring Data Movers on page 21.
For a complete list of Celerra Network Server parameters, refer to Celerra Network
Setting Up the TLU
Server Parameters Guide.
Table 9 Tunable Parameters: Summary
Assigning Data
Movers a Username Value Range
and Password
Facility Parameter 510 Data 507 Data Comment/Description
Setting Environment Movers & Movers &
Variables Higher Lower
PAX nFTSThreads 1–256 1–256 Specifies the number of threads

Configuring Your default=8 default=8 for a single backup job.
Backup Software More threads decrease the
likelihood that the NASA thread
will be a bottleneck.
Example:
param PAX nFTSThreads=128
PAX nPrefetch 1–32 1–8 Specifies the amount of data each

Backing Up a VDM File default=8 default=8 backup thread prefetches from
System with NDMP disk before finishing the file read
and writing data to tape.
Managing NDMP The exact prefetch amount =
Backups on Celerra nPrefetch times
<tape_block_size>
Where:
<tape_block_size> = a value
determined by the backup
software vendor. Most backup
software vendors use a value
close to 64 KB as the tape block
size.
Increasing this value allows each
backup thread to read more data,
but it also increases Data Mover
memory use.
Example:
param PAX nPrefetch=16
PAX nRestore 1–64 1–32 Specifies the number of restore

default=16 default=16 threads per restore job.
More threads can increase the
speed with which data is restored.
Example:
param PAX nRestore=128

NetVault
Table 9 Tunable Parameters: Summary (Continued)
Value Range
Facility Parameter 510 Data 507 Data Comment/Description

Movers & Movers &
Higher Lower
PAX nThread 1–128 1–64 Specifies the number of backup

default=64 default=64 threads.
Increasing the number of backup
threads could increase the speed
with which data is retrieved from
disk.
Example:
param PAX nThread=64
PAX paxStatBuff 1–2048 1–2048 Specifies the number of buffers

default=128 default=128 between the threads that send and
receive metadata (NASA) and
read data from disk (NASS).
More buffers can increase the
speed with which metadata is
provided.
Example:
param PAX paxStatBuff=1024
PAX paxWriteBuff 1–1024 1–64 Specifies the number of buffers

default=64 default=64 between the threads that read file
data (NASA) and write data to tape
(NASW).
More buffers can enhance tape
streaming.
Example:
param PAX paxWriteBuff=640

NetVault
Table 10 shows the performance-related backup parameters that require a Data
Mover reboot to take effect. These parameters are not tunable through the
server_param command.
Table 10 Nontunable Parameters: Summary
Facility Parameter Value Range Comment/Description
PAX paxReadBuff 16–512 Specifies the number of buffers between the

default=64 threads that read data from tape (NASA) and
restore it to disk (NASW).
More buffers can enhance tape streaming, and
therefore increase the restore speed.
Example:
param PAX paxReadBuff=16
Note: More buffers increase the amount of

Data Mover memory dedicated to the restore
process.
PAX writeToArch 0 or 1 (default) For server_archive, determines whether

the backup writes to a file.
PAX writeToArch = 1 specifies that
server_archive write to a file.
PAX writeToArch = 0 specifies that
server_archive discard the data without
writing to a file.
PAX writeToTape 0 or 1 (default) Determines whether the backup writes to tape.

PAX writeToTape = 1 specifies that the
backup write to tape.
PAX writeToTape = 0 specifies that the
backup data be discarded.
Specifying 0 allows you to test the backup
speed while eliminating tape-drive speed as a
performance factor.

NetVault
Viewing Backup Statistics
This section describes how to use the server_pax command to view statistics
related to your file-system data and backup performance. The output is grouped by
Configuring Data thread group, which performs various functions within the multithreaded backup
Movers and restore process. For more information, refer to Multithreaded Backup and
Restore Design on page 16.
Setting Up the TLU Use this command to view statistics on a backup session in progress.
Action
Assigning Data To view statistics on a backup session in progress, use this command syntax:
Movers a Username
and Password $ server_pax <movername> -stats -verbose
Where:
Setting Environment <movername> = name of the specified Data Mover
Variables Example:
For example, to view statistics for a backup running on server_2, type:
$ server_pax server_2 -stats -verbose
Configuring Your
Backup Software

System with NDMP
Managing NDMP
Backups on Celerra

NetVault
Output
************** SUMMARY PAX STATS ****************

---- NASS STATS ----
** nass thid 0 **
Total file processed: 16
throughput: 2 files/sec
Total nass wait nasa count: 13
Total nass wait nasa time: 236 msec
Total time since last reset: 8 sec
fts_build time: 0 sec
getstatpool: 0 buffersputstatpool: 128 buffers
---- NASA STATS ----

** nasa thid 0 (BACKUP) **
Backup root directory: /s4fs1/adm
Total bytes processed: 104937747
Total file processed: 16
throughput: 11 MB/sec
average file size: 6404KB
Total nasa wait nass count: 1
Total nasa wait nass time: 13 msec
Total time since last reset: 8 sec
Tape device name: /dev/c0t5l0
0 size file processed: 3
1 -- 8KB size file processed: 8
8KB+1 -- 16KB size file processed: 0
64KB+1 -- 1MB size file processed: 2
1MB+1 -- 32MB size file processed: 1
32MB+1 -- 1GB size file processed: 1
1G more size file processed: 0
---- NASW STATS ----

nasw00 BACKUP (in progress)
Session Total Time: 00:00:08 (h:min:sec)
Session Idle Time: 00:00:00 (h:min:sec)
KB Tranferred: 98406 Block Size: 64512 (63 KB)
Average Transfer Rate: 12 MB/Sec 42 GB/Hour
Average Burst Transfer: 12 MB/Sec 42 GB/Hour
Write Block Counters: 1562/0 (List/Direct)
__Point-in-Time__ (over the last 10 seconds):
Rate=8 MB/Sec Burst=11 MB/Sec Idle=11 msec/sec
Get Pool: 63 buffers Put Pool: 0 buffers
Compression Page retrieved 00:00:08 (h:min:sec) ago:
ReadC=2.1 WriteC=2.1 Read=310692 KB Written=408327 KB

NetVault
Notes
Note: When you use verbose mode, information on file size distribution is included in the output.
Where:
NASS STATS = thread responsible for traversing the file system and providing metadata for each
directory and/or file
Total file processed = total number of files and/or directories for which metadata was
processed
Total NASS wait NASA count = number of times NASS waited for NASA
Total NASS wait NASA time = amount of time NASS waited for NASA
Total time since last reset = time since the last reset; a reset occurs automatically after a
backup completes
fts_build time = time spent building the file system or directory tree
getstatpool = if the value is consistently 0, then NASA may be slowing down the backup
putstatpool = if the value is consistently 0, then NASS may be slowing down the backup
NASA STATS = thread responsible for writing file header information, reading file data, and writing
to the buffer
Backup root directory = directory being backed up
Total bytes processed = bytes backed up since last reset or start of current backup
Total file processed = number of files backed up since start or reset of current backup
Throughput = how fast NASA processed data
Average file size = average size of file for current backup
Total nasa wait nass count time = number of times NASA waited for NASS
Total nasa wait nass time = amount of time NASA waited for NASS
Total time since last reset = amount of time since the backup statistics were reset; a
reset occurs automatically after a backup completes
Tape device name = target device for the backup data
File size statistics = statistics on the size of files backed up since the start or reset of the
current backup
NASW STATS = thread responsible for getting data from the buffer pool, writing it to tape, or sending
it to a remote Data Mover
Session total time = total time of current session
Session idle time = idle time for current session
KB transferred = total KB transferred
Average transfer rate = per-second and per-hour transfer rate for current session’s data
Average burst transfer = burst transfer rate in MB/s and GB/s
Write block counters (List/Direct) = scatter/gather write count
_Point-in-time_ (over the last 10 seconds) = information on data processed during a
10 second point-in-time
Rate= transfer rate in MB/s
Burst= burst transfer rate in MB/s
Idle= amount of time NASW was idle in ms
Get pool = number of buffers in get pool; if value is consistently 0, then NASA and NASS may be
slowing down the backup
Put pool = number of buffers in put pool; if value is consistently 0, then the tape may be slowing
down the backup
Compression rate retrieved = compression rate
ReadC = read compression rate at the tape device
WriteC = write compression rate at the tape device
Read = amount of data read in KB
Written = amount of data written in KB

NetVault
Resetting Backup Statistics
You can use the server_pax command to reset the statistics for a backup session
in progress. Statistics are compiled for each backup session and automatically
Configuring Data reset when a backup completes.
Movers
Use this command to reset the statistics for a backup session in progress.
Setting Up the TLU Action
To reset statistics for a backup session, use this command syntax:

$ server_pax <movername> -reset
Assigning Data
Where:
Movers a Username
and Password <movername> = name of the specified Data Mover
Example:
Setting Environment For example, to reset the statistics for a backup running on server_2, type:
Variables $ server_pax server_2 -reset
Output
Configuring Your
Backup Software
server_2 : done

System with NDMP
Managing NDMP
Backups on Celerra

NetVault
Command Syntax Summary
This section summarizes the syntax for commands used in this technical module.
Command Reference
server_cpu Table 11
server_devconfig Table 12
server_user Table 13 on page 57
sevrer_log Table 14 on page 57
server_param Table 15 on page 58
server_pax Table 16 on page 58
For a more detailed synopsis of the command or to view syntax conventions, refer
to the Celerra Network Server Command Reference Manual.
Table 11 server_cpu Syntax Summary
Command Description
server_cpu {<movername> | ALL} Performs an orderly, timed or immediate halt or

reboot of the Data Mover.
Option Description
-halt Performs a logical shutdown of a Data Mover.

To restart a Data Mover, perform a -reboot.
-monitor now Polls and displays the boot status until

completion of the halt or reboot.
-reboot now Performs a logical shutdown and restart of a

Data Mover.
Table 12 server_devconfig Syntax Summary
Command Description
server_devconfig {<movername> | Queries, saves, and displays the device

ALL} configuration connected to the specified Data
Mover(s).
Option Description
-create Queries for devices and saves them into the

device table database.

NetVault
Option Description
-list Lists the device table database that has been

saved on the Data Mover.
-probe Queries and displays devices, but does not

save them into the database.
-scsi Limits operations to SCSI devices. This option

customizes the -create, -list, or -probe
operation.
-nondisks Limits operations to nondisks such as tapes,

jukeboxes, and gatekeeper devices. This option
customizes the -create, -list, or -probe
operation.
Table 13 server_user Syntax Summary
Command Description
server_user {<movername> | ALL} Allows you to create, modify, or delete a user

account for a specified Data Mover.
Option Description
-add [-md5] [-password] <name> Adds a new user account with the login
<name>. If you are creating a user account with
MD5 password encryption, use the -md5
option. The -password option allows you to
specify a password for the new user account.
Passwords have a six-character minimum.
Table 14 server_log Syntax Summary
Command Description
server_log {<movername> | ALL} Displays the log generated by the specified

Data Mover.

NetVault
Table 15 server_param Syntax Summary
Command Description
sevrer_param {<movername> | ALL} Allows you to modify parameter values without

rebooting the Data Mover.
Options Description
-info Displays and describes the facilities you can

modify with the server_param command.
-facility { <facility_name> | -all} Specifies the facility to which the -list, -

info, or -modify option applies, or specifies
all facilities.
-list For the specified facility, lists the parameters

you can modify with the server_param
command and the parameters’ default, current,
and configured values.
-info { <param_name> | -all } Displays information on the specified parameter

or on all parameters for the specified facility.
-facility <facility_name> -modify Allows you to modify the value of the specified
<param_name> -value <new_value> <param_name> and changes the value to
<new_value>; <facility_name> is the
facility for <param_name>.
Table 16 server_pax Syntax Summary
Command Description
sevrer_pax {<movername> | ALL} Allows you to view statistics related to your

backup.
Options Description
-stats Displays backup and restore performance

statistics for a backup session in progress.
-reset Resets the backup statistics for a backup

session in progress.
-verbose Displays backup performance statistics and file-

size distribution data for a backup session in
progress.

NetVault
Troubleshooting NDMP Backups
This section provides guidance for troubleshooting problems you may encounter
running NDMP backups with the Celerra Network Server. You can query the EMC
WebSupport database for related problem information, obtain release notes, or
report a Celerra technical problem to EMC at Powerlink™, EMC’s secure extranet
site, at http://powerlink.emc.com. For additional information about using
Powerlink and resolving problems, refer to the Celerra Problem Resolution
Roadmap technical module on the Celerra Network Server User Information CD.
Troubleshooting Checklist
Review this checklist for tips on troubleshooting your NDMP backup.
❑ Is the backup or restore spanning multiple tapes? If yes, are more tapes available when
the job spans to the next tape?
❑ Check the TLU physical connections and correct any loose connections or incorrectly
labeled hardware. Refer to Setting Up the TLU on page 29.
❑ Check the server log to ensure the parameters executed successfully.
To read the server log for a Data Mover, use this command syntax:
$ server_log <movername> | grep param
Where:
Refer to Configuring Data Movers on page 21 for more information on setting

parameters.
❑ Are the necessary parameters for NDMP and PAX set on the Data Mover? Refer to
Configuring Data Movers on page 21.
❑ Try using the following command syntax:
$ server_devconfig <movername> -probe -scsi -nondisks
Where:
Verify that all the devices are listed correctly and note any problems.
❑ Confirm in the EMC NAS Interoperability Matrix that your Celerra Network Server,
backup software version, and hardware are supported for NDMP backups with the
Celerra Network Server. Refer to EMC NAS Interoperability Matrix on page 12 for
instructions on accessing this document.
❑ Have you created the username and passwords on all NDMP-Host Data Movers? Refer
to Assigning Data Movers a Username and Password on page 32. Have you used the
same usernames and passwords when configuring Data Mover access in your backup
software?
❑ Have the TLU device names been recorded correctly and entered during configuration
of the backup software? Refer to Recording TLU Information on page 29 and to your
backup software vendor’s documentation.
❑ If your backup vendor supplies utilities for checking the physical and logical paths
between the backup server and the TLU devices, confirm that these paths are valid.

NetVault
❑ Test a backup or restore using the Celerra Network Server server_archive utility. By
eliminating the NDMP protocol, you may be able to eliminate possible problems and
more easily troubleshoot issues. Refer to the technical module Using the server_archive
Utility.
If the backup still doesn’t work correctly after you check these things, contact the
backup software vendor for further support.
Reporting a Problem
Refer to the Celerra Problem Resolution Roadmap technical module on the Celerra
Network Server User Information CD for additional information on troubleshooting
resources and processes. In addition to the general information in the Celerra
Problem Resolution Roadmap, you should gather the following backup-specific
information before reporting a problem to the EMC Support Center.
❑ At what stage did the problem occur?
❑ What is the version and patch number of your backup software?
❑ Is your backup software installed on a UNIX or Windows platform?
❑ What is the IP and hostname of the system running the backup software?
❑ Are you backing up CIFS files, NFS files, or both?
❑ What model is the TLU?
❑ Does your environment have a two- or three-way backup configuration?
Server Log Messages

This section includes:
◆ An explanation of the format and component parts of a server log message.
◆ A list of NDMP and PAX server log messages, including descriptions and
possible remedies.
For a complete list of server log messages for the Celerra Network Server, refer to
the Celerra Network Server Error Messages Guide.
Reading Log Messages
Each server log message has additional information that appears with the message
text related to a particular event. The following server log message shows a sample
NDMP message in context:
Server Log
2004-01-05 01:20:35: NDMP: 3: BlockBuf count in PAX Pool: 4
Table 17 lists and describes the server log components and includes the
corresponding portion of the sample message. A description of the severity levels
appears in Table 18.
Table 17 Server Log Description
Log Component Description Example
Date Displays the date. 2004-01-05

NetVault
Table 17 Server Log Description (Continued) (Continued)
Log Component Description Example
Time Displays the time. 01:20:35
Category Lists the part of the Celerra NDMP

Network Server from which the
error originates.
This technical module covers
only the NDMP and PAX
categories. For more
information on other
categories, refer to the Celerra
Network Server Command
Reference Manual.
Severity level Indicates the importance of the 3

event. Values can be 0 through
7, with 0 indicating the highest
level of importance.
These levels are defined in
Table 18.
The default severity for each
module is set to 4. Whenever
the Data Mover tries to
generate a log message, it
provides the log severity level
and the module name. If the
given severity is less than or
equal to the current severity
level for the given module, the
message goes to server log;
otherwise, it is ignored.
Message text The log message. BlockBuf count in PAX

Pool: 4
Table 18 defines the severity levels associated with the server logs.
Table 18 Server Log Message Severity Levels
Severity
Meaning
Level
0 Emergency
1 Alert
2 Critical
3 Error
4 Warning

NetVault
Table 18 Server Log Message Severity Levels (Continued)
Severity
Meaning
Level
5 Notice
6 Info
7 Debug
Server Log Messages for NDMP and PAX

Table 19 shows the server log messages from the NDMP and PAX categories,
including an explanation of the message and corrective action. For a complete list
of server log and system log messages, refer to the Celerra Network Server Error
Messages Guide.
Table 19 Server Log Messages
Server Log Messages Definition Corrective Action Other Considerations
/.etc/BackupDates The /.etc/BackupDates No corrective action is There is no impact to a

corrupted, it has been file, which saves backup necessary. previous restore, if
renamed in dates, is corrupted. The backup level has been applicable.
BackupDates.bad and reset. You will need to restart
rebuilt the backup.
<MOVER_LISTEN> before The NDMP client sends a Verify that your backup Refer to EMC NAS
tape open MOVER_LISTEN request software is qualified with Interoperability Matrix on
before a TAPE_OPEN request. Celerra. page 12.
Note: The backup or restore

will fail if the client does not
correct the error.
<MOVER_LISTEN> with A Data Mover listen request Verify that your backup Refer to EMC NAS
read only tape requires a tape write, but the software is qualified with Interoperability Matrix on
tape is in read-only mode. Celerra. page 12.
The NDMP client needs to
send the message in
read/write mode.
3-way DAR unable to fsr Occurs during a three-way Verify that your hardware, Refer to EMC NAS
1234, residualCount 998 direct access restore (DAR). drivers, and backup software Interoperability Matrix on
The forward skip record failed are qualified with Celerra. page 12.
with the remaining records and
the restore fails.
Answer occurred with This point should not be Verify that your backup Refer to EMC NAS
pdi==NULL reached with pdi==NULL. software vendor is qualified Interoperability Matrix on
The Data Mover terminates the with Celerra. page 12.
NDMP job, and the backup
fails.

NetVault
Table 19 Server Log Messages (Continued)
Backup type not Celerra does not support the Verify that the NDMP client is Refer to your backup
supported: ufsdump backup type specified in the using either the tar or dump software vendor’s
NDMP backup software. backup type. documentation and to
Celerra supports the tar and Setting Environment
dump backup types. Variables on page 34.
This message occurs when
Note: The backup will fail
using NDMP version 2.
without a valid backup type
specified.
BlockBuf count in PAX Displays the number of buffers To change the parameter Refer to Configuring Data
Pool: <number> initialized in the pool. This values, edit the param file. Movers on page 21.
message reflects the PAX
ReadBuff parameter.
<number> = number of buffers
Cannot reply connect An error occurred when Verify that your backup Refer to EMC NAS
sending a reply to software vendor is qualified Interoperability Matrix on
CONNECT_OPEN. The Data with Celerra. page 12.
Mover terminates the NDMP
backup job.
cannot send An error occurred when Verify that your backup Refer to EMC NAS
NDMP_CONFIG_GET_TAPE_IN sending a reply to this software vendor is qualified Interoperability Matrix on
FO reply message. The Data Mover with Celerra. page 12.
terminates the NDMP backup
job.
cannot send A reply to this request cannot Verify that your backup Refer to EMC NAS
NDMP_CONNECT_OPEN reply be sent. The Data Mover software vendor is qualified Interoperability Matrix on
terminates the NDMP job. with Celerra. page 12.

NetVault
Can't convert filename These two messages appear Verify that the NDMP Refer to Configuring Data
using the specified together and indicate one of dialect parameter specifies Movers for International
NDMP.dialect, or the following: the correct dialect. Character Sets on page 25.
invalid utf8 filename: • Internationalization on a
0x999 Data Mover is turned on
inode_%3456 is using and the specified dialect
for filename cannot be used to convert
the filename from UTF-8 to
the client’s dialect.
• The original filename is not
a valid UTF-8 name. For
example, if a Celerra client
(which may be a different
client from the NDMP client)
creates a file using a
character outside its own
code page, Celerra saves
the filename using an
invalid UTF-8 name.
In the inode_%3456 error
message, inode_<number>
is used in place of the file
name.
Can't have DIRECT=y/Y, Celerra does not support a In your backup software, For more information about
and RECURSIVE=y/Y recursive restore for a change the recursive restore DAR, refer to the NDMP
directory using DAR. The setting to n. Backup Concepts on page 6
Celerra rejects this type of Verify that your backup section. For information on
restore. software is qualified with environment variables, refer
Celerra. to Setting Environment
Variables on page 34 and to
your backup software
vendor’s documentation.
Can't open file_name These two messages indicate Verify that your backup Refer to EMC NAS
for write in 3214 that the Celerra encountered a software is qualified with Interoperability Matrix on
File <file_name> problem opening a file during a Celerra. The problem may be page 12.
create error in 3294 restore. The file due to a failed backup.
<file_name> is skipped, and
the restore continues.
create /.etc/ Creation of the file You need to restart the

BackupDates file BackupDates failed. This file backup.
failed, error: <error saves backup dates.
message>
The backup is terminated.
<error message> = type of
error, for example, I/O error
Data interface is At the time of a DATA_STOP No action is needed.

already deleted request, the Data interface is
already deleted.
The backup should complete
successfully.

NetVault
Empty archive The FILESYSTEM or PREFIX On the NDMP client, set a Refer to Setting
NDMP environment variable is value for the FILESYSTEM or Environment Variables on
not set in the NDMP client PREFIX environment variable. page 34 and to your backup
software. software vendor’s
documentation.
Error in NDMP restore An error in the restore Verify in the server log that you
arguments, argument argument occurred. specified the correct backup
<argument> <argument> = argument root and path, for example,
name, for example, TYPE verify the spelling and the
pathname.
ERROR MOVER try to The state is illegal for aborting Verify that your backup Refer to EMC NAS
Abort in state <state> the MOVER interface; legal software vendor is qualified Interoperability Matrix on
states are LISTEN, ACTIVE, with Celerra. page 12.
or PAUSED.
<state> = mover interface
state, for example,
NDMP_MOVER_STATE_IDLE
ERROR MOVER try to The state is illegal for setting Verify that your backup Refer to EMC NAS
change record size in record size; only the IDLE software vendor is qualified Interoperability Matrix on
state <state> state is legal. with Celerra. page 12.
state, for example,
NDMP_MOVER_STATE_ACTIVE
ERROR MOVER try to The state is illegal for a Verify that your backup Refer to EMC NAS
Continue in state MOVER_CONTINUE command; software is qualified with Interoperability Matrix on
<state> only the PAUSED state is legal. Celerra. page 12.
state, for example,
ERROR MOVER try to In a three-way configuration, Verify that your backup Refer to EMC NAS
disconnect in state not the mover interface tried to software vendor is qualified Interoperability Matrix on
connected disconnect while in a with Celerra and supports page 12.
disconnected state. three-way backups.
ERROR MOVER try to The NDMP client tried to stop Verify that your backup Refer to EMC NAS
Listen in state <state> the data interface in an invalid software is qualified with Interoperability Matrix on
state. Celerra. page 12.
state, for example,
ERROR MOVER try to Set The state is illegal for setting Verify that your backup Refer to EMC NAS
window in state <state> window size; only LISTEN or software vendor is qualified Interoperability Matrix on
PAUSED states are legal. with Celerra. page 12.
state, for example,

NetVault
ERROR MOVER try to Stop The state is illegal for stopping Verify that your backup Refer to EMC NAS
in state <state> the MOVER interface; only the software vendor is qualified Interoperability Matrix on
HALTED state is legal. with Celerra. page 12.
state, for example,
NDMP_MOVER_STATE_IDLE
ERROR MOVER try to Stop The NDMP client sent a Confirm that your NDMP client Refer to EMC NAS
in state <state> message not compliant with software is qualified with Interoperability Matrix on
Reason:<reason> the NDMP Version 4 Celerra. page 12.
specification. If your software is qualified,
<state> = mover interface then this message is
state, for example, informational only and you do
NDMP_MOVER_STATE_IDLE not need to take any action.
<reason> = reason for pause,
for example,
NDMP_MOVER_PAUSE_EOF
ERROR MOVER type LOCAL This should be a three-way Verify that your backup Refer to EMC NAS
try to Read read, but the mover interface software vendor is qualified Interoperability Matrix on
type is not three-way with Celerra. page 12.
compliant (it is not TCP).
Error on checking An error occurred in the Verify that the file and directory Refer to your backup
restore name list restore name list, which names you want to restore are software vendor’s
contains the file and directory listed correctly. documentation.
names to restore.
Error on environment The NDMP client sent an Verify that the environment Refer to Setting
variable: <variable> invalid environment variable. variable listed in the log Environment Variables on
<variable> = variable message is supported by page 34 and to your backup
associated with the error, for Celerra. software vendor’s
example, LEVEL documentation.
extractFtreeList: bad The backup path provided Ensure that the correct path Refer to your NMDP client
path /xyz does not exist. was specified and that the files documentation for more
specified for backup exist. information.
Note: This path is an absolute

path and is case-sensitive.
level exceeded maximum An incorrect increment level Verify that the backup level Refer to Setting
allowed (11) for backup was specified in the specified by the NDMP client is Environment Variables on
NDMP client software. between 0 and 10. page 34 and to your backup
software vendor’s
documentation.

NetVault
Mover connection error A connection to a three-way Verify that your backup Refer to EMC NAS
(connectDone) Data Mover accepting a TCP software vendor is qualified Interoperability Matrix on
stream failed. with Celerra. page 12.
The NDMP client sent an
invalid command.
Mover continue before A MOVER_CONTINUE request Verify that your backup Refer to EMC NAS
changing tape!!! was sent by the NDMP client software vendor is qualified Interoperability Matrix on
before the tape was changed. with Celerra. page 12.
The backup fails.
Mover not created The NDMP client sent an Verify that your backup Refer to EMC NAS
invalid command. software vendor is qualified Interoperability Matrix on
The mover interface was not with Celerra. page 12.
created when the NDMP client
requested
CONFIG_GET_CONNECTION_
TYPE.
name /foo/ A pathname and filename is Ensure that the file and Refer to your NDMP client
skoilksfoiefslk... greater than 1024 bytes, which pathnames in the backup documentation.
length 1102 too long exceeds Celerra’s limit. directory are less than 1024
bytes.
ndmp already started The NDMP client attempted to Verify that your backup Refer to EMC NAS
start an NDMP listen thread software is qualified with Interoperability Matrix on
while one was already running; Celerra. page 12.
starting another is
unnecessary.
NDMP Tape parameter not The NDMP ntape parameter Set the NDMP ntape Refer to Configuring Data
set. is not set in the param file. parameter in the param file, Movers for NDMP Backups
The ntape parameter and then reboot the Data on page 22.
specifies the number of tape Mover.
NDMP_TAPE_OPEN_REQUEST
denied. drives attached to a Data
Mover. Note: You must set this
parameter for both Data
Movers involved in a three-
way backup.
NDMP.bufsz > 1168K in The Data Mover’s buffer size To change the bufsz Refer to Configuring Data
param file, bufsz was parameter (bufsz) is too parameter value, edit the Movers for NDMP Backups
reset to 128K. large. param file, and then reboot the on page 22.
The bufsz value is Data Mover.
automatically reset to 128 KB,
the default value.

NetVault
NDMP_MOVER_STATE_ACTIV For NDMP V4, the state is Verify that your backup Refer to EMC NAS
E illegal for setting the window software is qualified with Interoperability Matrix on
size; only the LISTEN and Celerra and supports NDMP page 12. For more
PAUSED states are legal. Version 4. information on NDMP-
version compatibility refer to
Overriding the NDMP
Version on page 27.
network error Cannot send a message due Verify that the network is in a
(ndmp_mover.cxx: 2210) to a network error. good state.
next_head fail The file cannot be restored Verify that your backup Refer to your backup
(filename: line#) because a notification to the software is qualified with software vendor’s
NDMP client to read the file Celerra and that it supports documentation and to EMC
header failed for a direct DAR. NAS Interoperability Matrix
access restore (DAR). on page 12.
No password for NDMP The NDMP password is not set Use the server_user Refer to Assigning Data
user:ndmp on the Celerra Network Server. command to set the NDMP Movers a Username and
password or to verify that the Password on page 32.
password is set properly.
Retry:3 to get NDMP
user:ndmp - Passwd
Note: You must use the same
password for the Celerra Data
Mover and the NDMP client
software. Also, the username
must be ndmp.
open /.etc/BackupDates An open request failed on the No action is needed.

file failed, error: backup dates file, which stores This message could reflect a
<error message> the backup run level. problem with the root file
<error message> = type of system.
param PAX.<paramName> These two errors indicate that Configure an acceptable value Refer to Configuring Data
1024 out of range (4, the value for the PAX for the PAX parameter. Movers for NDMP Backups
512) parameter <paramName> is on page 22 and to Viewing
param PAX.<paramName> outside the parameter’s and Modifying Parameters
is set to 64 allowed range. on page 43 for parameter
descriptions and value
ranges.
Pattern Not Matched: / This pattern (file or directory) is Verify the integrity of the
fs/file3 (not restored) not found in the archive. backup media and the backup
path you entered.

NetVault
pax not started At the time of the Verify that your backup Refer to EMC NAS
DATA_CONNECT request, PAX software is qualified with Interoperability Matrix on
was not started. Celerra. page 12 for qualification
The Data Mover netd Verify that the netd file information.
configuration file needs to includes PAX.
include PAX. The netd file
resides in /nas/server/
slot_<x>/netd.
Where:
<x> = slot number of the Data
Mover, for example, slot_2
PAX.nFTSThreads is This message indicates that a No particular action is Refer to Configuring Data
reset to 64 value has been specified for necessary. The backup still Movers on page 21 for
the PAX.nFTSThreads succeeds; it simply uses fewer instructions on setting
parameter that is too large. threads to perform the backup. parameters.
The value is reset and the
backup continues normally.
pax_cmd_thread An internal error between Verify that your backup Refer to EMC NAS
expected ARCHIVE/ NDMP and PAX occurred. The software is qualified with Interoperability Matrix on
EXTRACT act, but Data Mover and NDMP client Celerra. page 12.
received <action> establish a connection, an
ARCHIVE or EXTRACT
message is expected, but not
others.
<action> = action received,
for example, LIST
pax_NotifyDataRead Notification to the NDMP client Verify that your backup Refer to your backup
failed (filename: to read the first file header for software is qualified with software vendor’s
line#) a three-way direct access Celerra and that it supports documentation and to EMC
restore (DAR) failed. three-way DAR. NAS Interoperability Matrix
on page 12.
Read fault on /fs/test The file you are trying to back Verify that the file or file Refer to EMC NAS
with error: <error up cannot be read on Celerra. system exists on Celerra, is in Interoperability Matrix on
message> a good state, and is not being page 12.
The attempt to read the file
data failed. used by other applications.
RecBuf in NDMP Pool Displays the number of buffers To change the buffer size, edit Refer to Configuring Data
(count:64), initiated in the pool and the the bufsz parameter in the Movers for NDMP Backups
NDMPMAXBUFSIZ is 128 maximum buffer size. param file, and then reboot the on page 22.
This setting reflects the bufsz Data Mover.
parameter.

NetVault
Request (0x702) not The request is not supported Verify that your backup Refer to EMC NAS
supported (No mover) because the mover interface is software is qualified with Interoperability Matrix on
not yet created. Celerra. page 12.
rw_thr() TCP connection PAX failed to receive a Verify that the network is in a
closed with mover message from the TCP good state.
connection.
Tape number > 8 in The ntape parameter Change the NDMP ntape Refer to Configuring Data
param file exceeds the maximum value, parameter value to 8 or less Movers for NDMP Backups
which is 8. and reboot the Data Mover. on page 22.
The value specifies the
number of tape drives attached
to a Data Mover. Celerra
supports no more than eight
tape drives per Data Mover.
TAPE_OPEN c1t2l0 fails A TAPE_OPEN request failed Verify that no contention for
with stat: <state> with <state>. the backup device exists
Many factors can trigger this among backup clients or Data
message. Movers.
<state> = state of the device, This may cause the backup to
for example, Device Busy fail.
thrdId 0 directory/ During a restore, the Celerra Verify that your backup Refer to EMC NAS
link error encountered a problem with software is qualified with Interoperability Matrix on
the directory and/or link. Celerra. You will need to page 12.
restart the restore. The
problem may be due to a failed
backup.
thrdId 0 error on An attempt was made to Ensure you are not trying to
restore file to root restore to the root file system, restore to root the file system.
filesystem which the Celerra does not
Permission denied to support.
restore <file or dir>
on Root fs
thrdId 0 The Data Mover encountered Verify that your backup Refer to EMC NAS
namedFileStreamSkip a problem and subsequently software is qualified with Interoperability Matrix on
error in 3214 skipped data for the named file Celerra. You may be trying to page 12.
stream. The restore is restore a failed backup.
terminated.
thrdId 0 positionTape A DAR restore encountered a Verify that your backup Refer to EMC NAS
error problem positioning the tape. software is qualified with Interoperability Matrix on
Celerra. The problem may be page 12.
due to a failed backup or a
corrupted tape.

NetVault
thrdId 1 mod_name error The Celerra could not rename Verify that your backup Refer to EMC NAS
a file during a restore. software is qualified with Interoperability Matrix on
Celerra. The problem may be page 12.
due to a failed backup.
Try to Stop data The backup client should not Verify that your backup Refer to EMC NAS
interface in state 3 stop the data interface in this software is qualified with Interoperability Matrix on
state. Celerra. page 12.
Try to tape_mtio in The NDMP client tried to The NDMP client should not Refer to your NDMP client’s
mover active state manipulate the tape drive while try to manipulate the tape drive documentation for more
the Data Mover had ownership while the Data Mover has information.
of the tape drive. ownership of it.
Unable to get position An error occurred while Verify that the tape is in a good
on tape (d),error: reading the tape position. The state.
<error message> tape is either not opened or is
not ready.
error, for example, Device
Error
Unable to reach The ndmp password is not set. Set a password for the ndmp Refer to Assigning Data
password data base user. Movers a Username and
Password on page 32.
Unknown Auth type (0x8) An unknown authorization Verify that the NDMP client Refer to Assigning Data
request was made. uses either text or the MD5 Movers a Username and
Celerra supports text and MD5 authorization format. Password on page 32 and to
authorizations. your backup software
documentation.
Unknown BT_NDMP_BUTYPE An invalid backup type is Verify that the tar or dump Refer to your backup
specified in the NDMP client backup type is specified in the vendor’s documentation for
software. NDMP client software. information on setting the
Celerra supports tar and backup type to tar or dump.
dump backup types.
Note: The backup will fail
without a valid backup type
specified.

NetVault
unknown mt cmd 0x97 An unknown tape command If using server_archive, For more information on the
was received. When using verify that you entered the server_mt command, refer
server_archive, an server_mt command to the Celerra Network
incorrect mt command was correctly. Server Command Reference
entered. Otherwise, verify that your Manual, to the man pages,
backup software vendor is and to the Using the Celerra
qualified with Celerra. server_archive Utility
technical module.
Refer to EMC NAS
Interoperability Matrix on
page 12 for information on
Celerra qualifications.
Unknown procedure Celerra received an unknown Verify that the your backup Refer to EMC NAS
(8765) message from the NDMP software is qualified with Interoperability Matrix on
Unknown command 0x8888 client and terminated the Celerra. page 12.
NDMP backup job.
VLC_FS_STATUS_DEVICE_ The specified volume was not Check the spelling of the
NOT_FOUND found. volume name you specified.
VLC_FS_STATUS_DEVICE_ These two messages indicate Create a volume that is the

TOO_SMALL that the target volume where same size as the original file
VLC_FS_STATUS_DEVICE_ you want to restore the file system. Restore the file
TOO_LARGE system is not identical in size system to this volume.
to the original file system.
VLC_FS_STATUS_ERROR Celerra encountered an Verify that your backup Refer to EMC NAS
internal error. This condition software is qualified with Interoperability Matrix on
causes the backup or restore Celerra. page 12 to verify software
to fail. qualification. Refer to the
related PAX server log
messages for more
information on this server
log condition.
VLC_FS_STATUS_NOT_FOUND The specified Correct the pathname, and

<file_system> <file_system> was not then restart backup.
found.
VLC_FS_STATUS_NOT_RAWF The target <file_system> When restoring a volume-level Refer to the Using Celerra
S <file_system> specified for recovery is not a copy, the target file system Replicator technical module
raw file system. must be a raw file system for more information.
(rawfs).
VLC_FS_STATUS_NOT_READ For a volume-level copy, the Mount the file system you want Refer to the Using Celerra
_ONLY specified file system must be to copy as a read-only file Replicator technical module
mounted as a read-only file system. for more information.
system.

NetVault
VLC_FS_STATUS_NOT_READ These messages appear To perform a volume-level Refer to Setting

_ONLY together. They indicate that a copy, create a checkpoint, Environment Variables on
VLC_FS_STATUS_NOT_READ volume-level copy (VLC) ensure the environment page 34.
_ONLY backup failed because a variable VLC=y, and back up For more information on
read/write file system was the read-only file system using volume-level copies, refer to
VLC Open error
used. You must use a read- NDMP. the Using Celerra Replicator
only file system to perform a technical module.
volume-level copy.
VLC_FS_STATUS_NOT_UFS The specified You must back up a volume-

<file_system> <file_system> is not a uxfs level copy from a uxfs file
type file system. A volume- system. A volume-level restore
level copy requires that you from tape must be to a raw file
use an uxfs file system. This system.
file-system type is the default
for Celerra.
VLC_FS_STATUS_READ_ These two messages indicate Refer to the related PAX

FAILED that a read or write to the file server log messages for more
VLC_FS_STATUS_WRITE_ system failed. information about this error
FAILED condition.
Write count exceeds Tape write or read exceeds the To change the bufsz Refer to Configuring Data
bufsz bufsz (buffer size) parameter. parameter, edit the param file Movers on page 21.
If the bufsz value is larger and reboot the Data Mover.
Read count exceeds than 1168 KB, the value is
bufsz automatically reset to 128 KB.
Write IO error status A write I/O error occurred. Verify that the tape drive is in a
error: <error message> <error message> = type of good state.
error, for example,
DeviceError

NetVault
Related Information
For more information related to the features and functionality described in this
technical module, refer to:
◆ Celerra Network Server Concepts Guide
◆ Celerra Network Server Command Reference Manual and man pages
◆ Using the Celerra server_archive Utility technical module
Foe general information on other EMC products publications, refer to the Celerra
Network Server User Information CD, which is supplied with our Celerra Network
Server and also available at Powerlink at http://powerlink.emc.com.
Also refer to the following documents for your backup software:
◆ NetVault Implementation Guide for the NDMP APM
◆ NetVault Application Plugin User’s Guide
◆ NetVault 7.0 Administrator’s Guide
Want to Know More?

EMC Customer Education Courses are designed to help you learn how EMC
storage products work together and integrate within your environment in order to
maximize your entire infrastructure investment. EMC Customer Education features
online, and hands-on training in state-of-the-art labs conveniently located
throughout the world. EMC customer training courses are developed and delivered
by EMC experts. For course information and registration, refer to EMC Powerlink,
our customer and partner website on http://powerlink.emc.com.

NetVault
direct access restore 10
Index discovering devices from Celerra 30
dynamic drive sharing
defined 2
A overview of 11
attributes, backup for Windows NT 34 restrictions for 4
B E
backup levels, with Celerra 35 education, on EMC products 74
backup software environment variables 34
configuration guidelines 37
configuring for Celerra 37 F
facility, PAX parameters 44
C failover of a Data Mover, caution 5
cabling the TLU 13 Fibre Channel TLU configuration 13
Celerra Network Server file restoration, overview 10
backup levels with 35
configuration guidelines for 20 G
setting environment variables on 34 guidelines for configuring
Celerra NS series backup software 37
media interface adapter for 20 Celerra Network Server 20
parameters for, summary 22
port configuration with 4
setting parameters on 24 I
checklist for troubleshooting NDMP backups international character sets
59 support overview 14
command syntax summary 56 with dump and tar backup types 15
commands interoperability matrix, accessing 12
server_cpu, summary 56
server_devconfig, summary 56 L
server_log, summary 57
levels of backup, with Celerra 35
server_param, summary 58
server_pax, summary 58
server_user, summary 57 M
configuration guidelines managing NDMP backups 43
for Celerra 20 MD5 password encryption, method for Celerra
for your backup software 37 33
configurations for NDMP backups media interface adapter, for the Celerra NS
dual-TLU 8 series 20
simple 6 modifying parameters 48
single TLU 7 multithreaded backup design 16
configuring
Data Movers 21
roadmap for 19
N
NASA thread group 16, 54
your backup software 37
NASS thread group 16, 54
connecting the robot to a Data Mover 13
NASW thread group 16, 54
customer education on EMC products 74
NDMP
Customer Support, reporting a problem to 60
backups, managing 43
concepts 6
D configurations 6
DAR, see direct access restore version, overriding 27
Data Movers Network Data Management Protocol, see
caution for connecting tape drives 5 NDMP
configuring 21 NIS, setting a Data Mover’s username and
failover caution 5 password with 32
parameters for 21 NS series, see Celerra NS series
setting a username and password for 32
devices, discovering from Celerra 30

NetVault
O third-party software
overriding the NDMP version 27 configuration guidelines 37
configuring for Celerra 37
thread groups 16, 54
P three-way backups
parameters heterogeneous 10
adding and editing 23 overview 9
configuring 21 restrictions with 4
file format 21 TLU
for international character sets 25 cabling 13
modifying 48 SCSI port, sample 31
nontunable 51 setting up 29
tunable 49 TLU configurations
viewing information on 44 dual TLU 8
password, setting on a Data Mover 32 Fibre Channel 13
PAX facility, parameters 44 simple NDMP 6
performance enhancements 16 single TLU 7
troubleshooting checklist 59
R
recovery, overview 10 U
related information, for Celerra and backup username, setting on a Data Mover 32
software 74
reporting a problem to Customer Support 60
restoration of files, overview 10 V
restrictions, general 4 viewing backup parameters 44
roadmap for configuring NDMP backups 19 viewing backup statistics 52
robotics, connecting to a Data Mover 13
W
S Windows NT attributes, backing up 34
SCSI TLU cabling configuration 13
server log messages
component parts of 60
for NDMP and PAX 62
reading 60
severity levels for 61
server_cpu command, summary 56
server_devconfig command, summary 56
server_log command, summary 57
server_param command, summary 58
server_pax command, summary 58
server_user command, summary 57
setting
a Data Mover’s username and password
32
environment variables on Celerra 34
parameters on Celerra 22
statistics, viewing 52
stripe size restriction, on an EMC storage
system 4
system requirements, for NDMP backups 12
T
tar backups
behavior with Celerra 15
terminology
definitions of 2
differences with backup software vendors
3

NetVault
Notes

NetVault
About This Technical Module
As part of its effort to continuously improve and enhance the performance and capabilities of the Celerra Network Server product line, EMC
from time to time releases new revisions of Celerra hardware and software. Therefore, some functions described in this document may not be
supported by all revisions of Celerra software or hardware presently in use. For the most up-to-date information on product features, see your
product release notes. If your Celerra system does not offer a function described in this document, please contact your EMC representative for
a hardware upgrade or software update.
Comments and Suggestions About the Documentation
Your suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a
message to celerradoc_comments@emc.com with your opinions of this document.
Copyright © 1998–2004 EMC® Corporation. All rights reserved.

EMC believes the information in this publication is accurate as of its publication date. The information is subject to change without notice.
THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS.” EMC CORPORATION MAKES NO REPRESENTATIONS OR
WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION, AND SPECIFICALLY DISCLAIMS IMPLIED
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Use, copying, and distribution of any EMC software described in this publication requires an applicable software license.
78 of 78 Version 5.3

NDMP Backups With Celerra

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

NDMP Backups With Celerra

Hochgeladen von

Copyright:

Verfügbare Formate

Configuring NDMP Backups with Celerra

and BakBone NetVault

2 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

EMC Term Equivalent Third-Party Terms

TLU robot Robotic arm, arm changer

NDMP-Host Data Mover Celerra filer, NAS filer, application server

Configuring NDMP Backups with Celerra and BakBone Version 5.3 3 of 78

EMC Term Equivalent Third-Party Terms

Celerra Network Server Client computer, Celerra filer

4 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

Important: If you change your network zoning configuration, where relevant:

Configuring NDMP Backups with Celerra and BakBone Version 5.3 5 of 78

6 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

Storage Tape Library

Figure 1 Simple NDMP Backup

Single TLU Configuration

Configuring NDMP Backups with Celerra and BakBone Version 5.3 7 of 78

NDMP Client with

Backup Backup Data and

PS0 PS1 PS2 PS3 PS4 SMB0 SMB1

Storage Tape Library

Figure 2 Single-TLU NDMP Backup

8 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

NDMP Connection NDMP Connection

Robotic Control Robotic Control

Tape Library Tape Library

Figure 3 Dual-TLU NDMP Backup

Three-Way Backup Configuration

Configuring NDMP Backups with Celerra and BakBone Version 5.3 9 of 78

Storage Celerra Celerra Tape Library

Backup Data Only Robotic

Network Boundary CNS-000351

Figure 4 Three-Way NDMP Backup

Restoring File Systems

10 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

Figure 5 Dynamic Drive Sharing

Configuring NDMP Backups with Celerra and BakBone Version 5.3 11 of 78

Note: The Celerra Network Server supports NDMP Version 4.0.

Table 2 System Requirements for NDMP Backups

Celerra Network Server Version 5.3.

Hardware Celerra Network Server.

Network Dedicated network (optional).

Storage Compatible tape device or tape library unit.

EMC NAS Interoperability Matrix

12 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

Data Mover-to-TLU Cabling Examples

Tape Library Unit

PS0 PS1 PS2 PS3 PS4 SMB0 SMB1

Figure 6 Sample SCSI Cabling Configuration

Configuring NDMP Backups with Celerra and BakBone Version 5.3 13 of 78

Figure 7 Sample Fibre Channel Configuration

Implementing International Character Support with NDMP

14 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

Vendor Does Not Support International Characters

Configuring NDMP Backups with Celerra and BakBone Version 5.3 15 of 78

NASA • Sends metadata to the NDMP backup software

NASS • Traverses the file system

NASW • Gets data from the data buffer pool

16 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone

Stat Buffer Data Buffer

PS0 PS1 PS2 PS3 PS4 SMB0 SMB1

Figure 8 Multithreaded Backup and Restore

Configuring NDMP Backups with Celerra and BakBone Version 5.3 17 of 78