c




   




ë Step 1 - Send flowers

ë Step 2 - Invoke the detailed plan that you already had in

place to ensure continuance after just such an
occurrence

ë Step 3 - Business as usual

ë Ôr«.., if you 
 have a Disaster Recovery

plan in place«

Start the arduous task of putting a puzzle back

together with many of the pieces missing

«and accept the fact that you¶re going to lose

time, money, reputation and clients.

¦ ¦
  




ë D
S about lack of Disaster Recovery

Planning

ë Understanding the impact to your business

ë PES of Disaster

ë SEPS to protect our business

ë Questions

º º
 D !
 
"
#
!
 
"
#

ë fter the incident of the World rade
enter, º$

of the companies without disaster recovery
capability were out of business within 6 weeks
[Dorbes Aagazine]

ë In fact, º$ of enterprises that experience 

disaster go out of business within five years.
[Gartner]

ë Enterprises can improve those odds ± but | 
if

they take the necessary measures before and
after the disaster.

O O
 D !
 
"
#
!
 
"
#

ë Dile corruption and data loss are becoming

much more common

ë It costs the average company between

]
] per year for desktop
oriented disasters (both hard and soft costs)

th Annual ICSA Lab's Virus Prevalence Survey, March 2002

 
 c


 %
&



 %
&

§ Disaster recovery is a series of actions to be taken in

the event of major unplanned outages to minimize
their adverse effects.
± Power failure
± Underground cable cuts or failures
± Dire, flood, earthquake, and other natural disasters
± Aistakes in system administration
± Sabotage (intentional, virus, hacking, internal/external)
± Loss of employee
 c 

 

 %



 

 %


§ We typically think of:

ë How to backup and restore data to computer

systems
ë How to restore network connections
ë How to replace computers and where to put them
ë Where employees can work if the building is
damaged

 
 

 %
 "


ë plan to restore all of these components must be in

place.

ë he system must be able to put them back together

if your business is to survive a disaster.

ë he efficiency with which this is done may make the

difference in surviving or not!

â â
  '
 (!
') &

ë Potential pitfall - Disaster Recovery focusing only on the

technical components.

ë
onsider the impact of the following:

± Lost productivity and idle employees

± Aissed service level agreements
± Diminished reputation for customer service
± Increased technical support costs for onsite repair
± Loss of customer confidence
± Legal liabilities
± Regulatory fines
± Downward stock prices
± « and more

i i
 ½   
 "


ë Instead of Computer Disaster Recovery, think in terms of

½   
 "


ë B
P is more comprehensive. It addresses:

ù Risk of lost revenue and productivity

ù Plan of action for continuing the business, NÔ computers

ii ii
 ½   
 "


Example of items that typical planning might leave out:

ë Business processes and procedures

ë Roles and responsibilities
ë What happens at the absence of key individuals
ë Sources and consumers of data
ë Recovery time-frame requirements
ë Ôrder of recovery
ë Documented procedures
ë Reconstitution

i
i

 ½  "
  
"
 

½   "
  
"
 


Business Processes and Procedures are:

ë Rarely documented

ë ypically defined only in the combined knowledge

of key employees
(his is true of the ³big picture´ as well as for the details of
each departmental process)

ë Ône of the most difficult things to put back

the if key employees are not available
 ½   
  
½    
  

ritical time is lost without pre-defined roles and

responsibilities for:

ë Aaking the decision to invoke the plan

ë he second in charge

ë Being responsible for each element of the plan

ë Exception handling

ë Decisions of priorities

ë Signature authority

iº iº
 ½  * %

½   * %


bsence of key individuals

ë more difficult thing to consider

ë Aental notes

ë Revenge (sabotage or withholding of information)

iO iO
 ½  

D'
½   

D'

Sources and
onsumers of Information

ë Detailed data flow

ë Detailed process flow

ë Updated documentation

i i
 ½   %
) D

) 
½    %
) D

) 

Recovery ime-frames and Ôrder

ë Set expectations up-front

ë Help to design budgets

ë ssign priorities for recovery

i
i

 ½   ) 

½    ) 


Documentation

ë
reate documentation so that a contractor can

restart your business

ë
reate policies and procedures for updating

i i
 ½    
½     

Reconstitution

ë When is disaster over?

ë How to go back to business as usual?

ë What steps need to be taken?

iâ iâ
 ½   
 "


ë We¶ve talked about things that are commonly

left out...

ë Now the things that typical planning ³almost

always´ leaves out

§ Aental notes
§ Periodic testing
§ Updating procedures and plan content
§ Aoving DR Planning to the DR Site
§ Details, Details, Details!

 ½  + 


½   + 
  

Aental Notes

³Steve knows how to do that´

But what if Steve isn¶t here?

ë Aost common obstruction

ë
an involve relationships, passwords, technical

understanding, history, contractual obligations«

ë Documentation will never be perfect

i
i
 ½   
 ) 

½    
 ) 


esting and Updating

ë 32% of all data lost is due to human error

ù We¶re all busy, so why take the time to work on

something that we can put off and we probably
won¶t use anyway?
ù³I¶ll have time to do it tomorrow´
ù ³It¶s someone else¶s responsibility´

ë We¶ve seen too many people that have lost data that they
³wish they would have taken the time´ to safeguard!

 ½   


Aoving Planning to the DR Site

ë he same disciplines must be put into practice

at the DR site.

¦
¦
 ½   
 "


method is needed that will:

ë Bring knowledge together

ë Document it

ë Enable processes to be reconstructed (possibly without

the help of key employees)

ë Enforce periodic testing and updating of the plan

º
º
 ½   
 "
! ))



ontinuance Planning defines and documents

ë Departmental processes
ë Sources of data
ë
onsumers of data
ë Relationships
ë
ost ramifications
ë Budget justifications
ë Recovery criteria
ë Solution design
ë Documentation
ë ssistance with testing and updating
 ½   
 "
! ))



Planning is approached in phases

ë Process nalysis
§ Data flows

ë Risk nalysis
§
osts/Effects

ë Disaster Recovery Planning

§ raditional technical component

ë Implementation and esting

§ nnual or after significant changes



 ½   
 "
! ))



ontinuance Planning can be implemented:

ë Departmentally
ë In phases
ë s a single phase
ë o practical extents

 hank You!

Questions?

Rob Didlake Aary Linse

913-780-2525 913-971-6863
rob@dataedge.net mlinse@olatheks.org