Clearing disk space on the Voyager server
List of directories to consider clearing files from when server disk space is running low and additional disk space is needed.
- Product: Voyager
- Product Version: All
- Relevant for Installation Type: Local
Question
Where can files be safely removed or deleted to clear or clean up disk space on a Voyager server?
Answer
Always use caution when deleting any files and be sure of backups
Contact Voyager Support if uncertain which files may be removed
Clearing or clean-up of unnecessary files from the Voyager server, especially when disk usage exceeds 80% will help prevent a number of down system scenarios.
The following directories may contain files which can be safely deleted from the Voyager server. Review files before deleting to be sure they are no longer useful/necessary.
Where xxxdb is the Voyager Database Instance
Directory | What to remove |
---|---|
/m1/incoming/ | Remove any tar.gz files and any directories named V### with a version older than the current version and any files ending in Linux-x86-64.zip older than the current version |
/m1/incoming/dbe/ | Remove any unneeded .dmp files |
/m1/incoming/v###/UTILITY | All contents of this directory may be removed. |
/m1/upgrade/ | Remove files and directories that are more than 30 days old |
/m1/incoming/regen/ | Remove all subdirectories for old regens except for the most recent subdirectory. |
/m1/voyager/utility/200#.#.#/xxxdb | Remove files from old regens that were not deleted. |
/m1/voyager/tmp | Remove large, and old files especially import files from webadmin. |
/m1/voyager/clients | Remove directories from older versions |
/m1/voyager/xxxdb/tmp | Remove any old/unnecessary reports and files. |
/m1/voyager/xxxdb/dump | Remove old/unneeded FPC backup files |
/m1/voyager/xxxdb/log | Remove old/unneeded log files |
/m1/voyager/xxxdb/rpt | Remove old/unneeded files. Archive/remove deleted.xxx.marc, discard.xxx.marc, replace.xxx.marc, and delete.item if very large. |
/m1/voyager/xxxdb/gdc | Remove old/unneeded marc, id, and log files from previous runs of GDC. (Preferred method is to delete from GDC client application) |
/m1/voyager/xxxdb/local | Remove any patron load files and/or bulk import files, no longer needed. |
/m1/voyager/xxxdb/local | Remove any patron load files and/or bulk import files, no longer needed. |
/m1/voyager/xxxdb/primo/Publishing/bundled | Remove files older than 90 days |
- Article last edited: 09-Mar-2016