Snapshot Job - General

Name

Identifying name.

Description

Optional descriptive text.

Save in

Folder in which to store the job.

Select Snapshot Job Type

Choose one of the following options:

• Snapshot components — The job records information for all components (specified using templates) which are discovered on the target servers you specify.
• Snapshot server objects — The job records server objects that you select from live servers.

Number of Targets to Process in Parallel

Choose one of the following options:

• Unlimited — Simultaneously runs the job on as many servers as possible. Application Server settings control the number of targets the job can access.
• Limited — Specifies the maximum number of targets on which the job can run simultaneously. Limiting the number of targets is useful when a job might temporarily disrupt the functionality of a target server, and you want to limit that disruption to a small fraction of your managed servers.
  If you want the job processed serially at the target servers, set this value to 1. Note, however, that although this is the best approach for achieving serial processing, it does not always guarantee full serial processing at all targets; the first two or three targets might still run in parallel.

Set Execution Override

Select if this job should always execute as if your current role and user are scheduling the job. After you click this option, the job definition shows the role:user combination under which the job executes.

Clear Execution Override

Remove an existing execution override.

Run auto-discovery

Whether to authorize the Snapshot Job to perform component discovery for the associated component templates and generate components for use in the Snapshot Job.

This replaces the need to manually run a Component Discovery Job before running the Snapshot Job.