Renaming the VMware vSphere Cluster used in a VMware vRealize Automation environment
search cancel

Renaming the VMware vSphere Cluster used in a VMware vRealize Automation environment

book

Article ID: 344298

calendar_today

Updated On:

Products

VMware Aria Suite

Issue/Introduction

This article provides best practice information for renaming a VMware vSphere cluster used by VMware vRealize Automation Reservations and the cluster resources.

Environment

VMware vRealize Automation 7.x
VMware vCloud Automation Center for Server 6.1.x
VMware vCloud Automation Center for Server 6.0.x
VMware vRealize Automation 6.2.x

Resolution

Note: Before making any changes make a backup of all VMware vRealize Automation systems and databases machines. Also ensure to take a backup of the database. This can be used to rollback in the event of encountering an issue.

To rename the VMware vSphere Cluster used in the VMware vRealize Automation environment:
  1. Rename the vSphere cluster.

    Rename the cluster in vSphere vCenter Server.

  2. Add the cluster to the Fabric Group.

    To add the cluster to the Fabric Group:

    1. Log in to the vRealize Automation tenant with admin privileges.
    2. Go to Infrastructure > Groups > Fabric Groups.
    3. Hover over the Fabric Group name and click Edit.

      Note: It may be necessary to wait a minute or two for the new cluster name to appear in the list of Compute resources.

    4. Select new cluster name and click OK.
    5. To check the status of data collection, navigate to Infrastructure > Compute Resources > Compute Resources. Hover over the renamed cluster and select Data Collection from the pop up menu.
    6. Verify that the Inventory, State, and Performance parameters have a Last completed as: In progress, In Queue or have a last time collected timestamp.
    7. Verify the status of Inventory Status, State Status and Performance Status change to Succeeded before proceeding.

  3. Create a new reservation.

    To create a new reservation:

    1. In vRealize Automation, go to Infrastructure > Reservations > Reservations.
    2. Edit the existing reservation and note the required information of the Resource, Network and Alerts Tabs. This information is used to create a new reservation.
    3. Click New Reservation > Virtual > vSphere and complete the Reservation Information.
    4. Click the Resources, Network and Alerts tabs and complete them so that they are aligned with the information captured in step b.
    5. Click OK.

  4. Migrate virtual machines to new reservation.

    To migrate virtual machines to new reservation:

    1. Move the virtual machines from the old Reservation to the new Reservation.
    2. Go to Infrastructure > Machines > Managed Machines. Filter the view to display all machines on the old reservation. Hover over each of these machines, and select Change Reservation from the menu.

  5. Delete the old reservation.

    To delete the old reservation:

    1. Go to Infrastructure > Reservations > Reservations.

      Note: Before deleting ensure that no virtual machines are in the reservation.

    2. Hover over the reservation and click Delete.
    3. Delete inactive hosts for the old cluster from IaaS database.

      Note: This step is required if running vRealize Automation 6.0.x and not required for vRealize Automation 6.1 and above.

      You can use a script to remove inactive hosts. For more information on removing inactive hosts using scripts, see Deleting an endpoint in vRealize Automation fails with the error: This endpoint is being used by # compute resources and # storage paths and cannot be deleted (2105809).

    4. Delete all DataCollectionStatus records for the old cluster from the IaaS database, by running this SQL query:

      DELETE from DataCollectionStatus

    5. Run a data collection on the new vCenter cluster in vRealize Automation.


Additional Information

Error 'This endpoint is being used by # compute resources and # storage paths and cannot be deleted' when you delete an endpoint in vRA
VMware vRealize Automation 環境で使用される VMware vSphere クラスタ名の変更