VM folder names do not match the VM names after failover to an On-Premises Site in vCloud Availability
search cancel

VM folder names do not match the VM names after failover to an On-Premises Site in vCloud Availability

book

Article ID: 314985

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

Symptoms:
After performing a failover from a Cloud Site to an On-Premises Site in vCloud Availability, you see the following naming scheme on the destination datastore:
  • The VM's name is the same as the source VM's vCenter name including the vCloud Director identifier.
  • The VM's folder name is the same as the Replication Manager replication ID, _H4-UUID.


Environment

VMware vCloud Availability 3.0.x

Cause

When a replication is configured, the datastore folder in the destination On-Premises site is created with a name that matches the Replication Manager replication ID. Then, when the replica disks are promoted to a VM on failover, the same datastore folder is used and its name remains unchanged.

Resolution

This is an expected behavior and does not affect the functionality.

Workaround:
If you want to change the name of the VM's datastore folder, this can be done by performing a storage vMotion of the VM. When you perform the storage vMotion, a new VM folder will be created on the new datastore with the same name as the VM instead of the Replication Manager replication ID.