Runtime considerations that affect backup frequency
The following items may cause a NetBackup job to run more frequently than expected, or may prevent a job from meeting its backup frequency requirement.
Table: Items that can affect backup frequency
Item | Description |
|---|
|
Changing a policy causes the policy to run
|
If the administrator changes or activates a policy, the change prompts NetBackup to run the job as soon as possible. It does not matter if the schedule is calendar-based or frequency-based.
|
|
Window availability
|
Whether the schedule is calendar-based or frequency-based, a job cannot run if windows are not open on the configured rundays. For calendar-based schedules, windows must be open on the specific dates, recurring weekdays, or recurring days of the month that the calendar schedule indicates. A frequency is not configurable for a calendar-based schedule. For this schedule type, NetBackup assumes a daily backup frequency. For frequency-based schedules, a daily frequency requires that a window is open each day.
|
|
Backup attempt limit
|
A Global Attribute host property setting determines how many times a failed job can attempt to run. The Schedule backup attempts property includes the number of attempts and the time period in which the attempts can take place.
By default, a failed job tries to run two times every 12 hours if an open window is available. Note that this setting supersedes any other frequency requirement and can cause a schedule to skip an open window.
For example, if a job meets the maximum number of job attempts, NetBackup does not try to run the job again during the retry period indicated. It does not attempt, even in an open window and a daily backup frequency has not been met that day.
See Global attributes properties.
|
