1 / 26

A Disaster Planning Case Study

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

garth-daniels
Télécharger la présentation

A Disaster Planning Case Study

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. A Disaster Planning Case Study For PALnet's joint Integrated Library System Stephanie John, PALnet Mark Evans, PALnet Roy Teahen, Baker College

  2. 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

  3. 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

  4. Top 10 causes of data loss

  5. The consequences of failure Trust Perceived competency and value Goodwill – the ‘emotional bank account’ Revenues Faculty time and effort ‘Votes’ at budget time

  6. What is PALnet? Baker College Kettering University Mott Community College PALnet Governing Board recommendations PALnet Advisory Committee (library directors) PALnet Director

  7. PALnet

  8. Playing well with others • Baker CIS • Mott ET and IT • Kettering IT • Lapeer Public Library

  9. 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

  10. 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)

  11. 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

  12. Identify priorities Your needs AND your users’ needs • Firewall data • Horizon database • Horizon server & OS • Remote Patron Authentication (RPA) data • Online Catalog (HIP) configuration

  13. Evacuation Take: • Backup tapes • Laptops • Paper licensing file • Vendor contract(s) • Service Express agreement and contact info • Network diagram • Contact info: personnel, insurance, consortia

  14. 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

  15. Where will you move? • Baker College Flint Library • Baker College Auburn Hills campus – Library

  16. Fire • Where is your extinguisher? • Where is your alarm? • Is there a special phone #? • PRACTICE

  17. 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

  18. Power • UPS protection • Backup generators & testing

  19. A/C and temp monitoring • A/C unit evaluation • Temp alarms • Temp monitoring • Auto shut-down for temp alerts • Campus security and alarm monitoring

  20. Backup Internet • Backup Internet connections • Global Crossing • Backup fiber ring • Router reconfigurations

  21. 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

  22. 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

  23. 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

  24. 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

  25. 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/

  26. 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

More Related