> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.zata.prathamchopde.site/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.zata.prathamchopde.site/_mcp/server.

# Arq Backup

Arq backs up your computer automatically and encrypts the backups with your own password. It stores them in a Zata bucket that you add as an **S3-Compatible Server** storage location.

## Before you start

* A bucket for the backups. See [Create a bucket](/buckets/create-a-bucket).
* An access key from the same region as the bucket. See [Access keys](/access/access-keys).
* [Arq](https://www.arqbackup.com/download/) installed (Windows or macOS).

## Connection settings

| Setting                           | Value                                                                                         |
| --------------------------------- | --------------------------------------------------------------------------------------------- |
| Server URL                        | `https://idr01.zata.ai` for Indore, `https://bom01.zata.ai` for Mumbai                        |
| Region                            | `us-east-1` (Zata does not check the region name)                                             |
| Access Key ID / Secret Access Key | From **Access Keys** in the Zata console. The key must be from the same region as the bucket. |
| Bucket Name                       | Your bucket name, for example `my-bucket`                                                     |

## Set up Arq

#### Create a backup plan

Open Arq and click **Create a backup plan**.

![Arq main window with the Create a backup plan button](/_fern-img/35cf9db299d409d86d8f690a03c4ba3ce3a1d6e93534963582ea154dd72201b1.webp)

#### Add a storage location

When Arq asks **Where should Arq store the backup data?**, click **Add Storage Location...**. Select **S3-Compatible Server** and click **Continue**.

![Where should Arq store the backup data dialog with the Add Storage Location button](/_fern-img/1a0beb34fe13b376be76f1c1b91750ad1f56cdf84fceeab2be28556c3b4bac2d.webp)![Add a Storage Location dialog with S3-Compatible Server selected](/_fern-img/a611670fb7afffc2abc1159c678e77b356154af001c710b8ba01754ed01da8ad.webp)

#### Enter the Zata details

Fill in the fields from the table above and click **Save**.

![S3-Compatible Storage Location dialog with server URL, region, access key ID, secret access key and bucket name](/_fern-img/a5d505c5a8f29dde1ae770e92b6e34727e827186cc554b225d6edf2fad8e9d8f.webp)

#### Confirm the storage location

Check that the Zata endpoint is selected and click **Continue**.

![Create Backup Plan dialog with https://idr01.zata.ai selected as the storage location](/_fern-img/cff9985bf69308cc1dfb28d265e17bf167593051fd0a38d32ac4eb00bde311e8.webp)

#### Set the encryption password

Tick **Encrypt with password**, enter a strong password twice, and click **Continue**. Keep the password safe: without it the backups cannot be restored, and Zata cannot recover it.

![Arq dialog asking for an encryption password](/_fern-img/7acd312fd5563a221e0b23c094c1ca581df2ad41e2bdb5167ce946c06ea1abda.webp)

#### Choose what to back up

Choose to back up all drives, your user data, or folders you pick, and click **Create Backup Plan**.

![Options to back up all drives, user data, or chosen folders, with the Create Backup Plan button](/_fern-img/9f4288f634c1e3887161bf07097bbe3f58d126d25238277eb0745da423bece46.webp)

## Test it

Back up a small folder, check that new files appear in your bucket in the Zata console, then restore one file with Arq to confirm it can be recovered.

## Troubleshooting

| Problem                              | Fix                                                                                 |
| ------------------------------------ | ----------------------------------------------------------------------------------- |
| Arq cannot connect                   | Check that **Server URL** starts with `https://` and matches the bucket's region.   |
| Access denied or invalid credentials | Copy the keys again from **Access Keys** and check that the key can use the bucket. |

For other errors, see [Signature errors](/help/troubleshooting/signature-errors) and [Endpoint and region](/help/troubleshooting/endpoint-and-region).