Elizabeth Chamberlain Mike Dickinson Buckinghamshire Chilterns University College

  • View
    214

  • Download
    1

Embed Size (px)

Transcript

  • Slide 1
  • Elizabeth Chamberlain Mike Dickinson Buckinghamshire Chilterns University College
  • Slide 2
  • Disaster Planning Or Dont panic Captain Mainwaring!
  • Slide 3
  • Disaster Planning Unix Sun Solaris System + Oracle Dbase Live & Test/Backup servers Live & Test/Backup servers 200,000 items, 3 Branches ( hour apart) 200,000 items, 3 Branches ( hour apart) Reasons for a Disaster Recovery plan Disasters we have (nearly) had! Thoughts on the backup process Process of recovery/restore Potential banana skins Open forum
  • Slide 4
  • Reasons for Disaster Planning Business continuity the disaster always happens in the wrong place at the wrong time! Business continuity the disaster always happens in the wrong place at the wrong time! To avoid headless chicken condition Risk assessment is being carried out throughout the organisation Validation from external bodies Previous disasters or near disasters To improve communication to users
  • Slide 5
  • Disasters we have (nearly) had! 3 July 2003 Partial power failure in main machine room. 10 July 2003 Complete air conditioning failure in main machine room 26 August 2003 Nachi virus struck BCUC 6 January 2004 Complete power failure
  • Slide 6
  • Implications of these events BCUC cut off from the outside world (some for several days) Key contact & address data not available (mainly during power failure events) Need to run key business processes e.g. payroll, BACS run General inconvenience
  • Slide 7
  • Thoughts on the backup process Do we need to have a system?
  • Slide 8
  • Thoughts on the backup process Do we need to have a system? How long will the server be out of action
  • Slide 9
  • Thoughts on the backup process Do we need to have a system? How long will the server be out of action Understand the time required (test)
  • Slide 10
  • Thoughts on the backup process Do we need to have a system? How long will the server be out of action Understand the time required (test) Understand your backup regime
  • Slide 11
  • Thoughts on the backup process Do we need to have a system? How long will the server be out of action Understand the time required (test) Understand your backup regime Plan the detail Recovery Process
  • Slide 12
  • Unscheduled
  • Slide 13
  • Unscheduled Put users on Standalone
  • Slide 14
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape
  • Slide 15
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape Restore data to backup server
  • Slide 16
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape Restore data to backup server Modify server specific settings (e.g. iLink url, Opac urls, Wf config, Self-issue)
  • Slide 17
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape Restore data to backup server Modify server specific settings (e.g. iLink url, Opac urls, Wf config, Self-issue) Run missed reports + other actions
  • Slide 18
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape Restore data to backup server Modify server specific settings (e.g. iLink url, Opac urls, Wf config, Self-issue) Run missed reports + other actions Test
  • Slide 19
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape Restore data to backup server Modify server specific settings (e.g. iLink url, Opac urls, Wf config, Self-issue) Run missed reports + other actions Test Upload Standalone transactions
  • Slide 20
  • Recovery Process Unscheduled Put users on Standalone Retrieve most recent full backup tape Restore data to backup server Modify server specific settings (e.g. iLink url, Opac urls, Wf config, Self-issue) Run missed reports + other actions Test Upload Standalone transactions Return to normal operation
  • Slide 21
  • Approximate Timings Standalone/retrieve backup tape hour Restore data to backup server 2-4 hrs Modify settings & run reports -2 hrs Testing hour Uploading standalone data hour Total 3 - 7 hours Total 3 - 7 hours
  • Slide 22
  • Restore Process Scheduled
  • Slide 23
  • Scheduled Stop all activities users on Standalone
  • Slide 24
  • Restore Process Scheduled Stop all activities users on Standalone Run full backup
  • Slide 25
  • Restore Process Scheduled Stop all activities users on Standalone Run full backup Restore data to live server
  • Slide 26
  • Restore Process Scheduled Stop all activities users on Standalone Run full backup Restore data to live server Modify server specific settings back
  • Slide 27
  • Restore Process Scheduled Stop all activities users on Standalone Run full backup Restore data to live server Modify server specific settings back Test
  • Slide 28
  • Restore Process Scheduled Stop all activities users on Standalone Run full backup Restore data to live server Modify server specific settings back Test Upload Standalone transactions
  • Slide 29
  • Restore Process Scheduled Stop all activities users on Standalone Run full backup Restore data to live server Modify server specific settings back Test Upload Standalone transactions Return to normal operation
  • Slide 30
  • Approximate Timings Run full backup 1 hour Restore data to live server 2-4 hrs Modify settings hour Testing hour Uploading standalone data hour Total 4 - 6 hours Total 4 - 6 hours
  • Slide 31
  • Potential banana skins WorkFlows configuration Opacs, Self-issue & other equipment Communicate with users (live/backup) Test & document then test & document Report suspension