How to Configure Acronis Backup with S3-Compatible Object Storage
TL;DR
Acronis Backup Gateway supports any S3-compatible object storage as a backup destination, and ZATA plugs in through the AuthV2 (S3) driver.
You need an Acronis Cyber Protect Cloud partner account, a Backup Gateway (VM or bare metal), a ZATA bucket, and an Access/Secret key pair.
ZATA endpoints for the integration:
https://idr01.zata.ai(Central India) orhttps://bom01.zata.ai(Southern India).The setup takes under few minutes and gives you offsite, encrypted, S3 backup repository storage without per-restore egress penalties.
Ideal for MSPs and enterprise IT teams that want India-resident, cost-predictable backup and disaster recovery on object storage.
Why S3-compatible object storage belongs in your backup stack
Backup workloads are a bad fit for block storage. They're write-heavy, retention-heavy, and rarely read until something breaks. Object storage was built for exactly this shape: flat namespace, cheap per-GB pricing, and durability guarantees that make long-term retention affordable.
The catch has always been vendor lock-in. Teams that standardized on AWS S3 got stuck with egress bills the moment they needed to restore at scale. That's why S3-compatible object storage, running on independent infrastructure like ZATA, has become the default choice for enterprise backup storage in 2026.
Acronis Backup treats any S3-compatible endpoint as a first-class destination, so you get the operational maturity of Acronis with the economics of independent object storage.
Why ZATA for Acronis Backup Repositories
| Requirement | What ZATA provides |
|---|---|
| S3 compatibility | Full S3 API surface, AuthV2 and AuthV4 |
| Data residency | Central India (Indore) and Southern India (Mumbai) regions |
| Egress cost | No charges on standard restore traffic |
| Durability | Multi-node replication inside the region |
| Access control | Per-bucket Access/Secret key pairs |
Prerequisites
Before you start, have the following ready:
Acronis Cyber Protect Cloud partner account
Acronis Backup Gateway deployed as a VM or bare metal node, reachable on port
44445for inbound trafficAcronis Agent installed on every workload you plan to protect
ZATA account with a bucket created for backups
ZATA Access Key and Secret Key pair
A resolvable DNS name pointing to your Backup Gateway's public IP
Configure Acronis Backup with ZATA S3 storage
Step 1: Create the backup storage in Acronis Cyber Protect Infrastructure.
Go to Storage Services → Backup Storage → Create backup storage.
Step 2: Choose the storage type.
Select Public Cloud, pick your storage node, and on the next screen choose AuthV2 compatible (S3) from the dropdown. Acronis uses this driver for ZATA and most independent S3 providers.
Step 3: Enter the ZATA connection details.
| Field | Value |
|---|---|
| Endpoint URL | https://idr01.zata.ai or https://bom01.zata.ai |
| Bucket Name | Your dedicated Acronis backup bucket |
| Access Key | From ZATA console |
| Secret Key | From ZATA console |
Step 4: Pick a redundancy level.
Match this to your organisation's data protection policy. If you're unsure, talk to your Acronis representative before committing.
Step 5: Bind a DNS name and register.
Enter the DNS name that resolves to your gateway, then supply your Acronis partner credentials to register the Cyber Protect Infrastructure with the cloud console.
Step 6: Verify the location.
In your Acronis Cyber Protect Cloud console, go to Settings → Locations. The new ZATA-backed location should appear as available. Attach it to a customer tenant and trigger your first backup job.
Verify and Secure the Backup
Confirm objects land in ZATA. Open the bucket in the ZATA console after the first job completes. You should see the Acronis object hierarchy building up.
Encrypt at the source. Enable Acronis-side encryption before objects leave the gateway. ZATA also enforces TLS in transit.
Rotate keys. Cycle Access/Secret pairs on a schedule and revoke old keys from the ZATA console.
Separate buckets per tenant if you're an MSP, so blast radius stays contained.
Troubleshooting Quick Reference
| Symptom | Likely cause |
|---|---|
| Authentication failed | Wrong Access/Secret pair, or keys revoked in ZATA |
| Bucket not found | Region mismatch between endpoint and bucket location |
| Endpoint unreachable | Firewall blocking outbound HTTPS from the gateway |
| Registration fails | DNS name not resolving to gateway public IP, or port 44445 closed |
Wrapping up
Acronis plus ZATA gives you a backup repository that's cheap to keep, fast to restore, and hosted on infrastructure that stays inside India. No egress surprises, no lock-in, no rearchitecting your protection stack.
Ready to set this up?
Create your ZATA bucket and generate your Access Keys at zata.ai and point your Acronis Backup Gateway in just few minutes.
FAQs
1. Does ZATA work with the standalone Acronis Cyber Protect agent, or only with the Backup Gateway?
Both paths work, but the supported integration goes through the Backup Gateway, which handles S3 translation for all downstream agents.
2. Which ZATA endpoint should I pick?
Pick the region closest to your workloads. bom01.zata.ai for west and south India, idr01.zata.ai for central and north.
3. Is data encrypted on ZATA?
Yes. Traffic uses TLS in transit, and you can layer Acronis-side encryption before objects are written.
4. Can I use ZATA for immutable Acronis backups?
Object versioning and lifecycle policies on the ZATA bucket give you the building blocks for immutability. Combine with Acronis retention rules.
5. What happens to backups if I switch S3 providers later?
Because everything is S3-compatible, you can migrate the bucket contents with tools like rclone without touching Acronis job definitions.
