> For the complete documentation index, see [llms.txt](https://docs.copia.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.copia.io/docs/devicelink/jobs/manual-backups.md).
# Manual Backups
## Overview
While Jobs will usually be set to run on a recurring schedule, it might sometimes be necessary to run a Project backup manually.
## Performing a Manual Backup
To initiate an on-demand backup, navigate to the *Projects* tab and find the Project you wish to backup manually. Click the *Backup Now* button to start the backup. You will find this same button on the Job and Device cards that are linked to your Project, so you can also start a Project backup from those Site assets as well.
{% hint style="warning" %}
You can only run manual backups for a Project whose supporting Agent is online. The status color on the left of the Project card shows if the Agent is online and able to perform the backup.
{% endhint %}
Your manual backup will initiate and you should be redirected to the *Job History* tab to see the progress of your backup.
{% hint style="info" %}
An on-demand backup will be listed as a "Manual Run" and will also display the avatar of the user who initiated the Project backup.
{% 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://docs.copia.io/docs/devicelink/jobs/manual-backups.md?ask=&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.
