> For the complete documentation index, see [llms.txt](https://docs.monokot.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monokot.io/time-series-and-stores/stores/backlog.md).

# Backlog

Backlog is designed to prevent data disappearance in the event of long-term loss of communication with the target store. This is achieved by saving data to the local disk and writing it again after the connection is restored. The backlog mechanism is available for all store types and offers the following settings:

* **Mode**: specifies backlog mode (*None* – do not use backlog, *Cyclic* – write files to disk cyclically).
* **File Size:** specifies the maximum backlog file size (in KB) that can be saved for each time series.
* **Files Count**: specifies the maximum number of files that can be saved for each time series. When this value is reached, the files are cyclically overwritten.
* **Buffer Size**: specifies the number of samples at which the backlog file is flushed to disk.
* **Flush Interval**: specifies the interval (in seconds) after which the backlog file is flushed to disk.

By default, the backlog is saved in the following directories:

* **Windows**: %ProgramData%\Monokot\Mos\Backlog\ (C:\ProgramData\Monokot\Mos\Backlog)
* **Linux**: /usr/share/Monokot/Mos/Backlog/

{% hint style="info" %}
Please note that these directories are hidden file system directories
{% endhint %}

You can change the backlog directory in the server [<mark style="color:blue;">startup settings</mark>](/basics/startup-parameters.md).


---

# 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.monokot.io/time-series-and-stores/stores/backlog.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.