1. Enterprise Vitrualization by Ernest de León

2. Brief Overview

3. Company Profile Public Utility Company Over 80,000 customers Multiple resource sources Complex asset and billing system Online payment system

4. Infrastructure Before VMs 16 servers total (Blades and 1Us). Fiber connected SAN. 2 high-capacity Ultruim Tape Drives. No Disaster Recovery system in place. All servers in use (no room for expansion). Server Rack nearly full. No additional power outlets on rack.

5. The Challenge Create Disaster Recovery plan, build infrastructure, and implement all. DR must be at an off-site location. All components to include servers, rack, switches, power, cooling and fiber connection must be procured. System must maintain full functionality of main location. Extremely constrained budget and space.

6. The Solution Created DR plan to address business continuity and focus efforts. Consolidation of all but 2 servers onto a VM host. Commodity hardware and open-source software. Usage of NAS vs SAN to reduce cost and ease implementation.

7. Virtual Infrastructure 1 high-powered 1U hosting all VMs. VMware Server on top of Ubuntu Server Dual Processor Dual Core Machine 16GB of RAM Quad 500GB Commodity Hard Drives Dual Gigabit NICs Private Subnet in VMware handles all networking translation between the VMs and host machine hardware.

8. V2P Connectivity Database server is a stand alone physical server necessitated by intensive demand of system resources. 2 NAS units are stand alone servers with locally attached large commodity hard drives. Connectivity between VM host and NAS units are via NFS and Samba Gigabit switch handles all traffic.

9. Implementation Process System designed and built from DR core outwards. Servers hand-built and OS installed first. Servers taken to off-site location and racked for testing and configuration. NAS units hand-built and configured, then taken to be racked off-site. Interconnectivity between all servers, VMs, and NAS units verified.

10. Implementation Process Main mission critical servers mirrored onto remote VMs and physical servers. Distributed file system mirrored across WAN and checked for integrity. Backup server installed, connected and tested to verify that written backups could be read from. Full system functionality and fail-over tested repeatedly.

11. Usage Scenarios Single system failure at main location. Multiple system failure at main location. Total system failure at main location. Natural disaster or complete destruction of main location. Data or traffic overload at main location. Data recovery from off-site location. Replacement of main equipment.

12. Results Entire mission critical system mirrored over WAN to remote location. SPOF file system now DFS over WAN. Additional D2D and D2T backup system now in place provides 3X redundancy as before. Ability to run partial or full business from remote location with minimal switch time.

13. Lessons Learned Virtual environment not well suited for extremely high volume data transfer or massive resource consumption. Commodity hardware provides economical and fully functional solutions. Open-source software decreases cost while still maintaining functionality. Mixed VM and physical environment is best.

14. Questions?