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

Business Continuity

  • Upload
    tanuja

  • View
    23

  • Download
    2

Embed Size (px)

DESCRIPTION

Business Continuity. For busy IT people GOETEC seminar 16 th February 2012. A bit about me. David Hayling. Kent MAN operations manager for 10 years. Kent MAN operations manager for 10 years Microwave radio links(rain, trees) ATM(LANE, clock) - PowerPoint PPT Presentation

Citation preview

Page 1: Business Continuity

Business ContinuityFor busy IT people

GOETEC seminar 16th February 2012

Page 2: Business Continuity

A bit about me

David Hayling

Page 3: Business Continuity

• Kent MAN operations manager for 10 years

Page 4: Business Continuity
Page 5: Business Continuity
Page 6: Business Continuity

• Kent MAN operations manager for 10 years– Microwave radio links (rain, trees)– ATM (LANE, clock)– BT circuits, first wavestream (spares)• The BT ‘excuse book’ (back breaking)

Page 7: Business Continuity

• Christ Church Infrastructure Manager– One or two interesting experiences

Page 8: Business Continuity

• Christ Church Infrastructure Manager– One or two interesting experiences

flood, fire, pestilence … …

Page 9: Business Continuity

electricity

Page 10: Business Continuity

electricity

Page 11: Business Continuity

Business Continuity

Page 12: Business Continuity

Why

Page 13: Business Continuity

Things go wrong

Page 14: Business Continuity

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

Albert Einstein

Page 15: Business Continuity

Things go wrong

Page 16: Business Continuity
Page 17: Business Continuity
Page 18: Business Continuity
Page 19: Business Continuity
Page 20: Business Continuity
Page 21: Business Continuity

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]

Page 22: Business Continuity

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]

Page 23: Business Continuity

Causes of outage

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 24: Business Continuity

Causes of outage

32%

14%

44%

7%

3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 25: Business Continuity

UCISA Top Concerns

Page 26: Business Continuity

UCISA Top Concerns

Page 27: Business Continuity

Networking Risks

Page 28: Business Continuity

Five golden rules of business continuity

British Computer Society

Page 29: Business Continuity

• Understand the business requirements

Page 30: Business Continuity
Page 31: Business Continuity
Page 32: Business Continuity

• Understand the business requirements– Institutional DR / BC plan– Make friends with the auditor– Insurance officer– Check with fellow service providers• Estates

– Senior managers– Your manager

Page 33: Business Continuity

• Commit time and effort from across the business

Page 34: Business Continuity

• Internal communications is critical

Page 35: Business Continuity

• Documentation should match the organisation

Page 36: Business Continuity

• Test the plan

Page 37: Business Continuity

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

Page 38: Business Continuity

Hardware fault

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 39: Business Continuity

Hardware fault

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 40: Business Continuity

Hardware fault

• Look at your key business systems– Network– AAA– Key services – web, mail, teaching

Page 41: Business Continuity

Hardware fault

• Identify single points of failure– Risk asses– Mitigate / accept– RAID 1,5, 10, …– SAN– Virtualisation

Page 42: Business Continuity

Hardware fault

www.brentozar.com Hierarchy of Database Needs

Page 43: Business Continuity

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

Page 44: Business Continuity

Human error

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 45: Business Continuity

Human error

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 46: Business Continuity

Human error

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 47: Business Continuity

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

Page 48: Business Continuity

Software malfunction

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 49: Business Continuity

Software malfunction

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 50: Business Continuity

Software malfunction

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 51: Business Continuity

Software malfunction

• Follow supplier’s patching plan– Do not compromise

• Automated tests– Test the actual service– (e.g. Nagios)

Page 52: Business Continuity

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

Page 53: Business Continuity

Site disaster

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 54: Business Continuity

Site disaster

32%

14%

44%

7% 3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 55: Business Continuity

Site disaster

32%

14%

44%

7%

3%

human errorsoftware malfunctionhardware faultcomputer virussite disaster

BCS – BC in practice

Page 56: Business Continuity

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

Page 57: Business Continuity

You’re already doing Business Continuity

Just document, review, improve

Page 58: Business Continuity

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

Albert Einstein

Page 59: Business Continuity

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

Page 60: Business Continuity

Links & credits

• UCISA, BCS, JANET(UK), Gartner• Harvey Rutt & Adrian Pickering (ECS,

Southampton University)• Brent Ozar (www.brentozar.com)

[email protected]