Why are there many SLP driven duplication jobs for 1 SLP that uses the same retention for the duplication jobs?

Problem

Why are there many SLP driven duplication jobs for 1 SLP that uses the same retention for the duplication jobs?

Error Message

If the backup source media is different, you will see in the nbstserv (oid = 226) log

add new batch job because "Media set does not match"
 

Cause

One objective of the nbstserv batching logic is to prevent media contention for tape operations (including VTL).
 

Solution

/usr/openv/netbackup/db/config/LIFECYCLE_PARAMETERS


DUPLICATION_SESSION_INTERVAL_MINUTES
This parameter indicates how frequently nbstserv starts a duplication session. During a duplication session, NetBackup looks for completed backups on backup storage destinations and decides whether or not it is time to start a new duplication job.
Default: 5 minutes. Minimum: 1 minute.
Syntax: DUPLICATION_SESSION_INTERVAL_MINUTES 5


MIN_GB_SIZE_PER_DUPLICATION_JOB
This parameter indicates the size that the batch of images should reach before one duplication job is run for the entire batch.
The lifecycle does not request a duplication job until either:
The aggregate size of the images in a batch reaches the minimum size as indicated by MIN_GB_SIZE_PER_DUPLICATION_JOB
The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB time passes. This parameter determines the maximum time be
tween batch requests.
Default: 7 gigabytes.
Syntax: MIN_GB_SIZE_PER_DUPLICATION_JOB GB_value


MAX_GB_SIZE_PER_DUPLICATION_JOB
This parameter determines how large the batch of images is allowed to grow. When the size reaches the size as indicated by this parameter, no additional images are added to the batch.
Default: 25 gigabytes.
Syntax: MAX_GB_SIZE_PER_DUPLICATION_JOB GB_value


DUPLICATION_GROUP_CRITERIA
This parameter indicates how batches are created. The entry applies to the use of tape and disk.
Syntax: DUPLICATION_GROUP_CRITERIA 0 | 1
0 = Select 0 to indicate that batches be created based on the storage lifecycle policy name.
1 = Select 1 to indicate that batches be created based on the duplication job priority from the storage lifecycle policy definition. This setting allows multiple storage lifecycle policies of the same priority together in a job.
Default: 1 (Use the storage lifecycle policy name).


TAPE_RESOURCE_MULTIPLIER
This parameter indicates a value which serves as the multiplier for the number of concurrently active duplication jobs that can access a single storage unit. This parameter applies to tape media.
Storage unit configuration includes limiting the number of jobs that can access the resource at one time. (The Maximum concurrent write drives value.) This value specifies the optimal number of jobs that the Resource Broker can consider running on that resource.
This parameter helps administrators ensure a balance in the following situation:
To overload the Resource Broker with jobs that it can't run is not prudent.
Make sure that there's enough work that is queued so that the devices won't become idle. The TAPE_RESOURCE_MULTIPLIER entry lets administrators tune the amount of work that the Resource Broker can evaluate for a particular storage unit.
For example, a particular storage unit contains three write drives. If the TAPE_RESOURCE_MULTIPLIER parameter is set to two, then the limit on concurrently active jobs is six. Other duplication jobs requiring the storage unit remain queued.
Default: 2
Syntax: TAPE_RESOURCE_MULTIPLIER n


Terms of use for this information are found in Legal Notices.

Search

Survey

Did this article answer your question or resolve your issue?

No
Yes

Did this article save you the trouble of contacting technical support?

No
Yes

How can we make this article more helpful?

Email Address (Optional)