Completion Report
Project Summary:
The objective stated at the outset of the project was to:
Provide a solution that upon single site or server hardware failure reduces the time to recover the web-tier. In addition the revised infrastructure must be proven through load testing to not degrade web-service response times
Completion Notes:
- The project has met the original objective through the utilisation of Virtual infrastructure technology. Deliverables
| Deliverable (strategy document covering the following items) | Delivered | Notes |
|---|---|---|
| Identify available solutions | Y | |
| Evaluate available solutions | Y | |
| Plan performance and availability testing (measurements and metrics) | Partial | Automated testing initially thought this possible but would have required significant additional effort. A decision was taken that given the vertical scaling capacity of VEEAM, additional resource could be deployed in event of any performance issue. |
| Execute performance testing against current Test infrastructure | Y | |
| Introduce chosen solution to Test infrastructure and re-execute test plan | Y | |
| Compare performance of new Test environment against 'old' | Y | |
| Decide whether solution meets business need or whether to adopt alternative solution | Y | |
| Introduce solution to Production environment | Y |
Phase 2 deliverables (postponed until further notice)
1. Configure load balancer for Test 2. Configure load balancer for Production
Benefits
As stated in the Project Brief the project benefit would result from alignment of a priority 1 service with the University goal to provide quality services through the development of the underlying technical architecture.
The primary objective was to reduce the time to recover webservices in event of loss of infrastructure or components. This time has been reduced from an estimated 2 days to 1 hour during IS business hours.
Analysis of Resource Usage:
Staff Usage Estimate: 56 days
Staff Usage Actual: 25 days
Staff Usage Variance: -55%
Other Resource Estimate: 0 days
Other Resource Actual: 0 days
Other Resource Variance: 0%
Explanation for variance:
Project estimation varied throughout the project as various solutions were considered. The chosen solution did not require the development originally anticipate as this work had already been completed by IS Architecture through their deployment of VEEAM.
Key Learning Points:
Outstanding issues:
There are no outstanding issues. Operational documentation has been updated with information arrising from testing.