1.8 File Retention Policy
Keeping unnecessary files makes locating files more difficult. Conversely, deleting files and asking questions later is not a sound policy either.
The first step in managing configuration files is finding out the local policy on file retention. If your office does not have a policy, contact your regional office. In the event no regional policy exists, follow the national recommendation:
According to the Hydrologic Support Branch, offices should keep patches and releases for a year, at least for now. The tar files for the builds and patches will also be available on the ftp site for about a year. Currently, the policy only covers install files.
Keep the patches and builds in the /awips/chps_share/install directory, with subdirectories named for the patch or the build (such as 35025_201102_patch.jar or OHD-CORE-CHPS-2.1.c).
Advantages of Removing Files
Removing clutter from the system has advantages for the people who maintain and troubleshoot the system and for the system itself. Getting rid of the clutter increases the processing speed of the system and decreases the frustration level of a focal point.
Personnel Advantages
CHPS Configuration Focal Points can locate the files they need more easily.
CHPS support personnel can investigate FogBugz tickets and identify solutions to the problems without sorting through unnecessary files.
System Advantages
The system runs more efficiently. Tasks complete quicker with fewer files to go through.
For example, if you retain tarred directories of all of the patches and installs (assuming two full builds and two patches per year), you are adding over 100 megabytes (MB) every year. Not a huge amount of space taken, but what if the practice of keeping every patch and build continues for five years?
Caution! Removing some files equates to a CHPS "show stopper" - the system will NOT function!
When in doubt, do not delete a file! Ask a focal point at another office or submit a FogBugz ticket before removing a file if you are uncertain!