Limiting the number of SLP secondary operations to maximize performance
Less is more. Run fewer jobs but allow each job to manage as much data as possible. SLP parameters can be used to assist the lifecycle to run duplication jobs more efficiently. To prevent the lifecycle from running numerous small duplication jobs in frequent succession, NetBackup accumulates lists of similar images into a batch. Then, each batch of images is copied as a set in one duplication job, instead of one image at a time. The NetBackup administrator can change how large the batch file scan becomes, or how frequently batch jobs are requested.
More information is available in the following technical articles:
Storage Lifecycle Policy (SLP) tuneable parameters to optimize the duplication process
Storage Lifecycle Policy (SLP) Cheat Sheet
Also see SLP Parameters properties in the NetBackup Administrator's Guide, Volume I
Table: Common SLP parameters that impact BID files
| SLP property | Default value |
|---|---|
Maximum size per duplication job The largest batch size that can run as a single duplication job. | 100 GB |
Minimum size per duplication job The smallest batch size that can run as a single duplication job. The job does not run until enough images accumulate to reach this minimum batch size or until the Force interval for small jobs time is reached. | 8 GB |
Maximum size per A.I.R. replication job The largest batch size that can run as a single job for Auto Image Replication. | 100 GB |
Maximum Images per A.I.R. Import job The largest number of images in a single batch that can run as an Auto Image Replication import job. | 250 |
Minimum Images per A.I.R. Import job The fewest number of images in a single batch that can run as an Auto Image Replication import job. The job does not run until either the minimum size is reached or the Force interval for small jobs time is reached. | 1 |
Force interval for small job The age that the oldest image in a batch must reach after which the batch is submitted as a duplication job. This value prevents many small duplication jobs from running at one time or running too frequently. It also prevents NetBackup from waiting too long before it submits a small job. | 30 minutes |
Effects of increasing these SLP parameters:
Minimum size per duplication job and Force interval for small job
Increasing the Minimum size per duplication job will cause the total number of images in a BID file to reach a higher size threshold before a small job will be started. The small job will be started after the Force interval for small job value is reached. This can have the effect of duplication jobs starting further apart because it will take more time for a total batch size to reach the limit.
Maximum size per duplication job
Increasing the Maximum size per duplication job will cause the maximum batch size for a single duplication job be raised to the specified size. A higher value can have the effect of reducing the number of duplication jobs that can run.
Maximum size per A.I.R. replication job
Increasing the Maximum size per A.I.R. replication job will cause the maximum batch size for a single A.I.R. replication job be raised to the specified size. A higher value can have the effect of reducing the number of A.I.R. replication jobs that run while managing more images at one time.
Maximum Images per A.I.R. Import job
Increasing the Maximum Images per A.I.R. Import job will cause the maximum number of images in a single job in an A.I.R. Import. A higher value can have the effect of reducing the number of A.I.R. Import jobs that run, while managing more images per job.
Minimum Images per A.I.R. Import job
Increasing the Minimum Images per A.I.R. Import job will cause the minimum number of images in a single job be increased and then wait until the Force interval for small job is reached. The effect of increasing this value is that fewer A.I.R. Import jobs run, but more images be managed with each job.