The Velocity Client is a service that facilitates automated database ingestion and sandbox preparation. To configure the Velocity Client, you must copy an installation package from the Velocity Storage Server. Then, you must install it on any host servers that are intended to be used for either sandboxes or database ingestion. Finally, each host server must be registered with Velocity before you can ingest databases or create sandboxes.
You can install and register the Velocity Client manually using a Windows installation wizard. If you prefer, you can install the Client using the Velocity launch pad. The launch pad walks you through the configuration process.
By default, Velocity uses host-based security for access to CIFS shares. To restrict access of CIFS shares to authorized users, you can choose to integrate with Active Directory when you configure the Velocity Client for Windows. However, you must first join the Velocity Storage Server to the Active Directory domain.
When the Velocity Client is successfully registered, it appears in the Velocity Console. To view any registered instances of the Velocity Client, click Clients in the left pane.
When you uninstall an instance of the Velocity Client, it must be able to connect to the Velocity Storage Server because the process also deregisters the Velocity Client.
You can also delete a client if an error was made in the initial registration and you want set it up again with valid information.
Configuring the Velocity Client for Windows manually
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.
To configure the Velocity Client for Windows manually
Log on to the Windows host server as an administrator.
Run the velocity-client.msi and follow the prompts to install the Client on your host server.
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.
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:
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.
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
You must first join the Velocity Storage Server to the Active Directory domain.
<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.
Configuring the Velocity Client for Windows using the Velocity launch pad
To configure the Velocity Client for Windows using the Velocity launch pad
On the Velocity Console, click Launch Pad.
On the Configure the Velocity Client tile, click Configure.
Click Next.
Select Windows for SQL Databases, and then click Next.
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
You must first join 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,...>
--clientUser
<user> [--clientPassword <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.
Searching...
