Migrating vRealize Automation 6.2 to 7.1 vRealize Automation 7.1 This document supports the version of each product listed and supports all subsequent versions until the document is replaced by a new edition. To check for more recent editions of this document, see http://www.vmware.com/support/pubs.
Migrating vRealize Automation 6.2 to 7.1 You can find the most up-to-date technical documentation on the VMware Web site at: http://www.vmware.com/support/ The VMware Web site also provides the latest product updates. If you have comments about this documentation, submit your feedback to: docfeedback@vmware.com Copyright © 2016 VMware, Inc. All rights reserved. Copyright and trademark information. VMware, Inc. 3401 Hillview Ave. Palo Alto, CA 94304 www.vmware.com 2 VMware, Inc.
Contents Updated Information 5 1 Migrating a vRealize Automation Environment 7 Migration Prerequisites 7 Prepare to Migrate Tenants and Identity Stores for Linux 8 Prepare to Migrate Tenants and Identity Stores for Windows 9 Migrate a vRealize Automation Environment with an IaaS Database Backup 9 Migrate a vRealize Automation Deployment with Automatic IaaS Database Cloning Post-Migration Task for Environments with an Internal vRealize Orchestrator 14 Validate the vRealize Automation Migrated Environment
Migrating vRealize Automation 6.2 to 7.1 4 VMware, Inc.
Updated Information This vRealize Migration guide is updated with each release of the product or when necessary. This table provides the update history of the vRealize Migration guide. Revision Description EN-002195-02 n n EN-002195-01 n n n n n n EN-002195 VMware, Inc. Revised step 3a in “Migrate a vRealize Automation Environment with an IaaS Database Backup,” on page 9.
Migrating vRealize Automation 6.2 to 7.1 6 VMware, Inc.
Migrating a vRealize Automation Environment 1 You can perform a side-by-side upgrade of your current vRealize Automation 6.2.x environment using migration. Migration moves the data in your current vRealize Automation 6.2.x environment to a new 7.1 environment that mirrors your current environment. Migration does not change your current 6.2.x environment. You cannot use migration to upgrade a vRealize Automation 7 or 7.0.1 environment to 7.1.
Migrating vRealize Automation 6.2 to 7.1 Prerequisites n Verify that you have a new target installation of vRealize Automation 7.1 whose components reflect the source 6.2.x environment. n 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.
Chapter 1 Migrating a vRealize Automation Environment 4 At the command prompt, run copy-sso. ~/copy-sso/bin/copy-sso Because you are logged in as root user, do not use sudo to run this script. 5 When prompted, enter the requested information.
Migrating vRealize Automation 6.2 to 7.1 Procedure 1 Create a full database backup of the source vRealize Automation 6.2.x IaaS Microsoft SQL database. 2 Restore the backup as a new database on the Microsoft SQL Server in the target vRealize Automation 7.1 environment. 3 Obtain the encryption key from your source vRealize Automation 6.2.x deployment. a Run the following command in an administrative command prompt on the virtual machine that hosts active Manager service to obtain the encryption key.
Chapter 1 Migrating a vRealize Automation Environment 11 12 13 Option Description Re-enter password Re-enter administrator password. Root username root Root password Root password that you entered when you deployed the vRealize 7.1 appliance. Re-enter password Re-enter root password. Enter the requested information for Source vRA IaaS Database Server. Option Description Encryption Key Encryption key string from your source vRealize Automation 6.2.x deployment.
Migrating vRealize Automation 6.2 to 7.1 What to do next “Validate the vRealize Automation Migrated Environment,” on page 16 Migrate a vRealize Automation Deployment with Automatic IaaS Database Cloning You can use the automatic migration process to migrate your vRealize Automation 6.2.x deployment to 7.1 using automatic IaaS database cloning.
Chapter 1 Migrating a vRealize Automation Environment 8 Enter the requested information for Source vRA Appliance. Option 9 10 11 VMware, Inc. Description Host name Host name for the vRealize Automation 6.2.x appliance. Root username root Root password Root password that you entered when you deployed the vRealize 6.2 appliance. Re-enter password Re-enter root password.
Migrating vRealize Automation 6.2 to 7.1 12 Option Description Passphrase New passphrase to re-encrypt sensitive content stored in migrated Microsoft SQL database. A passphrase is a series of words used to generate an encryption key to protect data while at rest in the database, such as endpoint credentials. You use this passphrase each time you install a new component. Database Security SQL Server authentication mechanism. Select Windows Authentication or SQL Authentication.
Chapter 1 Migrating a vRealize Automation Environment Procedure 1 On the vRealize Orchestrator Control Center, select Home > Manage Plug-Ins. 2 On the Manage Plug-Ins page, click the download icon for Library, vCAC, and vCACCAFE to download these plug-in DAR files. 3 Log in as root user to the vRealize Automation 7.1 virtual appliance. 4 Navigate to /usr/lib/vco/app-server/plugins. 5 Delete the DAR files that contain the Library (o11nplugin-library.dar), vCAC (o11nplugin-vcac.
Migrating vRealize Automation 6.2 to 7.1 26 Select vRealize Automation Infrastructure. 27 In the right pane, click the Reload icon. 28 Verify the IaaS host is added to the list. Validate the vRealize Automation Migrated Environment You can verify that all data is migrated successfully to the target VMware vRealize ™ Automation 7.1 environment. Prerequisites Completed migration from vRealize Automation 6.2.x to 7.1. Procedure 16 1 In your vRealize Automation 7.
Troubleshooting Migration 2 Migration troubleshooting topics provide solutions to problems you might experience when you migrate vRealize Automation. PostgreSQL Version Causes Error A source vRealize Automation 6.2.x environment containing an updated PostgreSQL database blocks administrator access. Problem If an upgraded PostgreSQL database is used by vRealize Automation 6.2.x, an administrator must add an entry to the pg_hba.conf file that provides access to this database from vRealize Automation.
Migrating vRealize Automation 6.2 to 7.1 18 VMware, Inc.
Index M migrate with automatic IaaS database cloning 12 with IaaS database backup 9 migrate tenants and identity stores linux 8 windows 9 migration overview 7 prerequisites 7 validate migration 16 P post-migration task, update vRealize Orchestrator configuration 14 T troubleshooting, external PostgreSQL database 17 U updated information 5 VMware, Inc.
Migrating vRealize Automation 6.2 to 7.1 20 VMware, Inc.
