9/11 - Respond and Recover: A Case Study Joy Heath-Porter Sidley Austin Brown & Wood LLP LawNet 2002 August 21, 2002.

Slides:



Advertisements
Similar presentations
The ePractice. Yesterday 1900s Word Processing about 30 words per minute.
Advertisements

Pamela Norris Project Manager Kraft Kennedy & Lesser, Inc.
Business Continuity/Disaster Recovery: Solutions For Firms Of All Sizes Atlas Lee, CBCP Director Of Business Continuity Atlas Lee, CBCP Director Of Business.
Copyright 2006 Mid-City Offices Systems. Busy people… How would your business be affected, if you suddenly lost all of your computer data? Rush through.
Martin County Emergency Management Agency. Is your business prepared to survive the economic impact of a major disaster? Are your company's valuable assets.
Presented at the 2006 CLEAR Annual Conference September Alexandria, Virginia Disaster Preparedness II: Planning for the Future By Deidre Gish-Panjada.
Business Continuity Training & Awareness by Sulia Toutai (ANZ)
SUNGARD PLANNING SOLUTIONS LESSONS LEARNED: SEPTEMBER 11 A Business Continuity Approach Barbara Allen SunGard Planning Solutions December 11, 2002.
Tony Lester August 2011 Consolidating, optimizing and safeguarding available IT resources and services in Tax Administration 1.
Networking Phone Systems Cabling and Wiring Server and Desktop Support Server and Network Virtualization Switches Routers and Hubs Hardware and Software.
Sharing Session: Business Contingency Plan (BCP) Big Flood Disaster
1 REFLECTIONS FROM GROUND ZERO: DISASTER PLANNING FOR COMPLIANCE (OR WHAT TO DO WHEN YOUR BUILDING FALLS DOWN) LINDA V. TIANO SENIOR VICE PRESIDENT AND.
Planning for the Future Disaster Recovery Plan / Business Continuity Plan Jim Zukowski, Ed.D. Texas State Board of Dental Examiners 2006 Annual ConferenceAlexandria,
Case Study: Business Continuity Planning for Site- Level Disaster Kimberley A. Pyles Northrop Grumman Corporation
Disaster Recovery Planning Because It’s Time! Copyright Columbia University and Bentley College, This work is the intellectual property of the author.
RETURN TO MAIN Surviving Disaster Presented by: Wayne Lyle, Project Manager Dilworth Paxson LLP Jenn Steele, Director of Information Technology Donovan.
What Can You Do Today?. Steps To Preparedness 1. Assess your risk – both internally and externally. 2. Assess your critical business functions. 3. Prepare.
DTCC Green DTCC’s Response to Super Storm Sandy Cecilia Humphrey Americas’ Representative, DTCC ACSDA General Assembly, April 2013 Antigua, Guatemala Special.
Integrating Educational Technology into the Curriculum
Ying Wang EDN 303 Fall Objectives Define curriculum-specific learning Explain the difference between computer, information, and integration literacy.
Backup Strategy. An Exam question will ask you to describe a backup strategy. Be able to explain: Safe, secure place in different location. Why? – For.
DISASTER CENTER Study Case DEMIRBANK ROMANIA “Piata Financiara” ConferenceJanuary 29, 2002 C 2002.
Public Librarians’ Response to Hurricanes: Lessons, Issues and Strategies Rebecca Hamilton State Librarian State Library of Louisiana.
Public Librarians’ Response to Hurricanes: Lessons, Issues and Strategies Rebecca Hamilton State Librarian State Library of Louisiana.
The Remote Workplace Designing, deploying, and supporting the remote workplace environment Presented by: John Milhoan Information Technology Cooperative,
Network and Server Basics. 6/1/20152 Learning Objectives After viewing this presentation, you will be able to: Understand the benefits of a client/server.
IT PLANNING Enterprise Architecture (EA) & Updates to the Plan.
Disaster Recovery Planning University of Utah. Presentation Overview  Lessons learned “In the wake of Katrina” by Louisiana State University  University.
Preservasi Informasi Digital.  It will never happen here!  Common Causes of Loss of Data  Accidental Erasure (delete, power, backup)  Viruses and.
Disaster Recovery and Business Continuity Ensuring Member Service in Times of Crisis.
IS Organization Peter E. Lesser Kraft Kennedy & Lesser (212) LawNet 2001.
Business Crisis and Continuity Management (BCCM) Class Session
Services Tailored Around You® Business Contingency Planning Overview July 2013.
November 2009 Network Disaster Recovery October 2014.
Legal Administration and Technology ©2007 Thomson Delmar Learning. ALL RIGHTS RESERVED. Chapter 2 Practical Law Office Management, 3 rd Edition, Thomson.
NGAC Interagency Data Sharing and Collaboration Spotlight Session: Best Practices and Lessons Learned Robert F. Austin, PhD, GISP Washington, DC March.
Elite Networking & Consulting Presents: Everything You Wanted To Know About Data Insurance* * But Were Afraid To Ask Elite Networking & Consulting, LLC,
IT Business Continuity Briefing March 3,  Incident Overview  Improving the power posture of the Primary Data Center  STAGEnet Redundancy  Telephone.
Security Baseline. Definition A preliminary assessment of a newly implemented system Serves as a starting point to measure changes in configurations and.
Dr.Backup Online Backup Service (888) (toll free)
HBCU National Workshop June 24, 2011 Disaster Recovery Reggie Brinson Assoc. VP/Chief Information Officer Clark Atlanta University.
DECS Community IT DIVISION OF ENGINEERING COMPUTING SERVICES Michigan State University College of Engineering.
Keeping you Running Part I Experiences in Helping Local Governments Develop Cyber Security and Continuity Plans and Procedures Stan France & Mary Ball.
Final Coverage Topic 4: INFORMATION RESOURCES and INFORMATION SYSTEMS By Dr. Faustino Reyes.
AT&T Response Terrorist Attack September 11, 2001 Presentation to NRIC V PJ Aduskevicz October 30, 2001 Presentation to NRIC V PJ Aduskevicz October 30,
BUSINESS AS USUAL. NO MATTER WHAT.. Business Continuity Is About The Future. BUSINESS AS USUAL. NO MATTER WHAT. The future of your family. The future.
Co-location Sites for Business Continuity and Disaster Recovery Peter Lesser (212) Peter Lesser (212) Kraft.
2012 MITA-ATA Annual Conference August 6-8, 2012 Disaster Recovery Planning for Telecommunications Companies.
PPD Computing “Business Continuity” David Kelsey 3 May 2012.
Preventing Common Causes of loss. Common Causes of Loss of Data Accidental Erasure – close a file and don’t save it, – write over the original file when.
Who Says Servers Can’t Crash? Rocky Mountain PBS Survives Multiple Server Crashes and Lives to tell about it! Presented By Michelle Nesmith Rocky Mountain.
ORGANIZING IT SERVICES AND PERSONNEL (PART 1) Lecture 7.
I NTRODUCTION TO N ETWORK A DMINISTRATION. W HAT IS A N ETWORK ? A network is a group of computers connected to each other to share information. Networks.
Chap 8: Administering Security.  Security is a combination Technical – covered in chap 1 Administrative Physical controls SE571 Security in Computing.
Introduction TO Network Administration
Disaster Recovery: Can Your Business Survive Data Loss? DR Strategies for Today and Tomorrow.
I NTRODUCTION TO N ETWORK A DMINISTRATION. W HAT IS A N ETWORK ? A network is a group of computers connected to each other to share information. Networks.
Disaster Recovery Management By: Chris Rozic COSC 481.
1 Recovering from Disaster Lessons learned in crisis management and communication Casualty Actuarial Society Enterprise Risk Management Panel May 21, 2002.
Ron Johnson, CFA Litman/Gregory Asset Management.
ALPA Information Technology Conference November 16-18, 2005.
And a great value too! We understand the importance of your data and the value of a full, fast and secure recovery. At Data Rescue MDs, our motto is “Lose.
Network and Server Basics. Learning Objectives After viewing this presentation, you will be able to: Understand the benefits of a client/server network.
It’s all about the dpisd dr plan
Atlas Lee, CBCP Director Of Business Continuity
Business Contingency Planning
Atlas Lee, CBCP Director Of Business Continuity
Atlas Lee, CBCP Director Of Business Continuity
Understanding Back-End Systems
Presentation transcript:

9/11 - Respond and Recover: A Case Study Joy Heath-Porter Sidley Austin Brown & Wood LLP LawNet 2002 August 21, 2002

Who are we? Large, multi-office, multi-national firm 14 offices; six countries 1,500 lawyers; 3,000 total personnel Two offices in New York before September 11; 600 person office in the North Tower of the World Trade Center

Status on September 10 Involved in one of the largest law firm mergers ever Two networks with different hubs Two different and document management systems Two different telephone systems

Status on September 10 (contd.) Same financial system, but on different versions with different database engine Still in the process of consolidating technology Had just moved equipment to WTC previous weekend

Brief Chronology 7:50 a.m. Tuesday - how we found out; first steps Mid-morning Tuesday - disaster recovery steering group assembled; began to map out recovery strategy Noon Tuesday - offsite storage provider contacted; arrangements made to drive tapes to Chicago

Brief Chronology (contd.) Throughout Tuesday - made sure phones were manned, so that staff calling in would have a live voice; determined status of our people; identified and arranged for recovery resources; Chicago and New York offices closed, but many staff members were working C.O.B. Tuesday - system recovery priorities established; servers identified for recovery

Brief Chronology (contd.) Tuesday night dial-in information numbers established and published; information made available via the Firms Web site; temporary space identified Wednesday morning - all offices contacted for spare equipment; arrangements made for rental equipment; PC vendor contacted for purchase of equipment; cabling began

Brief Chronology (contd.) Wednesday noon - Tapes arrived; restoration process began Wednesday p.m. - voice mail accounts on alternate voice system began to be created for lawyers Wednesday night- new server built; account creation in process; Internet mail redirected (brownwoodlaw.com)

Brief Chronology (contd.) Thursday a.m. - all lawyers had accounts and mail was flowing; equipment was shipped out from other Firm offices Thursday p.m. - Internet café established in alternate NY sight; image build began for rental equipment Thursday night - secure extranet site established for technology information

Brief Chronology (contd.) Friday a.m. - document management was available to NY users Friday noon - equipment began arriving from other offices and from vendor Friday p.m. - financial systems restoration was complete and consolidation began; image for rentals and new PCs finalized

Brief Chronology (contd.) Saturday a.m. - Rental equipment began arriving; imaging began; teams from Chicago began driving to New York transporting equipment not available in New York (cell phones, card keys, etc.) Throughout weekend - Phones, network equipment, printers, desks, PCs rolled out in temporary space

Six Days Later Monday 10:00 a.m. - all New York personnel assembled in a mid-town hotel for a briefing Monday noon - all New York personnel reported for work in temporary space

Today All servers returned to New York All technology migrated to firm standards New York office moved into new, permanent home over July 4 weekend

Key Aspects of Disaster Recovery Approach Maniacal approach to tape backups - daily offsite storage of tapes; offsite location outside metropolitan area Focus on running our daily operation to perfection Standardized hardware (network, PCs, phones) with standard images

Key Aspects of Disaster Recovery Approach (contd.) Emphasis on documentation and standard operating procedures Commitment to serving our lawyers the way our lawyers serve the Firm's clients

Lessons Learned/Affirmed You cannot plan for a plane hitting your building - accept the fact that you will have to improvise to some degree in virtually any disaster You cannot have too many friends - clients, vendors, co-counsel, even competitors Practice, practice, practice - staff need to be able to perform basic disaster recovery tasks "in their sleep"

Lessons Learned/Affirmed (contd.) If you have multiple offices, leverage them The fact of back-ups is not enough - they must be quality-checked, verified, and viable Efficiencies of centralization must be weighed against risks from a disaster recovery perspective

Lessons Learned/Affirmed (contd.) Recruit for character and creativity, as well as technical expertise Understanding the relative priority of your critical applications cannot be overstated - in a disaster situation, restoring contact information may be more important than restoring documents

Lessons Learned/Affirmed (contd.) Web access to your systems is not a luxury; it is a necessity Stress with principals the importance of using firm-standard repositories - if documents are in three different places, restoring access becomes much more difficult

Lessons Learned/Affirmed (contd.) Think about disaster recovery when making a buy/build decision Smart, dedicated people ultimately make it happen

How does the Story End? We were never down Clients were impressed Our most important assets - our smart and dedicated people - were not lost The loss of people is the only disaster truly to fear - if you are prepared, everything else can be recovered or replaced