Ransomware attackers specifically target and attempt to destroy backup systems to increase the probability of payment. Hardening your system is critical. Please ensure you have reviewed your platform security using the Security Hardening Checklist
Cohesity

COHESITY Documentation

Explore our documentation to get started, discover products & new features, access troubleshooting guides, register sources, platforms support.

Products
Data Security Alliance
Visit Cohesity.com
Demos
Support
Blogs
Developers
Partner Portals
Cohesity Community
© 2026 Cohesity, Inc. All Rights Reserved.
Terms of Use|
Privacy Policy|
Legal|
  1. Home
  2. NetBackup™ NAS Administrator's Guide
  3. Section III. Using NDMP
  4. Using NetBackup for NDMP scripts
  5. ndmp_end_path_notify script (UNIX)
NetBackup™ NAS Administrator's Guide

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

Feedback

Was this page helpful?
Previous

ndmp_start_path_notify.cmd script (Microsoft Windows)

Next

ndmp_end_path_notify.cmd script (Microsoft Windows)

Feedback

Was this page helpful?