You can migrate your current vRealize Automation environment data to a new installation of vRealize Automation 7.4 configured as a high-availability environment.
All tenants in the source system must be recreated in the target and go through the Migrate Identity Stores procedure. For more information, see Migrate Identity Stores to VMware Identity Manager.
Log in to the target vRealize Automation Appliance Management as root using the password you entered when you deployed the target vRealize Automation appliance.
- Select .
- Enter the information for the source vRealize Automation appliance.
The host name for the source vRealize Automation appliance.
The root password that you entered when you deployed the source vRealize Automation appliance.
- Enter the information for the migration package location on the source vRealize Automation appliance.
Migration package location
Path to an existing directory on the source vRealize Automation 6.2.x or 7.x appliance where the migration package is created.
- Enter the information for the target vRealize Automation appliance.
The root password that you entered when you deployed the target vRealize Automation appliance.
Password for the firstname.lastname@example.org user that you entered when you deployed the target vRealize Automation environment.
- Enter the information for the target IaaS database server.
The location of the Microsoft SQL Server instance where the restored vRealize Automation IaaS Microsoft SQL database resides. If a named instance and a non-default port are used, enter in SERVER,PORT\INSTANCE-NAME format. If you configure the target Microsoft SQL Server to use the AlwaysOn Availability Group (AAG) feature, the target SQL Server should be entered as the AAG listener name, without a port or instance name.
Cloned database name
Name of the source vRealize Automation 6.2.x or 7.x IaaS Microsoft SQL database that you backed up on the source and restored on the target environment.
If you use the Windows authentication mode, the IaaS service user must have the SQL Server db_owner role. The same permissions apply when using SQL Server authentication mode.
SQL Server opens the Login name and Password text boxes.
Login name of the SQL Server user with the db_owner role for the cloned IaaS Microsoft SQL database.
Password for the SQL Server user with the db_owner role for the cloned IaaS Microsoft SQL database.
Original encryption key
Original encryption key that you retrieve from the source environment. See Obtain the Encryption Key from the Source vRealize Automation Environment.
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 environment.
- Click Validate.
The page displays the validation progress.
If all the items validate successfully, go to step 8.
If an item fails to validate, inspect the error message and the validation log file on the IaaS nodes. For log file locations, see Migration Log Locations. Click Edit Settings and edit the problem item. Go to step 7.
- Click Migrate.
The page displays the migration progress.
If migration is successful, the page displays all migration tasks as completed.
If migration is unsuccessful, inspect the migration log files on the virtual appliance and the IaaS nodes. For log file locations, see Migration Log Locations.
Finish these steps before you restart migration.
Revert your target vRealize Automation environment to the state you captured when you took a snapshot before migration.
Restore your target IaaS Microsoft SQL database using the backup of the source IaaS database.