cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
458
Views
0
Helpful
1
Replies

RME 4.2: how to schedule the purge of the history of PurgeJobs ?

Martin Ermel
VIP Alumni
VIP Alumni

beside the fact that the job and report history in RME can fill-up a lot of space in RME db, it has an impact on some other points as well (e.g. long loading of RME Home page). So it is a good thing to configure job and report purging in

RME > Admin > System Preferences > Job Purge

When this feature is enabled for every listed item on that page to let it run periodically, the jobs will be handeled very differently.

They all run at the scheduled time - there is no difference - but some of them keep a history of their run, i.e. they are scheduled as an instance of the original job - which I think reverts the original idea behind...

Or did I miss something and someone tell me where I can configure the schedule to purge the history of these purge jobs? Or do I just not understand the GUI?

In my opinion, at least the following jobs are affected:

as they are listed with different descriptions in CS > Server > Admin > Job Browser and in RME > Admin > System Preferences > Job Purge I list both descriptions:

Jobs which keeps ....

instances of Jobs:

JobID - CS - RME

1017 - CDAPurgeJob - Credential Verification Jobs

1040 - ReportJobPurge - Reports Jobs

1042 - ReportArvPurge - Reports Archives

no instances of Jobs:

1021 - PURGEJOB - Software Management Jobs

1024 - PurgeJobNetConfigJob - Netconfig Jobs

1026 - PurgeJobArchiveMgmt - Archive Management Jobs

1028 - PurgeJobArchiveUpdate - Archive Update Jobs

1030 - PurgeJobArchivePoller - Archive Poller Jobs

1032 - PurgeJobArchivePurge - Config Archives

1034 - PurgeJobConfigEditorJob - Config Editor Jobs

1036 - PurgeJobCwConfig - ConfigCli Jobs

1044 - PurgeJobNetShow - Netshow Jobs

Instances, but History seems to be deleted like the policy:

1033 - ICServerPurgeJob - Inventory Collector Jobs

1039 - InvPollerPurgeJob - Inventory Poller Jobs

jobId not in RME but listed in CS with Instances starting with xxxx.1

1018 - CDAPurgeJob [duplicate of 1017 ?]

1038 - ReportJobPurge [duplicate of 1040 ?]

1041 - ReportArvPurge [duplicate of 1042 ?]

1 Reply 1

Joe Clarke
Cisco Employee
Cisco Employee

You are correct, purge jobs shouldn't be creating instance trails as there is no one to purge the purgers. This wouldn't be the first inconsistency with RME purge jobs. I suggest you work with TAC to get a bug filed on this.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: