This article explains how to install and configure EVnearSync. Before following the steps below, ensure the EVnearSync system requirements are met.

Installing EVnearSync

EVnearSync can be installed in two distinct stages:

  • Core/Web: This needs to be performed once on a separate Windows 2012 R2 or Windows 2016 server, meeting the requirements outlined in the EVnearSync system requirements.
  • Agent: This needs to be installed on each Enterprise Vault server that has Storage and/or indexing on it.

Installation Checklist

You’ll want to have the following information on hand before starting the installation:

  • Configuration details of the EVnearSync Application Server
  • List of connection details for Enterprise Vault servers that are going to have the EVnearSync agent installed
  • SQL Server connection details for the EVnearSync database that the installation creates
  • SQL Server connection details for the Enterprise Vault Directory Database
  • Enterprise Vault Service Account username and password. (This account should be a local administrator on the application server.)
  • License file for EVnearSync

EVnearSync Core Installation

Install the EVnearSync Core/Web components using these steps:

  1. Locate the EVnearSync installation file and copy it to a temporary folder.
  2. Launch the installation file and follow the prompts.
  3. If desired, customize which components are installed and the installation folder. A description of the components can be found in Appendix 1.
  4. When you’re asked for information relating to Microsoft SQL Server, provide the name of a SQL instance or SQL Server that will host the EVnearSync database, as well as information to connect to the Enterprise Vault Directory Database.
    • Named instances can be used, as well as the default instance. For example:
      • Default instance: mySqlServerName.MyDomain.com
      • Named instance: mySqlServerName.MyDomain.com\MyInstanceNam
  5. At the end of the installation wizard, click Install to start the installation.

Notes:

  • When asked for the Account Name and Password, it’s normal to use the Enterprise Vault Service Account.
  • If the installer doesn’t find the appropriate .Net Framework version, it prompts you to download and install it.
  • During the installation of the EVnearSync Core/Web components, Inbound Rules will be added to the Windows Firewall. This allows the EVnearSync agents to communicate with the EVnearSync Core.

Validating the Core Installation

To verify that the EVnearSync Core has been successfully installed, double-click on the EVnearSync icon on the desktop. It may take a few minutes to launch EVnearSync for the first time.

EVnearSync Agent Installation

Install the EVnearSync agent using the steps below.

  1. Locate the EVnearSync installation and license files. EVnearSync has 32-bit and 64-bit installers. Ensure the correct one is launched, depending on your operating system.
  2. Copy the installation and license files to a temporary folder on the Enterprise Vault server.
  3. Launch the installation file and follow the prompts.
  4. If desired, specify which components will be installed and the installation folder.
  5. When you’re asked for an account name and password, it’s normal to use the Enterprise Vault Service Account.
  6. When you’re asked for information relating to the EVnearSync Core, if the machine you’re installing the agent on is part of a cluster, select the checkbox and enter the Enterprise Vault cluster server name.
  7. You’ll be prompted to locate the license file. Browse to the folder and file containing your license information, and then select it. Checking the license can take a few minutes.
  8. At the end of the installation wizard, click Install to start the installation.

Note: On Enterprise Vault 10.0.4 or higher, in the Vault Administration Console, browse to the EVnearSync Content Provider. Open the properties, and set the status to Enabled.

Validating the Agent Installation

After installing each module, or at the end of the installation, use the steps below to test that the modules are functioning correctly and reporting to the Core.

  1. Open the EVnearSync Admin Console.
  2. Go to Manage.
  3. Go to EVnearSync.
  4. Review the list of Agent services and ensure they are idle.

Configuring EVnearSync

EVnearSync has an intuitive web interface for configuring replication of Enterprise Vault data. Initially, consider configuring replication at the Vault Store level. The web interface can be accessed via the console session where the EVnearSync Core/Web components were installed using the URL: http://localhost/EVnearSync
In addition, you can access the web interface remotely from a workstation using the URL: http://servername.domainname/EVnearSync
Note: The first time the site is accessed, there can be a delay before the screen loads. This is because of the way that ASP.Net works. It is normal.
Use the Vault Store Enablement Wizard to perform the initial configuration. This is accessed by going to Manage > Vault Store.

Vault Store Enablement Wizard

After you launch the wizard, set up the configuration using these steps:

  1. Click Add Group.
  2. Select the Vault Store group that you want to configure for replication.
  3. Replicate closed partitions to avoid data loss due to single instancing of Enterprise Vault in Vault Store Groups.
  4. Select if you want to start the initial replication immediately. If you don’t select this, the replication starts according to the site settings.
  5. Select the path to the remote location where you want to save the replicated data. For each Vault Store, enter a destination path. It is not necessary to create a sub-folder per Vault Store. Just the top level UNC path is needed.
  6. Review the EVnearSync service that is being used for the replication. This will normally be the Agent Service located on the Enterprise Vault server hosting the Vault Store. After selecting the appropriate EVnearSync service, click Finish.

Configuring Alerts

EVnearSync does not send SMTP alerts by default; however, alerts can be configured. To configure them refer to the SMTP Configuration section in the Administration Guide.

Deployment Scenario Examples

Many deployment scenarios are possible when approaching an EVnearSync and Enterprise Vault environment. This section contains a few examples.

Single Server

This example is suitable for very small Enterprise Vault installations. In this situation, the Core/Web components and Agent components are installed on the Enterprise Vault server, as shown below.

Single Server Vault Host

This is common in small-to-medium installations. In this situation, the Core/Web components are installed on one server, and the Agent components are installed on the Enterprise Vault server, as shown below.

Multi-Enterprise Vault Hosts

This is common in medium-to-large installations. In this situation, the Core/Web components are installed on one server and the Agent components are installed on each Enterprise Vault server that hosts a Storage or Indexing Service, as shown below.

Appendix 1 – Description of Install-able Components

The table below lists the components that are available during the installation of EVnearSync.

Component Notes
Core Service This is the core component of EVnearSync and provides the functionality of the product
Web Interface This is the user interface component that will be installed as an IIS application

Note: The agent-only installation doesn’t provide a list of components that can be selected or de-selected.
The table below lists the EVnearSync services that are installed with the Core services.

Component Notes
EVnearSync Core Service In Task Manager, this is shown as CoreService.exe.
This service will be set to automatic, and logon information will be whatever was provided during the installation.

The table below lists the services that are installed with the EVnearSync agent.

Component Notes
EVnearSync Agent Service In Task Manager, this is shown as AgentService.exe.
This service will be set to automatic, and logon information will be whatever was provided during the installation.

Appendix 2 – Accessing the Core from a remote machine

The EVnearSync Core/Web components provide the administration interface into EVnearSync. They also provide monitoring and reporting information. It’s not necessary to connect to the server console to run the administration console. It’s a normal website that can be accessed from any web browser.

Appendix 3 – Minimum List of Roles and Features

A list of the minimum Roles/Features that are needed to host, run, and access the Core/Web components of EVnearSync are below.

  • Web Server (IIS)
  • Web Server
  • Common HTTP Features
    • Static Content
    • Default Document
    • Directory Browsing
    • HTTP Errors
  • Application Development
    • ASP.NET
    • .Net Extensibility
    • ISAPI Extensions
    • ISAPI Filters
  • Security
    • Windows Authentication
    • Request Filtering
  • Performance
    • Static Content Compression
  • Management Tools
  • IIS Management Console

 

All the features above can be also installed using the following Power-shell cmdlet:

install-windowsfeature net-framework-features
Install-windowsfeature web-net-ext45, web-asp-net, web-server -includemanagementtools
Install-WindowsFeature Web-Asp-Net45
Install-WindowsFeature Web-Windows-Auth

Print Friendly, PDF & Email