Blackout period

Data scans are scheduled to run on a schedule based on the agent cluster assigned to a source. You can refine or alter a schedule for a given dataset. At either the agent cluster level or the dataset level, you can set a blackout period during which time no new jobs will be started—in-progress jobs will continue.

  • When you define a blackout period for an agent cluster, all agents assigned to the cluster abide by the blackout period. These agents will not start any new scan actions during this time. For more information, see Agent clusters

  • When you define a blackout period for a dataset, new scans against the dataset are not performed during the blackout period. If you assign an agent cluster with a blackout period to the dataset's source, the blackout period for the dataset overrides the blackout at the cluster level. For more information, see Manage datasets

If you need to have all scans of a specific data source type completely stop for a set time period, even if mid-scan, you can configure a blackout period at the agent level. When you set this at the agent level, new jobs are not processed and in-progress jobs are stopped at the start of the blackout period. For example, you have a need to stop all scanning activity of your Content Manager data during employee work hours.

    NOTE:
  • Agent level blackout periods do not apply to Documentum, Extended ECM, Structured Data Manager, or structured data source types.

  • Agent level blackout periods stop in-progress scans. Data items that may have been partially processed when the agent level blackout period started will be rescanned during the next scan.

  • Agent level blackout periods must be defined on every agent host for the desired data type.

  • When an agent cluster or dataset level blackout period is assigned in addition to an agent level blackout period, both black out periods apply.