Aleph Disk Space issues - NYULibraries/ILS-Tech GitHub Wiki

On Mon, Feb 3, 2014 at 1:46 PM, Ryan DiFrancesco  wrote:
Hi Aleph admins,
 
The Aleph application volume on the new production server is currently 80% full:
 
# df -h /exlibris
Filesystem            Size  Used Avail Use% Mounted on
/dev/dm-3             296G  223G   58G  80% /exlibris
 
This is of great concern because we sized this volume according to ExLibris’ recommendations; in fact we significantly padded their recommendation.  Ideally, we should be in the 50% to 60% range.  The attached graphs tell us a few things:
 
1.     The month graph shows a steady increase in volume usage since going live on the new server.  If left unchecked with growth around 2% a week, the volume will fill up and crash the Aleph application before long.  Possible causes include:

a.     Application logs that are not being rotated and/or purged on a regular basis

2.     The year graph shows a spike in October which corresponds to when ExLibris deployed the Aleph Beta environment before it turned into the production environment.  My guess is that when ExLibris copied Aleph application files from the old server a significant amount of legacy files, backups, etc came with it.  I’ve compiled a preliminary list of files/directories that I think may be eligible for removal:

a.     https://docs.google.com/a/nyu.edu/spreadsheet/ccc?key=0Ao7z1Oainmv5dFY4bWZCU2l3YUxOSmpSWGk2RHBfa3c&usp=sharing

 
Please review the above items as soon as possible and confirm which content can be safely removed and if there’s a reason for continuous growth.  Also, a review of the application volume in effort to identify other content which can be removed would be helpful.  Thanks for your assistance with this issue.
 
Ryan

⚠️ **GitHub.com Fallback** ⚠️