> For the complete documentation index, see [llms.txt](https://cortex-docs.paloaltonetworks.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/manage-data/reindex-a-specific-index-database.md). # Reindex a Specific Index Database In some cases, you might need to reindex a specific index database, if you encounter incorrect or partial data in Cortex XSOAR. Reindexing processes all data for that index database and ensures it is fully available for searches in the Cortex XSOAR UI. If issues are appearing related to multiple indexes, you can reindex more than one database at a time by listing the indexes as a comma separated list or you can [Reindex the Entire Database](/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/manage-data/reindex-the-entire-database.md). Depending on the volume of the data in the system, it may take some time for the indexing to complete. We recommend consulting with Cortex XSOAR support before reindexing. {% hint style="info" %} ### Note If using Live Backup, the index database must be reindexed on both the production and backup servers. {% endhint %} 1. Stop the Cortex XSOAR service using the appropriate command for your OS. * `systemctl stop demisto` * `sudo service demisto stop` 2. Back up the index directory by typing the following command: `tar -czvf filename.tar.gz /var/lib/demisto/data/demistoidx`

Note

The backup of the index directory should not be stored under /var/lib/demisto.

3. Run the server and specify the index as an argument. To re-index multiple indexes, use a comma separated list of index names for `indexName`. `sudo /usr/local/demisto/server -restore-index-name=`*`indexName`*` `` ``-public /usr/local/demisto/dist -stdout -conf /etc/demisto.conf ` For example, to reindex playbooks and scripts, run `sudo /usr/local/demisto/server -restore-index-name=playbooks,scripts -public /usr/local/demisto/dist -stdout -conf /etc/demisto.conf` 4. Log in to your Cortex XSOAR instance and verify that the reindex process was successful. 5. When a message appears stating `Server up and running, good luck to us all` or the Cortex XSOAR UI displays, verify that all the data is present from the reindexing, and stop the process by pressing `Ctrl+C` or `Cmd+C`. 6. Set permissions by running the following command. `sudo chown -R demisto:demisto /var/lib/demisto/data` 7. Start the Cortex XSOAR service using the appropriate command for your OS. * `systemctl start demisto` * `sudo service demisto start` --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://cortex-docs.paloaltonetworks.com/xsoar-6-administrator-guide/6.13/learn-about-cortex-xsoar/customize-and-configure-cortex-xsoar/manage-data/reindex-a-specific-index-database.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.