You are currently viewing Week 4 – Ivanti Automation maintenance

Week 4 – Ivanti Automation maintenance

This week we discuss the Ivanti Automation maintenance. Often we see large databases which directly infect the performance of the software and the execution of jobs. Ivanti delivers 2 tasks to export and clean the Job History list.

The tasks Ivanti Automation Results (Delete and Export) are 2 tasks which helps the database clean.
But how to check the size of the History tables in the database?
Go to Administration – Information – Size and check the size of the different tables.

When using Resources the Files size will be increasing fast but this is normal behavior based on the resources (i.e. adding multiple Office release). The Job History in the Information Size overview is the most important. We have seen customers with a size of 1 TB. These kind of sizes really decrease the performance of the system and the database.

But how can make sure the Job History is not increasing fast. Increasing of the Job History also depends on the amount of executed jobs. The more jobs are executed the faster the Job History expands. But do we need all the information in the Job History stored in the database or can we just remove Job History older than for example 6 months. Or do we first need to export the Job History to an external file. This blog discuss how to export and delete Job History older than 2 months and execute this job every month.

In the Automation Console go to Library – Modules and create a new Module. Give the module a name and select Tasks in the tabs. Select Add to select a new task. Search for results and the 2 tasks will popup.

First tasks we select is the Export. Change the period to the required period. In this example we set the value to 2 months.
Select All Agents in the Agents drop down list.
Change the location of the folder to store the file.

Be aware when executing this job when the size of the Job History is larger than 1 year we recommend to execute the export and delete in different periods. Otherwise the job takes to long to run and will impact the daily jobs because of the impact on the database.

For example:
When the data is older than 3 years execute the following process:

  • Period older than 3 years
  • Period older than 2 years
  • Period older than 1 year
  • Period older than 6 months
  • Period older than 2 months (these settings will be used for the recurring task)

Next step is creating the Delete task to delete the Job History after exporting the Job History. When storing the Job History isn’t required the Export task can be skipped.

Configure the same settings in the Delete tab.
Select All Agents from the agent dropdown list and set the period to 2 months.

When using the Export task before the Delete task it’s recommended to create a condition on the Delete task. We create a condition to make sure when the Export fails the Delete task will not execute and Job History could be lost.

Go to the Condition tab and select Add. From the list select the option Status of previously executed Task.

Configure the expression as below and select OK to continue.

Now we need to configure the condition. When the previously job is completed the task continues if the previously failed the delete task needs to skipped. Check the settings below how to configure the condition based on the created expression.

Last step is creating a recurring schedule.

Right mouse click the Module and select Schedule Job from the list.

Select an Agent close to the database (same subnet/same location). It’s not recommended to execute this job on a Dispatcher when agent is installed. This will increase the functionality of the Dispatcher. In this example the job is scheduled on an agent installed on the SQL Server.

Select the option Recurring from the dropdown list at the When option.

A new white field appears. Click in this field to create the recurring schedule.

When scheduling the job on monthly base there are 2 options available.
Every 1 month or Day of every month. In this example I use the Day of every month.
Configure the time when the system is not executing other recurring scheduled jobs or less jobs are scheduled.
And configure the Effective start to the first day of the next month.

Example of a recurring schedule is shown in the screenshot below.

Select OK to save the recurring schedule.

When multiple jobs are running during the schedule on the same agent it’s recommended to enable the option
Schedule in parallel with other jobs.

When the scheduling is configured and the agent is added select OK to continue. When finished a recurring job is added to Scheduling.

Below you find also the recording how to configure the Ivanti Automation maintenance.

Thank you for reading my blogs and hope to see you next week in another Tip of the Week. Next week we will discuss the Dispatcher WebAPI and Ivanti Automation Management Portal installed on the same server and the common issues.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.