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.

Understanding Repository Equivalence

  • Last updated on

Repository Equivalence allows a search to apply first to one repository and then to another, that is, its equivalent. This is useful when:

  • Two repositories which have the same repository name, but are stored in two different locations on disk, need to be merged. You can give the repositories different names and then mark one as the equivalent of the other. Any search which is run against a repository is automatically run for its repository equivalent.
  • A repository has been renamed but the retrieval link in the message stub still refers to the original repository name. You can create a new repository with the original name as give in the retrieval link and make this one a repository equivalent of the existing renamed repository.

For instance, if the user attempts to retrieve a message from the repository 2015 which has a repository equivalence set for Year_2015, then:

  • The Quick Link Client sends a retrieval request for a message in repository 2015.
  • The ArchiveOne service attempts to retrieve the message from repository 2015.
  • If the message cannot be located, for example, a repository of that name cannot be found, the ArchiveOne service checks for a repository equivalent.
  • The ArchiveOne service finds the repository equivalent Year_2015 and attempts to retrieve the message from this repository instead.
  • If this retrieval also fails, the ArchiveOne service then searches through all remaining repositories to locate the message for retrieval.

 

Last updated on