> 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.

# Syncovery

Syncovery backs up and synchronises folders on Windows, macOS and Linux. It connects to Zata with its **S3** protocol. You put the Zata endpoint in the bucket field, as `bucketname@host`.

## Before you start

* A bucket. See [Create a bucket](/buckets/create-a-bucket).
* An access key from the same region as the bucket. See [Access keys](/access/access-keys).
* [Syncovery](https://www.syncovery.com/) installed.

## Connection settings

| Setting                | Value                                                                                         |
| ---------------------- | --------------------------------------------------------------------------------------------- |
| Protocol               | **S3**                                                                                        |
| Access ID / Secret Key | From **Access Keys** in the Zata console. The key must be from the same region as the bucket. |
| Provider               | **Custom ([bucketname@host.url](mailto:bucketname@host.url))**                                |
| Bucket                 | `my-bucket@idr01.zata.ai` for Indore, `my-bucket@bom01.zata.ai` for Mumbai                    |
| Storage Class          | **Standard Storage Class** (Zata has one storage class)                                       |

## Set up Syncovery

#### Start a new profile

On the welcome screen, click **Perform a synchronization or backup now**.

![Syncovery welcome screen with Perform a synchronization or backup now](/_fern-img/396beceb59810c07ab0d4491f840a21ed4d518fa6a659d778619ec8637ad04da.webp)

#### Choose the local folder

In **Specify Folders**, set **Left-Hand Side** to the local folder you want to back up or sync.

![Specify Folders step with the left-hand and right-hand side paths and the globe buttons](/_fern-img/13b50149069af987b2e73d718da39cce2d77189bdf58cf0b0824ce44c1b09416.webp)

#### Set Zata as the right-hand side

Next to **Right-Hand Side**, click the globe button to open **Internet Protocol Settings**. Set **Protocol** to **S3** and fill in the fields from the table above. Optionally enter a **Folder** inside the bucket. Click **OK**.

![Internet Protocol Settings with protocol S3, the Custom provider and the bucket written as bucketname@idr01.zata.ai](/_fern-img/093f22af77e583bbafa169f1d659c05678657e4386a433d6214db1f863d39d6a.webp)

#### Set a schedule

Go through the next steps. In **Specify Timer Settings**, tick **Schedule This Profile** and choose when it runs. Save the profile at the end of the wizard.

![Specify Timer Settings step with Schedule This Profile ticked and a run interval](/_fern-img/75f3d4c8a143259ffc9adff021823b6bf98f41c459503a857e6abfdeaea4774f.webp)

## Test it

Put a small file in the local folder. On the welcome screen, click **Edit or run one of my saved profiles**, select your profile and click **Run Profile**. Check the job log, then check that the file is in your bucket in the Zata console. Use **Restore Files** to confirm you can get it back.

![Choose A Profile window with the Run Profile and Restore Files buttons](/_fern-img/5d2ffa931d5e718acbe0115e88e995b9fd31392e8a77533b1a10acf9a2dee2ff.webp)

## Troubleshooting

| Problem                                    | Fix                                                                                                                                                                                                       |
| ------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Cannot connect, or the bucket is not found | Write **Bucket** as `my-bucket@idr01.zata.ai` (or `@bom01.zata.ai`) with **Provider** set to **Custom ([bucketname@host.url](mailto:bucketname@host.url))**. Without the host, Syncovery connects to AWS. |
| Access denied or invalid credentials       | Copy the keys again from **Access Keys** and check that the key can use the bucket.                                                                                                                       |
| Error about the storage class              | Choose **Standard Storage Class**. Zata has one storage class.                                                                                                                                            |
| Files do not appear                        | Open the job log for the profile and look for the failed file.                                                                                                                                            |