1. Department of Information Technology SHARE New Architecture, Hardware, Disaster Recovery, and System Upgrade Project Update SHARE Service Manager – David Holmes Project Manager – John Prihoda June 20 th, 2012

2. DR Project Scope To recap, the purpose of this project is to establish a Disaster Recovery system for the SHARE environment. The goals include:  Move SHARE to newer hardware and commodity technology  Provide for a Highly Available, Redundant & Fault Tolerant System  Increase Agility – Expandable, Flexible & Scalable  Reduce Complexity & Increase Manageability  Establish a Disaster Recovery system easily moved to a remote Disaster Recovery Datacenter. 2

3. Current Status This project was moved back to Planning Phase and is now ready to proceed to Implementation  Architecture leverages previously purchased SHARE DR servers and software while redesigning to conform with DoIT Service strategies  Architecture has been reviewed and approved by TARC  All hardware previously purchased is utilized, no new servers are required  New Switches from DoIT to accommodate Storage  Disk Storage will be provided by DoIT as a Service  Server infrastructure support will be provided by DoIT as a Service  Database support will be provided by DoIT as a Service 3

4. Revised Architecture 4

5. Budget Status – 4/10/12 FundCertifiedSpentRemain Appropriations$1,700,000$1,679,745$20,255 FY09 Operating(expired)$400,000$373,645$0 ERF$0$0$0 Total$2,100,000$2,053,390$20,255 Note: The Project was certified for $2,100,000. Project financials continue under review. 5

6. High Level Plan Ready to move to Implementation to accomplish: 1)Re-platform current SHARE systems from the aging IBM systems and Hitachi storage to the “new” SHARE hardware platform 2)Establish DR system as a stand alone clone of SHARE Production 3)Move DR system to remote site when identified 6

7. Affect on Budget Contingent on the outcome of the review and new planning. The project may incur costs associated with:  Procuring additional hardware, software, and network components to complete the fully independent DR system  Utilizing professional services as required to complete the project 7

8. Affect on Schedule The new platform implementation plan is now targeting an October 6 th – 8 th, 2012 weekend Go Live  April – June: Moved back in Planning Phase to review and plan  June – July: Move to Implementation Phase to build and test hardware and technical design  July – September: Tuning and performance testing  August – October: Full functionality testing with agencies prior to the October 8th Go Live 8

9. Next Steps: Complete installations and technical testing Move applications and databases to new architecture Complete tuning and performance testing Complete Functional Testing with Agencies before Go Live 9

10. 10 Q&A Thank you