7.2

Procedure
u
Recongure the load balancers for the vRealize Automation appliance, the IaaS Web Server that hosts
the Model Manager, and the Manager Service to restore the original health check seings and enable
replica nodes to accept incoming trac.
Validate the vRealize Automation Migrated Environment
You can verify that all data is migrated successfully to the target VMware vRealize ™ Automation 7.2
environment.
Prerequisites
Successful migration from your vRealize Automation 6.2.x environment to a vRealize Automation to 7.2
environment.
Procedure
1 In your vRealize Automation 7.2 environment, log in to the vRealize Automation console as
administrator using your vRealize Automation 6.2.x credentials.
2 Select Infrastructure > Managed Machines and verify that all the managed virtual machines are
present.
3 Click Compute Resources, and for each endpoint, select the endpoint and click Data Collection,
Request now, and Refresh to verify that the endpoints are working.
4 Click Design, and on the Blueprints page, select and verify the elements of each blueprint.
5 Click XaaS and verify the contents of Custom Resources, Resource Mappings, XaaS Blueprints, and
Resource Actions.
6 Select Administration > Catalog Management and verify the contents of Services, Catalog Items,
Actions, Entitlements.
7 Select Items > Deployments and verify the details for the provisioned virtual machines.
8 On the Deployments page, select a provisioned, powered o, virtual machine and select Actions >
Power On, click Submit, and click OK. Verify that the machine powers on correctly.
9 Click Catalog, and request a new catalog item.
10 On the General tab, enter the request information.
11 Click the Machine icon, accept all the default seings, click Submit, and click OK. Verify that the
request completes successfully.
Restore Embedded vRealize Orchestrator Endpoint
If you add an embedded vRealize Orchestrator endpoint to a vRealize Automation 6.x deployment and
upgrade to the latest version of vRealize Automation, you must make changes to the vRealize Orchestrator
endpoint URL to restore the connection.
In vRealize Automation 6.x, the URL for the embedded vRealize Orchestrator is hps://hostname:8281/vco. In
vRealize Automation 7.0 and later, the URL for an embedded vRealize Orchestrator changes to
hps://hostname/vco. Because the 6.x URL does not change automatically when you upgrade to the latest
version, the system cannot nd vRealize Orchestrator. Perform the following steps to x this problem.
Prerequisites
n
Log in to the vRealize Automation console as an IaaS administrator.
Migrating vRealize Automation 6.2 to 7.2
22 VMware, Inc.