Skip to main content

Upgrading Datastores From VMFS3 to VMFS5

As with many vSphere tasks, there are multiple ways in which you can upgrade datastores from VMFS3 to VMFS5. Before looking at how to upgrade a datastore, there are a few things worth mentioning about VMFS 5 and upgraded datastores.
  • VMFS 5 has a block size of 1MB. This block size is the only one available an supports files of up to 2 TB.
  • VMFS 5 sub blocks are 8KB. Significantly smaller than with VMFS 3 (64 KB).
  • However, if you are upgrading, the block size you had in place on your VMFS 3 datastore will remain when it is upgraded to VMFS 5. Often, because of this, it is determined that it is preferable to replace VMFS 3 datastores with VMFS 5, utilising svMotion to move virtual machines around whilst datastores are destroyed and recreated.
  • The disk type of an upgraded VMFS 3 datastore will remain as MBR until it is grown larger than 2TB. At this point it will be converted to a GPT disk automatically.
  • VMFS datastore upgrades can be carried out on datastores with powered on virtual machines without issue.

Upgrading a Datastore using the vSphere Client

To upgrade a datastore to VMFS 5 using the vSphere client, log into vCenter, select a host that has access to the datastore you want to upgrade then, on the Configuration tab, click Storage.
With your chosen datastore highlighted, click ‘Upgrade to VMFS 5′:
vmfs3_upgrade
You will receive a warning stating that all hosts that need to access the datastore must be version 5.0 or above otherwise they will lose access to the datastore. Click OK to start the upgrade – it will complete fairly quickly. Once the task is complete you can confirm that your datastore is VMFS5 by checking the type column:
vmfs5

Upgrading a VMFS Datastore using esxcli

You can also perform the upgrade using esxcli. To do so, run the following command:
~ # esxcli storage vmfs upgrade -l Datastore

Upgrading VMFS Datastores using VMKFSTOOLS

We can upgrade a VMFS datastore using vmkfstools by running the following command. We’ll be upgrading the datastore detail in the previous example. It is currently VMFS-3.54. To upgrade, run the following:
~ # vmkfstools --upgradevmfs /vmfs/volumes/NewVOL/


VMware ESX Question:
Please ensure that the VMFS-3 volume /vmfs/volumes/4ff9c8a0-27ae1bdb-4a70-000c29e8410a is not in active use by any local or remote ESX 3.x/4.x server.

We recommend the following:
1. Back up data on your volume as a safety measure.
2. Take precautions to ensure no ESX 3.x/4.x servers are accessing this volume.

Continue converting VMFS-3 to VMFS-5?
0) _Yes
1) _No

Select a number from 0-1: 0

Checking if remote hosts are using this device as a valid file system. This may take a few seconds...
Upgrading file system /vmfs/volumes/NewVOL/...
done.
Check that it has been upgrade successfully by using vmkfstools to query the VMFS volume:
~ # vmkfstools --queryfs -h /vmfs/volumes/NewVOL/
VMFS-5.54 file system spanning 1 partitions.
File system label (if any): NewVOL
Mode: public
Capacity 4.8 GB, 4.2 GB available, file block size 1 MB
UUID: 4ff9c8a0-27ae1bdb-4a70-000c29e8410a
Partitions spanned (on "lvm"):
        mpx.vmhba1:C0:T2:L0:1
Is Native Snapshot Capable: NO
We can see that the VMFS version is now VMFS-5.54.

Comments

Popular posts from this blog

Quick Guide to VCF Automation for VCD Administrators

  Quick Guide to VCF Automation for VCD Administrators VMware Cloud Foundation 9 (VCF 9) has been  released  and with it comes brand new Cloud Management Platform –  VCF Automation (VCFA)  which supercedes both Aria Automation and VMware Cloud Director (VCD). This blog post is intended for those people that know VCD quite well and want to understand how is VCFA similar or different to help them quickly orient in the new direction. It should be emphasized that VCFA is a new solution and not just rebranding of an old one. However it reuses a lot of components from its predecessors. The provider part of VCFA called Tenenat Manager is based on VCD code and the UI and APIs will be familiar to VCD admins, while the tenant part inherist a lot from Aria Automation and especially for VCD end-users will look brand new. Deployment and Architecture VCFA is generaly deployed from VCF Operations Fleet Management (former Aria Suite LCM embeded in VCF Ops. Fleet Management...
  Issue with Aria Automation Custom form Multi Value Picker and Data Grid https://knowledge.broadcom.com/external/article?articleNumber=345960 Products VMware Aria Suite Issue/Introduction Symptoms: Getting  error " Expected Type String but was Object ", w hen trying to use Complex Types in MultiValue Picker on the Aria for Automation Custom Form. Environment VMware vRealize Automation 8.x Cause This issue has been identified where the problem appears when a single column Multi Value Picker or Data Grid is used. Resolution This is a known issue. There is a workaround.  Workaround: As a workaround, try adding one empty column in the Multivalue picker without filling the options. So we can add one more column without filling the value which will be hidden(there is a button in the designer page that will hide the column). This way the end user will receive the same view.  
  "Cloud zone insights not available yet, please check after some time" message on Aria Automation https://knowledge.broadcom.com/external/article?articleNumber=314894 Products VMware Aria Suite Issue/Introduction Symptoms: The certificate for Aria operations has been replaced since it was initially added to Aria Automation as an integration. When accessing the Insights pane under  Cloud Assembly  ->  Infrastructure  ->  Cloud Zone  ->  Insights  the following message is displayed:   "Cloud zone insights not available yet, please check after some time." The  /var/log/services-logs/prelude/hcmp-service-app/file-logs/hcmp-service-app.log  file contains ssl errors similar to:   2022-08-25T20:06:43.989Z ERROR hcmp-service [host='hcmp-service-app-xxxxxxx-xxxx' thread='Thread-56' user='' org='<org_id>' trace='<trace_id>' parent='<parent_id>' span='<span_id>'] c.v.a.h.a.common.AlertEnu...