|
Locator: NIE Home / Publications / Enterprise Search Newsletter / Issue 3 / Article 2 Collection Mirroring with Verity K2 Enterprise 4.5.1NIE Enterprise Search: Issue 3 - July, 2003 If your company owns Verity K2 enterprise search, one of the features for high availability and load-balancing situations is called collection mirroring, which enables identical collections to be accessed on two Verity K2 servers simultaneously. To mirror collections you need a minimum of two K2 servers in your search engine architecture. The collections must also be named identically on both servers in order to enable mirroring. On large collections we found that indexing the collections separately would provide a different amount of documents in each collection, thus the collections would be out of sync and would provide different results in some queries. By using the RCADMIN a command line tool that comes with Verity K2 and a series of batch files we can synchronize the collections fairly easily Before writing your batch files first login to your K2 servers using the RCADMIN command line utility and take note of what commands need to be used in the text file that will be piped to the RCADMIN utility. After logging in with RCADMIN you will get a prompt, enter “indexstateset” and then enter the name of your server. Select “C” and then enter the name of your collection. Select which state you want your collection in and exit the utility. Refer to your K2 enterprise documentation for further RCADMIN commands. To completely automate this process a series of commands need to be used in a single batch file. Here is a breakdown of the commands to be used to synchronize the mirrored collections.
If you have caching enabled on your servers you may want to automate the restart of the K2 servers and brokers to refresh the cache. Example of using RCADMIN in a batch file: Return to the Table of Contents |