EVnearSync System Requirements (QT3900)

This article contains system requirements for EVnearSync. An EVnearSync deployment consists of two components:

• EVnearSync Agent: The agent needs to be installed on each Enterprise Vault server in the environment that hosts a storage service or indexing service.
• Core/Web: The EVnearSync Core/Web components need to be installed on a separate server. It is the Core/Web components that collate replication data and give the administrator the interface to observe EVnearSync operations.

System Requirements

The following software requirements should be noted.

Agent only installation

*We’ve tested against operating systems supported by Enterprise Vault version 12.5 and earlier.

Core/Web product installation

Note: If the installer doesn’t find the appropriate .Net framework version, it prompts you to download and install it.

Enterprise Vault Requirements

EVnearSync doesn’t currently support Enterprise Vault Collections on open partitions. Enterprise Vault partition data that you want to replicate should be configured to use a trigger file, with partition scanning set to “every 1 minute”. This is an EVnearSync best practice configuration setting.

Microsoft SQL Server Requirements

EVnearSync stores configuration and replication information in a SQL database. For small environments this can be on the same SQL Server as the Enterprise Vault Directory Database (or Vault Store databases). In larger deployments, it is preferred to have this database on a dedicated SQL Server instance.

Disk Space

Here’s how much space is recommended for the EVnearSync database:

• Database: 250Mb
• Log: 500Mb

Note: Configuring best practice SQL Server maintenance plans and regularly backing up the EVnearSync database is recommended.

Versions

These versions of Microsoft SQL Server are supported:

Note: It’s recommended to have the latest service pack applied to the SQL Server.