Beruflich Dokumente
Kultur Dokumente
Rawley Burbridge IBM Systems and Technology Group ISV Enablement September 2012
Table of Contents
Abstract........................................................................................................................................2 Introduction .................................................................................................................................2
Guidance and assumptions ..................................................................................................................... 3
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 1
Abstract
The purpose of this paper is to provide insight into the value proposition of the IBM System Storage SAN Volume Controller and the IBM Storwize V7000 disk family for VMware environments, and to provide best practice configurations.
Introduction
The many benefits that server virtualization provides has led to its explosive adoption in todays data center. Server virtualization with VMware vSphere has been successful in helping customers use hardware more efficiently, increase application agility and availability, and decrease management and other costs. The IBM System Storage SAN Volume Controller is an enterprise-class storage virtualization system that enables a single point of control for aggregated storage resources. SAN Volume Controller consolidates the capacity from different storage systems, both IBM and non-IBM branded, while enabling common copy functions and non-disruptive data movement, and improving performance and availability. The IBM Storwize V7000 disk family has inherited the SAN Volume Controller software base, and as such offers many of the same features and functions. The common software base of the SAN Volume Controller and the IBM Storwize V7000 disk family allows IBM to conveniently offer the same VMware support, integrations, and plug-ins. This white paper focuses on and provides best practices for the following key components: IBM System Storage SAN Volume Controller IBM System Storage SAN Volume Controller combines hardware and software into an integrated, modular solution that forms a highly-scalable cluster. SAN Volume Controller allows customers to manage all of the storage in their IT infrastructure from a single point of control and also increase the utilization, flexibility, and availability of storage resources. For additional information about IBM SAN Volume Controller, refer to the following URL: ibm.com/systems/storage/software/virtualization/svc/index.html IBM Storwize V7000 and Storwize V7000 Unified systems The IBM Storwize V7000 system provides block storage enhanced with enterprise-class features to midrange customer environments. With the built-in storage virtualization, replication capabilities, and key VMware storage integrations, the Storwize V7000 system is a great fit for VMware deployments. The inclusion of IBM real-time compression further enhances the strong feature set of this product. The IBM Storwize V7000 Unified system builds upon the Storwize V7000 block storage capabilities by also providing support for file workloads and file specific features such as IBM Active Cloud Engine. For additional information about the IBM Storwize V7000 system, refer to the following URL: ibm.com/systems/storage/disk/storwize_v7000/index.html
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 2
VMware vSphere 5.0 VMware vSphere 5.0 (at the time of this publication) is the latest version of a market-leading virtualization platform. vSphere 5.0 provides server virtualization capabilities and rich resource management. For additional information about VMware vSphere 5.0, refer to the following URL: www.vmware.com/products/vsphere/mid-size-and-enterprise-business/overview.html
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 3
Infrastructure services
Infrastructure services perform the virtualization of server hardware, storage, and network resources. The services within the infrastructure services category are the foundation of the VMware vSphere platform.
Application services
The components categorized as application services address availability, security, and scalability concerns for all applications running on the vSphere platform, regardless of the complexity of the application.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 4
Figure 2 shows the main pillars of functionality provided by VMware vCenter Server.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 5
Feature 64 Terabyte VMFS volumes Support for more files Support for 64 TB physical raw device mappings Unified block size (1 MB) Atomic Test and Set (ATS) usage vStorage APIs for Array Integration (VAAI) locking mechanism Sub-blocks for space efficiency
No Limited
Yes Unlimited
64 KB (maximum approximately 3 k)
8 KB (maximum approximately 30 k) 1 KB
No
VMware provides a nondisruptive upgrade path between the various versions of VMFS.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 6
Load balancing Storage DRS continuously monitors VMFS datastore space usage and latency. Configurable presets can trigger Storage DRS to issue migration recommendations when response time and or space utilization thresholds have been exceeded. Storage VMotion is used to migrate virtual machines to bring the VMFS datastores back into balance. Figure 4 provides an example of Storage DRS load balancing.
VMFS datastore maintenance mode The last use case of Storage DRS is a way to automate the evacuation of virtual machines from a VMFS datastore which needs to undergo maintenance. Previously, each virtual machine would need to be migrated manually from the datastore. Datastore maintenance mode allows the administrator to issue the command to place the datastore in maintenance mode, and Storage DRS migrates all the virtual machines from the datastore.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 7
that are accessing a VMFS datastore. Virtual machine disk access is manipulated by controlling the host queue slots. Figure 5 shows two examples of virtual machines accessing a VMFS datastore. Without Storage I/O Control enforcing share priority, a non-production data mining virtual machine can monopolize disk resources, impacting the production virtual machines.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 8
In addition to providing intelligence of the storage system, the SATP also contains default settings for what Path Selection Plug-in (PSP) is used by the ESXi host for each storage volume.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 9
The PSP configured on a volume can be viewed from the Manage Paths window as displayed in Figure 8.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 10
Managing the preferred paths across hosts and VMFS datastores can become an unnecessary burden to administrators, and this is why IBM recommends modifying the default behavior of vSphere 4.0 through vSphere 5.0.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 11
From the Path Selection list, select Round Robin (VMware) and click Change, as shown in Figure 10.
IBM Storage Management Console for VMware vCenter The IBM Storage Management Console for VMware vCenter version 2.6.0 includes the ability to set multipath policy enforcement. This setting can enforce the Round Robin policy on all new volumes provisioned through the management console. This selection option is displayed in Figure 11.
Modify all volumes This method modifies the default PSP to be Round Robin. All new discovered volumes use the new default behavior, however, existing volumes are not
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 12
modified until the ESXi host rediscovers all the volumes as is done during a reboot. The default behavior can be modified with the following vSphere CLI commands: ESX/ESXi 4.x: esxcli nmp satp setdefaultpsp psp VMW_PSP_RR --satp VMW_SATP_SVC ESXi 5.0: esxcli storage nmp satp set --default-psp VMW_PSP_RR --satp VMW_SATP_SVC This method is recommended by IBM for simplicity and global enforcement.
VMware ESXi host Fibre Channel and iSCSI connectivity best practices
IBM SAN Volume Controller and the Storwize V7000 disk family support the FC and iSCSI protocols for block storage connectivity with VMware ESXi. Each protocol has its own unique best practices, which is covered in the following sections.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 13
VMware ESXi hosts must use the generic host object type for SAN Volume Controller and the Storwize V7000 disk family. As VMware is generally configured to allow multiple hosts to access the same clustered volumes, two approaches can be used for ensuring that consistency is maintained when creating host objects and volume access.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 14
The advantage of this approach is that the storage host definitions are very clear to create and maintain. The disadvantage, however, is when volume mappings are created; they must be created for each storage host object. It is also import, but not required, to use the same SCSI-LUN numbers across VMware ESXi hosts. This is more difficult to maintain with the single VMware ESXi host per storage object method.
Figure 14: Single storage host object for multiple ESXi hosts
The advantage of this approach is that volume mapping is simplified because a single mapping is performed for the VMware ESXi cluster against a per-host basis. The disadvantage of this approach is that the storage host definitions are not as clear as expected. If a VMware ESXi host is being retired, the WWPNs for that host must be identified and removed from the storage host object. Both of the storage host object approaches are valid, and the advantages and disadvantages should be weighed by each customer. IBM recommends that a single approach is chosen and implemented on a consistent basis.
iSCSI connectivity
VMware ESXi includes a software iSCSI initiator which can be used with 1 GbE or 10 GbE Ethernet connections. The VMware ESXi iSCSI initiator is the only supported way to connect to SAN Volume Controller or the Storwize V7000 disk family. Each VMware ESXi host can have a single iSCSI initiator and that initiator provides the source iSCSI qualified name (IQN).
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 15
A single iSCSI initiator does not limit the number or type of network interface cards (NICs) which can be used for iSCSI storage access. VMware best practice recommends that for each physical NIC which will be used, a matching virtualized VMkernel port NIC created and bonded to the physical NIC. The VMkernel port is assigned an IP address, while the physical NIC acts as a virtual switch uplink. Figure 15 provides an example of a VMware ESXi iSCSI initiator configured with two VMkernel IP addresses, and bonded to two physical NICs.
The VMware ESXi iSCS initiator supports two types of storage discovery which is covered in the following sections.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 16
With static discovery, each of the source VMkernel IP addresses performs an iSCSI session login to each of the static target port IPs. Each time a login occurs, an iSCSI session is registered on the node in which the login occurred. The following example provides an overview of the sessions created with static discovery. Source VMkernel IPs of: 1.1.1.1 1.1.1.2
SAN Volume Controller or the Storwize V7000 disk family system target IPs of: 1.1.1.10 1.1.1.11 1.1.1.12 1.1.1.13
The following sessions are created on each node: Vmk-0 (1.1.1.1) to Port-0 (1.1.1.10) Vmk-0 (1.1.1.1) to Port-1 (1.1.1.11) Vmk-1 (1.1.1.2) to Port-0 (1.1.1.10) Vmk-1 (1.1.1.2) to Port-1 (1.1.1.11)
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 17
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 18
When using iSCSI connectivity for VMware ESXi along with SAN Volume Controller and the Storwize V7000 disk family systems, the important thing to note is how many iSCSI sessions are created on each node. For storage systems running software older than 6.3.0.1, only one session can be created on each node. This means that the following rules must be followed: Maximum of one VMware iSCSI initiator session per node. Static discovery only, dynamic discovery is not supported. VMware ESXi host iSCSI initiator can only have one VMkernel IP associated with one physical NIC.
For storage systems running software version 6.3.0.1 or newer, these rules are changed to the following: Maximum of four VMware iSCSI initiator sessions per node. Static and dynamic discovery are both supported. VMware ESXi host iSCSI initiator can have up to two VMkernel IPs associated with two physical NICs.
The configuration presented in Figure 17 provides a redundancy for the VMware ESXi host since two physical NICs are actively used. It also uses all available ports of both nodes of the storage system. Regardless of whether static or dynamic discovery is used, this configuration stays within the guidelines of four sessions per node.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 19
In both situations the storage capacity requirement is satisfied, however the storage performance offered by each disk configuration is very different. To understand the storage capacity and performance requirements of a VMware virtualized workload, it is important to understand what applications and workloads are running inside the virtual machines. Twelve virtual machines running Microsoft Windows 2008 do not generate a significant amount of storage performance. However, if those 12 virtual machines are also running Microsoft SQL Server, the storage performance requirement can be very high. The SAN Volume Controller and the Storwize V7000 disk family systems enable volumes to use a large number of disk spindles by striping data across all the spindles contained in a storage pool. A storage pool can contain a single managed disk (MDisk), or multiple MDisks. The IBM Redbooks titled SAN Volume Controller Best Practices and Performance Guidelines provides performance best practices for configuring MDisks and storage pools. The Redbooks can be found at the following website: ibm.com/redbooks/redbooks.nsf/RedbookAbstracts/sg247521.html?OpenDocument The heterogeneous storage workload created by VMware benefits from the volume striping performed by SAN Volume Controller and the Storwize V7000 disk family. It is still important to ensure that the storage performance provided by the storage pool is satisfactory to the workload, however, as most VMware workloads are variable in their times of peak demand, the volume striping and more spindles available enables more consolidation.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 20
and formatted as a VMFS datastore. The support for large volumes has been made possible by eliminating the legacy SCSI-2 locking which VMware used to maintain VMFS integrity. More information about that is available in the VMware integrations section. The advantage of large volumes to VMware administrators is that it simplifies management. As long as a storage pool has the storage capacity and performance available to satisfy the requirements, the maximum VMFS datastore size of 64 TB can be used. However operations such as IBM FlashCopy, Metro Mirror or Global Mirror, or Volume Mirroring are impacted by volume size. For example, the initial replication of a 64 TB volume can be a significant amount of time. VMware vSphere 5.0 offers the ability to create datastore clusters, which are a logical grouping of VMFS datastores into a single management object. This means smaller, more manageable VMFS volumes can be grouped into a single management object for VMware administrators. The IBM recommendation for volume and datastore sizing with VMware vSphere 5.0 and SAN Volume Controller and the Storwize V7000 disk family is to use volumes sized between 1 TB to 10 TB, and group these together into the VMware datastore clusters.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 21
performing SSDs. Easy Tier reduces the overall cost and investment of SSDs by effectively managing their usage. Easy Tier works seamless to the applications accessing the storage, including VMware and the virtualized workloads running on it. There are also no special configurations which must be implemented for an application to benefit from Easy Tier.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 22
Figure 19: vStorage APIs for Array Integration relationship to VMware functions
The implementation of vStorage APIs for Array Integration in vSphere 4.1 introduced three primitives: hardware-accelerated block zero, hardware-assisted locking, and hardware-accelerated full copy. The VMware vSphere 4.1 implementation of VAAI does not use standard SCSI commands to provide instructions to the storage array, so a device driver is required to be installed on the vSphere 4.1 ESX/ESXi hosts. You can find more details about installing the IBM Storage Device Driver for VMware VAAI at the following URL: http://delivery04.dhe.ibm.com/sar/CMA/SDA/02l6n/1/IBM_Storage_DD_for_VMware_VAAI_1.2.0_ IG.pdf The vSphere 5.0 implementation of VAAI also began using standard SCSI commands, so a device driver was no longer required to be installed on the vSphere 5.0 ESXi hosts. With both vSphere 4.1 and 5.0 implementations of VAAI, the SAN Volume Controller or the Storwize V7000 disk family system must be running the software version 6.2.x or newer. The VAAI primitives can be easily enabled and disabled with the following methods:
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 23
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 24
The IBM Storage Management Console for VMware is installed and runs as a Microsoft Windows Server service on the vCenter Server. When a vSphere client connects to the vCenter Server, the running service is detected and the features provided by the Storage Management Console are enabled for the client. Features of the IBM Storage Management Console include: Integration of the IBM storage management controls into the VMware vSphere graphical user interface (GUI) with the addition of an IBM storage resource management tool and a dedicated IBM storage management tab Full management of the storage volumes including: volume creation, deletion, resizing, renaming, mapping, unmapping, and migration between storage pools Detailed storage reporting such as capacity usage, FlashCopy or snapshot details, and replication status
The graphic in Figure 22 shows the relationships and interaction between the IBM plug-in, VMware vCenter and vSphere, and the IBM storage system.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 25
Data consistent backups by leveraging the Microsoft Volume Shadow Copy Service (VSS) for virtual machines running supported Microsoft Windows operating systems.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 26
Tivoli Storage Manager for Virtual Environments can centrally back up virtual machines across multiple vSphere hosts without the requirement of a backup agent within the virtual machines by using VADP. The backup operation is off loaded from the vSphere host, allowing the host to run more virtual machines. Figure 23 shows an example of a Tivoli Storage Manager for Virtual Environments architecture.
Tivoli Storage Manager for Virtual Environments includes a GUI that can be used from the VMware vSphere Client. The Data Protection for VMware vCenter plug-in is installed as a vCenter Server extension in the Solutions and Applications panel of the vCenter Server system. The Data Protection for VMware vCenter plug-in can be used to complete the following tasks: Create and initiate or schedule a backup of virtual machines to a Tivoli Storage Manager server. Restore files or virtual machines form a Tivoli Storage Manager server to the vSphere host or datastore. View reports of backup, restore, and configuration activities.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 27
Figure 24 shows the Getting Started page which is displayed when the plug-in is first opened.
Figure 24: The Getting Started page of Tivoli Data Protection for VMware vCenter plug-in
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 28
Summary
The IBM System Storage SAN Volume Controller and the Storwize V7000 disk family systems provide scalability and performance for VMware vSphere environments through the native characteristics of the storage systems, and also through VMware API integrations. This paper outlined configuration best practices for using SAN Volume Controller and the Storwize V7000 disk family, and also included information on efficiency features such as thin provisioning, Easy Tier, and Real-Time Compression that can be seamlessly deployed within a VMware environment.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 29
Resources
The following websites provide useful references to supplement the information contained in this paper:
IBM Systems on PartnerWorld ibm.com/partnerworld/systems IBM Redbooks ibm.com/redbooks IBM System Storage Interoperation Center (SSIC) ibm.com/systems/support/storage/config/ssic/displayesssearchwithoutjs.wss?start_over= yes IBM Storwize V7000 ibm.com/storage/storwizev7000 IBM System Storage SAN Volume Controller ibm.com/systems/storage/software/virtualization/svc/index.html IBM TechDocs Library ibm.com/support/techdocs/atsmastr.nsf/Web/TechDocs VMware vSphere 5 Documentation Center pubs.vmware.com/vsphere50/index.jsp?topic=/com.vmware.vsphere.install.doc_50/GUID-7C9A1E23-7FCD-42959CB1-C932F2423C63.html
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 30
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 31
presented here to communicate IBM's current investment and development activities as a good faith effort to help with our customers' future planning. Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve throughput or performance improvements equivalent to the ratios stated here. Photographs shown are of engineering prototypes. Changes may be incorporated in production models. Any references in this information to non-IBM websites are provided for convenience only and do not in any manner serve as an endorsement of those websites. The materials at those websites are not part of the materials for this IBM product and use of those websites is at your own risk.
VMware vSphere best practices for IBM SAN Volume Controller and IBM Storwize V7000 disk family 32