> For the complete documentation index, see [llms.txt](https://wiki.lucysecurity.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.lucysecurity.com/application-reference/settings/backup-and-restore.md).

# Backup and Restore

### Location of backup files

{% hint style="info" %}
Navigate to **Settings -> Backup & Restore > Backups**
{% endhint %}

All backups are stored in a centralized directory on your server: `/opt/phishing/backups`. Backups and exports are displayed in the dashboard under **Settings -> Backup & Restore**. 

<figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2FocS0DYS77UoKEGIgT2pE%2Fimage.png?alt=media&amp;token=90ac4ada-7662-4246-9223-e71411ee5b3c" alt=""><figcaption><p>Here you can view, download, and delete your backups and exports.</p></figcaption></figure>

***

### What data can I back up?

You can create backups of your campaigns and templates from the dashboard by selecting the object you want to backup and then selecting "Backup" from the Actions menu:

{% tabs %}
{% tab title="Campaigns" %}

<figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2FCeGAqePsj9OS51P4kfiq%2Fimage.png?alt=media&amp;token=257983c3-652e-452c-b70e-21fa9e7d0321" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
A campaign backup is a tar.gz archive that contains the following:

* Campaign settings and statistics.
* Email and Landing Page templates.
* LUCY version info.
  {% endhint %}
  {% endtab %}

{% tab title="Templates" %}

<figure><img src="https://3536856424-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FVYPsDfg76rUuy4DWfSsJ%2Fuploads%2F3RshaDC8LYFjd5UBUR1T%2Fimage.png?alt=media&amp;token=f53ff6dd-11a4-47b3-bb84-4b4ae0119abf" alt=""><figcaption><p>You can backup Attack, Awareness, Attachment (File), and Report templates. </p></figcaption></figure>

{% hint style="info" %}
A template backup is a .tar.gz archive that contains the following:

* Email and Landing Page files (html, css, javascript files).
* Static assets (like images and videos).
* SCORM data (if the template is SCORM-compatible).
  {% endhint %}
  {% endtab %}
  {% endtabs %}

***

### Restoring backups

You can restore backups to any LUCY server with the same Actions menu.\*

Just select "Restore" and then select the template's archive from your file browser.

{% hint style="warning" %}
\*Backups should be restored on a server running the same LUCY version as the one used to create the backup. Avoid mixing different versions to prevent compatibility issues.
{% endhint %}

***


---

# 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://wiki.lucysecurity.com/application-reference/settings/backup-and-restore.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.