> 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/cortex-xsoar-6-multi-tenant-guides/6.12/configure-multi-tenant/configure-the-multi-tenant-deployment/reindex-a-specific-index-for-a-tenant.md).

# Reindex a Specific Index for a Tenant

In some cases, you might need to reindex a specific index database for a tenant, 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 index database at a time or [reindex the entire database](/cortex-xsoar-6-multi-tenant-guides/6.12/configure-multi-tenant/configure-the-multi-tenant-deployment/reindex-a-tenant-database.md). We recommend consulting with Cortex XSOAR support before reindexing.

{% hint style="info" %}

### Note

Depending on the volume of the data in the system, it may take some time for the indexing to complete. Reindexing a tenant requires machine resources and might have a temporary impact on the performance of other tenants.
{% endhint %}

1. Stop the tenant process.

   Go to **Settings** → **ACCOUNT MANAGEMENT** → **Accounts** , select the tenant account, and click **Stop**. Click **Stop** again to confirm.
2. Backup the index directory.

   **`tar -czvf /tmp/<TenantName>_index_bkp.tar.gz /var/lib/demisto/tenants/acc_<TenantName>/data/demistoidx`**

   The example command above uses the tmp directory. Any directory can be used, but the backup should not be stored under\*\* `/var/lib/demisto`\*\*.
3. Select the tenant account in the UI and click **Start**.
4. In **Additional arguments for tenant start**, add the following argument: **`-restore-index-name=`*****`indexName`***, and click **Start**.

   To reindex multiple indexes, use a comma separated list of index names for *indexName*.
5. View the tenant server.log.

   Status code 433 indicates that the database is being reindexed. Example: **`2022-09-27 14:55:58.7146 info [GET] "/health" 433 60.463µs, message-id: cb0cce4d-cb6d-48d4-8b3b-82b61804942b (source: /builds/GOPATH/src/code.pan.run/xsoar/server/web/middleware.go:79)`**

   When new 433 statuses no longer appear in the log, the tenant is reindexed.
6. From the server terminal, set permissions.

   **`sudo chown -R demisto:demisto /var/lib/demisto/tenants/acc_{`*****`TENANT_NAME`*****`}/data`**


---

# 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/cortex-xsoar-6-multi-tenant-guides/6.12/configure-multi-tenant/configure-the-multi-tenant-deployment/reindex-a-specific-index-for-a-tenant.md?ask=<question>&goal=<endgoal>
```

`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.