Archive

Archive for the ‘Storage’ Category

vSphere 5.x Storage vMotion does not rename virtual machine files on completing migration

February 1, 2013 6 comments

Since vSphere 5.0 was released, a feature previously avaiable was found to not work anymore.  This feature was that after a successful storage vmotion migration a renamed virtual machines’ files were no longer renamed to match.

This feature has been restored in vSphere 5.0 update 2, and in vSphere 5.1 update 1, however must be turned on.

Having upgraded, the option provisioning.relocate.enableRename must be set in the advanced vCenter Server settings.

Using the vSphere Client, navigate to the Home Page, and select vCenter Server Settings (under Administration), then select Advanced Settings from the left.  The parameter needs to be added with the value true as below:

vcenteradvsettings

The vCenter Service (or vCenter Server) will now need to be restarted.  Afterwards Storage vMotion should now rename the files when the virtual machine has been renamed.

This currently is not available for vSphere 5.1, but will be included in a future update.

Categories: Storage, vSphere

Tricking ESXi into seeing an SSD device

January 30, 2013 3 comments

Sometimes supported SSD drives do not appear in the vSphere Client or Web Client as an SSD, but instead as unknown or Non-SSD.

It is possible to use storage claim rules to alter this behaviour, to be able to use the ESXi host cache feature in ESXi 5.0 and above.

To start with, it is important to identify the device that is being reported incorrectly.

SelectDatastore

As you can see from the vSphere Client above, the datastore created as SharedSSD is reported as Non-SSD.

We need to identify the device that this datastore has been created on, one possible way would be to go into the properties of the datastore, and then enter the manage paths screen as shown below.

IdentifyDevice

Notice that the SATP (Storage Array Type Plugin) used for this device is VMW_SATP_DEFUALT_AA, we will need this with the device id.

We can then right click on the path and copy the name to the clipboard. In this case that would contain all the detail after Name: in the lower window. The only detail required is in this case the iSCSI t10 number.

(Although in this example we have already created a datastore on the device, it would be possible to configure a device that does not currently have a datastore as SSD except we would need to identify the device via the storage adapter.)

Once we have the device id, and SATP we can than use the esxcli command line tool (found in the ESXi shell, and vCli and vMa) to configure a claim rule.

The first setup is to create the claim rule with the required optional parameter to enable SSD.

CreateClaimRule

The next step is to ensure that the claim rule has been added.

CheckClaimRuleApplied

Notice that the claim rule previously entered is displayed as a result of the command.

Now we need to reclaim all claim rules to ensure that SSD is now enabled for this device.

ReclaimRules

Notice that in this case it was unable to unclaim the path. This can happen sometimes, and is easily fixed with a reboot of the host.

Alternatively, unclaim the device:

esxcli storage core claiming unclaim -t device -d t10.945445000000000023030000000000000000000000000000

Then load, and run the claim rule:

esxcli storage core claimrule load
esxcli storage core claimrule run

If you do not get the unable to reclaim message detailed above, you can now confirm hat the rule has been applied and that the device is now seen as SSD.

ConfirmSSDstatus

As you can see in the above, the value for Is SSD: is true.

You should now see the datastore listed as SSD in the client.

NowSSDisShown

It is also possible to use this method to allow the use of SSD for host caching when using a nested setup for testing.

vSphere Storage Appliance – Offline Demo

November 28, 2012 Leave a comment

When revising for the VCP510-DV exam, it is recommended to look at the vSphere Storage Appliance (VSA) as this is a new technology in vSphere 5.x and is included in the subjects covered in the exam as stated in the exam blueprint.

To help individuals get a better understanding of this feature, VMware have resources dedicated on VSA, which can be found here.

There is also an offline demo (based on Flash) which can be downloaded from here.

The demo expires on 30th November 2013.

Enjoy!

Reclaim Space: Great new tool from VMware Labs (Fling)

VMware Labs have released a great new tool for reclaiming space from a thin provisioned disk/LUN.

The disk must be a local physical disk or LUN, and must be used as a RDM within the vm.

Written by Faraz Shaikh and Prasanna Aithal, Guest Reclaim reclaims dead space from NTFS volumes hosted on a thin provisioned SCSI disk.

  • Reclaim space from Simple FAT/NTFS volumes
  • Works on WindowsXP to Windows7
  • Can reclaim space from flat partitions and flat disks
  • Can work in virtual as well as physical machines

You can check it out at http://labs.vmware.com/flings/guest-reclaim.

Categories: Flings, Storage, vSphere

Nested Home Lab – Setting up Shared Storage on SuSE (SLES11)

June 14, 2012 Leave a comment

Over the years teaching vSphere, several peers, colleagues and students have asked me how I setup shared storage in my nested test environment.  Being a Novell instructor teaching SuSE Linux. for me this was the obvious choice.  However, most of my colleagues and students are not familiar with Linux, so I have decided to put together a procedure detailing the steps necessary to configure your own shared storage.

You will need:
VMware Workstation 8 / Player 4

SuSE Linux Enterprise Server 11

Due to the length of the instructions (plus loads of screen grabs), I decided to make a PDF available , Enjoy!

NestedHomeLab-SharedStorage

Categories: Nested Lab, Storage, vSphere