260 likes | 371 Views
A Disaster Planning Case Study. For PALnet's joint Integrated Library System. Stephanie John, PALnet Mark Evans, PALnet Roy Teahen, Baker College. TODAY’S GOALS. Something for every level Examples of inter-agency cooperation Real-life examples to tickle your brain
E N D
A Disaster Planning Case Study For PALnet's joint Integrated Library System Stephanie John, PALnet Mark Evans, PALnet Roy Teahen, Baker College
TODAY’S GOALS • Something for every level • Examples of inter-agency cooperation • Real-life examples to tickle your brain • Concerns unique to e-libraries • Learning from each other NOT INCLUDED: IT basics like backups, log analysis, antivirus
Communication disasters • 70% - by people cable cuts, work errors, vandalism & sabotage 15% - equipment failure software, power loss, circuit board failures • 10% - environment related loss of a/c, excessive humidity • >5% - natural causes tornadoes, flood, fire & lightning
The consequences of failure Trust Perceived competency and value Goodwill – the ‘emotional bank account’ Revenues Faculty time and effort ‘Votes’ at budget time
What is PALnet? Baker College Kettering University Mott Community College PALnet Governing Board recommendations PALnet Advisory Committee (library directors) PALnet Director
Playing well with others • Baker CIS • Mott ET and IT • Kettering IT • Lapeer Public Library
Insurance • Read EXCLUSIONS carefully • Usual: $0 for data reconstruction • Data insurance • Business interruption insurance • Business continuity coverage • Pay vendor for ASP hosting? • Pay for move to backup site? • Principle of mitigation • Discounts available for good prep
Hardware maintenance contracts • Single item based response time • 24/7/365 for critical • 4 or 8 hour for others • Service person permanently assigned to your account • System monitoring optional • Parts and spares kept locally • Site moves (post-disaster)
Start SIMPLE • Paper and online phone trees • PALnet staff • Building staff • Agency directors • Baker CIS, Security • MCC and KTU IT Adv Comm members • Baker Clinton Twp director contact information • Service bureau • Major vendor (SirsiDynix) • OCLC, MELCat, other partners
Identify priorities Your needs AND your users’ needs • Firewall data • Horizon database • Horizon server & OS • Remote Patron Authentication (RPA) data • Online Catalog (HIP) configuration
Evacuation Take: • Backup tapes • Laptops • Paper licensing file • Vendor contract(s) • Service Express agreement and contact info • Network diagram • Contact info: personnel, insurance, consortia
Mirrored data on remote • IP range data for all agencies • Password list for systems • Firewall info • Most recent images of servers • Photos & inventory of all equipment, furnishings • Photos of offices, server room • Copies of contact lists • Copy of: http://www.techsoup.org/katrina/ITRecoveryManual_vI.pdf
Where will you move? • Baker College Flint Library • Baker College Auburn Hills campus – Library
Fire • Where is your extinguisher? • Where is your alarm? • Is there a special phone #? • PRACTICE
Supplies • Tool kit(s) • Wrist strap(s) for static • Plastic sheeting • Trash bags • Fans • USB drives – easy to share common files before network restored • FLASHLIGHTS
Power • UPS protection • Backup generators & testing
A/C and temp monitoring • A/C unit evaluation • Temp alarms • Temp monitoring • Auto shut-down for temp alerts • Campus security and alarm monitoring
Backup Internet • Backup Internet connections • Global Crossing • Backup fiber ring • Router reconfigurations
Internet Internet Internet Flint Clinton Twp Muskegon Cass City Fremont Port Huron Cadillac Sandusky Jackson Owosso Coldwater Auburn Hills Allen Park West Branch Baker WAN
Unique to libraries • Licensing of e-books: Choose vendors carefully • Alternate access to databases for when auto-authentication down RPA, Ezproxy, squid • RPA can authenticate against a flat file, output from db • Offline circulation software • Partnerships/collection sharing
ILS vendors • ILS = Integrated Library System • Vendors or 3rd parties offer service bureaus • Use service bureau as backup facility • Establish basic profile, test backup tapes • Run circulation from remote vendor site until local server restored
Single site disaster • Closing a single library site • Stop fines • Keep materials out of shared catalog • Suspend overdues & bills • Verify items are not showing in public catalog • Holds disallowed
Other Resources • EZProxy URL rewriter http://www.usefulutilities.com/ • Remote User Auth in Libraries http://library.smc.edu/rpa.htm Nagios service and network monitoring http://www.nagios.org/
Other Resources • Disaster Recover Journal’s Sample Plans and Outlines http://www.drj.com/new2dr/samples.htm • University and Library Disaster Plans http://palimpsest.stanford.edu/bytopic/disasters/plans/ TechSoup:Restoring IT Infrastructure http://www.techsoup.org/katrina/ITRecoveryManual_vI.pdf