cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1068
Views
5
Helpful
5
Replies

ArchivePurge jobs filling up /var/adm/CSCOpx

yjdabear
VIP Alumni
VIP Alumni

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?

1 Accepted Solution

Accepted Solutions

Joe Clarke
Cisco Employee
Cisco Employee

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.

View solution in original post

5 Replies 5

Joe Clarke
Cisco Employee
Cisco Employee

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.

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?

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

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?

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.

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:

Innovations in Cisco Full Stack Observability - A new webinar from Cisco