| |
|
 |
|
 |
|
 |
 |
|
|
|
1.6 Built-in failure tolerance, asynchronous long-distance replication, and stretched clusters |
|
59% |
 |
|
2 Requires dedicated knowledge of storage silos |
|
0.9 No more LUNs, and no more volumes |
|
56% |
 |
|
2 Creates dependency between storage admin and VM admin |
|
0.9 Storage is built into the “Create VM” process |
|
53% |
 |
|
10 Requires multiple tools; difficulty achieving end-to-end visibility |
|
5.5 One tool provides visibility into storage, compute, and networking |
|
45% |
 |
|
2 Requires manual intervention and ongoing load balancing to ensure high performance |
|
1.2 App policy can be changed in a single click; the system automatically adjusts |
|
38% |
 |
|
2 Overprovisioning is necessary to ensure availability—but it comes with a high cost |
|
1.0 Just-in-time storage services automatically allocate resources as needed |
|
51% |
 |
|
4 Requires expensive professional services and third-party tools |
|
2.6 Uses proven VMware vMotion® and Storage vMotion tools to move data or replace hardware |
|
36% |
 |
|
2 Requires expensive proprietary hardware |
|
1.0 A new cost model is based on $/CPU, not $/TB |
|
49% |
 |
|
12 Requires a mix of teams and people outside of IT |
|
6.4 Skill sets and knowledge now freely cross organizational boundaries |
|
47% |
|
|
|
|
