NetBackup™ NAS Administrator's Guide
- Section I. About NAS backups
- Section II. Using NAS-Data-Protection (D-NAS)
- D-NAS overview
- Pre-requisites for D-NAS configuration
- Configure D-NAS policy for NAS volumes
- Using accelerator
- Replication using D-NAS policy
- Restoring from D-NAS backups
- Troubleshooting
- Troubleshooting
- Setting the log level
- Logging directories for Linux platforms
- Logging folders for Windows platforms
- Restore from a snapshot fails with status 133
- Backup from snapshot fails with error 50
- Backup from snapshot parent job fails with error 4213: Snapshot import failed
- Backup host pool creation fails with the error "Failed to fetch host list"
- Snapshot job fails and the snapshot command does not recognize the volume name
- Accelerator enabled incremental backup of NetApp NAS volume
- Snapshot method: Auto
- Section III. Section 3
- Introduction to NetBackup for NDMP
- About NetBackup for NDMP
- About Network Data Management Protocol (NDMP)
- Types of NDMP backup
- About NDMP policies in NetBackup
- About NetBackup storage units
- About assigning tape drives to different hosts
- About the NDMP backup process
- About the NDMP restore process
- About Direct Access Recovery (DAR)
- Snapshot Client assistance
- About NDMP multiplexing
- About NDMP support for Replication Director
- Limitations of Replication Director with NDMP
- About NDMP support for NetApp clustered Data ONTAP (cDOT)
- Installation Notes for NetBackup for NDMP
- Configuring NDMP backup to NDMP-attached devices
- About configuring NDMP-attached devices
- Authorizing NetBackup access to a NAS (NDMP) host
- About access for three-way backups and remote NDMP
- About Media and Device Management configuration
- Using the Device Configuration Wizard to configure an NDMP filer
- About adding volumes
- About verifying NDMP password and robot connection
- Adding NDMP storage units
- About creating an NDMP policy
- About environment variables in the backup selections list
- About appropriate host selection for NetApp cDOT backup policies
- About backup types in a schedule for an NDMP policy
- About enabling or disabling DAR
- Configuring NetBackup for NDMP in a clustered environment
- Configuring NDMP backup to NetBackup media servers (remote NDMP)
- Configuring NDMP DirectCopy
- Accelerator for NDMP
- Remote NDMP and disk devices
- Using the Shared Storage Option (SSO) with NetBackup for NDMP
- Backup and restore procedures
- Troubleshooting
- Using NetBackup for NDMP scripts
- About the NetBackup for NDMP scripts
- ndmp_start_notify script (UNIX)
- ndmp_start_notify.cmd script (Microsoft Windows)
- ndmp_end_notify script (UNIX)
- ndmp_end_notify.cmd script (Microsoft Windows)
- ndmp_start_path_notify script (UNIX)
- ndmp_start_path_notify.cmd script (Microsoft Windows)
- ndmp_end_path_notify script (UNIX)
- ndmp_end_path_notify.cmd script (Microsoft Windows)
- ndmp_moving_path_notify script (UNIX)
- ndmp_moving_path_notify.cmd script (Microsoft Windows)
- Introduction to NetBackup for NDMP
ndmp_end_path_notify script (UNIX)
The UNIX scripts are provided as examples only. You must customize the scripts before using them. For example, the -ne value in the first if statement must be modified to reflect the number of passed parameters. For the ndmp_end_path_notify script, the -ne value must be set to 7.
Note:
Before you use this script, make sure you can run it by using other on the media server. Run chmod 755 script_name, where script_name is the name of the script.
For a UNIX media server, if you need notification whenever the NDMP host completes a backup, copy
/usr/openv/netbackup/bin/goodies/bpend_notify
from the server, to
/usr/openv/netbackup/bin/ndmp_end_path_notify
on the UNIX NetBackup for NDMP host. Then, modify the script and ensure that you have permission to run it.
The ndmp_end_path_notify script runs after the NAS machine has informed NetBackup that it has completed sending data.
NetBackup passes the following parameters to the ndmp_end_notify script:
Table: Script parameters for ndmp_end_path_notify (UNIX)
Parameter | Description |
|---|---|
$1 | Specifies the name of the client from the NetBackup catalog. |
$2 | Specifies the policy name from the NetBackup catalog. |
$3 | Specifies the schedule name from the NetBackup catalog. |
$4 | Specifies one of the following: FULL INCR (differential incremental) CINC (cumulative incremental) |
$5 | Specifies the exit code from bptm. |
$6 | Not used. |
$7 | Specifies the path being backed up. |
For example:
ndmp_end_path_notify freddie cd4000s fulls FULL 0 ndmp_end_path_notify danr cd4000s incrementals INCR 73
To create an ndmp_end_path_notify script for a specific policy or policy and schedule combination, create script files with a .policyname or .policyname.schedulename suffix. In the following two examples of script names, the policy is named production and the schedule is named fulls:
/usr/openv/netbackup/bin/ndmp_end_path_notify.production /usr/openv/netbackup/bin/ndmp_end_path_notify.production.fulls
The first script affects all scheduled backups in the policy that is named production. The second script affects scheduled backups in the policy that is named production only when the schedule is named fulls.
Note:
For a given backup, NetBackup uses only one ndmp_end_path_notify script and that is the one with the most specific name. For example, if there are both ndmp_end_path_notify.production and ndmp_end_path_notify.production.fulls scripts, NetBackup uses only ndmp_end_path_notify.production.fulls.
The ndmp_end_path_notify script can use the following environment variables:
BACKUPID UNIXBACKUPTIME BACKUPTIME
The NetBackup bptm process creates these variables. The following are examples of the strings that are available to the script for use in recording information about a backup:
BACKUPID=freddie_0857340526 UNIXBACKUPTIME=0857340526 BACKUPTIME=Sun Mar 2 16:08:46 1997