DroboElite VMware Best Practices

Data Robotics DroboElite and VMware vSphere4
Best Practice and Configuration Guide
Quick Reference & Notes:

Section 1: DroboElite storage array
For highest availability, please use at least two switches. You may use one gigabit switch, but we recommend configuring it with separate VLANs and/or networks. Configuring your switch in this manner makes it easier to move to a redundant network topology in the future.
Section 2: Preparing DroboElite for use with VMware vSphere 4

Although DroboElite supports 16TB volumes for use with RDMs, VMware VMFS supports a maximum LUN size of 2TB.
Section 3: Configuring VMware iSCSI adapters

There may be a slight delay while the iSCSI discovery process completes. For ESX/ESXi servers supporting VMotion, HA, and DRS, a host group must be defined so that the DroboElite storage system has a configured iSCSI path to each of the hosts.
Section 4: Creating a VMFS datastore to use DroboElite

For more information on configuring ESX/ESXi, see the VMware Support website at support.vmware.com. Data Robotics has determined that optimal performance is achieved with 8MB block sizes. Using a smaller block size will adversely affect performance.
Other Tips, Tricks, and Notes

If you experience iSCSI timeouts with your DroboElite, we recommend that you increase the iSCSI timeout setting to 14 seconds using the following command:
esxcfg-advcfg -s 14000 /VMFS3/HBTokenTimeout
The recommended Multi-pathing method is MRU (Most Recently Used). By default it will be
fixed. To change the parameter use the following command:
esxcli nmp satp setdefaultpsp --psp VMW_PSP_MRU --satp VMW_SATP_DEFAULT_AA
1
NOTE: Operating system alignment is critical within a VMFS datastore. Although vSphere4 ensures proper alignment at the (VMFS) volume level, the issue of proper guest operating system alignment is still a potential issue with VMware performance with the DroboElite. It is critical to ensure proper alignment of the guest operating systems, within the virtual machines (VMs). Misaligned guest O/S partitions are likely to result in degraded performance and could ultimately cause a loss of connectivity to the datastore on the DroboElite. VMware has great documentation on the topic and several are referenced below. Although, the following VMware document was created for version 3.0, the section entitled "Instructions for Guest File System Alignment", is still applicable to vSphere4.0 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide v4 May 2010 Page 1
http://www.vmware.com/pdf/esx3_partition_align.pdf Please follow the instructions carefully. Finally, here is VM Ware's Best Practices for vSphere4.0: http://www.vmware.com/pdf/Perf_Best_Practices_vSphere4.0.pdf Please refer to the section entitled: "ESX Storage Considerations.
Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide v4 May 2010
Page 2
Executive Summary
Data Robotics, Inc. is excited to announce VMware certification with VMware vSphere 4 using the award winning DroboElite iSCSI storage array. This document will detail best practices for a successful deployment using the DroboElite in an ESX/ESXi environment. iSCSI is recognized for its simple integration, interoperability, lower cost, and the ability to utilize a companys inherent networking skills for quick and rapid adoption. iSCSI is a standard IP-based storage access protocol for interconnecting servers and storage using standard Ethernet. iSCSI is built upon the SCSI and TCP/IP protocols, the dominant standards for storage and networking in use today. The DroboElite allows an organization to effectively leverage the capabilities of the VMware Infrastructure (including VMotion, Distributed Resource Scheduling, and High Availability). Storage must be network accessible, highly available, and easily scaled without impacting applications as workloads change and grow. The chosen storage solution must be simple to deploy, easy to manage, and intrinsically reduce ongoing costs to truly leverage the economic benefits of server consolidation. VMwares virtual server software and DroboElites virtualized architecture are complementary technologies that deliver tremendous rewards. Because virtual servers require a simple, flexible and cost-effective virtual storage solution, customers can now choose Data Robotics iSCSI storage over other, more expensive iSCSI solutions. The simple integration, flexibility and unmatched scalability are driving more and more leading organizations worldwide to embrace virtualized iSCSI storage for the new virtual data center.
Introduction
This document describes the configuration steps to deploy VMware vSphere 4 solutions on DroboElite storage arrays from Data Robotics.
Support Matrix
DroboElite Supported ESX Software Versions and Features vMotion / Data Robotics Supported Recommended Storage Storage VMware ESX Hosts vMotion Device Software Supported Support VMware HA / DRS Support
Support Notes VMFS data stores should be formatted with 8MB block size
DroboElite
vSphere 4
4-6
Yes
Yes
Page 3
Section 1: DroboElite storage array

Standard Configuration: The standard configuration includes a DroboElite storage array with a single controller with two 1 gigabit Ethernet iSCSI ports. The DroboElite storage solution can be deployed to support four to six ESX/ESXi hosts.
Reference Solution
The following configuration illustrates the recommended deployment for the DroboElite storage array with the ESX/ESXi software. In the figure below, four ESX/ESXi servers are connected to the DroboElite storage array with one dedicated VLAN. On each server, a virtual NIC is created with two NICs connected to an iSCSI VLAN. For more storage, additional DroboElite arrays may be connected to the same VLAN. All DroboElite storage arrays are managed via a single instance of Drobo Dashboard (running on Windows or Mac OS X) per VLAN or iSCSI network. NOTE: All the devices are in the same iSCSI VLAN.
*NOTE: To optimize DroboElite for performance, you should use a separate, dedicated gigabit switch for iSCSI traffic or a dedicated iSCSI VLAN within a managed switch.
3
Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide v4 May 2010 Page 4
Section 2: Preparing DroboElite for use with VMware vSphere 4

Unpack the DroboElite and install Drobo Dashboard on a computer running Windows or Mac OS X (note please check www.drobo.com/support for supported OS versions). Next, insert at least two SATA hard drives and connect the DroboElite to the computer using the USB cable included in the packaging. Once Drobo Dashboard discovers the DroboElite, follow this procedure to configure the DroboElite for iSCSI. 1. Click on Advanced Controls
2. Click on Tools
Page 5
3. Click on Check For Updates to make sure you are running the latest software and firmware versions. Follow the instructions to update either if indicated. Then click on Settings.
4. Verify that the Disk Drive Spin Down is set to Never
Page 6
5. Click the iSCSI tab 6. Set IP addresses for both iSCSI1 and iSCSI2 a) Set the IP address and subnet mask (record this information for later use.) b) Click OK
5 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide
Page 7
7. Enable Administrative password. If your environment requires this level of added security please select the Admin tab: Select Enable administrative password protection. Fill in Username and Password information. This will change Drobo Dashboard with the username and password information before the DroboElite can be managed. Click OK. At this point, Drobo Dashboard will ask you to restart the DroboElite to apply all of your changes. While the DroboElite is restarting, remove the USB, attach the system (the management station and the DroboElite) onto the iSCSI network.
Page 8
8. Once restarted and rediscovered by Drobo Dashboard, Go to Advanced Controls -> Tools -> Volume Management.
9. Listed are the Smart Volumes on the DroboElite. By default, there is a single 16TB volume created. Feel free to delete this volume, as it is not needed for VMware.

NOTE: Although DroboElite supports 16TB volumes for use with RDMs, VMware VMFS supports a maximum LUN size of 2TB.
Page 9
10. Up to 128 Smart Volumes may be created. In this example, we are creating a 1TB volume. This unit had 48 Smart Volumes to begin with and we will add one more. Click Create Volume -> Multi Host
The Default size is 16TB, but please chose 1TB or 2TB. It is very important to choose Multi Host, otherwise only one ESX server will be able to see the Smart Volumes.
Click OK. Notice a new volume is ready to be created.
7
Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide v4 May 2010 Page 10
11. Click Submit Changes -> Yes, Apply Changes and allow the DroboElite to create the new Smart Volume(s). Note: You can create and delete multiple volumes at once before clicking Submit Changes.
12. If you plan to use CHAP within VMware, please enable CHAP by clicking the Enable button next to the newly created Smart Volume. The username is DroboElite for all CHAP volumes.
13. Connect the DroboElite to the iSCSI VLAN previously described above.
Page 11
Section 3: Configuring VMware iSCSI adapters

This section lists the steps required to configure the software initiator on ESX/ESXi. For more information, see the VMware Configuration Guide at www.vmware.com. Configurations examples are performed on the VI client for vSphere 4 for all ESX servers. Connect DroboElite to the iSCSI VLAN. Using vSphere, connect to the ESX cluster and follow the steps below. Check iSCSI Software Adapter. 1. Select Configuration -> Storage Adapters on the ESX/ESXi server.
Page 12
2. Select iSCSI Software Adapter and click on Properties. The iSCSI Initiator Properties window is displayed.
3. Ensure that the Software Initiator Properties Status is Enabled. If not then the iSCSI Initiator needs to be enabled to allow the ESX server to connect to the DroboElite. a. Under the General tab, click Configure. b. Ensure it is enabled - click the Enabled checkbox, if necessary. c. Click OK. d. Select Close.
Page 13
4. Select iSCSI Software Adapter under Storage Adapters. iSCSI initiator name is listed. 5. Select Properties under Storage Adapters. a. Select the Dynamic Discovery tab. b. Select Add.
NOTE: There may be a slight delay while the iSCSI discovery process completes. 6. Enter the IP address of the DroboElite storage array (Port should be 3260) -> click OK
NOTE: Repeat the steps above for both IP addresses belonging to the DroboElite.
Page 14
NOTE: For ESX/ESXi servers supporting VMotion, HA, and DRS, a host group must be defined so that the DroboElite storage subsystem has a configured iSCSI path to each of the hosts. If you enabled CHAP for the Smart Volumes Created, click the CHAP button. Select Use CHAP Enter DroboElite as the username and the password you chose.
Page 15
Section 4: Creating a VMFS datastore to use DroboElite

Connect to the ESX/ESXi server/Virtual Center using vSphere and follow the steps below. 1. Click the Configuration tab a. Select Storage Adapters b. Select the iSCSI Software Adapter and right-click Rescan. The newly created iSCSI target and LUN is displayed on the ESX/ESXi software.
NOTE: For more information on configuring ESX/ESXi, see the VMware Support website at support.vmware.com. 2. Go to Home -> Inventory -> Datastores. On the Getting Started tab click Add a datastore
Page 16
Page 17
Select which host to add the datastore.
11 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide 3. Select Disk/LUN -> Next
Page 18
4. Select the newly created iSCSI LUN -> Next. The LUN id matches the Volume id when you created in Drobo Dashboard above. In this case, id49.
5. Review the disk layout -> Next
e vSphere 4 Best Practice Guide
Page 19
6. Provide a name for the VMFS datastore -> Next
7. Select the appropriate block size (8MB) and capacity for the VMFS database -> Next NOTE: Data Robotics has determined that optimal performance is achieved with 8MB block sizes. A block size smaller than 8MB block size will adversely affect performance.
Page 20
8. Review the disk layout and click Finish to create the VMFS datastore. The new datastore is ready for storing virtual machine images.
Page 21
NOTE: All NICs in a vSwitch must be in the same VLAN. If you connect the NICs directly to the DroboElite storage array, then they will not be accessible on a VLAN.
Copyright 2010 Data Robotics, Inc. Data Robotics, DroboElite, DroboPro, Drobo, DroboShare, BeyondRAID, and Smart Volumes are trademarks of Data Robotics, Inc., which may be registered in some jurisdictions. All other trademarks used are owned by their respective owners. All rights reserved. Specifications subject to change without notice.
Page 22

DroboElite VMware Best Practices

Încărcat de

Informații document

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

DroboElite VMware Best Practices

Încărcat de

Drepturi de autor:

Formate disponibile

Data Robotics DroboElite and VMware vSphere4

Best Practice and Configuration Guide

Quick Reference & Notes:

Section 2: Preparing DroboElite for use with VMware vSphere 4

Section 3: Configuring VMware iSCSI adapters

Section 4: Creating a VMFS datastore to use DroboElite

Other Tips, Tricks, and Notes

esxcli nmp satp setdefaultpsp --psp VMW_PSP_MRU --satp VMW_SATP_DEFAULT_AA

Section 1: DroboElite storage array

Section 2: Preparing DroboElite for use with VMware vSphere 4

4. Verify that the Disk Drive Spin Down is set to Never

5 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide

6 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide

Click OK. Notice a new volume is ready to be created.

8 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide

Section 3: Configuring VMware iSCSI adapters

9 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide

Section 4: Creating a VMFS datastore to use DroboElite

Select which host to add the datastore.

5. Review the disk layout -> Next

e vSphere 4 Best Practice Guide

6. Provide a name for the VMFS datastore -> Next

13 Data Robotics DroboElite and VMware vSphere 4 Best Practice Guide

S-ar putea să vă placă și