The NetBackup SLP manager (nbstserv) batches backup images before submitting a duplication job to optimize resource usage. This batching is primarily controlled by the "Minimum size per duplication job" parameter. The default value for this parameter is typically much larger than 100MB. Because the backup image is small, the SLP manager waits for more images to accumulate to meet this size threshold, causing a delay. By reducing the minimum size to 50MB (a value less than the 100MB backup), the administrator ensures the size threshold is met immediately after the backup completes, thus triggering the duplication job as soon as possible.

A. The "Job submission interval" is a time-based trigger that runs only if the size threshold is not met. The primary cause of the delay here is the size threshold.

C. This is a manual, one-time operation. The question asks how to ensure duplications run quickly, implying an automated and persistent configuration change.

D. Priority affects how a job competes for resources against other active jobs once it is submitted. It does not influence when the SLP manager submits the job.

1. Veritas NetBackup™ Administrator's Guide

Vol. I (Version 10.0)

Chapter: "Managing storage lifecycle policies"

Section: "SLP parameter host properties". This section details the function of "Minimum size per duplication job" and "Job submission interval

" explaining that the size parameter is the primary control for batching images for duplication.

2. Veritas NetBackup™ Deduplication Guide (Version 10.0)

Chapter: "About NetBackup storage lifecycle policies"

Section: "How SLPs manage duplication jobs". This guide explains that nbstserv uses the configured parameters to decide when to create a duplication job

prioritizing the batch size to create fewer

larger jobs for efficiency.

3. Veritas™ NetBackup Troubleshooting Guide (Version 9.1)

Chapter: "Troubleshooting Storage Lifecycle Policies"

Section: "SLP duplication job is delayed". This section explicitly identifies the "Minimum size per duplication job" being set too high for the size of the backup images as a common cause for duplication delays.