- Article Type: Q&A
- Product: Voyager
- Relevant for Installation Type: Local;
What common tasks are required in order to maintain my Voyager system and keep it running smoothly?
- Maintaining, and testing the quality of backups is an obligation.
- Ex Libris installs a default backup script that stops the software, takes a disk snapshot, starts the software, then writes the snapshot to tape
- Alternate backups are allowed, and Ex Libris recommends that backups are: run nightly, full, and cold
- While many applications can be run indefinitely in linux/unix without issue, periodic reboots of the Voyager server are mandatory to ensure correct functionality.
- Recommended: Daily reboot of server.
- Minimum: Weekly restart of Oracle, and Voyager application.
- Keyword regens are a periodically required maintenance procedure. Frequency depends on usage and database size.
- Failing to run a regen when required, will result in slower search performance, or the failure of the search to retrieve all relevant records.
- A regen is required if a bulk import is conducted without keyword indexing.
- A regen is required if the size of the dynamic index file is greater that half the size of the largest static index file.
Rotate Logs/Monitor Disk Space
- Monitor disk space usage using df -h /m1. If /m1 usage is >80% Ex Libris recommends taking measures to clear or add disk space.
- Rotate OS and Voyager log files on a regularly or automation rotation. Maintaining logs on the system for >14 days is usually not neccesary.
- If log.voyager becomes 2 GB or larger in size, Voyager application componenets associated with this log will fail to start.