1. Business Continuity For busy IT people GOETEC seminar 16 th February 2012

2. A bit about me David Hayling

3. Kent MAN operations manager for 10 years

6. – Microwave radio links(rain, trees) – ATM(LANE, clock) – BT circuits, first wavestream(spares) The BT ‘excuse book’(back breaking)

7. Christ Church Infrastructure Manager – One or two interesting experiences

8. Christ Church Infrastructure Manager – One or two interesting experiences flood, fire, pestilence … …

9. electricity

11. Business Continuity

12. Why

13. Things go wrong

14. “In theory, theory and practice are the same. In practice, they are not.” Albert Einstein

15. Things go wrong

21. City University fire 2001 “ Around 300 people had to be evacuated from City University's college building in central London last night, after a fire gutted the roof and fourth floor offices. ” [guardian, Tuesday 22 May 2001]

22. City University fire 2001 “ Around 300 people had to be evacuated from City University's college building in central London last night, after a fire gutted the roof and fourth floor offices. Students continued to sit their examinations today. ” [guardian, Tuesday 22 May 2001]

23. Causes of outage BCS – BC in practice

24. Causes of outage BCS – BC in practice

25. UCISA Top Concerns

27. Networking Risks

28. Five golden rules of business continuity British Computer Society

29. Understand the business requirements

32. – Institutional DR / BC plan – Make friends with the auditor – Insurance officer – Check with fellow service providers Estates – Senior managers – Your manager

33. Commit time and effort from across the business

34. Internal communications is critical

35. Documentation should match the organisation

36. Test the plan

37. Five golden rules Understand the business requirements Commit time and effort from across the business Internal communications is critical Documentation should match the organisation Test the plan

38. Hardware fault BCS – BC in practice

39. Hardware fault BCS – BC in practice

40. Hardware fault Look at your key business systems – Network – AAA – Key services – web, mail, teaching

41. Hardware fault Identify single points of failure – Risk asses – Mitigate / accept – RAID 1,5, 10, … – SAN – Virtualisation

42. Hardware fault www.brentozar.com Hierarchy of Database Needs

43. Hardware fault Test your backups – Can you recover the data – How long does it take Maintenance contracts – What do they cover – just break/fix – replacement Cold spares – Check you can deploy

44. Human error BCS – BC in practice

45. Human error BCS – BC in practice

46. Human error BCS – BC in practice

47. Human error Change control – Don’t change unless you know (and have written down); why, what, when, to what, who to tell, what success looks like, backout plan, test plan Working mobile phones – Normally used

48. Software malfunction BCS – BC in practice

49. Software malfunction BCS – BC in practice

50. Software malfunction BCS – BC in practice

51. Software malfunction Follow supplier’s patching plan – Do not compromise Automated tests – Test the actual service – (e.g. Nagios)

52. Software malfunction Anti-virus – Keep up to date automatically – Check all vectors – Beware false positive User behaviour training – Spear phishing – Have a response – Make sure CERT contacts are up to date

53. Site disaster BCS – BC in practice

54. Site disaster BCS – BC in practice

55. Site disaster BCS – BC in practice

56. Site disaster Consult with estates – What is their plan wrt site loss Telco circuit faults are rare <5% SPF Acute & long time to recover – vs – Acute quick to recover – vs - chronic

57. You’re already doing Business Continuity Just document, review, improve

58. “In theory, theory and practice are the same. In practice, they are not.” Albert Einstein

59. The Practice of System and Network Administration – Thomas A. Limoncelli, et al

60. Links & credits UCISA, BCS, JANET(UK), Gartner Harvey Rutt & Adrian Pickering (ECS, Southampton University) Brent Ozar (www.brentozar.com) david.hayling@canterbury.ac.uk