> For the complete documentation index, see [llms.txt](https://docs.geodin.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.geodin.com/geodin-onsite/configuration/backups.md).

# Backups

Onsite includes an **automatic backup feature** that protects your work against mistakes, crashes, and accidental deletion. When enabled, Onsite takes timed snapshots of your active form at regular intervals and keeps a fixed number of previous versions. You can restore any saved version via the Tools menu.

## Enable backups

Backups are off by default. To turn them on:

1. Open **Configuration → Backups**.
2. Tick **Do timed backups**.
3. Set the interval, backup folder, and retention count (see below).

## Backup settings

| Setting              | What it controls                                           | Example                                                     |
| -------------------- | ---------------------------------------------------------- | ----------------------------------------------------------- |
| **Interval**         | How often to take a snapshot, as HH:MM:SS                  | `00:00:30` = every 30 seconds; `00:02:00` = every 2 minutes |
| **Backup folder**    | Where the snapshots are stored                             | Default: `[AppData]\GeoDin.Onsite\backups`                  |
| **Versions to keep** | How many snapshots to retain before overwriting the oldest | `10` (the default)                                          |

<figure><img src="/files/p1MYeANZjydmGEv3eqvf" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**Notes:**

* Backups run automatically - you don't need to press Save.
* Forms are also saved automatically when closed or when Onsite exits.
* Backup files are named with a combination of location name, form code, and date.
* Older forms remain accessible via **Load Local**, allowing you to retrieve previous work.
  {% endhint %}

## Choosing your backup frequency

More frequent backups = better protection, but more disk usage. For a typical project:

* **Every 30 seconds** - suitable for fast-moving, high-stakes work (field drilling with complex forms)
* **Every 2-5 minutes** - fine for office-based work on stable data
* **Longer intervals** (15+ minutes) - leave you exposed if a crash happens; not recommended while actively editing

## Restore a backup

To restore a previous version of a form:

1. From the main menu, open **Tools → Restore backups**. The backup browser shows your recent forms - pick the form you want to restore.

<figure><img src="/files/uSXZov70TZpLlQ6RTbQM" alt=""><figcaption></figcaption></figure>

2. Browse the saved versions for that form. Each entry is a snapshot; select one to preview it in read-only mode.
3. When you've found the version you want, click **Restore**. Onsite asks for confirmation before overwriting the current form with the selected version.

<figure><img src="/files/AaCg5lT53OXAChjgqJVE" alt=""><figcaption></figcaption></figure>

{% hint style="danger" %}
Restoring overwrites the current version of the form - the action cannot be undone. Make sure you really want to discard the current state before confirming.
{% endhint %}

***

**See also**

* [Folder structure](/geodin-onsite/core-concepts/folder-structure.md) - where the `backups/` folder lives
* [Forms & projects](/geodin-onsite/core-concepts/forms-and-projects.md) - how forms are saved automatically


---

# 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:

```
GET https://docs.geodin.com/geodin-onsite/configuration/backups.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.