When a new System Update, PRU, etc,. Is available (Baselined) in ZCC, the old system-update (folder and GUID) that it's replacing should be removed from the /var/opt/novell/zenworks/content-repo/system-update directory to free up space. It could perhaps leave behind just the meta-data in case it is scanned for needing that prior update but the bulk of the space should be reclaimed. What's in the system-update in ZCC should match what's in the /var/opt/novell/zenworks/content-repo/system-update directory

Thank you,

Comments

  • Seems like the in-ZCC list cleanup is better now (2017U1) than it has been at the past, but I agree that one can find a lot of dead updates consuming space in content-repo; cleaned out 10 PRUs and 3 ancient updates for a customer recently.