NDMP_Backups_with_Celerra

Configuring NDMP Backups with Celerra

and BakBone NetVault

P/N 300-001-623 Rev A01

Version 5.3

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

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.

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.

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

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.

Celerra Network Server Client computer, Celerra filer Table 1 Terminology Differences (Continued)

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.

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.

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.

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.

Network Boundary NDMP Control Data Backup Data NDMP Client with Backup Software Tape Library Backup Device Storage System NDMP-Host Data Mover Celerra Robotic Control CNS-000349 PS0PS1PS2PS3PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15

Note: Your backup software and TLU manufacturer determine which configuration options are available to you.

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

Backup Host Storage System Network Boundary Celerra NDMP-Host Data Mover NDMP-Host Data Mover Backup Data Backup Data NDMP Control Data NDMP Control Data NDMP Client with Backup Software Tape Library Backup Device

Backup Data and Robotic Control CNS-000348 PS0PS1PS2PS3PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15

and launches the backup. The Data Mover processes the data and sends it to the

tape device.

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

Network Boundary Celerra NDMP-Host Data Mover NDMP-Host Data Mover NDMP Connection NDMP Connection NDMP Client with Backup Software Tape Library Backup Device Storage Systems Backup Data Robotic Control Tape Library Backup Device Backup Data Robotic Control CNS-000350 PS0PS1PS2PS3PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15 PS0 PS1 PS2 PS3 PS4 SMB0SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15

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.

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.

Tape Library Backup Device Storage System NDMP Client with Backup Software Network Boundary NDMP-Host Data Server NDMP-Host Tape Server Celerra Celerra Backup Data Backup Data Backup Data Only

NDMP Control Data NDMP Control Data Robotic Control CNS-000351 PS0PS1PS2PS3PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15

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.

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

NDMP Client with Backup Software NDMP-Host Data Mover Celerra NDMP-Host Data Mover Celerra Network Boundary SAN CNS-000356 Tape Drive

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.

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.

Software Celerra Network Server Version 5.3.

NDMP- and Celerra-compatible backup software running on the NDMP client.

Hardware Celerra Network Server.

Network Dedicated network (optional).

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.

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

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

Tape Library Unit

Storage System Celerra CNS-000353 PS0PS1 PS2PS3 PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15

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.

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.

PS0 PS1 PS2PS3 PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB8 SB10 SB12 SB13 SB14 SB15 Storage System Celerra Bridge Switch Switch SCSI FC FC FC FC FC FC FC FC CNS-000352 DM 1 DM 2 Tape Library Backup Device Tape Library Backup Device PS0PS1 PS2 PS3PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15

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.

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

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.

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

Storage System Network Boundary Celerra Client with NDMP-compliant backup software Tape Library Unit CNS-000441 PS0PS1PS2PS3PS4SMB0 SMB1 SB0 SB1 SB2 SB3 SB4 SB5 SB6 SB7 SB8 SB9 SB10 SB11 SB12 SB13 SB14 SB15 Backup and Restore Threads Data Mover NASA NASW NASS Stat Buffer Pool Data Buffer Pool FTS Threads

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.

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

Managing NDMP Backups on

Celerra

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 NDMP Backups on

Celerra

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.

Configuring Data Movers

This section includes the following procedures.

For a summary of parameter file formats, refer to

Parameter File Format

, which

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

the parameters, and if found, modify one and remove any duplicates. However, if

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

server file,

/nas/server/slot_<x>/param

, overwrite the values in the system

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.

Configuring Data Movers

Setting Up the TLU

Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software Action Procedure

Define parameters for NDMP-Host Data Movers.

Note: This procedure is required for NS series Celerra Network Servers.

Configuring Data Movers for NDMP Backups on page 22

Configure parameters for Internationalization. Configuring Data Movers for International Character Sets on page 25

Override the NDMP version used by the Celerra Network Server.

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

performance-related parameters, refer to

Managing NDMP Backups on Celerra on

page 43

. For more information on other Celerra Network Server parameters, refer

to the Celerra Network Server Parameters Guide.

Note: Configuring the

enable_fabric_aux0

linx_speed_aux0

required for NS series Celerra Network Servers. Configuring Data

Movers

Setting Up the TLU

Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software

Table 4 Summary of Required Parameters

Module Parameter Value Comment/Description

NDMP bufsz buffer size in

kilobytes default=128

Specifies the size of the buffer allocated for reading and writing on the tape. The NDMP client determines this value through the TAPE_READ/TAPE_WRITE request. Example:

param NDMP bufsz=256

fcTach enable_fa bric_aux0

0 (default) or 1 _{Note: This parameter applies only to the NS} series Celerra Network Servers.

param fcTach enable_fabric_aux0=0 on a Celerra NS-Series system, configures the tape backup port for an FC-AL environment. param fcTach enable_fabric_aux0=1 on a Celerra NS-Series system, configures the tape backup port for a Fibre Channel switched fabric environment.

fcTach linx_spee d_aux0

0x4000 (default) or

0x2000 Note: This parameter applies only to the NS _{series Celerra Network Servers.}

param fcTach linx_speed_aux0=0x4000 sets the tape backup link speed to

accommodate an LC optical 1 Gb interface. param fcTach linx_speed_aux0=0x2000 sets the tape backup link speed to

!

!

CAUTION

!

!

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.

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:

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:

param NDMP bufsz=256

param fcTach enable_fabric_aux0=1 param fcTach linx_speed_aux0=0x4000

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. Step Action

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

Network Server Parameters Guide.

This section explains how to specify a dialect in the Celerra Network Server. You

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. Configuring Data

Movers

Setting Up the TLU

Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software

Table 5 dialect and convDialect Parameters

Module Parameter Value Comment/Description

NDMP convDialect dialect string default=8859-1

You must set the conversion dialect when you restore an ASCII-mode Data Mover image to a Data Mover that has Internationalization turned on. This applies only when the conversion dialect you want to use is a non-Latin1 dialect, such as big5.

Example:

param NDMP convDialect=big5

NDMP dialect dialect string default=“ ” (UTF-8)

Sets the dialect on the Data Mover to match the dialect of the Data Mover clients. This applies when Celerra operates in Internationalization mode.

Note: The default value (null) means that UTF-8 is used.

Example:

!

!

CAUTION

!

!

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.

Use this procedure to set the dialect.

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.

Step Action

1. Open the file /nas/server/slot_<x>/param with a text editor. 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: $ server_cpu <movername> -reboot -monitor now

Where:

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

Parameters Guide

.

!

!

CAUTION

!

!

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.

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

this default setting. However, you can override the automatic NDMP-version

selection by specifying the latest NDMP version that can be used.

Overriding the NDMP version can be a useful troubleshooting tool, for example, to

isolate NDMP issues by determining whether they occur with different versions.

Use this procedure to override the NDMP version.

Configuring Data Movers

Setting Up the TLU

Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software

Table 6 maxProtocolVersion Parameter

Module Parameter Value Comment/Description

NDMP maxProtoc olVersion

1–4 default=4

Sets the maximum NDMP version that can be used. Autonegotiation between Celerra and the NDMP client determines the highest NDMP version used. This parameter setting overrides the autonegotiation.

Example:

param NDMP maxProtocolVersion=3

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

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

4. Close and save the files.

5. After setting all parameters, reboot the Data Mover. Use this command syntax: $ server_cpu <movername> -reboot -monitor now

Where:

<movername> = name of the specified Data Mover Example:

To reboot server_2, type:

$ server_cpu server_2 -reboot -monitor now

Setting Up the TLU

This section includes the steps for retrieving and recording device names, which

you need when configuring your backup software.

Recording TLU Information

The Celerra Network Server addresses a TLU device component as follows:

<SCSI_controller> <SCSI_ID> <SCSI_LUN>

Where:

<SCSI_controller>

= chain number of the controller

<SCSI_ID>

= SCSI ID (target) of the controller

<SCSI_LUN>

= logical unit number (LUN) of the controller

Note: For backups with a NS-Series Celerra Network Server, a media interface adapter (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 documented in individual setup instructions provided with each system.

Use this procedure to connect the Data Movers to the TLU via SCSI, and to record

device names.

Setting Up the TLU

Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software Configuring Data Movers Step Action

1. From the Control Station, halt each Data Mover to be connected to the TLU and confirm that it has been halted. Use this command syntax:

$ server_cpu <movername> -halt -monitor now Where:

<movername> = name of the specified Data Mover 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:

$ server_cpu <movername> -reboot -monitor now Where:

<movername> = name of the specified Data Mover Example:

To restart server_2, type:

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:

<movername> = name of the specified Data Mover

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:

<movername> = name of the specified Data Mover 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. Step Action

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

Data Mover TLU SCSI Port _{Device Name}Resulting Device Component

server_x chain 1, target 0, LUN 0 C1T0L0 Robot

server_y chain 1, target 4, LUN 0 C1T4L0 Tape Drive 1

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.

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 Variables on page 34.

With NIS

For Network Information Service (NIS) installations, the username and password

must match the username and password in the NIS database. If you are using NIS,

enter the following into the NIS database:

◆

ndmp

as the user ID

◆

Same password to be entered when you configure 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 System with NDMP

Managing NDMP Backups on Celerra Setting Up the TLU

Setting Environment Variables Configuring Your Backup Software Configuring Data Movers Assigning Data Movers a Username and Password Step Action

1. To assign a user account name and password to one or more Data Movers, log in to the Celerra Network Server Control Station as nasadmin and switch user to root by typing: $su

Note: The su- command will fail. You must use the su command.

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:

<movername> = name of the specified Data Mover

<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 -passwordndmp

To use the MD5 password encryption method, from nas/sbin/, type: # server_user ALL -add -md5 -password ndmp

Setting Environment Variables

Table 8

shows environment variables supported by the Celerra Network Server.

Check your backup vendor’s documentation for more information about

environment variable requirements, as backup vendors use and implement

variables differently.

Note: If you are backing up NT attributes, be sure that HIST=y and OPTIONS=NT.

Backing Up a VDM File System with NDMP

Managing NDMP Backups on Celerra Setting Up the TLU

Assigning Data Movers a Username and Password Configuring Your Backup Software Configuring Data Movers Setting Environment Variables

Table 8 Environment Variables

Variable _ValuesPossible _ValueDefault Description

BASE_DATE Obtained from the NDMP data server for the previous backup operation or set to 0 (zero) for a full backup.

N/A Incremental count and date/time of previous backup operation.

Note: This variable works in conjunction with DUMP_DATE.

When BASE_DATE is specified, LEVEL is ignored. For more information, refer to

Backup Levels with Celerra and NDMP on page 35.

DIRECT y/n n This value (along with the HIST variable) must be set to y before you perform a backup if you want to use DAR when recovering files.

DUMP_DATE Obtained from the NDMP data server for the current backup operation only if BASE_DATE is specified by the backup client as part of the environment.

N/A Incremental count and date/time of current backup operation.

Note: This variable works in conjunction with BASE_DATE.

For more information, refer to Backup Levels with Celerra and NDMP on page 35.

EMC_OFFLINE DATA

y/n n By default, the Celerra backs up only offline 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.

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.

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 LK AT MI/MD/MM NT for tar and dump

Saves NT attributes. Follows symbolic links.

Preserves access time in archive mode. 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.

Table 8 Environment Variables (Continued)

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.

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

Server. Refer to your backup software vendor’s documentation for more

information. A list of documents appears in

Related Information on page 74

.

Guidelines

The following guidelines apply to your backup software configuration:

◆

You must configure Data Mover access from your backup software before you

can carry out any operations. You enable access to the NDMP-Host Data Mover

by entering a trusted user account name and password in your backup software

that match those assigned to each NDMP-Host Data Mover.

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.

◆

When configuring stand-alone tape drives in your backup software, EMC

recommends prefixing the Celerra Network Server device name with

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

◆

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

Related Information on page 74

.

Backing Up a VDM File System with NDMP

Managing NDMP Backups on Celerra Setting Up the TLU

Assigning Data Movers a Username and Password Configuring Data Movers Configuring Your Backup Software Setting Environment Variables

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

must know the cabling configurations between the NDMP-Host Data Movers and

the tape drives. You perform these steps at the backup host.

Note: For drive index information, refer to the TLU manufacturer’s documentation.

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

on NetVault Version 7.0, which was qualified with the Celerra Network Server. To

access the most up-to-date patch and qualification information, refer to

EMC NAS

Interoperability Matrix on page 12

.

Task 1: Add an NDMP Server

Use this procedure to add an NDMP Server.

Backing Up a VDM File System with NDMP

Managing NDMP Backups on Celerra Setting Up the TLU

Assigning Data Movers a Username and Password Configuring Data Movers Configuring Your Backup Software Setting Environment Variables 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.

2. If you are running NDMP APM Version 5.4 or higher, skip to step 3.

If you are running NDMP APM Version 5.3, you must install the following files on your NDMP client:

• The NDMP configuration file ndmpversions.cfg • 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.

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. Step Action