> 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.15/configure-multi-tenant/configure-the-multi-tenant-deployment/back-up-a-tenant.md).

# Back Up a Tenant

Create manual or automatic backups of tenant databases in Cortex XSOAR 6.15 multi-tenant deployments.

With Cortex XSOAR, you can perform both automated and manual backups, which store the entire database of incidents, playbooks, scripts, and user-defined configurations. Cortex XSOAR stores daily, weekly, and monthly backup files. As of Cortex XSOAR version 6.1, any XSOAR service that uses the Elasticsearch database no longer runs automatic backups. To back up the contents of your Elasticsearch database, follow the instructions in the Elasticsearch documentation.

You can define whether you want Cortex XSOAR to create automatic backups, and the location to store the backups. The default directory for tenant database backup files is `/var/lib/demisto/tenants/acc_{TENANT_NAME}/backup`. In addition to automated backups, manual backups are recommended before doing server operations and maintenance work. We also recommend you set up backups for additional Cortex XSOAR folders listed in Step 3, scheduled for off-peak hours, using your standard backup tools.

1. Create a manual backup before server operations or maintenance work.
   1. Stop the tenant process.

      Go to Settings → ACCOUNT MANAGEMENT → **Accounts**, select the tenant account, and click **Stop**.
   2. Create the backup file. The default data directory for a specific tenant is `/var/lib/demisto/tenants/acc_{TENANT_NAME}/data`.

      `tar -czvf archive.tar.gz /var/lib/demisto/tenants/acc_{TENANT_NAME}/data`

      The backup of the database directory should not be stored under `/var/lib/demisto/tenants/acc_{TENANT_NAME}`.
2. Configure automated database backups.
   1. Select Settings → ADVANCED → **Backups**.
   2. Check that Automated Backups are enabled.
   3. **Backups Directory** - option to change where backups are stored.
   4. **Backup Time** - option to change the scheduled time for daily backups.
   5. Define the maximum number of daily, weekly, and monthly backups to store.
3. Backup additional directories.

   The following directories must be backed up manually:

   * `/var/lib/demisto/tenants/acc_{TENANT_NAME}/artifacts`
   * `/var/lib/demisto/tenants/acc_{TENANT_NAME}/attachments`
   * `/var/lib/demisto/tenants/acc_{TENANT_NAME}/images`
   * `/var/lib/demisto/tenants/acc_{TENANT_NAME}/d2_server.key`
   * `/var/lib/demisto/tenants/acc_{TENANT_NAME}/tools`
   * `/var/lib/demisto/tenants/acc_{TENANT_NAME}/versionControlRepo`
   * `/usr/local/demisto`
   * `/etc/demisto.conf`


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://cortex-docs.paloaltonetworks.com/cortex-xsoar-6-multi-tenant-guides/6.15/configure-multi-tenant/configure-the-multi-tenant-deployment/back-up-a-tenant.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.