Ensure a successful migration to a minimal environment by reviewing these prerequisites.
Minimal deployments include one vRealize Automation appliance and one Windows server that hosts the IaaS components. In a minimal deployment, the vRealize Automation SQL Server database can be on the same IaaS Windows server with the IaaS components, or on a separate Windows server.
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.
On the IaaS host, log in to Windows as a local user with administrator privileges.
Use Windows Explorer to go to the agent installation directory.
Under the serviceConfiguration tag, look for the value of the agentName attribute.
Review Knowledge Base article 51531.
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 on the target vRealize Automation appliance.
Log in to the target vRealize Automation Appliance Management as root using the password you entered when you deployed the target vRealize Automation 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 endpoint vCenter has sufficient resources to complete migration.
Verify that the target vRealize Automation environment system time is synchronized between Cafe and the IaaS components.
Verify that the IaaS server node in the target environment has at least Java SE Runtime Environment (JRE) 8, 64 bit, update 161 or later installed. After you install the JRE, make sure the JAVA_HOME environment 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.
Verify that any antivirus or security software running on IaaS nodes in the target vRealize Automation environment that might interact with the operating system and its components is correctly configured or disabled.
Verify that the IaaS Web Service and Model Manager do not need to be restarted because of pending Windows installation updates. Pending updates might prevent the migration to begin or end the World Wide Web Publishing Service.