Ensure a successful migration to a minimal environment by reviewing these prerequisites.
Before you begin
Verify that you have a new target environment of vRealize Automation.
Install relevant proxy agents on the target environment according to these requirements.
Target proxy agent name must match the source proxy agent name for vSphere, Hyper-V, Citrix XenServer, and Test proxy agents.Note:
Finish these steps to obtain an agent name.
Go to the agent installation directory on the IaaS node.
Under the serviceConfiguration tag, look for the value of the agentName attribute.
Target proxy agent endpoint name must match the source proxy agent endpoint name for vSphere, Hyper-V, Citrix XenServer, and Test proxy agents.
Do not create an endpoint for vSphere, Hyper-V, Citrix XenServer, or Test proxy agents on the target environment.
Review the version numbers of vRealize Automation components.
In your target vRealize Automation 7.3 environment, start a browser. Go to the vRealize Automation appliance management console at https://vra-va-hostname.domain.name:5480.
Log in with the user name root and the password you entered when you deployed the appliance.
Expand the Host / Node Name records by clicking the triangle.
Verify that the version numbers of the vRealize Automation IaaS components match.
Verify that the target Microsoft SQL Server version for the vRealize Automation target IaaS database is 2012, 2014, or 2016.
Verify that port 22 is open between the source and target vRealize Automation environments. Port 22 is required to establish Secure Shell (SSH) connections between source and target virtual appliances.
Verify that the IaaS server node in the target environment has at least Java SE Runtime Environment (JRE) 8, update 111 (64 bit) installed. After you install the JRE, make sure the JAVA_HOME system variable points to the Java version you installed on each IaaS node. Revise the path if necessary.
Verify that each IaaS node has PowerShell 3.0 or later installed.
Verify that the source and target vRealize Automation environments are running.
Verify that no user and provisioning activities are happening on the source vRealize Automation environment.
Security software must not interact with the operating system and its components running on IaaS nodes in the target vRealize Automation environment during migration. If you have any antivirus or security software installed, verify that the software is correctly configured or disabled for migration.