Vmware-soldes-ptptn Pdc v1 1

8/13/2019 Vmware-soldes-ptptn Pdc v1 1

1/34

Solution Design VMware Server

Consolidation

For

Perbadanan Tabung Pendidikan Tinggi

Nasional - PTPTN


2/34


3/34

Solution Design Documentation for Consolidation and Virtualization Project

Private and Confidential

Page 3

Document Properties

Document Author Amirullah Iqram

Document Type Project Proposal Report Others

Document Reference VMware-SOLDES-PTPTN PDC v1 1.doc for PTPTN

Version 1.1

Created Date 07 July 2011Last Modified Date 08 July 2011

Document History

Version Status Approved by Date

Changes From Last Issue

Ver Date Updated RevisionAuthor

Summary of Major ChangesMade

Reviewed By Review Date

Distribution List

Referenced Documents

Number Title Reference Note

1.

2.

Abbreviations


4/34



Page 4

Table of content

1 Overview....................................................................................................................................... 5

1.1 Executive Summary .............................................................................................................. 5

1.2 Design Overview ................................................................................................................... 6

1.3 Requirement .......................................................................................................................... 7

1.4 Constraints .............................................................................................................................. 71.5 Assumptions ........................................................................................................................... 8

2 Host at Production Data Center ............................................................................................... 9

2.1 Requirements ......................................................................................................................... 9

2.2 Design Patterns ...................................................................................................................... 9

2.3 Logical Design ..................................................................................................................... 10

2.4 Physical Design .................................................................................................................... 11

3 Virtual Datacenter .................................................................................................................... 13

3.1 Requirements ....................................................................................................................... 13

3.2 Design Patterns .................................................................................................................... 14

3.3 Logical Design ..................................................................................................................... 17

3.4 Physical Design .................................................................................................................... 184 Network ....................................................................................................................................... 20

4.1 Requirements ....................................................................................................................... 20

4.2 Design Patterns .................................................................................................................... 20

4.3 Logical Design ..................................................................................................................... 21

4.4 Physical Design .................................................................................................................... 21

5 Storage........................................................................................................................................ 22

5.1 Requirements ....................................................................................................................... 22

5.2 Design Patterns .................................................................................................................... 22

5.3 Logical Design ..................................................................................................................... 24

5.4 Physical Design .................................................................................................................... 24

6 Virtual Machine ......................................................................................................................... 256.1 Requirements ....................................................................................................................... 25

6.2 Design Patterns .................................................................................................................... 25

6.3 Virtual Machines Specification ......................................................................................... 26

7 Implementation Strategy ......................................................................................................... 27

7.1 Requirements ....................................................................................................................... 27

7.2 Strategy ................................................................................................................................ 27

8 Appendix .................................................................................................................................... 28

8.1 Appendix A Security Configuration .............................................................................. 28

8.2 Appendix B Port Requirements ...................................................................................... 28

8.3 Appendix C Migration Date ........................................................................................... 31

9 References ................................................................................................................................. 3210 Consolidation Agreement ....................................................................................................... 34


5/34



Page 5

1 Overview

1.1 Executive Summary

Perbadanan Tabung Pendidikan Tinggi Nasional (PTPTN), It is responsible for giving study loans to students

pursuing tertiary education in Malaysia. The functions of PTPTN are, to manage disbursement for the purpose

of higher education, and to collect loan settlement. Beside to collect deposits, design and offer saving

schemes for the purpose of saving in higher education. The CIO is very cost-conscious and will question

anything that seems overly complex or overpriced. ZEN has been asked to introduce virtualization in an

effort to reduce costs and promote the fact that the company is going green.

As part of a virtualization project, ZEN has been asked to virtualize all twenty two(22) x86-based servers onto

the VMware vSphere 4.1 platform at PTPTN production data center in HTV2.

PTPTN environment has two zones: Server Farm(SFZ) and Dimilitarize(DMZ). From the preliminary

virtualization assessment, it was determined that PTPTN can consolidate a considerable number of existing

and expected future workloads. This increases average server utilization and lowers the overall hardware

footprint and associated costs.

The virtualization assessment shows that twenty two (22) physical servers can be virtualized. The

consolidation ratio depended upon proposed platform as below:-

C

D

IBM BladeCenter HS22;Intel Xeon 6C Processor ModelX5650 95W 2.66GHz/1333MHz/12MB 03:01 01:01

Each blade servers come with a four (4) port GigE NIC. Availability of the virtual machines is an important

requirement. Separation of management and production virtual machines is desired. The 22 physical servers

are comprised of 22 virtual servers.

Server distribution:

16 servers SFZ 6 servers DMZ


6/34



Page 6

Existing Workloads

Web/Application Server Transaction Server MSQL Server Mail Server etc

There are nine (9) servers with maximum hard disk is 30GB, while the rest is 10GB and 20GB. There are no

servers have two CPUs while the rest with single CPU. PTPTN wants to adopt a virtualization first policy. The

department plans to provision another unknown number of new virtual machines within the next year.

1.2 Design Overview

The architecture is described by a logical design, which is independent of hardware-specific details.

Specifications of physical design components that were chosen for the logical design are also provided.

This architecture design can be used to implement the solution using different hardware vendors, so long as

the requirements do not change.

This design includes:

One physical site; Production data center(PDC - HTV2) Clusters of hosts for load balancing through VMware High Availability/VMware Distributed

Resource Scheduler (DRS) for host and guest operating system (virtual machine) failure.

VMware vCenter Server integrated with Microsoft Active Directory. vCenter Server will leveragethe extensive inventory of existing Active Directory users and groups to secure access to vSphere.

Redundancy in network and storage infrastructure System component monitoring, with SNMP traps or email alerts VMware vCenter Update Manager for automating patching of all hosts and VMware Tools


7/34



Page 7

1.3 Requirement

Requirements describe, in business or technical terms, the necessary properties, qualities, and

characteristics of a solution. These are provided by the client and used as a basis for the design.

Number Description

R001 Deploy 4 ESXi and 1 vCenter server at PDC

R002Virtualize existing 22 servers as virtual machines with no significant change in performance or

stability, compared to current physical workloads in PDC.

R003Establish a sound and best practice architecture design while addressing PTPTN specific

requirements and constraints.

R004 Design should be scalable and the implementation easily repeatable.

R005 Design should be resilient and provide high levels of availability where possible.

R006 Automated deployment of systems and services is desirable.

R007 Overall anticipated cost of ownership should be reduced after deployment.

R008Production servers must be completely segregated using VLAN from all other servers due to

network security requirements.

1.4 Constraints

Constraints can limit the design features as well as the implementation of the design.

Number Description

C001 Hardware upgrade readiness (NIC, memory & etc)

C002 SAN storage additional drive readiness


8/34



Page 8

1.5 Assumptions

Assumptions are expectations regarding the implementation and use of a system. These assumptions

cannot be confirmed at the design phase and are used to provide guidance in the design.

Number Description

A001 All required upstream dependencies will be present during the implementation

phase. PTPTN will determine which dependencies sit outside of the virtual

infrastructure.

A002 All VLANs and subnets required will be configured before implementation.

A003 PDC and DRC vCenter will be able to communicate with each other

A004 There is sufficient network bandwidth to support operational requirements.

A005 Storage will be provisioned and presented to the VMware ESXi hosts accordingly.


9/34



Page 9

2 Host at Production Data Center

2.1 Requirements

Host capacity must accommodate the planned virtualization of 22 physical servers. Size capacity to ensure that there is no significant change in performance or stability, compared to

current physical workloads.

Expect minimum 8 new virtual machine slots (per cluster) for future deployment.

2.2 Design PatternsBlade Servers

Design Choice New IBM Blade Center will be used for virtualization

Justification New blades servers are suffice for future scalability and node dependencies for

high-availability within PTPTN approved budget

Impact Future scalability may require additional resources upgrade

Server Consolidation (minimum number of hosts required)

Design Choice 4x ESXi hosts and 1x vCenter

Justification Formula: Total VMs/ consolidation ratio

SFZ + DMZ : (16 + 6)/4 = 5/6 VM

Impact DMZ VMs will running on the same hosts as Server Farm VMs on separated

network and isolated by VLAN

Server Containment (number of additional hosts required)

Design Choice New VMs: 9

JustificationFormula: New VMs / consolidation ratio

9/4 = 2

Impact Server containment figures can influence procurement planning.


10/34


11/34



Page 11

2.4 Physical DesignAttribute Specification

Vendor and model IBM Blade Center HS22

Processor type

Total CPU sockets

Cores per CPU

Total number of cores

Processor speed

Intel Xeon Processor X5650

2

6

12

2.66GHz

Memory 32GB

Onboard NIC vendor and model

Onboard NIC ports x speed

Number of attached NICs

NIC vendor and model

Number of ports/NIC x speed

Total number of NIC ports

Virtual Fabric Adapter (10 GbE) ships integrated in some

models BroaPDCom 5709S onboard NIC with dual Gigabit

Ethernet ports with TOE2x Gigabit

2

2/4 1GB Port Ethernet Expansion Card (CFFh)

2

4

Number and type of local drives

RAID level

Total storage

2x IBM 146 GB 2.5in SFF Slim-HS 15K 6Gbps SAS HDD

1

135.97GB

System monitoring N/A


12/34



Page 12

Attribute PDC Host 1 PDC Host 2 PDC Host 3 PDC Host 4

Hostname PDCesx01 PDCesx02 PDCesx03 PDCesx04

DPDCesx01.ptptn.go

v.my

PDCesx02.ptptn.go

v.my

PDCesx03.ptptn.go

v.my

PDCesx04.ptptn.gov

.my

vmk0(Managem

ent) 192.168.100.211 192.168.100.212 192.168.100.213 192.168.100.214

Netmask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

Gateway 192.168.100.1 192.168.100.1 192.168.100.1 192.168.100.1

DNS1 192.168.100.240 192.168.100.240 192.168.100.240 192.168.100.240

DNS2 192.168.100.241 192.168.100.241 192.168.100.241 192.168.100.241

1(

)10.10.1.11 10.10.1.12 10.10.1.13 10.10.1.14

Netmask 255.255.255.0 255.255.255.0 255.255.255.0 255.255.255.0

Gateway 192.168.100.1 192.168.100.1 192.168.100.1 192.168.100.1

192.168.100.240 192.168.100.240 192.168.100.240 192.168.100.240

Table1: PTPTN ESXi Details (PDC)


13/34



Page 13

3 Virtual Datacenter

3.1 Requirements Will running as virtual machines and dedicated for Management vCenter Database and application running on the same host Simplify ESXi hosts management with virtual network distributed switch environment

Figure 1: Virtual Datacenter Design


14/34


15/34



Page 15

vCenter Update Manager (VUM) Location

Design Choice Update Manager will be co-located on the vCenter application Server

system and requires a separate database on an external database

system (VCMSDB). Others :-

Download Frequent : Weekly (Sunday) Patch Host/VM : Host ONLY Based Line : Critical & Security

Justification The vCenter System server will be sized appropriately to accommodate

download patch for ESX hosts ONLY.

Impact Another Database creation and management are required by

database team.

Cluster Architecture

Design Choice PTPTN cluster requires four(4)hosts.

The cluster will be managed from vCenter running on virtual machine

which is connected to Server farm network.

Justification Formula: Minimum hosts per cluster using HA calculator

Impact None

VMware High-Availability(HA)

Design Choice Existing VMware HA setup will be used :-

Host Monitoring = Enable Admission Control = Allow Admission Control Policy = Auto VM Default Restart Priority = Medium Host Isolation Response = Power-off VM Enable VM Monitoring = Enable VM Monitoring Sensitivity = Default/Medium

Justification Its proven that the current setting is working fine and no changes are

needed.

Impact vCenter must follow exactly VMware HA settings.


16/34


17/34



Page 17

3.3 Logical Design

Figure 2: vSphere Logical Design for PTPTN HQ & DR Site

Attribute Specification

vCenter Server version 4.1

Physical or virtual system Physical

Number of CPUs

Processor type

Processor speed

1

Virtual CPU

2.0Ghz

Memory 4 GB

Number of NIC and ports 2

Number of disks and disk sizes 135.7GB = 50GB(OS) and 85GB (VMware)

Operating System Type Windows Server 2008 Standard Edition (64 Bit)


18/34



Page 18

3.4 Physical Design

Figure 3: 3x Hosts Cluster Physical Design


19/34



Page 19


Vendor and model VMware virtual hardware 7

Processor type VMware vCpu

NIC vendor and model

Number of ports

Network

VMXNET3

1

Management NetworkLocal disk VMDK

vCenter Application Server PTPTN HQ


Operating System Windows Server 2008 Standard Edition 64 bit R2

No. of CPU 4

No. of Memory 4GB

No. of NIC 1

Physical Disk C:\50GB(OS) and D:\50GB (VMware)

Network Details :- Hostname

Domain IP address Netmask Gateway DNS1 DNS2

vcmsPDC

PTPTN.gov.my192.168.100.215

255.255.255.0

192.168.100.

192.168.100.240

192.168.100.241

SMTP Server Mail.ptptn.gov.my

Sender Email [email protected]

Receiver Email [email protected]

vCenter Database Server PTPTN HQ


SQL Version Microsoft SQL 2008

Database Instances :- vCenter DB Name VUM DB Name

vcdc

vumdb

SQL Account :- Username Password Sql(browser)Default*

vCenter Alarm & Notification

Design Choice Existing alarm (default) both for PTPTN PDC

Email Notification = Yes SNMP Notification = No

Justification No requirement to readjust the existing vCenter alarm. Therefore, existing

alarm setting will be used.

Impact Email Administrator need to allow open relay for new vCenter VM.


20/34



Page 20

4 Network

4.1 Requirements Require 1GbE network connection for vMotion and Fault Tolerance. Virtual networking must be configured for availability, security, and performance.

4.2 Design PatternsvNetwork Standard Switch or vNetwork Distributed Switch

Design Choice A vNetwork standard switch will be configured.

Justification vNetwork distributed switch design will prevent administrator

from managing vNDS network when vCenter goes down.

Impact Will need to configure vSwitch on each host

vSwitch VLAN Configuration

Design Choice Separate VLANs will be assigned to VM Network (SFZ/DMZ),

vMotion, and Fault Tolerance. External Switch Tagging (EST)

will be used with.

Justification Virtual LANs provide isolation and separation of traffic.

Impact All ESX host facing ports must be configured as trunk ports.

vSwitch Load-Balancing Configuration

Design Choice Virtual port ID-based load balancing will be used.

Justification Under this setting, traffic from a given virtual NIC is

consistently sent to the same physical adapter unless a

failover occurs. This setting provides an even distribution of

traffic if the number of virtual NICs is greater than the

number of physical adaptors.

Impact This is the default load-balancing setting. Minimal

configuration is required.

vShield Zones

Design Choice vShield Zones will not be implemented.


21/34



Page 21

JustificationInspection of virtual networking traffic is not a current

requirement.

ImpactExisting hardware firewalls will be utilized to inspect and filter

VM traffic.

4.3 Logical Design

Shading denotes active physical adapter to port group mapping. The vmnics shaded in the same color as a

given port group will be configured as active, with all other vmnics designated as standby.

4.4 Physical Design

vSwitch vmnic NIC/Slot Port Function

00

Onboard

1 Management Network & Prod

1 2 Vmotion Network

12 3

DMZ3 4

vSwitch Port Group Name VLAN ID

0 Management & Prod

0 Vmotion

1DMZ

1


22/34


23/34



Page 23

LUN Presentation

Design Choice LUNs will be masked consistently across all hosts in a cluster.

Justification Having consistent storage presentation ensures that virtual

machines can be run on any host in a cluster. This optimizes high

availability and DRS while reducing storage troubleshooting. It is

importing to minimize differences in LUNs visible across hosts

within the same cluster or vMotion scope.

Impact Requires close coordination with the storage team because LUN

masking is performed at the array level.

Thin vs. Thick Provisioning

Design Choice Maintain using thick

Justification To minimize the risk while performing vSphere upgrade, disk

conversion and major changes on the VM, existing virtualmachine disk type will be maintained as is.

Impact No Thin provision disk will be configured.


24/34



Page 24

5.3 Logical DesignAttribute Specification

Storage type Fiber Channel

Number of Controller N/A

LUN size 500GB

Total LUNs 5

VMFS datastores per LUN 1/500GB

5.4 Physical DesignAttribute Specification

Vendor and model ?ESX host multi-path policy Default / Fixed

Min./max. speed rating of switch ports 1GB / 4GB

VMFS Information

LUN IDDatastore

NameBlock Size Multipath

LUN1 DS01 8MB = 2TB Default / Fixed






25/34



Page 25

6 Virtual Machine

6.1 Requirements Recommended to ONLY running supported guest OS in vSphere All virtual machines must be protected with high-availability (HA) All virtual machines will automatically distributed across 4x ESXi hosts via DRS IBM Guardium need to reconfigure back those virtual CPU, RAM and disk due to the

virtual environment.

Operating system with OEM licensesis not supported and need to be upgraded to fullversion before migrations.

6.2 Design PatternsVirtual Machine Deployment Considerations

Design Choice "Right-size" virtual machines based on application profile.

Justification Virtual machines must be properly designed, provisioned, and

managed to ensure the efficient operation of these applications and

services.

Impact To ensure performance of virtual machine same as before migration.

Swap and Operating System Paging File Location

Design Choice Place the virtual machine swap files in the same location as the other

virtual machine files (default behavior).

Justification Keeping files on the default datastore is easier to manage. Moving

the vmswap files to a different location for performance or

replication bandwidth issues requires additional configuration and

management processes.

Impact If future requirements mandate that virtual machine swap files be

moved to a separate location, all relevant virtual machines will need

to be reconfigured.


26/34


Private and Confidential Page 26

6.3 Virtual Machines Specification

1 ... > 1

2 ... > 1

3 () // & C > 1

4 () C > 1

5 () C > 1

6 () C > 1

7 (D) C > 1

8 () C > 1

9 / (D) C > 1

10 A C > 1

11 B * // A 4

12 B * A 4

13 B * A 4

14 EA E 2003 0

15 EA B 2003 1

16 EA //2 2003 1

17 EA E 2003 0

18 EA B 2003 1

19 EA 2003 1

20 EA E 2003 0

21 EA B 2003 1

22 EA 2003 1

23 2003 1


27/34


28/34



Page 28

8 Appendix

8.1 Appendix A Security ConfigurationvSphere Roles and Permissions

vSphere Role

Name

Corresponding AD

Groups

Enabled vSphere

Privileges

vCenter Inventory

Level for Permissions

Description

Enterprise vSphere

Administrators*

Admin All Datacenter and allchild objects

Administrative

rights to the entire

vSphere

infrastructure

vSphere Network

Administrators*

Admin Network and allchild privileges

Network and all

network child

objects ONLY

Administrative

rights to all

vSphere network

components

vSphere Storage

Administrators*

Admin Datastore and allchild privileges

Storage Viewsand all child

privileges

Datastores and all

datastore childobjects ONLY

Administrative

rights to allvSphere storage

components

8.2 Appendix B Port RequirementsESX Port requirements

Description Port(s) Protocol Direction

vSphere Client to ESX/ESXi host 443, 902, 903 TCP Incoming

VM Console to ESX/ESXi host 903 TCP Incoming

ESX/ESXi host and vCenter Heartbeat 902 UDP Incoming/

Outgoing

ESX/ESXi host DNS client 53 UDP Outgoing

ESX/ESXi host NTP client to NTP server 123 UDP Outgoing

ESX/ESXi host NFS 111, 2049 TCP, UDP Outgoing

VMotion between ESX/ESXi hosts 8000 TCP Incoming/

Outgoing

HA between ESX/ESXi hosts 2050-2250, 8042-8045 TCP, UDP Incoming/

Outgoing

ESX/ESXi host to Update Manager 80, 443, 9034 TCP Outgoing

Update Manager to ESX/ESXi host 902, 9000-9010 TCP Incoming

ESX/ESXi host CIM Client to Secure Server 5988, 5989 TCP Incoming

ESX/ESXi host CIM service location protocol 427 TCP, UDP Incoming/

Outgoing


29/34



Page 29

vCenter Server Port requirements


vSphere Client to vCenter Server 443 TCP Incoming

vSphere Web Access to vCenter Server 443 TCP Incoming

VM Console to vCenter Server 902, 903 TCP IncomingESX/ESXi host and vCenter Heartbeat 902 UDP Incoming/

Outgoing

LDAP 389 TCP Incoming

Linked Mode SSL 636 TCP Incoming

ESX/ESXi 2.x/3.x host to legacy License Server 27000, 27010 TCP Incoming/

Outgoing

Web Services HTTP 8080 TCP Incoming

Web Services HTTPS 8443 TCP Incoming

vCenter SNMP server polling 161 UDP Incoming

vCenter SNMP client trap send 162 UDP Outgoing

vCenter DNS client 53 UDP Outgoing

vSphere Active Directory integration 88, 445 UDP, TCP Outgoing

ODBC to MS SQL Server database 1433 TCP Outgoing

Oracle Listener port to Oracle database 1521 TCP Outgoing

vCenter Converter Standalone Port Requirements


Converter Client (GUI) to Converter Server 443

(configurable)

TCP Incoming

Converter Server to remote Windows powered-on

Machine remote agent deployment, Windows file

sharing

445 and 139 TCP Incoming


Machine remote agent deployment, Windows file

sharing

137 and 138 UDP Incoming


machine agent connection

9089 TCP Incoming

Converter Server/Linux agent to remote Linux

powered-on machine

22 TCP Incoming

Converter Server/Agent to managed destination VM creation/management (includes VM Helper

creation/management)

443 TCP Incoming

Windows powered-on machine to managed

destination hot clone access (vCenter/ESX/ESXi)

443 TCP Incoming

Windows powered-on machine to managed

destination hot clone copy (ESX/ESXi)

902 TCP Incoming

Windows powered-on machine to hosted

destination hot clone Windows file sharing



30/34



Page 30

Windows powered-on machine to hosted

destination hot Clone Windows file sharing


Helper VM to Linux powered-on machine hot

clone

22 TCP Outgoing

Converter Server/Agent to managed

source/destination VM import access

(vCenter/ESX/ESXi)

443 TCP Incoming

Converter Server/Agent to managed

source/destination VM import copy from/to

ESX/ESXi

(Traffic from ESX/ESXi to ESX/ESXi direct for disk-

based cloning only)

902 TCP Incoming

Converter Server/Agent to hosted

source/destination VM import Windows file

sharing


Converter Server/Agent to Hosted

Source/Destination VM Import Windows file

sharing


vCenter Update Manager Port Requirements


Update Manager to vCenter Server 80 TCP Incoming

Update Manager to external sources (to acquire

metadata regarding patch updates from VMware

80, 443 TCP Outgoing

Update Manager client to Update Manager server 8084 TCP Incoming

Listening ports for the web server, providing access

to the plug-in client installer and the patch depot

9084, 9087 TCP Incoming

Update Manager to ESX/ESXi host (for pushing

virtual machine and host updates/patches)

902 TCP Incoming


31/34


32/34



Page 32

9 References

Item URL

Documentation http://www.vmware.com/support/pubs

VMTN Technology information http://www.vmware.com/vcommunity/technology

VMTN Knowledge Base http://kb.vmware.com

Discussion forums http://www.vmware.com/community

User groups http://www.vmware.com/vcommunity/usergroups.html

Technical Papers http://www.vmware.com/vmtn/resources

Network throughput between virtual

machines

http://kb.vmware.com/kb/1428

Detailed explanation of vMotion

considerations

http://www.vmware.com/resources/techresources/1022

Time keeping in virtual machines http://www.vmware.com/vmtn/resources/238

http://kb.vmware.com/kb/1006427

VMFS partitions http://www.vmware.com/vmtn/resources/608

VI3 802.1Q VLAN Solutions http://www.vmware.com/pdf/esx3_vlan_wp.pdf

VMware Virtual Networking Concepts http://www.vmware.com/resources/techresources/997

VMware vCenter Update Manager

documentation

http://www.vmware.com/support/pubs/vum_pubs.html

VMware vCenter Update Manager

Best Practices


Performance Best Practices for VMware

vSphere 4.0


Recommendations for aligning VMFS

partitions

http://www.vmware.com/vmtn/resources/608

Performance Troubleshooting for

VMware vSphere

http://communities.vmware.com/docs/DOC-10352

Large Page Performance http://www.vmware.com/resources/techresources/1039

VMware vSphere PowerCLI http://www.vmware.com/support/developer/windowstoolkit/VI3 security hardening http://www.vmware.com/vmtn/resources/726

VMware HA: Concepts and Best

Practices


Java in Virtual Machine on ESX http://www.vmware.com/files/pdf/Java_in_Virtual_Machines_o

SX-FINAL-Jan-15-2109.pdf


33/34



Page 33

CPU scheduler in ESX 4.0 http://www.vmware.com/resources/techresources/10059

Dynamic Storage Provisioning (Thin

Provisioning)


Understanding memory resource

management on ESX



34/34