Migrating vVol metadata volumes from Version 1 to Version 2 format

IBM Storage Virtualize version 8.6.0.0 and later support a version 2 metadata volume when configuring VMware Virtual Volumes (vVols). A metadata volume created on earlier versions uses a version 1 metadata format. It is recommended that users migrate the metadata volume from version 1 to version 2 to take advantage of future feature updates for vVols.

To migrate a metadata volume from version 1 to version 2 format by using command-line interface, complete the following steps:

Note: The version 2 metadata format is only supported for embedded VASA Provider (EVP). For IBM Spectrum® Connect users, only the version 1 metadata format is available.

An invocation example to migrate a version 1 metadata volume to a new version 2 volume in storage pool 0:
```
mkmetadatavdisk -mdiskgrp 0 -migrate
```
The resulting output:
```
Virtual Disk, id [2], successfully created
```
Note: If the migration fails, contact IBM® Support Center to resolve the issue. For more information about mkmetadatavdisk command, see mkmetadatavdisk.
Use lsmetadatavdisk command to verify the version of a metadata volume.
```
lsmetadatavdisk
```
The resulting output:
```
vdisk_id vdisk_name      status version
0        vdisk0          online 1
5        metadatavolume0 online 2
```
Note: The metadata migration is performed asynchronously and may take several minutes to complete. Depending on the size of the configuration, this process could take up to an hour. The VASA provider service is unavailable while the migration is in progress. Wait until the migration is complete and the Storage Provider status is online in VMware vCenter before performing any configuration changes for the VASA Provider or vVols in vCenter.