ServerTasksAt1

Parameter: ServerTasksAt1
Short description: Defines server tasks that are started automatically every day at 01:00. By default, the Catalog task (database catalog update) is entered here. Overwritten on upgrade installs unless SetupLeaveServerTasks is set.

Description

Defines server tasks that are started automatically every day at 01:00 (full hour 1). By default, the Domino setup writes the Catalog task here, which updates the database catalog (catalog.nsf).
ServerTasksAt1 belongs to the ServerTasksAt<N> family (N = 0 … 23) — each variable defines server tasks for one specific full hour of the day. This makes it possible to start routine maintenance tasks (Catalog, Design, Compact, Updall, Fixup) on a schedule without having to create a dedicated program document in the Domino Directory.

Profile

Parameter
ServerTasksAt1
Category
Startup / Tasks
Component
Domino server
Value range
Comma-separated list of server task names (e.g. Catalog, Design, Compact)
Default
Catalog (written by setup)
Available since
Very early (before 9.0.1) — standard setup parameter in all Notes/Domino versions
Effective
Next server restart, or at the next matching hour after a server restart
GUI equivalent
Configuration document → NOTES.INI Settings tab (Set/Modify Parameters)

Examples

ServerTasksAt1=Catalog
ServerTasksAt1=Catalog,Design

Notes

  • During an upgrade install, ServerTasks and ServerTasksAt<N> are automatically reset by HCL Domino to the new default values — this is working as designed (HCL KB0104793). Customizations are lost as a result.
  • To preserve your own customizations across an upgrade, write SetupLeaveServerTasks=1 to notes.ini before the upgrade.
  • On clustered servers or with multiple identical servers, program documents in the Domino Directory are preferable, because they can be managed centrally and do not depend on the local notes.ini (HCL Domino 11.0.1 „Domino server tasks“).
  • There is exactly one ServerTasksAt<N> variable per hour; multiple entries with the same <N> would overwrite each other. For different times of day, ServerTasksAt2, ServerTasksAt3, ServerTasksAt5, etc. are used.
  • Tasks from ServerTasksAt<N> run in addition to the tasks started at server start via ServerTasks, and exit again after completion.

Sources (HCL Product Documentation)