® Connections applications maintain delete and access-control update information for a maximum of 30 days. Indexes that are more than 30 days old are not considered suitable for restoration because they might contain obsolete or orphan content.
You can use a backup copy of the Search index to restore the index in the event of loss or corruption. You must restore the backup consistently for all the nodes in your deployment.
To restore a Search index in the event of loss or corruption, complete the following steps:
1. Disable any regular indexing tasks that you have configured.
a. To list the indexing tasks, enter the following command:
b. To disable tasks, enter the following command:
There is only one indexing task by default.
2. To prepare the HOMEPAGE database to successfully load the restored indexes on each node, enter the following command:
where the isNewIndex parameter specifies whether all entries are removed from the database table that is used by the file content extraction process to track the status of individual files. Set the parameter to false when you are restoring an index backup.
For more information about this command, see Backing up the Search index using wsadmin commands
3. On each Search node, delete the contents of the index directory and all its subdirectories from the IBM
Connections Search data directory.
4. On each Search node, copy the backup index and all its subdirectories into the Search directory.
5. On each Search node, reload the index using the following command:
6. Re-enable your indexing task or tasks using the SearchService.enableAllTasks()
If you don't want to enable all tasks (for example, if some tasks were disabled before you started these steps and you want to keep them disabled), use the SearchService.enableTask(String taskName) command instead to enable one task at a time.
The next indexing task to run resumes indexing at the point at which the restored index was last successfully indexed.