Arctera Enterprise Vault™ Insight Surveillance Installation Guide

To create the configuration database

1. If you have yet to display the eDiscovery Manager website, browse to the following location:

   http://server_name/EVBAAdmin

   Where server_name is the name of the server on which you installed the Insight Surveillance server software.

2. In the Configuration Database Details page, enter your preferred details, and then click OK.

   SQL Server	Specifies the name or IP address of the SQL Server computer. You can specify the IP address in either IPv4 or IPv6 format. SQL instances are supported. Alternatively, in SQL Server environments where the database is part of an Always On availability group or failover cluster instance (FCI), you can specify the virtual network name or IP address of the availability group listener or FCI. For guidelines on deploying databases in Always On environments, see the following article on the Microsoft website: https://msdn.microsoft.com/library/ff878487.aspx You must append the port number if you have chosen to use a non-default port. For example, SQLServer,1234.
   Database name	Specifies the name of the configuration database. The name cannot contain any of the following characters: \ / : * ? " < > | ' Note: Surveillance and eDiscovery cannot share the same configuration database. So, if you previously created the configuration database for one application, you must create a new database with a different name when setting up the other application.
   Use Existing Database	Instructs Insight Surveillance to use the specified existing database instead of creating a new one. If you choose this option, the remaining boxes in the page are unavailable.
   Data File Folder	Specifies a location for the configuration database file. This location should be a valid, existing path on the SQL Server computer. A minimum of 300 MB is required for the default configuration database. You can specify a local path or a UNC path. For example, you might specify the path as E:\SQLData or \\my_computer\SQLData.
   Log File Folder	Specifies a location for the database log files. This location should be a valid, existing path on the SQL Server computer. A minimum of 300 MB is required for the database log files. You can specify a local path or a UNC path. For example, you might specify the path as E:\SQLLogs or \\my_computer\SQLLogs.
   Initial Database Size	Sets the initial size in megabytes of the configuration database file. In the Growth % box, you can specify as a percentage of the file size the amount of space that is automatically added to the file each time more is needed.
   Initial Log Size	Sets the initial size in megabytes of the database log files. In the Growth % box, you can specify as a percentage of the file size the amount of space that is automatically added to a file each time more is needed.
   Windows Authentication	Specifies whether to use a Microsoft Windows user account to connect to the configuration database. If you clear this option, you must set the SQL logon name and password to use for the database connection.
   Connection Time Out	Specifies the amount of time in seconds to wait for connections to the configuration database to complete before terminating the attempt and generating an error.
   Connection Life Time	Specifies the time in seconds that a connection to the configuration database is considered valid. When the time has elapsed, the connection is disposed of.
   Max Pool Size	Specifies the maximum number of database connections that can be simultaneously opened to the configuration database.

3. Under Database Master Key Configuration, specify the following:

   Database Master Key Password

   Enter Database Master Key Password. To encrypt the data of the Configuration Database, type the password to create the SQL Server Database Master Key. Note down this password as it is required while migrating or restoring the configuration database to another SQL server instance. This password must comply with the Windows Password Policy of the computer that is running the instance of SQL Server. While using the existing database, if the selected database already has the database master key, the application ignores this password and proceeds to the next step. If the selected database does not have the database master key, the application uses the same password to create a new database. Note: If you are upgrading the database, providing this password is a one-time activity only. You do not need to provide this password during the next upgrade, click Update to start the configuration.

   Confirm Password

   Enter the same Database Master Key Password again for confirmation. The Confirm Password must match the Database Master Key Password.

4. When Insight Surveillance prompts you to do so, restart the Enterprise Vault eDiscovery Manager service by using the Services snap-in to Microsoft Management Console.

   Note:

   Restarting the service causes Insight Surveillance to check the security of various temporary folders that the application uses. If this security check fails, an error event with an ID of 585 is recorded in the Arctera Enterprise Vault event log, and the service does not start.

   See Security requirements for temporary folders.

5. In the eDiscovery Manager website, click Upload License to import your license key file into Insight Surveillance.

To create the customer databases

1. In the left pane of the eDiscovery Manager website, right-click the server node, and then click New Customer.
2. Complete the details in the Create Customer page, and then click OK.

   Customer Type	Indicates that this database is a customer database for Insight Surveillance.
   Name	Specifies a unique name for the customer. The name cannot contain any of the following characters: \ / : * ? " < > | '
   VaultID(s)	Identifies the journal mailbox archive that the customer uses. You can obtain the ID by looking at the archive's property page in the Vault Administration Console. One customer must have a blank VaultID(s) field to designate that it is the default customer. All other customers must have a unique entry in the field, such as the required ID or a statement such as "Do_Not_Use".
   Directory DNS aliases	Specifies the DNS alias, server name, or IP address of the Enterprise Vault Directory service computer. You can specify IP addresses in either IPv4 or IPv6 format. Take care to specify the correct DNS alias information. If the information is wrong, no vault stores will be visible in any area of the client.
   Administrator User or Group	Optionally nominates an Active Directory user account or group account as an administrator for the Insight Surveillance customer database. This user or group has full administrative permissions in the customer database and typically assigns application-wide roles to other users. Specify the account details in the form domain\user_or_group_name; for example, "OurDomain\Marie.Lopez". The Vault Service account already has full administrative permissions in the customer database, so there is usually no need to nominate another user or group. However, you may want to do this if your company policy restricts the use of service accounts. Note: If you choose to nominate an administrator user or group then, using the Insight Surveillance web application, you must also create an employee profile for the user or group in the customer database. For instructions on how to do this, see the Administrator's Guide. By creating an employee profile, you allow the user or group to perform administrative tasks in the customer database, such as deleting departments.
   Enable Customer's tasks	Enables users to perform activities in the Insight Surveillance web application. If you clear this option, only automatic tasks like scheduled searches are permissible.
   IIS section
   Virtual Directory	Specifies the name of the IIS virtual directory that the Insight Surveillance reporting functionality uses. No two customers can share the same virtual directory name. The directory name must not include space characters or any of the following characters: * ? \ / % ' " Note that you cannot name the virtual directory for any Insight Surveillance customer as "EVBAAdmin" because this name is reserved for the eDiscovery Manager website.
   IIS Server	Specifies the name or IP address of the IIS server that is to host the Insight Surveillance site. You can type the IP address in either IPv4 or IPv6 format. However, you cannot type an IPv6 address that includes colons (:) or is enclosed in square brackets ([]). The default entry for this field is the server on which you are running the eDiscovery Manager website.
   Manage Virtual Directory	Lets you administer the virtual directory by using the Insight Surveillance application. By default, the option is selected.
   Database Details section
   SQL Server	Specifies the name or IP address of the SQL Server computer on which the customer database is to reside. You can specify the IP address in either IPv4 or IPv6 format. SQL instances are supported. Alternatively, if the database is part of an Always On availability group or failover cluster instance (FCI), you can specify the virtual network name or IP address of the availability group listener or FCI. For guidelines on deploying databases in Always On environments, see the following article on the Microsoft website: https://msdn.microsoft.com/library/ff878487.aspx You must append the port number if you have chosen to use a non-default port. For example, SQLServer,1234.
   Database	Specifies the name of the customer database. The name cannot contain any of the following characters: \ / : * ? " < > | '
   Use Existing Database	Instructs Insight Surveillance to use the specified existing database instead of creating a new one. If you select this option, many of the remaining boxes in the page become unavailable. By default, the option is not selected.
   Data File Folder	Specifies a location for the configuration database file. This location should be a valid, existing path on the SQL Server computer. You can specify a local path or a UNC path. For example, you might specify the path as E:\SQLData or \\my_computer\SQLData.
   Log File Folder	Specifies a location for the database log files. This location should be a valid, existing path on the SQL Server computer. You can specify a local path or a UNC path. For example, you might specify the path as E:\SQLLogs or \\my_computer\SQLLogs.
   Initial Database Size	Sets the initial size in megabytes of the customer database file. In the Growth % box, you can specify as a percentage of the file size the amount of space that is automatically added to the file each time more is needed.
   Initial Log Size	Sets the initial size in megabytes of the database log files. In the Growth % box, you can specify as a percentage of the file size the amount of space that is automatically added to a file each time more is needed.
   Windows Authentication	Specifies whether to use a Microsoft Windows user account to connect to the customer database. If you clear this option, you must set the SQL logon name and password to use for the database connection.
   Connection Time Out	Specifies the amount of time in seconds to wait for connections to the customer database to complete before terminating the attempt and generating an error.
   Connection Life Time	Specifies the time in seconds that a connection to the customer database is considered valid. When the time has elapsed, the connection is disposed of.
   Max Pool Size	Specifies the maximum number of database connections that can be simultaneously opened to the customer database.
   DSN	Specifies the full connection string, or Data Source Name (DSN), to use when connecting to the customer database. The process of creating and connecting to the database automatically fills in this field. Do not modify the details unless Arctera Support advises you to do so.
   Reporting FileGroup Location	During the fresh Surveillance installation or upgrade, the new Enhanced Reporting feature presents a mandatory field to specify the 'FileGroup' location. This specified FileGroup location serves as the storage for reports-specific data. It is recommended to select storage location other than the CA database location with sufficient storage.

3. Wait for Insight Surveillance to create the customer database. This process can take several minutes to complete.
4. Repeat steps 1 through 3 for each customer database that you want to create.