3. Business Continuity Dynamic Datacenter Server Sprawl Power Consumption Costly Disaster Recovery Datacenter Expansion Branch Office Growth Additional Applications Support and Hardware Costs Timely Recovery Maintenance Windows Space Constraints Server Consolidation Test and Dev Virtualization Business Requirements
4.
5.
6.
7.
8.
9.
10.
11.
12. VHD Type Features Use Instructions DEDICATED (Passthrough) Guest receives pass-through access to the physical device for exclusive use. Highest performance; least flexible. Used for production servers when performance is top priority. These drives are not available to other guests. FIXED SIZE Creates a dedicated file the size of the VHD that doesn't change regardless of content. High performance; less efficient. Used for production servers where performance is important. DYNAMIC SIZE File size starts as zero, grows only as data is added, allocated in blocks. File size is limited by the specified size. Slower performance, and subject to fragmentation. Used for test and development when disk space is uncertain or limited. Dynamic drives only reserve physical drive space as the need grows. However, they must be manually shrunk (offline). DIFFERENCING Records only the changes that differentiate a VHD from its parent file. Allows for flexible versioning and fast reversion to parent image. Always configured as dynamic, so performance is slower. Used for test and development scenarios where branching is a high priority and performance is less important. Parent drives should be located on separate spindles from the differencing drives for best performance. UNDO Provides quick "back to original state" imaging solution. Similar to differencing, but doesn’t require parent-child relationship. Undo drives are only to be used for testing purposes. They should not be turned on in production.
13.
14.
15.
16.
17.
18.
19.
20.
21.
22.
23.
24.
25.
26.
27.
28. Server A Migrating Physical Servers to Virtual (Guests) Server B Workload Simulation Library Server
29.
30.
31. Site A Administrator Console Site B Clustered Hyper-V Hosts Library Server SAN Storage Hyper-V Hosts Geo-Cluster SAN Storage
32.
33.
34.
35.
36. Server Population (~ 570 servers) TBE Phase II 106 servers Servers out of scope 87 servers Applications / Services at end of life 20 servers Branch Servers to be centralized 50 servers Windows Servers to be consolidated 309 servers (222 NA and 87 Europe)
37.
38. TRANSITION FROM CURRENT ARCHITECTURE TO SHARED ENVIRONMENT 11 5 TRANSITION FROM CURRENT ARCHITECTURE TO SHARED ENVIRONMENT 11 5 3 Expected 18 Month Growth 11 Servers!