Review these prerequisites to ensure a successful migration.
Verify that you have a new target installation of VMware vRealize ™ Automation 7.2.
Verify that endpoint names configured for agents, such as vSphere agents, running on the target system match the endpoint names used by the source installation.
Verify that installed agent names are the same on both source and target systems for vSphere and Hyper-V proxy agents, Citrix Xen Server, and Test agents.
For a clustered environment, configure load balancers for the vRealize Automation appliance, the IaaS Web Server that hosts the Model Manager, and the Manager Service to meet the following requirements:
The load balancer must point to the appropriate master (primary, active) node, and exclude any traffic routes to replica nodes.
The load balancer must not have any health check URLs defined in its configuration.
Verify that the target Microsoft SQL Server version for the vRealize Automation 7.2 IaaS database is either 2012 or 2014.
Verify that Secure Shell (SSH) service is enabled on both the source and target vRealize Automation virtual appliances.
Verify that port 22 is open between the source and target vRealize Automation environments.
Verify that each IaaS server node in the target environment has at least Java SE Runtime Environment (JRE) 8, Update 91 (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, and adjust the path if necessary.
Verify that each IaaS node has at least PowerShell 3.0 installed.Note:
PowerShell 3.0 is integrated with Windows Server 2012.
Verify that the source and target vRealize Automation environments are running.
Verify that the default vRealize Orchestrator admin group, vsphere.local/vcoadmin, is present in the vRealize Orchestrator control center prior to migration. vRealize Automation migration from 6.x to 7.2 fails if the 7.2 target environment has a different vRealize Orchestrator admin group set as the default. For more information, see KB 2148669.
Create a full backup of the source vRealize Automation 6.2.x IaaS Microsoft SQL database and use the backup to restore the SQL database in the target environment. For information, find articles on the Microsoft Developer Network about creating a full SQL Server database backup and restoring an SQL Server database to a new location.
Take a snapshot of each vRealize Automation target 7.2 virtual machine.
In this table, enter the values from your environment that you need for migration.
Table 1. Source vRealize Automation appliance
Log in to the vRealize Automation appliance management console on your master or primary virtual appliance. Find host name on the System tab.
The root password that you entered when you deployed your master or primary vRealize Automation appliance.
Table 2. Target vRealize Automation appliance
The root password that you entered when you deployed your target vRealize Automation appliance.
Default tenant configured in the target vRealize Automation deployment. Usually, vsphere.local.
Default tenant administrator user name that you entered during the installation of your targetvRealize Automation environment. Usually administrator.
Password for the default tenant administrator user that you entered during the installation of your target vRealize Automation environment.
Table 3. Target IaaS Database
Location of Microsoft SQL Server instance where the cloned database resides. If named instance and non-default port is used, enter in SERVER,PORT\INSTANCE-NAME format.
Cloned database name
Name of the source vRealize Automation 6.2.x IaaS Microsoft SQL database that you backed up on the source and restored on the target. environment.
Login name of the SQL Server user configured to access and manage the cloned IaaS database.
Password for the SQL Server user configured to access and manage the cloned IaaS database.
Original encryption key
Source IaaS Microsoft SQL database encryption key that you retrieve from the source environment at the beginning of the migration procedure.
A series of words used to generate a new encryption key. You use this passphrase each time you install a new IaaS component in the target vRealize Automation 7.2 deployment.