7.4
Table Of Contents
- Migrating vRealize Automation to 7.4
- Contents
- Migrating vRealize Automation
- vRealize Automation Environment User Interfaces
- Migration Prerequisites
- Pre-Migration Tasks
- Review Changes Introduced by Migration from vRealize Automation 6.2.x to 7.x
- Apply Software Agent Patch
- Change DoDeletes Setting on the vSphere Agent to False
- Check Templates in Your vRealize Automation 6.x Source Environment
- Prepare vRealize Automation Virtual Machines for Migration
- Gather Information Required for Migration
- Obtain the Encryption Key
- List Tenant and IaaS Administrators
- Add Each Tenant from the Source Environment
- Create an Administrator for Each Added Tenant
- Synchronize Users and Groups Before Migration to a Minimal Environment
- Synchronize Users and Groups Before Migration to a High-Availability Environment
- Run Data Collection in Source
- Manually Clone the Source Microsoft SQL Database
- Snapshot the Target Environment
- Migration Procedures
- Post-Migration Tasks
- Add Tenant and IaaS Administrators
- Run Test Connection and Verify Migrated Endpoints
- Run Data Collection on Target
- Reconfigure Load Balancers After Migration
- Migrate an External Orchestrator Server
- Reconfigure the vRealize Automation Endpoint
- Reconfigure the vRealize Automation Infrastructure Endpoint
- Install vRealize Orchestrator Customization
- Reconfigure Embedded vRealize Orchestrator Endpoint
- Reconfigure the Azure Endpoint
- Migrate Automation Application Services
- Delete Original Target vRealize Automation IaaS Microsoft SQL Database
- Update Data Center Location Menu Contents After Migration
- Upgrading Software Agents to TLS 1.2
- Validate the Target vRealize Automation 7.4 Environment
- Troubleshooting Migration
- PostgreSQL Version Causes Error
- Some Virtual Machines Do Not Have a Deployment Created during Migration
- Migration Log Locations
- Catalog Items Appear in the Service Catalog After Migration But Are Not Available to Request
- Data Collection Radio buttons Disabled in vRealize Automation
- Troubleshooting the Software Agent Upgrade
Table 2‑5. vRealize Orchestrator Control Center
Purpose Access Required Credentials
You use the vRealize Orchestrator Control
Center to edit the configuration of the
default vRealize Orchestrator instance
that is embedded in vRealize Automation.
1 Start a browser and open the
vRealize Automation appliance splash page
using the fully qualified domain name of the
virtual appliance:
https://vra-va-hostname.domain.name.
2 Click vRealize Automation Appliance
Management.
You can also use this URL to open
vRealize Automation Appliance Management:
https://vra-va-hostname.domain.name:5480.
3 Log in.
4 Click vRA Settings > Orchestrator.
5 Select Orchestrator user interface.
6 Click Start.
7 Click the Orchestrator user interface URL.
8 Log in.
User Name
n
Enter root if role-based
authentication is not
configured.
n
Enter your
vRealize Automation user
name if it is configured for
role-based authentication.
Password
n
Enter the password you
entered when you
deployed the
vRealize Automation
appliance if role-based
authentication is not
configured.
n
Enter the password for
your user name if your
user name is configured
for role-based
authentication.
Table 2‑6. Linux Command Prompt
Purpose Access Required Credentials
You use the Linux command prompt on a
host, such as the vRealize Automation
appliance host, for these tasks.
n
Stop or start services
n
Edit configuration files
n
Run commands
n
Retrieve data
1 On the vRealize Automation appliance host ,
open a command prompt.
One way to open the command prompt on your
local computer is to start a session on the host
using an application such as PuTTY.
2 Log in.
n
User name: root
n
Password: Password you
created when you
deployed the
vRealize Automation
appliance.
Table 2‑7. Windows Command Prompt
Purpose Access Required Credentials
You can use a Windows command prompt
on a host, such as the IaaS host, to run
scripts.
1 On the IaaS host, log in to Windows.
One way to log in from your local computer is to
start a remote desktop session.
2 Open the Windows command prompt.
One way to open the command prompt is to right-
click the Start icon on the host and select
Command Prompt or Command Prompt
(Admin).
n
User name: User with
administrative privileges.
n
Password: User's
password.
Migrating vRealize Automation to 7.4
VMware, Inc. 9