FileConnect Enterprise v2

  • Updated

Introduction

FileConnect Enterprise empowers you to perform in-place management of large volumes of data, records, and content stored on network file shares. This allows you to bring your file share content under RecordPoint control without moving it, so you can apply classification, retention, and defensible disposal while users continue to work with their existing file shares.

FileConnect Enterprise is an on-premise agent that runs on a Windows or Linux host within your corporate network. The agent is designed to avoid changes to on-premises firewall rules. The host that runs the FileConnect Enterprise agent only requires outbound internet connectivity in order to communicate with the RecordPoint service.

All communication back to RecordPoint is encrypted.

The RecordPoint FileConnect Enterprise connector is a premium connector and requires an additional subscription. If you believe your organization is subscribed, or would like to inquire about subscribing, contact Support.

FileConnect Enterprise is typically used alongside other RecordPoint connectors (such as Microsoft 365 or content services platforms) to give you a single place to manage records across multiple repositories.

 

Prerequisites

Operating System Requirements

FileConnect Enterprise is a containerized application that is run within Docker, a set of platforms as a service product that use OS-level virtualization to deliver software in packages called containers.

The following operating system are supported for the deployment of Docker.

  • Linux (Centos or Ubuntu)
  • Windows (Windows 10) (Limitations apply for AWS please discuss with your RecordPoint Consultant)

Please see Get Docker | Docker Documentation for further information on the environments available.

Network Requirements

There must be network connectivity between the FileConnect Enterprise agent and the following:

  • Network shares hosting the content to be managed

  • The virtual machine hosting Power BI Desktop

  • The virtual machine hosting your internet browser

The host machine must also have internet access to pull the required Docker images from container registries.

Permission Requirements

As part of the deployment of the FileConnect Enterprise Agent, the following Account Permissions are required:

  • Installation/Configuration Account
    • Local Administrator account on host machine
    • Able to install required PowerShell Modules
    • Able to map network file shares
    • Azure Global Administration permissions (app registration, certificate/client secret creation)
    • Application Administration Permissions
  • Service Account
    • Local Administrator on the host machine
    • Modify permissions to file shares for management
  • Analysis Account
    • Access to Power BI desktop and Swagger Interface 

Hardware Specifications

The following are the minimal specifications required for running the FileConnect Enterprise Agent:

  • Number of Cores: 8
  • RAM: 32 GB
  • Disk Space: >200 GB per TB of data (approximately 20% of the target source data size)

Software and Other

External Site Access

To support the operation of the FileConnect Enterprise agent, access to the following services are required: 

Elasticsearch and Redis images (Docker Hub)

Azure Container Registry (RecordPoint)

Application Insights

For further detail please see Microsoft Azure Monitor Documentation.

Launch Darkly

  • https://app.launchdarkly.com
  • https://stream.launchdarkly.com

RecordPoint APIs

Azure services

  • *.windows.net

Antivirus and malware exclusions

Real-time antivirus or endpoint protection scanning of container storage and runtime directories can cause performance and stability issues for FileConnect Enterprise. To avoid operational issues, configure your antivirus or malware scanner to exclude the following locations on the FileConnect Enterprise host.

General container data root

  • All files and directories under ${HOME}/docker

The exact path depends on the value of ${HOME} at FileConnect Enterprise deployment time. This may be a user home directory or a path such as /opt/docker.

Docker deployments

  • /var/lib/docker

    • As recommended by Docker

    • If the Docker data root was changed using the data-root configuration option, exclude that directory instead of /var/lib/docker.

Podman deployments

These are the default locations. They can be changed in Podman’s storage.conf file, and paths differ depending on whether Podman is running rootful or rootless. See Podman documentation for more information.

  • Container storage

    • Rootful: /var/lib/containers/storage

    • Rootless: ~/.local/share/containers

  • Runtime state

    • Rootful: /run/containers/storage

    • Rootless: /run/user/<UID>/containers

Deployment

A step-by-step deployment guide is provided by RecordPoint Support or your technical consultant for Windows or Linux deployments.

 

Was this article helpful?

1 out of 1 found this helpful

Have more questions? Submit a request