NDMP_Backups_with_Celerra

1 of 78

Configuring NDMP Backups with Celerraand BakBone NetVault

P/N 300-001-623Rev A01

Version 5.3 August 2004

ContentsIntroduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2

Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5

NDMP Backup Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6NDMP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Restoring File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10Dynamic Drive Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12EMC NAS Interoperability Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

Planning Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13Data Mover-to-TLU Cabling Examples . . . . . . . . . . . . . . . . . . . . . . . .13Implementing International Character Support with NDMP . . . . . . .14Multithreaded Backup and Restore Design . . . . . . . . . . . . . . . . . . . .16

User Interface Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18Configuring NDMP Backups with Celerra and BakBone NetVault Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Configuring Data Movers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Setting Up the TLU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Assigning Data Movers a Username and Password . . . . . . . . . . . . . . . .32Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Configuring Your Backup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37

Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

Backing Up a VDM File System with NDMP . . . . . . . . . . . . . . . . . . . . . . .42Managing NDMP Backups on Celerra . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

Viewing and Modifying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .43Viewing Backup Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52

Command Syntax Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56Troubleshooting NDMP Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59

Troubleshooting Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74

Want to Know More? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75

Configuring NDMP Backups with Celerra and BakBoneNetVault

2 of 78 Version 5.3

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

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

3 of 78Version 5.3Configuring 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 DifferencesThe 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


4 of 78 Version 5.3

RestrictionsWhen 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)

EMC Term Equivalent Third-Party Terms


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


6 of 78 Version 5.3

NDMP Backup ConceptsThe 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 ConfigurationsThe 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 ConfigurationThe 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 ConfigurationFigure 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

NDMPControl Data

BackupData

NDMP Clientwith Backup

Software

Tape LibraryBackup Device

StorageSystem

NDMP-Host Data Mover

Celerra

RoboticControl

CNS-000349

PS0 PS1 PS2 PS3 PS4 SMB0 SMB1

SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15


8 of 78 Version 5.3

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

Figure 2 Single-TLU NDMP Backup

Dual-TLU ConfigurationFigure 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

StorageSystem

Network Boundary

Celerra

NDMP-HostData Mover

NDMP-HostData Mover

BackupData

BackupData

NDMP Control DataNDMP Control Data

NDMP Client with Backup Software


Backup Data andRobotic Control

CNS-000348


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15


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 ConfigurationSome 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)

Network Boundary

Celerra

NDMP-HostData Mover

NDMP-HostData Mover

NDMP ConnectionNDMP Connection


Software

Tape LibraryBackup DeviceStorage Systems

BackupData

Robotic Control


BackupData

Robotic Control

CNS-000350


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

PS0PS1PS2PS3PS4SMB0SMB1

SB0

SB1

SB2

SB3

SB4

SB5

SB6

SB7

SB8

SB9

SB10

SB11

SB12

SB13

SB14

SB15


10 of 78 Version 5.3

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


StorageSystem


Software

Network Boundary

NDMP-HostData Server

NDMP-HostTape Server

Celerra Celerra

BackupData

BackupData

Backup Data Only

NDMP ControlData

NDMP ControlData

RoboticControl

CNS-000351


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15


Dynamic Drive SharingSeveral 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


Software

NDMP-HostData Mover

Celerra

NDMP-HostData Mover

Celerra

NetworkBoundary

SAN

CNS-000356

Tape Drive



System RequirementsThis 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 MatrixRefer 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.

Table 2 System Requirements for NDMP Backups

SoftwareCelerra Network Server Version 5.3.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.

https://powerlink.emc.com


Planning ConsiderationsThis 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 ExamplesThis 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 ConfigurationIn 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 ConnectivityIf 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 ConfigurationFigure 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.


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

Tape Library Unit

StorageSystemCelerra

CNS-000353


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15



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


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6S

B8

SB

10S

B12

SB

13

SB

14

SB

15

StorageSystem

Celerra

Bridge

Switch Switch

SCSI

FC

FC

FCFC

FC

FC

FC

FC

CNS-000352

DM 1

DM 2




SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15


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 SetsData 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 DesignThe 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


Multithreaded Backup ProcessWhen 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 ProcessThe 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.

StorageSystem

Network Boundary

Celerra

Client withNDMP-compliantbackup software

Tape LibraryUnit

CNS-000441


SB

0

SB

1

SB

2

SB

3

SB

4

SB

5

SB

6

SB

7

SB

8

SB

9

SB

10

SB

11

SB

12

SB

13

SB

14

SB

15

Backup andRestoreThreads

Data Mover

NASA

NASWNASS

Stat BufferPool

Data BufferPool

FTS Threads



User Interface ChoicesThe 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 RoadmapThis 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




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 MoversThis section includes the following procedures.

For a summary of parameter file formats, refer to Parameter File Format, which follows.

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


Setting Up the TLU



Assigning Data Movers a Username

and Password



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.

Overriding the NDMP Version on page 27



Parameter File FormatParameters 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 BackupsTable 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, and linx_speed_aux0 parameters is required for NS series Celerra Network Servers.


Setting Up the TLU




and Password



Table 4 Summary of Required Parameters

Module Parameter Value Comment/Description

NDMP bufsz buffer size in kilobytesdefault=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_fabric_aux0

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

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

fcTach linx_speed_aux0

0x4000 (default) or 0x2000

Note: This parameter applies only to the NS series Celerra Network Servers.

param fcTach linx_speed_aux0=0x4000sets the tape backup link speed to accommodate an LC optical 1 Gb interface.param fcTach linx_speed_aux0=0x2000sets the tape backup link speed to accommodate a 2 Gb FC-AL interface.


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

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:param NDMP bufsz=256



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=256param fcTach enable_fabric_aux0=1param 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 SetsTable 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.


Setting Up the TLU




and Password



Table 5 dialect and convDialect Parameters


NDMP convDialect dialect stringdefault=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 stringdefault=� �(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:param NDMP dialect=big5





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 MoverExample:/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:<movername> = the name of the Data Mover controlled by the slot_<x>/param file.


Overriding the NDMP VersionTable 6 shows the NDMP maxProtocolVersion parameter and its values. For more information on other Celerra parameters, refer to Celerra Network Server Parameters Guide.



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.


Setting Up the TLU




and Password



Table 6 maxProtocolVersion Parameter


NDMP maxProtocolVersion

1�4default=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

Note: If the line appears and indicates a different NDMP version, edit the line and add the NDMP version you want to specify.



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

Step Action


Setting Up the TLUThis section includes the steps for retrieving and recording device names, which you need when configuring your backup software.

Recording TLU InformationThe 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




and Password




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 MoverExample: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 MoverExample: To restart server_2, type:$ server_cpu server_2 -reboot -monitor now

The output is similar to the following:server_2: reboot in progress 0.0.3.4 done



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 MoverFor 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 MoverFor 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 tablename addr type infojbox1 c1t0l0 jbox ATL P1000 62200501.21tape2 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 Resulting Device Name Device Component

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



Assigning Data Movers a Username and PasswordNDMP configuration for your backup software and Celerra Network Server requires that you set a trusted username and password for each NDMP-Host Data Mover.

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

With NISFor 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 NISIf you do not have NIS, use this procedure to assign a user account name and password to the NDMP-Host Data Movers.



Setting Up the TLU





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.

2. Type the root password when prompted.


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 maximumOutput:Creating new user ndmpUser ID: mandatory fieldGroup ID: mandatory fieldComment: optional fieldHome directory: optional fieldShell: optional fieldChanging password for user ndmpNew 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 maximumExample:# server_user ALL -add -password ndmpTo use the MD5 password encryption method, from nas/sbin/, type: # server_user ALL -add -md5 -password ndmp

Step Action



Setting Environment VariablesTable 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.



Setting Up the TLU


and Password



Setting Environment

Variables

Table 8 Environment Variables

Variable Possible Values

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

FILESYSTEM <pathname> N/A The device or file system to be backed up.


Backup Levels with Celerra and NDMPA 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

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 NTLKATMI/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)

Variable Possible Values

Default Value Description



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

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

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



Setting Up the TLU


and Password






Configuration StepsThe 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 ServerUse this procedure to add an NDMP Server.



Setting Up the TLU


and Password




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


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



Task 2: Using the Automatic Device ConfigurationNetVault 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 recognize and configure a device through the NetVault wizard.

Note: To manually recognize and configure devices, refer to your BakBone NetVault documentation.

Use this procedure to recognize and configure a device through the NetVault wizard.



Setting Up the TLU


and Password




Step Action

1. Recognize a device. Launch NetVault and click the Device Management button (or select Device Management from the Administration menu. NetVault automatically scans the SCSI bus on all NetVault clients and the server.

2. NetVault searches for a library with serialization capability. If it finds one, a Device 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.

5. To set default performance options, select the Configure Performance Options 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, select the Scan clients for remote/shared drives checkbox. This launches another 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.


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.

Step Action



Backing Up a VDM File System with NDMPA Virtual Data Mover (VDM) is a Celerra Network Server software feature that enables you to administratively separate CIFS servers and their associated resources, like file systems, into virtual containers. These virtual containers allow 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 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 system, you must specify the full mount path of the file system. To retrieve the full path, use the server_mount command.



Setting Up the TLU


and Password




Step Action

1. To retrieve the full mount path of a file system, use this command syntax: $ server_mount <movername> | grep <fs_name>

Where:<movername> = name of the Data Mover<fs_name> = name of the file system for which you want the full pathExample:$ server_mount server_2 | grep ufs1

Output:ufs1 on /root_vdm_1/ufs1 uxfs,perm,rw

Note: /root_vdm_1 in this example indicates that the file system is a VDM-configured file system. When using NDMP to back up this file system, you would enter in your backup 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.


Managing NDMP Backups on CelerraThis section describes how to view and dynamically modify NDMP backup parameters, and how to monitor backup performance statistics. It includes:

◆ Viewing and Modifying Parameters, which describes the commands you use to view details on and dynamically modify parameters that affect backup performance.

◆ Viewing Backup Statistics on page 52, which describes the commands you use to view detailed backup and restore performance statistics.

Viewing and Modifying ParametersYou can view and dynamically modify performance-related backup parameters using the server_param command or through Celerra Manager. This technical 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 Server Parameters Guide.

This section includes the following tasks.


Setting Up the TLU


and Password





Action Procedure

For a particular Data Mover, view the tunable backup parameters and their values.

Viewing Backup Parameters on page 44

View information on a specified parameter or view information on all tunable backup parameters for a specified Data Mover.

Viewing Parameter Information on page 45

Modify the value of a tunable backup parameter. Modifying Parameters on page 48



Viewing Backup ParametersUse this command to view tunable backup parameters and their values.


Setting Up the TLU


and Password





Action

To view parameters and their values, use this command syntax:$ server_param <movername> -facility <facility_name> -list

Where:<movername> = name of the specified Data Mover<facility_name> = name of the facility to which the parameter belongsExample:For example, to view a list of PAX parameters on server_2, type: $ server_param server_2 -facility PAX -list

Output

name facility default current configuredpaxWriteBuff PAX 64 128 30paxStatBuff PAX 128 128 nFTSThreads PAX 8 8 nThread PAX 64 16 nPrefetch PAX 8 8 nRestore PAX 16 16

Notes

Note: Parameter and facility names are case-sensitive.

Where:name = name of the parameter facility = facility to which the parameter belongsdefault = default value for the parametercurrent = value set on the Data Moverconfigured = 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.


Viewing Parameter InformationUse this procedure to view details on a specific parameter, including current, default, and possible values. Refer to Parameter Summary on page 49 for parameter descriptions.


Setting Up the TLU


and Password





Action

To view detailed information on a specific parameter, use the following command syntax:$ server_param <movername> -facility <facility_name> -info <param_name>

Where:<movername> = name of the specified Data Mover<facility_name> = name of the facility to which the parameter belongs<param_name> = name of the parameter you want to viewExample:For server_2, to view detailed information on the paxWriteBuff parameter, type:$ server_param server_2 -facility PAX -info paxWriteBuff

Output

name = paxWriteBufffacility_name = PAXdefault_value = 64current_value = 128configured_value = 128user_action = nonechange_effective = immediaterange = (1,2048)description = Number of buffers in tape write queue per

backup session

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 belongsdefault_value = value set as the defaultcurrent_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 effectchange_effective = when the parameter change takes effectrange = range of possible valuesdescription = refer to Parameter Summary on page 49 for parameter descriptions



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<facility_name> = name of the facility to which the parameter belongsExample:$ 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 = paxWriteBufffacility_name = PAXdefault_value = 64current_value = 64configured_value = 64user_action = nonechange_effective = immediaterange = (1,1024)description = Number of buffers in tape write queue per

backup session

name = paxStatBufffacility_name = PAXdefault_value = 128current_value = 128configured_value =user_action = nonechange_effective = immediaterange = (1,2048)description = Number of buffers in stat queue per backup

session

name = nRestorefacility_name = PAXdefault_value = 16current_value = 30configured_value = 30user_action = nonechange_effective = immediaterange = (1,64)description = Number of worker threads per restore session


Output

name = nFTSThreadsfacility_name = PAXdefault_value = 8current_value = 8configured_value = 8user_action = nonechange_effective = immediaterange = (1,256)description = Number of FTS threads per backup session

name = nThreadfacility_name = PAXdefault_value = 64current_value = 32configured_value = 32user_action = nonechange_effective = immediaterange = (1,128)description = Number of worker threads per backup session

name = nPrefetchfacility_name = PAXdefault_value = 8current_value = 8configured_value = 8user_action = nonechange_effective = immediaterange = (1,32)description = Number of tape records prefetched per worker

thread



Modifying ParametersThis section describes how to modify a parameter value. Refer to Parameter Summary on page 49 for parameter descriptions.

!! CAUTIONS

◆ Parameters allow you to increase the number of threads and data blocks used 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.

◆ Parameter changes made while backups are running on a Data Mover take effect only after all backups on the Data Mover have ceased.

Use this command to modify a parameter.


Setting Up the TLU


and Password





Action

To modify a parameter, use this command syntax:$ server_param <movername> -facility <facility_name> -modify <param_name> -value <new_value>

Where:<movername> = name of the specified Data Mover<facility_name> = name of the facility to which the parameter belongs<param_name> = name of the parameter<new_value> = value you want to set for the specified parameterExample: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.


Parameter SummaryTable 9 and Table 10 on page 51 describe performance-related parameters. Table 9 includes the parameters you can modify with the server_param command or through Celerra Manager. (Refer to the online help for information on 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 Server Parameters Guide.


Setting Up the TLU


and Password





Table 9 Tunable Parameters: Summary

Facility Parameter

Value Range

Comment/Description510 Data Movers & Higher

507 Data Movers & Lower

PAX nFTSThreads 1�256default=8

1�256default=8

Specifies the number of threads for a single backup job. More threads decrease the likelihood that the NASA thread will be a bottleneck.Example:param PAX nFTSThreads=128

PAX nPrefetch 1�32default=8

1�8default=8

Specifies the amount of data each backup thread prefetches from disk before finishing the file read and writing data to tape.The exact prefetch amount = 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�64default=16

1�32default=16

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



PAX nThread 1�128default=64

1�64default=64

Specifies the number of backup 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�2048default=128

1�2048default=128

Specifies the number of buffers 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�1024default=64

1�64default=64

Specifies the number of buffers 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

Table 9 Tunable Parameters: Summary (Continued)

Facility Parameter

Value Range

Comment/Description510 Data Movers & Higher

507 Data Movers & Lower


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�512default=64

Specifies the number of buffers between the 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.



Viewing Backup StatisticsThis 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 thread group, which performs various functions within the multithreaded backup and restore process. For more information, refer to Multithreaded Backup and Restore Design on page 16.

Use this command to view statistics on a backup session in progress.


Setting Up the TLU


and Password





Action

To view statistics on a backup session in progress, use this command syntax:$ server_pax <movername> -stats -verbose

Where:<movername> = name of the specified Data MoverExample:For example, to view statistics for a backup running on server_2, type:$ server_pax server_2 -stats -verbose


Output

************** SUMMARY PAX STATS ****************---- NASS STATS ----** nass thid 0 **Total file processed: 16throughput: 2 files/secTotal nass wait nasa count: 13Total nass wait nasa time: 236 msecTotal time since last reset: 8 secfts_build time: 0 secgetstatpool: 0 buffersputstatpool: 128 buffers

---- NASA STATS ----** nasa thid 0 (BACKUP) **Backup root directory: /s4fs1/admTotal bytes processed: 104937747Total file processed: 16throughput: 11 MB/secaverage file size: 6404KBTotal nasa wait nass count: 1Total nasa wait nass time: 13 msecTotal time since last reset: 8 secTape device name: /dev/c0t5l0 0 size file processed: 3 1 -- 8KB size file processed: 8 8KB+1 -- 16KB size file processed: 016KB+1 -- 32KB size file processed: 032KB+1 -- 64KB size file processed: 164KB+1 -- 1MB size file processed: 2 1MB+1 -- 32MB size file processed: 132MB+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/HourAverage Burst Transfer: 12 MB/Sec 42 GB/HourWrite 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/secGet Pool: 63 buffers Put Pool: 0 buffersCompression Page retrieved 00:00:08 (h:min:sec) ago:ReadC=2.1 WriteC=2.1 Read=310692 KB Written=408327 KB



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 fileTotal file processed = total number of files and/or directories for which metadata was processedTotal NASS wait NASA count = number of times NASS waited for NASATotal NASS wait NASA time = amount of time NASS waited for NASATotal time since last reset = time since the last reset; a reset occurs automatically after a backup completesfts_build time = time spent building the file system or directory treegetstatpool = if the value is consistently 0, then NASA may be slowing down the backupputstatpool = if the value is consistently 0, then NASS may be slowing down the backupNASA STATS = thread responsible for writing file header information, reading file data, and writing to the bufferBackup root directory = directory being backed upTotal bytes processed = bytes backed up since last reset or start of current backupTotal file processed = number of files backed up since start or reset of current backupThroughput = how fast NASA processed data Average file size = average size of file for current backupTotal nasa wait nass count time = number of times NASA waited for NASSTotal nasa wait nass time = amount of time NASA waited for NASSTotal time since last reset = amount of time since the backup statistics were reset; a reset occurs automatically after a backup completesTape device name = target device for the backup dataFile size statistics = statistics on the size of files backed up since the start or reset of the current backupNASW STATS = thread responsible for getting data from the buffer pool, writing it to tape, or sending it to a remote Data MoverSession total time = total time of current sessionSession idle time = idle time for current sessionKB transferred = total KB transferredAverage 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/sWrite 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-timeRate= transfer rate in MB/s Burst= burst transfer rate in MB/sIdle= 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 backupPut pool = number of buffers in put pool; if value is consistently 0, then the tape may be slowing down the backupCompression rate retrieved = compression rateReadC = read compression rate at the tape device WriteC = write compression rate at the tape deviceRead = amount of data read in KB Written = amount of data written in KB


Resetting Backup StatisticsYou 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 reset when a backup completes.

Use this command to reset the statistics for a backup session in progress.


Setting Up the TLU


and Password





Action

To reset statistics for a backup session, use this command syntax: $ server_pax <movername> -reset

Where:<movername> = name of the specified Data MoverExample:For example, to reset the statistics for a backup running on server_2, type:$ server_pax server_2 -reset

Output

server_2 : done



Command Syntax SummaryThis section summarizes the syntax for commands used in this technical module.

For a more detailed synopsis of the command or to view syntax conventions, refer to the Celerra Network Server Command Reference Manual.

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

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> | ALL}

Queries, saves, and displays the device configuration connected to the specified Data Mover(s).

Option Description

-create Queries for devices and saves them into the device table database.


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

Option Description



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 <param_name> -value <new_value>

Allows you to modify the value of the specified <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.


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

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

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.




❑ 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 ProblemRefer 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 MessagesThis 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 MessagesEach 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


Table 18 defines the severity levels associated with the server logs.

Time Displays the time. 01:20:35

Category Lists the part of the Celerra 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.

NDMP

Severity level Indicates the importance of the 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.

3

Message text The log message. BlockBuf count in PAX Pool: 4

Table 18 Server Log Message Severity Levels

Severity Level Meaning

0 Emergency

1 Alert

2 Critical

3 Error

4 Warning

Table 17 Server Log Description (Continued) (Continued)

Log Component Description Example



Server Log Messages for NDMP and PAXTable 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.

5 Notice

6 Info

7 Debug

Table 18 Server Log Message Severity Levels (Continued)

Severity Level Meaning

Table 19 Server Log Messages

Server Log Messages Definition Corrective Action Other Considerations

/.etc/BackupDates corrupted, it has been renamed in BackupDates.bad and rebuilt

The /.etc/BackupDates file, which saves backup dates, is corrupted.

No corrective action is necessary. The backup level has been reset. You will need to restart the backup.

There is no impact to a previous restore, if applicable.

<MOVER_LISTEN> before tape open

The NDMP client sends a MOVER_LISTEN request before a TAPE_OPEN request.

Verify that your backup software is qualified with Celerra.

Refer to EMC NAS Interoperability Matrix on page 12.

Note: The backup or restore will fail if the client does not correct the error.

<MOVER_LISTEN> with read only tape

A Data Mover listen request requires a tape write, but the tape is in read-only mode.

Verify that your backup software is qualified with Celerra.The NDMP client needs to send the message in read/write mode.


3-way DAR unable to fsr 1234, residualCount 998

Occurs during a three-way direct access restore (DAR). The forward skip record failed with the remaining records and the restore fails.

Verify that your hardware, drivers, and backup software are qualified with Celerra.


Answer occurred with pdi==NULL

This point should not be reached with pdi==NULL. The Data Mover terminates the NDMP job, and the backup fails.

Verify that your backup software vendor is qualified with Celerra.



Backup type not supported: ufsdump

Celerra does not support the backup type specified in the NDMP backup software.Celerra supports the tar and dump backup types.This message occurs when using NDMP version 2.

Verify that the NDMP client is using either the tar or dump backup type.

Refer to your backup software vendor�s documentation and to Setting Environment Variables on page 34.

Note: The backup will fail without a valid backup type specified.

BlockBuf count in PAX Pool: <number>

Displays the number of buffers initialized in the pool. This message reflects the PAX ReadBuff parameter.<number> = number of buffers

To change the parameter values, edit the param file.

Refer to Configuring Data Movers on page 21.

Cannot reply connect An error occurred when sending a reply to CONNECT_OPEN. The Data Mover terminates the NDMP backup job.



cannot send NDMP_CONFIG_GET_TAPE_INFO reply

An error occurred when sending a reply to this message. The Data Mover terminates the NDMP backup job.



cannot send NDMP_CONNECT_OPEN reply

A reply to this request cannot be sent. The Data Mover terminates the NDMP job.



Table 19 Server Log Messages (Continued)




Can't convert filename using the specified NDMP.dialect, or invalid utf8 filename: 0x999

inode_%3456 is using for filename

These two messages appear together and indicate one of the following: � Internationalization on a

Data Mover is turned on and the specified dialect 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.

Verify that the NDMP dialect parameter specifies the correct dialect.

Refer to Configuring Data Movers for International Character Sets on page 25.

Can't have DIRECT=y/Y, and RECURSIVE=y/Y

Celerra does not support a recursive restore for a directory using DAR. The Celerra rejects this type of restore.

In your backup software, change the recursive restore setting to n.Verify that your backup software is qualified with Celerra.

For more information about DAR, refer to the NDMP Backup Concepts on page 6 section. For information on environment variables, refer to Setting Environment Variables on page 34 and to your backup software vendor�s documentation.

Can't open file_name for write in 3214

File <file_name> create error in 3294

These two messages indicate that the Celerra encountered a problem opening a file during a restore. The file <file_name> is skipped, and the restore continues.

Verify that your backup software is qualified with Celerra. The problem may be due to a failed backup.


create /.etc/BackupDates file failed, error: <error message>

Creation of the file BackupDates failed. This file saves backup dates. The backup is terminated.<error message> = type of error, for example, I/O error

You need to restart the backup.

Data interface is already deleted

At the time of a DATA_STOP request, the Data interface is already deleted.The backup should complete successfully.

No action is needed.




Empty archive The FILESYSTEM or PREFIX NDMP environment variable is not set in the NDMP client software.

On the NDMP client, set a value for the FILESYSTEM or PREFIX environment variable.

Refer to Setting Environment Variables on page 34 and to your backup software vendor�s documentation.

Error in NDMP restore arguments, argument <argument>

An error in the restore argument occurred. <argument> = argument name, for example, TYPE

Verify in the server log that you specified the correct backup root and path, for example, verify the spelling and the pathname.

ERROR MOVER try to Abort in state <state>

The state is illegal for aborting the MOVER interface; legal states are LISTEN, ACTIVE, or PAUSED.<state> = mover interface state, for example, NDMP_MOVER_STATE_IDLE



ERROR MOVER try to change record size in state <state>

The state is illegal for setting record size; only the IDLE state is legal.<state> = mover interface state, for example, NDMP_MOVER_STATE_ACTIVE



ERROR MOVER try to Continue in state <state>

The state is illegal for a MOVER_CONTINUE command; only the PAUSED state is legal.<state> = mover interface state, for example, NDMP_MOVER_STATE_ACTIVE



ERROR MOVER try to disconnect in state not connected

In a three-way configuration, the mover interface tried to disconnect while in a disconnected state.

Verify that your backup software vendor is qualified with Celerra and supports three-way backups.


ERROR MOVER try to Listen in state <state>

The NDMP client tried to stop the data interface in an invalid state.<state> = mover interface state, for example, NDMP_MOVER_STATE_ACTIVE



ERROR MOVER try to Set window in state <state>

The state is illegal for setting window size; only LISTEN or PAUSED states are legal.<state> = mover interface state, for example, NDMP_MOVER_STATE_ACTIVE







ERROR MOVER try to Stop in state <state>

The state is illegal for stopping the MOVER interface; only the HALTED state is legal.<state> = mover interface state, for example, NDMP_MOVER_STATE_IDLE



ERROR MOVER try to Stop in state <state> Reason:<reason>

The NDMP client sent a message not compliant with the NDMP Version 4 specification.<state> = mover interface state, for example, NDMP_MOVER_STATE_IDLE

<reason> = reason for pause, for example, NDMP_MOVER_PAUSE_EOF

Confirm that your NDMP client software is qualified with Celerra. If your software is qualified, then this message is informational only and you do not need to take any action.


ERROR MOVER type LOCAL try to Read

This should be a three-way read, but the mover interface type is not three-way compliant (it is not TCP).



Error on checking restore name list

An error occurred in the restore name list, which contains the file and directory names to restore.

Verify that the file and directory names you want to restore are listed correctly.

Refer to your backup software vendor�s documentation.

Error on environment variable: <variable>

The NDMP client sent an invalid environment variable.<variable> = variable associated with the error, for example, LEVEL

Verify that the environment variable listed in the log message is supported by Celerra.


extractFtreeList: bad path /xyz

The backup path provided does not exist.

Ensure that the correct path was specified and that the files specified for backup exist.

Note: This path is an absolute path and is case-sensitive.

Refer to your NMDP client documentation for more information.

level exceeded maximum allowed (11)

An incorrect increment level for backup was specified in the NDMP client software.

Verify that the backup level specified by the NDMP client is between 0 and 10.





Mover connection error (connectDone)

A connection to a three-way Data Mover accepting a TCP stream failed.The NDMP client sent an invalid command.



Mover continue before changing tape!!!

A MOVER_CONTINUE request was sent by the NDMP client before the tape was changed.The backup fails.



Mover not created The NDMP client sent an invalid command.The mover interface was not created when the NDMP client requested CONFIG_GET_CONNECTION_TYPE.



name /foo/skoilksfoiefslk... length 1102 too long

A pathname and filename is greater than 1024 bytes, which exceeds Celerra�s limit.

Ensure that the file and pathnames in the backup directory are less than 1024 bytes.

Refer to your NDMP client documentation.

ndmp already started The NDMP client attempted to start an NDMP listen thread while one was already running; starting another is unnecessary.



NDMP Tape parameter not set.

NDMP_TAPE_OPEN_REQUEST denied.

The NDMP ntape parameter is not set in the param file.The ntape parameter specifies the number of tape drives attached to a Data Mover.

Set the NDMP ntape parameter in the param file, and then reboot the Data Mover.

Note: You must set this parameter for both Data Movers involved in a three-way backup.

Refer to Configuring Data Movers for NDMP Backups on page 22.

NDMP.bufsz > 1168K in param file, bufsz was reset to 128K.

The Data Mover�s buffer size parameter (bufsz) is too large.The bufsz value is automatically reset to 128 KB, the default value.

To change the bufsz parameter value, edit the param file, and then reboot the Data Mover.






NDMP_MOVER_STATE_ACTIVE

For NDMP V4, the state is illegal for setting the window size; only the LISTEN and PAUSED states are legal.

Verify that your backup software is qualified with Celerra and supports NDMP Version 4.

Refer to EMC NAS Interoperability Matrix on page 12. For more information on NDMP-version compatibility refer to Overriding the NDMP Version on page 27.

network error (ndmp_mover.cxx: 2210)

Cannot send a message due to a network error.

Verify that the network is in a good state.

next_head fail (filename: line#)

The file cannot be restored because a notification to the NDMP client to read the file header failed for a direct access restore (DAR).

Verify that your backup software is qualified with Celerra and that it supports DAR.

Refer to your backup software vendor�s documentation and to EMC NAS Interoperability Matrix on page 12.

No password for NDMP user:ndmp

Retry:3 to get NDMP user:ndmp - Passwd

The NDMP password is not set on the Celerra Network Server.

Use the server_user command to set the NDMP password or to verify that the password is set properly.

Note: You must use the same password for the Celerra Data Mover and the NDMP client software. Also, the username must be ndmp.

Refer to Assigning Data Movers a Username and Password on page 32.

open /.etc/BackupDates file failed, error: <error message>

An open request failed on the backup dates file, which stores the backup run level. <error message> = type of error, for example, I/O error

No action is needed. This message could reflect a problem with the root file system.

param PAX.<paramName> 1024 out of range (4, 512)

param PAX.<paramName> is set to 64

These two errors indicate that the value for the PAX parameter <paramName> is outside the parameter�s allowed range.

Configure an acceptable value for the PAX parameter.

Refer to Configuring Data Movers for NDMP Backups on page 22 and to Viewing and Modifying Parameters on page 43 for parameter descriptions and value ranges.

Pattern Not Matched: /fs/file3 (not restored)

This pattern (file or directory) is not found in the archive.

Verify the integrity of the backup media and the backup path you entered.




pax not started At the time of the DATA_CONNECT request, PAX was not started.The Data Mover netd configuration file needs to include PAX. The netd file resides in /nas/server/slot_<x>/netd.Where:<x> = slot number of the Data Mover, for example, slot_2

Verify that your backup software is qualified with Celerra.Verify that the netd file includes PAX.

Refer to EMC NAS Interoperability Matrix on page 12 for qualification information.

PAX.nFTSThreads is reset to 64

This message indicates that a value has been specified for the PAX.nFTSThreads parameter that is too large. The value is reset and the backup continues normally.

No particular action is necessary. The backup still succeeds; it simply uses fewer threads to perform the backup.

Refer to Configuring Data Movers on page 21 for instructions on setting parameters.

pax_cmd_thread expected ARCHIVE/EXTRACT act, but received <action>

An internal error between NDMP and PAX occurred. The Data Mover and NDMP client establish a connection, an ARCHIVE or EXTRACT message is expected, but not others.<action> = action received, for example, LIST



pax_NotifyDataRead failed (filename: line#)

Notification to the NDMP client to read the first file header for a three-way direct access restore (DAR) failed.

Verify that your backup software is qualified with Celerra and that it supports three-way DAR.

Refer to your backup software vendor�s documentation and to EMC NAS Interoperability Matrix on page 12.

Read fault on /fs/test with error: <error message>

The file you are trying to back up cannot be read on Celerra.The attempt to read the file data failed.<error message> = type of error, for example, I/O error

Verify that the file or file system exists on Celerra, is in a good state, and is not being used by other applications.


RecBuf in NDMP Pool (count:64), NDMPMAXBUFSIZ is 128

Displays the number of buffers initiated in the pool and the maximum buffer size.This setting reflects the bufsz parameter.

To change the buffer size, edit the bufsz parameter in the param file, and then reboot the Data Mover.






Request (0x702) not supported (No mover)

The request is not supported because the mover interface is not yet created.



rw_thr() TCP connection closed with mover

PAX failed to receive a message from the TCP connection.

Verify that the network is in a good state.

Tape number > 8 in param file

The ntape parameter exceeds the maximum value, which is 8.The value specifies the number of tape drives attached to a Data Mover. Celerra supports no more than eight tape drives per Data Mover.

Change the NDMP ntape parameter value to 8 or less and reboot the Data Mover.


TAPE_OPEN c1t2l0 fails with stat: <state>

A TAPE_OPEN request failed with <state>.Many factors can trigger this message.<state> = state of the device, for example, Device Busy

Verify that no contention for the backup device exists among backup clients or Data Movers. This may cause the backup to fail.

thrdId 0 directory/link error

During a restore, the Celerra encountered a problem with the directory and/or link.

Verify that your backup software is qualified with Celerra. You will need to restart the restore. The problem may be due to a failed backup.


thrdId 0 error on restore file to root filesystem

Permission denied to restore <file or dir> on Root fs

An attempt was made to restore to the root file system, which the Celerra does not support.

Ensure you are not trying to restore to root the file system.

thrdId 0 namedFileStreamSkip error in 3214

The Data Mover encountered a problem and subsequently skipped data for the named file stream. The restore is terminated.

Verify that your backup software is qualified with Celerra. You may be trying to restore a failed backup.


thrdId 0 positionTape error

A DAR restore encountered a problem positioning the tape.

Verify that your backup software is qualified with Celerra. The problem may be due to a failed backup or a corrupted tape.





thrdId 1 mod_name error The Celerra could not rename a file during a restore.

Verify that your backup software is qualified with Celerra. The problem may be due to a failed backup.


Try to Stop data interface in state 3

The backup client should not stop the data interface in this state.



Try to tape_mtio in mover active state

The NDMP client tried to manipulate the tape drive while the Data Mover had ownership of the tape drive.

The NDMP client should not try to manipulate the tape drive while the Data Mover has ownership of it.

Refer to your NDMP client�s documentation for more information.

Unable to get position on tape (d),error: <error message>

An error occurred while reading the tape position. The tape is either not opened or is not ready.<error message> = type of error, for example, Device Error

Verify that the tape is in a good state.

Unable to reach password data base

The ndmp password is not set. Set a password for the ndmp user.

Refer to Assigning Data Movers a Username and Password on page 32.

Unknown Auth type (0x8) An unknown authorization request was made.Celerra supports text and MD5 authorizations.

Verify that the NDMP client uses either text or the MD5 authorization format.

Refer to Assigning Data Movers a Username and Password on page 32 and to your backup software documentation.

Unknown BT_NDMP_BUTYPE An invalid backup type is specified in the NDMP client software.Celerra supports tar and dump backup types.

Verify that the tar or dump backup type is specified in the NDMP client software.

Refer to your backup vendor�s documentation for information on setting the backup type to tar or dump.

Note: The backup will fail without a valid backup type specified.





unknown mt cmd 0x97 An unknown tape command was received. When using server_archive, an incorrect mt command was entered.

If using server_archive, verify that you entered the server_mt command correctly.Otherwise, verify that your backup software vendor is qualified with Celerra.

For more information on the server_mt command, refer to the Celerra Network Server Command Reference Manual, to the man pages, and to the Using the Celerra server_archive Utility technical module.Refer to EMC NAS Interoperability Matrix on page 12 for information on Celerra qualifications.

Unknown procedure (8765)

Unknown command 0x8888

Celerra received an unknown message from the NDMP client and terminated the NDMP backup job.

Verify that the your backup software is qualified with Celerra.


VLC_FS_STATUS_DEVICE_NOT_FOUND

The specified volume was not found.

Check the spelling of the volume name you specified.

VLC_FS_STATUS_DEVICE_TOO_SMALL

VLC_FS_STATUS_DEVICE_TOO_LARGE

These two messages indicate that the target volume where you want to restore the file system is not identical in size to the original file system.

Create a volume that is the same size as the original file system. Restore the file system to this volume.

VLC_FS_STATUS_ERROR Celerra encountered an internal error. This condition causes the backup or restore to fail.


Refer to EMC NAS Interoperability Matrix on page 12 to verify software qualification. Refer to the related PAX server log messages for more information on this server log condition.

VLC_FS_STATUS_NOT_FOUND <file_system>

The specified <file_system> was not found.

Correct the pathname, and then restart backup.

VLC_FS_STATUS_NOT_RAWFS <file_system>

The target <file_system> specified for recovery is not a raw file system.

When restoring a volume-level copy, the target file system must be a raw file system (rawfs).

Refer to the Using Celerra Replicator technical module for more information.

VLC_FS_STATUS_NOT_READ_ONLY

For a volume-level copy, the specified file system must be mounted as a read-only file system.

Mount the file system you want to copy as a read-only file system.

Refer to the Using Celerra Replicator technical module for more information.






VLC Open error

These messages appear together. They indicate that a volume-level copy (VLC) backup failed because a read/write file system was used. You must use a read-only file system to perform a volume-level copy.

To perform a volume-level copy, create a checkpoint, ensure the environment variable VLC=y, and back up the read-only file system using NDMP.

Refer to Setting Environment Variables on page 34.For more information on volume-level copies, refer to the Using Celerra Replicator technical module.

VLC_FS_STATUS_NOT_UFS

<file_system>

The specified <file_system> is not a uxfs type file system. A volume-level copy requires that you use an uxfs file system. This file-system type is the default for Celerra.

You must back up a volume-level copy from a uxfs file system. A volume-level restore from tape must be to a raw file system.

VLC_FS_STATUS_READ_FAILED

VLC_FS_STATUS_WRITE_FAILED

These two messages indicate that a read or write to the file system failed.

Refer to the related PAX server log messages for more information about this error condition.

Write count exceeds bufsz

Read count exceeds bufsz

Tape write or read exceeds the bufsz (buffer size) parameter. If the bufsz value is larger than 1168 KB, the value is automatically reset to 128 KB.

To change the bufsz parameter, edit the param file and reboot the Data Mover.

Refer to Configuring Data Movers on page 21.

Write IO error status error: <error message>

A write I/O error occurred.<error message> = type of error, for example, DeviceError

Verify that the tape drive is in a good state.





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




Index

Aattributes, backup for Windows NT 34

Bbackup levels, with Celerra 35backup software

configuration guidelines 37configuring for Celerra 37

Ccabling the TLU 13Celerra Network Server

backup levels with 35configuration guidelines for 20setting environment variables on 34

Celerra NS seriesmedia interface adapter for 20parameters for, summary 22port configuration with 4setting parameters on 24

checklist for troubleshooting NDMP backups 59

command syntax summary 56commands

server_cpu, summary 56server_devconfig, summary 56server_log, summary 57server_param, summary 58server_pax, summary 58server_user, summary 57

configuration guidelinesfor Celerra 20for your backup software 37

configurations for NDMP backupsdual-TLU 8simple 6single TLU 7

configuringData Movers 21roadmap for 19your backup software 37

connecting the robot to a Data Mover 13customer education on EMC products 74Customer Support, reporting a problem to 60

DDAR, see direct access restoreData Movers

caution for connecting tape drives 5configuring 21failover caution 5parameters for 21setting a username and password for 32

devices, discovering from Celerra 30

direct access restore 10discovering devices from Celerra 30dynamic drive sharing

defined 2overview of 11restrictions for 4

Eeducation, on EMC products 74environment variables 34

Ffacility, PAX parameters 44failover of a Data Mover, caution 5Fibre Channel TLU configuration 13file restoration, overview 10

Gguidelines for configuring

backup software 37Celerra Network Server 20

Iinternational character sets

support overview 14with dump and tar backup types 15

interoperability matrix, accessing 12

Llevels of backup, with Celerra 35

Mmanaging NDMP backups 43MD5 password encryption, method for Celerra

33media interface adapter, for the Celerra NS

series 20modifying parameters 48multithreaded backup design 16

NNASA thread group 16, 54NASS thread group 16, 54NASW thread group 16, 54NDMP

backups, managing 43concepts 6configurations 6version, overriding 27

Network Data Management Protocol, see NDMP

NIS, setting a Data Mover�s username and password with 32

NS series, see Celerra NS series

76 of 78 Configuring NDMP Backups with Celerra and BakBoneNetVault

Version 5.3

Ooverriding the NDMP version 27

Pparameters

adding and editing 23configuring 21file format 21for international character sets 25modifying 48nontunable 51tunable 49viewing information on 44

password, setting on a Data Mover 32PAX facility, parameters 44performance enhancements 16

Rrecovery, overview 10related information, for Celerra and backup

software 74reporting a problem to Customer Support 60restoration of files, overview 10restrictions, general 4roadmap for configuring NDMP backups 19robotics, connecting to a Data Mover 13

SSCSI TLU cabling configuration 13server log messages

component parts of 60for NDMP and PAX 62reading 60severity levels for 61

server_cpu command, summary 56server_devconfig command, summary 56server_log command, summary 57server_param command, summary 58server_pax command, summary 58server_user command, summary 57setting

a Data Mover�s username and password 32

environment variables on Celerra 34parameters on Celerra 22

statistics, viewing 52stripe size restriction, on an EMC storage

system 4system requirements, for NDMP backups 12

Ttar backups

behavior with Celerra 15terminology

definitions of 2differences with backup software vendors

3

third-party softwareconfiguration guidelines 37configuring for Celerra 37

thread groups 16, 54three-way backups

heterogeneous 10overview 9restrictions with 4

TLUcabling 13SCSI port, sample 31setting up 29

TLU configurationsdual TLU 8Fibre Channel 13simple NDMP 6single TLU 7

troubleshooting checklist 59

Uusername, setting on a Data Mover 32

Vviewing backup parameters 44viewing backup statistics 52

WWindows NT attributes, backing up 34


Notes

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.

About This Technical ModuleAs 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 DocumentationYour suggestions will help us continue to improve the accuracy, organization, and overall quality of the user publications. Please send a message to [email protected] with your opinions of this document.

Version 5.3 78 of 78

Documents

NDMP_Backups_with_Celerra