Upgrading my home vSphere 4 cluster to a vSphere5 cluster (Part 4 upgrading VMFS)

In part 3 of the series Upgrading my home vSphere 4 cluster to a vSphere5 cluster we upgraded my ESXi4 hosts to ESXi5 with the help of Update Manger. Now that we’re running ESXi 5 where able to upgrade the VMFS3 datastores to VMFS5.

First a little overview. My server who is named ESX2 has 1 VMFS3.46 datastore named vmfslun1 with a block size of 4 MB. On this datastore I have 1 test VM called WinXP Mike. During the upgrade this VM is powered on. The LUN is hosted on a QNAP NAS with iSCSI.

As you have probably heard as of vSphere5 the default and only block size you can select is 1MB. This is because of VMFS5 VMware isn’t using MBR anymore as the default partition table but GPT (GUID Partition Table). So when I upgrade my VMFS3 datastore to VMFS5 is MBR changed to GPT? No, as you probably know, the maximum size of a VMFS3 datastore is 2TB-512 Byte  (without extends), the maximum size of a  VMFS5 datastore is 64TB – 512 Bytes (without extends). This is a major improvement. So when does the MBR partition table change to GPT? Simple, when the VFMS5 datastore grows beyond 2 TB.
Be aware that upgrading your VMFS3 to VMFS5 is a one-way process, there is no turning back.The block size will not change, so if you have a VMFS3 datastore with a 4MB block size, after the upgrade you will have a VMFS5 datastore with a 8MB block size.

That said, you probably asking your self: “Does it matter that I have VMFS5 datastores with different block sizes?” This depends if you have a VAAI capable storage. This can influence the performance of your storage. Best is to have all the datastores the same block size. So a best practice is to create your VMFS datastores with a 1MB block size and move your VMs to them.

If recreating your VMFS datastores isn’t a option, you have to upgrade them.

  1. Select your ESXi host and click on the configuration tab.
  2. Select Storage and click on the LUN who holds a VMFS3 partition.
  3. In the Datastore Details section select Upgrade to VMFS5.
  4. vCenter will check is the datastore is ready to be upgrade. This means that all the host connected to the datastore have to be ESXi 5.
  5. The upgrade is perfomed by the ESXi host where you are connected to. Wait until the task is Completed in the resend tasks section.
  6. After a while your VMFS datastore is upgrade to VMFS5. This while my VM kept running. Nice!

More info on VMFS5? Look at the following blog post of Frank Denneman and Jason Boche.

About Michael
Michael Wilmsen is a VMware training/consultant (no specific order) with more than 15 years in the IT industry. Main focus is VMware vSphere, Horizon View and Site Recovery Manager with a deepdive to performance. Michael is VCDX 210, VCAP 4/5 certified, has been rewarded with the vExpert title from 2011, is a PernixPro, Nutanix Tech Champion and a Nutanix Platform Professional.

4 Comments to “Upgrading my home vSphere 4 cluster to a vSphere5 cluster (Part 4 upgrading VMFS)”

  1. By Willem, September 16, 2011 @ 21:13

    Hi Mike,

    Interesting series on the upgrade, thanks! A little remark on your example on the blocksize when upgrading to VMSF5… A 3MB blocksize does not exist with VMware… so a typo but it was a bit confusing. 🙂

    As moving to a newly created VMFS volume is recommended, there are no gotchas you’ve seen when moving large vmdk’s on a VMFS3 with a large block size to a newly created VMFS volume with the fixed 1MB blocksize? I’d imagine not, still curious if some extra steps are needed….

    Cheers,
    Willem

    • By Mike, October 10, 2011 @ 10:35

      Hi Willem,

      Sorry for the late reaction, somehow I don’t get notified when a comment is placed. Have to look into that.
      3MB is indeed a typo. I changed it. Thanks.

      About the migration, No I didn’t experienced any problems when upgrading to VMFS5. As far as I can see is that the filesystem layout hasn’t changed. When you to a upgrade it updates the MBR and when it exceeds 2TB it becomes a GPT partition.

  2. By Willem, September 16, 2011 @ 21:13

    Hi Mike,

    Interesting series on the upgrade, thanks! A little remark on your example on the blocksize when upgrading to VMSF5… A 3MB blocksize does not exist with VMware… so a typo but it was a bit confusing. 🙂

    As moving to a newly created VMFS volume is recommended, there are no gotchas you’ve seen when moving large vmdk’s on a VMFS3 with a large block size to a newly created VMFS volume with the fixed 1MB blocksize? I’d imagine not, still curious if some extra steps are needed….

    Cheers,
    Willem

    • By Mike, October 10, 2011 @ 10:35

      Hi Willem,

      Sorry for the late reaction, somehow I don’t get notified when a comment is placed. Have to look into that.
      3MB is indeed a typo. I changed it. Thanks.

      About the migration, No I didn’t experienced any problems when upgrading to VMFS5. As far as I can see is that the filesystem layout hasn’t changed. When you to a upgrade it updates the MBR and when it exceeds 2TB it becomes a GPT partition.

RSS feed for comments on this post. TrackBack URI

Leave a Reply

You must be logged in to post a comment.