Migrating to Nerada Content Repository - AFS

AFS Installation and Administration Guide

Product
AFS
AFS_Version
7.10
Platform
RHEL
Category
Reference Guide

From AFS v7.9.6.0, it is possible to migrate to the second-generation content repository technology called Nerada.

Nerada uses a centralized mongoDB database avoiding the replication of database on each front, and thus increasing deployment performance.

Nerada supports the following features:

  • Consistent query response across all front servers that is resilient against crashed PaFs
  • Synchronization between search side and content side using an explicit synchronization query parameter

Please refer to your Antidot contact to better prepare your migration to Nerada.

The following diagram shows the workflow within an installation using the Legacy Content Repository.

Workflow with the Legacy Content Repository

The following diagram shows the workflow within an installation using Nerada.

Workflow when using Nerada

Before totally switching to the Nerada solution, it is possible to make a transition gathering both the Legacy Repository and Nerada.

The following diagram shows the workflow when using the Legacy Content Repository and Nerada.

Workflow during transition with Nerada and the legacy CR

If a Mongo Cluster is already in use for FluidTopics database, Nerada can be deployed on the same Mongo cluster if disk space is sufficient. The size of Nerada Mongo is maximum 10 times the size of the Mongo database located on front servers.