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

# Acronis

Acronis Cyber Protect can keep backups in a Zata bucket. You add the bucket as **Public cloud** backup storage on an Acronis Backup Gateway, then register the gateway with your Acronis Cyber Protect Cloud partner account.

![Diagram of the backup agent, the Acronis Storage Gateway, Acronis Backup Cloud and Zata with the ports between them](/_fern-img/ffc8411e6901d96be71608acbbc65978d176b88faed3d1a257a34006a88ef10e.webp)

## 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).
* An Acronis Cyber Protect Cloud partner account. See the [Acronis partner page](https://www.acronis.com/en-us/partners/).
* An Acronis Backup Gateway (VM or bare metal). See the [Acronis Backup Gateway quick start](https://dl.acronis.com/u/storage2/html/AcronisStorage_2_quick_start_guide_en-US/index.html).
* The Acronis Agent on each machine you want to protect. See the [Acronis Agent install guide](https://kb.acronis.com/content/55052).
* A DNS name that resolves to the gateway's IP address, with inbound port 44445 open on the gateway.

## Connection settings

| Setting                                               | Value                                                                                         |
| ----------------------------------------------------- | --------------------------------------------------------------------------------------------- |
| Object storage type                                   | **AuthV2 compatible (S3)**                                                                    |
| Endpoint URL                                          | `https://idr01.zata.ai` for Indore, `https://bom01.zata.ai` for Mumbai                        |
| Bucket                                                | Your bucket name, for example `my-bucket`                                                     |
| Access key ID / Secret key ID                         | From **Access Keys** in the Zata console. The key must be from the same region as the bucket. |
| Allow using a self-signed certificate of the endpoint | Leave unticked. Zata uses a public certificate.                                               |

## Set up the gateway

#### Start the wizard

In the Acronis Cyber Infrastructure console of the gateway, open **Storage Services** → **Backup storage** and click **Create backup storage**.

![Backup storage page with the Create backup storage button](/_fern-img/e0b9aa376d6f3614cc59def233e26089cc1493fb55fb0f4a3baa2c1d0380789b.webp)

#### Choose Public cloud

Under **Backup destination**, choose **Public cloud** and click **Next**.

![Backup destination step with Public cloud selected](/_fern-img/2116e8d32db56afd0dd2527abfab36d125960650859094c482d1af82dc1f6f41.webp)

#### Select the gateway nodes

Tick the node or nodes that will act as the gateway and click **Next**.

![Nodes step with the backup gateway node ticked](/_fern-img/c8de71fb60d404a6af6cbb70a7da669e099b2d8fecc93429d742aaa1f60d3bc5.webp)

#### Connect to Zata

Set **Object storage type** to **AuthV2 compatible (S3)**. Fill in **Endpoint URL**, **Bucket**, **Access key ID** and **Secret key ID** from the table above. Leave **Allow using a self-signed certificate of the endpoint** unticked, then click **Next**.

![Object storage type list with AuthV2 compatible (S3) highlighted](/_fern-img/30bf7f4f4fd8eb4f1a8e08c2aa1b565c4cb3300701e7a3b10eead05e4a56c2c9.webp)![Public cloud step with the endpoint URL, bucket and blurred access keys](/_fern-img/1520f0cfddaa4269bdce54a28c0db65e7091672e7b7c03405871d4f0b0ebe60f.webp)

#### Choose a storage policy

Choose the **Tier**, **Failure domain** and **Redundancy** that fit your policy, then click **Next**. Ask your Acronis representative which redundancy level suits your setup.

![Storage policy step with tier, failure domain and redundancy](/_fern-img/90f3108298328b35029d29798757029fd48b164ae0ba9cbcf6eecb3ffb6ecc14.webp)

#### Enter the domain name

Enter the **Domain name** of the gateway and click **Next**. It must be a real DNS name that resolves to the gateway's IP address, and the gateway must accept inbound connections on port 44445.

![DNS step with the domain name field and an example DNS zone](/_fern-img/f74a7987855b859b51c1b25f13f0c1473f61bf5ff10d6b87c4e02b3d1fdb9ffa.webp)

#### Register with your Acronis account

Enter the address and the credentials of your Acronis partner account and click **Next**.

![Acronis account step with the portal address, user name and password](/_fern-img/d2f1fbce00ea3d1fd2534c0329c0f711507f8dc50982a5ac982354571442a92a.webp)

#### Create the storage

Review the **Summary** and click **Create**.

#### Check the registration

On the **Backup storage** page, open the **Registrations** tab and check that the registration is listed.

![Registrations tab of the backup storage with one registration](/_fern-img/a1b5902706ae54a49ae6da1a1f73d217e9446f979fbad20ec91dba1d4b38ee15.webp)

Then sign in to your Acronis Cyber Protect Cloud partner account, open **Settings** → **Locations**, and check that the new location is there.

![Locations page of the Acronis partner portal with the new gateway location](/_fern-img/36190a877e24f66b8d7cd005aa7da8b948bb2aed5066273b068eba773544ceb9.webp)

## Test it

Assign the new storage to a customer, back up a small folder, and check that backup data appears in your bucket in the Zata console. Then restore the folder to confirm the backup can be recovered.

## Troubleshooting

| Problem                                        | Fix                                                                                                                                                                                                    |
| ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| Access denied or invalid credentials           | Copy the keys again from **Access Keys**, without extra spaces. The key must be from the same region as the **Endpoint URL**.                                                                          |
| Cannot connect to the endpoint                 | Check that the **Endpoint URL** matches the bucket's region and that the gateway allows outbound HTTPS (port 443).                                                                                     |
| Certificate error                              | Do not tick the self-signed certificate option. Check the gateway's date and time, and that no proxy intercepts HTTPS. See [Network and certificates](/help/troubleshooting/network-and-certificates). |
| Registration fails                             | The domain name must resolve to the gateway's IP address, and inbound port 44445 must be open.                                                                                                         |
| The location is missing in the partner account | Open the **Registrations** tab on the gateway and check that registration finished.                                                                                                                    |