> For the complete documentation index, see [llms.txt](https://docs.output.industries/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.output.industries/admin/backups.md).
# Backups
#### **Context:**
Periodic snapshots of platform data.
#### **Importance:**
Ensures data integrity.
#### Setup:
Backups, Metrics and Downtime downloads can be found in this page of Busroot.
Each file represents a different “view” of what is happening on the line. Together they let you explain when you ran, what you produced, and where time was lost.
### Downtime file
* Contains one row per **downtime event** with start and end timestamps, duration, and whether the event is still ongoing.
* Lets you see which station was down, for which SKU/work order, and for how long.
### Production file
* Contains one row per **completed unit (or batch)** with good/bad quantity, station, SKU, work order, and the exact time the last unit was produced.
* Lets you see how many good/bad parts each station produced over time, and calculate things like throughput and effective cycle time.
### Metrics file
* Contains **minute‑by‑minute performance metrics** per station and SKU, including scheduled time, productive time, downtime, good/bad counts, and production rate per hour.
* Lets you build higher‑level KPIs such as OEE-style views, lost production cost, and compare actual vs ideal/target rates across the shift.
---
# 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://docs.output.industries/admin/backups.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.