Installation

The NDMP Plugin is installed along the FileDaemon. To avoid network load between the FD and the SD, please install it on the same system of a SD.

It is possible to install the NDMP Plugin on any other host, but doing so is less efficient because it will cause the data to traverse two network links – once from the NAS to the File Daemon, and a second time from the File Daemon to the Storage Daemon.

If you plan to use the SMTAPE Incremental feature, it is required to install the NetAp OnTap API on your system. See NetApp OnTAP Python API Installation for more information.

Prerequisites

The Plugin Directory option in the File Daemon resource should point to where the ndmp-fd.so plugin is installed, which usually is /opt/bacula/plugins

FileDaemon {
   Name = bacula-fd
   Plugin Directory = /opt/bacula/plugins
   ...
}

The File Daemon should have direct network access to the NAS, which can be verified using telnet, for example:

# telnet nasbox 10000
Connected to nasbox.
Escape character is '^]'.

Note

NDMP, when doing the actual backup, connects back from the filer to the host initiating the NDMP session. This may require firewalls to be configured accordingly. Using the data_port_range option, it is possible to control which TCP ports the NAS will attempt to use, allowing for more restricted firewall configuration. When the network connection is not possible, the error NDMP4_CONNECT_ERR can be issued.

Network Connections During Backup — Network Connections

The job specific configuration of the NDMP Plugin is part of the FileSet that is used and provided as options of the plugin directive.

Depending on NAS setup, the authentication method can be configured to be md5 or text.