Operating the indexer

This section describes the use of the indexer in a single-server environment. Please contact the ConSol CM support or your ConSol CM consultant for information about the indexer in a cluster.

Indexer directory structure

The data directory is set using the CM system property cmas-core-shared, data.directory. Please see section ConSol CM data directory for information about the structure and content of the index directory.

Monitoring the indexer

This is treated in the section Checking the status of the indexer.

Backup and recovery of the index

All ConSol CM indices are stored on the file system. However, you cannot just go ahead and copy the files and directories during system operation, because this might lead to inconsistent states (e.g., .lock files are used). That means, in order to make a backup of the CM indices, you have to follow some basic principles. Here we offer you a backup concept.

Index backup

The correct way is to use the following HTTP request using basic authentication for global admin:

wget http://${indexing.master.host:port}/index/snapshot --user ${admin} --password ${password} -Obackup.jar

This will download the full index into a backup.jar file. The received full snapshot will have the timestamp of the moment when the command was executed. Please see the following code block for an example of the file content.

unzip -l backup.jar

Archive:  backup.jar

  Length      Date     Time    Name

---------  ---------- -----   ----

      158  2012-08-23 11:09   META-INF/...

     7739  2012-08-23 11:09   ticket/_82.fdt

      280  2012-08-23 11:09   ticket/segments_7y

    12293  2012-08-23 11:09   ticket/_82.frq

      123  2012-08-23 11:09   ticket/_82.nrm

    10577  2012-08-23 11:09   ticket/_82.prx

    21624  2012-08-23 11:09   ticket/_82.tis

     1366  2012-08-23 11:09   ticket/_82.fnm

      956  2012-08-23 11:09   ticket/_82.fdx

      308  2012-08-23 11:09   ticket/_82.tii

           2012-08-23 11:09   unit/...

           2012-08-23 11:09   engineer/...

---------                     -------

    84070                     49 files

Index restore

In order to recover/restore, e.g., a corrupted ticket index you have to:

• Stop the CM master indexing server (the CM server has to be stopped, not only the indexer services).
• Clean the master indexing server directory <CMAS_DATADIR>/index/index.${number}/ticket/.
• Clean the master indexing server directory <CMAS_DATADIR>/index/index.${number}/ticket.uuid/.
• Unpack the backup.jar/ticket/* files into the master indexing server directory <CMAS_DATADIR>/index/index.${number}/ticket/.
• Restart the CM master indexing server (the CM server has to be restarted, not only the indexer services).

In a cluster environment, the master indexing server will automatically synchronize the recovered index with the slave nodes.

In order to update the index for the data which has been generated during the time of the backup, use the Web Admin Suite, menu Operation, menu item Index -> Rebuild index.