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

# cPanel

WHM can send cPanel account and system backups to a Zata bucket. You add Zata as an **S3 Compatible** additional destination in **Backup Configuration**.

## Before you start

* A bucket for the backups, with a name without dots, for example `cpanel-backups`. With virtual-host style addressing (`my-bucket.idr01.zata.ai`), a dot in the name breaks the certificate check. See [Create a bucket](/buckets/create-a-bucket).
* An access key from the same region as the bucket. See [Access keys](/access/access-keys).
* Root access to WHM.

## Connection settings

| Setting                           | Value                                                                                         |
| --------------------------------- | --------------------------------------------------------------------------------------------- |
| Destination Type                  | **S3 Compatible**                                                                             |
| S3 Endpoint                       | `idr01.zata.ai` for Indore, `bom01.zata.ai` for Mumbai (no `https://`, port or path)          |
| Bucket                            | Your bucket 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. |
| Timeout                           | Leave the default (`30`)                                                                      |

## Set up WHM

#### Open Additional Destinations

In WHM, open **Backup** → **Backup Configuration** and select the **Additional Destinations** tab. Set **Destination Type** to **S3 Compatible** and click **Create New Destination**.

![WHM Backup Configuration page with the Additional Destinations tab, S3 Compatible destination type and Create New Destination](/_fern-img/db1113937054988d0b6f3d6fac2fa9c2369474b6c0b73ce0a4fe428f480bf199.webp)

#### Name the destination

Enter a **Destination Name**, for example `zata-backup`. Tick **Transfer System Backups to this Destination** if you also want system backups sent to Zata.

Leave **Only use this destination for log file transfers** unticked. When it is ticked, account and system backups are not sent to this destination.

#### Enter the Zata details

Fill in **S3 Endpoint**, **Bucket**, **Access Key ID**, **Secret Access Key** and **Timeout** from the table above. Click **Save and Validate Destination** (or **Save Destination**).

![Destination form with S3 endpoint idr01.zata.ai, bucket, access key ID, secret access key, timeout 30 and the save buttons](/_fern-img/1829271f41cbfab937c597bb138a32a491c552e88d5f265e9377e93e11badda0.webp)

The destination appears in the list with the transport **S3Compatible**. Click **Validate** to test the connection again at any time.

![Additional Destinations list with the Zata destination and the Edit, Delete, Validate and Disable actions](/_fern-img/61132325929fa1e626675c77ead77015d06c5540014788d70323e29971b38d43.webp)

#### Turn on backups

On the **Backup Settings** tab, turn backups on, set the schedule and retention, and save. Choose which accounts are backed up in **Backup** → **Backup User Selection**.

## Test it

Let a backup run to the new destination. Open your bucket in the Zata console and check that the backup files are there, then download one to confirm it can be retrieved.

## Troubleshooting

| Problem                                             | Fix                                                                                                                                |
| --------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |
| **Validate** fails                                  | Check that **S3 Endpoint** is only the host name (`idr01.zata.ai`) and matches the bucket's region.                                |
| **Validate** fails with an SSL or certificate error | If the bucket name has a dot, use a bucket without dots in its name.                                                               |
| Access denied                                       | Copy the keys again from **Access Keys** and check that the key can use the bucket.                                                |
| No backups appear in the bucket                     | Check that **Only use this destination for log file transfers** is unticked, backups are turned on, and the accounts are selected. |

For other errors, see [Access denied](/help/troubleshooting/access-denied) and [Network and certificates](/help/troubleshooting/network-and-certificates).