|
|
HOME | About PALNI | PALNI OPAC | Digital Library | Recent News |
|
|
Earlham . Franklin . Goshen . Grace . Hanover . Huntington Manchester . Marian . Oakland City . St Francis . St Josephs St Meinrad . Taylor . Trine . U of Indianapolis . Wabash |
User loginOPAC Quick Search |
PALNI System Uptime Statistics for 2007Submitted by admin on Fri, 01/04/2008 - 2:25pm.
PALNI staff use system monitoring software to monitor and automatically log whether our Ex Libris Aleph system is online and operational at 15-minute intervals throughout the day. If the PALNI system is down for any reason, an "on-call" member of the PALNI staff is automatically paged so that any problem can be resolved quickly. We have completed a review of our system monitor system log file for the 2007 calendar year. It shows that we experienced a total of 8.5 hours of unplanned Aleph system downtime during 2007. In addition, we scheduled a total of 9.25 hours of planned downtime over the 12 months for Aleph Service Pack installations and for other routine planned system maintenance activities.
As the Aleph downtime table shows, staff kept the PALNI system online and operational for over 99.9% of the approximately 8600 scheduled hours of PALNI system operation during the 2007 calendar! That is a significant achievement for a complex system like PALNI's that is routinely kept online on virtually a 24 hrs x 7 days per week basis. NOTE: Individual campuses may have experienced slightly more downtime than shown in the table due to local campus issues. Downtime due to campus LAN or Internet problems is not recorded if the PALNI Aleph system itself is online and operational. Also note that the table does not reflect approximately 15 minutes each night, from 2:00am to 2:15am when the PALNI system is routinely reset as part of our nightly system maintenance procedures. printer friendly version | 205 reads
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||