Browse articles

Database backup

# Backup destinations: managed bucket, external S3, and Google Drive

Choose where backup artifacts are uploaded: the built-in managed bucket, your own S3-compatible bucket, or Google Drive, including how to connect and test each one.

3 min readUpdated: October 23, 2026[Baca dalam Bahasa Indonesia](/docs/tujuan-backup)

A destination is where the agent uploads backup artifacts. Each job picks one destination in the **Storage** step. The list of destinations is under **Settings → Storage destinations**.

## Destination types

Destination

How to connect

Download from the dashboard

Managed bucket

created automatically at sign-up

15-minute presigned URL

External S3

enter the endpoint and keys, tested before saving

15-minute presigned URL

Google Drive

**Connect Google Drive** button (OAuth)

15-minute signed link

External S3 buckets and Google Drive are available from the Business plan.

## 1\. Managed bucket

Every organisation gets a **managed** destination at sign-up, so the first job can be created without any configuration. If a job does not pick a destination, the first one in the list is used.

## 2\. Add an external S3 bucket

1.  Open **Settings → Storage destinations**.
2.  Click **Add external S3 bucket**.
3.  Fill in **Name**, **Endpoint**, **Region** (empty = `us-east-1`), **Bucket**, **Prefix (optional)**, **Access key**, and **Secret key**.
4.  Click **Test & save**. The connection to the bucket is tested first; the destination is only saved if the bucket can be accessed.

Any S3-compatible provider works (for example Wasabi, AWS, MinIO). You can also use a bucket in your own Linuxteknosia Cloud object storage: enter the endpoint `https://storage.linuxteknosia.cloud`, region `id-jkt-1`, the bucket name exactly as shown in the dashboard (for example `backup-example-co`), and an access key [restricted to that bucket](/docs/access-key).

## 3\. Connect Google Drive

1.  Under **Settings → Storage destinations**, click **Connect Google Drive**.
2.  Sign in to your Google account and grant access. The application only requests access to files it creates itself (the `drive.file` scope).
3.  Back in the dashboard, a message confirms that Google Drive is connected. Choose this destination when creating a job.

Files are stored in the `Linuxteknosia Cloud Backup/<organisation>` folder. The Google token is stored encrypted in the control plane; the agent only receives a short-lived access token for each run or restore.

## 4\. Object name structure

Artifacts are stored with the following pattern, so they are easy to trace per server, job, and date:

```bash
{prefix}/{server_id}/{job_id}/YYYY/MM/DD/{db}-HHMMSS.{sql|dump|archive}[.zst|.gz][.age]
```

The `.zst` or `.gz` extension indicates compression and `.age` indicates an encrypted artifact.

## 5\. Delete a destination

Click the delete icon on the destination and confirm. Before deleting, move any job that still uses it to another destination through the job settings.

## Troubleshooting

-   **"tidak bisa mengakses bucket: ..."** (cannot access the bucket): check the endpoint (including `https://`), bucket name, region, access key, and secret key. Make sure the key can read and write the bucket.
-   **"destination eksternal ... tersedia mulai paket Business"**: upgrade under **Subscription & billing**.
-   **"Google Drive could not be connected"**: start again from **Connect Google Drive** and make sure you grant access on Google's consent screen.
-   **Uploads to the destination fail during a backup**: check the run log and [Backup failed](/help/backup-gagal).

## See also

-   [Scheduling backups](/docs/jadwal-backup)
-   [Restoring a backup](/docs/restore)

Still need help?

Open a support ticket from the dashboard and our team will reply as soon as possible.

[Help center](/en/help)[Open a ticket](/app/support/new)