Removing Legacy Content Repository - AFS

AFS Installation and Administration Guide

Product
AFS
AFS_Version
7.10
Platform
RHEL
Category
Reference Guide

It is possible to remove the Legacy Content Repository and only keep writing in Nerada.

This can be useful in two cases:

  • The migration to Nerada was tested and validated.
  • Uploads are only done in full mode, allowing to directly switch to Nerada as a writing location.

Disable the writing in the Legacy database

For each indexer, edit the conf.xml configuration file located in /usr/local/afs7/conf/ and set the following parameter to false:

Delete the Legacy MongoDB Content Repository database

For each front, the content repository comprises databases named as follows:

  • antidot-cr-$SERVICE_ID-$SERVICE_STATUS-$FEED_NAME

These databases can be removed in any order.

  1. Connect to the front-end server by using SSH.

    Example:

    ssh fluid-front01

  2. Connect remotely to the Mongo databases located on the front server.

    Example:

    mongo -u $USER --authenticationDatabase admin -p fluid-dbfrontXX.vitry.exploit.anticorp

  3. Enter your password when requested.
  4. List the Mongo databases by running the following command:

    mongo> show dbs

  5. Select the database to remove by running the following command:

    mongo> use antidot-cr-$SERVICE_ID-$SERVICE_STATUS-$FEED_NAME

  6. Delete the database by calling the following method:

    mongo> db.dropDatabase()

  7. Repeat Steps 4 and 5 for all other databases to remove.

Clean the Update Manager data

On the Update Manager server, run the following command:

As antidot user

afs_um_delete -t CREP_REPLY -s $SERVICE_ID -S $SERVICE_STATUS -f $FEED_NAME