Veritas Velocity™ User's Guide

To configure the Velocity Client for Windows manually

1. Log on to the Windows host server as an administrator.
2. Run the velocity-client.msi and follow the prompts to install the Client on your host server.

   \\<storage FQDN/IP address>\packages\velocity-client.msi

3. Log on to the Velocity Cloud Console as an administrator.
4. From the Velocity Cloud Console, in the left pane, click Velocity Storage Server.
5. Click Generate Server Credentials.

   Make a note of the generated User name and Password credentials that display.

6. On the host server, use one of the following commands to register the host with Velocity:

   If you use the computer's hostname to identify the host server on the network:	Type the following command: %PROGRAMFILES%\Veritas\Velocity\bin\velocity_registration.exe initialize -s https://<Storage FQDN/IP address>:8443 -u <user> -p <password> Note: If you configure the Velocity Storage Server so that it is multihomed, these commands may not provide the correct IP address. You may need to change the IP address to the same IP address that matches the network that the Velocity Client is on. Where <Storage FQDN/IP address> is the FQDN or IP address of the Velocity Storage Server. Replace <user> with the user name and <password> with the password from the Generate Server Credentials dialog in the previous step. Note: If you installed the Client in a directory other than the default directory, C:\Program Files, you must modify the command to use the appropriate directory.
   If the primary FQDN or IP address of the host server is not on the same network path as the Velocity Storage Server:	Type the following command: %PROGRAMFILES%\Veritas\Velocity\bin\velocity_registration.exe initialize -i <MS SQL FQDN/IP address> -s https://<Storage FQDN/IP address>:8443 -u <user> -p <password> Note: If you configure the Velocity Storage Server so that it is multihomed, these commands may not provide the correct IP address. You may need to change the IP address to the same IP address that matches the network that the Velocity Client is on. Where <Storage FQDN/IP address> is the appropriate FQDN or IP address of the Velocity Storage Server. Replace <user> with the user name and <password> with the password from the Generate Server Credentials dialog in the previous step. The -i flag lets you specify the FQDN or IP address that is associated with the interface and represents the network path to the Velocity Storage Server. Using the -i flag ensures that Velocity uses the correct network path when it communicates with the Velocity Storage Server. Note: If you installed the Client in a directory other than the default directory, C:\Program Files, you must modify the command to use the appropriate directory.
   (Optional) If you want to secure the CIFS shares with Active Directory	Note: You must first join the Velocity Storage Server to the Active Directory domain. See Joining the Velocity Storage Server to the Active Directory domain. For Active Directory integration, include the following arguments: --adGroups <group1, group2,...> --adUser <user> [--adPassword <password>] Where: <group1, group2,...> is a group or a set of groups that are separated by commas with no spaces in between. Group names that include spaces are currently not supported. Members of the group or groups have access to the CIFS share. <user> must be a member of at least one of the groups that are listed in the adGroups argument. <password> is the password for the Active Directory user account. Velocity uses this password to configure the Velocity Client vexecd service. Velocity does not store this password. You can provide the user name on the command line to assist with the script. Otherwise, Velocity prompts you to enter a password. The SQL Server service account for the instance on the server that will host the sandbox database must be configured to run as an Active Directory account. The Active Directory account must be a member of at least one of the Active Directory groups that is specified when the Velocity Client is registered. Then, the SQL Server service account can access the CIFS share and start the database for the sandbox.

To configure the Velocity Client for Windows using the Velocity launch pad

1. On the Velocity Cloud Console, click Launch Pad.
2. On the Configure the Velocity Client tile, click Configure.
3. Click Next.
4. Select Windows for SQL Databases, and then click Next.
5. Do one of the following:

   To use host-based security for access to CIFS shares

   Complete the directions that display on the launch pad.

   To secure the CIFS shares with Active Directory

   Note: You must first join the Velocity Storage Server to the Active Directory domain. See Joining the Velocity Storage Server to the Active Directory domain. Complete the directions that display on the launch pad, and include the following arguments to the commands that are copied and pasted into the terminal: --adGroups <group1, group 2,...> --adUser <user> [--adPassword <password>] Where: <group1, group 2,...> is a group or a set of groups that are separated by commas with no spaces in between. Group names that include spaces are not currently supported. Members of the group or groups have access to the CIFS share. <user>must be a member of at least one of the groups that are listed in the adGroups argument. <password> is the password for the Active Directory user account. Velocity uses this password to configure the Velocity Client vexecd service. Velocity does not store this password. You can provide the user name on the command line to assist with the script. Otherwise, Velocity prompts you to enter a password. The SQL Server service account for the instance on the server that will host the sandbox database must be configured to run as an Active Directory account. The Active Directory account must be a member of at least one of the Active Directory groups that is specified when the Velocity Client is registered. Then, the SQL Server service account can access the CIFS share and start the database for the sandbox.

6. Click Done.