You deploy and configure a Windows-based virtual machine to host the SQL Server database required for the vRealize Automation IaaS components. After you install the SQL instance, you perform additional configuration to allow Cloud Builder to perform initial validation and deploy the necessary vRealize Automation components.

You create a virtual machine on the sfo01m01esx01.sfo01.rainpole.local host for the Microsoft SQL Server with the following virtual machine, software, and network configuration requirements.

Table 1. Virtual Machine Requirements for the External vRealize Automation SQL Server

Setting

Value

ESXi Host

sfo01m01esx01

VM Name

vra01mssql01

Guest OS

Microsoft Windows Server 2016 (64-bit)

vCPU

8

Memory (GB)

16

Hard Disk (GB)

200

SCSI Controller

LSI Logic SAS

Datastore

sfo01-m01-bkp01

Network Interface

VM Network

Network Adapter Type

1 x VMXNET3

Table 2. Network Requirements for the External vRealize Automation SQL Server

Setting

Value

Host Name

vra01mssql01

Static IPv4 Аddress

172.16.11.72

Subnet Мask

255.255.255.0

Default Gateway

172.16.11.253

DNS Server

172.16.11.5

FQDN

vra01mssql01.rainpole.local

Table 3. Software Requirements for the External vRealize Automation SQL Server

Component

Requirement

Operating System

Windows Server 2016 (64-bit)

VMware Tools

Latest version

SQL Server

SQL Server 2017 Standard or later (64-bit)

Microsoft SQL Server Management Studio

Important:

During the SQL Server installation, the Database Engine configuration wizard prompts you to provide the user name and password for the SQL Server administrator. If this user is not added during the SQL Server installation, select SQL Authentication from the Authentication drop-down menu, enter sa in the User name text box, and sa_password in the Password text box.

Active Directory

Join the virtual machine to the rainpole.local domain.

Remote Desktop Protocol

Enable RDP access.

Procedure

  1. Deploy the the External vRealize Automation SQL Server VM with the specified configuration.
  2. Log in to the SQL Server virtual machine by using a Remote Desktop Protocol (RDP) client.
    1. Open an RDP connection to the vra01mssql01.rainpole.local virtual machine.
    2. Log in by using the following credentials.
      Settings Value
      User name Windows administrator user
      Password windows_administrator_password
  3. Enable Microsoft Distributed Transaction Coordinator (MSDTC).
    1. Click the Windows Start button, type comexp.msc, and press Enter.

      The Component Services window opens.

    2. In the Console Root on the left pane, navigate to Component Services > Computers > My Computer > Distributed Transaction Coordinator.
    3. Right click Local DTC and select Properties.
    4. In the Local DTC Properties dialog box, click the Security tab, configure the following values, and click OK.

      Setting

      Value

      Network DTC Access

      Selected

      Allow Remote Clients

      Selected

      Allow Inbound

      Selected

      Allow Outbound

      Selected

    5. In MSDTC Service dialog box, select Yes to restart the MSDTC service.
  4. Create the vRealize Automation account in the SQL Server instance.
    1. Click the Windows Start button and open Microsoft SQL Server Management Studio.
    2. In the Connect to Server dialog box, leave the default value for the Server Name text box, from the drop-down menu select Windows Authentication, and click Connect.
    3. In the Object Explorer tree, expand the VRA01MSSQL01 server instance, right click theSecurity folder, and select New > Login.
    4. In the Login dialog box, under General, enter rainpole\svc-vra in the Login name text box.
    5. On the Server Roles page, select sysadmin and click OK.
  5. Create the new vRealize Automation database.
    1. Click the Windows Start button and open Microsoft SQL Server Management Studio.
    2. Right click the Databases folder and select New Database.

      The New Database wizard appears.

    3. In theGeneral page, enterVRADB01 forDatabase name and rainpole\svc-vra for Owner.
    4. On the Optionspage, configure the following recovery model settings, and click OK.

      Setting

      Value

      Recovery model

      Simple

      Compatibility level

      SQL Server 2014 (120)

      Other options > Miscellaneous > Allow Snapshot Isolation

      True

      Other options > Miscellaneous > Is Read Committed Snapshot On

      True

  6. Allow access to Microsoft SQL Server on TCP port 1433.
    1. Click the Windows Start button, type WF.msc, and press Enter.

      The Windows Firewall with Advanced Security window appears.

    2. In the navigation pane, right click Inbound Rules and select New Rule.

      The New Inbound Rule Wizard appears.

    3. On the Rule Type page, select the Port radio button, and click Next.
    4. On the Protocol and Ports page, select TCP, enter the port number 1433 in the Specific local ports text box, and click Next.
    5. On the Action page, select Allow the connection, and click Next.
    6. On the Profile page, select the Domain,Private, and Public profiles, and click Next.
    7. On the Name page, enter Microsoft SQL Server Port (1433) and click Finish.
  7. Allow access for Microsoft Distributed Transaction Coordinator.
    1. Click the Windows Start button, type WF.msc and press Enter.

      The Windows Firewall with Advanced Security window appears.

    2. In the navigation pane, select Inbound Rules > New RuleInbound Rules.

      The New Inbound Rule Wizard appears.

    3. On the Rule Type page, select the Predefined radio button, selectDistributed Transaction Coordinator, and click Next.
    4. On the Predefined Rules page, select all rules for Distributed Transaction Coordinator (RPC-EPMAP), Distributed Transaction Coordinator (RPC), Distributed Transaction Coordinator (TCP-In), and click Next.
    5. On the Action page, select Allow the connection, and click Finish.
  8. Unmount any ISO files mounted to the virtual machine.