LIFECYCLE_PARAMETERS file for optional lifecycle-managed job configuration on UNIX/Linux

Article:HOWTO33715  |  Created: 2010-10-28  |  Updated: 2011-03-10  |  Article URL http://www.symantec.com/docs/HOWTO33715
Article Type
How To


Environment

Subject


LIFECYCLE_PARAMETERS file for optional lifecycle-managed job configuration on UNIX/Linux

The NetBackup administrator can customize how the NetBackup Storage Lifecycle Manager (nbstserv) runs duplication and import jobs.

Both the Duplication Manager service and the Import Manager service run within nbstserv. Table: Role of the nbstserv services describes the role of each service.

Table: Role of the nbstserv services

nbstserv service

Purpose of service

Location of LIFECYCLE_PARAMETER file

Duplication Manager

Manages the duplication jobs within storage lifecycle policies.

In the duplication to remote master process, the Duplication Manager duplicates images and creates batches of the images to be imported in the target domain.

Configure Duplication Manager parameters in the source domain to tune the duplication to remote master jobs.

Note:

The Duplication Manager parameters affect all SLP duplications, even those that are not duplicated to a remote master. Exercise caution when tuning for one case or the other.

Import Manager

In the duplication to remote master process, the Import Manager monitors a worklist in EMM for images to be imported and initiates bpimport jobs for those images.

If the NetBackup environment is not configured for duplication to a remote master, the Import Manager does not perform any actions.

If the NetBackup environment is configured for duplication to a remote master, configure Import Manager parameters in the target domain.

See Process overview to duplicate to a remote master on UNIX/Linux.

The nbstserv default values work well for most environments. To change the values, the administrator must create a file named LIFECYCLE_PARAMETERS and save it in the following location:

/usr/openv/netbackup/db/config

One or all of the parameters in Table: Lifecycle parameters can appear in the LIFECYCLE_PARAMETERS file in any order. If the file does not exist, NetBackup uses the defaults as indicated.

Table: Lifecycle parameters

Parameter

Description

AUTO_CREATE_IMPORT_SLP

Affects:

Import Manager

Indicates to the Import Manager how NetBackup should handle notifications from storage about images for which there is no matching Import storage lifecycle policy.

The entry is Boolean, where a non-zero value directs NetBackup to create a storage lifecycle policy definition that uses the name provided in the import notification to the storage device.

Syntax: AUTO_CREATE_IMPORT_SLP 0 | 1

0 = Select 0 to indicate that NetBackup should not automatically create an Import SLP if a notification is received for an Import SLP which does not exist.

To remove the parameter from LIFECYCLE_PARAMETERS file has the same effect as 0.

1 = Select 1 to automatically create an Import SLP if a notification is received for an Import SLP which does not exist.

The SLP that is automatically created has the following characteristics:

  • The SLP is always a data classification of None.

  • The SLP always uses the default import priority.

  • The SLP always specifies any storage unit which includes the device from which the event was received.

Default: 0; storage lifecycle policies are not created automatically.

Note:

This parameter is used primarily to duplicate to a remote master using NetBackup appliances.

See Configuring the storage lifecycle policies required to duplicate to a remote master server on UNIX/Linux.

CLEANUP_SESSION_INTERVAL_HOURS

Affects:

Duplication Manager

Concerns the deletion of storage lifecycle policy versions where a more recent version exists.

Controls how often nbstserv looks for the versions that have been deleted.

Syntax: CLEANUP_SESSION_INTERVAL_HOURS nn_hours

Default: 24 (24 hours).

See About deleting old storage lifecycle policy versions on UNIX/Linux.

DUPLICATION_GROUP_CRITERIA

Affects:

Duplication Manager

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.

DUPLICATION_SESSION_INTERVAL_MINUTES

Affects:

Duplication Manager

Indicates how frequently the Duplication Manager 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.

Syntax: DUPLICATION_SESSION_INTERVAL_MINUTES 5

Default: 5 (five minutes). Minimum: one minute.

IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS

Affects:

Duplication Manager

All copies must be completed in a lifecycle. If necessary, NetBackup initially tries three times to duplicate an image to a duplication destination. The limit prevents NetBackup from retrying too frequently. If, after three tries, the copy is still unsuccessful, this parameter indicates how long NetBackup waits before an image copy is added to the next duplication job. (The DUPLICATION_SESSION_INTERVAL_MINUTES parameter determines the frequency.)

The NetBackup administrator may need more than two hours (the default) to solve the problem. Alternatively, the administrator can temporarily de-activate a lifecycle using nbstlutil.

Syntax: IMAGE_EXTENDED_RETRY_PERIOD_IN_HOURS 2

Default: 2 (two hours). Minimum: one hour.

IMPORT_EXTENDED_RETRY_SESSION_TIMER

Affects:

Import Manager

After four failed attempts, the Import Manager retries at the extended retry interval indefinitely or until the number of days specified by the REPLICA_METADATA_CLEANUP_TIMER parameter has elapsed.

Syntax: IMPORT_EXTENDED_RETRY_SESSION_TIMER 360

Default: 360 (360 minutes; six hours).

IMPORT_SESSION_TIMER

Affects:

Import Manager

Indicates to the Import Manager how many minutes to wait between import sessions.

During an import session, the Import Manager performs the following tasks:

  • Cleans up image import status and increments the retry count of failed imports. The Import Manager retries in the current session.

    After four failed attempts to import an image, NetBackup enters an extended retry state. (See the IMPORT_EXTENDED_RETRY_SESSION_TIMER parameter description in this table.)

  • Deletes old, unimported import records. (By default, the records are not deleted and the Import Manager retries indefinitely. For the Import Manager to delete old import records, configure the REPLICA_METADATA_CLEANUP_TIMER parameter.)

  • Creates batches of images for import and starts import jobs.

Syntax: IMPORT_SESSION_TIMER 5

Default: 5 (five minutes).

MIN_GB_SIZE_PER_DUPLICATION_JOB

Affects:

Duplication Manager

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 between batch requests.

Syntax: MIN_GB_SIZE_PER_DUPLICATION_JOB GB_value

Default: 7 (7 gigabytes).

MAX_GB_SIZE_PER_DUPLICATION_JOB

Affects:

Duplication Manager

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.

Syntax: MAX_GB_SIZE_PER_DUPLICATION_JOB GB_value

Default: 25 (25 gigabytes).

MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB

Affects:

Duplication Manager

Indicates how old any image in the group can become before the batch is submitted as a duplication job. It applies to both disk and tape.

The MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB entry working differently in this release than it did in previous releases.

A very small batch is not submitted to nbstserv until one source job in the batch has finished at least 30 minutes ago.

Note:

The timer does not come into effect if the total size of all the images in the batch exceeds the parameter value. Or, if all of the source media that the duplication job requires is full.

This parameter helps to ensure a balance between the following conditions:

  • Submitting many small duplication jobs too soon or too frequently.

    On the one hand, nbstserv doesn't want to submit a small job if there's additional work available to make the job bigger and more efficient.

  • Waiting too long before submitting a small job.

    On the other hand, nbstserv should not wait too long to submit a small job.

Syntax: MAX_MINUTES_TIL_FORCE_SMALL_DUPLICATION_JOB 30

Default: 30 (30 minutes).

REPLICA_METADATA_CLEANUP_TIMER

Affects:

Import Manager

Indicates the number of days after which the Import Manager stops trying to import the image. After the number of days indicated, the record is deleted.

How frequently the Import Manager tries to import the images depends on the setting of the extended retry timer and session timer. The first four attempts occur at the regular session interval and the remaining attempts occur at the extended retry interval.

Syntax: REPLICA_METADATA_CLEANUP_TIMER 0 | n

Default: 0 (off).

TAPE_RESOURCE_MULTIPLIER

Affects:

Duplication Manager

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.

See Maximum concurrent write drives storage unit setting on UNIX/Linux.

This parameter helps administrators ensure a balance in the following situation:

  • To overload the Resource Broker with jobs 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.

Syntax: TAPE_RESOURCE_MULTIPLIER n

Default: 2 (multiplier of two).

VERSION_CLEANUP_DELAY_HOURS

Affects:

Duplication Manager

Concerns the deletion of storage lifecycle policy versions where a more recent version exists.

Controls how much time must pass since an inactive version was the active version. If the version has been inactive for at least as long as the VERSION_CLEANUP_DELAY_HOURS value, NetBackup considers it for deletion.

Syntax: VERSION_CLEANUP_DELAY_HOURS nn_hours

Default: 336 (336 hours; 14 days).

See About deleting old storage lifecycle policy versions on UNIX/Linux.

See LIFECYCLE_PARAMETERS file example on UNIX/Linux


Legacy ID



v42387048_v46435089


Article URL http://www.symantec.com/docs/HOWTO33715


Terms of use for this information are found in Legal Notices