1 / 17

Techniques for Voyager Disaster Recovery and Business Continuity

Techniques for Voyager Disaster Recovery and Business Continuity. Christopher Manly Coordinator, Library Systems and Discovery Services Cornell University Library Information Technology. Saving your data (and maybe your bacon). Context Business continuity concepts Cornell’s approach

kaiya
Download Presentation

Techniques for Voyager Disaster Recovery and Business Continuity

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. Techniques for Voyager Disaster Recovery and Business Continuity Christopher Manly Coordinator, Library Systems and Discovery Services Cornell University Library Information Technology

  2. Saving your data (and maybe your bacon) Context Business continuity concepts Cornell’s approach Finding the right solution

  3. Context: Cornell Library Private R1 University Voyager supports 17 unit libraries 8 million volumes 125 Librarians, 312 staff 3.5 million visits per year 880,000 circulations per year

  4. Context: Cornell IT environment • CUL has good relationship with central IT • Solid systemadmin support • Mature & extensive SAN environment • Multiple data centers on-campus • Centralized tape backup service • Oh, and I used to be one of “them”, which helps.

  5. Business Continuity & Disaster Recovery • What kinds of disaster do you anticipate? • Fat fingers • Hardware failures • Power outages • Disease outbreak • Natural disaster • More readiness = more cost

  6. Business Continuity • Disasters happen • Just because it hasn’t happened to you yet, doesn’t mean it won’t. • No, really. It will. • When (not if) disaster strikes, • How long can you be down? • How much data can you lose?

  7. Secret bonus A well-built BC approach will make non-emergency maintenance and upgrades easier, too

  8. BC Metrics • Recovery Time Objective (RTO) • The time it takes you to detect, respond, and get things up and running again • Recovery Point Objective (RPO) • The amount of time going backwards from the event to your latest safe data capture.

  9. Develop a Business Continuity Strategy • Determine your desired RTO and RPO • Develop an approach and assess costs • Re-architect or revise targets as needed • Lather, rinse, repeat

  10. Cornell’s approach – original design • Triple mirror of Voyager database • Solaris, disksuite, UFS • Split 1 mirror weekly to make snapshot for backups • Keep 3rd mirror separate • Back up archive logs in between

  11. Cornell’s approach – current design Mirrored across buildings on SAN ZFS snapshot for backup Test server in other datacenter Second on-disk copy replicated on test server

  12. What does this give us? • RPO of 2 hours • We back up the archive logs every 2 hours so the most data loss we can suffer is 2 hours’ activity • RTO of 4 hours for most scenarios • Unless we lose both buildings • We may choose to take a longer downtime in some circumstances

  13. What can you do? Backups Work with IT Explore technologies

  14. Backups Do you have them? Are they automated? Have you tested a restore lately? How about an on-disk copy?

  15. Working with IT • Talk to them before the crisis • Build a relationship • Lunch is a good thing • Don’t specify technology • Do specify your parameters

  16. Explore technologies • Vendors will sell you anything if you have money to throw at the problem • Free/cheap solutions abound • Rsync • OS level snapshots

  17. Go forth and recover… Assess your needs Make a plan Put it together Test it out

More Related