Expected Scanning Behaviors For Background Scans - IBM Proventia Network Enterprise Scanner User Manual

Expected Scanning Behaviors for Background Scans

Introduction
Expected behaviors
IBM Proventia Network Enterprise Scanner User Guide, Version 1.3
This topic answers question you may have about what to expect from background scans
in different circumstances.
Expect the following with background scans:
I changed a Scan Control policy when there were additional scan windows available in
Q:
the refresh cycle, but the scans did not start until the new refresh cycle.
Scans will run only once during a refresh cycle. If you change the Scan Control
A:
policy after the scans have run for that cycle, the changes do not go into effect until the
beginning of the next refresh cycle.
When is a background scan scheduled in the Command Jobs window?
Q:
Background scans appear in the Command Jobs window as follows:
A:
If the agent to run the background scan is available, the scan job appears in the
■
Command Jobs window at midnight on the day of a new refresh cycle.
If the agent to run the background scan is not available, the scan job appears in the
■
Command Jobs window when the agent is available, provided it is on a valid start
date.
How many states does a background job go through?
Q:
A background job starts out in the Pending state. It quickly goes to one of these
A:
states:
The job moves to the Idle state if a scan window is not open.
■
The job moves to the Processing state when a scan window is open, if an agent is
■
available, and if it is the highest priority job.
Why does a scanning job expire?
Q:
If a scan job has not finished when a new refresh cycle begins, the job goes into the
A:
Expired state shortly after midnight on the day of the new refresh cycle.
Why did my background scan continue to run even when the refresh cycle started
Q:
again?
If you rerun a background scan, it is not confined by refresh cycles. It runs like an
A:
ad hoc scan in that respect.
Q: Why did my background scanning job stop when I ran an ad hoc scan on the same
group?
According to the rules for prioritization, an ad hoc scan has priority of a
A:
background scan. If you run an ad hoc scan on a group where background scan is
running, the background scan pauses after it completes its current subtask and then
gives priority to the ad hoc scan. The background scan will resume after the ad hoc
scan has finished.
Expected Scanning Behaviors for Background Scans
159