Browse articles

Database backup

# Installing the backup agent on a server

Install the lt-backup agent on a Linux server with a single command, register the server in the dashboard, check its status, and update the agent without reinstalling.

3 min readUpdated: October 22, 2026[Baca dalam Bahasa Indonesia](/docs/pasang-agent)

The `lt-backup` agent is a small program that runs on your database server. It runs database dumps on schedule, compresses and encrypts the output, and uploads it straight to the backup destination. The agent only opens outbound connections; no inbound ports need to be opened.

## Requirements

-   Linux x86\_64 (amd64) or arm64 with systemd, and root access (`sudo`).
-   Outbound HTTPS to `https://linuxteknosia.cloud` and to the backup destination endpoint.
-   The database's own dump tools on the PATH: `mysqldump` and `mysql`, `pg_dump`/`pg_dumpall`/`pg_restore`/`psql`, or `mongodump`/`mongorestore`.
-   An active backup plan. The number of servers is limited by the plan.

## 1\. Create an enrollment token

1.  Open **Servers** in the sidebar.
2.  In the **Add a server** card, enter a **Server name** (optional; without a name the server's hostname is used).
3.  Click **Add server**. The dashboard shows the install command with a single-use token valid for 24 hours.

## 2\. Run the install command

Copy the command with **Copy command**, then run it on the server as root:

```bash
curl -fsSL https://linuxteknosia.cloud/install.sh | sudo bash -s -- --server https://linuxteknosia.cloud --token <token from the dashboard>
```

The installer downloads the binary to `/usr/local/bin/lt-backup`, registers the server with the token, writes the `lt-backup.service` systemd unit, and starts it. The agent's configuration and credentials are stored in `/etc/lt-backup`.

## 3\. Confirm the agent is connected

The dashboard card changes to **Agent connected** as soon as the first heartbeat arrives; click **Open server** to continue. The agent sends a heartbeat every 60 seconds. On the server you can also check:

```bash
systemctl status lt-backup
sudo lt-backup status
journalctl -u lt-backup -n 50
```

`lt-backup status` shows the version, server ID, control plane address, the number of stored connections, and whether the control plane is reachable.

## 4\. Manual install (optional)

If you prefer not to run `curl | bash`, open the **manual install** section of the same card. Download the binary from `https://linuxteknosia.cloud/agent/lt-backup-linux-amd64` (or `-arm64`), save it as `/usr/local/bin/lt-backup`, then run:

```bash
sudo lt-backup connect --server https://linuxteknosia.cloud --token <token from the dashboard>
sudo lt-backup install && sudo systemctl daemon-reload && sudo systemctl enable --now lt-backup
```

## 5\. Update the agent

The server detail page shows the agent version and the latest version. When the agent is behind, an **Update agent** button appears. The agent downloads the new binary, verifies its SHA-256 checksum, replaces itself, and is restarted by systemd; the new version shows on the next heartbeat. If the checksum does not match, the agent keeps the old binary.

Manual update from the server:

```bash
sudo lt-backup update && sudo systemctl restart lt-backup
```

## 6\. Rename or delete a server

On the server page, change the **Server name** and click **Save** (the hostname is not changed). **Delete server** also deletes its connections, jobs, and history; artifacts in the bucket are kept.

## Troubleshooting

-   **"jalankan sebagai root (sudo)"**: run the command with `sudo`.
-   **"arsitektur ... belum didukung" (architecture not supported)**: the agent is available for amd64 and arm64.
-   **Registration fails**: the token works only once and for 24 hours. Create a new one from **Add server**.
-   **Server limit message from your plan**: upgrade under **Subscription & billing** or delete servers you no longer use.
-   **Update fails with "read-only file system"**: older agents use a systemd unit that does not yet allow replacing the binary. Run `sudo lt-backup install && sudo systemctl daemon-reload && sudo systemctl restart lt-backup` once, then send the update again.
-   **The server shows as offline**: read [Agent offline](/help/agent-offline).

## See also

-   [Connecting a database](/docs/koneksi-database)
-   [Scheduling backups](/docs/jadwal-backup)

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)