SynopsisThis cmdlet updates a VMFS5 datastore to VMFS6.
SyntaxUpdate-VmfsDatastore [-Server] <VIServer> [-Datastore] <Datastore> [-TemporaryDatastore] <Datastore> [[-TargetVmfsVersion] <Int32>] [-Rollback] [-Resume] [-Force] [-WhatIf] [-Confirm] [<CommonParameters>]
Related CommandsOnline version
Detailed DescriptionThis cmdlet updates a VMFS5 datastore to a supported specified target VMFS version. The supported new VMFS version in vSphere 6.5 is version 6.
Things to consider before running this cmdlet:
- This operation deletes the existing VMFS5 datastore to create a VMFS6 datastore. You should back up any files from the VMFS5 datastore to prevent any data loss.
- As the existing VMFS5 datastore is formatted to VMFS6 datastore, the UUID of the datastore will change.
- If the UUID of the datastore is different from the previous UUID of the VMFS5 datastore, all applications that depend on the UUID of VMFS5 datastores should be updated with the new UUID.
- Example: Any backup solution which uses datastore UUID to back up datastore contents must be updated with the new UUID before running this cmdlet.
- HBR (Host Based Replciation)/VR (vSphere Replication) and SRM (Site Recovery Manager) enabled vSphere environments are not supported with this cmdlet. You should not run the VMFS update with HBR or SRM configured as the cmdlet is not aware of any files or configurations related to HBR or SRM.
- If VADP is enabled on a VM, migration is disabled on such a VM. The cmdlet will fail to move such VM.
- After migrating all active or registered VMs from the source datastore, if swap files or delta.vmdk (snapshots of vitual disk) files are found, the datastore will not be upgraded.
- VMFS extend: In case the VMFS datastore (which you try to upgrade from VMFS version 5 to 6) is extended across multiple devices (or extents), this cmdlet extends the VMFS on the primary datastore over the tail devices. All data on the tail devices (extents), including the partitions, will be deleted. Hence, the tail devices with multiple active partitions are not supported.
- This cmdlet supports DRS on a cluster, SDRS, SIOC, SPBM (VMFS tagging), CBRC (Content Based Read Cache), and vFRC (vSphere Flash Read Cache) only.
- This cmdlet does not support VADP (VMware vSphere Storage APIs - Data Protection), SRM (Site Recovery Manager), HBR (Host Based Replication)/VR (vSphere Replication), SMP-FT (Symmetric Multi-Processing Fault Tolerance) and FT (Fault Tolerance), First Class Disks (FCD), Windows Server Failover Clustering (WSFC), and Oracle Real Application Clusters (RAC).
This cmdlet performs the following tasks:
1. Backs up the VMFS5 (source) datastore, if the datastore contains any VMs or any other directories or files, to another VMFS5 datastore (temporary).
2. Deletes the source datastore, re-creates it with VMFS6 file system, and moves back all the files from temporary to source.
3. Rollback option: If there are infrastructure issues causing the ongoing task on step 1 to abort, use the Rollback option in the cmdlet to roll back all VMs and copied files from temporary to source.
4. If the Rollback option is not possible (due to being past step 1), you can resume the task which is initiated in step 1 by rectifying any infrastructure issues.
5. There is no post-update rollback option as the goal is to move all files from the VMFS5 datastore (temporary) to the newly formatted VMFS6 (source) datastore.
6. HA (High Availability) is supported in the 6.5.4 release.
7. VAAI (VMware vSphere Storage APIs - Array Integration) enabled VMFS5 datastores are supported in the 6.5.4 release.
|Name||Type||Description||Required?||Pipeline Input||Default Value|
|Server||VIServer||Specifies the vCenter Server systems on which you want to run the cmdlet. If no value is given to this parameter, the command runs on the default servers. For more information about default servers, see the description of Connect-VIServer.||true||false|
|Datastore||Datastore||Specifies datastore to update to VMFS6. It must be of version VMFS5.||true||true (ByValue)|
|TemporaryDatastore||Datastore||Specifies the temporary datastore to help the upgrade to VMFS6. It should be of VMFS5 version. This datastore should be empty and its size should be more than that of the datastore you want to upgrade. The temporary datastore must have enough backing to support the migration.||true||false|
|TargetVmfsVersion||Int32||Specifies the target version to which you want to update the datastore. By default, the target VMFS version is 6.||false||false|
|Confirm||SwitchParameter||If the value is $true, indicates that the cmdlet asks for confirmation before running. If the value is $false, the cmdlet runs without asking for user confirmation.||false||false|
|Force||SwitchParameter||Suppresses the confirmation prompt if vSphere Replication/HBR or SRM is enabled on the specified datastore.||false||false|
|Resume||SwitchParameter||Indicates that you want to resume the previous upgrade attempt.||false||false|
|Rollback||SwitchParameter||Specifies whether to roll back Storage vMotion after a failure happens. This is possible only before the original datastore has been deleted. After the original datastore is removed, only resume is possible.||false||false|
|WhatIf||SwitchParameter||Indicates that the cmdlet is run only to display the changes that would be made and actually no objects are modified.||false||false|
-------------- Example 1 --------------
Update-VmfsDatastore -Datastore $source -TemporaryDatastore $temp
Starts an update of the $source VMFS5 datastore to VMFS version 6 by using $temp as a temporary datastore.
-------------- Example 2 --------------
Update-VmfsDatastore -Datastore $source -TemporaryDatastore $temp -Resume
Resumes a previous failed attempt of updating the $source datastore to the specified VMFS version.
Copyright © VMware, Inc. All rights reserved.