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
Track log sizing considerations
The accelerator track log stores file system metadata, and the unique fingerprints of files (128KiB segments). The track log size is relative to the size of the file system, and the number of backup files. Different track logs are created for each policy, client, and stream combination.
Here are some general guidelines, but the requirements in a specific environment might be different. Environments with a high rate of data change may require a larger track log size.
For D-NAS policy, the track log is stored on the backup host, and transferred to the primary server in-line during the backup operation. You can use the following formula to calculate the approximate size:
Total Track log size in Bytes for a NAS volume backup job = 2*( (Number of files * 200) + ((Total used disk space in KiB/128KiB) * 20))
For example, 1 TB NAS volume with one million files = ~ 701 MiB total track log size. If four streams are configured for backup and one million files are equally distributed amongst four streams, streams, then each stream's track log can be of ~175 MiB in size.