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

# Iperius Backup

Iperius Backup is Windows backup software. It can send backup jobs to a Zata bucket through its **Amazon S3** cloud destination, which works with S3-compatible storage.

## 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).
* [Iperius Backup](https://www.iperiusbackup.com/) installed.

## Connection settings

| Setting                           | Value                                                                                         |
| --------------------------------- | --------------------------------------------------------------------------------------------- |
| Type                              | **S3**                                                                                        |
| Access Key ID / Secret Access Key | From **Access Keys** in the Zata console. The key must be from the same region as the bucket. |
| Service Point (URL)               | `idr01.zata.ai` for Indore, `bom01.zata.ai` for Mumbai                                        |
| Use SSL                           | Ticked                                                                                        |
| Signature version                 | `4`                                                                                           |
| Bucket name (S3)                  | Your bucket name, for example `my-bucket`                                                     |

## Set up Iperius Backup

#### Create a backup job

Open Iperius Backup and click **Create new backup**.

![Iperius Backup home screen with Create new backup](/_fern-img/c1a51665e255196bd90919ad5c30dc4abf8d5e639a444d3c32f5fd9e9b419a1d.webp)

#### Add what to back up

On the **Items** tab, use **File or Folder** to add the files and folders you want to back up. Filters and exclusions are optional.

![Items tab of a new backup job with the Add new item buttons](/_fern-img/48e9ccb5f41b561e34a7b1e8357fd30ed47a41dd97aa0aa3994647ee34acb22e.webp)

#### Add a Zata cloud account

On the **Destinations** tab, add a **Cloud** destination, choose **Amazon S3**, and click **New Account**. Enter a **Name** (for example `zata`), fill in the fields from the table above, and click **Save**.

![Add new Cloud account window with type S3, service point idr01.zata.ai, Use SSL ticked and signature version 4](/_fern-img/4b8f872dc53f7a59c57f913fc7a17c16f08e81fa5219ad4bf52f65e532dc6d3f.webp)

#### Choose the bucket and options

Select the new account under **Account Cloud** and enter your **Bucket name (S3)**. Optionally add a **Subpath**. Choose the **Backup type** and **Number of copies**, and turn on zip compression and a zip password if you want them. Click **OK**.

![Add or edit Cloud destination window with the account, bucket name, backup type and zip compression options](/_fern-img/0d05196e70d8286fde5709dde71f3a71dfd59cdd8f74e1ca347f776aa9285213.webp)

#### Set a schedule

On the **Scheduling** tab, tick **Run backup automatically using the following scheduling**, choose the days, and add the times.

![Scheduling tab with weekly, monthly and interval options and the list of execution times](/_fern-img/4a8d4a0b0effa5adc22247ef71f2effcd7964797ac36281e5ca5f1cbe5da67c7.webp)

#### Save the job

On the **Summary** tab, enter a **Job name** and click **OK**.

![Summary tab with the job name field](/_fern-img/b38b8ea219b6bdf840560009256c6043c2a5a531ebf707df6fbcb1f78e265c73.webp)

> **Note**
>
> For immutable backups, create the bucket with Object Lock turned on before you set up the job. Object Lock can only be turned on when you create a bucket. See [Object Lock](/buckets/object-lock/overview).

## Test it

Run the job once by hand with a small file. When it reports **Backup completed successfully**, check that the file is in your bucket in the Zata console. Then restore it with Iperius to confirm it can be recovered.

![Iperius Backup window reporting Backup completed successfully, with the See log button](/_fern-img/1cd840b8fc4f51c8ab383a77fc977e00c9cb28abbf55e34521b2c1644085e73f.webp)

## Troubleshooting

| Problem                              | Fix                                                                                                                      |
| ------------------------------------ | ------------------------------------------------------------------------------------------------------------------------ |
| The backup fails                     | Click **See log** after the backup to read the error.                                                                    |
| Access denied or invalid credentials | Check the keys and the **Service Point** in the cloud account, and that the bucket exists in the same region as the key. |
| Signature or time errors             | Make sure the computer's clock is correct. See [Clock and credentials](/help/troubleshooting/clock-and-credentials).     |
| Large files fail but small ones work | See [Large uploads](/help/troubleshooting/large-uploads).                                                                |

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