Prerequisites

• RDP to all IaaS component servers, select Start > Administrative Tools > Services and stop all VMware vRealize Automation Services, Agents, and Distributed Execution Managers.
• RDP into all IaaS Web component servers.
• Use Internet Information Services Manager to stop the VMware vRealize Automation application pools: Repository, vCAC, and WAPI.
• Backup your current VMware vRealize Automation SQL database and restore it to the new database server.
• Grant the database connection credentials used by the VMware vRealize Automation service dbo and access to the database in the new location. Ensure you can connect to the new SQL server and database from the IaaS server.

Update the configuration files for the Manager Service and Model Manager Web components

For vRealize Automation 6.x

1. Within the IaaS Manager servers, modify:

"...\Program Files (x86)\VMware\vCAC\Server\ManagerService.exe.config" as follows:

1. Within the < connectionStrings... section, update Data Source and Initial Catalog with the new details.

< connectionStrings > < add name="VMPS2" connectionString="Data Source=NewSQLserver;Initial Catalog=DBname;....

2. Within the < serviceConfiguration... section, update Data Source and Initial Catalog with the new details.

< serviceConfiguration serviceUri="https://VCAC6.yourdomain.com:443/VMPS" ...... connectionString="Data Source=NewSQLserver;Initial Catalog=DBname;...

2. Within the IaaS Web component servers, modify:

1. Within the < repository server... section, update with the new database server and name:

< repository server="NewSQLserverName" database="DBname" store="https://vcac6.yourdomain.com/"...

For vRealize Automation 7.x

1. Within the IaaS Manager server, modify:

1. In the < connectionStrings... section, update Data Source and Initial Catalog with the new details.

<connectionStrings> <add name="vcac-repository" providerName="System.Data.SqlClient" connectionString="Data Source=NewSQLserver;Initial Catalog=DBname;...

2. Within the IaaS Web component servers, modify:

1. In the < connectionStrings... section, update Data Source and Initial Catalog with the new details.

<connectionStrings> <add name="vcac-repository" providerName="System.Data.SqlClient" connectionString="Data Source=NewSQLserver;Initial Catalog=DBname;... />

All 6.x and 7.x versions

3. Within the VMware vRealize Automation IaaS MSSQL database on the new server:
   1. Update the DynamicOps.RepositoryModel.Models tables to reflect the update configuration file changes:

1. Execute the following query against the IaaS MS SQL database to check the current configuration for each model

   SELECT * FROM [vra].[DynamicOps.RepositoryModel].[Models]

2. Ensure the connection strings in use are the same on the models as used by the configuration files modified previously.
   1. Modify the value in the "ConnectionString" column:

UPDATE [vra].[DynamicOps.RepositoryModel].[Models] set ConnectionString="<updated_connection_string>" WHERE ConnectionString like '%User ID%'

Note: In case of cross-domain configuration between SQL Server and the IaaS Windows server components, update the credentials settings portion within the ConnectionString to "Integrated Security=True;" or "Integrated Security=False" if using local SQL authentication.  These values should reflect the same used within the configuration files.

4. Within the IaaS Manager / Web component servers:

   1. Start the VMware vRealize Automation application pools: Repository, vCAC, and WAPI.
   2. Start the VMware vRealize Automation Services, Agents, and Distributed Execution Managers.