A simple step-by-step procedure to configure Remote NDMP backup on NetBackup Enterprise Server 5.x

Article:TECH48316  |  Created: 2006-01-28  |  Updated: 2009-01-02  |  Article URL http://www.symantec.com/docs/TECH48316
Article Type
Technical Solution

Product(s)

Environment

Issue



A simple step-by-step procedure to configure Remote NDMP backup on NetBackup Enterprise Server 5.x

Solution



Remote NDMP allows data on an NDMP host to be backed up to a storage device that is connected to a NetBackup media server. This is a form of three-way backup: the NDMP host sends the backup data over the network to a storage device on a NetBackup media server, rather than using a storage device on the NDMP host itself.

Remote NDMP is supported only on Solaris and Windows NT/2000/2003 platforms.

Remote NDMP is enabled by an NDMP mover agent daemon/service running on the NetBackup media server.
A log file can be created for this agent and is located in folder <install_path>\VERITAS\NetBackup\Logs\ndmpmoveragent (Windows platforms) <install_path>/netbackup/logs/ndmpmoveragent (Solaris platform).

For the purpose of this document I have imagined the following scenario:

Master/media server running NetBackup 5.1 MP4 with the NDMP Option installed and licensed (hostname = atlantis.techsupportux.it)
NDMP host --> A filer which is being backup up using Netbackup Enterprise Server
Robot TLD(1) with five LTO2 (hcart2) tape drives, four used for non-NDMP backup and one for NDMP backup.

The configuration of Remote NDMP backup requires 5 steps:


1. Authorizing access to the NDMP Host

Before NetBackup can carry out any backup operation, it must have access to the NDMP host. To authorize this access, execute the following command on your master/media server:

<install_path>/volmgr/bin/set_ndmp_attr -auth <ndmp-host> <username>    (Solaris)
<install_path>\Volmgr\bin\set_ndmp_attr -auth <ndmp-host> <username>   (Windows)

IMPORTANT NOTE: This "ndmp-host" name is case-sensitive. Whenever this host name is used the name must be identical to the name entered here on the set_ndmp_attr command


2. Setting up NDMP authentication for the NetBackup media server

To set up remote NDMP, you must configure the NetBackup media server as an NDMP host. To do this, execute the same command specifying the media server name instead of the ndmp-host.

<install_path>/volmgr/bin/set_ndmp_attr <media_server_name> <username>              (Solaris)
<install_path>\Volmgr\bin\set_ndmp_attr -auth <media_server_name> <username>     (Windows)


3.  Configure tape drive(s) to be NDMP drive(s)
Remote NDMP cannot be configured by means of the Device Configuration wizard. When you run the wizard, all devices attached to NetBackup servers are configured as standard NetBackup devices that will not be available for remote NDMP until they are manually set up for this purpose using the Media Manager command <install_path>/volmgr/bin/tpconfig. Proceed as follows:


a. Configure the 5 tape drives in the library using the Device configuration wizard. Then run "tpconfig -d" to display the configuration:

Index DriveName              DrivePath                Type    Shared   Status
*****   *********                  **********                  ****      ******     ******
 0   HPUltrium2-DR4       /dev/rmt/3cbn   hcart2   No      UP
      TLD(1) Definition DRIVE=4
 1   HPUltrium2-DR1       /dev/rmt/0cbn   hcart2   No      UP
      TLD(1) Definition DRIVE=1
 2   HPUltrium2-DR2       /dev/rmt/1cbn   hcart2   No      UP
      TLD(1) Definition DRIVE=2
 3   HPUltrium2-DR3       /dev/rmt/2cbn   hcart2   No      UP
      TLD(1) Definition DRIVE=3
 4   HPUltrium2-DR5       /dev/rmt/4cbn   hcart2   No      UP
      TLD(1) Definition DRIVE=5

Currently defined robotics are:
 TLD(1)     robot control host = atlantis.techsupportux.it
                volume database host = atlantis.techsupportux.it


b. Choose the tape drive that will be devoted to NDMP backups and re-configure it as an NDMP tape drive. (In the example below I have picked drive HPUltrium2-DR4 at index 0)

Command syntax:  tpconfig -update -drive <index> -type <drvtype> -path <media_server_name>:<device_file>
Example: tpconfig -update -drive 0 -type hcart2 -path atlantis.techsupportux.it:/dev/rmt/3cbn


c. Verify that the configuration has been updated using tpconfig -d once again:

Index DriveName              DrivePath                 Type     Shared   Status
*****   *********                  **********                  ****      ******      ******
 0   HPUltrium2-DR4       /ndmp//dev/rmt/3cbn   hcart2   No      UP
      TLD(1) Definition DRIVE=4
 1   HPUltrium2-DR1       /dev/rmt/0cbn             hcart2   No      UP
      TLD(1) Definition DRIVE=1
 2   HPUltrium2-DR2       /dev/rmt/1cbn             hcart2   No      UP
      TLD(1) Definition DRIVE=2
 3   HPUltrium2-DR3       /dev/rmt/2cbn             hcart2   No      UP
      TLD(1) Definition DRIVE=3
 4   HPUltrium2-DR5       /dev/rmt/4cbn             hcart2   No      UP
      TLD(1) Definition DRIVE=5

Currently defined robotics are:
 TLD(1)     robot control host = atlantis.techsupportux.it
                volume database host = atlantis.techsupportux.it


IMPORTANT NOTE: Some of the drives in a robotic library can be configured for non-NDMP backups, and others can be configured for remote NDMP. Once a drive has been configured for NDMP backup, it cannot be used for non-NDMP backups.

4. Create an NDMP-type storage unit

On the Add New Storage Unit display, make sure to specify the NetBackup media server as an NDMP host.

 


5. Create an NDMP-type policy. On the New/Change Policy display, be sure to specify the storage unit created at step 4
 
 





Legacy ID



284075


Article URL http://www.symantec.com/docs/TECH48316


Terms of use for this information are found in Legal Notices