Renaming a vSphere cluster without causing errors in VMware vRealize Automation for Server 5.1.x

Products

• VMware Aria Suite

Issue/Introduction

This article provides best practice information on renaming a vSphere cluster without breaking the link between vRealize Automation (formerly known as vCloud Automation Center) Reservations and the cluster resources.

Environment

VMware vCloud Automation Center for Server 5.1.x

Resolution

To rename your vSphere cluster:

1. Back up your vRealize Automation (formerly known as vCloud Automation Center) database.
   
   Note: This is important in case you need to roll back.
   
   
2. Stop all vRealize Automation services (i.e. - Manager, Agent, and DEMs).
3. Rename the cluster in vSphere.
4. Update the Host table in the vRealize Automation database and set the HostName to the new cluster name.
5. Update the Host table in the vRealize Automation database and set the HostUniqueID to the same value it has, but replace the old cluster name with the new one.
6. Start all vRealize Automation services and check the Log Viewer for errors.

Additional Information

Impact/Risks:
Make sure to backup your vRealize Automation (formerly known as vCloud Automation Center) database prior to changing the database and/ or cluster name. If you rename the cluster without stopping the services, data collection may run and pull in the new cluster name as a new resource and lose access to the correct cluster.