When you add an existing service,
PowerFlex Manager checks to see whether there are any vSphere Cluster Services (vCLS) VMs on local storage. If it finds any, it puts the service in lifecycle mode and lets you migrate the VMs to shared storage.
About this task
After you add an existing service,
PowerFlex Manager displays a warning banner to notify you that the service is in lifecycle mode. You can then migrate the vCLS VMs to shared storage by launching the
Migrate vCLS VMs wizard.
You can launch the wizard for migrating vCLS VMs to shared storage from the
Service Actions section of the
Service Details page. You can also launch the wizard from the warning banner at the top of the
Service Details page or from the warning banner at the top of the
Node Compliance Report. The operations available are the same regardless of where you launch the wizard.
When you migrate vCLS VMs,
PowerFlex Manager automatically creates two service volumes and maps these volumes to datastores. The service volume names follow the convention of
powerflex-service-vol-<NUMBER> where
<NUMBER> is the next available digit that has not been taken. The datastore names follow the convention of
powerflex-<CLUSTER_NAME>-ds-<NUMBER> where
<CLUSTER_NAME> is the name of the vCenter cluster and the
<NUMBER> is the next available digit. Examples of generated service volumes are: powerflex-service-vol-1 and powerflex-service-vol-2. Examples of generated service datastores are: powerflex-hyperconverged-DKIM-ds-1 and powerflex-hyperconverged-DKIM-ds-2.
CAUTION:Do not rename the automatically generated service volumes and datastores. If for some reason, the names have been changed,
PowerFlex Manager creates new service volumes and datastores, as needed, that use the correct naming conventions. Do not migrate vCLS VMs manually to a nonheartbeat datastore. This action activates lifecycle mode and requires a migration. In this case, volumes and datastores may be created with new names and digits (for example, powerflex-service-vol-3, powerflex-service-vol-4, and so forth).
Steps
To access the wizard from the
Service Actions section of the
Service Details page:
On the menu bar, click
Services.
Select a service that is in lifecycle mode because it includes vCLS VMs that are on local storage.
In the right pane, click
View Details.
The
Service Details page is displayed.
In the right pane, click
Migrate vCLS VMs under
Service Actions.
The
Migrate vCLS VMs wizard is displayed.
For a compute-only service, select a protection domain from the
Protection Domain field.
The
Protection Domain field is not displayed for a hyperconverged service, since it is already defined by the service.
For a hyperconverged or compute-only service, select a storage pool in the
Storage Pool drop-down.
The list of storage pools available for selection is filtered to list the storage pools in the selected protection domain.
Review the
Destination Datastores. The destination datastores are the two heartbeat datastores that
PowerFlex Manager creates automatically when you migrate the vCLS VMs to shared storage.
PowerFlex Manager also creates two service volumes and maps these volumes to the destination datastores.
Only two datastores and service volumes are created. If you already have existing datastores,
PowerFlex Manager adds the new datastores to the list. If you already have datastores with the same names in the same cluster,
PowerFlex Manager does not create new ones, but simply uses the ones that exist already.
Type
MIGRATE VCLS VIRTUAL MACHINES to confirm.
Click
Confirm.
Results
After the migration,
PowerFlex Manager takes the service out of lifecycle mode, and the full set of service actions are available.
Data is not available for the Topic
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please provide ratings (1-5 stars).
Please select whether the article was helpful or not.
Comments cannot contain these special characters: <>()\