NetBackup™ NAS Administrator's Guide
- Section I. About NAS backups
- Section II. Using NAS-Data-Protection (D-NAS)
- D-NAS overview
- D-NAS Planning and Tuning
- Pre-requisites for D-NAS configuration
- Configuring Storage Lifecyle Policies for D-NAS
- About storage lifecycle policies
- Snapshot operation in SLP
- Creating a storage lifecycle policy for snapshots and snapshot replication
- Replication operation in the SLP
- Index from snapshot operation in an SLP
- Backup from snapshot operation in an SLP
- Duplication operation in an SLP
- Retention types for SLP operations
- Volume multi-host backup
- Configure D-NAS policy for NAS backups
- About policies for NAS backups
- Planning for policies
- Prerequisites for D-NAS policies
- Configure D-NAS policy for NAS volumes
- Policy attributes
- Creating schedule attributes for policies
- Configuring the Start window
- Configuring the exclude dates
- Configuring clients
- Configuring backup selections
- Configuring exclude lists
- Ordering of backup from snapshot jobs
- About mixed mode volumes
- Configuring include and exclude lists
- Auto-resume backup for incomplete backup jobs
- Using Accelerator
- Using Vendor Change Tracking
- Using true image restore
- Replication using D-NAS policy
- Restoring from D-NAS backups
- Multi-stream restores from D-NAS backups
- Considerations for restoring from D-NAS backups
- About the Overwrite existing file option during restore
- RBAC role for D-NAS restores
- Scanning for malware
- Restore everything to a different location
- Restore individual files and folders to different locations
- Original location restores for D-NAS Policy
- Point-in-time rollback
- Multi-stream restores from D-NAS backups
- Troubleshooting
- Troubleshooting
- Setting the log level
- Logging directories for Linux platforms
- Logging folders for Windows platforms
- Logging folders for multi-stream restore
- Exclude list is not working during backup
- Restore from a snapshot fails with status 133
- Backup from snapshot jobs do not start after the snapshot job completes successfully
- 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
- Backup from snapshot jobs for NAS-Data-Protection policy fail with error 4213
- A full VCT-enabled indexing job runs, when followed by a non-VCT indexing job with a backup host prior to version to 10.3
- Backup from snapshot jobs for NAS data protection policy fail with error 927
- Error code: 930: No supported media server is available in the All_Media_Server_Pool to use to backup the NAS shares.
- Restore from NAS array volume fails with the status: 174 Media manager - system error occurred.
- NAS job fails with the error: Crawler process timed out after 600 seconds waiting for streams to attach with shared memory.
- D-NAS backup fails with the error: The file system crawler process timed-out waiting for streams to attach with shared memory. (3003)
- Isilon backup from snapshot failed with the Snapshot cannot be mounted error.
- Discovery and snapshot operations fail with the errors 156 and 1542
- Section III. Using NDMP
- 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 creating an NDMP policy
- About appropriate host selection for NetApp cDOT backup policies
- Attributes tab options for an NDMP policy
- Schedules tab options for an NDMP policy with Accelerator for NDMP enabled
- About backup types in a schedule for an NDMP policy
- Clients tab options for an NDMP policy
- Backup selection options 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
- NAS appliance information for NDMP
- About NAS appliances support
- Non-vendor-specific information
- Vendor-specific information
- Dell EMC Isilon
- Dell EMC VNX
- Dell EMC Unity
- EMC Celerra
- Hitachi HDI/VFP
- Hitachi NAS (HNAS)
- HP X9000 NAS
- Huawei OceanStor V3
- IBM System Storage Nxxxx
- NEC Storage NV series
- NetApp
- Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
- Using a node name as the NDMP client name in all versions of NetBackup
- Using a data Vserver LIF as the NDMP client name in non-CAB-aware versions of NetBackup
- Using a cluster_mgmt vserver LIF as the NDMP client name in non-CAB-aware versions of NetBackup
- Using a cluster_mgmt Vserver LIF as the NDMP client name in CAB-aware versions of NetBackup
- Using NetBackup with NetApp's Data ONTAP 8.2 cluster mode
- Nexenta
- Nexsan
- Oracle Axiom Series
- Oracle Solaris Server
- Stratus V Series
- 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_moving_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_moving_path_notify script, the -ne value must be set to 7.
To use this script, create a script similar to
/usr/openv/netbackup/bin/goodies/bpstart_notify
on the server, and copy it to
/usr/openv/netbackup/bin/ndmp_moving_path_notify
on the UNIX NetBackup for NDMP server. Then, modify the script and ensure that you have permission to run it.
On UNIX media servers, the ndmp_moving_path_notify script runs after the backup process sends data to NetBackup.
Note:
Before you use this script, make sure you can run it using other on the media server. Run chmod 755 script_name, where script_name is the name of the script.
If the /usr/openv/netbackup/bin/ndmp_moving_path_notify script exists, it runs in the foreground. The bptm process that is on the NetBackup for NDMP server waits for it to complete before continuing. Any commands in the script that do not end with an & character run serially.
The server expects the client to respond with a continue message within the period of time that the NetBackup CLIENT_READ_TIMEOUT option on the server specifies.
The default for CLIENT_READ_TIMEOUT is 300 seconds. If the script needs more than 300 seconds, increase the value to allow more time.
NetBackup passes the following parameters to the script:
Table: Script parameters for ndmp_moving_path_notify (UNIX)
Parameter | Description |
|---|---|
$1 | Specifies the name of the NDMP host. |
$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 NetBackup status code for the operation. |
$6 | Not used. |
$7 | Specifies the path being backed up. |
For example:
ndmp_moving_path_notify freddie cd4000s fulls FULL ndmp_moving_path_notify danr cd4000s incrementals INCR ndmp_moving_path_notify hare cd4000s fulls FULL
To create an ndmp_moving_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_moving_path_notify.production /usr/openv/netbackup/bin/ndmp_moving_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_moving_path_notify script and that is the one with the most specific name. For example, if there are both ndmp_moving_path_notify.production and ndmp_moving_path_notify.production.fulls scripts, NetBackup uses only ndmp_moving_path_notify.production.fulls.
The ndmp_moving_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