Types of Data Retained

When you run Jobs and Workflows, their Job data is saved on the RunMyJobs server. Depending on the Job or Workflow type, the output can also be saved on Platform Agents (for OS jobs) or on the spool host. All of these records must be taken into account for healthy housekeeping.

Execution Data

Each Job and Workflow generates output and log files for each execution. This includes, but is not always limited to:

• The RunMyJobs log file.
• An entry in the RunMyJobs history.
• A potential log from an automated application.

To put this in context, here are some examples of frequency and number of executions over a period of time if you do not set retention policies.

Note: Keep in mind that these are single Jobs. If you have a Workflow with three Job Calls, you must multiply this number by at least three. (A Workflow is a Job, as well as each of the Steps in the process, so a Workflow with three Steps and one Job Call in each Step generates seven Jobs in the Redwood repository.)

• A single Job that runs every 5 minutes generates 288 daily, 2.016 weekly, about 8.640 monthly, and 105.120 yearly Jobs.
• A single Job that runs every 15 minutes generates 96 daily, 672 weekly, about 2.880 monthly, and 35.040 yearly Jobs.
• A single Job that runs 8 times a day during business hours generates 8 daily, 56 weekly, about 240 monthly, and 2.920 yearly Jobs.
• A single Job that runs weekly generates 1 weekly, 4-5 monthly, and 52 yearly Jobs.

Static Data

In addition to execution data, there is static data to archive, including Events, Operator Messages, Audits, and logging information. For more information, see Purging Static Data.