We use cookies on our website to ensure we provide you with the best experience on our website. By using our website, you agree to the use of cookies for analytics and personalized content.This website uses cookies. More Information
It seems like your browser didn't download the required fonts. Please revise your security settings and try again.

Attention

Starting May 1st, 2018, we will no longer offer the ArchiveOne family of products. This includes all editions of ArchiveOne, ArchiveOne for Files, Max Compression, and Access Security Manager. If you currently hold a maintenance and support contract, you will continue to receive our award-winning support until your contract expires, or until May 1st, 2019, whichever occurs first. The license for ArchiveOne is perpetual; therefore the software may continue to be used independently without any updates or support indefinitely.

How to Implement Repository Replacement

  • Last updated on

This article refers to the Barracuda ArchiveOne version 6.5.1.2840 and higher.

Implement Repository Replacement to assist with slow retrievals in the following scenarios:

  • When a repository is moved from one location to another and the original repository is no longer valid but still present in URL links;
  • A stub is pointing to a linked repository on a server that no longer exists (this can introduce at least an eight second delay to resolve the server name);
  • Linked repositories to Compliance are present and no longer in use, causing an timeout.

Use the following steps to define a repository replacement for a repository on a decommissioned server:

  1. Log in to the Archive server, and browse to: \\Configuration_Server\Add-ins\AOnePol
    where Configuration_Server is the name of the Configuration server where the Add-ins shared folder is hosted. If you do not know the Configuration Server name, go to the Status Node in the Admin Console.
  2. Right-click AOnePol, and click New > Text Document.
  3. Name the file AOneRepReplacement.C2C, and open the file in Notepad.
  4. Add the following text to the file:
    [RepReplacement]
    RepositoryRpMultiCountItem=1
    [Original]
    Name0=\OLD_SERVERNAME\Repository1
    [Replacement]
    Name0= \NEW_SERVERNAME\Repository1

    Where \OLD_SERVERNAME\Repository is the old path to the repository on the decommissioned server and \NEW_SERVERNAME\Repository1 is the path to the current location on the new server.
    For example, if you have a repository called 2015 which has been moved from SERVER01 to SERVER02, you would add the following text:
    [RepReplacement]
    RepositoryRpMultiCountItem=1
    [Original]
    Name0=\SERVER01\2015
    [Replacement]
    Name0= \SERVER02\2015

    For additional repositories, you will need to increment the RepositoryRpMultiCountItem value by one and the Name value by one, for example:
    [RepReplacement]
    RepositoryRpMultiCountItem=3
    [Original]
    Name0=\SERVER01\2015
    Name1=\SERVER01\2014
    Name2=\SERVER01\2013
    [Replacement]
    Name0=\SERVER02\2015
    Name1=\SERVER02\2014
    Name2=\SERVER02\2013


  5. Save and close the file.

  6. The next time the Quick Link Client is launched, it sends a request for a message for repository \OLD_SERVERNAME\Repository. The Policy service determines if a replacement repository is present, for example, \NEW_SERVERNAME\Repository. When the replacement repository is found, the Policy service no longer attempts to load the repository \OLD_SERVERNAME\Repository, saving the time taken to resolve the old server.
Last updated on