NDMP

It is possible to integrate NDMP backups into NetBackup's scheduling with the use of the NetBackup's NDMP agent. This enables a NetBackup media or master server to send NDMP control commands to a compatible filer and for the filer to send the data to the appropriate backup target.

 

A prerequisite before configuring NDMP within NetBackup is to have a NDMP user created on the target filer. This user must have the appropriate rights to run NDMP backups on the filer. The filer's documentation will have all the necessary steps required to create the user and assign the correct permissions.

In addition to the user creation, the  NetBackup host which will be acting as the NDMP control host must have access to port 10000 on the filer. Port 10000 is the port the NDMP service listens  on and it is this port to which NetBackup will be sending the NDMP operations, hence connectivity to it is reuqired. A simply telnet test to this port on the filer will confirm that the port is contactable

# telnet <filer_hostname> 10000 </dev/null

There are several differnent ways to perform NDMP backups :

- Local NDMP: The filer has dirct connectivity to the backup target i.e. tape drives are zoned to the filer. During a NSMP backup data will be sent directly from the filer to the backup target

 

- Remote NDMP : The filer does not have direct access to the backup target, backup data is sent from the filer to a orage unit connected to a media server

 

- Three way NDMP : The filer does not have direct access to the backup target, backup data is sent to a media server which in turn writes the data to a remote storage unit

If local NDMP is being used then the Filer must have access to the backup target which is likely to mean it is zoned to physical tape drives or to the relevant target ports on a VTL.

 

The first step within NetBackup is to add the NDMP user

 

# /usr/openv/volmgr/bin/tpconfig -add -nh <filer_hostname> -user_id <NDMP_user> -password <NDMP_password>

Confirm that the user credentials are working and communication is successful

# /usr/openv/volmgr/bin/tpconfig -verify -<filer_hostname>

Confirm that the filer can see the relevant tape drives zoned to it

# /usr/openv/volmgr/bin/tpautoconf -probe <filer_hostname>

The tape drives for the filer need to be configured on the media server which will be the NDMP control host. Running the tpautoconf -probe command will show the device paths for the tape drives. The output will print multiple devices per tape drive but only the devices ending with "a" need to be configured i.e. nrst1a , nrst2a.

 

The tapes drives can be added via the command line with the tpconfig command. The tpconfig command needs to be run on the media server which will be th NDMP control host. The following command  will add a tape drive with the following options :

-type :  density of hcart3

-path :  tape drive path  of nrst1a on the filer

-nh : the filer to which the tape drive is attached

# /usr/openv/volmgr/bin/tpconfig -add -drive -type hcart3 -path nrst1a -nh FILER1 -robot 1 -robtype TLD -robdrnum 10 -asciiname "FILER_DRIVE_1_10" -shared no -drstatus up

The tpconfig command needs to be repeated for each of the tape drives he filer has visibilty of and will use.

 

 

Once the tape drives have been added then a NDMP storage unit needs to be configured. Th.e following command will add a non multiplexed storage which is only available on demand

bpstuadd -label FILER1_STU -density hcart 3 -host MEDIASERVER -nh FILER1 -maxmpx 1 -rt tld -rn 1 -cj 1 -odo 1

The above storage unit will look like the following once added :

 

Label:                FILER1_STU
Storage Unit Type:    NDMP
Host Connection:      MEDIASERVER
Number of Drives:     1
On Demand Only:       yes
Max MPX/drive:        1
Density:              hcart3 - 1/2 Inch Cartridge 3
Robot Type/Number:    TLD / 1
Max Fragment Size:    1048576 MB
NDMP attach host:     FILER1

When working with NDMP configured tape drives via the tpconfig command the -drpath switch must be used when performing drive operations such as taking the drive offline or bringing it online.

# tpconfig -update -drpath -path nrst1a -nh FILER1 -asciiname "FILER_DRIVE_1_10" -drstatus  down

# tpconfig -update -drpath -path nrst1a -nh FILER1 -asciiname "FILER_DRIVE_1_10" -drstatus  up