GDOC – Geographically Dispersed Open Clusters

1. GDOC – Geographically Dispersed Open Clusters For (Insert Customer Name)

2. agenda 1 • GDOC Overview • Confirming & Addressing (Insert Customer Name)'s Requirements • GDOC Methodology & Value • Alignment with business requirements • Standardization (class of service) • Best practice implementation • Moving Forward 2 3 4 Insert title of presentation in Footer | July 2007

3. Solaris AIX Linux Windows HP-UX Z/OS Insert title of presentation in Footer | July 2007

4. Solaris AIX Linux Windows HP-UX GDPS GDOC Insert title of presentation in Footer | July 2007

5. Solaris AIX Linux Windows HP-UX Enterprise wideBusiness Continuity Solution GDPS GDOC Insert title of presentation in Footer | July 2007

6. GDOC - Geographically Dispersed Open Clusters • GDOC is an end-to-end solution which follows a methodology ensuring alignment of IT recovery strategies with business objectives. • GDOC leverages leading practices and policies as well as leading open systems technologies from IBM & Symantec Insert title of presentation in Footer | July 2007

7. A proven Business Continuity solution that can be: • GDOC Implemented across Unix, Windows & Linux servers to provide a business continuity solution for open systems • Implemented with GDPS on the Mainframe to provide a business continuity solution across the Enterprise Insert title of presentation in Footer | July 2007

8. GDOC provides the best : Methodology, Technology and Services. • Proven methods and experience to successfully deliver: • Requirements gathering and solution design • Network bandwidth analysis • Dual data center replication • Disaster recovery testing • DR Plan Development • Project management, HA/DR design, planning, deployment, and testing • Market-leading enterprise high-availability disaster recovery solutions providing: • Automation of application startup and application restart on another server in the event of a server failure • Monitoring of data replication and application status • Single console for management of all clusters Insert title of presentation in Footer | July 2007

9. Addressing (Insert Customer Name)'s Requirements Critical Success Factors • Alignment of IT strategy with business recovery objectives • Remove silo based IT recovery strategies • Achieve good utilized of infrastructure • Implement standardization to reduce risk of effective recovery • Ensure processes are well documented • Improve testing processes • Implement live DR testing strategy • Ensure capability to failback to primary site • Enable Datacentre consolidation (opportunity for change) Critical Success Factors Insert title of presentation in Footer | July 2007

10. Business Continuity Management y t t n e t f e t n a g n & m e S n e t y t i e s n m r n n m & g e n e e e n e v a o h g m a m i g o n t l t a e y l a c P a e a n t a C g i n e c g a M r e a i y O a a R u n H c n M n c n D M u n r a i l a e e y G a e m a s M t S c M h g n s e m n i n o k a C s t i e i o i s s t i t l i i y s g i n a C l c r i R D o r p p e a C p u C F m c u c E S O Business Operations & Process Management GDOC Methodology Alignment with (Insert Customer Name)’s BCM • Leading Practice: • Holistic discipline concerning protection & recovery of the business • Business Continuity should be built around the business service rather than protecting discrete components of the service • Consideration of all components including application/database, storage, server, network, security and any supporting infrastructure • Understand applications, their interdependencies and manage ongoing change and configuration management • GDOC can be a key component of enterprise risk management Insert title of presentation in Footer | July 2007 10

11. Frame Assess Plan Design Implement Sustain The GDOC Methodology consists of six stages Insert title of presentation in Footer | July 2007

12. Findings A Actions A - … C - … E E - … Importance C D Project Plan B Month 1 Month 2 Month 3 Month 4 Month 5 Month 6 Week 1 Week 2 Week3 Week5 Week 7 Week 12 Support Frame Mobilise Supply chain context Discovery workshops Mobilised Assess Determine KPIs CCRs agreed Share leading practices Plan Determine design principles Conduct visioning workshop Vision Complete Design Complete design Design Determine architecture Implement Train Pilot Live Rollout Sustain Frame Assess Plan Develop Implement Sustain OBJECTIVES Develop consensus on DR requirements, develop high level reference architecture and agree to next steps Illustration KEY ACTIVITIES • Review in-scope business processes and associated I/T applications • Review current recovery process • Reach consensus on availability and disaster recovery definitions and requirements • Document disaster recovery objectives • Provide an overview of GDOC • Develop high level reference architecture • Jointly agree on next steps Recommendations KEY DELIVERABLES • Findings and Recommendations • Next Steps (High Level Task List) Insert title of presentation in Footer | July 2007

13. Frame Assess Plan Design Implement Sustain OBJECTIVES Develop detailed application file inventory and collect data to be used for network bandwidth analysis KEY ACTIVITIES • Develop data collection plan • Document risk • Document impact • Document business process dependencies • Document recovery objectives • Take inventory and categorize application files by replication type (continuous, periodic, manual) • Collect write activity of in-scope applications over a period of time for network bandwidth analysis • Workshops and interviews Illustration Application File Inventory Findings … Application A Server 01 Business … Server XX Server 02 Network Bandwidth Analysis KEY DELIVERABLES • Network Bandwidth Analysis Periodic Continuous Periodic Manual Continuous KEY DELIVERABLES • Gap analysis • Impact analysis • Document Service requirements • Application component inventory • Continuous replication file inventory • Manual change file inventory • Periodic copy file inventory • Network Bandwidth Analysis Report • Write Statistics • Estimated Network Bandwidth • Overall Findings Manual Insert title of presentation in Footer | July 2007

14. Dynamic DNS Updates Site B Site A Multi-master replication Primary Master(s) Primary Master(s) Slave Server(s) Slave Server(s) Illustration Zone Files Zone Files Caching Server(s) • Synchronous • Asynchronous • Periodic Caching Server(s) Queries Queries Resolver Replication Modes Technology Alternatives Storage Replication • caching/recursive nameservers provide a proxy service for clients so that they do not have to make requests directly to external nameservers • authoritative nameservers hostin a domain so that all Internet users can have access to the names in that domain. Database Replication Volume-based Replication Application Replication Frame Assess Plan Design Implement Sustain OBJECTIVES Make key infrastructure decisions and plan change control and systems management process updates KEY ACTIVITIES • Develop Service Delivery categories • Develop initial Conceptual Design • Select replication technology • Plan multi-site infrastructure • Establish a networking strategy • Establish change control process • Develop change control monitoring plan Illustration DNS Strategy Findings Business Replication Technology Selection KEY DELIVERABLES • Service delivery strategy • Initial Conceptual Design • Proposed Multi-site “to be” inventory • Recommended change control process updates • Recommended systems management and monitoring enhancements • DNS Strategy Insert title of presentation in Footer | July 2007 Illustration

15. Phase 3: Plan Customer visible, high revenue earning systems High revenue earning or supporting systems Class B - Enhanced Recovery Class A - Failover Class C - Base Level Recovery Vital legacy applications $$$$$ $$$ $$ Migration Plan Migration Plan * Note: Class A recovery and data loss times are those defined as targets in typical DR standards. Actual recovery times in minutes with zero data loss can be achieved with GDOC. Insert title of presentation in Footer | July 2007

16. Qualities Class A Class B Class C Storage Management Response Time for Online Data < 1 second < 2 seconds < 3 seconds Throughput IO/Sec not just MB/sec Up to 50MB/sec Up to 20MB/sec Up to 5MB/sec Allow Migration? No Yes Yes Response Time for Migrated Data N/A < 2 mins < 5 mins Time to provision additional Capacity < 2 hours < 24 hours < 3 working days High Availability Overall Availability 99.999% 99.9% 99% Accessibility 7x24 7x24 7x18 Data Protection Backup Schedule Daily Full Weekly Full / Daily Inc Weekly Full / Daily Inc Retention Period - Daily - Weekly - Monthly 12 weeks1 year7 years 4 weeks3 months1 year 1 week1 month3 months Duplication & Off-siting All Weeklies only None Disaster Recovery Time to recover (RTO) 2 hours 12 hours 72 hours Acceptable data loss (RPO) < 10 mins < 2 hours < 24 hours Phase 3: Plan Insert title of presentation in Footer | July 2007

17. Frame Assess Plan Design Implement Sustain OBJECTIVES Develop a comprehensive design to deliver customer requirements Illustration KEY ACTIVITIES • Apply leading practices and design principles to develop the following: • Conceptual Design • Site Level Architecture • Application Level Architecture • Component Models Site Level Architecture Both Sites Share Network End User Illustration Primary Site Secondary Site Asynchronous Data Replication over dedicated DR network Application Level Architecture 1200 Miles KEY DELIVERABLES • Conceptual Design • Site Level Architecture • Application Level Architecture • Component Models Insert title of presentation in Footer | July 2007

18. Test Results Frame Assess Plan Design Implement Sustain OBJECTIVES Implement and test solution designed in previous phases Illustration KEY ACTIVITIES • Deploy and test pilot environment (People, Processes, Technology) • Implement and test non-production environments • Develop a deployment schedule • Implement production environments • Develop a skills transfer plan Implementation Report KEY DELIVERABLES • Updated Implementation and Test Plan • Installation and Configuration Record Insert title of presentation in Footer | July 2007

19. SLA Reporting Frame Assess Plan Design Implement Sustain OBJECTIVES Provide post-implementation transition, support, and informal skills transfer Illustration KEY ACTIVITIES • Post-implementation support • Review effectiveness of the skills transfer plan • On-going testing of key environments • Performance and alert monitoring • Capacity planning • Measure against Service Levels • Develop repeatable Standard Operating procedures KEY DELIVERABLES • Regular status reporting • Updates to operations manuals as required Insert title of presentation in Footer | July 2007

20. Addressing Insert Customer Name's Requirements Critical Success Factors • Alignment of IT strategy with business recovery objectives • GDOC • Framing workshop/s to achieve business commitments • Recovery plans based on business services • Consistent Class of Service model Critical Success Factors Insert title of presentation in Footer | July 2007

21. Addressing (Insert Customer Name)'s Requirements Critical Success Factors • Remove silo based IT recovery strategies • GDOC • Commitment to strategic framework • Standardise & simplified design • Consistent Class of Service • Repeatable & consistent recovery methodologies & processes Critical Success Factors Insert title of presentation in Footer | July 2007

22. Addressing (Insert Customer Name)'s Requirements Critical Success Factors • Achieve good utilisation of infrastructure • GDOC • Leverage Insert Customer Name’s current infrastructure investment in replication & storage • Leverage investment in second datacentre • Leverage investment in Symantec proven high availability solutions • Leverage deployment of existing Insert Customer Name skills across gap/high risk areas • Review datacentre consolidation opportunity to maximise high availability infrastructure e.g. maximise development /test environments Critical Success Factors Insert title of presentation in Footer | July 2007

23. Addressing (Insert Customer Name)'s Requirements Critical Success Factors • Implement standardisation to reduce risk of effective recovery • GDOC • Standardised recovery process • People & Process • Reduce dependencies on key personnel Critical Success Factors Insert title of presentation in Footer | July 2007

24. Addressing (Insert Customer Name)'s Requirements Critical Success Factors • Ensure processes are well documented • GDOC • Documentation to be part of change control process • Regular live testing encourages sustainability of accurate documentation Critical Success Factors Insert title of presentation in Footer | July 2007

25. Addressing (Insert Customer Name)'s Requirements Critical Success Factors • Improve testing processes • Implement live DR testing strategy • Ensure capability to failback to primary site • GDOC • Increase automation of recovery testing • Initial design includes the capability to failback to primary site Critical Success Factors Insert title of presentation in Footer | July 2007

26. Moving Forward with GDOC • Confirm value in proposed approach • Provide indicative GDOC proposal • Confirm Insert Customer Name funding approval • Obtain acceptance of GDOC proposal • Program initiation • Commence GDOC Phase 1: Frame Insert title of presentation in Footer | July 2007

27. Frame Assess Plan Design Implement Sustain Phased Approach, Phase 1 • Deliverables • IT Risk and Business Impact Analysis • Gap Analysis • Dependency Mappings, (Business Process – Applications - IT Infrastructure) • Documented Recovery Objectives • Service Delivery Strategy • Conceptual Design • Duration • Approx 230 days • 3 – 4 Consultants Insert title of presentation in Footer | July 2007

28. Frame Assess Plan Design Implement Sustain Phased Approach, Phase 2 • Deliverables • Architecture document for each environment • Deployment timeframe and schedule, target environments identified • Deployment to target environment/s • Standard framework for managing the environment • Duration • Determined from previous Phase • Target environments identified • Gradual increase in NAB ownership as staff are trained Insert title of presentation in Footer | July 2007

29. Reference Methodologies Reference GDOC Reference Technology GDOC official launch December 2006: • Bharti • Caremark • Large American financial services institution • Other references available upon request GDOC leverages GDPS proven methodologies • GDPS : 352 installations in 236 customers in 31 countries. • Includes several financial and federal government accounts in Australia – available on request GDOC leverages Symantec’s High Availability Product Suite Symantec HA sites: Including but not limited to: • Many large financial services institution (local & international) • Large Telco • Federal government - available on request Insert title of presentation in Footer | July 2007