1 / 31

Elizabeth Chamberlain Mike Dickinson

Elizabeth Chamberlain Mike Dickinson. Buckinghamshire Chilterns University College. Disaster Planning. Or “Don’t panic Captain Mainwaring!”. Disaster Planning. Unix Sun Solaris System + Oracle Dbase Live & Test/Backup servers 200,000 items, 3 Branches (½ hour apart)

ewa
Download Presentation

Elizabeth Chamberlain Mike Dickinson

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. Elizabeth ChamberlainMike Dickinson Buckinghamshire Chilterns University College

  2. Disaster Planning Or “Don’t panic Captain Mainwaring!”

  3. Disaster Planning • Unix Sun Solaris System + Oracle Dbase Live & Test/Backup servers 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

  4. Reasons for Disaster Planning • 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

  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

  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

  7. Thoughts on the backup process • Do we need to have a system?

  8. Thoughts on the backup process • Do we need to have a system? • How long will the server be out of action

  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)

  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

  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

  12. Recovery Process • Unscheduled

  13. Recovery Process • Unscheduled • Put users on Standalone

  14. Recovery Process • Unscheduled • Put users on Standalone • Retrieve most recent full backup tape

  15. Recovery Process • Unscheduled • Put users on Standalone • Retrieve most recent full backup tape • Restore data to backup server

  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)

  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

  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

  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

  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

  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

  22. Restore Process • Scheduled

  23. Restore Process • Scheduled • Stop all activities – users on Standalone

  24. Restore Process • Scheduled • Stop all activities – users on Standalone • Run full backup

  25. Restore Process • Scheduled • Stop all activities – users on Standalone • Run full backup • Restore data to live server

  26. Restore Process • Scheduled • Stop all activities – users on Standalone • Run full backup • Restore data to live server • Modify server specific settings back

  27. Restore Process • Scheduled • Stop all activities – users on Standalone • Run full backup • Restore data to live server • Modify server specific settings back • Test

  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

  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

  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

  31. Potential banana skins • WorkFlows configuration • Opacs, Self-issue & other equipment • Communicate with users (live/backup) • Test & document then test & document • Report suspension

More Related