1. Disaster Recovery Sudath Wijeratne 15-Sep-06

2. Information Services 2 Agenda Background Methodology Our DR Strategy Learning Management system (Blackboard) DR implementation Discussions

3. Information Services 3 Background Griffith has 5 campus locations from Brisbane's Southbank to the Gold Coast Servers have been installed local to campus Nathan centric corporate systems and servers

4. Information Services 4 Background The University AUQA audit in 2003 identified risk management as a priority, and the impact of failure of electronic infrastructure was identified as a risk requiring mitigation. A loss of the core Nathan Data Centre has the potential to cripple the University’s ability to deliver its core services. Achieving sufficient involvement and sponsorship from core business units to undertake a traditional top down Business Impact Statement (BIA) approach to disaster recovery has proven difficult over the last few years.

5. Information Services 5 Background … In absence of BCP plan/strategy, ICTS management team commissioned a disaster recovery project to jumpstart the process via a bottom up approach for three critical University systems: –Learning@Griffith –Staff Email –Corporate Web Services

6. Information Services 6 Methodology Dozens Of Systems Hundreds of IT Components (building blocks) How they relate to each other and what is a real impact of failure of any particular building block? We needed a process / methodology to guide us to approach DR system by system

7. Information Services 7 Methodology We have developed a methodology called “Building Block” Methodology is about –Systems / Services –Architectural components –And their dependencies

8. Information Services 8 Methodology

9. Information Services 9 Building Block methodology Top down approach is to analyse IT services iteratively decomposing them into key technological components and dependencies. As a result of this process the key building blocks required to deliver the service are identified. Recovery solutions for each building block are then undertaken. A second round of analysis identified common building blocks that are reusable for other systems, or as base components for holistic disaster recovery (e.g. DNS services, LDAP).

10. Information Services 10 Understanding Environment Interdependencies Web/Apps Services (S1-APS)Database Services (S1-DBS)Authentication (S1-AUS)Network Services (S1-NW) System-1 (S1)

11. Information Services 11 Web/Apps Services (S1-APS)Database Services (S1-DBS)Authentication (S1-AUS)Network Services (S1-NW) Apps Servers (S1-APS-SRV)Storage Services (S1-APS-SS) DNS01 LBS (S1-APS-NW) System-1 (S1) Understanding Environment Interdependencies

12. Information Services 12 Web/Apps Services (S1-APS)Database Services (S1-DBS)Authentication (S1-AUS)Network Services (S1-NW) Apps Servers (S1-APS-SRV)Storage Services (S1-APS-SS) LBS (S1-AUS-NW) LDAP servers (S1-AUS-SVR) DNS01 LBS (S1-APS-NW) System-1 (S1) Understanding Environment Interdependencies

13. Information Services 13 Web/Apps Services (S1-APS)Database Services (S1-DBS)Authentication (S1-AUS)Network Services (S1-NW) Apps Servers (S1-APS-SRV)Storage Services (S1-APS-SS) LBS (S1-AUS-NW) Database Server (S1-DBS-SVR) LDAP servers (S1-AUS-SVR) Storage Service (S1-DBS-SS) DNS01 LBS (S1-APS-NW) System-1 (S1) Understanding Environment Interdependencies

14. Information Services 14 Web/Apps Services (S1-APS)Database Services (S1-DBS)Authentication (S1-AUS)Network Services (S1-NW) Apps Servers (S1-APS-SRV)Storage Services (S1-APS-SS) LBS (S1-AUS-NW) Database Server (S1-DBS-SVR) LDAP servers (S1-AUS-SVR) Storage Service (S1-DBS-SS) DNS01 LBS (S1-APS-NW) System-1 (S1) Understanding Environment Interdependencies

15. Information Services 15 Understanding Environment Interdependencies Web/Apps Services (S1-APS)Database Services (S1-DBS)Authentication (S1-AUS)Network Services (S1-NW) Apps Servers (S1-APS-SRV)Storage Services (S1-APS-SS) LBS (S1-AUS-NW) Database Server (S1-DBS-SVR) LDAP servers (S1-AUS-SVR) Storage Service (S1-DBS-SS) DNS01 LBS (S1-APS-NW) System-1 (S1)

16. Information Services 16 Methodology application to Backboard

17. Information Services 17 Methodology Summary for Blackboard

18. Information Services 18 Fact sheets

19. Information Services 19

20. Information Services 20 Our DR Strategy is based around … Two physically separated primary Data Centres Distributed operation of major systems between these Campuses Near real-time data replication capabilities between these Data Centres

21. Information Services 21 Key Dependencies for DR Project SAN Infrastructure provisioning at Gold Coast campus Network server campus virtualisation (Between Nathan and Gold Coast)

22. Information Services 22 SAN Infrastructure design Tiered storage capabilities Provide inter campus (Inter SAN) copy (TRUE Copy) and snapshot (Shadow Image) capabilities Tier to tier copy capabilities Central management of storage Allow for DR implementation using above capabilities

23. Information Services 23 Virtual server campus network design

24. Information Services 24 Virtual server campus network design Provide equal access to servers from anywhere Well defined access points into the server subnets Greater server to server connectivity Allow for DR planning by allowing a shared layer 2 between sites Easy to migrate servers and services between sites

25. Information Services 25 Learning@Griffith Distributed DR Architecture

26. Information Services 26

27. Information Services 27

28. Information Services 28

29. Information Services 29

30. Information Services 30 DR Plans DR Management Framework DR Plans for each building block Resumption plans

31. Information Services 31 Lesions learnt Resource issues and priorities with multiple projects Distributed environment –Benefits and challenges Resources at 2 nd primary site External audit  University Audit committees BCP awareness

32. Information Services 32 Discussions