Amanda Enterprise supports backup and recovery of NDMP appliances using NDMPv4 (version 4) protocol. It does not support earlier versions of NDMP protocol. Amanda Enterprise supports Remote NDMP, Direct NDMP as well as 3-way NDMP configurations.
In Remote NDMP configurations, NDMP appliance such as Netapp Filers, Sun Unified Storage and BlueArc storage are backed up to tape changers and disk attached to the Amanda server. The backup and recovery data goes through the server. In Direct NDMP and 3-way NDMP configurations, Appliances can be backed up to a tape changer that is attached to a SAN or using iSCSI and is accessible from the appliance. The backup and recovery data is not transferred through the server. The Amanda backup server acts as a backup control program.
NDMP backup and recovery in Amanda Enterprise is implemented as an Amanda application. As a result, management of NDMP backup and recovery is identical to other applications. The Amanda disk list entries (DLEs) for NDMP can be present in a backup set that has other application DLEs. This configuration is not recommended.
The NDMP backups from an appliance can be restored to an appliance from the same vendor.
Configuring NDMP backups requires configurations steps using Zmanda Management Console and some manual steps.
The NDMP backups are always initiated from the Amanda server. The Vendor can be Netapp, BlueArc and Sun Unified Storage. The Directory must be in //<name or ip address of the filer or appliance>/<volume name>/[<directory name>] format. In the above example, 192.168.29.155 is the IP address of the filer that contains the volume that has to be backed up. The Username and Password are the user credentials for performing backup and recovery from the filer whose IP address or the name is specified as Appliance IP addr.
Compression and Encryption cannot be used for NDMP DLEs. The Data Path must be set to DirectTCP for LAN free backups.
This authentication file should be readable only by amandabackup user. An example ndmp-passfile file is shown below:
172.17.47.2 /vol/vol1/data "root" "root_password" TEXT
172.17.47.2 is the IP address of the Netapp filer. /vol/vol1/data is the DLE. root is the user on the Netapp filer used for the backup operations and password for the user is root_password. The password must not be encrypted.
$ amcheck <backup set name>
Please resolve any configuration errors found.
This procedure has to be performed for Direct NDMP and 3-way NDMP configurations.
Configuration of NDMP tape changer has to be done manually. You can create a backup to disk configuration using Zmanda Management Console Backup Where and Admin Devices page and use it as a template.
define changer ndmp-changer { tpchanger "chg-ndmp:172.17.47.2@mc0" changerfile "/etc/amanda/<backup-set-name>/disk-2-ndmp_changer.changer.conf" property "use-slots" "19-20" # skip slots 17-18, cleaning tapes property "tape-device" "0=ndmp:172.17.47.2@nrst1h" "1=ndmp:172.17.47.2@nrst0h" "2=ndmp:1 72.17.47.2@nrst2h" "3=ndmp:172.17.47.2@nrst3h" property "ndmp-username" "root" property "ndmp-password" "netapp1" property "ndmp-auth" "text" property "driveorder" "lru" }
tpchanger should be "chg-ndmp:<ip address of the netapp filer@changer-name" The changer name can be found using Netapp filer storage show mc command. In case of BlueArc storage, you can find changer name and drive name in the user interface as shown in the figure below.
use-slots property specifies the list of slots in the tape changer that can be used by the backup set.
tape-device property specifies the list of tape drives available in the changer. In the above example, three tape drives are configured for the backup set. Each tape drive configuration has the format "<drive number>=ndmp:<filer IP address>@device name". The device name can be obtained using Netapp filer command sysconfig -t. Use no rewind device file name.
ndmp-username, ndmp-password, ndmp-auth are the filer authentication information which runs the NDMP tape agent for the tape changer. In 3-way NDMP configuration, filer/appliance which manages the tape changer should have authentication information specified in this section.
tpchanger "ndmp-changer"
$ amcheck -c <backup set name>
Please resolve any configuration errors found. Configuration checks are automatically performed in Zmanda Management Console Backup What page.
Please do not try to change these configurations using Backup Where and Admin Devices page. Your configuration will get overwritten.
You can schedule backups using Zmanda Management Console Backup When page or run immediate backups for the backup set from the Backup Activate page.
The status of the backup are shown in the Monitor page. Backup reports will be available under the Report tab in the Zmanda Management Console.
This section describes how to use Amanda recovery command amrecover to perform NDMP volume/directory restoration.
amrecover> sethost localhost
200 Dump host set to localhost.
amrecover> setdisk //netapp1.company.com/vol/vol3
200 Disk set to //netapp1.company.com/vol/vol3
amrecover> ls 2010-03-03-17-22-35 MyData
2010-03-03-17-22-35 MyMusic
...
amrecover> add *
Added file /MyData
Added file /MyMusic
amrecover> extract
amrecover> setproperty directory //netapp1.company.com/vol/vol2/restored/