ArchivePurge jobs filling up /var/adm/CSCOpx

Answered Question
Jun 11th, 2007

It seems every ArchivePurge job takes up >900MB disk space, so it ends up consuming over 5GB with jobs 1-48. How to safely free up the disk space and limit the space usage?

I have this problem too.
0 votes
Correct Answer by Joe Clarke about 9 years 5 months ago

Purge the jobs ;-). Seriously, you should first delete all completed ArchivePurge jobs using the RME Job Browser, or the Archive Mgmt Job Browser to quickly free up space. Moving forward, check to make sure all of your debugging is disabled under RME > Admin > System Preferences > Loglevel Settings (click the Default button to be sure).

Finally, add a schedule to purge archive purge jobs under RME > Admin > System Preferences > Job Purge.

  • 1
  • 2
  • 3
  • 4
  • 5
Overall Rating: 5 (2 ratings)
Loading.
Correct Answer
Joe Clarke Mon, 06/11/2007 - 09:40

Purge the jobs ;-). Seriously, you should first delete all completed ArchivePurge jobs using the RME Job Browser, or the Archive Mgmt Job Browser to quickly free up space. Moving forward, check to make sure all of your debugging is disabled under RME > Admin > System Preferences > Loglevel Settings (click the Default button to be sure).

Finally, add a schedule to purge archive purge jobs under RME > Admin > System Preferences > Job Purge.

yjdabear Mon, 06/11/2007 - 09:59

All the Job Purge jobs are enabled, but with the default 180-day policy. Do you know what other jobs besides ArchivePurge have the potential of getting this huge?

Joe Clarke Mon, 06/11/2007 - 10:03

SWIM jobs can get large, as could inventory jobs with debugging enabled.

yjdabear Mon, 06/11/2007 - 10:09

Do "inventory jobs" include both Inventory Collector and Inventory Poller jobs?

I didn't have debug on for ArchiveMgmt. The only ones with debug on are Config Job and NetConfig. Does that explain the big ArchivePurge jobs?

Joe Clarke Mon, 06/11/2007 - 10:14

Inventory jobs just include the collector. Config Job debugging can make all config-related jobs big, so that would help explain the archive purge size. Netconfig debugging covers just the client, so that would make the netconfigclient.log big.

Actions

This Discussion