NDMP_Backups_with_Celerra

Configuring NDMP Backups with Celerra and BakBone NetVaultP/N 300-001-623 Rev A01 Version 5.3 August 2004 Contents Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Terminology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .2 Restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4 Cautions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .5 NDMP Backup Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 NDMP Configurations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6 Restoring File Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .10 Dynamic Drive Sharing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11 System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 EMC NAS Interoperability Matrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . .12 Planning Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .13 Data Mover-to-TLU Cabling Examples . . . . . . . . . . . . . . . . . . . . . . . .13 Implementing International Character Support with NDMP . . . . . . .14 Multithreaded Backup and Restore Design . . . . . . . . . . . . . . . . . . . .16 User Interface Choices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18 Configuring NDMP Backups with Celerra and BakBone NetVault Roadmap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19 Configuration Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20 Configuring Data Movers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21 Setting Up the TLU. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29 Assigning Data Movers a Username and Password . . . . . . . . . . . . . . . .32 Setting Environment Variables. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34 Configuring Your Backup Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Guidelines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37 Configuration Steps . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38 Backing Up a VDM File System with NDMP . . . . . . . . . . . . . . . . . . . . . . .42 Managing NDMP Backups on Celerra . . . . . . . . . . . . . . . . . . . . . . . . . . . .43 Viewing and Modifying Parameters . . . . . . . . . . . . . . . . . . . . . . . . . .43 Viewing Backup Statistics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52 Command Syntax Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .56 Troubleshooting NDMP Backups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Troubleshooting Checklist. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .59 Related Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Want to Know More? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74 Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .75 1 of 78 Introduction The Network Data Management Protocol (NDMP) allows you to control the backup and recovery of an NDMP server through a network backup application, without installing third-party software on the server. In a Celerra® Network Server, the Data Mover functions as the NDMP server. This technical module is part of the Celerra Network Server information set and is intended for the System Administrator implementing a backup strategy with one or more Celerra Network Servers. The System Administrator should be familiar with backup and restore operations and with the basic administration of a Celerra Network Server. This technical module explains how to perform Network Data Management Protocol (NDMP) backups with the Celerra Network Server and your backup software. It also contains the information you need to cable and configure the Celerra Network Server. Use this and other Celerra Network Server documentation in conjunction with the documentation for your specific backup vendor. Terminology This section defines terms that are important to understanding NDMP backup capabilities on the Celerra Network Server. Refer to the Celerra Network Server User Information Glossary for a complete list of Celerra terminology. automated backup and restore: A procedure in which a remote backup server running NDMP-compliant backup software backs up data to a TLU. backup and restore: A technique for ensuring file-system integrity and security by backing up to tape or disk a file system or incremental changes to a file system; this data can then be restored at a later time. cumulative incremental backup: A backup that copies all data objects modified since the last full backup. To restore data when cumulative incremental backups are in use, you need only the latest full backup and the latest cumulative incremental backup. See also differential incremental backup, full backup, incremental backup. DAR: Direct access restore. An optimized data recovery operation that allows the NDMP client to directly access backed-up data in the middle of a tape set without having to traverse the tape set sequentially. differential incremental backup: A backup that copies data objects modified since the last full backup or incremental backup. To restore data when differential incremental backups are in use, the newest full backup and all subsequent differential backups are required. See also cumulative incremental backup, full backup, incremental backup. dynamic drive sharing (DDS): A feature of NDMP-compliant backup software that allows NDMP servers to share tape drives. full backup: A backup that copies all of a defined set of data objects, regardless of whether they have changed since the last backup. A full backup is the basis from which incremental backups are taken. See also cumulative incremental backup, differential incremental backup, incremental backup. 2 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone NetVault heterogeneous three-way backup: A three-way NDMP backup involving a Data Mover, which serves as the interface to the file system or primary storage system, and a qualified third-party NDMP server, which serves as the interface to the tape devices or other secondary storage. See also three-way backup. incremental backup: A term that encompasses both cumulative incremental backups and differential incremental backups. Any backup that copies only data objects modified since the time of some previous backup. See also cumulative incremental backup, differential incremental backup, full backup. local backup: A procedure that backs up a copy of a file system or incremental changes to a file system from a Data Mover to a locally attached TLU. See also automated backup and restore, manual local backup. NDMP: Network Data Management Protocol. An open standard network protocol designed for enterprise-wide backup and recovery of heterogeneous networkattached storage. NDMP client: The application that controls the NDMP session. The NDMP client runs an NDMP-compliant backup application, such as LEGATO® NetWorker. NDMP Host: The host system (Data Mover) that executes the NDMP server application. Data is backed up from the NDMP Host to either a local tape drive or to a backup device on a remote NDMP Host. NDMP server: The NDMP process that runs on an NDMP Host, which is a Data Mover in a Celerra Network Server environment. PAX: Portable Archive Interchange. A Celerra Network Server archive protocol that works with standard UNIX tape formats. remote backup: A remotely initiated procedure that backs up data to a TLU that can be attached to a target server different from the source Data Mover. Your configuration determines whether data traverses the network. See also automated backup and restore, three-way backup. tape library unit (TLU): A physical device that contains and manages multiple magnetic tape units accessible as a single unit. three-way backup: An NDMP-protocol backup that directs data from one Data Mover through a network connection to a remote Data Mover to its attached tape library backup device. See also heterogeneous three-way backup. Terminology Differences The following terminology differences exist between this guide and the third-party documentation. Table 1 Terminology Differences EMC Term Tape library unit (TLU), jukebox, tape drive Equivalent Third-Party Terms Library (refers to any backup storage device), autochanger handle, autochanger Robotic arm, arm changer Celerra filer, NAS filer, application server TLU robot NDMP-Host Data Mover Configuring NDMP Backups with Celerra and BakBone NetVault Version 5.3 3 of 78 On an NS-Series Celerra Network Server. the AUX port used for backup defaults to Fibre Channel Arbitrated Loop (FC-AL) and 1 Gb. When you restore a Data Mover’s root partition. NDMP does not follow symbolic links among file systems. • Data Mover to NDMP server in a heterogeneous three-way configuration. you must edit the parameter file for the Data Mover to which you are connecting the tape drive. NDMP does not support the Archive Bit method. This includes the NS-Series Celerra Network Servers. Therefore. For more information on symbolic links. refer to Configuring CIFS on Celerra for the Windows Environment. The Data Movers can reside on the same Celerra Network Server or on different Celerra Network Servers. The special wildcard characters. For optimal backup stripe size settings on Symmetrix® and CLARiiON® systems. ◆ EMC supports NDMP drive sharing through a storage area network (SAN) only. as well as the include/ exclude options. include all directories in the file/directory list when creating the backup job. only full backups are supported with BakBone NetVault and Celerra. you must specify a restore path that is different from the original location. Celerra filer Restrictions When configuring your Celerra Network Server. only the Date/Time stamp method is supported. To use the AUX port in a switched fabric environment or to change the speed. note the following restrictions: ◆ EMC supports three-way NDMP backups in the following circumstances: • Celerra Data Mover to Data Mover.Table 1 Terminology Differences (Continued) EMC Term Celerra Network Server Equivalent Third-Party Terms Client computer. which can provide one or both Data Movers in a three-way configuration. Refer to the EMC NAS Interoperability Matrix on page 12 and check with your vendor for information on dynamic drive sharing support.3 Configuring NDMP Backups with Celerra and BakBone NetVault . To back up multiple directories. Refer to Configuring Data Movers on page 21. refer to the EMC NAS Interoperability Matrix on page 12. You cannot restore to the original location. Currently. an NDMP backup does not include a symbolic link's target file system. are not supported. Refer to EMC NAS Interoperability Matrix on page 12 to locate the most upto-date information on heterogeneous three-way backup support. ◆ ◆ ◆ ◆ ◆ ◆ 4 of 78 Version 5. Stripe size on your storage system can affect backup performance. you must directly connect the tape drive to the new Data Mover and restart the backup. ! ◆ CAUTIONS You must configure Data Movers attached to tape drives for any NS Series Celerra Network Server. You may also need to reconfigure your backup software. where relevant: — Propagate changes to the consistent binding table.3 5 of 78 . refer to Configuring Data Movers on page 21. This will cause the backup to fail and could cause tape contention. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. ! ◆ ◆ Important: If you change your network zoning configuration. For more information. If a failover occurs during a backup. Do not connect a standby Data Mover to the TLU by means of a SCSI connection.Cautions This section lists cautions for configuring your Celerra Network Server for NDMP backups. — Adjust the backup software to reflect the new zoning configuration. The NDMP protocol separates the control and data transfer components of a backup or restore.3 Configuring NDMP Backups with Celerra and BakBone NetVault . NDMP Configurations The procedures in this technical module assume that the TLU connects directly to the Celerra Network Server Data Mover. 6 of 78 Version 5. Only the backup software’s control data (scheduling. The actual backups are handled by the Data Mover. without traversing the network. as shown in Figure 1.NDMP Backup Concepts The Network Data Management Protocol (NDMP) allows you to control the backup and recovery of an NDMP server through a network backup application. without installing third-party software on the server. and TLU commands) travels across the network. cataloging. the Data Mover functions as the NDMP server. which minimizes network traffic. NDMP-based backups are used for high-capacity backups and in environments where true multiprotocol (both CIFS and NFS) support is required. In a Celerra Network Server. Backup data flows from the storage system to the Data Mover to an attached tape library backup device. This section covers: ◆ ◆ ◆ Basic NDMP configuration Single and dual-TLU configurations Three-way backups Simple NDMP Backup Configuration The NDMP architecture uses a client/server model in which the backup software is the NDMP client to the NDMP-Host Data Mover. Refer to your backup software vendor’s documentation for information on configuring a TLU attached to a backup host. The Data Mover maintains a state machine for each NDMP client connection that executes and maintains the backup and restore processes. Network Boundary Celerra NDMP Client with Backup Software NDMP Control Data NDMP-Host Data Mover Robotic Control Backup Data SB14 SB12 SB10 SB11 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 SB8 SB6 SB4 SB2 SB0 SB1 SB3 SB5 SB7 SB9 SB13 SB15 Storage System Tape Library Backup Device CNS-000349 Figure 1 Simple NDMP Backup Single TLU Configuration Figure 2 on page 8 demonstrates the first and most common TLU configuration. One Data Mover can execute both backups and robot operations.3 7 of 78 . When a TLU configuration consists of several Data Movers sharing one robot. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. only one Data Mover needs to be connected to the robot. as shown in Figure 2 on page 8. Robotic commands are executed from the backup software. A maximum of four simultaneous backups are supported on each NDMP-Host Data Mover. Note: Your backup software and TLU manufacturer determine which configuration options are available to you. The NDMP client controls 8 of 78 Version 5. Backup Host NDMP Client with Backup Software Network Boundary NDMP Control Data Celerra NDMP Control Data NDMP-Host Data Mover Backup Data Backup Data NDMP-Host Data Mover Backup Data and Robotic Control SB14 SB12 SB10 SB8 SB6 SB4 SB2 SB0 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 Storage System SB1 SB3 SB5 SB7 SB9 SB11 SB13 SB15 Tape Library Backup Device CNS-000348 Figure 2 Single-TLU NDMP Backup Dual-TLU Configuration Figure 3 shows two Data Movers connected to two separate storage-system volumes and two separate tape library backup devices.3 Configuring NDMP Backups with Celerra and BakBone NetVault . With NDMP Version 2. The Data Mover processes the data and sends it to the tape device. NDMP Client with Backup Software Network Boundary Celerra NDMP Connection NDMP Connection NDMP-Host Data Mover Robotic Control Backup Data Backup Data NDMP-Host Data Mover Robotic Control SB14 SB15 51BS 41BS SB12 SB13 31BS 21BS SB10 SB11 11BS 01BS SB8 SB9 9BS 8BS SB6 SB7 7BS 6BS SB4 SB5 5BS 4BS SB2 SB3 3BS 2BS SB0 SB1 1BS 0BS PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 1BMS 0BMS 4SP 3SP 2SP 1SP 0SP Tape Library Backup Device Storage Systems Tape Library Backup Device CNS-000350 Figure 3 Dual-TLU NDMP Backup Three-Way Backup Configuration Some third-party vendor backup software is not qualified with the Celerra Network Server for three-way backup configurations. The NDMP tape server can be a Data Mover or another qualified server. 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) ◆ Configuring NDMP Backups with Celerra and BakBone NetVault Version 5.and launches the backup. 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.0 and higher and some backup software vendors.3 9 of 78 . This configuration is known as a three-way backup. and then restores the file system on the storage system. During a direct access restore. This operation. DAR requires that you enable the file history feature on the Celerra Network Server. Note: It is unnecessary to back up the Celerra Network Server root file system. the NDMP client moves directly to the location of the file you want to restore. retrieves the file system from the backup device. You are not allowed to restore to this file system. The down side to this feature is that the file history information adds network traffic. NDMP Client with Backup Software Storage System Celerra NDMP Control Data Backup Data Backup Data Only NDMP-Host Data Server Network Boundary NDMP Control Data Celerra Tape Library Backup Device SB14 SB12 SB10 SB8 SB9 SB11 SB13 SB15 Backup Data Robotic Control SB6 SB4 SB2 SB0 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 SB1 SB3 SB5 SB7 NDMP-Host Tape Server CNS-000351 Figure 4 Three-Way NDMP Backup Restoring File Systems A restore reverses the backup process shown in Figure 1 on page 7. In a three-way backup. 10 of 78 Version 5. both file system and control data travel across the network. This connection can be a dedicated network to avoid network traffic. The benefit of the NDMP backup and restore is that it does not impact the network with data traffic. without reading through the entire backup to find the file. sends it to the Data Mover. Figure 4 illustrates a Data Mover-to-Data Mover three-way backup. The NDMP feature direct access restore (DAR) allows you to perform file-level restores. initiated by the backup software.Note: The Celerra Network Server supports heterogeneous three-way backups with some backup software vendors.3 Configuring NDMP Backups with Celerra and BakBone NetVault . which tells the Celerra Network Server to send the NDMP client the file history information for the backup. By default. a Data Mover supports only four concurrent backups per Data Mover. However.3 11 of 78 . a Data Mover is configured to accommodate four attached tape drives. 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 Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Celerra NDMP-Host Data Mover NDMP Client with Backup Software Celerra SAN Tape Drive Network Boundary NDMP-Host Data Mover CNS-000356 Figure 5 Dynamic Drive Sharing A Celerra Data Mover supports up to eight attached tape drives per Data Mover. EMC supports sharing tape drives over a SAN as shown in Figure 5. you must edit the ntape parameter.Dynamic Drive Sharing Several backup software vendors are developing the ability to allow more than one NDMP-Host Data Mover to share a single or multiple tape drives. To attach more than four 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. Dedicated network (optional). Search for NAS Interoperability Matrix. The EMC NAS Interoperability Matrix appears in the list. and application support for Celerra network-attached storage (NAS) products. network.0.com. In the Sort Search Results by box.System Requirements This section describes the Celerra Network Server software. Go to http://powerlink. such as backup software.and Celerra-compatible backup software running on the NDMP client. 2. To view the EMC NAS Interoperability Matrix: 1. Celerra Network Server. 3.emc.3 Configuring NDMP Backups with Celerra and BakBone NetVault . Fibre Channel switches. Note: The Celerra Network Server supports NDMP Version 4. Software Hardware Network Storage EMC NAS Interoperability Matrix Refer to the EMC NAS Interoperability Matrix for definitive information on supported software and hardware.3. Compatible tape device or tape library unit. and storage configurations required for performing NDMP backups as described in this technical module. hardware. select Score. NDMP. Table 2 System Requirements for NDMP Backups Celerra Network Server Version 5. 12 of 78 Version 5. refer to the appropriate vendor’s documentation. An overview of how the Celerra Network Server handles international character sets.Planning Considerations This section includes: ◆ ◆ Cabling examples for SCSI. Configuring NDMP Backups with Celerra and BakBone NetVault SB1 SB3 SB5 SB7 SB9 SB11 SB13 SB15 Version 5.3 13 of 78 . and the other one is daisy chained to two tape drives and a robot. Robotic control is configured in the backup software. Storage System Celerra Tape Library Unit SB14 SB14 SB15 SB12 SB12 SB13 SB10 SB10 SB11 SB8 SB8 SB9 SB6 SB6 SB7 SB4 SB4 SB5 SB2 SB2 SB3 SB0 SB0 SB1 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 CNS-000353 Figure 6 Sample SCSI Cabling Configuration Robot Connectivity If a configuration consists of several Data Movers sharing one TLU robot. two SCSI connections go from the NDMP-Host Data Movers to the TLU. All the Data Movers in Figure 6 have two direct SCSI connections to the storage system.and Fibre Channel–connected TLUs. For more information on robotic control. refer to your backup software vendor’s documentation. refer to Setting Up the TLU on page 29. Fibre Channel Configuration Figure 7 shows the Fibre Channel connection from the storage system to a switch and from the switch to the top port of each Data Mover. For instructions on setting up the TLU and identifying device names. SCSI Cabling Configuration In Figure 6. you need to connect only one of these Data Movers to the robot. and then from that switch to the TLU through Fibre Channel. The bottom port of each Data Mover connects to another switch through Fibre Channel. Data Mover-to-TLU Cabling Examples This section includes examples of both SCSI and Fibre Channel cabling from the Data Mover to the TLU. One SCSI connection is daisy chained to two tape drives. For information on cabling a TLU to a backup host. In a configuration where SCSI is used to connect to a TLU. Celerra Network Server supports the architecture-independent UTF-8 Unicode format. verify that the EMC-qualified NDMP backup vendor you choose supports international character sets. 14 of 78 Version 5. Tape Library Backup Device Celerra Storage System FC FC FC SB5 SB14 SCSI FC FC SB10 SB12 SB8 DM 1 DM 2 SB3 SB13 SB15 SB14 SB6 SB12 SB4 SB10 Bridge FC FC Switch SB2 SB8 SB0 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 SB1 SB6 Switch FC SB4 SB2 SB0 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 Tape Library Backup Device CNS-000352 Figure 7 Sample Fibre Channel Configuration Implementing International Character Support with NDMP The Celerra Network Server supports international character sets if you have Unicode enabled.3 Configuring NDMP Backups with Celerra and BakBone NetVault SB1 SB3 SB5 SB7 SB9 SB11 SB13 SB15 . When performing NDMP backups with Unicode enabled. 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. If your vendor does not support 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.Figure 7 illustrates a two-switch configuration. Verify Vendor Support for International Character Sets Verify that the EMC-qualified NDMP backup vendor you choose supports 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. If you have chosen a translation configuration file. Refer to the technical module Using International Character Sets with Celerra for details about translation files and choosing the appropriate file for your configuration.The Celerra Network Server’s default translation dialect is UTF-8. the data is backed up without the catalog information. For more information about setting parameters.Vendor Supports International Characters If your vendor supports international character sets. For more information on how to use international character sets with the Celerra Network Server. 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. You must also set the Celerra Network Server parameters as specified in Configuring Data Movers for NDMP Backups on page 22. NDMP tar/dump Backups During an NDMP tar or dump backup. follow the vendor instructions for implementation and follow up with your backup software vendor regarding any issues you encounter. but your backup vendor does not support international character sets. 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. you may set up your environment to work with the best translation configuration file for your environment. 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. The default translation dialect is UTF-8. Vendor Does Not Support International Characters If Unicode is enabled on your Celerra Network Server. These backup types are processed differently when difficulties with the translation are encountered. refer to the Using International Character Sets with Celerra technical module. Data Backup Type Behavior with International Character Sets Data is backed up onto tape using either the tar or dump NDMP backup type.3 15 of 78 . refer to Configuring Data Movers on page 21. the filename is converted to the client encoding and sent to the client as the file history. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. An error log is created. 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. displays backup statistics for each thread group. and NASW. These thread groups process and deliver backup and restore data and metadata. referred to as NASA. The design involves three main thread groups.Multithreaded Backup and Restore Design The Celerra Network Server uses a multithreaded backup and restore design that improves the Celerra NDMP backup and restore performance in most environments. which is covered in Viewing Backup Statistics on page 52.3 Configuring NDMP Backups with Celerra and BakBone NetVault . Table 3 Backup Thread Groups Thread NASA Function • Sends metadata to the NDMP backup software • Reads file data • Writes data to the buffer pool • Traverses the file system • Provides metadata for each file and/or directory • Gets data from the data buffer pool • Writes data to tape or sends it to a remote Data Mover or NDMP server NASS NASW 16 of 78 Version 5. NASS. The server_pax command. it waits for subsequent threads to complete their backup portions before starting a new one. Each restore thread is responsible for a single small file or part of a bigger file. which is described in more detail on Table 9 on page 49. Multithreaded Restore Process The multithreaded restore process involves the NASA and NASW thread groups. which is described in more detail in Table 9 on page 49. Client with NDMP-compliant backup software Network Boundary Data Mover NASA Backup and Restore Threads Data Buffer Pool SB14 SB12 SB13 SB15 Stat Buffer Pool SB10 SB8 SB6 SB4 SB2 SB0 PS0 PS1 PS2 PS3 PS4 SMB0 SMB1 SB1 SB3 SB5 SB7 SB9 SB11 NASS Storage System FTS Threads Celerra NASW Tape Library Unit CNS-000441 Figure 8 Multithreaded Backup and Restore The stat buffer pool contains a user-definable number of buffers (determined by the paxStatBuff parameter). the NASA thread group activates multiple backup threads and puts metadata buffers in the stat buffer pool. the NASA thread activates the restore threads and waits for NASW to deliver data to the data buffer pool. Upon receiving metadata buffers. You can define the number of restore threads through the nRestore parameter. The user-definable ReadBuff parameter determines the number of buffers between the NASA and NASW thread groups. When the backup software begins the restore process. When a thread completes its portion of the backup. Figure 8 shows the components of the multithreaded backup and restore design. When a metadata buffer is available. in sequential order. which is shared by NASA and NASS. NASS traverses the backup file system or directory and returns metadata to the stat buffer pool.Multithreaded Backup Process When you initiate an NDMP backup. The number of backup threads is determined by the nThread parameter. which transfer file-system metadata. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. a backup thread backs up one directory or file per thread.3 17 of 78 . You can also perform some of these tasks using Celerra Manager.3 Configuring NDMP Backups with Celerra and BakBone NetVault . refer to Getting Started with Celerra Management in the documentation kit. This technical module describes how to configure NDMP backups using the command line interface (CLI).User Interface Choices The Celerra Network Server offers flexibility in managing networked storage based on your support environment and interface preferences. For more information about Celerra Manager. 18 of 78 Version 5. click the text in the roadmap to access that phase.3 19 of 78 . click the roadmap symbol at the center bottom of the page. any nonsequential phases are represented in the blocks at the base of the roadmap. This process contains components that represent the sequential phases of the roadmap. Configuring Data Movers Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software Backing Up a VDM File System with NDMP Managing NDMP Backups on Managing NDMP Backups on Celerra Celerra Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. To return to this roadmap from other pages. In addition. Each phase contains the tasks required to complete the process.Configuring NDMP Backups with Celerra and BakBone NetVault Roadmap This roadmap shows the process for configuring NDMP backups with Celerra and your backup software vendor. Note: When viewing online. The ability to connect a Data Mover to a TLU is dependent on the number of SCSI ports on a Data Mover. The TLU may also have Fibre Channel connections. You can connect multiple Data Movers to the same TLU. In Celerra Network Server Version 5. you must physically connect the Data Mover’s TLU cable to the standby. you should do so before. The TLU may have multiple SCSI host connections (refer to the TLU documentation for installation and configuration information). It is advised that these storage-system SCSI ports not be used for TLU connections. For each TLU SCSI connection. not after.3 or later. and restart the backup. If an NDMP-Host Data Mover fails over to its standby. Instructions on how to install a MIA in a NS series Celerra are documented in individual setup instructions provided with each system. You cannot daisy chain any of the Data Mover’s storage-system SCSI connections to the TLU. If you plan to turn on Internationalization. The default ntape value is now set to 4. you do not need to configure the ntape or nbuf parameters. ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ ◆ 20 of 78 Version 5. you create your file systems.Configuration Guidelines ◆ The Celerra Network Server supports a maximum of four concurrent backups per NDMP-Host Data Mover. Some older models of a Data Mover may have only two SCSI ports. Do not connect the Celerra Network Server Control Station to the TLU. which is sufficient for performing backups with one through four attached tape drives. The nbuf parameter has been removed altogether. which are required for storage-system connectivity and redundancy. An NS Series Celerra Network Server requires a media interface adapter (MIA) for device connection to the AUX-0 port. You may also need to reconfigure the backup software with the appropriate address. EMC recommends attaching no more than two tape drives.3 Configuring NDMP Backups with Celerra and BakBone NetVault . the parameter value for gid32 must be set up as follows: In the system parameter file. overwrite the values in the system file. type: param ufs gid32=1 Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra In the server parameter file.3 21 of 78 . Configuring Your Backup Software For a summary of parameter file formats. /nas/site/slot_param. /nas/server/slot_3/param. and if found. Parameter Files Parameters are stored in text files. it is recommended that you search the file for all occurrences of the parameters. Note: This procedure is required for NS series Celerra Network Servers. To allow you to modify parameters for individual Data Movers. However. /nas/site/slot_param (system) and /nas/ server/slot_<x>/param (server). if you want 32-bit GIDs (group IDs) turned on for all Data Movers except server_3. For example. you must reboot the Data Mover for the parameters to take effect.Configuring Data Movers This section includes the following procedures. the values in the server file. modify one and remove any duplicates. if the file does contain duplicates. Configure parameters for Internationalization. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Procedure Configuring Data Movers for NDMP Backups on page 22 Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables Configuring Data Movers for International Character Sets on page 25 Overriding the NDMP Version on page 27 Override the NDMP version used by the Celerra Network Server. /nas/server/slot_<x>/param. which follows. Configuring Data Movers Action Define parameters for NDMP-Host Data Movers. Because these files might already contain parameter settings. /nas/site/slot_param. refer to Parameter File Format. type: param ufs gid32=0 Note: After editing the system or server file. the last one in the file takes precedence. Example: param NDMP bufsz=256 Configuring Your Backup Software fcTach enable_fa bric_aux0 0 (default) or 1 Note: This parameter applies only to the NS series Celerra Network Servers. param fcTach enable_fabric_aux0=1 on a Celerra NS-Series system. configures the tape backup port for a Fibre Channel switched fabric environment.3 Configuring NDMP Backups with Celerra and BakBone NetVault . 22 of 78 Version 5.Parameter File Format Parameters are formatted as follows: param <module> <parameter> = <paramvalue> Where: <module> = name of module <parameter> = name of parameter <paramvalue> = value associated with the parameter Configuring Data Movers for NDMP Backups Table 4 describes the bufsz. Note: Configuring the enable_fabric_aux0. refer to Managing NDMP Backups on Celerra on page 43. For information on optional performance-related parameters. and linx_speed_aux0 parameters. refer to the Celerra Network Server Parameters Guide. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra fcTach linx_spee d_aux0 0x4000 (default) or 0x2000 Note: This parameter applies only to the NS series Celerra Network Servers. Table 4 Summary of Required Parameters Configuring Data Movers Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables Module NDMP Parameter bufsz Value buffer size in kilobytes default=128 Comment/Description 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. which you will configure in this section. enable_fabric_aux0. param fcTach enable_fabric_aux0=0 on a Celerra NS-Series system. param fcTach linx_speed_aux0=0x2000 sets the tape backup link speed to accommodate a 2 Gb FC-AL interface. configures the tape backup port for an FC-AL environment. param fcTach linx_speed_aux0=0x4000 sets the tape backup link speed to accommodate an LC optical 1 Gb interface. For more information on other Celerra Network Server parameters. and linx_speed_aux0 parameters is required for NS series Celerra Network Servers. 3. Use this procedure to define parameters for NDMP-Host Data Movers. you do not need to configure the ntape or nbuf parameters. Contact EMC Customer Support for more information. • In Celerra Network Server Version 5. 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. you also need to set required parameters (step 3) for the Data Mover without an attached tape drive. Example: To set the buffer size on server_2 to 256. Where: <x> = slot number of the Data Mover attached to the tape device Note: In a Data Mover-to-Data Mover three-way configuration.3 or later. Notes: • The procedure that follows is required for NS series Celerra Network Servers. To configure the bufsz parameter. Example: /nas/server/slot_2/param contains the server_2 configuration parameters. use the following format. Open the file /nas/server/slot_<x>/param with a text editor. Step 1. type: param NDMP bufsz=256 Configuring NDMP Backups with Celerra and BakBone NetVault Version 5.3 23 of 78 . The nbuf parameter has been removed altogether.! CAUTION ! Do not change other lines in the parameter file without a thorough knowledge of the potential effects on the system. The default ntape value is now set to 4. which is sufficient for performing backups with one through four attached tape drives. 2. Action Log in to the Control Station. 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. In addition to the bufsz parameter. If you are performing a Data Mover-to-Data Mover three-way backup. You will reboot the Data Mover as part of the next procedure. Action This step is required only if you are configuring an NS series Celerra Network Server. Proceed to Setting Up the TLU on page 29.3 Configuring NDMP Backups with Celerra and BakBone NetVault . For example. the buffer size is 256. the environment is switched fabric. 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. Note: You do not need to reboot the Data Mover that attaches to tape drives. 24 of 78 Version 5. Example: To reboot server_2.Step 4. add these parameters: param fcTach enable_fabric_aux0=<paramvalue> Where: <paramvalue> = type of Fibre Channel environment (0=FC-AL. Optional. and the link speed is LC optical 1 Gb: param NDMP bufsz=256 param fcTach enable_fabric_aux0=1 param fcTach linx_speed_aux0=0x4000 5. refer to Table 4 on page 22. The default dialect is UTF-8. slot_2/param affects server_2. Close and save the file. 8. 7. Configure the Data Mover for international character sets. Setting Up the TLU on page 29. For more information on these parameters. To change the dialect. type: $ server_cpu server_2 -reboot -monitor now 6. refer to Configuring Data Movers for International Character Sets on page 25. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. When restoring. you must restore the entire directory in which the file resides. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Example: param NDMP dialect=big5 This section explains how to specify a dialect in the Celerra Network Server. you cannot perform a single-file restore on a file that contains an invalid (inode_<number>) filename. This applies only when the conversion dialect you want to use is a non-Latin1 dialect. The filename must then be converted. You may need to specify a dialect when: ◆ Your backup software does not support Unicode. Table 5 dialect and convDialect Parameters Configuring Data Movers Setting Up the TLU Module NDMP Parameter convDialect Value dialect string default=8859-1 Comment/Description You must set the conversion dialect when you restore an ASCII-mode Data Mover image to a Data Mover that has Internationalization turned on. and a backup is done with Unicode enabled on 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.3 25 of 78 . then an entry in the server log is created. Note: During a backup. an entry in the server log is created. if a file was created using a character that does not appear in the code page’s character set. such as big5. Note: The default value (null) means that UTF8 is used. For example. refer to the Celerra Network Server Parameters Guide. or if an NDMP dialect does not match the dialect used to create the file. if a file is found that the translation configuration file cannot translate.Configuring Data Movers for International Character Sets Table 5 shows the NDMP convDialect and dialect parameters and their values. This applies when Celerra operates in Internationalization mode. ◆ For more information on support and behavior of international character sets with the Celerra Network Server. For more information on other Celerra parameters. Example: param NDMP convDialect=big5 Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software NDMP dialect dialect string default=“ ” (UTF-8) Sets the dialect on the Data Mover to match the dialect of the Data Mover clients. 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. To restore the file. Close and save the file. and the Celerra Network Server is in internationalization mode: <paramvalue> = the dialect used on the ASCII mode Data Mover 3. Contact EMC Customer Support for more information. Use this procedure to set the dialect. 26 of 78 Version 5. Step 1. 2. For more information about implementing international character sets. 4. 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. Where: <x> = slot number of the Data Mover Example: /nas/server/slot_2/param contains the server_2 configuration parameters. After setting all parameters. reboot the Data Mover. and your backup software vendor’s documentation on this subject.3 Configuring NDMP Backups with Celerra and BakBone NetVault .! CAUTION ! Do not change other lines in the parameter file without a thorough knowledge of the potential effects on the system. refer to the Using International Character Sets with Celerra technical module. Action Open the file /nas/server/slot_<x>/param with a text editor. 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. Where: <x> = slot number of the Data Mover 3.Overriding the NDMP Version Table 6 shows the NDMP maxProtocolVersion parameter and its values. This parameter setting overrides the autonegotiation.3 27 of 78 . 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. However. The default value is 4. some servers and NDMP devices autonegotiate to use the latest NDMP version supported by both the server and NDMP devices. type: param NDMP maxProtocolVersion=3 Note: If the line appears and indicates a different NDMP version. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra By default. Autonegotiation between Celerra and the NDMP client determines the highest NDMP version used. Open the file /nas/server/slot_<x>/param with a text editor. to isolate NDMP issues by determining whether they occur with different versions. 2. edit the line and add the NDMP version you want to specify. Action Log in to the Control Station. Step 1. Example: To set the maximum NDMP version to 3. refer to Celerra Network Server Parameters Guide. Example: param NDMP maxProtocolVersion=3 Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software ! CAUTION ! Do not change other lines in the parameter file without a thorough knowledge of the potential effects on the system. Use this procedure to override the NDMP version. Contact EMC Customer Support for more information. For more information on other Celerra parameters. EMC recommends using this default setting. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. for example. Table 6 maxProtocolVersion Parameter Configuring Data Movers Setting Up the TLU Module NDMP Parameter maxProtoc olVersion Value 1–4 default=4 Comment/Description Sets the maximum NDMP version that can be used. Overriding the NDMP version can be a useful troubleshooting tool. you can override the automatic NDMP-version selection by specifying the latest NDMP version that can be used. Action Close and save the files.Step 4. 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 28 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone NetVault . 5. After setting all parameters. 3. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Instructions on how to install a MIA in an NS series Celerra are documented in individual setup instructions provided with each system. Configuring Data Movers Recording TLU Information The Celerra Network Server addresses a TLU device component as follows: <SCSI_controller> <SCSI_ID> <SCSI_LUN> Where: <SCSI_controller> = chain number of the controller <SCSI_ID> = SCSI ID (target) of the controller <SCSI_LUN> = logical unit number (LUN) of the controller Note: For backups with a NS-Series Celerra Network Server. Step 1. which you need when configuring your backup software. 5. Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software Use this procedure to connect the Data Movers to the TLU via SCSI.0. type: $ server_cpu server_2 -reboot -monitor now The output is similar to the following: server_2: reboot in progress 0. halt each Data Mover to be connected to the TLU and confirm that it has been halted.3. Action From the Control Station.4 done 4. Restart each Data Mover connected to the TLU and confirm that it has restarted using this command syntax: $ server_cpu <movername> -reboot -monitor now Where: <movername> = name of the specified Data Mover Example: To restart server_2. a media interface adapter (MIA) adapts the Fibre Channel AUX-0 port from an HSSDC copper interface to an LC optical (1 Gb) interface.3 29 of 78 . Turn on the TLU and verify that it is online. Run /nas/sbin/getreason and make sure the status is powered off. Refer to Data Mover-to-TLU Cabling Examples on page 13 for more information. type: $ server_cpu server_2 -halt -monitor now Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra 2. Cable each Data Mover to the TLU.Setting Up the TLU This section includes the steps for retrieving and recording device names. Use this command syntax: $ server_cpu <movername> -halt -monitor now Where: <movername> = name of the specified Data Mover Example: To halt the Data Mover running on server_2. and to record device names. Perform this procedure for each Data Mover attached to the TLU. 30 of 78 Version 5. Use this command syntax: $ server_devconfig <movername> -create -scsi -nondisks Where: <movername> = name of the specified Data Mover. use this command syntax: $ server_devconfig <movername> -list -scsi -nondisks Where: <movername> = name of the specified Data Mover For example. You will need to record this information in step 8.3 Configuring NDMP Backups with Celerra and BakBone NetVault . Use this command syntax: $ server_devconfig <movername> -probe -scsi -nondisks Where: <movername> = name of the specified Data Mover For example. verify that the Data Mover can recognize its TLU device. To list the devices and their addresses. You will need the device names when you configure your backup software. to confirm that server_2 can recognize its TLU devices. which follows this procedure. Record the device name information as shown in Table 7. List the device addresses. type: $ server_devconfig server_2 -probe -scsi -nondisks 7. 10.Step 6. Example: $ server_devconfig server_2 -create -scsi -nondisks 8. to list the devices for server_2. Action After the Data Mover has restarted. Save the Data Mover’s TLU devices to the Celerra Network Server database. type: $ server_devconfig server_2 -list -scsi -nondisks The output will look similar to the following: server_2 : scsi device table name addr type jbox1 c1t0l0 jbox tape2 c1t4l0 tape tape3 c1t5l0 tape info ATL P1000 62200501.21 QUANTUM DLT7000 245Fq_ QUANTUM DLT7000 245Fq_ 9. the default compression setting for the tape drive is used. target 5. LUN 0 Resulting Device Name C1T0L0 C1T4L0 C1T5L0 Device Component Robot Tape Drive 1 Tape Drive 2 Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. When no prefix is specified. LUN 0 chain 1. target 4. target 0. EMC recommends prefixing the Celerra Network Server device name with c in your backup software. When you configure a stand-alone tape drive in your backup software. For example. Table 7 Sample Device Name Information Data Mover server_x server_y server_z TLU SCSI Port chain 1. to use tape compression for the device C1T0L0. This ensures that tape compression is used during a backup. you can add a c or u prefix to the Celerra Network Server device name to specify whether tape compression is used. LUN 0 chain 1. prefix the device name with u. enter cC1T0L0 as the device name. Note: When configuring stand-alone tape drives. to turn off compression. prefix the device name with c. You will need this information when you configure your backup software.Table 7 shows an example of the configuration information you should record. To turn on tape compression.3 31 of 78 . Type the root password when prompted. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Step 1. the username and password must match the username and password in the NIS database. Action To assign a user account name and password to one or more Data Movers. Therefore.3 Configuring NDMP Backups with Celerra and BakBone NetVault . If you are using NIS. With NIS Assigning Data Movers a Username and Password Setting Environment Variables For Network Information Service (NIS) installations. 32 of 78 Version 5. use this procedure to assign a user account name and password to the NDMP-Host Data Movers. log in to the Celerra Network Server Control Station as nasadmin and switch user to root by typing: $ su Note: The su. Without NIS If you do not have NIS. You must use the su command. Configuring Data Movers Setting Up the TLU Note: The only username recognized by the Celerra Network Server is ndmp.command will fail. enter the following into the NIS database: ◆ ◆ ndmp as the user ID Same password to be entered when you configure your backup software Configuring Your Backup Software Note: NIS must be enabled on every NDMP-Host Data Mover. 2. 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.Assigning Data Movers a Username and Password NDMP configuration for your backup software and Celerra Network Server requires that you set a trusted username and password for each NDMP-Host Data Mover. 2. use the appropriate command syntax. use the appropriate command syntax. passwords have a sixcharacter minimum and an eight-character maximum Output: Creating new user ndmp User ID: mandatory field Group ID: mandatory field Comment: optional field Home directory: optional field Shell: optional field Changing password for user ndmp New password: same password to be configured in NDMP backup software (minimum 6 characters. Note: The Celerra Network Server accesses a Data Mover by its internal name (movername). which is server_2 in the sample output. maximum 8) Retype new password: server_2 : done In the output. Action From /nas/sbin/. 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. type: # server_user ALL -add -md5 -password ndmp Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Text method example: # server_user server_2 -add -password ndmp MD5 encryption method example: # server_user server_2 -add -md5 -password ndmp 4.Step 3. To assign the same user account and password to all Data Movers in the Celerra Network Server cabinet. passwords have a sixcharacter minimum and an eight-character maximum Example: # server_user ALL -add -password ndmp To use the MD5 password encryption method.3 33 of 78 . and 3 for each NDMP-Host Data Mover. the two mandatory fields. User ID (UID) and Group ID (GID). from /nas/sbin/. 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. Repeat steps 1. are integers. from nas/sbin/. Setting Environment Variables Table 8 shows environment variables supported by the Celerra Network Server. For more information. LEVEL is ignored. the Celerra backs up only offline attributes. refer to Backup Levels with Celerra and NDMP on page 35.3 Configuring NDMP Backups with Celerra and BakBone NetVault . This variable applies only when using Distributed HSM. as well as attributes. Note: This variable works in conjunction with BASE_DATE. Default Value N/A Description Incremental count and date/time of previous backup operation. Note: If you are backing up NT attributes. 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. For more information. 34 of 78 Version 5. When BASE_DATE is specified. Configuring Data Movers Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software Table 8 Environment Variables Variable BASE_DATE Possible Values Obtained from the NDMP data server for the previous backup operation or set to 0 (zero) for a full backup. y/n N/A EMC_OFFLINE DATA n By default. Yes specifies that Celerra back up data. as backup vendors use and implement variables differently. refer to Backup Levels with Celerra and NDMP on page 35. Refer to the Configuring DHSM on Celerra technical module for more information. Note: This variable works in conjunction with DUMP_DATE. Check your backup vendor’s documentation for more information about environment variable requirements. be sure that HIST=y and OPTIONS=NT. Incremental count and date/time of current backup operation. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra 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. FILESYSTEM <pathname> N/A The device or file system to be backed up. This must be set to y before you perform a backup to use direct access restore (DAR) when recovering files. In a token-based backup. rather than the data server (Data Mover).3 35 of 78 . refer to the Using Celerra Replicator technical module. PREFIX can be used in place of FILESYSTEM for backward compatibility. maintains the database of backup time stamps. The DUMP_DATE environment variable specifies the dump-date token for the current backup operation. Specifies an NDMP volume-level copy to tape. Either DUMP_DATE obtains it from the NDMP data server or the NDMP client sets it to zero to request a full backup. Note: You must use a read-only file system for a volume-level copy. which are used to identify files that should be included in incremental backups. The NDMP client never computes the value of BASE_DATE. PREFIX N/A TYPE tar or dump N/A VLC y/ n n Backup Levels with Celerra and NDMP A token-based incremental backup uses the BASE_DATE and DUMP_DATE environment variables to invoke full and incremental backups. LEVEL 0–10 0 OPTION NT LK AT MI/MD/MM <pathname> NT for tar and dump Saves NT attributes. refer to Backup Levels with Celerra and NDMP on page 35. the NDMP client should retrieve the DUMP_DATE environment variable. 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. For more information on backup levels. It retrieves this variable Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Follows symbolic links. The data type. For information on replicating data. At the end of a successful backup operation. Preserves access time in archive mode. Note: Dump format does not cross file system boundaries. Dump level.Table 8 Environment Variables (Continued) Variable HIST Possible Values y/n Default Value n Description Determines whether a file history is created. Restores collision policy for localization. the NDMP client. 36 of 78 Version 5. NDMP defines 0–9 for dump levels. It backs up all files modified since the most recent backup.3 Configuring NDMP Backups with Celerra and BakBone NetVault . which can be a level 10 or lower. For incremental-backup levels 1–9. DUMP_DATE is returned only if BASE_DATE was previously specified by the NDMP client as part of the backup environment. the LEVEL environment is ignored. which allows any number of incremental backups. with level 0 being a full backup. if no level 10 backup was run previously.by issuing an NDMP_DATA_GET_ENV request while the NDMP data server is in a halted state. When BASE_DATE is specified. Celerra NDMP supports level 10. only changes since the next available lower-level incremental backup or since a full backup are copied. Without a prefix. only full backups are supported with BakBone NetVault and Celerra.3 37 of 78 . Configuring Your Backup Software ◆ When configuring stand-alone tape drives in your backup software. Configuring Data Movers Setting Up the TLU Guidelines The following guidelines apply to your backup software configuration: ◆ Assigning Data Movers a Username and Password Setting Environment Variables You must configure Data Mover access from your backup software before you can carry out any operations. Currently. This ensures that tape compression is used during a backup. Refer to Setting Up the TLU on page 29 for information on determining Celerra Network Server device names. Refer to your backup software vendor’s documentation for more information. to use tape compression for the device C1T0L0. 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. EMC recommends prefixing the Celerra Network Server device name with c. A list of documents appears in Related Information on page 74. 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. For example.Configuring Your Backup Software Perform the steps in this section from your backup software. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. These procedures provide guidelines for configuring your backup software with the Celerra Network Server. enter cC1T0L0 as the device name. refer to the documents listed in Related Information on page 74. the default compression setting for the tape device is used. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra ◆ For more information on your third-party software. In your backup software. you must know the cabling configurations between the NDMP-Host Data Movers and the tape drives. which was qualified with the Celerra Network Server. The procedures in this section are based on NetVault Version 7.cfg • A new emc-celerra-dump-backup. Enter the required information as follows: Name — The name of the NDMP-Host Data Mover. Step 1. A second dialog box appears. Right-click the NDMP APM and select Add Server to open the initial NDMP Server dialog box. Add an NDMP Server.0. 3. skip to step 3. To access the most up-to-date patch and qualification information. Account — The username. Configuring Your Backup Software Action Ensure that version 5. which you must set as 10000. This string should not exceed eight characters and must match the password you set for the NDMP-Host Data Mover.3 Configuring NDMP Backups with Celerra and BakBone NetVault .srn file For information on installing these files. refer to EMC NAS Interoperability Matrix on page 12. Configuring Data Movers Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables This section describes how to configure your BakBone NetVault software for NDMP backups with the Celerra Network Server. This is the only username recognized by the Celerra NDMP-Host Data Mover. To perform the configuration steps in this section. 6. 5. 38 of 78 Version 5.Configuration Steps The steps in this section assume that the robot device is directly attached to the NDMP-Host Data Mover. For a list of qualified APM versions. Password — Password for the username account. Note: For drive index information. separated by commas. Address(es) — One or more IP addresses to the NDMP-Host Data Mover. refer to the EMC NAS Interoperability Matrix. 4.3 or higher of the NDMP APM is installed on your client running the NetVault backup software. Task 1: Add an NDMP Server Use this procedure to add an NDMP Server. You perform these steps at the backup host. If you are running NDMP APM Version 5. refer to the TLU manufacturer’s documentation. which should be ndmp. If you are running NDMP APM Version 5.3. Refer to the NetVault documentation for information on installing the NDMP APM. you must install the following files on your NDMP client: • The NDMP configuration file ndmpversions. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra 2. Click OK. refer to your NetVault documentation. Port — NDMP server port number. Open the Backup window by clicking the Backup button on the toolbar or by selecting the Operations Backup command.4 or higher. Refer to Table 7 on page 31 and Setting Up the TLU on page 29 for more information. Separate multiple paths for multiple nodes with commas. 8. For example. Action Enter the required information as follows: Name — The name you entered in the previous window. target. This should include chain. target. Click OK. which should be set to 10000. Password — Password for the username account. Tape Drive(s) — The exact path to the device for any locally attached tape drive. You cannot edit this value. Address(es) — The addresses you entered in the previous window appears. This is the only username recognized by the Celerra NDMP-Host Data Mover.3 39 of 78 . which should be ndmp. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. This should include chain. Separate multiple paths for multiple nodes with commas. C1T0L0.Step 7. Arm(s) — The exact path to the device node for any locally attached tape drive. Account — The username. Refer to Table 7 on page 31 and Setting Up the TLU on page 29 for more information. 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. C1T0L0. LUN numbers. LUN numbers. Port — NDMP server port number. Edit this value as necessary. For example. Total shared memory size also depends on the operating system you are running. select the Scan clients for remote/shared drives checkbox. 40 of 78 Version 5. which you can edit. Configuring Your Backup Software 2. refer to your BakBone NetVault documentation. NetVault searches for a library with serialization capability. Media Block Size — Increasing the Media Block Size may increase the backup performance on various device types. Assigning Data Movers a Username and Password Setting Environment Variables Step 1. Increasing this value will optimize performance. To add a library in a SAN environment where the drives can be seen by many clients. if memory permits. you must also increase the shared memory setting. NetVault automatically scans the SCSI bus on all NetVault clients and the server. After you add the NDMP Server. If it finds one.Task 2: Using the Automatic Device Configuration NetVault 7. Optional.0 will automatically locate devices on the network. To set default performance options. On the Add Library window. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra 5. the Name field displays the library name and path. The shared memory value must be equal to at least four times the Media Block Size plus 1 Kb. which describes how to recognize and configure a device through the NetVault wizard. complete the procedure in this section. 7. Note: To manually recognize and configure devices. Use caution when setting block and shared memory size.3 Configuring NDMP Backups with Celerra and BakBone NetVault . 4. Configure performance options as follows: Amount of memory to assign to transfer buffers (Kb)— The default. To autoconfigure the device. if desired. Notes: If you increase the Media block size. 3. select the Configure Performance Options checkbox. a Device Configuration Wizard launches. This launches another window after you click Next. is equal to eight buffers of 32 Kb plus 1 Kb. Configuring Data Movers Setting Up the TLU Use this procedure to recognize and configure a device through the NetVault wizard. Action Recognize a device. Launch NetVault and click the Device Management button (or select Device Management from the Administration menu. select Yes. Click Next. 257. 6. This launches another window after you click Next. From the Add Library window. Action Optional. a.Step 8. In the Automatic Device Configuration window.3 41 of 78 . and then click Finish. Select Clients Window — Select any or all clients that may have a device attached. select Scan clients for remote/ shared devices to rescan the bus for devices. Click Next. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. b. Click Next. If you do not rescan. NetVault scans the selected clients and automatically adds any devices it finds. you see a window with the following text: Devices added successfully. 9. Rescan for devices. the devices previously detected and stored in cache are used. Once NetVault has scanned and added the devices. complete the following: Re-scan clients for devices — Select to force a rescan for devices. 10. Backing Up a VDM File System with NDMP A Virtual Data Mover (VDM) is a Celerra Network Server software feature that enables you to administratively separate CIFS servers and their associated resources. 42 of 78 Version 5. To retrieve the full path. Step 1. when you use NDMP to back up a VDM-configured file system. and allow the movement of CIFS servers from Data Mover to Data Mover. For more information on VDM. into virtual containers. In your NDMP backup software. Configuring Your Backup Software Configuring Data Movers Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables Action To retrieve the full mount path of a file system.rw Note: /root_vdm_1 in this example indicates that the file system is a VDM-configured file system. In a CIFS environment.perm. These virtual containers allow administrative separation between groups of CIFS servers. enable replication of CIFS environments. Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra 2. 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 path Example: $ server_mount server_2 | grep ufs1 Output: ufs1 on /root_vdm_1/ufs1 uxfs. 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. When using NDMP to back up this file system. you must specify the full mount path of the file system.3 Configuring NDMP Backups with Celerra and BakBone NetVault . The procedure in this section explains only the NDMP-specific guideline for VDM. you would enter in your backup software /root_vdm_1/ufs1 as the full path. use the server_mount command. like file systems. enter the pathname that was revealed in step 1. refer to the Configuring Virtual Data Movers for Celerra technical module. For more information on all Celerra Network Server parameters. which describes the commands you use to view details on and dynamically modify parameters that affect backup performance. Viewing Parameter Information on page 45 Modifying Parameters on page 48 Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. This technical module describes only the command-line procedures. Action For a particular Data Mover. and how to monitor backup performance statistics.Managing NDMP Backups on Celerra This section describes how to view and dynamically modify NDMP backup parameters. Setting Up the TLU ◆ Assigning Data Movers a Username and Password Setting Environment Variables Viewing and Modifying Parameters You can view and dynamically modify performance-related backup parameters using the server_param command or through Celerra Manager. view the tunable backup parameters and their values.3 43 of 78 . which describes the commands you use to view detailed backup and restore performance statistics. Viewing Backup Statistics on page 52. Modify the value of a tunable backup parameter. Refer to the online help for information on using Celerra Manager to modify parameter values. This section includes the following tasks. refer to Celerra Network Server Parameters Guide. It includes: Configuring Data Movers ◆ Viewing and Modifying Parameters. Configuring Your Backup Software Procedure Viewing Backup Parameters on page 44 Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra View information on a specified parameter or view information on all tunable backup parameters for a specified Data Mover. type: $ server_param server_2 -facility PAX -list Assigning Data Movers a Username and Password Setting Environment Variables Output name paxWriteBuff paxStatBuff nFTSThreads nThread nPrefetch nRestore facility PAX PAX PAX PAX PAX PAX default 64 128 8 64 8 16 current 128 128 8 16 8 16 configured 30 Configuring Your Backup Software Notes Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Note: Parameter and facility names are case-sensitive. 44 of 78 Version 5. to view a list of PAX parameters on server_2. the parameter change requires user action. use this command syntax: $ server_param <movername> -facility <facility_name> -list Setting Up the TLU Where: <movername> = name of the specified Data Mover <facility_name> = name of the facility to which the parameter belongs Example: For example. which you have not yet taken. Where: name = name of the parameter facility = facility to which the parameter belongs default = default value for the parameter current = value set on the Data Mover configured = value set through the server_param command Note: The configured and current values can differ when: — you use the server_param command to configure the value of a parameter (different from the default). and — to take effect. Configuring Data Movers Action To view parameters and their values.Viewing Backup Parameters Use this command to view tunable backup parameters and their values.3 Configuring NDMP Backups with Celerra and BakBone NetVault . to view detailed information on the paxWriteBuff parameter. type: $ server_param server_2 -facility PAX -info paxWriteBuff Assigning Data Movers a Username and Password Setting Environment Variables Configuring Your Backup Software Output name facility_name default_value current_value configured_value user_action change_effective range description = = = = = = = = = paxWriteBuff PAX 64 128 128 none immediate (1. Refer to Parameter Summary on page 49 for parameter descriptions.Viewing Parameter Information Use this procedure to view details on a specific parameter. default. including current. 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 view Example: For server_2. The output in this example shows that the paxWriteBuff parameter value has been increased from the default value to 128.2048) Number of buffers in tape write queue per backup session Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Notes Note: Parameter and facility names are case-sensitive.3 45 of 78 . Where: facility_name = facility to which the parameter belongs default_value = value set as the default current_value = value set on the Data Mover configured_value = value configured with the server_param command user_action = action necessary for the parameter change to take effect change_effective = when the parameter change takes effect range = range of possible values description = refer to Parameter Summary on page 49 for parameter descriptions Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Action Setting Up the TLU Configuring Data Movers To view detailed information on a specific parameter. and possible values. refer to the previous example. server_2 : name facility_name default_value current_value configured_value user_action change_effective range description = = = = = = = = = paxWriteBuff PAX 64 64 64 none immediate (1.1024) Number of buffers in tape write queue per backup session paxStatBuff PAX 128 128 none immediate (1.To view information on all parameters for a particular Data Mover or all Data Movers. 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 belongs Example: $ server_param server_2 -facility PAX -info -all Output Note: For an explanation of the categories displayed in this output.2048) Number of buffers in stat queue per backup session nRestore PAX 16 30 30 none immediate (1.64) Number of worker threads per restore session name facility_name default_value current_value configured_value user_action change_effective range description = = = = = = = = = name facility_name default_value current_value configured_value user_action change_effective range description = = = = = = = = = 46 of 78 Version 5. Action To view all parameters for a particular Data Mover.3 Configuring NDMP Backups with Celerra and BakBone NetVault . use this command syntax. 32) Number of tape records prefetched per worker thread Configuring NDMP Backups with Celerra and BakBone NetVault Version 5.Output name facility_name default_value current_value configured_value user_action change_effective range description name facility_name default_value current_value configured_value user_action change_effective range description name facility_name default_value current_value configured_value user_action change_effective range description = = = = = = = = = = = = = = = = = = = = = = = = = = = nFTSThreads PAX 8 8 8 none immediate (1.128) Number of worker threads per backup session nPrefetch PAX 8 8 8 none immediate (1.3 47 of 78 .256) Number of FTS threads per backup session nThread PAX 64 32 32 none immediate (1. Configuring Your Backup Software Action To modify a parameter. type: $ server_param server_2 -facility PAX -modify paxWriteBuff -value 128 Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Output server_2 : done Notes Parameter and facility names are case-sensitive. Refer to Parameter Summary on page 49 for parameter descriptions. 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. ! Setting Up the TLU Assigning Data Movers a Username and Password Setting Environment Variables ◆ Use this command 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 parameter Example: For example. 48 of 78 Version 5. more threads and data blocks increase the amount of Data Mover memory dedicated to the backup and restore processes. to set the paxWriteBuff parameter to 128. Configuring Data Movers ◆ ! CAUTIONS Parameters allow you to increase the number of threads and data blocks used during the backup and restore processes.Modifying Parameters This section describes how to modify a parameter value. However.3 Configuring NDMP Backups with Celerra and BakBone NetVault . Table 9 includes the parameters you can modify with the server_param command or through Celerra Manager.3 49 of 78 . The exact prefetch amount = nPrefetch times <tape_block_size> Where: <tape_block_size> = a value determined by the backup software vendor. For a complete list of Celerra Network Server parameters. Example: param PAX nFTSThreads=128 PAX Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra nPrefetch 1–32 default=8 1–8 default=8 Specifies the amount of data each backup thread prefetches from disk before finishing the file read and writing data to tape. but it also increases Data Mover memory use. Increasing this value allows each backup thread to read more data. Example: param PAX nPrefetch=16 PAX nRestore 1–64 default=16 1–32 default=16 Specifies the number of restore threads per restore job. Example: param PAX nRestore=128 Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. as described in Configuring Data Movers on page 21. Most backup software vendors use a value close to 64 KB as the tape block size. (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. refer to Celerra Network Server Parameters Guide.Parameter Summary Table 9 and Table 10 on page 51 describe performance-related parameters. Table 9 Assigning Data Movers a Username and Password Setting Environment Variables Configuring Data Movers Setting Up the TLU Tunable Parameters: Summary Value Range Facility Parameter 510 Data Movers & Higher 1–256 default=8 507 Data Movers & Lower 1–256 default=8 Comment/Description PAX Configuring Your Backup Software nFTSThreads Specifies the number of threads for a single backup job. More threads decrease the likelihood that the NASA thread will be a bottleneck. More threads can increase the speed with which data is restored. Example: param PAX nThread=64 PAX paxStatBuff 1–2048 default=128 1–2048 default=128 Specifies the number of buffers between the threads that send and receive metadata (NASA) and read data from disk (NASS). More buffers can enhance tape streaming. More buffers can increase the speed with which metadata is provided.Table 9 Tunable Parameters: Summary (Continued) Value Range Facility Parameter 510 Data Movers & Higher 1–128 default=64 507 Data Movers & Lower 1–64 default=64 Comment/Description PAX nThread Specifies the number of backup threads. Example: param PAX paxWriteBuff=640 50 of 78 Version 5. Example: param PAX paxStatBuff=1024 PAX paxWriteBuff 1–1024 default=64 1–64 default=64 Specifies the number of buffers between the threads that read file data (NASA) and write data to tape (NASW). Increasing the number of backup threads could increase the speed with which data is retrieved from disk.3 Configuring NDMP Backups with Celerra and BakBone NetVault . PAX writeToTape = 0 specifies that the backup data be discarded. PAX writeToTape 0 or 1 (default) Determines whether the backup writes to tape. and therefore increase the restore speed. Specifying 0 allows you to test the backup speed while eliminating tape-drive speed as a performance factor. determines whether the backup writes to a file. Example: param PAX paxReadBuff=16 Note: More buffers increase the amount of Data Mover memory dedicated to the restore process. PAX writeToArch = 0 specifies that server_archive discard the data without writing to a file. Table 10 Nontunable Parameters: Summary Facility PAX Parameter paxReadBuff Value Range 16–512 default=64 Comment/Description Specifies the number of buffers between the threads that read data from tape (NASA) and restore it to disk (NASW).3 51 of 78 . PAX writeToTape = 1 specifies that the backup write to tape. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. PAX writeToArch 0 or 1 (default) For server_archive. These parameters are not tunable through the server_param command.Table 10 shows the performance-related backup parameters that require a Data Mover reboot to take effect. PAX writeToArch = 1 specifies that server_archive write to a file. More buffers can enhance tape streaming. type: $ server_pax server_2 -stats -verbose Configuring Your Backup Software Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra 52 of 78 Version 5. Action Assigning Data Movers a Username and Password Setting Environment Variables Configuring Data Movers Setting Up the TLU To view statistics on a backup session in progress.Viewing Backup Statistics This section describes how to use the server_pax command to view statistics related to your file-system data and backup performance. Use this command to view statistics on a backup session in progress.3 Configuring NDMP Backups with Celerra and BakBone NetVault . to view statistics for a backup running on server_2. which performs various functions within the multithreaded backup and restore process. The output is grouped by thread group. use this command syntax: $ server_pax <movername> -stats -verbose Where: <movername> = name of the specified Data Mover Example: For example. For more information. refer to Multithreaded Backup and Restore Design on page 16. 64KB size file processed: 64KB+1 -.NASS STATS ---** nass thid 0 ** Total file processed: 16 throughput: 2 files/sec Total nass wait nasa count: 13 Total nass wait nasa time: 236 msec Total time since last reset: 8 sec fts_build time: 0 sec getstatpool: 0 buffersputstatpool: 128 buffers ---.Output ************** SUMMARY PAX STATS **************** ---.1 WriteC=2.1GB size file processed: 1G more size file processed: 3 8 0 0 1 2 1 1 0 ---.32MB size file processed: 32MB+1 -.32KB size file processed: 32KB+1 -.NASA STATS ---** nasa thid 0 (BACKUP) ** Backup root directory: /s4fs1/adm Total bytes processed: 104937747 Total file processed: 16 throughput: 11 MB/sec average file size: 6404KB Total nasa wait nass count: 1 Total nasa wait nass time: 13 msec Total time since last reset: 8 sec Tape device name: /dev/c0t5l0 0 size file processed: 1 -.NASW STATS ---nasw00 BACKUP (in progress) Session Total Time: 00:00:08 (h:min:sec) Session Idle Time: 00:00:00 (h:min:sec) KB Tranferred: 98406 Block Size: 64512 (63 KB) Average Transfer Rate: 12 MB/Sec 42 GB/Hour Average Burst Transfer: 12 MB/Sec 42 GB/Hour Write Block Counters: 1562/0 (List/Direct) __Point-in-Time__ (over the last 10 seconds): Rate=8 MB/Sec Burst=11 MB/Sec Idle=11 msec/sec Get Pool: 63 buffers Put Pool: 0 buffers Compression Page retrieved 00:00:08 (h:min:sec) ago: ReadC=2.16KB size file processed: 16KB+1 -.3 53 of 78 .1MB size file processed: 1MB+1 -.1 Read=310692 KB Written=408327 KB Configuring NDMP Backups with Celerra and BakBone NetVault Version 5.8KB size file processed: 8KB+1 -. a reset occurs automatically after a backup completes Tape device name = target device for the backup data File size statistics = statistics on the size of files backed up since the start or reset of the current backup NASW STATS = thread responsible for getting data from the buffer pool.3 Configuring NDMP Backups with Celerra and BakBone NetVault . if value is consistently 0. then NASS may be slowing down the backup NASA STATS = thread responsible for writing file header information. then the tape may be slowing down the backup Compression rate retrieved = compression rate ReadC = read compression rate at the tape device WriteC = write compression rate at the tape device Read = amount of data read in KB Written = amount of data written in KB 54 of 78 Version 5. and writing to the buffer Backup root directory = directory being backed up Total bytes processed = bytes backed up since last reset or start of current backup Total file processed = number of files backed up since start or reset of current backup Throughput = how fast NASA processed data Average file size = average size of file for current backup Total nasa wait nass count time = number of times NASA waited for NASS Total nasa wait nass time = amount of time NASA waited for NASS Total time since last reset = amount of time since the backup statistics were reset. writing it to tape. Where: NASS STATS = thread responsible for traversing the file system and providing metadata for each directory and/or file Total file processed = total number of files and/or directories for which metadata was processed Total NASS wait NASA count = number of times NASS waited for NASA Total NASS wait NASA time = amount of time NASS waited for NASA Total time since last reset = time since the last reset. a reset occurs automatically after a backup completes fts_build time = time spent building the file system or directory tree getstatpool = if the value is consistently 0. then NASA may be slowing down the backup putstatpool = if the value is consistently 0.Notes Note: When you use verbose mode. then NASA and NASS may be slowing down the backup Put pool = number of buffers in put pool. information on file size distribution is included in the output. or sending it to a remote Data Mover Session total time = total time of current session Session idle time = idle time for current session KB transferred = total KB transferred Average transfer rate = per-second and per-hour transfer rate for current session’s data Average burst transfer = burst transfer rate in MB/s and GB/s Write block counters (List/Direct) = scatter/gather write count _Point-in-time_ (over the last 10 seconds) = information on data processed during a 10 second point-in-time Rate= transfer rate in MB/s Burst= burst transfer rate in MB/s Idle= amount of time NASW was idle in ms Get pool = number of buffers in get pool. reading file data. if value is consistently 0. type: $ server_pax server_2 -reset Output Configuring Your Backup Software server_2 : done Backing Up a VDM File System with NDMP Managing NDMP Backups on Celerra Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. use this command syntax: Assigning Data Movers a Username and Password Setting Environment Variables Configuring Data Movers Setting Up the TLU $ server_pax <movername> -reset Where: <movername> = name of the specified Data Mover Example: For example. Statistics are compiled for each backup session and automatically reset when a backup completes. to reset the statistics for a backup running on server_2.3 55 of 78 . Use this command to reset the statistics for a backup session in progress. Action To reset statistics for a backup session.Resetting Backup Statistics You can use the server_pax command to reset the statistics for a backup session in progress. timed or immediate halt or reboot of the Data Mover. -monitor now Polls and displays the boot status until completion of the halt or reboot. 56 of 78 Version 5. Command server_cpu server_devconfig server_user sevrer_log server_param server_pax Reference Table 11 Table 12 Table 13 on page 57 Table 14 on page 57 Table 15 on page 58 Table 16 on page 58 For a more detailed synopsis of the command or to view syntax conventions.3 Configuring NDMP Backups with Celerra and BakBone NetVault . Option -create Description Queries for devices and saves them into the device table database. Option -halt Description Performs a logical shutdown of a Data Mover. and displays the device configuration connected to the specified Data Mover(s). Performs a logical shutdown and restart of a Data Mover. -reboot now Table 12 server_devconfig Syntax Summary Command server_devconfig {<movername> | ALL} Description Queries. perform a -reboot. To restart a Data Mover. refer to the Celerra Network Server Command Reference Manual.Command Syntax Summary This section summarizes the syntax for commands used in this technical module. Table 11 server_cpu Syntax Summary Command server_cpu {<movername> | ALL} Description Performs an orderly. saves. Table 14 server_log Syntax Summary Command server_log {<movername> | ALL} Description Displays the log generated by the specified Data Mover. Option -add [-md5] [-password] <name> Description Adds a new user account with the login <name>. Passwords have a six-character minimum. If you are creating a user account with MD5 password encryption. Limits operations to SCSI devices. This option customizes the -create.Option -list Description Lists the device table database that has been saved on the Data Mover. This option customizes the -create.3 57 of 78 . use the -md5 option. jukeboxes. or delete a user account for a specified Data Mover. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. or -probe operation. -list. Limits operations to nondisks such as tapes. and gatekeeper devices. but does not save them into the database. modify. -probe -scsi -nondisks Table 13 server_user Syntax Summary Command server_user {<movername> | ALL} Description Allows you to create. Queries and displays devices. The -password option allows you to specify a password for the new user account. or -probe operation. -list. Specifies the facility to which the -list.Table 15 server_param Syntax Summary Command sevrer_param {<movername> | ALL} Description Allows you to modify parameter values without rebooting the Data Mover. lists the parameters you can modify with the server_param command and the parameters’ default. <facility_name> is the facility for <param_name>. Options -stats Description Displays backup and restore performance statistics for a backup session in progress. Displays backup performance statistics and filesize distribution data for a backup session in progress. For the specified facility. Displays information on the specified parameter or on all parameters for the specified facility. Allows you to modify the value of the specified <param_name> and changes the value to <new_value>. -reset -verbose 58 of 78 Version 5. -facility { <facility_name> | -all} -list -info { <param_name> | -all } -facility <facility_name> -modify <param_name> -value <new_value> Table 16 server_pax Syntax Summary Command sevrer_pax {<movername> | ALL} Description Allows you to view statistics related to your backup. current. or -modify option applies. or specifies all facilities. and configured values.3 Configuring NDMP Backups with Celerra and BakBone NetVault . info. Options -info Description Displays and describes the facilities you can modify with the server_param command. Resets the backup statistics for a backup session in progress. 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. Refer to Setting Up the TLU on page 29. and hardware are supported for NDMP backups with the Celerra Network Server. ❑ 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. You can query the EMC WebSupport database for related problem information. confirm that these paths are valid. ❑ If your backup vendor supplies utilities for checking the physical and logical paths between the backup server and the TLU devices. backup software version.com. ❑ Is the backup or restore spanning multiple tapes? If yes.emc.3 59 of 78 . For additional information about using Powerlink and resolving problems. ❑ Check the server log to ensure the parameters executed successfully. at http://powerlink. EMC’s secure extranet site. ❑ Are the necessary parameters for NDMP and PAX set on the Data Mover? Refer to Configuring Data Movers on page 21. 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.Troubleshooting NDMP Backups This section provides guidance for troubleshooting problems you may encounter running NDMP backups with the Celerra Network Server. ❑ Confirm in the EMC NAS Interoperability Matrix that your Celerra Network Server. Refer to EMC NAS Interoperability Matrix on page 12 for instructions on accessing this document. ❑ 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. Troubleshooting Checklist Review this checklist for tips on troubleshooting your NDMP backup. or report a Celerra technical problem to EMC at Powerlink™. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. refer to the Celerra Problem Resolution Roadmap technical module on the Celerra Network Server User Information CD. To read the server log for a Data Mover. obtain release notes. Reading Log Messages Each server log message has additional information that appears with the message text related to a particular event. contact the backup software vendor for further support. you should gather the following backup-specific information before reporting a problem to the EMC Support Center. For a complete list of server log messages for the Celerra Network Server.or three-way backup configuration? Server Log Messages This section includes: ◆ ◆ An explanation of the format and component parts of a server log message. Table 17 Server Log Description Log Component Date Description Displays the date. If the backup still doesn’t work correctly after you check these things. A list of NDMP and PAX server log messages. A description of the severity levels appears in Table 18.❑ Test a backup or restore using the Celerra Network Server server_archive utility. ❑ 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. Reporting a Problem Refer to the Celerra Problem Resolution Roadmap technical module on the Celerra Network Server User Information CD for additional information on troubleshooting resources and processes.3 Configuring NDMP Backups with Celerra and BakBone NetVault . or both? ❑ What model is the TLU? ❑ Does your environment have a two. refer to the Celerra Network Server Error Messages Guide. you may be able to eliminate possible problems and more easily troubleshoot issues. 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. By eliminating the NDMP protocol. Refer to the technical module Using the server_archive Utility. In addition to the general information in the Celerra Problem Resolution Roadmap. NFS files. including descriptions and possible remedies. Example 2004-01-05 60 of 78 Version 5. Table 18 Server Log Message Severity Levels Severity Level 0 1 2 3 4 Meaning Emergency Alert Critical Error Warning Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Whenever the Data Mover tries to generate a log message. refer to the Celerra Network Server Command Reference Manual. Values can be 0 through 7. Lists the part of the Celerra Network Server from which the error originates. The default severity for each module is set to 4. This technical module covers only the NDMP and PAX categories. These levels are defined in Table 18. BlockBuf count in PAX Pool: 4 Table 18 defines the severity levels associated with the server logs. If the given severity is less than or equal to the current severity level for the given module. it is ignored. with 0 indicating the highest level of importance. 3 Message text The log message. it provides the log severity level and the module name. For more information on other categories.Table 17 Server Log Description (Continued) (Continued) Log Component Time Category Description Displays the time.3 61 of 78 . the message goes to server log. Example 01:20:35 NDMP Severity level Indicates the importance of the event. otherwise. Note: The backup or restore will fail if the client does not correct the error. Answer occurred with pdi==NULL Verify that your backup software vendor is qualified with Celerra. For a complete list of server log and system log messages. refer to the Celerra Network Server Error Messages Guide. Other Considerations There is no impact to a previous restore. The Data Mover terminates the NDMP job. The backup level has been reset. but the tape is in read-only mode. it has been renamed in BackupDates.Table 18 Server Log Message Severity Levels (Continued) Severity Level 5 6 7 Meaning Notice Info Debug Server Log Messages for NDMP and PAX Table 19 shows the server log messages from the NDMP and PAX categories. and the backup fails. Refer to EMC NAS Interoperability Matrix on page 12. if applicable.bad and rebuilt <MOVER_LISTEN> before tape open Definition The /. The NDMP client sends a MOVER_LISTEN request before a TAPE_OPEN request. Corrective Action No corrective action is necessary. Verify that your backup software is qualified with Celerra.etc/BackupDates file. and backup software are qualified with Celerra. Verify that your backup software is qualified with Celerra. 62 of 78 Version 5. which saves backup dates. Table 19 Server Log Messages Server Log Messages /.3 Configuring NDMP Backups with Celerra and BakBone NetVault . <MOVER_LISTEN> with read only tape A Data Mover listen request requires a tape write. Refer to EMC NAS Interoperability Matrix on page 12. Refer to EMC NAS Interoperability Matrix on page 12. including an explanation of the message and corrective action. Verify that your hardware. drivers.etc/BackupDates corrupted. This point should not be reached with pdi==NULL. is corrupted. Refer to EMC NAS Interoperability Matrix on page 12. You will need to restart the backup. residualCount 998 Occurs during a three-way direct access restore (DAR). The forward skip record failed with the remaining records and the restore fails. The NDMP client needs to send the message in read/write mode. 3-way DAR unable to fsr 1234. Cannot reply connect An error occurred when sending a reply to CONNECT_OPEN. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. This message occurs when using NDMP version 2. The Data Mover terminates the NDMP backup job. <number> = number of buffers To change the parameter values. Corrective Action Verify that the NDMP client is using either the tar or dump backup type. Refer to EMC NAS Interoperability Matrix on page 12. The Data Mover terminates the NDMP job.3 63 of 78 . cannot send NDMP_CONNECT_OPEN reply Verify that your backup software vendor is qualified with Celerra. The Data Mover terminates the NDMP backup job.Table 19 Server Log Messages (Continued) Server Log Messages Backup type not supported: ufsdump Definition Celerra does not support the backup type specified in the NDMP backup software. Note: The backup will fail without a valid backup type specified. Celerra supports the tar and dump backup types. An error occurred when sending a reply to this message. cannot send NDMP_CONFIG_GET_TAPE_IN FO reply Verify that your backup software vendor is qualified with Celerra. Refer to EMC NAS Interoperability Matrix on page 12. BlockBuf count in PAX Pool: <number> Displays the number of buffers initialized in the pool. Refer to EMC NAS Interoperability Matrix on page 12. Other Considerations Refer to your backup software vendor’s documentation and to Setting Environment Variables on page 34. Verify that your backup software vendor is qualified with Celerra. This message reflects the PAX ReadBuff parameter. A reply to this request cannot be sent. edit the param file. Refer to Configuring Data Movers on page 21. The file <file_name> is skipped. The backup is terminated. Creation of the file BackupDates failed. • The original filename is not a valid UTF-8 name. and RECURSIVE=y/Y In your backup software. the Data interface is already deleted. The Celerra rejects this type of restore. The backup should complete successfully. 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. or invalid utf8 filename: 0x999 inode_%3456 is using for filename Definition 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. Can't have DIRECT=y/Y. create /. In the inode_%3456 error message. Corrective Action Verify that the NDMP dialect parameter specifies the correct dialect. Other Considerations Refer to Configuring Data Movers for International Character Sets on page 25. Data interface is already deleted At the time of a DATA_STOP request. error: <error message> You need to restart the backup. refer to the NDMP Backup Concepts on page 6 section. <error message> = type of error. The problem may be due to a failed backup.3 Configuring NDMP Backups with Celerra and BakBone NetVault . inode_<number> is used in place of the file name. 64 of 78 Version 5. and the restore continues. Verify that your backup software is qualified with Celerra. For more information about DAR. For information on environment variables. 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. Celerra does not support a recursive restore for a directory using DAR. I/O error Verify that your backup software is qualified with Celerra. Refer to EMC NAS Interoperability Matrix on page 12.dialect. for example. change the recursive restore setting to n.etc/ BackupDates file failed.Table 19 Server Log Messages (Continued) Server Log Messages Can't convert filename using the specified NDMP. For example. Celerra saves the filename using an invalid UTF-8 name. This file saves backup dates. refer to Setting Environment Variables on page 34 and to your backup software vendor’s documentation. No action is needed. Verify that your backup software is qualified with Celerra. only the PAUSED state is legal. NDMP_MOVER_STATE_ACTIVE Verify that your backup software vendor is qualified with Celerra. ERROR MOVER try to Listen in state <state> Refer to EMC NAS Interoperability Matrix on page 12. for example. Refer to EMC NAS Interoperability Matrix on page 12. for example. for example. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. Error in NDMP restore arguments. ERROR MOVER try to Continue in state <state> The state is illegal for a MOVER_CONTINUE command. or PAUSED. ERROR MOVER try to disconnect in state not connected In a three-way configuration. NDMP_MOVER_STATE_ACTIVE Verify that your backup software vendor is qualified with Celerra and supports three-way backups. ACTIVE. only LISTEN or PAUSED states are legal.3 65 of 78 . ERROR MOVER try to Abort in state <state> The state is illegal for aborting the MOVER interface. NDMP_MOVER_STATE_IDLE ERROR MOVER try to change record size in state <state> The state is illegal for setting record size. Refer to EMC NAS Interoperability Matrix on page 12. The NDMP client tried to stop the data interface in an invalid state. Other Considerations Refer to Setting Environment Variables on page 34 and to your backup software vendor’s documentation. <state> = mover interface state. Refer to EMC NAS Interoperability Matrix on page 12. <state> = mover interface state. for example. <state> = mover interface state. only the IDLE state is legal. the mover interface tried to disconnect while in a disconnected state. ERROR MOVER try to Set window in state <state> The state is illegal for setting window size. legal states are LISTEN.Table 19 Server Log Messages (Continued) Server Log Messages Empty archive Definition The FILESYSTEM or PREFIX NDMP environment variable is not set in the NDMP client software. Verify that your backup software vendor is qualified with Celerra. argument <argument> An error in the restore argument occurred. Corrective Action On the NDMP client. TYPE Verify in the server log that you specified the correct backup root and path. NDMP_MOVER_STATE_ACTIVE Verify that your backup software vendor is qualified with Celerra. for example. <state> = mover interface state. NDMP_MOVER_STATE_ACTIVE Verify that your backup software is qualified with Celerra. for example. Refer to EMC NAS Interoperability Matrix on page 12. Refer to EMC NAS Interoperability Matrix on page 12. <state> = mover interface state. set a value for the FILESYSTEM or PREFIX environment variable. for example. verify the spelling and the pathname. <argument> = argument name. for example. Error on checking restore name list Verify that the file and directory names you want to restore are listed correctly.3 Configuring NDMP Backups with Celerra and BakBone NetVault . for example. ERROR MOVER type LOCAL try to Read This should be a three-way read. <state> = mover interface state. NDMP_MOVER_PAUSE_EOF Confirm that your NDMP client software is qualified with Celerra. ERROR MOVER try to Stop in state <state> Reason:<reason> The NDMP client sent a message not compliant with the NDMP Version 4 specification. Refer to Setting Environment Variables on page 34 and to your backup software vendor’s documentation. Refer to your backup software vendor’s documentation. Refer to your NMDP client documentation for more information. LEVEL Verify that your backup software vendor is qualified with Celerra. 66 of 78 Version 5. then this message is informational only and you do not need to take any action. If your software is qualified. which contains the file and directory names to restore. level exceeded maximum allowed (11) An incorrect increment level for backup was specified in the NDMP client software. but the mover interface type is not three-way compliant (it is not TCP). The NDMP client sent an invalid environment variable. for example. for example. NDMP_MOVER_STATE_IDLE Corrective Action Verify that your backup software vendor is qualified with Celerra. <state> = mover interface state. only the HALTED state is legal. extractFtreeList: bad path /xyz The backup path provided does not exist. Refer to EMC NAS Interoperability Matrix on page 12. NDMP_MOVER_STATE_IDLE <reason> = reason for pause. <variable> = variable associated with the error. Verify that the backup level specified by the NDMP client is between 0 and 10.Table 19 Server Log Messages (Continued) Server Log Messages ERROR MOVER try to Stop in state <state> Definition The state is illegal for stopping the MOVER interface. Refer to EMC NAS Interoperability Matrix on page 12. Note: This path is an absolute path and is case-sensitive. Ensure that the correct path was specified and that the files specified for backup exist. Other Considerations Refer to EMC NAS Interoperability Matrix on page 12. An error occurred in the restore name list. Refer to Setting Environment Variables on page 34 and to your backup software vendor’s documentation. Error on environment variable: <variable> Verify that the environment variable listed in the log message is supported by Celerra. . Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. edit the param file. NDMP. Refer to EMC NAS Interoperability Matrix on page 12. The backup fails. The Data Mover’s buffer size parameter (bufsz) is too large. The NDMP ntape parameter is not set in the param file. which exceeds Celerra’s limit. Mover not created 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. To change the bufsz parameter value. Note: You must set this parameter for both Data Movers involved in a threeway backup. The mover interface was not created when the NDMP client requested CONFIG_GET_CONNECTION_ TYPE. and then reboot the Data Mover. Refer to Configuring Data Movers for NDMP Backups on page 22. Verify that your backup software vendor is qualified with Celerra. Refer to EMC NAS Interoperability Matrix on page 12. Set the NDMP ntape parameter in the param file. Refer to your NDMP client documentation.bufsz > 1168K in param file. length 1102 too long A pathname and filename is greater than 1024 bytes. bufsz was reset to 128K. Other Considerations Refer to EMC NAS Interoperability Matrix on page 12. NDMP Tape parameter not set. Verify that your backup software is qualified with Celerra.. ndmp already started The NDMP client attempted to start an NDMP listen thread while one was already running. The bufsz value is automatically reset to 128 KB. Verify that your backup software vendor is qualified with Celerra. name /foo/ skoilksfoiefslk. The ntape parameter specifies the number of tape drives attached to a Data Mover. The NDMP client sent an invalid command. the default value. Refer to Configuring Data Movers for NDMP Backups on page 22.3 67 of 78 . NDMP_TAPE_OPEN_REQUEST denied.Table 19 Server Log Messages (Continued) Server Log Messages Mover connection error (connectDone) Definition A connection to a three-way Data Mover accepting a TCP stream failed. and then reboot the Data Mover. Refer to EMC NAS Interoperability Matrix on page 12. Corrective Action Verify that your backup software vendor is qualified with Celerra. starting another is unnecessary. Ensure that the file and pathnames in the backup directory are less than 1024 bytes. the state is illegal for setting the window size. Also. Configure an acceptable value for the PAX parameter. Corrective Action Verify that your backup software is qualified with Celerra and supports NDMP Version 4.etc/BackupDates file failed. I/O error No action is needed. Refer to Assigning Data Movers a Username and Password on page 32. For more information on NDMPversion compatibility refer to Overriding the NDMP Version on page 27.cxx: 2210) next_head fail (filename: line#) Cannot send a message due to a network error. 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. which stores the backup run level. Other Considerations Refer to EMC NAS Interoperability Matrix on page 12. Refer to your backup software vendor’s documentation and to EMC NAS Interoperability Matrix on page 12. 512) param PAX. open /. error: <error message> An open request failed on the backup dates file.Table 19 Server Log Messages (Continued) Server Log Messages NDMP_MOVER_STATE_ACTIV E Definition For NDMP V4. Note: You must use the same password for the Celerra Data Mover and the NDMP client software. Verify the integrity of the backup media and the backup path you entered. This message could reflect a problem with the root file system. The file cannot be restored because a notification to the NDMP client to read the file header failed for a direct access restore (DAR). <error message> = type of error.<paramName> is set to 64 These two errors indicate that the value for the PAX parameter <paramName> is outside the parameter’s allowed range. param PAX. only the LISTEN and PAUSED states are legal.<paramName> 1024 out of range (4. Use the server_user command to set the NDMP password or to verify that the password is set properly. 68 of 78 Version 5. the username must be ndmp. Verify that your backup software is qualified with Celerra and that it supports DAR.Passwd The NDMP password is not set on the Celerra Network Server. for example. Verify that the network is in a good state.3 Configuring NDMP Backups with Celerra and BakBone NetVault . No password for NDMP user:ndmp Retry:3 to get NDMP user:ndmp . Pattern Not Matched: / fs/file3 (not restored) This pattern (file or directory) is not found in the archive. network error (ndmp_mover. RecBuf in NDMP Pool (count:64). Verify that the netd file includes PAX. Refer to Configuring Data Movers for NDMP Backups on page 22. edit the bufsz parameter in the param file. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. To change the buffer size. The Data Mover and NDMP client establish a connection. for example. Refer to your backup software vendor’s documentation and to EMC NAS Interoperability Matrix on page 12.nFTSThreads parameter that is too large. and is not being used by other applications. <action> = action received. PAX was not started. I/O error Verify that the file or file system exists on Celerra. NDMPMAXBUFSIZ is 128 Displays the number of buffers initiated in the pool and the maximum buffer size. an ARCHIVE or EXTRACT message is expected. The netd file resides in /nas/server/ slot_<x>/netd. Refer to Configuring Data Movers on page 21 for instructions on setting parameters.Table 19 Server Log Messages (Continued) Server Log Messages pax not started Definition At the time of the DATA_CONNECT request. LIST No particular action is necessary. Read fault on /fs/test with error: <error message> The file you are trying to back up cannot be read on Celerra. <error message> = type of error. Verify that your backup software is qualified with Celerra and that it supports three-way DAR. An internal error between NDMP and PAX occurred. slot_2 Corrective Action Verify that your backup software is qualified with Celerra. PAX. The attempt to read the file data failed. it simply uses fewer threads to perform the backup.nFTSThreads is reset to 64 This message indicates that a value has been specified for the PAX.3 69 of 78 . but not others. is in a good state. Refer to EMC NAS Interoperability Matrix on page 12. 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. The backup still succeeds. for example. for example. pax_cmd_thread expected ARCHIVE/ EXTRACT act. Refer to EMC NAS Interoperability Matrix on page 12. Other Considerations Refer to EMC NAS Interoperability Matrix on page 12 for qualification information. The value is reset and the backup continues normally. and then reboot the Data Mover. Where: <x> = slot number of the Data Mover. but received <action> Verify that your backup software is qualified with Celerra. This setting reflects the bufsz parameter. The Data Mover netd configuration file needs to include PAX. A DAR restore encountered a problem positioning the tape. TAPE_OPEN c1t2l0 fails with stat: <state> A TAPE_OPEN request failed with <state>. Verify that your backup software is qualified with Celerra. Celerra supports no more than eight tape drives per Data Mover. the Celerra encountered a problem with the directory and/or link.3 Configuring NDMP Backups with Celerra and BakBone NetVault . You may be trying to restore a failed backup. 70 of 78 Version 5. The ntape parameter exceeds the maximum value. The value specifies the number of tape drives attached to a Data Mover. You will need to restart the restore. Many factors can trigger this message. which the Celerra does not support. Verify that the network is in a good state.Table 19 Server Log Messages (Continued) Server Log Messages Request (0x702) not supported (No mover) Definition The request is not supported because the mover interface is not yet created. Device Busy Verify that no contention for the backup device exists among backup clients or Data Movers. The restore is terminated. <state> = state of the device. which is 8. Ensure you are not trying to restore to root the file system. thrdId 0 positionTape error Verify that your backup software is qualified with Celerra. Tape number > 8 in param file Change the NDMP ntape parameter value to 8 or less and reboot the Data Mover. The Data Mover encountered a problem and subsequently skipped data for the named file stream. Refer to Configuring Data Movers for NDMP Backups on page 22. for example. Refer to EMC NAS Interoperability Matrix on page 12. Refer to EMC NAS Interoperability Matrix on page 12. Verify that your backup software is qualified with Celerra. Refer to EMC NAS Interoperability Matrix on page 12. thrdId 0 error on restore file to root filesystem Permission denied to restore <file or dir> on Root fs thrdId 0 namedFileStreamSkip error in 3214 An attempt was made to restore to the root file system. Corrective Action Verify that your backup software is qualified with Celerra. rw_thr() TCP connection closed with mover PAX failed to receive a message from the TCP connection. The problem may be due to a failed backup or a corrupted tape. The problem may be due to a failed backup. thrdId 0 directory/ link error During a restore. This may cause the backup to fail. Other Considerations Refer to EMC NAS Interoperability Matrix on page 12. error: <error message> Unable to reach password data base The ndmp password is not set. for example. Celerra supports text and MD5 authorizations. Other Considerations Refer to EMC NAS Interoperability Matrix on page 12. Refer to Assigning Data Movers a Username and Password on page 32 and to your backup software documentation. <error message> = type of error. Verify that the tar or dump backup type is specified in the NDMP client software. The tape is either not opened or is not ready. Verify that the tape is in a good state. Device Error Refer to EMC NAS Interoperability Matrix on page 12. Corrective Action Verify that your backup software is qualified with Celerra. Try to tape_mtio in mover active state Unable to get position on tape (d). 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. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. The problem may be due to a failed backup. Note: The backup will fail without a valid backup type specified. Celerra supports tar and dump backup types. Refer to your NDMP client’s documentation for more information. An error occurred while reading the tape position. The NDMP client should not try to manipulate the tape drive while the Data Mover has ownership of it. Try to Stop data interface in state 3 The backup client should not stop the data interface in this state. Verify that your backup software is qualified with Celerra. The NDMP client tried to manipulate the tape drive while the Data Mover had ownership of the tape drive.3 71 of 78 . Set a password for the ndmp user. Unknown Auth type (0x8) An unknown authorization request was made.Table 19 Server Log Messages (Continued) Server Log Messages thrdId 1 mod_name error Definition The Celerra could not rename a file during a restore. Unknown BT_NDMP_BUTYPE An invalid 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. This condition causes the backup or restore to fail. Unknown procedure (8765) Unknown command 0x8888 Celerra received an unknown message from the NDMP client and terminated the NDMP backup job.3 Configuring NDMP Backups with Celerra and BakBone NetVault . The specified volume was not found. Mount the file system you want to copy as a read-only file system. Refer to the related PAX server log messages for more information on this server log condition. Celerra encountered an internal error. and to the Using the Celerra server_archive Utility technical module. refer to the Celerra Network Server Command Reference Manual. 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. Refer to the Using Celerra Replicator technical module for more information. Other Considerations For more information on the server_mt command. Refer to the Using Celerra Replicator technical module for more information. Verify that the your backup software is qualified with Celerra. VLC_FS_STATUS_NOT_FOUND <file_system> The specified <file_system> was not found. VLC_FS_STATUS_NOT_READ _ONLY For a volume-level copy. to the man pages. VLC_FS_STATUS_DEVICE_ NOT_FOUND VLC_FS_STATUS_DEVICE_ TOO_SMALL VLC_FS_STATUS_DEVICE_ TOO_LARGE Check the spelling of the volume name you specified. 72 of 78 Version 5. Refer to EMC NAS Interoperability Matrix on page 12. Correct the pathname. VLC_FS_STATUS_NOT_RAWF S <file_system> When restoring a volume-level copy. the target file system must be a raw file system (rawfs). Otherwise. Create a volume that is the same size as the original file system. verify that you entered the server_mt command correctly. an incorrect mt command was entered. and then restart backup. Restore the file system to this volume. When using server_archive. the specified file system must be mounted as a read-only file system. Refer to EMC NAS Interoperability Matrix on page 12 to verify software qualification. Corrective Action If using server_archive.Table 19 Server Log Messages (Continued) Server Log Messages unknown mt cmd 0x97 Definition An unknown tape command was received. verify that your backup software vendor is qualified with Celerra. VLC_FS_STATUS_ERROR Verify that your backup software is qualified with Celerra. The target <file_system> specified for recovery is not a raw file system. Refer to EMC NAS Interoperability Matrix on page 12 for information on Celerra qualifications. Table 19 Server Log Messages (Continued) Server Log Messages VLC_FS_STATUS_NOT_READ _ONLY VLC_FS_STATUS_NOT_READ _ONLY VLC Open error Definition 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 readonly file system to perform a volume-level copy. The specified <file_system> is not a uxfs type file system. A volumelevel copy requires that you use an uxfs file system. This file-system type is the default for Celerra. These two messages indicate that a read or write to the file system failed. Corrective Action 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. Other Considerations 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> You must back up a volumelevel 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 Write count exceeds bufsz Read count exceeds bufsz Write IO error status error: <error message> Refer to the related PAX server log messages for more information about this error condition. To change the bufsz parameter, edit the param file and reboot the Data Mover. Refer to Configuring Data Movers on page 21. 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. A write I/O error occurred. <error message> = type of error, for example, DeviceError Verify that the tape drive is in a good state. Configuring NDMP Backups with Celerra and BakBone NetVault Version 5.3 73 of 78 Related Information For more information related to the features and functionality described in this technical module, refer to: ◆ ◆ ◆ Celerra Network Server Concepts Guide Celerra Network Server Command Reference Manual and man pages Using the Celerra server_archive Utility technical module Foe general information on other EMC products publications, refer to the Celerra Network Server User Information CD, which is supplied with our Celerra Network Server and also available at Powerlink at http://powerlink.emc.com. Also refer to the following documents for your backup software: ◆ ◆ ◆ NetVault Implementation Guide for the NDMP APM NetVault Application Plugin User’s Guide NetVault 7.0 Administrator’s Guide Want to Know More? EMC Customer Education Courses are designed to help you learn how EMC storage products work together and integrate within your environment in order to maximize your entire infrastructure investment. EMC Customer Education features online, and hands-on training in state-of-the-art labs conveniently located throughout the world. EMC customer training courses are developed and delivered by EMC experts. For course information and registration, refer to EMC Powerlink, our customer and partner website on http://powerlink.emc.com. 74 of 78 Version 5.3 Configuring NDMP Backups with Celerra and BakBone NetVault Index A attributes, backup for Windows NT 34 direct access restore 10 discovering devices from Celerra 30 dynamic drive sharing defined 2 overview of 11 restrictions for 4 B backup levels, with Celerra 35 backup software configuration guidelines 37 configuring for Celerra 37 E education, on EMC products 74 environment variables 34 F facility, PAX parameters 44 failover of a Data Mover, caution 5 Fibre Channel TLU configuration 13 file restoration, overview 10 C cabling the TLU 13 Celerra Network Server backup levels with 35 configuration guidelines for 20 setting environment variables on 34 Celerra NS series media interface adapter for 20 parameters for, summary 22 port configuration with 4 setting parameters on 24 checklist for troubleshooting NDMP backups 59 command syntax summary 56 commands server_cpu, summary 56 server_devconfig, summary 56 server_log, summary 57 server_param, summary 58 server_pax, summary 58 server_user, summary 57 configuration guidelines for Celerra 20 for your backup software 37 configurations for NDMP backups dual-TLU 8 simple 6 single TLU 7 configuring Data Movers 21 roadmap for 19 your backup software 37 connecting the robot to a Data Mover 13 customer education on EMC products 74 Customer Support, reporting a problem to 60 G guidelines for configuring backup software 37 Celerra Network Server 20 I international character sets support overview 14 with dump and tar backup types 15 interoperability matrix, accessing 12 L levels of backup, with Celerra 35 M managing NDMP backups 43 MD5 password encryption, method for Celerra 33 media interface adapter, for the Celerra NS series 20 modifying parameters 48 multithreaded backup design 16 D DAR, see direct access restore Data Movers caution for connecting tape drives 5 configuring 21 failover caution 5 parameters for 21 setting a username and password for 32 devices, discovering from Celerra 30 Configuring NDMP Backups with Celerra and BakBone NetVault NASA thread group 16, 54 NASS thread group 16, 54 NASW thread group 16, 54 NDMP backups, managing 43 concepts 6 configurations 6 version, 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 N Version 5.3 75 of 78 for NDMP backups 12 Windows NT attributes. summary 56 server_devconfig command.3 Configuring NDMP Backups with Celerra and BakBone NetVault . summary 56 server_log command. overview 10 related information. on an EMC storage system 4 system requirements. for Celerra and backup software 74 reporting a problem to Customer Support 60 restoration of files. summary 58 server_pax command. viewing 52 stripe size restriction. parameters 44 performance enhancements 16 third-party software configuration guidelines 37 configuring for Celerra 37 thread groups 16. setting on a Data Mover 32 PAX facility. backing up 34 T tar backups behavior with Celerra 15 terminology definitions of 2 differences with backup software vendors 3 76 of 78 Version 5. general 4 roadmap for configuring NDMP backups 19 robotics.O overriding the NDMP version 27 P parameters adding and editing 23 configuring 21 file format 21 for international character sets 25 modifying 48 nontunable 51 tunable 49 viewing information on 44 password. 54 three-way backups heterogeneous 10 overview 9 restrictions with 4 TLU cabling 13 SCSI port. summary 57 setting a Data Mover’s username and password 32 environment variables on Celerra 34 parameters on Celerra 22 statistics. overview 10 restrictions. connecting to a Data Mover 13 U username. setting on a Data Mover 32 V viewing backup parameters 44 viewing backup statistics 52 W S SCSI TLU cabling configuration 13 server log messages component parts of 60 for NDMP and PAX 62 reading 60 severity levels for 61 server_cpu command. summary 57 server_param command. sample 31 setting up 29 TLU configurations dual TLU 8 Fibre Channel 13 simple NDMP 6 single TLU 7 troubleshooting checklist 59 R recovery. summary 58 server_user command. 3 77 of 78 .Notes Configuring NDMP Backups with Celerra and BakBone NetVault Version 5. THE INFORMATION IN THIS PUBLICATION IS PROVIDED “AS IS. Copyright © 1998–2004 EMC® Corporation. see your product release notes. Therefore. organization. EMC believes the information in this publication is accurate as of its publication date.com with your opinions of this document. Please send a message to celerradoc_comments@emc. AND SPECIFICALLY DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. The information is subject to change without notice.About This Technical Module As part of its effort to continuously improve and enhance the performance and capabilities of the Celerra Network Server product line. For the most up-to-date information on product features. EMC from time to time releases new revisions of Celerra hardware and software.” EMC CORPORATION MAKES NO REPRESENTATIONS OR WARRANTIES OF ANY KIND WITH RESPECT TO THE INFORMATION IN THIS PUBLICATION. and distribution of any EMC software described in this publication requires an applicable software license. If your Celerra system does not offer a function described in this document. copying. Comments and Suggestions About the Documentation Your suggestions will help us continue to improve the accuracy. please contact your EMC representative for a hardware upgrade or software update. 78 of 78 Version 5. and overall quality of the user publications. Use. All rights reserved. some functions described in this document may not be supported by all revisions of Celerra software or hardware presently in use.3 .